draft-ietf-lisp-gpe-02.txt   draft-ietf-lisp-gpe-03.txt 
Internet Engineering Task Force F. Maino, Ed. Internet Engineering Task Force F. Maino, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track J. Lemon Intended status: Standards Track J. Lemon
Expires: October 1, 2018 Broadcom Expires: October 7, 2018 Broadcom
P. Agarwal P. Agarwal
Innovium Innovium
D. Lewis D. Lewis
M. Smith M. Smith
Cisco Cisco
March 30, 2018 April 5, 2018
LISP Generic Protocol Extension LISP Generic Protocol Extension
draft-ietf-lisp-gpe-02 draft-ietf-lisp-gpe-03
Abstract Abstract
This document describes extending the Locator/ID Separation Protocol This document describes extending the Locator/ID Separation Protocol
(LISP) Data-Plane, via changes to the LISP header, to support multi- (LISP) Data-Plane, via changes to the LISP header, to support multi-
protocol encapsulation. protocol encapsulation.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 1, 2018. This Internet-Draft will expire on October 7, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 45 skipping to change at page 5, line 45
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFI = x | Address ... | | AFI = x | Address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multiple Data-Planes LCAF Type Multiple Data-Planes LCAF Type
g Bit: The RLOCs listed in the AFI-encoded addresses in the next g Bit: The RLOCs listed in the AFI-encoded addresses in the next
longword can accept LISP-GPE (Generic Protocol Extension) longword can accept LISP-GPE (Generic Protocol Extension)
encapsulation using destination UDP port 4341 encapsulation using destination UDP port 4341
All other fields As defined in [RFC8060] All other fields: As defined in [RFC8060]
4.2. Type of Service 4.2. Type of Service
When a LISP-GPE router performs Ethernet encapsulation, the inner When a LISP-GPE router performs Ethernet encapsulation, the inner
802.1Q [IEEE8021Q] priority code point (PCP) field MAY be mapped from 802.1Q [IEEE8021Q] priority code point (PCP) field MAY be mapped from
the encapsulated frame to the Type of Service field in the outer IPv4 the encapsulated frame to the Type of Service field in the outer IPv4
header, or in the case of IPv6 the 'Traffic Class' field header, or in the case of IPv6 the 'Traffic Class' field
4.3. VLAN Identifier (VID) 4.3. VLAN Identifier (VID)
When a LISP-GPE router performs Ethernet encapsulation, the inner When a LISP-GPE router performs Ethernet encapsulation, the inner
header 802.1Q [IEEE8021Q] VLAN Identifier (VID) MAY be mapped to, or header 802.1Q [IEEE8021Q] VLAN Identifier (VID) MAY be mapped to, or
used to determine the LISP Instance ID field. used to determine the LISP Instance ID field.
5. IANA Considerations 5. IANA Considerations
IANA is requested to set up a registry of LISP-GPE "Next Protocol". IANA is requested to set up a registry of LISP-GPE "Next Protocol".
These are 8-bit values. Next Protocol values in the table below are These are 8-bit values. Next Protocol values in the table below are
defined in this document. New values are assigned via Standards defined in this document. New values are assigned via Standards
Action [RFC5226]. Action [RFC5226]. The protocols that are being assigned values do
not themselves need to be IETF standards track protocols.
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| Next Protocol | Description | Reference | | Next Protocol | Description | Reference |
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| 0 | Reserved | This Document | | 0 | Reserved | This Document |
| 1 | IPv4 | This Document | | 1 | IPv4 | This Document |
| 2 | IPv6 | This Document | | 2 | IPv6 | This Document |
| 3 | Ethernet | This Document | | 3 | Ethernet | This Document |
| 4 | NSH | This Document | | 4 | NSH | This Document |
| 5..255 | Unassigned | | | 5..255 | Unassigned | |
skipping to change at page 7, line 28 skipping to change at page 7, line 29
o Larry Kreeger o Larry Kreeger
o John Lemon, Broadcom o John Lemon, Broadcom
o Puneet Agarwal, Innovium o Puneet Agarwal, Innovium
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-lisp-rfc6830bis]
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
Cabellos-Aparicio, "The Locator/ID Separation Protocol
(LISP)", draft-ietf-lisp-rfc6830bis-12 (work in progress),
March 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID [RFC6834] Iannone, L., Saucez, D., and O. Bonaventure, "Locator/ID
Separation Protocol (LISP) Map-Versioning", RFC 6834, Separation Protocol (LISP) Map-Versioning", RFC 6834,
DOI 10.17487/RFC6834, January 2013, <https://www.rfc- DOI 10.17487/RFC6834, January 2013, <https://www.rfc-
editor.org/info/rfc6834>. editor.org/info/rfc6834>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-lisp-rfc6830bis]
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
Cabellos-Aparicio, "The Locator/ID Separation Protocol
(LISP)", draft-ietf-lisp-rfc6830bis-12 (work in progress),
March 2018.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, <https://www.rfc- DOI 10.17487/RFC5226, May 2008, <https://www.rfc-
editor.org/info/rfc5226>. editor.org/info/rfc5226>.
[RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger,
L., Sridhar, T., Bursell, M., and C. Wright, "Virtual L., Sridhar, T., Bursell, M., and C. Wright, "Virtual
eXtensible Local Area Network (VXLAN): A Framework for eXtensible Local Area Network (VXLAN): A Framework for
Overlaying Virtualized Layer 2 Networks over Layer 3 Overlaying Virtualized Layer 2 Networks over Layer 3
Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014,
skipping to change at page 8, line 37 skipping to change at page 8, line 37
Fabio Maino (editor) Fabio Maino (editor)
Cisco Systems Cisco Systems
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: fmaino@cisco.com Email: fmaino@cisco.com
John Lemon John Lemon
Broadcom Broadcom
3151 Zanker Road 270 Innovation Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: john.lemon@broadcom.com Email: john.lemon@broadcom.com
Puneet Agarwal Puneet Agarwal
Innovium Innovium
USA USA
Email: puneet@acm.org Email: puneet@acm.org
 End of changes. 9 change blocks. 
13 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/