draft-ietf-manet-dlep-lid-extension-02.txt   draft-ietf-manet-dlep-lid-extension-03.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: September 20, 2018 VT iDirect Expires: February 21, 2019 VT iDirect
March 19, 2018 August 20, 2018
DLEP Link Identifier Extension DLEP Link Identifier Extension
draft-ietf-manet-dlep-lid-extension-02 draft-ietf-manet-dlep-lid-extension-03
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 1, line 47 skipping to change at page 1, line 47
with the operation of core DLEP. with the operation of core DLEP.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 September 20, 2018. This Internet-Draft will expire on February 21, 2019.
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 (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 4, line 30 skipping to change at page 4, line 30
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 differ 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
identified by the pair: {MAC Address,Link Id}. identified by the pair: {MAC Address,Link Id}.
skipping to change at page 6, line 22 skipping to change at page 6, line 22
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 4, 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.
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.
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
skipping to change at page 7, line 15 skipping to change at page 7, line 15
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".
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,
editor.org/info/rfc2119>. <https://www.rfc-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.
Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175, Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
DOI 10.17487/RFC8175, June 2017, <https://www.rfc- DOI 10.17487/RFC8175, June 2017,
editor.org/info/rfc8175>. <https://www.rfc-editor.org/info/rfc8175>.
6.2. Informative References 6.2. Informative References
[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,
editor.org/info/rfc5226>. <https://www.rfc-editor.org/info/rfc5226>.
Authors' Addresses Authors' Addresses
Rick Taylor Rick Taylor
Airbus Defence & Space Airbus Defence & Space
Quadrant House Quadrant House
Celtic Springs Celtic Springs
Coedkernew Coedkernew
Newport NP10 8FZ Newport NP10 8FZ
UK UK
 End of changes. 10 change blocks. 
14 lines changed or deleted 14 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/