Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 07 March 2018 20:56 UTC

Return-Path: <ginsberg@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 704E11277BB for <idr@ietfa.amsl.com>; Wed, 7 Mar 2018 12:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 rmC7KqEV1RT4 for <idr@ietfa.amsl.com>; Wed, 7 Mar 2018 12:56:16 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23E93126B6D for <idr@ietf.org>; Wed, 7 Mar 2018 12:56:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8760; q=dns/txt; s=iport; t=1520456176; x=1521665776; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=KQk8pqxMB58qQOS6jJIpsC7wM6a3W4IEmoSPX1SiDd0=; b=At/I5o4U/+3MLf9VDCdAKOY8c+OBsj6n6slWK2FVPSXyy1y81JP6xXky 5WbUIcPsfJJnaxPz6W9GImJ5WFSNHu9yKrDViKWm/IBTvBzJv5GlRnYx1 VjG68q0FP3WOQs40FmiQZ0WOqeT3PT9lQVHa9Lp0qOhiPqDchoy19E1Dx w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CzAgDUUKBa/5NdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJaSS1mcCgKm2mCAoEWjxGFIxSCAQolhQsCgwohNRcBAgEBAQE?= =?us-ascii?q?BAQJrJ4UjAQEBBC1cAgEIDgMEAQEoBzIUCQgBAQQBEgiEL2QQqHKCcFuIZ4IcB?= =?us-ascii?q?YUygi6BV4UTgUeBZwIDAYEwc4U3BJpnCQKGUoohgXGEN4hciX6HLAIRGQGBLQE?= =?us-ascii?q?fATaBUnAVgn2CY24BCG53iT6BL4EYAQEB?=
X-IronPort-AV: E=Sophos; i="5.47,437,1515456000"; d="scan'208,217"; a="80727634"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2018 20:56:15 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w27KuF6A015580 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Mar 2018 20:56:15 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 7 Mar 2018 14:56:14 -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; Wed, 7 Mar 2018 14:56:14 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Susan Hares <shares@ndzh.com>, "'idr wg'" <idr@ietf.org>
Thread-Topic: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)
Thread-Index: AdO2MgZujpRAsp7XQFKnjQkuXD65bwAJCtmA
Date: Wed, 7 Mar 2018 20:56:14 +0000
Message-ID: <8b887c20515b4eaeaa418640dd1ba5b8@XCH-ALN-001.cisco.com>
References: <011201d3b633$0b5fee60$221fcb20$@ndzh.com>
In-Reply-To: <011201d3b633$0b5fee60$221fcb20$@ndzh.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.24.71.196]
Content-Type: multipart/alternative; boundary="_000_8b887c20515b4eaeaa418640dd1ba5b8XCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/R0y8qcnFoo9u45gd5v6HMClbg2g>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)
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: Wed, 07 Mar 2018 20:56:18 -0000

Support

BGP-LS is a key element of routing deployments today - and Segment Routing is a technology which is deployed and adoption is increasing. It is therefore obvious that BGP should carry this information.

I have followed/reviewed this draft over its multiple revisions and I believe it is mature and ready for publication.

   Les


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, March 07, 2018 8:41 AM
To: 'idr wg' <idr@ietf.org>
Subject: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04.txt from March 7th to March 21.  During your discussion in the WG LC, please indicate the following things:


1)      Do you think BGP should carry these link state information regarding segment routing,

2)      Are there any technical issues with this draft?

3)      Is this draft is ready for publication?

For your quick access to this draft, click on the link below:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext/


Susan Hares