draft-ietf-lisp-gpe-10.txt		draft-ietf-lisp-gpe-11.txt
	skipping to change at page 1, line 15 ¶		skipping to change at page 1, line 15 ¶
	Intended status: Standards Track J. Lemon		Intended status: Standards Track J. Lemon
	Expires: May 7, 2020 Broadcom		Expires: May 7, 2020 Broadcom
	P. Agarwal		P. Agarwal
	Innovium		Innovium
	D. Lewis		D. Lewis
	M. Smith		M. Smith
	Cisco		Cisco
	November 4, 2019		November 4, 2019
	LISP Generic Protocol Extension		LISP Generic Protocol Extension
	draft-ietf-lisp-gpe-10		draft-ietf-lisp-gpe-11
	Abstract		Abstract
	This document describes extentions to the Locator/ID Separation		This document describes extentions to the Locator/ID Separation
	Protocol (LISP) Data-Plane, via changes to the LISP header, to		Protocol (LISP) Data-Plane, via changes to the LISP header, to
	support multi-protocol encapsulation.		support multi-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 4, line 27 ¶		skipping to change at page 4, line 27 ¶
	3. Generic Protocol Extension for LISP (LISP-GPE)		3. Generic Protocol Extension for LISP (LISP-GPE)
	This document defines two changes to the LISP header in order to		This document defines two changes to the LISP header in order to
	support multi-protocol encapsulation: the introduction of the P-bit		support multi-protocol encapsulation: the introduction of the P-bit
	and the definition of a Next Protocol field. This is shown in		and the definition of a Next Protocol field. This is shown in
	Figure 2 and described below.		Figure 2 and described below.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Res. |I|P|K|K| Nonce/Map-Version | Next Protocol |		| Res. |I|P|K|K| Reserved | Next Protocol |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Instance ID |		| Instance ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: LISP-GPE Header		Figure 2: LISP-GPE Header
	Bits 0-3: Bits 0-3 of the LISP-GPE header are Reserved. They MUST		Bits 0-3 and 8-23: Bits 0-3 and 8-23 of the LISP-GPE header are
	be set to zero on transmission and ignored on receipt.		Reserved. They MUST be set to zero on transmission and ignored on
			receipt.
	Features that were implemented with bits 0-3 in		Features that were implemented with bits 0-3 in
	[I-D.ietf-lisp-rfc6830bis], such as echo-noncing, map-versioning		[I-D.ietf-lisp-rfc6830bis], such as echo-noncing, map-versioning
	and reachability, can be implemented by defining the appropriate		and reachability, can be implemented by defining the appropriate
	shim headers.		shim headers.
	Instance ID When the I-Bit is set to 1 the high-order 24 bits of the		Instance ID When the I-Bit is set to 1 the high-order 24 bits of the
	Instance ID field are used as an Instance ID, as specified in		Instance ID field are used as an Instance ID, as specified in
	[I-D.ietf-lisp-rfc6830bis]. The low-order 8 bits are set to zero,		[I-D.ietf-lisp-rfc6830bis]. The low-order 8 bits are set to zero,
	as the Locator-Status-Bits feature is not supported in LISP-GPE.		as the Locator-Status-Bits feature is not supported in LISP-GPE.
End of changes. 3 change blocks.
	4 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/