Re: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-05.txt

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Fri, 16 June 2017 17:41 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5AFD129B39 for <idr@ietfa.amsl.com>; Fri, 16 Jun 2017 10:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Wdu31Iruu63r for <idr@ietfa.amsl.com>; Fri, 16 Jun 2017 10:41:44 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E739C12945F for <idr@ietf.org>; Fri, 16 Jun 2017 10:41:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7572; q=dns/txt; s=iport; t=1497634903; x=1498844503; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zflsSppYeY/PRFks18Xzfyg6RtcAM9qpCvRvrjJJNbE=; b=FLATcx3+LCFK7WoMA4YKWd49vusQTKVqlqCPhae0ERKTN1yKk9Auvytu 1BV7u7V9ojQGExMa8sLN2P1pqe4tdwy/489iMs5WalSHwPjedfMj5J6bM q+utg8OqVo6eJ+1nSU/IAZNn8EsvXyAGhNCubsWi3HECr4PdubpYK8XMH 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D0AAAUGERZ/40NJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0Hg2SEJYVzkVoilgeCESELhXgCGoJPPxgBAgEBAQEBAQF?= =?us-ascii?q?rHQuFGAEBAQECAQEBIRE6CwUHBAIBCBEBAwEBAQICIwMCAgIlCxQBAgYIAgQOB?= =?us-ascii?q?QmKGwgQqXiCJotCAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELhViBYCsLgm2DJoE?= =?us-ascii?q?VEgEcF4J7MIIxBZ5XAoctjCuCCFaEcYo/iR6CYYkGAR84fwt0FR8qEgGEehyBZ?= =?us-ascii?q?nYBh1SBI4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,348,1493683200"; d="scan'208";a="261798352"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Jun 2017 17:41:42 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v5GHfgEX003704 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 16 Jun 2017 17:41:42 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 16 Jun 2017 13:41:41 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Fri, 16 Jun 2017 13:41:41 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
CC: Susan Hares <shares@ndzh.com>, idr wg <idr@ietf.org>
Thread-Topic: I-D Action: draft-ietf-idr-bgp-prefix-sid-05.txt
Thread-Index: AQHSubxBjeliABb8XUKQwfepd4WDEKIn1ceggACJcgA=
Date: Fri, 16 Jun 2017 17:41:41 +0000
Message-ID: <8E574359-28FE-4812-BC66-BA859B67A88E@cisco.com>
References: <149268187426.22262.7793747029960844423@ietfa.amsl.com> <7F80FC76-81D7-46AF-9662-633FB769CDF8@cisco.com> <6066_1497620677_5943E0C5_6066_346_1_53C29892C857584299CBF5D05346208A47786DD4@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <6066_1497620677_5943E0C5_6066_346_1_53C29892C857584299CBF5D05346208A47786DD4@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.228.16]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FA216365820A9F4FB7389E84B1C922AE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/P6Ejyo3kOkR8wE3zm55UmVVTv1o>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-05.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jun 2017 17:41:47 -0000

Hi Bruno,

thanks for the comment. I’d propose following text:

      The Originator SRGB TLV contains the SRGB of the node 
      originating the prefix to which the BGP Prefix-SID is 
      attached. The Originator SRGB TLV MUST NOT be changed 
      during the propagation of the BGP update.

Let me know if address your concern.

Thanks.
s.



> On Jun 16, 2017, at 3:44 PM, bruno.decraene@orange.com wrote:
> 
> Hi Stefano,
>  
> Thanks for the updated version.
> -05 address my comments.
>  
> 1 possible nit.
> In §3.3, IMHO the (primary) goal is that the SRGB TLV must not be changed. Then that it should not be removed.
> I believe that the following change would better reflect the goal.
>  
> OLD:
>    The Originator SRGB TLV contains the SRGB of the node originating the
>    prefix to which the BGP Prefix-SID is attached and MUST be kept in
>    the Prefix-SID Attribute unchanged during the propagation of the BGP
>    update.
>  
> NEW:
>    The Originator SRGB TLV contains the SRGB of the node originating the
>    prefix to which the BGP Prefix-SID is attached and MUST be kept unchanged in
>    the Prefix-SID Attribute during the propagation of the BGP
>    update.
>  
> ---
> Possibly, what was really meant is “MUST NOT be changed”
>  
> Please feel free to silently drop this comment.
>  
> Regards,
> --Bruno
>  
> > -----Original Message-----
> > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Stefano Previdi (sprevidi)
> > Sent: Thursday, April 20, 2017 11:56 AM
> > To: idr wg
> > Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-prefix-sid-05.txt
> > 
>  > This is the updated version after comments from many reviews in IDR and SPRING.
> > 
>  > Note that section 3.2. "IPv6 SID” proposes now a new format for the IPv6 SID. It shouldn’t be
> > a problem since I don’t know any ipv6 implementations yet.
> > 
>  > Thanks.
> > s.
> > 
>  > > On Apr 20, 2017, at 11:51 AM, internet-drafts@ietf.org wrote:
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > > This draft is a work item of the Inter-Domain Routing of the IETF.
> > >
> > >        Title           : Segment Routing Prefix SID extensions for BGP
> > >        Authors         : Stefano Previdi
> > >                          Clarence Filsfils
> > >                          Acee Lindem
> > >                          Arjun Sreekantiah
> > >                          Hannes Gredler
> > >        Filename        : draft-ietf-idr-bgp-prefix-sid-05.txt
> > >        Pages           : 16
> > >        Date            : 2017-04-20
> > >
> > > Abstract:
> > >   Segment Routing (SR) architecture allows a node to steer a packet
> > >   flow through any topological path and service chain by leveraging
> > >   source routing.  The ingress node prepends a SR header to a packet
> > >   containing a set of segment identifiers (SID).  Each SID represents a
> > >   topological or a service-based instruction.  Per-flow state is
> > >   maintained only at the ingress node of the SR domain.
> > >
> > >   This document describes the BGP extension for announcing BGP Prefix
> > >   Segment Identifier (BGP Prefix-SID) information.
> > >
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-prefix-sid/
> > >
> > > There are also htmlized versions available at:
> > > https://tools.ietf.org/html/draft-ietf-idr-bgp-prefix-sid-05
> > > https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-prefix-sid-05
> > >
> > > A diff from the previous version is available at:
> > > https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-prefix-sid-05
> > >
> > >
> > > 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
> > 
>  > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> _________________________________________________________________________________________________________________________
> 
> 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.
>