Re: [Sip] ABNF issue

[Christer Holmberg <christer.holmberg@lmf.ericsson.se>]

Hi,

> You specific question has been answered twice already, and I will
> answer it a third time.  If you still do not understand, please email
> one of the chairs privately and we will arrange for someone to explain
> it to you.
>
> On Wednesday, December 11, 2002, at 06:21 AM, Christer Holmberg wrote:
> > I never said that the CRLF is part of the header name. My question was
> > if the header name token could be proceeded by LWS, or
> > the header name token always be at the beginning of a new line.
>
> as rob@netrake said:
> >       RFC-3261 does not specifically ALLOW the name token to be proceeded
> > by LWS, i.e. the definition of message-header per ABNF is:
> >
> >       message-header = (Accept / .... / extension-header) CRLF
> >
> > Therefore, the header name token MUST always be at the beginning of a
> > new line.
>
> and as robert sparks said:
> > The grammar answers that.
> > extension-header starts with a token.
>
> in other words, a SIP header ALWAYS starts with a token (all of the
> existing headers are tokens), which can NEVER contain leading
> whitespace.

And I don't know how many times I've said this: I've NEVER claimed that a
header would start with anything else than a token. What I've been talking
about are general ABNF rules.

Anway, I have had a private discussion with Brian about this, so there is no
idea to continue it here. Rob also presented some assumptions we make in SIP,
and if everybody agrees on those I am happy.

Regards,

Christer Holmberg
Ericsson Finland


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip