El Martes, 10 de Febrero de 2009, Theo Zourzouvillys escribió:
> On Tue, Feb 10, 2009 at 8:07 PM, Iñaki Baz Castillo <[email protected]> wrote:
> > Well, the first example is invalid since according to BNF grammar:
> >
> > display-name = *(token LWS)/ quoted-string
> >
> > This is: the display name (The Operator) is incorrect since it's not a
> > token (it contains a space) and it's not a quoted-string.
> >
> > Perhaps I miss something?
>
> Yes, you are missing something. I suggest you go and read RFC 2234
> well, so that you understand what:
>
> display-name = *(token LWS) / quoted-string
>
> means, as (The Operator) matches that rule just fine.
Yes, anyway there is a bug there, and it's explained in RFC 4475:
3.1.1.6. Message with No LWS between Display Name and <
This OPTIONS request is not valid per the grammar in RFC 3261 since
there is no LWS between the token in the display name and < in the
From header field value. This has been identified as a specification
bug that will be removed when RFC 3261 is revised. Elements should
accept this request as well formed.
From: caller<sip:[email protected]>;tag=323
The correct grammar would be:
display-name = [ token *( LWS token ) ] / quoted-string
Best regards.
--
Iñaki Baz Castillo
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
