Re: Sequence of attributes in a SCRAM message

[Dave Cridland <dave@xxxxxxxxxxxx>]

On Mon Jun 15 19:47:32 2009, Nicolas Williams wrote:
> On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
> > Hi,
> > From Section 5.1 of the latest draft:
> >
> > > Note that the order of attributes in client or server messages  
> is
> > >    fixed, with the exception of extension attributes (described  
> by the
> > >    "extensions" ABNF production), which can appear in any order  
> in the
> > >    designated positions.  See the ABNF section for authoritative
> > >    reference.
> > >
> > >
> > Does this mean that during serialization, attribute 'a' goes  
> first, then
> > 'n', 'm', 'r' and so on? If so why the restriction on sequence?
>
> The ABNF itself provides the order.  See the ABNF.

That's not answering the question, though - what is the purpose of  
this rule? (I don't recall it existing before, except that 'r' was at  
the end).

Dave.
--
Dave Cridland - mailto:dave@xxxxxxxxxxxx - xmpp:dwd@xxxxxxxxxxxxxxxxx
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade