DLEP Lantency Range Extension
draft-ietf-manet-dlep-latency-extension-01

Document Type Active Internet-Draft (manet WG)
Last updated 2017-10-30
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           B. Cheng
Internet-Draft                                        Lincoln Laboratory
Intended status: Standards Track                          L. Berger, Ed.
Expires: May 3, 2018                             LabN Consulting, L.L.C.
                                                        October 30, 2017

                     DLEP Lantency Range Extension
               draft-ietf-manet-dlep-latency-extension-01

Abstract

   This document defines an extension to the DLEP protocol to provide
   the range of latency that may be experienced on a link.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 3, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Cheng & Berger             Expires May 3, 2018                  [Page 1]
Internet-Draft        DLEP Latency Range Extension          October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Key Words . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Extension Usage and Identification  . . . . . . . . . . . . .   2
   3.  Latency Range Data Items  . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Extension Type Value  . . . . . . . . . . . . . . . . . .   4
     5.2.  Data Item Value . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Dynamic Link Event Protocol (DLEP) is defined in [RFC8175].  It
   provides the exchange of link related control information between
   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
   extensions.  This document defines one such extension.

   The base DLEP specification includes the Latency metric which
   provides an average latency on a link.  This document adds the
   ability to relay the minimum and maximum latency range seen on a
   link.  The extension defined in this document is referred to as
   "Latency Range".

   This document defines a new DLEP Extension Type Value in Section 2
   which is used to indicate the use of the extension, and one new DLEP
   Data Items in Section 3.

1.1.  Key Words

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Extension Usage and Identification

   The use of the Latency Range Extension SHOULD be configurable.  To
   indicate that the Latency Range Extension is to be used, an
   implementation MUST include the Latency Range Extension Type Value in
   the Extensions Supported Data Item.  The Extensions Supported Data
   Item is sent and processed according to [RFC8175].

   The Latency Range Extension Type Value is TBA1, see Section 5.

Cheng & Berger             Expires May 3, 2018                  [Page 2]
Internet-Draft        DLEP Latency Range Extension          October 2017
Show full document text