> I also realised that errata was reported very recently > by you in March 2016.
Yes; I was slow in opening errata after raising the issue in 2013 within the sipcore working group while we were working on the similar issue with RFC 3325. http://www.ietf.org/mail-archive/web/sipcore/current/msg05731.html > Another question is that whether this correction is > also applicable for constructing Request-URI for > any request. No. The RFC 5502 errata only applies to P-Served-User. And as draft-sparks-sipcore-name-addr-guidance indicates, the RFC 3261 update applies when constructing the value of any SIP header field whose grammar allows choosing between name-addr and addr-spec. "When constructing the value of any SIP header field whose grammar allows choosing between name-addr and addr-spec, such as those that use the form '(name-addr / addr-spec)', the "addr-spec" form MUST NOT be used if its value would contain a comma, semicolon, or question mark." > INVITE sip:+34610510036;cic=+4...@spe01.vodafone.com;user=phone SIP/2.0 > > Is the above example correct? Yes. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
