Internet-Draft SRH TLVs for 3GPP Mobility November 2026
Horn Expires 19 May 2027 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-horn-dmm-srh-3gpp-mobility-tlv-00
Published:
Intended Status:
Standards Track
Expires:
Author:
J. Horn
Cisco Systems

Segment Routing Header TLVs for 3GPP Mobility Metadata

Abstract

This document requests two Segment Routing Header (SRH) TLV codepoints. Both are containers for mobility metadata used by 3GPP user-plane functions. One does not change en route. The other may change en route. This document specifies the framing so that any Segment Routing node can skip either container. Sub-TLV types and their meaning are under 3GPP change control. Neither container changes IPv6 forwarding.

Note to Readers

This note is to be removed before publishing as an RFC.

This document is an individual submission. Comments are invited from the SPRING and DMM working groups.

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 19 May 2027.

▲

Table of Contents

1. Introduction

The Segment Routing Header (SRH) [RFC8754] carries optional TLVs for the segment endpoint identified by the active Segment Identifier (SID). TLV types 0 through 127 do not change en route. Types 128 through 255 may change en route. The registry policy is IETF Review.

A 3GPP user-plane function that uses SRv6 [RFC9433] can need per-packet session metadata at that endpoint. Some of that metadata is fixed by the SR source. Some of it is updated by a 3GPP function at a segment endpoint along the path. The metadata is not a forwarding instruction, and the set of information elements changes on the 3GPP release cycle. One SRH TLV type per information element would consume a registry shared by every SRv6 deployment and would require IETF Review for each addition.

This document specifies two containers with one common framing. The 3GPP Mobility Container TLV does not change en route, and its codepoint is requested from the range 7 through 123. The 3GPP Mobility Mutable Container TLV may change en route inside a size the SR source pre-allocates, and its codepoint is requested from the range 128 through 251. That size does not change en route. Each value is a sequence of sub-TLVs. This document defines how those sub-TLVs are delimited. 3GPP specifications assign the Sub-Type values of each container and define each Value. A Sub-Type in one container has no meaning in the other unless a 3GPP specification says so. This document creates no IANA registry for Sub-Types. The IETF does not assign Sub-Type meanings.

Both containers are used inside a limited domain [RFC8402] that includes the 3GPP functions which place them in an SRH and consume them. They are carried only in an IPv6 SRH, Routing Type 4. They do not change the Segment List, the SRH Flags, or the SRH Tag.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. Container Format

Both TLVs use the format in this section. Alignment requirement: 4n, measured from the start of the SRH as specified in [RFC8754]. The SR source uses Pad1 and PadN for alignment and to keep the Routing Header a multiple of 8 octets.

An SRH contains at most one TLV of each type. The SR source does not place a TLV of either type in the SRH when that TLV would contain no sub-TLV. The value contains only sub-TLVs, with no version field, flags field, or padding between them.

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|      Type     |     Length    |         Sub-TLVs ...          |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type:
8 bits. One of the two values allocated under Section 5. The 3GPP Mobility Container TLV is allocated from the range 0 through 127. The 3GPP Mobility Mutable Container TLV is allocated from the range 128 through 255.
Length:
8 bits. Number of octets in Sub-TLVs, excluding Type and Length. The maximum is 255. Length equals the sum, over every sub-TLV, of (2 + Sub-Length), and is not 0.

Each sub-TLV has this format:

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    Sub-Type   |   Sub-Length  |         Value ...             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
8 bits. Assigned by a 3GPP specification for the container in which it appears. This document assigns no value. All 256 values of each container are available to 3GPP.
Sub-Length:
8 bits. Number of octets in Value, excluding Sub-Type and Sub-Length. Zero is syntactically valid.
Value:
Sub-Length octets, interpreted only under the 3GPP specification of this Sub-Type.

4. Processing

Forwarding MUST NOT depend on the presence or contents of either container. A node MUST NOT add or remove either container in flight, and MUST NOT modify the 3GPP Mobility Container TLV in flight. The SR source pre-allocates the 3GPP Mobility Mutable Container TLV and sets its Length. A consumer MAY rewrite octets inside that pre-allocated value as specified by 3GPP. The rewrite MUST leave a valid sequence of sub-TLVs that occupies exactly that Length. The consumer MUST NOT change Length and MUST NOT add or remove octets. The size of the mutable container therefore does not grow or otherwise change en route. Every node that is not that consumer MUST NOT modify the mutable container.

