Skip to main content

Segment Routing over IPv6 for the Mobile User Plane
draft-ietf-dmm-srv6-mobile-uplane-24

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, dmm-chairs@ietf.org, dmm@ietf.org, draft-ietf-dmm-srv6-mobile-uplane@ietf.org, ek.ietf@gmail.com, rfc-editor@rfc-editor.org, sgundave@cisco.com
Subject: Document Action: 'Segment Routing IPv6 for Mobile User Plane' to Informational RFC (draft-ietf-dmm-srv6-mobile-uplane-24.txt)

The IESG has approved the following document:
- 'Segment Routing IPv6 for Mobile User Plane'
  (draft-ietf-dmm-srv6-mobile-uplane-24.txt) as Informational RFC

This document is the product of the Distributed Mobility Management Working
Group.

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/


Ballot Text

Technical Summary

   This document specifies the applicability of SRv6 (Segment Routing
   IPv6) to the user-plane of mobile networks.  The network programming
   nature of SRv6 accomplishes mobile user-plane functions in a simple
   manner.  The statelessness of SRv6 and its ability to control both
   service layer path and underlying transport can be beneficial to the
   mobile user-plane, providing flexibility, end-to-end network slicing,
   and SLA control for various applications.

Working Group Summary

   The main issue during working group development was the document's
   intended track.  There was consensus to aim for PS, save for one
   objection.  Upon consultation with the 3GPP liaison from CT/CT4 it
   was decided that the document indeed had to be Informational
   (this was the reason for its 2nd IETF LC).

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?

   Yes, there are product implementations already.

                                 Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?

   Joel Halpern's concern about the intended track was borne out,
   and his concern prompted important communications with 3GPP
   that resulted in useful, decisive feedback.

   Lionel Morand's time and energy as liaison were essential to
   getting 3GPP's input on the document.  Suresh Krishnan helped
   coordinate relevant communications, many times.

   These folks, and all reviewers, are greatly appreciated.

Personnel

   Document Shepherd: Sri Gundavelli 
   Responsible Area Director: Erik Kline

IESG Note

   This document had two IETF Last Calls: one as PS (per the
   authors' desire) and a 2nd as Informational (per feedback
   from 3GPP liaison communications).

IANA Note

   The values defined by this document come from the FCFS portion
   of the "SRv6 Endpoint Behaviors" registry. There are placeholders
   entries already pointing to this draft.

RFC Editor Note