> > > Sorry for not being clear and thanks for your time. I
> want to know the
> > > meaning of *token. Appendix defines what is token, which itself
> > > containts multiple characters since it is 1*(.......).So, how does
> > > *token make sense?
> > >
> > > If *token is correct, what would be the separator between two
> > > consequetive tokens? If there is no separator, what is the
> > > use of *token
> > > because the definition of the token would suffice.
> > >
> >
> > 1* of the token definition means there is
> > at least one.
> >
> > The display-name definition *token basically
> > just cancels the "at least one" part of the
> > token definition.
>
>
> Isn't it so that *token is 0 or more tokens separated with
> LWS. This would
> make Foo Bar a legal display-name.
The definition of the *rule does not indicate
that the elements are separated by LWS.
Foo Bar is not a legal display-name per definition.
However most implementations allow it solely because
the examples have incorrectly reflected its use
since the original rfc.
"Foo Bar" is legal through the quoted string
definition portion of display-name. And the
quotes should be removed prior to actually
displaying the name. I mention this mainly
because I've noticed some implementations
forgetting to do so.
> Token is 1*(alphanum|"-"|"."|"!"|"%"|"*"|"_"|"+"|"`"|"'"|"~")
> which does not
> include LWS. So if display-name would be defined as 1*token,
> Foo Bar would
> be an illegal display-name.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
