Share via

3.3.5 Message Processing Events and Sequencing Rules

  • Article

The SPNEGO Extension client SHOULD invoke Send Fragmented Messages (section 3.1.5.6) when a GSS_Accept_sec_context() ([RFC2743] section 2.2.2) with the FragmentToFit parameter set to TRUE (section 3.1.1) is received, and either:

  • The Negotiate Token ([RFC4178] section 4.2) to be sent exceeds MaxOutputTokenSize, or

  • FragmentOutputToken is set to TRUE.

The server MUST invoke Receive Fragmented Messages (section 3.1.5.9) when a packet is received and either:

  • The packet contains a valid ASN.1 header but an incomplete body, or

  • FragmentOutputToken is set to TRUE.

To support non-compliant implementations of [RFC4178] that send a supportedMech field in a subsequent NegTokenResp message, the SPNEGO Extension client SHOULD<10> accept the message without returning an error, but MUST ignore the new supportedMech field.