Hi Daniel,
Suresh,
Hal may not have been clear. The four extension fields we're discussing are the four defined by the NTS draft. Due to the registry's unfortunate lack of any P&E range, Hal and other implementers have picked four codes that they've been squatting on for their
draft implementations. Desiring to avoid a flag day when the draft becomes final, they'd like IANA to turn these four codes into official allocations rather than having IANA arbitrarily assign something else. Speaking as an author of the draft I have no objection
to this.
Ah. Thanks for clarifying. That makes sense. I don’t have any issues with this either. As Ben Kaduk said downthread, you can stuff in the currently used values as “requested values” into the draft after the last call completes. I will work with IANA to get
these values assigned (I don’t foresee an issue)
Regards
Suresh
|
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
