User Plane Message Encoding
draft-murakami-dmm-user-plane-message-encoding-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf ps 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)
Internet Engineering Task Force                         T. Murakami, Ed.
Internet-Draft                                               Arrcus, Inc
Intended status: Informational                             S. Matsushima
Expires: May 7, 2020                                            SoftBank
                                                              K. Ebisawa
                                                Toyota Motor Corporation
                                                               P. Garvia
                                                              R. Shekhar
                                                     Cisco Systems, Inc.
                                                        November 4, 2019

                      User Plane Message Encoding
           draft-murakami-dmm-user-plane-message-encoding-00

Abstract

   This document defines the encoding of User Plane messages into
   Segment Routing Header (SRH).  The SRH carries the User Plane
   messages over SRv6 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."

   This Internet-Draft will expire on May 7, 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

Murakami, et al.           Expires May 7, 2020                  [Page 1]
Internet-Draft         user-plane-message-encoding         November 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   4.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  User Plane Message encoding into SRH  . . . . . . . . . . . .   3
     5.1.  GTP-U Header format . . . . . . . . . . . . . . . . . . .   3
     5.2.  Encoding of Tags Field  . . . . . . . . . . . . . . . . .   4
     5.3.  User Plane message Information Element Support  . . . . .   5
     5.4.  Consideration of PSP case . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Consideration  . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   3GPP defines User Plane messages.  The User Plane messages support
   in-band signaling for path and tunnel management.  Currently, User
   Plane messages are defined in TS 29.281 [TS29281].

   When applying SRv6 (Segment Routing IPv6) to the user plane of mobile
   networks based on draft-ietf-dmm-srv6-mobile-uplane
   [I-D.ietf-dmm-srv6-mobile-uplane], User Plane messages must be
   carried over SRv6 network.  This document defines which User Plane
   message must be encoded to SRv6 and also defines how to encode the
   User Plane messages into SRH.

   In addition, SRH is mandatory at the ultimate segment upon carrying
   the User Plane messages because User Plane message is encoded into
   SRH.  Hence, this document considers how to deal with the encoding of
   User Plane messages into SRH when PSP is applied that SRH is popped
   out at the penultimate segment.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Murakami, et al.           Expires May 7, 2020                  [Page 2]
Internet-Draft         user-plane-message-encoding         November 2019
Show full document text