Hi Brett, Thanks a lot for your immediate response.
Unfortunately, I did not get your explanation clearly
"Based upon what you supplied, you need to implement RFC 5502 errata
4648concerning when Name-Addr must be used.......If you implement the errata,
the brackets will allow the header to be decodedas you actually desired."
What is the errata? What type of brackets need to be used for this case? Even
After going through RFC 4648, I have not understood what change I require to
perform in my example to get it parsed correctly in remote node !!!!
Can you please explain in more detailed way?
Also I have referred the Draft-sparks-sipcore-name-addr-guidance . There I
can see
Network Working Group R. Sparks
Internet-Draft Oracle
Updates: 3261, 3515, 5002, 5318, 5360, June 07, 2016
5502 (if approved)Intended status: Standards Track
Expires: December 9, 2016
Clarifications for when to use the name-addr production in SIP messages
draft-sparks-sipcore-name-addr-guidance-00
=================
3. Updates to RFCs defining SIP Extension header fields
[RFC3515], [RFC5002], [RFC5318], [RFC5360], and [RFC5502] are updated to
include: This RFC contains the definition of one or more SIP header fields that
allow choosing between addr-spec and name-addr when constructing header field
values. As specified in RFCxxxx, the "addr-spec" form MUST NOT be used if its
value would contain a comma, semicolon, or question mark.
So is it already a standard? Or it will be accepted only after approval?
Please excuse me for my ignorance.
Thanks in advance for your comments.
Regards,Sourav
On Wednesday, 29 June 2016 6:56 PM, Brett Tate <br...@broadsoft.com> wrote:
> So my understanding from above grammar that the header value
> [sip:+ACE34610520436;cic=+7...@tqf01.test.abc;sescase=term;regstate=unreg]
> has not violated the ABNF.. Can you please confirm if my
> understanding is correct ?
Based upon what you supplied, you need to implement RFC 5502 errata 4648
concerning when Name-Addr must be used. The ABNF violation is caused by cic
being decoded as header parameter (i.e. violates generic-param rule). If
you implement the errata, the brackets will allow the header to be decoded
as you actually desired.
Draft-sparks-sipcore-name-addr-guidance has been created to address the
issue with RFC 5502 and other RFCs.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
