Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-14.txt
"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 20 December 2017 02:02 UTC
Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D5B124D85 for <isis-wg@ietfa.amsl.com>; Tue, 19 Dec 2017 18:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 AloKSxBRQm7v for <isis-wg@ietfa.amsl.com>; Tue, 19 Dec 2017 18:02:32 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F91F124234 for <isis-wg@ietf.org>; Tue, 19 Dec 2017 18:02:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8942; q=dns/txt; s=iport; t=1513735352; x=1514944952; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=WjVLkZMUww9tuxM8UyVBZWvYeEd/Dm/q8SsLSKFD2NY=; b=DaEuz6Qb++RQkQMlliG5oN+IA3ZCHorHKWksXyuOpeO2BKQcuQmW/d51 vwMUzAHNxj9LPABeY+U/pFrzQDQUY6zZkUKKndW2Ns6dhEpcx+x1Jq7sG 1ybBDRZYfAtVrEKstZcY+H0m6oBzdiAwRfQk1OQx/fYzQDRlwY5AduF+D k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DmAAAvxDla/4YNJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYM+ZnQnB4N/iiGPDIICiQSOIIIVChgLhRgCGoR0PxgBAQEBAQEBAQFrKIUjAQEBAQMBASEROhcEAgEIEQQBAQECAiMDAgICHwYLFAEICAIEARIIigsDFRClQoInhz8NgyYBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQ+CX4ISgVaBaAGDLIJrRAEBF4FAPIJwgmMFmV+JJj0Ch36IL4R1gh9lhTCLS40cPohyAhEZAYE6AR85gU9vFRgkgikJgkscgWd4iSeBFQEBAQ
X-IronPort-AV: E=Sophos;i="5.45,429,1508803200"; d="scan'208";a="46408058"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Dec 2017 02:02:31 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id vBK22Vw4014699 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Dec 2017 02:02:31 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 19 Dec 2017 20:02:30 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Tue, 19 Dec 2017 20:02:30 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Chris Bowers <chrisbowers.ietf@gmail.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-14.txt
Thread-Index: AQHTdctIc9jhS+q9iEqzMo6pDaCyC6NEsurggAb3ZID//9S2EA==
Date: Wed, 20 Dec 2017 02:02:30 +0000
Message-ID: <c372b425a82745c6a696e21f7682d65a@XCH-ALN-001.cisco.com>
References: <151335939850.30523.7213037938955532957@ietfa.amsl.com> <dd7879436a02406cb4c2576912bc42d5@XCH-ALN-001.cisco.com> <CAHzoHbvBCLkYHaTv+ts5ndgmBLw84RcazC0KiPR=hP-Ueq7AYQ@mail.gmail.com>
In-Reply-To: <CAHzoHbvBCLkYHaTv+ts5ndgmBLw84RcazC0KiPR=hP-Ueq7AYQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.131.19]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/Oxk3bLMSVejohd3JQOMWMpOEEU0>
Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-14.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 02:02:34 -0000
Chris - Thanx for the prompt review. I have posted a new version which addresses all of your comments. More inline. > -----Original Message----- > From: Chris Bowers [mailto:chrisbowers.ietf@gmail.com] > Sent: Tuesday, December 19, 2017 2:28 PM > To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; isis-wg@ietf.org > Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions- > 14.txt > > Les, > > Thanks for updating the text. Below are a few proposed changes/additions > to the current text that are mainly to clarify a few things. > > Thanks, > Chris > > ============= > 2.4.4. Mapping Server Prefix-SID > > The Prefix-SID sub-TLV (suggested value 3) is defined in Section 2.1 > and contains the SID/index/label value associated with the prefix and > range. The Prefix-SID SubTLV MUST be present in the SID/Label > Binding TLV. > > Proposed last sentence: > > The Prefix-SID Sub-TLV MUST be present in the SID/Label Binding TLV unless > the the M-flag is set in the Flags field of the parent TLV. > [Les:] Done > ============= > Existing text: > > The SID/Label sub-TLV may be present in the following TLVs/sub-TLVs > defined in this document: > > SR Capability (Section 3.1) > > SRLB (Section 3.3) > > Binding TLV (Section 2.4) > > MT Binding TLV (Section 2.5) > > Note that when used in the SR Capability and SRLB sub-TLVs the code > point used is the same as the sub-TLV code point assigned by IANA in > the sub-TLVs for TLV 149 and 150 registry. > > Proposed text: > > The SID/Label sub-TLV may be present in the following TLVs/sub-TLVs > defined in this document: > > SR-Capabilities Sub-TLV (Section 3.1) > > SR Local Block Sub-TLV (Section 3.3) > > SID/Label Binding TLV (Section 2.4) > > Multi-Topology SID/Label Binding TLV (Section 2.5) > > Note that the code point used for the SID/Label Sub-TLV in the SR- > Capabilities Sub-TLV and the SR Local Block sub-TLV is the same as the code > point used for the SID/Label Sub-TLV in the SID/Label Binding TLV and the > Multi-Topology SID/Label Binding TLV. This code point is assigned by IANA in > the “sub-TLVs for TLV 149 and 150” registry > [Les:] Done - though I reworded the last paragraph a bit. > =============== > 3.3. SR Local Block Sub-TLV > > (add after first paragraph) > The SR Local Block sub-TLV is inserted into the IS-IS Router Capability > TLV-242 that is defined in [RFC7981]. > > =============== > 3.3. SR Local Block Sub-TLV > > (add after first paragraph) > The SRMS Preference sub-TLV is inserted into the IS-IS Router Capability > TLV-242 that is defined in [RFC7981]. > [Les:] I added text in the parent section (3.) to indicate all the sub-TLVs described in the sub-sections are in the Router Capability TLV. > =============== > 5.3. Sub TLVs for Type 242 > … > Description: Segment Routing Local Base (SRLB) <<<< OLD > > Description: Segment Routing Local Block (SRLB) <<<< NEW > [Les:] Done Les > =============== > > On Fri, Dec 15, 2017 at 12:09 PM, Les Ginsberg (ginsberg) > <ginsberg@cisco.com> wrote: > > > > I have assumed the editor role from Stefano. > > > > This new version restores the support for SID/Label sub-TLV in the > SID/Label Binding TLV - needed to support Mirror Context (as requested by > Chris Bowers). > > It also addresses some IANA related issues - including the conflicting code > point w the MSD draft. > > > > Some other minor editorial changes have been made. > > > > Thanx. > > > > Les > > > > > > > -----Original Message----- > > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of > > > internet- drafts@ietf.org > > > Sent: Friday, December 15, 2017 9:37 AM > > > To: i-d-announce@ietf.org > > > Cc: isis-wg@ietf.org > > > Subject: [Isis-wg] I-D Action: > > > draft-ietf-isis-segment-routing-extensions- > > > 14.txt > > > > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > This draft is a work item of the IS-IS for IP Internets WG of the IETF. > > > > > > Title : IS-IS Extensions for Segment Routing > > > Authors : Stefano Previdi > > > Les Ginsberg > > > Clarence Filsfils > > > Ahmed Bashandy > > > Hannes Gredler > > > Stephane Litkowski > > > Bruno Decraene > > > Jeff Tantsura > > > Filename : draft-ietf-isis-segment-routing-extensions-14.txt > > > Pages : 34 > > > Date : 2017-12-15 > > > > > > Abstract: > > > Segment Routing (SR) allows for a flexible definition of end-to-end > > > paths within IGP topologies by encoding paths as sequences of > > > topological sub-paths, called "segments". These segments are > > > advertised by the link-state routing protocols (IS-IS and OSPF). > > > > > > This draft describes the necessary IS-IS extensions that need to be > > > introduced for Segment Routing operating on an MPLS data-plane. > > > > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-ext > > > ensions/ > > > > > > There are also htmlized versions available at: > > > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensio > > > ns-14 > > > https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routin > > > g- > > > extensions-14 > > > > > > A diff from the previous version is available at: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing- > > > extensions-14 > > > > > > > > > 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/ > > > > > > _______________________________________________ > > > Isis-wg mailing list > > > Isis-wg@ietf.org > > > https://www.ietf.org/mailman/listinfo/isis-wg > > > > _______________________________________________ > > Isis-wg mailing list > > Isis-wg@ietf.org > > https://www.ietf.org/mailman/listinfo/isis-wg
- [Isis-wg] I-D Action: draft-ietf-isis-segment-rou… internet-drafts
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Les Ginsberg (ginsberg)
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Jeff Tantsura
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Chris Bowers
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Les Ginsberg (ginsberg)
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Stewart Bryant
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Les Ginsberg (ginsberg)
- Re: [Isis-wg] I-D Action: draft-ietf-isis-segment… Stewart Bryant