RFC 9889 on A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies
rfc-editor@rfc-editor.org Wed, 05 November 2025 22:47 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AC66283F27F1; Wed, 5 Nov 2025 14:47:30 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 7691DC000CCC; Wed, 5 Nov 2025 14:47:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9889 on A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251105224730.7691DC000CCC@rfcpa.rfc-editor.org>
Date: Wed, 05 Nov 2025 14:47:30 -0800
Message-ID-Hash: LNNCSMFI3C6NV6YNLK7SB7AZM7PDDPWE
X-Message-ID-Hash: LNNCSMFI3C6NV6YNLK7SB7AZM7PDDPWE
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teas@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/KjAn_FqhtGQGKIo-whhalPe6xOQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9889
Title: A Realization of Network Slices for
5G Networks Using Current IP/MPLS Technologies
Author: K. Szarkowicz, Ed.,
R. Roberts, Ed.,
J. Lucek,
M. Boucadair, Ed.,
LM. Contreras
Status: Informational
Stream: IETF
Date: November 2025
Mailbox: kszarkowicz@juniper.net,
richard.roberts@nokia.com,
jlucek@juniper.net,
mohamed.boucadair@orange.com,
luismiguel.contrerasmurillo@telefonica.com
Pages: 68
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-5g-ns-ip-mpls-18.txt
URL: https://www.rfc-editor.org/info/rfc9889
DOI: 10.17487/RFC9889
Network slicing is a feature that was introduced by the 3rd
Generation Partnership Project (3GPP) in Mobile Networks. Realization
of 5G slicing implies requirements for all mobile domains, including
the Radio Access Network (RAN), Core Network (CN), and Transport
Network (TN).
This document describes a network slice realization model for IP/MPLS
networks with a focus on the Transport Network fulfilling the service
objectives for 5G slicing connectivity. The realization model reuses
many building blocks commonly used in service provider networks at
the current time.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team