< draft-ietf-manet-dlep-lid-extension-00.txt		draft-ietf-manet-dlep-lid-extension-01.txt >
	Mobile Ad hoc Networks Working Group R. Taylor		Mobile Ad hoc Networks Working Group R. Taylor
	Internet-Draft Airbus Defence & Space		Internet-Draft Airbus Defence & Space
	Intended status: Standards Track S. Ratliff		Intended status: Standards Track S. Ratliff
	Expires: June 18, 2018 VT iDirect		Expires: August 3, 2018 VT iDirect
	December 15, 2017		January 30, 2018
	Link Identifier Extension to DLEP		Link Identifier Extension to DLEP
	draft-ietf-manet-dlep-lid-extension-00		draft-ietf-manet-dlep-lid-extension-01
	Abstract		Abstract
	There exists a class of modems that wish to support the Dynamic Link		There exists a class of modems that wish to support the Dynamic Link
	Exchange Protocol (DLEP) [RFC8175] but do not present a single Layer		Exchange Protocol (DLEP) [RFC8175] but do not present a single Layer
	2 network domain as required by DLEP. Such devices may be:		2 network domain as required by DLEP. Such devices may be:
	o Modems that maintain a varying link to some upstream backbone		o Modems that maintain a varying link to some upstream backbone
	network infrastructure, where the ability to announce link state		network infrastructure, where the ability to announce link state
	and DLEP metrics is desired, but the concept of a DLEP destination		and DLEP metrics is desired, but the concept of a DLEP destination
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	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 June 18, 2018.		This Internet-Draft will expire on August 3, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 33 ¶		skipping to change at page 3, line 33 ¶
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in BCP 14, RFC 2119.		document are to be interpreted as described in BCP 14, RFC 2119.
	2. Operation		2. Operation
	To refer to a Layer 3 DLEP Destination, the DLEP session participant		To refer to a Layer 3 DLEP Destination, the DLEP session participant
	adds a Link Identifier Data Item (Section 3.2) to the relevant		adds a Link Identifier Data Item (Section 3.2) to the relevant
	Destination Message, and (as usual) includes a MAC Address Data Item.		Destination Message, and (as usual) includes a MAC Address Data Item.
	When paired with a Link Identifier Data Item, the MAC Address Data		When paired with a Link Identifier Data Item, the MAC Address Data
	Item describes the MAC address of the node in the network beyond		Item MUST contain the MAC address of the last reachable node in the
	which the Layer 3 DLEP Destination resides. The MAC address MAY		Layer 2 domain beyond which the Layer 3 DLEP Destination resides.
	belong to the DLEP peer modem, if the over-the-air network is not a		For example, if the over-the-air network is not a single Layer 2
	single Layer 2 domain, or MAY be the MAC address of a remote node in		domain, the MAC Address Data Item might be the address of the LAN-
	the Layer 2 domain that has indicated that it has DLEP Destinations		side interface of the local modem. Alternatively, when used with
	reachable beyond it. How such remote destinations are discovered is		some kind of backbone infrastructure, the MAC Address Data Item would
			be the address of the last device reachable on the local Layer 2
			domain. However, how such remote destinations are discovered is
	beyond the scope of this specification.		beyond the scope of this specification.
	As only modems are initially aware of Layer 3 DLEP Destinations, Link		As only modems are initially aware of Layer 3 DLEP Destinations, Link
	Identifier Data Items referring to a new link MUST first appear in a		Identifier Data Items referring to a new link MUST first appear in a
	DLEP Destination Up Message from the modem to the router. Once a		DLEP Destination Up Message from the modem to the router. Once a
	link has been identified in this way, Link Identifier Data Items MAY		link has been identified in this way, Link Identifier Data Items MAY
	be used by either DLEP participant during the lifetime of a DLEP		be used by either DLEP participant during the lifetime of a DLEP
	session. Because of this, a router MUST NOT send a DLEP Destination		session. Because of this, a router MUST NOT send a DLEP Destination
	Announce Message containing a Link Identifier Data Item referring to		Announce Message containing a Link Identifier Data Item referring to
	a link that has not been mentioned in a prior DLEP Destination Up		a link that has not been mentioned in a prior DLEP Destination Up
	skipping to change at page 4, line 22 ¶		skipping to change at page 4, line 22 ¶
	infrastructure, this means one or more IPv4 or IPv6 Attached Subnet		infrastructure, this means one or more IPv4 or IPv6 Attached Subnet
	Data Items, for example: '0.0.0.0/0' or '::/0'. This allows the DLEP		Data Items, for example: '0.0.0.0/0' or '::/0'. This allows the DLEP
	peer router to understand the properties of the link to those routes.		peer router to understand the properties of the link to those routes.
	When the DLEP peer router wishes to forward packets to the Layer 3		When the DLEP peer router wishes to forward packets to the Layer 3
	destination or subnet, the MAC address associated with the link MUST		destination or subnet, the MAC address associated with the link MUST
	be used as the Layer 2 destination of the packet.		be used as the Layer 2 destination of the packet.
	2.1. Identifier Restrictions		2.1. Identifier Restrictions
	A Link identifier is by default 4 octets in length. If a modem		A link identifier is by default 4 octets in length. If a modem
	wishes to use an identifier of a different length, it MUST be		wishes to use an identifier of a different length, it MUST be
	announced using the Link Identifier Length Data Item (Section 3.1)		announced using the Link Identifier Length Data Item (Section 3.1)
	contained in the DLEP Session Initialization Response message sent by		contained in the DLEP Session Initialization Response message sent by
	the modem to the router.		the modem to the router.
	During the lifetime of a DLEP session, the length of Link Identifiers		During the lifetime of a DLEP session, the length of link identifiers
	MUST remain constant, i.e. the Length field of the Link Identifier		MUST remain constant, i.e. the Length field of the Link Identifier
	Data Item must not alter between destinations.		Data Item must not alter between destinations.
	The method for generating identifiers is a modem implementation		The method for generating identifiers is a modem implementation
	matter and out of scope of this document. Routers MUST NOT make any		matter and out of scope of this document. Routers MUST NOT make any
	assumptions about the meaning of identifiers, or how identifiers are		assumptions about the meaning of identifiers, or how identifiers are
	generated.		generated.
	Within a single DLEP session, all link identifiers MUST be unique per		Within a single DLEP session, all link identifiers MUST be unique per
	MAC Address. This means that a Layer 3 DLEP Destination is uniquely		MAC Address. This means that a Layer 3 DLEP Destination is uniquely
End of changes. 7 change blocks.
	13 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/