1 / 5

LISP Generic Protocol Extension (LISP- GPE)

LISP Generic Protocol Extension (LISP- GPE). d raft- lewis -lisp- gpe P. Quinn , D. Lewis, L. Kreeger , F. Maino , CISCO M . Smith, N. Yadav , INSIEME NETWORKS IETF 88, Vancouver, BC, Canada. Why LISP- GPE.

mckenzie-norton
Download Presentation

LISP Generic Protocol Extension (LISP- GPE)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LISP Generic Protocol Extension (LISP-GPE) draft-lewis-lisp-gpe P. Quinn, D. Lewis, L. Kreeger, F. Maino, CISCO M. Smith, N. Yadav, INSIEME NETWORKS IETF 88, Vancouver, BC, Canada

  2. Why LISP-GPE • RFC6830 relies on the inspection of the first byte of the inner header to indicate the inner header’s IP version • Use cases for both DC host mobility and L2 VPNs require encapsulation of Ethernet • Desire of the authors to promote experimentation with LISP in these use cases

  3. LISP-GPE • Define lower 16 bits in first word of LISPheader as protocol type • Define Protocol bit (P bit) • P=0: payload MUST conform to RFC6830 as currently defined (i.e. IP[4,6]) • P=1: Indicates presence of protocol type field • When P bit is set, N, E and V bits must be Zero +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |N|L|E|V|I|P|R|R| Reserved |Nonce/Map Version/Protocol Type| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Instance ID / Locator-Status-Bits | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  4. Trade Offs • The P bit comes at the expense of two features: Nonce, Map Versioning and Echo-Nonceing

  5. Summary • Enables operators/experimenters to use LISP for all protocols • Compatible with draft-quinn-vxlan-gpesee presentation at NVO3WG • Working with authors of draft-yong-l3vpn-nvgre-vxlan-encap to align on common format

More Related