Greetings,
During our SIP inter-operation testing, we discovered a problem with
INVITEs being rejected due to white space in the SDP attribute filed. I
have gone through the mail archives in an attempt to address my concern
but cannot locate a definitive answer.
I realize, and have seen mailings to same, that SIP (RFC 3261) is quite
free in allowing white spaces to appear in headers on either side of a
colon (e.g., "Subject : lunch"). I have also seen mailings
related to LWS.
My specific concern is with SDP (RFC 2327) coding of the fields
containing a colon and white spaces around same. Section 6, paragraph 2,
makes a point of clearly stating that "Whitespace is not permitted
either side of the `=' sign." No such statement is made concerning a
colon appearing later in the field. For example,
b=<modifier>:<bandwidth-value>
k=<method>:<encryption key>
a=<attribute>:<value>
While the RFC shows the format of these fields, it does not declare
rules regarding white spaces. In addition, the RFC states that any
attribute not understood should be ignored, so I believe that clearing
the session is inappropriate either way; the observed behavior of a
terminal adaptor.
We need to resolve the question in order to address where changes should
be made. We appreciate any feedback to clarify how to handle this issue.
Sincerely,
Glenn Gobeli
Sr. Design Engineer
Nortel
[EMAIL PROTECTED]
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
