RFC Errata
RFC 5688, "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes", January 2010
Source of RFC: IETF - NON WORKING GROUPArea Assignment: rai
Errata ID: 1999
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2010-01-10
Held for Document Update by: Robert Sparks
Section 3, 1st para says:
The 'sip.app-subtype' media feature tag is of type token with a case- insensitive equality relationship. Its value can be any registered | or private MIME application subtype compliant to the subtype-name grammar defined in [RFC4288]. When included in the Contact header field of a REGISTER request, an agent SHOULD include all application subtypes that it can support as streaming formats. An application | subtype is supported if the user agent would be capable of processing a Session Description Protocol (SDP) [RFC4566] offer [RFC3264] that contained that subtype as a format in the m-line of the SDP.
It should say:
The 'sip.app-subtype' media feature tag is of type token with a case- insensitive equality relationship. Its value can be any registered | or private 'application' media subtype compliant to the subtype-name grammar defined in [RFC4288]. When included in the Contact header field of a REGISTER request, an agent SHOULD include all application subtypes that it can support as streaming formats. An application | subtype is supported if the user agent would be capable of accepting a Session Description Protocol (SDP) [RFC4566] offer [RFC3264] that contained that subtype as a format in the m-line of the SDP.
Notes:
Rationale:
For clarity, the whole paragraph is shown here, including both changes.
a) editorial; see GLOBAL Errata note, EID=1997.
b) technical: the ability of "processing" an SDP offer does not
mean the ability to _accept_ it. The latter reasonably seems
to be synonymous to "supporting" the feature contained therein,
but the former isn't. Therefore, s/processing/accepting/ .