[sfc] New version of draft-ietf-bess-nsh-bgp-control-plane

Adrian Farrel <adrian@olddog.co.uk> Tue, 02 June 2020 16:44 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8D13A0C99 for <sfc@ietfa.amsl.com>; Tue, 2 Jun 2020 09:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 xlvVkWH34QuN for <sfc@ietfa.amsl.com>; Tue, 2 Jun 2020 09:44:10 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B0F3A0C97 for <sfc@ietf.org>; Tue, 2 Jun 2020 09:44:10 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 052Gi80J006763 for <sfc@ietf.org>; Tue, 2 Jun 2020 17:44:08 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5FEE222040 for <sfc@ietf.org>; Tue, 2 Jun 2020 17:44:08 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id 4AEED2203C for <sfc@ietf.org>; Tue, 2 Jun 2020 17:44:08 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 052Gi7Sn015429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <sfc@ietf.org>; Tue, 2 Jun 2020 17:44:07 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: sfc@ietf.org
Date: Tue, 02 Jun 2020 17:44:05 +0100
Organization: Old Dog Consulting
Message-ID: <042101d638fd$07f6e270$17e4a750$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdY4/KvSKubp6JgvSDKfhj9f1pOdpA==
Content-Language: en-gb
X-Originating-IP: 84.93.26.18
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25458.001
X-TM-AS-Result: No--26.976-10.0-31-10
X-imss-scan-details: No--26.976-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25458.001
X-TMASE-Result: 10--26.975800-10.000000
X-TMASE-MatchedRID: tIBWMHlNqVMsO+kVEfVuQoicBKfMHlV8pQH4ogtVQP0S39b8+3nDx4RS ZST9rmfiSMQbWc3fWqqkK5deTcbImPa9Ixfq9T3YsrmINHJ4yALIEQTlh1/QMV2YKfSY6fzMSHg UVMoIv2HTFeWcNFHhRV7LYHGSSpoCam2DS6xi1qC8coKUcaOOvQ73P4/aDCIFIFWQH/JudNgilQ 5m6YSK201i8No7236cNYYFTQ0sf/dGmitRUBp4l5VRzPxemJL0mAQwMiIyxlRGMe+tDjQ3Foj3p UNN3tP6gSA7jvhGUu4sqm30ya4QYfMJ6Vofe2DKdhnFihmbnwWCxDtmOm10/8xzM8CbVIFINiiX NOko0Fuar39byU2evL73xG6zBNMf7D3wIFP3sNXTK3Menen4ltFTR6mnbN4LSnXYhdlqPHnqtxV PkBgBSdet3zya7vpkR4JSZpR2k/YVZKEn/wWg12pno6KlGnd6rO1NBP3Ts3xJfyfUaPjAAWhyGR geI0RKk/Tq9ZYJJP9/t5tveyBGEJuHU2C1DeL3B89GKHo03nbXvCCuWFhuDpsoi2XrUn/Jsuf7R WbvUtze3/9uSSiAvlOm2gN+nomsxEHRux+uk8irEHfaj14ZyVVoEXK0hBS3
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/d75-56qoM9SguiElpI5nEnB-qBo>
Subject: [sfc] New version of draft-ietf-bess-nsh-bgp-control-plane
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2020 16:44:13 -0000

Hi SFC WG,

Just a note to let you know that we've made a new version of this draft.

We've been responding to various IESG Discusses and Comments, and to the Routing Directorate review for this draft. You can see the exchanges on the BESS list.

This revision makes all of the associated changes. There is a fairly high level of change, but we believe that the changes are not very substantive.

Please take some time to look at the diffs and shout if anything is alarming or unclear.

Many thanks,
Adrian
 
> -----Original Message-----
> From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
> internet-drafts@ietf.org
> Sent: 02 June 2020 09:05
> To: i-d-announce@ietf.org
> Cc: bess@ietf.org
> Subject: I-D Action: draft-ietf-bess-nsh-bgp-control-plane-14.txt
> 
> 
> 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 the Network Service Header
> in Service Function Chaining
>          Authors         : Adrian Farrel
>                            John Drake
>                            Eric Rosen
>                            Jim Uttaro
>                            Luay Jalil
> 	Filename        : draft-ietf-bess-nsh-bgp-control-plane-14.txt
> 	Pages           : 68
> 	Date            : 2020-06-02
> 
> 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 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 to give a unique designator to each such path so that they can be
>     used in conjunction with the Network Service Header defined in RFC
>     8300.
> 
>     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-14
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-
> 14
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-14
> 
> 
> 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/