[bess] Changes to draft-ietf-bess-nsh-bgp-control-plane-04.txt

"Adrian Farrel" <adrian@olddog.co.uk> Sun, 01 July 2018 12:20 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 CC72B130E79 for <bess@ietfa.amsl.com>; Sun, 1 Jul 2018 05:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 e8xPgDNKLyig for <bess@ietfa.amsl.com>; Sun, 1 Jul 2018 05:20:29 -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 E018A130E10 for <bess@ietf.org>; Sun, 1 Jul 2018 05:20:28 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id w61CKRjG031514 for <bess@ietf.org>; Sun, 1 Jul 2018 13:20:27 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C6FA52203A for <bess@ietf.org>; Sun, 1 Jul 2018 13:20:26 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id B21CC22032 for <bess@ietf.org>; Sun, 1 Jul 2018 13:20:26 +0100 (BST)
Received: from 950129200 ([88.128.81.183]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id w61CKOEK004129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bess@ietf.org>; Sun, 1 Jul 2018 13:20:25 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bess@ietf.org
Date: Sun, 01 Jul 2018 13:20:22 +0100
Message-ID: <03ef01d41135$e3590d30$aa0b2790$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdQRNdmA8/GcpUhgQPmIoLmgLs666A==
Content-Language: en-gb
X-Originating-IP: 88.128.81.183
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-23940.005
X-TM-AS-Result: No--13.673-10.0-31-10
X-imss-scan-details: No--13.673-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23940.005
X-TMASE-Result: 10--13.673000-10.000000
X-TMASE-MatchedRID: enoHDQRUzZFrtoObOqfJT1z+axQLnAVBYQXxsZnRwoKSeV7T1XnwPXkv YGlzSDgVTWLw2jvbfpzxP0/UCnihG7CTZx473DqJlVHM/F6YkvRyawdArtww50Yx760ONDcWGIe xdL6RBBF+cORUq46A1X7wZhseqbX08A4X1qvMzfVwUSK4/EeOxR83WxJo1IH1Blt4RZwvTdWoBV 9sc+TYxzNAuA6abqMjUJPgYUktHdBq4a4gnnHewcWUKBjERoYTJjlv06yk4fAR34ro7k23nWoT/ 9Y0Seqc6dW+yomUlT4OYLFb+3JssQ8rMzVfGoV9qbg9uWhLYLd1k+gP1XamtK8Jn6QfJT48pwp7 1wW2N27i8zVgXoAltlwtzewu2M63VkVZa47CjvDdB/CxWTRRu/558CedkGIvzP4Frv6e/e5vtgv XepLgC2DdF+ut4QhqXLRszMU9Y38yqaS1xVoTw37cGd19dSFd
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/LIhcs9o9S5vZVfm_oa8OVvGHfhI>
Subject: [bess] Changes to draft-ietf-bess-nsh-bgp-control-plane-04.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.26
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: Sun, 01 Jul 2018 12:20:31 -0000

Hi,

The changes can be seen in the diff and are mainly to address Yuanlong's
comments.

- 3.1.1 clarify text
- 3.2.1.2 clarify text and note two possible sub-TLVs of the Hop TLV
- 3.2.1.3 and 3.2.1.4 split into two sub-TLVs and explain their use
- 10.3 fix up IANA section per 3.2.1.3/4
- 12 add Yuanlong
- 13.2 update references
- Typos

Cheers,
Adrian

> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 01 July 2018 09:30
> To: i-d-announce@ietf.org
> Cc: bess@ietf.org
> Subject: I-D Action: draft-ietf-bess-nsh-bgp-control-plane-04.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 NSH SFC
>         Authors         : Adrian Farrel
>                           John Drake
>                           Eric Rosen
>                           Jim Uttaro
>                           Luay Jalil
> 	Filename        : draft-ietf-bess-nsh-bgp-control-plane-04.txt
> 	Pages           : 55
> 	Date            : 2018-07-01
> 
> 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-04
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-04
> 
> 
> 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