Credit Windowing extension for DLEP
draft-ietf-manet-credit-window-07

Document Type Active Internet-Draft (manet WG)
Last updated 2016-12-08 (latest revision 2016-11-13)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Other - see Comment Log
Document shepherd Justin Dean
Shepherd write-up Show (last changed 2016-04-01)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Justin Dean" <bebemaster@gmail.com>, aretana@cisco.com
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Mobile Ad hoc Networks Working Group                          S. Ratliff
Internet-Draft                                                VT iDirect
Intended status: Standards Track                       November 13, 2016
Expires: May 17, 2017

                  Credit Windowing extension for DLEP
                   draft-ietf-manet-credit-window-07

Abstract

   This draft describes an extension to the DLEP protocol to provide a
   credit-windowing scheme for destination-specific flow control.

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 http://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 17, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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.

Ratliff                   Expires May 17, 2017                  [Page 1]
Internet-Draft     Credit Windowing extension for DLEP     November 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  DLEP Messages for Credit-Window Extension . . . . . . . . . .   5
   7.  DLEP Status Codes for Credit-Window Extension . . . . . . . .   5
   8.  DLEP Data Items for Credit-Window Extension . . . . . . . . .   5
   9.  Credit Window Data Item Definitions . . . . . . . . . . . . .   6
     9.1.  Credit Grant  . . . . . . . . . . . . . . . . . . . . . .   6
     9.2.  Credit Window Status  . . . . . . . . . . . . . . . . . .   7
     9.3.  Credit Request  . . . . . . . . . . . . . . . . . . . . .   8
   10. Credit Data Item Use in DLEP Messages . . . . . . . . . . . .   9
     10.1.  DLEP Destination Up Message  . . . . . . . . . . . . . .   9
     10.2.  DLEP Destination Announce Message  . . . . . . . . . . .   9
     10.3.  DLEP Destination Up Response Message . . . . . . . . . .   9
     10.4.  DLEP Destination Announce Response Message . . . . . . .  10
     10.5.  DLEP Destination Update Message  . . . . . . . . . . . .  11
     10.6.  DLEP Link Characteristics Request Message  . . . . . . .  11
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     12.1.  Registrations  . . . . . . . . . . . . . . . . . . . . .  12
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   14. Normative References  . . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   In the world of radio-based networking, there are modems that need
   fine-grained flow control over traffic ingressing from a LAN
   connection, bound for transmission over a Radio Frequency (RF) link.
   The need for such fine-grained control can exist for multiple
   reasons.  For example, radio devices are typically connected to the
   network by Ethernet.  The capacity of an Ethernet link is normally
   far superior to that of the wireless medium, leading to the
   possibility of overruns and dropped traffic.  This is exacerbated by
   the fact that RF link capacity can vary from moment to moment, for an
   indeterminate amount of time.  Additionally, the capacity of the link
   can vary greatly depending on the destination, due to factors such as
   obstructions or multipath fading.

   These challenges motivate the requirement for a fine-grained flow
   control in radio-based communications - one that can support
Show full document text