Note that the ABNF in 3261 is quite explicit about whitespace. "SP"
isn't used very much. In most places, where multiple spaces make sense,
WSP, or LWS is used. So you should be able to assume that where SP is
used that is what is meant. It is certainly saying that to be conformant
you should use exactly one space when constructing the request line.
When parsing one you may still choose to be more tolerant.
Paul
Rayees Khan wrote:
> By definition in RFC 3261 there should be a single space. However, most
> of the SIP elements do accept more than one spaces for SP
>
> regards
> Rayees
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Zeev
> Kamelmacher
> Sent: Monday, May 14, 2007 3:32 PM
> To: sip-implementors
> Subject: [Sip-implementors] Syntax validation according to SIP BNF
>
> Hi all,
>
> I'm trying to implement a validation of the sip syntax. I need some
> clarifications concerning the SIP BNF (rfc 3261):
>
> 1. In case of parsing the request-line (Request-Line = Method
> SP Request-URI SP SIP-Version CRLF)
> does the SP have to be a single space or there maybe more than
> single space, and still the message would be legal ?
>
>
>
>
> Thanks in advance
>
> Zeev.K 4804
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
>
>
>
> ----------------------------------------------------------------------------------
> IMPORTANT The information contained in this e-mail any
> attachments is intended only for the named recipient and may be
> privileged or confidential.
>
> If you are not the intended recipient, please notify us immediately
> on +44 (0)1908 425000 and do not disclose, copy, distribute
> or take any action based on the contents of this e-mail.
>
> You should understand and accept that, when communicating with us
> by e-mail, it is not a totally secure communication medium.
>
> We accept no liability for any direct, indirect or consequential loss
> arising from any action taken in reliance on the information contained
> in this e-mail and give no warranty or representation as to its accuracy
> or reliability.
>
> DIGITALK has the facility to monitor and read both incoming
> and outgoing communications by e-mail. In line with industry efforts
> to reduce the proliferation of Un-Solicited SPAM messages,
> DIGITALK uses various methods including Reverse-DNS
> lookups and ban-lists to prevent malicious content reaching our users.
>
> This message and any attachments has been scanned for known
> viruses. However, we would advise you to ensure the content is
> indeed virus free. We do not, to the extent permitted by law, accept
> any liability (whether in contract, negligence or otherwise) for any virus
> infection and/or external compromise of security and/or breach of
> confidentiality in relation to transmissions sent by e-mail.
>
> VAT No: GB 876 3287 81. Reg No: 3080801
> Place of Registration: England
> Registered Office Address: 2 Radian Court, Knowlhill, Milton Keynes
> ----------------------------------------------------------------------------------"
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
