DLEP Multi-Hop Forwarding Extension
draft-ietf-manet-dlep-multi-hop-extension-06

The information below is for an old version of the document
Document Type Active Internet-Draft (manet WG)
Last updated 2019-05-02 (latest revision 2019-03-11)
Replaces draft-cheng-manet-dlep-multi-hop-extension
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Stan Ratliff
Shepherd write-up Show (last changed 2018-08-13)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                           B. Cheng
Internet-Draft                                    MIT Lincoln Laboratory
Intended status: Standards Track                          L. Berger, Ed.
Expires: September 12, 2019                      LabN Consulting, L.L.C.
                                                          March 11, 2019

                  DLEP Multi-Hop Forwarding Extension
              draft-ietf-manet-dlep-multi-hop-extension-06

Abstract

   This document defines an extension to the DLEP protocol that enables
   the reporting and control of Multi-Hop Forwarding by DLEP capable
   modems.

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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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 September 12, 2019               [Page 1]
Internet-Draft          DLEP Multi-Hop Extension              March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Key Words . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Extension Usage and Identification  . . . . . . . . . . . . .   3
   3.  Extension Data Items  . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Hop Count . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Hop Control . . . . . . . . . . . . . . . . . . . . . . .   5
       3.2.1.  Reset . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  Terminate . . . . . . . . . . . . . . . . . . . . . .   7
       3.2.3.  Direct Connection . . . . . . . . . . . . . . . . . .   7
       3.2.4.  Suppress Forwarding . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Extension Type Value  . . . . . . . . . . . . . . . . . .   8
     5.2.  Data Item Values  . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Hop Control Actions Registry  . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Dynamic Link Exchange 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.

   Some modem technologies support mobile ad hoc network (MANET)
   forwarding where connectivity to destinations is provided via
   forwarding in intermediate modems.  This document refers to
   forwarding by intermediate modems as 'multi-hop forwarding'.  example
   using . DLEP Destination messages can be used to report such
   reachable destinations, see [RFC8175], but do not provide any
   information related to the number or capacity of the hops.  The
   extension defined in this document enables modems to inform routers
   when multi-hop forwarding is being used, and routers to request that
   modems change multi-hop forwarding behavior.  The extension defined
   in this document is referred to as "Multi-Hop Forwarding", where each
   modem that transmits/sends data to reach a particular destination is
   counted as a hop.

   It is important to note that the use of the hop control mechanism
   defined in this can result in connectivity changes and even loss of
Show full document text