Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension
RFC 8629
Document | Type | RFC - Proposed Standard (July 2019; No errata) | |
---|---|---|---|
Authors | Bow-Nan Cheng , Lou Berger | ||
Last updated | 2019-07-23 | ||
Replaces | draft-cheng-manet-dlep-multi-hop-extension | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Stan Ratliff | ||
Shepherd write-up | Show (last changed 2018-08-13) | ||
IESG | IESG state | RFC 8629 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
Send notices to | Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) B. Cheng Request for Comments: 8629 MIT Lincoln Laboratory Category: Standards Track L. Berger, Ed. ISSN: 2070-1721 LabN Consulting, L.L.C. July 2019 Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension Abstract This document defines an extension to the Dynamic Link Exchange Protocol (DLEP) that enables the reporting and control of multi-hop forwarding by DLEP-capable modems. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8629. 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 Standards Track [Page 1] RFC 8629 DLEP Multi-Hop Extension July 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 . . . . . . . . . . . . . . . . . . . . 9 5.3. Hop Control Actions Registry . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . 10 6.2. Informative References . . . . . . . . . . . . . . . . . 10 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 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". 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 allows 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 document can result in connectivity changes and even loss of the ability to reach one or more destinations. The defined Cheng & Berger Standards Track [Page 2] RFC 8629 DLEP Multi-Hop Extension July 2019Show full document text