Requirements of Layer 3 Deterministic Latency Service
draft-geng-detnet-requirements-bounded-latency-02

Document Type Active Internet-Draft (individual)
Last updated 2019-06-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                 P. Willis
Expires: December 5, 2019                                             BT
                                                                S. Homma
                                                                     NTT
                                                                L. Qiang
                                                                  Huawei
                                                            June 3, 2019

         Requirements of Layer 3 Deterministic Latency Service
           draft-geng-detnet-requirements-bounded-latency-02

Abstract

   This document specifies some technical, operational and management
   requirements of deploying deterministic latency service on layer 3
   networks from the perspective of the service provider.

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 December 5, 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

Geng, et al.            Expires December 5, 2019                [Page 1]
Internet-Draft    Requirements of Deterministic Latency        June 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology & Abbreviations . . . . . . . . . . . . . . .   3
   2.  Technical Requirements  . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirement 1: Must support the dynamic creation,
           modification and deletion of deterministic services . . .   3
     2.2.  Requirement 2: Should tolerate a certain degree of time
           variance  . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.2.1.  Sub-requirement 2.1: Should support asynchronous
               clocks across domains . . . . . . . . . . . . . . . .   4
       2.2.2.  Sub-requirement 2.2: Should tolerate clock jitter &
               wander within a clock synchronous domain  . . . . . .   4
     2.3.  Requirement 3: Must support Inter-Continental propagation
           delay . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Operational and Management Requirements . . . . . . . . . . .   6
     3.1.  Requirement 4: Should have self-monitoring capability . .   6
     3.2.  Requirement 5: Should be robust against denial of service
           attacks . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Requirement 6: Must tolerate failures of links or nodes
           and topology changes  . . . . . . . . . . . . . . . . . .   7
     3.4.  Requirement 7: Must be scalable . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   DetNet is chartered to provide bounds on latency, jitter (delay
   variation) and packet loss [draft-ietf-detnet-problem-statement].
   Where latency and jitter are two closely related performance
   characteristics, this document refers to bounded latency and bounded
   jitter collectively as deterministic latency.

   This document does not intend to define any specific mechanism, but
   specifies some technical, operational and management requirements
   that must be considered when deploying deterministic latency service
   at layer 3.
Show full document text