OK, thanks for clarification. So, it I need to keep backwards compatibility with RFC2543 then should SPACE b/w ‘sip’ and : to be allowed?
Thanks, Arun On 10/11/15, 4:40 PM, "Brett Tate" <br...@broadsoft.com> wrote: >RFC 3261 does not allow it (RFC 2543 tended to be more vague concerning >where whitespace was valid). If RFC 3261 intended to allow it, it would >have used things like COLON instead of ":" within the ABNF. > >SIP-URI = "sip:" [ userinfo ] hostport > uri-parameters [ headers ] >SIPS-URI = "sips:" [ userinfo ] hostport > uri-parameters [ headers ] > >absoluteURI = scheme ":" ( hier-part / opaque-part ) > >scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." ) > >COLON = SWS ":" SWS ; colon > > > >> -----Original Message----- >> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- >> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Arun Arora >> Sent: Tuesday, November 10, 2015 5:52 AM >> To: sip-implementors@lists.cs.columbia.edu >> Subject: [Sip-implementors] Is it OK to put spaces b/w SIP and COLON in >> SIP >> URI >> >> I am working on a SIP parser while reading RFC3261. I wonder is it OK to >> put >> WHITESPACE between SIP and COLON in a SIP URI, for e.g. >> >> “BOB"<sip :b...@biloxi.com> >> >> Is this syntactically correct. >> >> >> Thanks, >> Arun _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
