Connected: An Internet Encyclopedia
RFC 1510 - 8.2.2. OSI transport

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1510
Up: 8. Constants and other defined values
Up: 8.2. KDC messages
Prev: 8.2.1. IP transport
Next: 8.2.3. Name of the TGS

### 8.2.2. OSI transport

During authentication of an OSI client to and OSI server, the mutual authentication of an OSI server to an OSI client, the transfer of credentials from an OSI client to an OSI server, or during exchange of private or integrity checked messages, Kerberos protocol messages may be treated as opaque objects and the type of the authentication mechanism will be:

       OBJECT IDENTIFIER ::= {iso (1), org(3), dod(5),internet(1),
                              security(5), kerberosv5(2)}

Depending on the situation, the opaque object will be an authentication header (KRB_AP_REQ), an authentication reply (KRB_AP_REP), a safe message (KRB_SAFE), a private message (KRB_PRIV), or a credentials message (KRB_CRED). The opaque data contains an application code as specified in the ASN.1 description for each message. The application code may be used by Kerberos to determine the message type.

Next: 8.2.3. Name of the TGS

Connected: An Internet Encyclopedia
RFC 1510 - 8.2.2. OSI transport