Hi, draft-ietf-sip-gruu-15 contains (amongst others) these ABNF rules:
| contact-params =/ temp-gruu / pub-gruu | temp-gruu = "temp-gruu" EQUAL LDQUOT *(qdtext / quoted-pair ) | RDQUOT | pub-gruu = "pub-gruu" EQUAL LDQUOT *(qdtext / quoted-pair ) | RDQUOT which, when adding them to the grammar from RFC 3261, would produce from <Contact> a language that's a superset of the language that would be produced by <Contact> from RFC 3261-only. In particular, the language produced by <foo> is a subset of the "GRUU extended" language, but not of the RFC 3261-only one: | foo = "m: <sip:[email protected]>;temp-gruu=" DQUOTE "x" DQUOTE SP CRLF To put it in more practical terms: the <RDQUOT> in both <temp-gruu> and <pub-gruu> allow for trailing <LWS>, which <contact-extension> does not, so an implementation conforming to draft-ietf-sip-gruu-15 could produce a Contact header that potentially could not be parsable (except as an <extension-header>) by an implementation conforming to RFC 3261. Thus, I would suggest to replace the rules quoted above by: | contact-params =/ temp-gruu / pub-gruu | temp-gruu = "temp-gruu" EQUAL LDQUOT *(qdtext / quoted-pair ) | DQUOTE | pub-gruu = "pub-gruu" EQUAL LDQUOT *(qdtext / quoted-pair ) | DQUOTE This produces the same language, maybe it's a better replacement: | contact-params =/ temp-gruu / pub-gruu | temp-gruu = "temp-gruu" EQUAL quoted-string | pub-gruu = "pub-gruu" EQUAL quoted-string Florian _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip
