Re: [Sip] ABNF issue

[Christer Holmberg <christer.holmberg@lmf.ericsson.se>]

Hi,

> >In this case, I think it is important to note that a SIP header MUST start at the BEGINNING of a new line.
>
> Header fields can be extended over multiple lines by preceding each extra line with at least one SP or horizontal tab (HT).

That's line folding, which is a separate issue. What I said was that the START of the header MUST be at the BEGINNING of a new
line, no matter if the rest of the header is then folded/extended over multiple lines.

> Also, in RFC2822:
>
> "Messages are divided into lines of characters.  A line is a series of
>    characters that is delimited with the two characters carriage-return
>    and line-feed; that is, the carriage return (CR) character (ASCII
>    value 13) followed immediately by the line feed (LF) character (ASCII
>    value 10).  (The carriage-return/line-feed pair is usually written in
>    this document as "CRLF".)
>
> A message consists of header fields (collectively called "the header
>    of the message") followed, optionally, by a body.
>
> ...
>
> Header fields are lines composed of a field name, followed by a colon
>    (":"), followed by a field body, and terminated by CRLF.  A field
>    name MUST be composed of printable US-ASCII characters (i.e.,
>    characters that have values between 33 and 126, inclusive), except
>    colon.  "
>
> No header name is allowed a CR or LF in it,and certainly no sip header has CRLF included in its name.

I never said that the CRLF is part of the header name. My question was if the header name token could be proceeded by LWS, or
the header name token always be at the beginning of a new line.

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip