Dino, > > Dino, > > > >>> So active/active I think should be in the charter. > >>> External tromboning if included would be a pull towards LISP and would be > >>> nice to have just one encap for both purposes. > >> > >> Just an FYI that LISP and VxLAN use the same encapsulation headers. An 8 b yte > >> UDP header followed by a 8 byte LISP header. What is the inner versus the > >> outer outer headers depends on the address type for your EID or RLOC > >> respectively. > > > > Here is the LISP header: > > > > > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > L |N|L|E|V|I|flags| Nonce/Map-Version | > > I \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > S / | Instance ID/Locator Status Bits | > > P +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > Here is the VxLAN header: > > > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > |R|R|R|R|I|R|R|R| Reserved | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | VXLAN Network Identifier (VNI) | Reserved | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > So, if one measure similarity by the size of the header, then indeed > > both LISP and VxLAN use "the same encapsulation header" - both are > > 8 bytes long. > > When the I-bit is set in the LISP header, then the format is: > > x x x x 1 x x x > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |N|L|E|V|I|flags| Nonce/Map-Version | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Instance ID | LSBs | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > VxLAN's header is a subset functionality of the LISP header and > always sets the I-bit.
Functionality of a used car is a subset functionality of a new car. Yet according to your logic the two are the same... > > However, if we look inside these 8 bytes, we find that the two > > encapsulation headers are quite different. > > > > So, your statement that "LISP and VxLAN use the same encapsulation > > headers" is incorrect. > > Not true Yakov. I guess your definition of "the same" is different from mine. Yakov. _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
