Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-node-admin-tag-extension-01 (6/14/2017 to 6/28/2017)

"Susan Hares" <shares@ndzh.com> Fri, 16 June 2017 18:57 UTC

Return-Path: <shares@ndzh.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 F2632127863; Fri, 16 Jun 2017 11:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 5UBT0k2jhf1Q; Fri, 16 Jun 2017 11:57:38 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD990127011; Fri, 16 Jun 2017 11:57:37 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.176.217;
From: Susan Hares <shares@ndzh.com>
To: 'Pushpasis Sarkar' <pushpasis.ietf@gmail.com>
Cc: 'idr wg' <idr@ietf.org>, idr-chairs@ietf.org
References: <00d701d2e559$600b0270$20210750$@ndzh.com> <CAEFuwkg95wLK8S0yQLqDdrLde1O=csObhbqNBRqA_ZhdwOLN4g@mail.gmail.com>
In-Reply-To: <CAEFuwkg95wLK8S0yQLqDdrLde1O=csObhbqNBRqA_ZhdwOLN4g@mail.gmail.com>
Date: Fri, 16 Jun 2017 14:51:55 -0400
Message-ID: <006e01d2e6d1$a074d3d0$e15e7b70$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006F_01D2E6B0.196333D0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQHGEJmr+n709MDefT8S5lkZx/33NAI6TWBxoi+vIjA=
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-QTr9Q9TUS6uUH8UqH6aJoXSaH4>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-node-admin-tag-extension-01 (6/14/2017 to 6/28/2017)
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 18:57:40 -0000

Pushpasis:

 

The IDR Working Group does not require 2 implementations for WG LC.  However, to send an IDR document to the IESG – the IDR WG requires 2 implementations.   We can simply hold the draft at approved, but waiting for implementations. 

 

Sue 

 

From: Pushpasis Sarkar [mailto:pushpasis.ietf@gmail.com] 
Sent: Friday, June 16, 2017 11:37 AM
To: Susan Hares
Cc: idr wg; idr-chairs@ietf.org
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-ls-node-admin-tag-extension-01 (6/14/2017 to 6/28/2017)

 

Hi Chairs,

 

Please find some answers inline.. 

 

On Thu, Jun 15, 2017 at 3:28 AM, Susan Hares <shares@ndzh.com> wrote:

This begins a 2 week WG LC for draft-ietf-bgp-ls-node-admin-tag-extension (6/14/2017 to 6/28/2017).   The WG should be aware that this draft has IPR associated with it.  In your responses regarding this WG LC, please indicate if you are concerned about the IPR. 

 

The chairs would appreciate if the operators would indicate whether they would deploy this draft.   

 

The authors should within the first 5 days do the following: 

1)      Send a statement to the WG indicating whether you know of any additional IPR,

[Pushpasis] I am not aware of any IPR other than the one already disclosed 

2)      Please respond to the IDR list questions on a daily basis

[Pushpasis] Sure, will be glad to do so. 

3)      Submit a implementation reports to the IDR wiki under the location 

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-node-admin-tag-extension-01

[Pushpasis] Honestly, I don't know about any implementation(s) of this draft myself. But this draft carries the same node-admin tags in BGP-LS as distributed by IGPs as specified in RFC 7917 (ISIS Node admin tags) and RFC 7777 (OSPF Node admin tags), and I doubt that there is an implementation of these IGP RFCs yet (I may be wrong though). So I would like to ask the WG if implementation report is still an absolute MUST for WGLC or not. 

 

Thanks and regards

-Pushpasis

 

The IDR WG will do a WG LC on a draft, but it will not forward this draft to the IESG without 2 working implementations.   If the these actions are not taken within 5 days, will extend the WG LC by 1 week while we wait for this information.   

 

Cheerily, Sue Hares and John Scudder (co-Chairs) 

Jie Dong (WG secretary) 


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr