Paul Kyzivat wrote:
> If you are involved in SIP, or almost any IETF protocol, then I strongly
> suggest that you *learn* to read ABNF. RFC 5234 should tell you all you
> need to know.
No argument. It's just one of the innumerable things I haven't gotten
around to. :-)
--
Alex Balashov - P
tors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
> Sent: Friday, September 04, 2009 2:05 PM
> To: Alex Balashov
> Cc: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Carets encasing URIs.
>
>
>
> Alex Balashov wrote:
> > I cannot easily tell from 326
Alex Balashov wrote:
> I cannot easily tell from 3261 whether references to URIs other than the
> Request URI must be encased in "<" and ">" or not, probably because I do
> not know how to read BNF.
If you are involved in SIP, or almost any IETF protocol, then I strongly
suggest that you *lea
Of
Alex Balashov
Sent: Friday, September 04, 2009 11:08 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Carets encasing URIs.
I cannot easily tell from 3261 whether references to URIs other than the
Request URI must be encased in "<" and ">" or
I cannot easily tell from 3261 whether references to URIs other than the
Request URI must be encased in "<" and ">" or not, probably because I do
not know how to read BNF.
In other words, in the absence of a display name (which would be a
quoted string), is this valid?
Contact: sip:xx.xxx.
