Re: [Idr] Thoughts on https://www.ietf.org/id/draft-hares-idr-bgp-registries-01.txt

"Susan Hares" <shares@ndzh.com> Thu, 23 March 2017 19:14 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 BB22012986E for <idr@ietfa.amsl.com>; Thu, 23 Mar 2017 12:14:46 -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, URIBL_BLOCKED=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 ojGc4PZ4y9iJ for <idr@ietfa.amsl.com>; Thu, 23 Mar 2017 12:14:45 -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 4DB8C13162D for <idr@ietf.org>; Thu, 23 Mar 2017 12:14:28 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.5.9;
From: Susan Hares <shares@ndzh.com>
To: 'Jeffrey Haas' <jhaas@pfrc.org>
Cc: 'Eric C Rosen' <erosen@juniper.net>, "'John G. Scudder'" <jgs@juniper.net>, idr@ietf.org
References: <048701d29cd9$15204b80$3f60e280$@olddog.co.uk> <022201d29ce6$ffb2ba40$ff182ec0$@ndzh.com> <c369a60a-3ccc-bf7d-dd29-d289d7a6b67e@juniper.net> <02dc01d2a25b$a1eca590$e5c5f0b0$@ndzh.com> <3b9c229a-4573-c586-8627-3a8c38539ff8@juniper.net> <E40AC551-E802-4662-A2F5-2E8EDB3C746F@juniper.net> <c8804d0b-39e0-bb56-464c-fe1d051f2d91@juniper.net> <050901d2a3fd$734b3e10$59e1ba30$@ndzh.com> <20170323181052.GL27015@pfrc.org> <001f01d2a401$1fc173a0$5f445ae0$@ndzh.com> <20170323184608.GM27015@pfrc.org>
In-Reply-To: <20170323184608.GM27015@pfrc.org>
Date: Thu, 23 Mar 2017 15:09:19 -0400
Message-ID: <00b301d2a408$f975b460$ec611d20$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHgLJVhftftdlZ2OeQGM5dxbx7ZtQIfusEjApalZLoB3VIuCQJnQvCHApVdmPIBwb1GPgECN7t0AgoLdiwB6VksPAE6yA/0oOukvgA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/N9H8Pz_1IU_0jqQOV6UvRe6eA1Q>
Subject: Re: [Idr] Thoughts on https://www.ietf.org/id/draft-hares-idr-bgp-registries-01.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: Thu, 23 Mar 2017 19:14:47 -0000

Thanks for the ideas!  

1) boilerplate text for allocations, 
2) flagged issues to one WG 
3) cross-WG review button in datatracker.  

Sue 

-----Original Message-----
From: Jeffrey Haas [mailto:jhaas@pfrc.org] 
Sent: Thursday, March 23, 2017 2:46 PM
To: Susan Hares
Cc: 'Eric C Rosen'; 'John G. Scudder'; idr@ietf.org
Subject: Re: [Idr] Thoughts on
https://www.ietf.org/id/draft-hares-idr-bgp-registries-01.txt

On Thu, Mar 23, 2017 at 02:13:07PM -0400, Susan Hares wrote:
> - If flagging for more eye review is the case, then Job's suggestion 
> is the way forward.  It works for most YANG modules.

As I noted off-list to Job, pattern matching works great when you have a
pattern that can catch it.  Better than nothing, especially if we end up
with good boilerplate text for allocations.  (It might be worth having a
chat with IANA about that.)

> - If having the expertise to review the "flag" is the issue,  1 WG 
> being in charge of the situation will suffice with the current setup.
> - if cross-review in all BGP working group is issue - then try my 
> registries proposal + IETF consensus.
> - if distrust of a single answer from WG shepherd, WG chair or set of 
> WG chairs - this draft + Eric's suggestion for who can review.

Mostly, I think once an issue is flagged, all eyes need to be pulled to one
place.  For the registries in question, IDR@ietf is probably fine, as long
as we reach out.

While I share some of Eric's dislike of process, I don't quite share his
paranoia about process blockers.  When things go awry anyway, the best we
have in process is the appeals process.  If we've reached that point, speed
is doomed anyway.

> If we can define the largest concern(s), let's we could start with 
> that solution.

I'd suggest finding a way to flag stuff is appropriate.  Nits search is one.
Allowing chairs to prod a button in datatracker that says cross-WG review is
needed might be another.  I suspect this may make good wgchairs discussion.

-- Jeff