Hi,
Concerning RFC 3325's P-Asserted-Identity and P-Preferred-Identity, should the
typical bracket rule apply concerning parameters?
Since these headers do not contain parameters, I assume that the following RFC
3261 section 20 snippet does not apply.
Thanks,
Brett
-----
RFC 3261 section 20:
The Contact, From, and To header fields contain a URI. If the URI
contains a comma, question mark or semicolon, the URI MUST be
enclosed in angle brackets (< and >). Any URI parameters are
contained within these brackets. If the URI is not enclosed in angle
brackets, any semicolon-delimited parameters are header-parameters,
not URI parameters.
RFC 3325 section 9.1:
PAssertedID = "P-Asserted-Identity" HCOLON PAssertedID-value
*(COMMA PAssertedID-value)
PAssertedID-value = name-addr / addr-spec
RFC 3325 section 9.2:
PPreferredID = "P-Preferred-Identity" HCOLON PPreferredID-value
*(COMMA PPreferredID-value)
PPreferredID-value = name-addr / addr-spec
This email is intended solely for the person or entity to which it is addressed
and may contain confidential and/or privileged information. If you are not the
intended recipient and have received this email in error, please notify
BroadSoft, Inc. immediately by replying to this message, and destroy all copies
of this message, along with any attachment, prior to reading, distributing or
copying it.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
