[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Sip] ABNF issue




> -----Original Message-----
> From: ext Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Wednesday, December 11, 2002 2:42 PM
> To: Rob Phillips
> Cc: Khartabil Hisham (NMP/Helsinki); rsparks@dynamicsoft.com;
> jdrosen@dynamicsoft.com; sip@ietf.org
> Subject: Re: [Sip] ABNF issue

> 
> 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).  

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.

Regards,
Hisham

> 
_______________________________________________
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