[SIPForum-discussion] A CRLF for multi-line?

[Herve Jourdain]

Hi,

 

1.	I think you can get the information in the RFC 3261, in the
¡°Augmented BNF¡± part (chapter 25, p.219)
A line can be continued on another line if this other line starts with a
¡°space¡± (SP), a ¡°Horizontal Tab¡± (HTAB) or a ¡°Linear White Space¡±
LWS=[*WSP CRLF] 1*WSP
Depending on your parsing strategy and implementation, you could preprocess
the SIP message and replace any LWS you find by a single SP¡­ Or you can add
your parsing rules taking LWS into account.
So to answer to your question, the end character for the first line is CRLF,
SIP considers it¡¯s folded with the NEXT LINE starting with a WSP¡­
In fact, I guess every ¡°line¡± in SIP ends with a CRLF.
2.	As Far As I Know, the ¡°multi-line¡± process is completely
orthogonal with the syntax, so you should just be able to split anywhere in
the SIP message.

 

Regards,

 

Herve

 

 

  _____  

From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of ? ?
Sent: vendredi 21 d¨¦cembre 2007 14:08
To: discussion at sipforum.org
Subject: [SIPForum-discussion] A CRLF for multi-line?

 

Hi, all

Through I have tried my best, there are two things puzzle me:
 
1.If a SIP header field values be folded onto multiple lines.
eg:
          From: Bob <sip:bob at biloxi.com>;tag=a6c8 <CRLF>  
*=>  From: Bob <sip:bob at biloxi.com> <??>
          *<SP>;tag=a6c8 <CRLF>  
    
  Well, the RFC3261 states the extended line should have at least a SP or
TAB as beginner character, but how about the end of the first line , Is
there still a CRLF?                                 

 

2.Is any header field could be split into a multiple line or just some
particular fields can do this ? 

 

As I am doing the SIP parsing now, your answer is very important to me!

 

Regards

 

Nora

 

  

  _____  

 
<http://cn.mail.yahoo.com/gc/index.html?entry=5&souce=mail_mailletter_taglin
e> ÑÅ»¢ÓÊÏä´«µÝÐÂÄê×£¸££¬¸öÐԺؿ¨ËÍÇ×Åó£¡ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/discussion/attachments/20071222/96d7a401/attachment-0007.html