RFC 4992, "XML Pipelining with Chunks for the Internet Registry Information Service", August 2007Source of RFC: crisp (app)
Errata ID: 2832
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-09-09
Held for Document Update by: Peter Saint-Andre
Date Held: 2011-06-11
Section 6.5 says:
o mechanism data length - the length of the SASL data.
It should say:
o mechanism data length - the length of the SASL data, or the special value 65535 (to indicate the absence of an initial SASL response -- see below).
The final paragraph of Section 6.5 (i.e., the 2nd paragraph
on page 12) says:
When used as an initial challenge response for SASL mechanisms that
support such a feature, the mechanism data length may be set to a
decimal value of 65,535 to indicate an absent initial response. A
value of 0 indicates an empty initial response.
Apparently, the need to subtly distinguish an absent initial response
from an empty initial response is the only justification left for the
existence of the 'mechanism data length' field.
But this information could be conveyed in a single flag bit.
[Separating into individual errata from 1009]