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?
This restriction is to simplify implementations.