Hi Paul,
Even then, ideally there should have been some words to indicate that
the <field-name>s used as extensions for trace be disjoint from those
used as non-trace extension headers.
It gets more ugly when we start to extends <optional-field>
syntactically via =/. Now, when the syntax is evaluated the new header
fields we are defining show up as explicitly syntactically valid in both
places. :-(
In the erratum for RFC 5536, a sentence may be added to say that news
header fields defined by this document are not trace header fields, in
the terminology of RFC 5322.
--
Julien ÉLIE
« You know it's love when all you want is that person to be happy;
even if you're not part of their happiness. »
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
