Technical Requirements of Bounded Latency Forwarding
draft-geng-detnet-requirements-bounded-latency-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-03-07
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            L. Geng
Internet-Draft                                              China Mobile
Intended status: Informational                                  L. Qiang
Expires: September 9, 2019                           Huawei Technologies
                                                               T. Eckert
                                                                  Huawei
                                                           March 8, 2019

          Technical Requirements of Bounded Latency Forwarding
           draft-geng-detnet-requirements-bounded-latency-01

Abstract

   This document analyses the technical requirements that Layer 3
   bounded latency forwarding scheme should satisfy.

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 9, 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.

Geng, et al.            Expires September 9, 2019               [Page 1]
Internet-Draft       Requirements of Bounded Latency          March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology & Abbreviations . . . . . . . . . . . . . . .   3
   2.  Tolerance of Time Deviation . . . . . . . . . . . . . . . . .   3
   3.  Long Link Propagation Delay . . . . . . . . . . . . . . . . .   3
   4.  Massive Dynamic Flows . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   DetNet is chartered to provide deterministic forwarding over Layer 3.
   Deterministic forwarding means packet forwarding with bounded
   latency, loss and delay variation
   [draft-ietf-detnet-problem-statement].  In current DetNet's
   discussion, low packet loss is mainly achieved through PREOF (Packet
   Replication, Elimination, and Ordering
   Functions)[draft-ietf-detnet-architecture].  This document focuses on
   bounded latency.

   Common IP/MPLS forwarding has long tail effect that couldn't
   guarantee bounded latency.  DetNet has to have an approach to
   identify DetNet flows, and divert them into a DetNet forwarding plane
   in which some schemes are adapted to guarantee bounded latency.
   There are several schemes are proposed for bounded latency forwarding
   such as dedicated tunnel, light load with per-flow per-hop shaping,
   Time Aware Shaping[IEEE802.1Qbv], Cyclic Queuing and
   Forwarding[IEEE802.1Qch], Scalable Deterministic
   Forwarding[draft-qiang-detnet-large-scale-detnet], and SR based
   bounded latency[draft-chen-detnet-sr-based-bounded-latency].  This
   document is not going to compare and analyze these schemes, but to
   propose some factors (Layer 3 specific) worth to be considered when
   selecting Layer 3 bounded latency forwarding scheme.

1.1.  Requirements Language

   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.

Geng, et al.            Expires September 9, 2019               [Page 2]
Internet-Draft       Requirements of Bounded Latency          March 2019

1.2.  Terminology & Abbreviations
Show full document text