IETF Logo Mail Archive

Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-15.txt

Adrian Farrel <adrian@olddog.co.uk> Mon, 15 June 2020 13:24 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89BE73A0D77 for <bess@ietfa.amsl.com>; Mon, 15 Jun 2020 06:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 6PjuOr0zqaed for <bess@ietfa.amsl.com>; Mon, 15 Jun 2020 06:24:26 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 AC03B3A0D76 for <bess@ietf.org>; Mon, 15 Jun 2020 06:24:25 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05FDONA3022712 for <bess@ietf.org>; Mon, 15 Jun 2020 14:24:23 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 86EF422044 for <bess@ietf.org>; Mon, 15 Jun 2020 14:24:22 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id 7BF002203D for <bess@ietf.org>; Mon, 15 Jun 2020 14:24:22 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 05FDOKAT022539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <bess@ietf.org>; Mon, 15 Jun 2020 14:24:21 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bess@ietf.org
References: <159222269682.15783.5238920674974309758@ietfa.amsl.com>
In-Reply-To: <159222269682.15783.5238920674974309758@ietfa.amsl.com>
Date: Mon, 15 Jun 2020 14:24:19 +0100
Organization: Old Dog Consulting
Message-ID: <00f801d64318$471ae7b0$d550b710$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJLQkjCmguLSRTN6dheE6VuTpW5WKfvqbEw
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-25482.007
X-TM-AS-Result: No--16.671-10.0-31-10
X-imss-scan-details: No--16.671-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25482.007
X-TMASE-Result: 10--16.671200-10.000000
X-TMASE-MatchedRID: PL66URbwWA9or4mPA3EMtnFPUrVDm6jtyBEE5Ydf0DFs98Z8fG/6kSKV DmbphIrbQIrDavfhGmy/CzyEMgUVo+yt+a9Mtf+esgYw1+LBrk15j2Sw+Nvsaw/vnJWZIdGAWmr Yr8SaWTVHSYz7tSK8WlJ9oM1UkvlK5a9YaFWBWfSSvRb8EMdYRd1eFEoaE12na/z+7VNQGK4RLH A2u6cHsp9NxqRbsrdJpt3L5VFqVtu29wQgZg1df8+Qb/9oChYJq1xz4AyB7S1YjtHrjqa8D1CW8 ig4Qr2JtUYbbbDctpTWlAxinuN4atkxaR8QXcVv8Otj0KvfR1kfqkfNzTRFShboQu7Fla5XIQwd t8FiOhRM+fB+KW5xPlej7nRZhIz4HlnRzQXcZk2InASnzB5VfJhwKdlCfPk8DO+DX+rUwfbBk2U V37fBLFpV4aaUhGMYkBAw5x9XDqqPl8suWHSuVOqq/TX+iM8Te24VF0CecQWbKItl61J/ycnjLT A/UDoAnL8I93XanomH15aeUvXHwN0H8LFZNFG7/nnwJ52QYi8hem0kmpPZMQ==
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/bess/kFcrZo1V9ZUvMIeZyk3XLpEIaHg>
Subject: Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-15.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 15 Jun 2020 13:24:28 -0000

BESS,

This revision adopts the text and registry change as just discussed on list
with Ketan.

Thanks,
Adrian

-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
internet-drafts@ietf.org
Sent: 15 June 2020 13:05
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Subject: I-D Action: draft-ietf-bess-nsh-bgp-control-plane-15.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-15.txt
	Pages           : 69
	Date            : 2020-06-15

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-15
https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-
15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-15


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/


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

v2.23.0 | Report a Bug | By Email