IETF Logo Mail Archive

Re: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext prior to WG LC (7/17 - 7/31)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 19 October 2017 19:11 UTC

Return-Path: <ketant@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 48A68132D89 for <idr@ietfa.amsl.com>; Thu, 19 Oct 2017 12:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Z3zGiQH1acMj for <idr@ietfa.amsl.com>; Thu, 19 Oct 2017 12:11:34 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A51C61321C7 for <idr@ietf.org>; Thu, 19 Oct 2017 12:11:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10347; q=dns/txt; s=iport; t=1508440294; x=1509649894; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=NrK6cP8HsRic7uYDw3sAydqQm9yuBVi71A9IacbmuBs=; b=f/kcHzXYfj9wb1O25NOtL+2MSFlmlwHdKyu1O9iZwaaIsSnrF0SAQN7y +CgYLEtdmg0LBsAheFtST+ea3bQBc+V4GwnNaFg82NqHTujrhIqqqUSH0 RjqH/DBOfNUpCghPrrpGDOBk0orHyrlV1+nWD6HTj+j0o8sKi25LiTDS2 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CzAAAT+OhZ/5JdJa1dGQEBAQEBAQEBAQEBBwEBAQEBgm9wZG4nB44Sjz+BenuPeYU/ghQKJYUWAoULPxgBAgEBAQEBAQFrKIUdAQEBBC1MEAIBCBEEAQEoBzIUCQgBAQQBDQUIiTRkEK1eiyEBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMvggeBUYFqgnk1hTuFPwWhUwKHX40Fgh2FdosPiiOLJAIRGQGBOAEfOIFbehWDLYMRgU52iVWBEQEBAQ
X-IronPort-AV: E=Sophos;i="5.43,402,1503360000"; d="scan'208,217";a="309876606"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2017 19:11:32 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v9JJBWRK002053 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Oct 2017 19:11:32 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 19 Oct 2017 14:11:32 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Thu, 19 Oct 2017 14:11:32 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "John G. Scudder" <jgs@juniper.net>, "idr@ietf. org" <idr@ietf.org>
CC: Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext prior to WG LC (7/17 - 7/31)
Thread-Index: AdL+34j1x/OxqugKRpega2ZuoyB6nBKJHd8AAAJe85A=
Date: Thu, 19 Oct 2017 19:11:32 +0000
Message-ID: <2819c675344d464bbcb356541c19732c@XCH-ALN-008.cisco.com>
References: <001f01d2fee0$11747560$345d6020$@ndzh.com> <A4F39AB4-B449-4ED1-8F56-122EDC5B4C8A@juniper.net>
In-Reply-To: <A4F39AB4-B449-4ED1-8F56-122EDC5B4C8A@juniper.net>
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.65.86.22]
Content-Type: multipart/alternative; boundary="_000_2819c675344d464bbcb356541c19732cXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fEPvB2ziPTCjyQgJ8Tg-lGzyRB4>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext prior to WG LC (7/17 - 7/31)
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: Thu, 19 Oct 2017 19:11:36 -0000

Hi John/Sue,

Apologies for missing the WGLC on this document. There is definitely interest and multiple implementations. In course of concurrent discussions related to the IANA early allocations, the WGLC perhaps got missed by multiple folks.


In the meantime, I've update implementation record at the wiki below - https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-ext-implementations

Would request others to also review/update and I hope we can redo the WGLC sometime soon.

Thanks,
Ketan

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of John G. Scudder
Sent: 19 October 2017 18:29
To: idr@ietf. org <idr@ietf.org>
Cc: Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-segment-routing-ext prior to WG LC (7/17 - 7/31)

Hi All,

I see that we never formally closed this WGLC.

Since there were no replies at all to the WGLC, there is no consensus to advance the document. Presumably there is still interest in it, considering we were asked for -- and provided -- early allocations, subsequent to the WGLC. So, I guess the WG should reconsider the WGLC in the future, after we've processed the other outstanding WGLCs in our queue.

--John

On Jul 17, 2017, at 12:35 PM, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:

This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext from 7/17/17 to 7/31/17.  You can obtain the draft at:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext/

In your discussions, please indicate if you believe this draft is ready for publication.  Also, it would be helpful to know if have experience with any of the implementations of this draft.

Sue Hares and John Scuder

v2.23.0 | Report a Bug | By Email