Carsten Bormann <c...@tzi.org> wrote:
> Doing that gives you all you need to attach to the existing voucher
(e.g., using augment).
No, this does not work in practice, because you can't merge augments.
My slides explaining this are at some 2023 IETF.
I was looking at the RFC8520 extension example in Appendix B, and it uses
augment, and that most certainly does not work the way that they want.
> Having an undefined “here’s some bytes, but we won’t tell you what they
> mean” is probably a bit outside the way YANG people envision their
> ecosystem.
> (Note that there is an SID range for experimental use, if you promise
> to never use these in interchange; megaranges can also allow for
> private allocation.)
No, we are specifically aiming for the opposite :-)
> I’ll need to revise the PEN-Holder draft (by adding a 32-bit space per
> PEN-Holder to the 64-bit space already in there):
That's why I wanted PEN-based spaces too.
A sorta-public mega-range as suggested by Andy would also work for private
modules.
> https://www.ietf.org/archive/id/draft-bormann-core-yang-sid-pen-01.html
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
