draft-ietf-manet-dlep-lid-extension-01.txt   draft-ietf-manet-dlep-lid-extension-02.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: August 3, 2018 VT iDirect Expires: September 20, 2018 VT iDirect
January 30, 2018 March 19, 2018
Link Identifier Extension to DLEP DLEP Link Identifier Extension
draft-ietf-manet-dlep-lid-extension-01 draft-ietf-manet-dlep-lid-extension-02
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 August 3, 2018. This Internet-Draft will expire on September 20, 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 2, line 38 skipping to change at page 2, line 38
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 3
2. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Identifier Restrictions . . . . . . . . . . . . . . . . . 4 2.1. Identifier Restrictions . . . . . . . . . . . . . . . . . 4
2.2. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 4
3. New Data Items . . . . . . . . . . . . . . . . . . . . . . . 5 3. New Data Items . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Link Identifier Length Data Item . . . . . . . . . . . . 5 3.1. Link Identifier Length Data Item . . . . . . . . . . . . 5
3.2. Link Identifier Data Item . . . . . . . . . . . . . . . . 6 3.2. Link Identifier Data Item . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5.1. DLEP Link Identifier Flag . . . . . . . . . . . . . . . . 7
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . 7 6.1. Normative References . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . 7 6.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
The Dynamic Link Exchange Protocol (DLEP) [RFC8175] describes a The Dynamic Link Exchange Protocol (DLEP) [RFC8175] describes a
protocol for modems to advertise the status of wireless links between protocol for modems to advertise the status of wireless links between
reachable destinations to attached routers. The core specification reachable destinations to attached routers. The core specification
of the protocol assumes that every modem in the radio network has an of the protocol assumes that every modem in the radio network has an
attached DLEP router, and requires that the MAC address of the DLEP attached DLEP router, and requires that the MAC address of the DLEP
interface on the attached router is used to identify the destination interface on the attached router is used to identify the destination
in the network for purposes of reporting the state and quality of the in the network for purposes of reporting the state and quality of the
skipping to change at page 5, line 32 skipping to change at page 5, line 32
3. New Data Items 3. New Data Items
This extension introduces two new DLEP Data Items: the Link This extension introduces two new DLEP Data Items: the Link
Identifier Data Item (Section 3.2) used to identify a Layer 3 link at Identifier Data Item (Section 3.2) used to identify a Layer 3 link at
or beyond a destination, and the Link Identifier Length Data Item or beyond a destination, and the Link Identifier Length Data Item
(Section 3.1) used to announce the length of Link Identifiers at (Section 3.1) used to announce the length of Link Identifiers at
session initialization. session initialization.
3.1. Link Identifier Length Data Item 3.1. Link Identifier Length Data Item
The Link Identifier Length Data Item MAY be used by a DLEP modem The Link Identifier Length Data Item MUST be used by a DLEP modem
implementation to define the length of Link Identifier Data Items if implementation to define the length of Link Identifier Data Items if
it does not with to use the default value of 4 octets. it does not with to use the default value of 4 octets.
The Link Identifier Length Data Item MAY be used during Session The Link Identifier Length Data Item MAY be used during Session
Initialization, contained in a Session Initialization Response Initialization, contained in a Session Initialization Response
Message. Message.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 17 skipping to change at page 6, line 17
3.2. Link Identifier Data Item 3.2. Link Identifier Data Item
The Link Identifier Data Item MAY be used wherever a MAC Address Data The Link Identifier Data Item MAY be used wherever a MAC Address Data
Item is defined as usable in core DLEP. Item is defined as usable in core DLEP.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Link Identifier... : | Link Identifier... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD3, Section 5 Data Item Type: TBD3, Section 5
Length: The length of the Data Item, by default 5, but may be Length: The length of the Data Item, by default 5, but may be
different if a Link Identifier Length Data Item (Section 3.1) has different if a Link Identifier Length Data Item (Section 3.1) has
been announced during session initialization. been announced during session initialization.
Flags: Flags field, defined below.
Link Identifier: The unique identifier of the Layer 3 destination. Link Identifier: The unique identifier of the Layer 3 destination.
This identifier has no implicit meaning and is only used to This identifier has no implicit meaning and is only used to
discriminate between multiple links. discriminate between multiple links.
The Flags field is defined as:
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| Reserved |
+-+-+-+-+-+-+-+-+
Reserved: MUST be zero. Left for future assignment.
4. Security Considerations 4. Security Considerations
As an extension to the core DLEP protocol, the security As an extension to the core DLEP protocol, the security
considerations of that protocol apply to this extension. This considerations of that protocol apply to this extension. This
extension adds no additional security mechanisms or features. extension adds no additional security mechanisms or features.
None of the features introduced by this extension require extra None of the features introduced by this extension require extra
consideration by an implementation. consideration by an implementation.
5. IANA Considerations 5. IANA Considerations
skipping to change at page 7, line 20 skipping to change at page 7, line 9
of the DLEP Extensions Registry, named "Link Identifiers". of the DLEP Extensions Registry, named "Link Identifiers".
o Assign a new value (TBD2) from the Specification Required section o Assign a new value (TBD2) from the Specification Required section
of the DLEP Data Item Type Values Registry, named "Link Identifier of the DLEP Data Item Type Values Registry, named "Link Identifier
Length". Length".
o Assign a new value (TBD3) from the Specification Required section o Assign a new value (TBD3) from the Specification Required section
of the DLEP Data Item Type Values Registry, named "Link of the DLEP Data Item Type Values Registry, named "Link
Identifier". Identifier".
5.1. DLEP Link Identifier Flag
Upon approval of this document, IANA is requested to create a new
DLEP registry, named "Link Identifier Flags".
The following table provides initial registry values and the RFC 5226
defined policies that should apply to the registry:
+------------+------------------------------------+
| Bit | Description/Policy |
+------------+------------------------------------+
| 0-7 | Unassigned/Specification Required |
+------------+------------------------------------+
6. References 6. References
6.1. Normative References 6.1. Normative References
[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>.
[RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. [RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
 End of changes. 10 change blocks. 
35 lines changed or deleted 9 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/