RFC 9015 on BGP Control Plane for the Network Service Header in Service Function Chaining
rfc-editor@rfc-editor.org Tue, 08 June 2021 23:06 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8CD3A0E3B; Tue, 8 Jun 2021 16:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I55YEhTG9aVS; Tue, 8 Jun 2021 16:06:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1AC3A0E27; Tue, 8 Jun 2021 16:06:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D0490F40721; Tue, 8 Jun 2021 16:05:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9015 on BGP Control Plane for the Network Service Header in Service Function Chaining
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210608230532.D0490F40721@rfc-editor.org>
Date: Tue, 08 Jun 2021 16:05:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FO5HWP5ALep04rayVBJQvwALP2Y>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2021 23:06:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9015
Title: BGP Control Plane for the
Network Service Header in Service Function
Chaining
Author: A. Farrel,
J. Drake,
E. Rosen,
J. Uttaro,
L. Jalil
Status: Standards Track
Stream: IETF
Date: June 2021
Mailbox: adrian@olddog.co.uk,
jdrake@juniper.net,
erosen52@gmail.com,
ju1738@att.com,
luay.jalil@verizon.com
Pages: 59
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-nsh-bgp-control-plane-18.txt
URL: https://www.rfc-editor.org/info/rfc9015
DOI: 10.17487/RFC9015
This document describes the use of BGP as a control plane for
networks that support service function chaining. The document
introduces a new BGP address family called the "Service Function
Chain (SFC) Address Family Identifier / Subsequent Address Family
Identifier" (SFC AFI/SAFI) with two Route Types. One Route Type is
originated by a node to advertise that it hosts a particular instance
of a specified service function. This Route Type also provides
"instructions" on how to send a packet to the hosting node in a way
that indicates that the service function has to be applied to the
packet. The other Route Type is used by a controller to advertise
the paths of "chains" of service functions and give a unique
designator to each such path so that they can be used in conjunction
with the Network Service Header (NSH) defined in RFC 8300.
This document adopts the service function chaining architecture
described in RFC 7665.
This document is a product of the BGP Enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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