Dear Authors, et al.,
I have a rather benign question the new registry requested in Section 8.3.
The draft states that the whole 1-127 range is "RFC required" per RFC 5226.
Firstly, a nit - RFC 5226 has been obsoleted by RFC 8126. My question is
Would you agree to split the 128-255 range and set First Come First Served
<https://tools.ietf.org/html/rfc8126#section-4.4> sub-range. For example:
+----------------+------------------+---------------+
| Control type | Description | Reference |
+----------------+------------------+---------------+
| 0 | Control payload | This document |
| | needs more | |
| | context for | |
| | interpretation | |
| | | |
| 1..127 | Unassigned | |
| | | |
| 128..250 | First Come | RFC 8126 |
| | First Served | |
| 251..254 | Experimental | This document |
| | | |
| 255 | Reserved | This document |
| | | |
+----------------+------------------+---------------+
Also, you may consider updating 0 as Reserved and assigning 1 as Control
payload ...
Much appreciate your consideration.
Regards,
Greg
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
