draft-ietf-manet-dlep-latency-extension-04.txt   draft-ietf-manet-dlep-latency-extension-05.txt 
Network Working Group B. Cheng Network Working Group B. Cheng
Internet-Draft MIT Lincoln Laboratory Internet-Draft MIT Lincoln Laboratory
Intended status: Standards Track L. Berger, Ed. Intended status: Standards Track L. Berger, Ed.
Expires: April 20, 2019 LabN Consulting, L.L.C. Expires: May 23, 2020 LabN Consulting, L.L.C.
October 17, 2018 November 20, 2019
DLEP Latency Range Extension Dynamic Link Exchange Protocol (DLEP) Latency Range Extension
draft-ietf-manet-dlep-latency-extension-04 draft-ietf-manet-dlep-latency-extension-05
Abstract Abstract
This document defines an extension to the DLEP protocol to provide This document defines an extension to the Dynamic Link Exchange
the range of latency that may be experienced on a link. Protocol (DLEP) to provide the range of latency that can be
experienced on a link.
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 https://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 April 20, 2019. This Internet-Draft will expire on May 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Key Words . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Extension Usage and Identification . . . . . . . . . . . . . 2 2. Extension Usage and Identification . . . . . . . . . . . . . 2
3. Latency Range Data Item . . . . . . . . . . . . . . . . . . . 3 3. Latency Range Data Item . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4 5.1. Extension Type Value . . . . . . . . . . . . . . . . . . 4
5.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 4 5.2. Data Item Value . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175]. The Dynamic Link Exchange Protocol (DLEP) is defined in [RFC8175].
It provides the exchange of link related control information between It provides the exchange of link related control information between
DLEP peers. DLEP peers are comprised of a modem and a router. DLEP DLEP peers. DLEP peers are comprised of a modem and a router. DLEP
defines a base set of mechanisms as well as support for possible defines a base set of mechanisms as well as support for possible
extensions. This document defines one such extension. extensions. This document defines one such extension.
skipping to change at page 3, line 15 skipping to change at page 3, line 15
Note: the usage of the extension defined in this document does not Note: the usage of the extension defined in this document does not
impact processing associated with the Latency Data Item defined in impact processing associated with the Latency Data Item defined in
[RFC8175]. [RFC8175].
The Latency Range Extension Type Value is TBA1, see Section 5. The Latency Range Extension Type Value is TBA1, see Section 5.
3. Latency Range Data Item 3. Latency Range Data Item
The Latency Range Data Item serves much the same purpose as the The Latency Range Data Item serves much the same purpose as the
Latency Data Item defined in [RFC8175] with the addition of being Latency Data Item defined in [RFC8175] with the addition of being
able to communicate the latency range that may be experienced by able to communicate the latency range that can be experienced by
traffic on a link. The Latency Range Data Item MAY be carried in any traffic on a link. The Latency Range Data Item MUST be included in
message where the Latency Data Item [RFC8175] is allowed and is the Session Initialization Response Message, with default values to
carried as an additional data item. When present, the Latency Range be used on a session-wide basis. The Latency Range Data Item also
Data Item MUST be processed according to the same rules as the MAY be carried in any message where the Latency Data Item [RFC8175]
Latency Data Item defined in [RFC8175]. is allowed and is carried as an additional data item. When present,
the Latency Range Data Item MUST be processed according to the same
rules as the Latency Data Item defined in [RFC8175].
The format of the Latency Range Data Item is: The format of the Latency Range Data Item is:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Latency : | Maximum Latency :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 3, line 51 skipping to change at page 4, line 6
Maximum Latency: Maximum Latency:
A 64-bit unsigned integer, representing the longest transmission A 64-bit unsigned integer, representing the longest transmission
delay, in microseconds, that a packet encounters as it is delay, in microseconds, that a packet encounters as it is
transmitted over the link. transmitted over the link.
Minimum Latency: Minimum Latency:
A 64-bit unsigned integer, representing the shortest transmission A 64-bit unsigned integer, representing the shortest transmission
delay, in microseconds, that a packet encounters as it is delay, in microseconds, that a packet can encounter as it is
transmitted over the link. transmitted over the link.
4. Security Considerations 4. Security Considerations
The extension introduces a new Data Item for the DLEP protocol. The The extension introduces a new Data Item for DLEP. The extension
extension does not inherently introduce any additional threats above does not inherently introduce any additional vulnerabilities above
those documented in [RFC8175]. The approach taken to Security in those documented in [RFC8175]. The approach taken to Security in
that document applies equally when running the extension defined in that document applies equally when running the extension defined in
this document. this document.
5. IANA Considerations 5. IANA Considerations
This document requests the assignment of 2 values by IANA. All This document requests the assignment of two values by IANA. All
assignments are to registries defined by [RFC8175]. assignments are to registries defined by [RFC8175].
5.1. Extension Type Value 5.1. Extension Type Value
This document requests one new assignment to the DLEP Extensions This document requests one new assignment to the DLEP Extensions
Registry named "Extension Type Values" in the range with the Registry named "Extension Type Values" in the range with the
"Specification Required" policy. The requested value is as follows: "Specification Required" policy. The requested value is as follows:
+------+---------------+ +------+---------------+
| Code | Description | | Code | Description |
 End of changes. 10 change blocks. 
19 lines changed or deleted 22 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/