DetNet Service Model
draft-varga-detnet-service-model-02

Document Type Active Internet-Draft (individual)
Last updated 2017-05-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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)
DetNet                                                     B. Varga, Ed.
Internet-Draft                                                 J. Farkas
Intended status: Standards Track                                Ericsson
Expires: November 3, 2017                                    May 2, 2017

                          DetNet Service Model
                  draft-varga-detnet-service-model-02

Abstract

   This document describes service model for scenarios requiring
   deterministic networking.

   This new version 02 of the DetNet Service Model draft is primarily
   intended to prevent it from expiring.  Major parts of this document
   were moved to the architecture draft, but some remaining text is
   under discussion in the workgroup (e.g., QoS, etc.).

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 November 3, 2017.

Copyright Notice

   Copyright (c) 2017 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

Varga & Farkas          Expires November 3, 2017                [Page 1]
Internet-Draft            DetNet Service Model                  May 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3
   3.  Terminology and Definitions . . . . . . . . . . . . . . . . .   3
   4.  End systems connected to DetNet . . . . . . . . . . . . . . .   4
   5.  DetNet service model  . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Service parameters  . . . . . . . . . . . . . . . . . . .   8
     5.2.  Service overview  . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Reference Points  . . . . . . . . . . . . . . . . . . . .  10
     5.4.  Service scenarios . . . . . . . . . . . . . . . . . . . .  11
     5.5.  Data flows  . . . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  Service components/segments . . . . . . . . . . . . . . .  12
   6.  DetNet service instances  . . . . . . . . . . . . . . . . . .  12
     6.1.  Attributes used by DetNet functions . . . . . . . . . . .  12
     6.2.  Service instance for DetNet flows . . . . . . . . . . . .  13
   7.  DetNet flows over multiple technology domains . . . . . . . .  14
     7.1.  Flow attribute mapping between layers . . . . . . . . . .  14
     7.2.  Flow-ID mapping examples  . . . . . . . . . . . . . . . .  15
   8.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  18
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  18
   12. Annex 1 - Service Instance shared by DetNet and regular
       traffic . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  L2 service instance shared by regular and DetNet traffic  18
     12.2.  L3 service instance shared by regular and DetNet traffic  19
   13. Annex 2 - Integrating Layer 3 and Layer 2 QoS . . . . . . . .  20
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  26
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  27
     14.2.  Informative References . . . . . . . . . . . . . . . . .  27
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  28

1.  Introduction

   A Deterministic Networking (DetNet) service provides a capability to
   carry a unicast or a multicast data flow for an application with
   constrained requirements on network performance, e.g., low packet
   loss rate and/or latency.  During the discussion of DetNet use cases,
Show full document text