> 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.
Well, you can perhaps be even stricter than that. All headers
will start in "column" 0.
> 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.
Indeed.
> 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.
<snippet>
m:"Quoted string \"\"" <sip:[EMAIL PROTECTED]> ; newparam =
newvalue ;
secondparam = secondvalue ; q = 0.33
</snippet>
Yes, I'm guessing that it's an unfortunate case of wrapping
in the production of the draft. I suspect that the
"newvalue ;" should be appended to the line above.
- Jo.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
