Re: [Ntp] New Version Notification for draft-rsalz-update-registries-00.txt

["Salz, Rich" <[e-mail]>]

     >   I liked the Daniel's idea to keep them both, the original values
        unchanged and then mark the swapped set as reserved, occupied, or
        similar.

>    If we're listing them as reserved, we should put them in the RFC.  I'll do that today or tomorrow.

New commit pushed to the repo, https://github.com/richsalz/draft-rsalz-update-registries/commit/2eecd8c308ade0a9f8dce6231f3cc8fcbc5e06bc

    >    I'm ok with the the proposed range 0xD000-0xFFFF for experimenal
        extension fields, but others here probably will not like it as it will
        randomly set the "response" and "error" flags in their interpretation
        of the value.

So the registry contains more than just the extension field type, it contains the length and those flag bits.  The following diff tries to capture that, is it correct?

And also where are the response and error flags defined?  A quick search in RFC 5905 didn't find anything obvious.
diff --git a/draft-rsalz-update-registries.md b/draft-rsalz-update-registries.md
index 7d62fdd..575d101 100644
--- a/draft-rsalz-update-registries.md
+++ b/draft-rsalz-update-registries.md
@@ -86,8 +86,12 @@ around the interaction with the Message Authentication Code (MAC) field.
 The following problems exists with the current registry:
 
 - Many of the entries in the Extension Field Types registry have
-swapped nibbles (half of a byte).
+swapped some of the bytes; 1234 is listed as 1432 for example.
 This document marks the erroneous values as reserved.
+- The field type registry includes the Field Type, as defined in Figure
+14 of {{!RFC5905}}, but also the length. This is arguably an error, but
+one we will preserve as existing software might depend on the length values
+being fixed.
 - Some values were mistakenly re-used.
 
 ## Network Time Security Registries
@@ -174,7 +178,7 @@ possible, replace the existing 5905 with 5906.
 
 The following Note is added:
 
-- Field Types in the range 0xD000 throught 0xFFFF, inclusive, are reserved
+- Field Types in the range 0xD000 through 0xFF00, inclusive, are reserved
 for experimentation and development. IANA cannot assign them.
 Both NTS Cookie and Autokey Message Request have the same Field Type;
 in practice this is not a problem as the field semantics will be
@@ -182,7 +186,8 @@ determined by other parts of the message.
 
 The columns are defined as follows:
 
-- Field Type (required): A two-byte value in hexadecimal.
+- Field Type (required): A four-byte value in hexadecimal, that includes
+the type as the top two bytes and the length as the bottom two.
 
 - Meaning (required): A brief text description of the field type.