> No attempt is made in the document to explain how/why the reduction in size of
> some standard LISP header fields is acceptable. For example, if
> implementations
> of this spec can safely operate with a 16 bit Nonce or 8 bit Map-Versions, why
> does 6830/6830bis feel the need for 24 and 12 bit fields rspectively?
Note, you misread RFC6830. The Map-Version field is 24-bits when the V bit is
set. And is divided up like this:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|N|L|E|V|I|flags| Source Map-Version | Dest Map-Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Instance ID/Locator-Status-Bits |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Dino
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
