[bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-01.txt
internet-drafts@ietf.org Mon, 25 September 2017 17:21 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1052C134512; Mon, 25 Sep 2017 10:21:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150636010301.27379.11556033271374219463@ietfa.amsl.com>
Date: Mon, 25 Sep 2017 10:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/O5Ca835vhPZVHth-xFgWsGD4izA>
Subject: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-01.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 17:21:43 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : BGP Control Plane for NSH SFC Authors : Adrian Farrel John Drake Eric Rosen Jim Uttaro Luay Jalil Filename : draft-ietf-bess-nsh-bgp-control-plane-01.txt Pages : 52 Date : 2017-09-25 Abstract: This document describes the use of BGP as a control plane for networks that support Service Function Chaining (SFC). The document introduces a new BGP address family called the 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 to give a unique designator to each such path so that they can be used in conjunction with the Network Service Header. This document adopts the SFC architecture described in RFC 7665. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-bess-nsh-bgp-control-plane-01 https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [bess] I-D Action: draft-ietf-bess-nsh-bgp-contro… internet-drafts
- Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-co… Adrian Farrel