Re: [spring] I-D Action: draft-ietf-spring-segment-routing-msdc-07.txt

<bruno.decraene@orange.com> Thu, 21 December 2017 14:05 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B92212D7F7; Thu, 21 Dec 2017 06:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level:
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 OexrPkdBn3nd; Thu, 21 Dec 2017 06:05:17 -0800 (PST)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1E0B127078; Thu, 21 Dec 2017 06:05:16 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 484C120A41; Thu, 21 Dec 2017 15:05:15 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.33]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 25F45120087; Thu, 21 Dec 2017 15:05:15 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0361.001; Thu, 21 Dec 2017 15:05:14 +0100
From: bruno.decraene@orange.com
To: "draft-ietf-spring-segment-routing-msdc@ietf.org" <draft-ietf-spring-segment-routing-msdc@ietf.org>
CC: "spring@ietf.org" <spring@ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-segment-routing-msdc-07.txt
Thread-Index: AQHTeKahshRyKAHV/U2nSlhXAwGgU6NNqDoA
Date: Thu, 21 Dec 2017 14:05:14 +0000
Message-ID: <13708_1513865115_5A3BBF9B_13708_176_1_53C29892C857584299CBF5D05346208A479298D4@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151367351502.7415.8457234964917496618@ietfa.amsl.com>
In-Reply-To: <151367351502.7415.8457234964917496618@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/4C0gVm9xxY35KaHNtMWdgJJqnes>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-msdc-07.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 14:05:21 -0000

Hi authors,

Thanks for the updated draft and having updated draft-ietf-mpls-rfc3107bis with RFC 8277 in section 4.2 "eBGP"
Could you apply the same change in section  4.3 "iBGP" ? i.e.
OLD: iBGP Labeled Unicast (draft-ietf-mpls-rfc3107bis)
NEW: iBGP Labeled Unicast (RFC8277)

Nothing urgent on my side.


Nits:
"The BGP-Prefix-SID is a lightweight extension to BGP Labeled Unicast  (RFC8277 [RFC8277])."
Probably, one reference to RFC 8277 is enough.

 > -----Original Message-----
 > From: spring [mailto:spring-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
 > Sent: Tuesday, December 19, 2017 9:52 AM
 > To: i-d-announce@ietf.org
 > Cc: spring@ietf.org
 > Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-msdc-07.txt
 > 
 > 
 > A New Internet-Draft is available from the on-line Internet-Drafts directories.
 > This draft is a work item of the Source Packet Routing in Networking WG of the IETF.
 > 
 >         Title           : BGP-Prefix Segment in large-scale data centers
 >         Authors         : Clarence Filsfils
 >                           Stefano Previdi
 >                           Jon Mitchell
 >                           Ebben Aries
 >                           Petr Lapukhov
 > 	Filename        : draft-ietf-spring-segment-routing-msdc-07.txt
 > 	Pages           : 24
 > 	Date            : 2017-12-19
 > 
 > Abstract:
 >    This document describes the motivation and benefits for applying
 >    segment routing in BGP-based large-scale data-centers.  It describes
 >    the design to deploy segment routing in those data-centers, for both
 >    the MPLS and IPv6 dataplanes.
 > 
 > 
 > The IETF datatracker status page for this draft is:
 > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-msdc/
 > 
 > There are also htmlized versions available at:
 > https://tools.ietf.org/html/draft-ietf-spring-segment-routing-msdc-07
 > https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-msdc-07
 > 
 > A diff from the previous version is available at:
 > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-msdc-07
 > 
 > 
 > 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/
 > 
 > _______________________________________________
 > spring mailing list
 > spring@ietf.org
 > https://www.ietf.org/mailman/listinfo/spring

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.