Hi Ahmed,
Good point & thanks for raising this.
I guess we have two main avenues forward:
1) low touch, just mention that the ebit draft keeps honoring the
reserved values mentioned in rfc7834 so for those the e-bit / PEN
mechanism will be disabled;
2) slightly more ambitious, while 655535 keeps being a reserved value,
effectively say that the e-bit mechanism does replace the original
experimental mechanism;
The former is a band-aid to address the issue you raised, like i could
have it included in a -02 proposal before the submission deadline
tomorrow (Monday), but it's dirty.
I think we should aim at the latter and, after having seen whether there
is rough agreement around it, it could become the way to go for a -03
(and later) proposals.
Let me know your thoughts.
Paolo
On 3/3/23 23:56, [email protected] wrote:
Hello Paolo, Yunan, all,
In draft-ietf-grow-bmp-tlv-ebit-01 Section 3.3 states that:
While the proposed encoding is not per-
se backward compatible, there is no existing IANA-allocated Type
value that makes use of the most significant bit (which is being used
Future BMP Message Types MUST make use of the TLV encoding defined in
this document.
However, IANA registry already reserves the range 65531-65534 for
experimental use for Information TLVs, Termination TLVs, Route Mirroring
TLVs
What’s going to be the status of these already reserved codes? I
couldn’t tell from the current version of the draft.
Best,
-Ahmed
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
