Could we register the existing codepoints in the draft as provisional?
I think the current draft has these code points:
address_discovery transport parameter: 0x9f81a176 (16 bits)OBSERVED_ADDRESS frame: 0x9f81a6..0x9f81a7 (12 bits)
From https://www.rfc-editor.org/rfc/rfc9000.html#name-selecting-codepoints
For codepoints that are encoded in variable-length integers (Section 16), such as frame types, codepoints that encode to four or eight bytes (that is, values 214 and above) SHOULD be used unless the usage is especially sensitive to having a longer encoding.
So I'm not sure if you can argue that OBSERVED_ADDRESS is "especially sensitive". It's not like this is a frame that gets sent a lot in a connection. Perhaps that should also have been chosen in the 16 bit range?
Otherwise I think all the requirements for provisional registration are met.
Could we register the existing codepoints in the draft as provisional?
I think the current draft has these code points:
address_discoverytransport parameter: 0x9f81a176 (16 bits)OBSERVED_ADDRESSframe: 0x9f81a6..0x9f81a7 (12 bits)From https://www.rfc-editor.org/rfc/rfc9000.html#name-selecting-codepoints
So I'm not sure if you can argue that OBSERVED_ADDRESS is "especially sensitive". It's not like this is a frame that gets sent a lot in a connection. Perhaps that should also have been chosen in the 16 bit range?
Otherwise I think all the requirements for provisional registration are met.