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

"Adrian Farrel" <> Sat, 12 January 2019 16:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C558412426E for <>; Sat, 12 Jan 2019 08:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SAEfoaHBUTgJ for <>; Sat, 12 Jan 2019 08:51:08 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 128B1124BAA for <>; Sat, 12 Jan 2019 08:51:07 -0800 (PST)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id x0CGp5Au002681 for <>; Sat, 12 Jan 2019 16:51:05 GMT
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id C73982203B for <>; Sat, 12 Jan 2019 16:51:02 +0000 (GMT)
Received: from (unknown []) by (Postfix) with ESMTPS id AC04E2203A for <>; Sat, 12 Jan 2019 16:51:02 +0000 (GMT)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id x0CGp1qX016344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <>; Sat, 12 Jan 2019 16:51:02 GMT
From: Adrian Farrel <>
References: <>
In-Reply-To: <>
Date: Sat, 12 Jan 2019 16:50:59 -0000
Organization: Old Dog Consulting
Message-ID: <04a901d4aa96$ff283b30$fd78b190$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQGYq9CqFfnn9gn/qH8R8QxypO0laKYj00jA
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--7.713-10.0-31-10
X-imss-scan-details: No--7.713-10.0-31-10
X-TMASE-Result: 10--7.712600-10.000000
X-TMASE-MatchedRID: X4bcv0S75KnxIbpQ8BhdbAqS/NVvA9Zc5IGsYdjJ9roLCC+rIG9+ZVRI BHtnMvWEW7Iq1ViQZjERgDSy6nqA2GResrHRY7dKzNY33yIEF4ZHRJfU7CVkWuzNIeey9vjBWKo DKTsuRuR1L+X18ZczPR/Ne6ZdAvcMkg6GA5mI8yxnV/5dB3nNz/x3eAlFiEvxut/GVGOoEnfWk2 S49P8eb3F7+YArNpT4ArcMPwv93rRwnCnLeerTqjnI52876vPfQ95F2IiVUkSSp2BlHLFDYZdED nskDq+Wf/+tBCjs2R8XfgaNHLcVwRLzzuWmRrvbvHKClHGjjr0hmbYg1ZcOnmTYnZ5/c13f9Os/ l7x5zsG36h2hK5rvdpGTpe1iiCJqtD9qpBlNF8qWwBC0tiSzK4tkBWmEtb9tKrauXd3MZDUMFsa +1wyh/J6o5I6sWshh3xY9rJoCmPi+Rh4gqeDyuYtJBH5re2WuxX6VHga8v1Q=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-05.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 12 Jan 2019 16:51:11 -0000

Hello all and Happy New Year,

This version replaces the expired draft, fixes a few nits, adds a few
clarifications, and backs out a couple of small and unnecessary changes
introduced in -04.

The authors think that this version is ready for the chairs to review and
start working group last call.


-----Original Message-----
From: BESS <> On Behalf Of
Sent: 12 January 2019 14:30
Subject: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts
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-05.txt
	Pages           : 54
	Date            : 2019-01-12

   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:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

BESS mailing list