[Teas] RFC 9543 on A Framework for Network Slices in Networks Built from IETF Technologies
rfc-editor@rfc-editor.org Tue, 12 March 2024 02:58 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43622C14CE40; Mon, 11 Mar 2024 19:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHS_2P-S2KCB; Mon, 11 Mar 2024 19:58:35 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10EE1C14F6A7; Mon, 11 Mar 2024 19:58:35 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id EE0A0191A4A3; Mon, 11 Mar 2024 19:58:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240312025834.EE0A0191A4A3@rfcpa.amsl.com>
Date: Mon, 11 Mar 2024 19:58:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/YZ9Wq16uPIGbB00aL8n6aNIo3oY>
Subject: [Teas] RFC 9543 on A Framework for Network Slices in Networks Built from IETF Technologies
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2024 02:58:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9543
Title: A Framework for Network Slices
in Networks Built from IETF Technologies
Author: A. Farrel, Ed.,
J. Drake, Ed.,
R. Rokui,
S. Homma,
K. Makhijani,
L. Contreras,
J. Tantsura
Status: Informational
Stream: IETF
Date: March 2024
Mailbox: adrian@olddog.co.uk,
je_drake@yahoo.com,
rrokui@ciena.com,
shunsuke.homma.ietf@gmail.com,
kiran.ietf@gmail.com,
luismiguel.contrerasmurillo@telefonica.com,
jefftant.ietf@gmail.com
Pages: 44
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-ietf-network-slices-25.txt
URL: https://www.rfc-editor.org/info/rfc9543
DOI: 10.17487/RFC9543
This document describes network slicing in the context of networks
built from IETF technologies. It defines the term "IETF Network
Slice" to describe this type of network slice and establishes the
general principles of network slicing in the IETF context.
The document discusses the general framework for requesting and
operating IETF Network Slices, the characteristics of an IETF Network
Slice, the necessary system components and interfaces, and the
mapping of abstract requests to more specific technologies. The
document also discusses related considerations with monitoring and
security.
This document also provides definitions of related terms to enable
consistent usage in other IETF documents that describe or use aspects
of IETF Network Slices.
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
Association Management Solutions, LLC