The SR source sets Type to the allocated codepoint of each container and places each container in the TLV area of the SRH, with Hdr Ext Len and Last Entry set as specified in [RFC8754], Section 2.1. When either container is present, the SR source pushes an SRH even for a single SID, and includes that SID in the Segment List, so the start of the TLV area is unambiguous. Each endpoint that reads or modifies a container still has the SRH when its SID is the Destination Address.

A segment endpoint processes a container only when local configuration identifies the active SID as a consumer, which is the same gate [RFC8754] defines for SRH TLVs. Every other node ignores the TLV.

A consumer walks the sub-TLVs of each container it is configured to process. A container is malformed if it is not fully contained in the SRH, if more than one TLV of that type is present, if Length is 0, if the sub-TLV sequence does not fill Length exactly, or if a recognized Sub-Type has a Sub-Length that its 3GPP specification rejects. A consumer discards a packet that contains a malformed container. It SHOULD send an ICMP Parameter Problem, Code 0, rate-limited, as specified for an SRH TLV error in [RFC8754], so the source can diagnose the discard. The packet is discarded whether or not the ICMP message is sent. The Pointer identifies Hdr Ext Len when the TLV exceeds the SRH, and otherwise the Type octet of the malformed container.

The consumer MUST skip an unrecognized Sub-Type by Sub-Length and MUST continue. It MUST NOT discard the packet only because a Sub-Type is unknown. It applies each recognized sub-TLV as specified by 3GPP. It MUST NOT use a sub-TLV to change the Destination Address, the Segment List, or the endpoint behavior of the active SID. A sub-TLV MAY affect local handling of the payload at the consumer, including quality-of-service treatment, when the 3GPP specification of that Sub-Type says so.

5. IANA Considerations

IANA is requested to allocate two values from the "Segment Routing Header TLVs" registry:

Table 1
Value Description Reference
TBA-1 3GPP Mobility Container TLV This document
TBA-2 3GPP Mobility Mutable Container TLV This document

TBA-1 is allocated from the unassigned values in 7 through 123. TBA-2 is allocated from the unassigned values in 128 through 251. No sub-TLV registry is requested. IANA is requested to note on each registration, if the registry allows a note: "Sub-TLV types inside this TLV are assigned by 3GPP specifications and are not registered by IANA."

6. Security Considerations

Both containers are for use inside a limited domain [RFC8402]. The security considerations of [RFC8754] and [RFC8402] apply. The HMAC TLV defined in [RFC8754] does not cover other SRH TLVs, so a successful HMAC check does not authenticate either container. A consumer may rewrite the contents of the mutable container. The size remains the size the SR source pre-allocated. This document defines no cryptographic algorithm, key, or certificate. A deployment that needs integrity or confidentiality of the metadata uses a mechanism that covers these octets, such as IPsec inside the limited domain.

Neither container changes the IPv6 path, as specified in Section 4. Values are visible to nodes that can read the SRH. A 3GPP specification that places a session identifier in a Value needs to account for that visibility, and for the fact that a consumer may rewrite the mutable container.

7. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8754]
Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header (SRH)", RFC 8754, DOI 10.17487/RFC8754, , <https://www.rfc-editor.org/rfc/rfc8754>.

8. Informative References

[RFC8402]
Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., Decraene, B., Litkowski, S., and R. Shakir, "Segment Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, , <https://www.rfc-editor.org/rfc/rfc8402>.
[RFC9433]
Matsushima, S., Ed., Filsfils, C., Kohno, M., Camarillo, P., Ed., and D. Voyer, "Segment Routing over IPv6 for the Mobile User Plane", RFC 9433, DOI 10.17487/RFC9433, , <https://www.rfc-editor.org/rfc/rfc9433>.

Author's Address

Jakub Horn
Cisco Systems
Milpitas, CA 95035
United States of America