>>>>> "Dino" == Dino Farinacci <dino at cisco.com> writes:
>> I do not see why, based on this note, this document should
>> mandate anything about the relationship of the N and L bits to
>> the R bit. Everything works if we say nothing about that
>> relationship.
Dino> Okay, so how about this text:
Dino> R: this is the Research bit. This bit is reserved and
Dino> it's usage is not documented in this specification.
Doesn't work because it fails to specify what you do if you get a
packet with this bit set.
How about: The X bit provides an experimental [RFC 3692] flag for the
LISP header. If a ETR receives a packet with this bit set and has not
been explicitly configured to participate in an experiment, then [pick
from group a]. As described in [RFC 3692], this bit can only be set
when an implementation is configured to participate in an experiment.
Group A:
* drop the packet
* decapsulate and process the inner packet but ignore the LISP header
I don't actually support this option, preferring that if we're going
to have a version field it be at least two bits wide. Howevver I
think it would be reasonable for the WG to decide on a one-bit version
field and if the WG did so, I think the above text is consistent with
how such things are handled in the rest of the IETF.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.