]> Apple Inc

castiz@apple.com

Apple Inc

a_pelletier@apple.com

ART TIGRESS tigress GSS API sample implementation This document describes a sample implementation of transferring digital credentials securily (Tigress) using GSS API. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Source for this draft and an issue tracker can be found at .

Introduction Prevously Tigress reviewed an implementation of digital credentials transfer using Tigress protocol (https://datatracker.ietf.org/doc/draft-art-tigress/). In previous IETF meetings community asked to review other possible solutions using alternative standards to illustrate how Tigress problem can be solved differently. In this document we are trying to describe how an alternative potential implementation of a solution to Tigress problem of transferring digital credentials securily can be done using GSS API .

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

GSS-Api Proposal General security service application program interface, or GSS-API, from defines a generic protocol for the security of messages being transferred and can provide authentication, integrity, and confidentiality. GSS-API does not define how the messages are sent between parties. Leveraging GSS-API provides flexibility to easily change the security of how a credential is transferred, but a lot of work to define the communication channel between two devices is still required. GSS-API also requires that each party have auth credentials before the communication occurs, which isn’t a requirement for our use case. ## Secure Credential Transfer with GSS-API Because GSS-API does not define the communication channel we will assume the devices are able to communicate via an arbitrary intermediary server. An example transfer using GSS-API + Tigress could like like:

1. Sender creates a single use auth credential and encrypts it with a symmetric key that will be a shared secret.
   1. Tigress: The creation, structure, and validation of this single use auth credential would need to be defined by Tigress.
2. Sender creates a GSS-API security context token with the encrypted credential.
3. Sender sends security context token + shared secret to receiver.
   1. If a mailbox style intermediate server is used this can be done via a url where the shared secret is include in the url fragment.
   2. Tigress: How this information is sent to the intermediary server would need to be defined by tigress.
4. Receiver gets information for communicating with the sender and the shared secret.
   1. This information could be transferred via a url, a file, a QR code, etc.
   2. Tigress: The high level format of this information would need to be defined by tigress so that devices could parse the data and extract the GSS-API specific parts.
   3. Tigress: We could recommend that this information have a nice preview, but that wouldn't be required.
5. Receiver accepts the security context token, and uses the shared secret to validate the credential.
6. Receiver sends back security context token to sender. This process is repeated until the security context is full established.
   1. Tigress: How the receiver sends the opaque blob to the sender via the intermediary server would need to be defined by tigress.
7. Sender creates credential to share, use GSS-API to create a message token, send message token to receiver.
8. Receiver gets message token and uses GSS-API to extract the underlying credential.
   1. If the receiver is done they can terminate the transfer and send a GSS-API termination back to the sender.
      1. Tigress: How the session with the intermediary server between the sender and receiver is terminated would need to be defined by tigress.
   2. Or, the receiver can perform additional calls with the sender to complete transferring the credential.

Security Considerations TODO Security

IANA Considerations This document has no IANA actions.

References Normative References This memo obsoletes [STANDARDS-TRACK] In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References

Acknowledgments TODO acknowledge.