Diffserv to QCI Mapping
draft-henry-tsvwg-diffserv-to-qci-02

Document Type Active Internet-Draft (individual)
Last updated 2019-10-14
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                           J. Henry
Internet-Draft                                                T. Szigeti
Intended status: Informational                                     Cisco
Expires: April 14, 2020                                 October 12, 2019

                        Diffserv to QCI Mapping
                  draft-henry-tsvwg-diffserv-to-qci-02

Abstract

   As communication devices become more hybrid, smart devices include
   more media-rich communication applications, and the boundaries
   between telecommunication and other applications becomes less clear.
   Simultaneously, as the end-devices become more mobile, application
   traffic transits more often between enterprise networks, the
   Internet, and cellular telecommunication networks, sometimes using
   simultaneously more than one path and network type.  In this context,
   it is crucial that quality of service be aligned between these
   different environments.  However, this is not always the case by
   default, and cellular communication networks use a different QoS
   nomenclature from the Internet and enterprise networks.  This
   document specifies a set of 3rd Generation Partnership Project (3GPP)
   Quality of Service (QoS) Class Identifiers (QCI) to Differentiated
   Services Code Point (DSCP) mappings, to reconcile the marking
   recommendations offered by the 3GPP with the recommendations offered
   by the IETF, so as to maintain a consistent QoS treatment between
   cellular networks and the Internet.  This mapping can be used by
   enterprises or implementers expecting traffic to flow through both
   types of network, and wishing to align the QoS treatment applied to
   one network under their control with the QoS treatment applied to the
   other network.

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."

Henry & Szigeti          Expires April 14, 2020                 [Page 1]
Internet-Draft                DIFFSERV-QCI                  October 2019

   This Internet-Draft will expire on April 14, 2020.

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Related Work  . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Applicability Statement . . . . . . . . . . . . . . . . .   4
     1.3.  Document Organization . . . . . . . . . . . . . . . . . .   5
     1.4.  Requirements language . . . . . . . . . . . . . . . . . .   5
     1.5.  Terminology Used in this Document . . . . . . . . . . . .   5
   2.  Service Comparison and Default Interoperation of Diffserv and
       3GPP LTE  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Diffserv Domain Boundaries  . . . . . . . . . . . . . . .   7
     2.2.  QCI and Bearer Model in 3GPP  . . . . . . . . . . . . . .   7
     2.3.  QCI Definition and Logic  . . . . . . . . . . . . . . . .   9
       2.3.1.  Conversational  . . . . . . . . . . . . . . . . . . .   9
       2.3.2.  Streaming . . . . . . . . . . . . . . . . . . . . . .   9
       2.3.3.  Interactive . . . . . . . . . . . . . . . . . . . . .  10
       2.3.4.  Background  . . . . . . . . . . . . . . . . . . . . .  10
     2.4.  QCI implementations . . . . . . . . . . . . . . . . . . .  13
     2.5.  GSMA IPX Guidelines Interpretation and Conflicts  . . . .  13
   3.  P-GW Device Marking and Mapping Capability Recommendations  .  14
   4.  DSCP-to-QCI Mapping Recommendations . . . . . . . . . . . . .  15
     4.1.  Control Traffic . . . . . . . . . . . . . . . . . . . . .  15
       4.1.1.  Network Control Protocols . . . . . . . . . . . . . .  15
       4.1.2.  Operations, Administration, and Maintenance (OAM) . .  16
Show full document text