Hi,
Please bear with this long mail.
Thumb rule for the my Parser is
It has to support the headers defined in the RFC2543.
For other headers, it should just ignore.
To find the header in the SIP message, I am referring
section 6.6 Header file format. In this section it is
described as follows;
message-header = field-name ":" [ field-value ] CRLF
field-name = token
field-value = *( field-content | LWS )
LWS = [CRLF] 1*( SP | HT )
The field value MAY be preceded by any amount of
leading white space (LWS), though a single space (SP)
is preferred. Header fields can be extended over
multiple lines by preceding each extra line with at
least one SP or horizontal tab (HT).
So, I am assuming that if the field value is wrapped
to the second line, it will start with SP or HT AND
all the headers will start in the same column. The
delimiter for different headers is just CRLF. If it
finds CRLF and <HT/ SP>, I am assuming that it is wrap
up of the previous header. For eg., my SIP message
may look like this,
>From : "J Rosenberg \\\"" <sip:[EMAIL PROTECTED]>
;
tag = 98asjd8
Call-ID
: [EMAIL PROTECTED]
cseq: 8
INVITE
Via : SIP / 2.0
/UDP
135.180.130.133
If my assumption is right, how can any Parser pass 7.1
INVITE Parser Torture Test Message in
draft-ietf-sip-call-flows-05.txt. Because in this
message, even the field value of a header (m:"Quoted
string \"\"" <��..) starts with the same column as the
field name starts.
If my assumption is wrong, what is the delimiter to be
used to distinguish two different headers?
Thanks,
Sathya
____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
