sounds good.
Fabio
On 11/29/17 3:13 PM, Dino Farinacci wrote:
I’d also add before the last sentence:
If the N-bit and V-bit are 0 when the P-bit is set, the middle 16-bits are set
to 0.
Dino
On Nov 29, 2017, at 3:07 PM, Fabio Maino <[email protected]> wrote:
On 11/29/17 3:05 PM, Dino Farinacci wrote:
How about this wording Fabio:
P: The P-bit is the Next Protocol bit. When set, the low-order 8 bits is used
for the Next Protocol field. When the N-bit is also set with the P-bit, the
Nonce field is the middle 16 bits. When the V bit is also set with the P-bit,
the Version field is the middle 16 bits. Details on Next Protocol field usage
are described in [draft-lewis-lisp-gpe].
Comments?
much better.
Thanks,
Fabio
Dino
On Nov 29, 2017, at 2:49 PM, Fabio Maino <[email protected]> wrote:
Definition of the P bit will look like:
P: The P-bit is the Next Protocol bit. When this bit is set to
1, Nonce length, when used, is limited to 16 bits and the lenght
of the Source and Destination Map-Version fields, when used, is limited
to 8 bits. Refer to [draft-lewis-lisp-gpe] for more details.
The P-bit is set to 1 to indicate the presence of the 8 bit Next
Protocol field encoded as:
Do you think the overall proposed extension makes sense?
Thanks,
Fabio
On 11/29/17 2:38 PM, Fabio Maino wrote:
On 11/29/17 2:36 PM, Dino Farinacci wrote:
The use of the P-bit is not compatible with the Map-Versioning feature, but an
equivalent function can be specified (if needed) with a Next-Protocol shim
header. I can add text to the LISP-GPE draft to reflect that.
Well it could be. Just like you did with the Nonce field. Make the Version
field the middle 16-bits. So V and P can be set at the same as well as N and P.
Dino
Good point, shortening versions to 8 bits...
Seems fine to me.
Fabio
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
