Re: [Idr] BGP autodiscovery design team

Jeffrey Haas <jhaas@pfrc.org> Thu, 05 December 2019 22:15 UTC

Return-Path: <jhaas@pfrc.org>
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 ACDCF120168 for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 14:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 FfJF2kXf7eGw for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 14:15:39 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E50EE1201CE for <idr@ietf.org>; Thu, 5 Dec 2019 14:15:38 -0800 (PST)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 878121E2F2; Thu, 5 Dec 2019 17:19:53 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <E7E38075-54F2-4F16-97BE-EE24943B5BFE@juniper.net>
Date: Thu, 5 Dec 2019 17:15:36 -0500
Cc: idr wg <idr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D145A2C-2498-413B-A805-79E4DF8876FE@pfrc.org>
References: <E7E38075-54F2-4F16-97BE-EE24943B5BFE@juniper.net>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Y_VpcJV6OoyIWr7XG1lg1txfJjk>
Subject: Re: [Idr] BGP autodiscovery design team
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Dec 2019 22:15:41 -0000

Publicly echoing my private responses, I'm willing to be on the design team.

-- Jeff

> On Dec 4, 2019, at 2:33 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org>; wrote:
> 
> Hi All,
> 
> I realized this morning that although we announced in the last meeting that we’re forming this design team, we never announced it on the list. This is to correct that mistake. Here’s the text of the slide we presented at the meeting (https://datatracker.ietf.org/meeting/106/materials/slides-106-idr-sessa-auto-discovery-design-team-chairs-00):
> 
> ---
> Autodiscovery
> 
> • Clear interest in WG to work on this topic.
> • No clear consensus on a specific approach.
> • Proposals (four of them) progressively closer semantically, seems likely convergence can happen. 
> • But, important differences remain.
> 	• At least: transport (L2, L3), liveness, security, maybe multihop.
> • Chairs propose to charter a design team to close on a single proposal, by next meeting.
> 	• Might build on one of the existing drafts, might be a new draft, up to the design team.
> 	• Emphasis on pragmatism, OK to limit applicability (for example, to a single administrative domain). 
> • Questions? Comments? Volunteers?
> —
> 
> We are in the process of forming the team and hope to announce it soon. We have many good volunteers already but if you didn’t know and do want to volunteer, please contact Sue and me. 
> 
> Note that the design team will not make any binding decisions: as with all WG work, the WG has the final word, so any output of the DT will serve as input to the WG as a whole. (So even if you aren’t part of the DT, that doesn’t mean you won’t have a chance to be part of the process.)
> 
> Thanks,
> 
> —John
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr