Re: [Idr] BGP autodiscovery design team

" 徐小虎(义先) " <> Thu, 05 December 2019 03:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 85FB4120043; Wed, 4 Dec 2019 19:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5oNosfxUYX5p; Wed, 4 Dec 2019 19:44:27 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 90BD612001A; Wed, 4 Dec 2019 19:44:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=default; t=1575517463; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=51byAiatb/SHxTa8UjkeFS8WTQ/jSgFUEv25wpZOUN4=; b=wW2AM1B6XsQCeRJ8pA2Oib5aEl4e9j7+1IeEB/K1lSv/lf6Vji4ncZXYlwta1fxq7Ni+QniKqRbLR8AiqZNqyUBQww2ZDKPGU9RG4eM3WO/wb8eKEXxh7DK2UCZuSHF/C7cx7Je010mLXiHkYLzKnFhP7YUSansVT1SKdM4pG14=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R161e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03299;; NM=1; PH=DW; RN=2; SR=0; TI=W4_5657687_v5ForWebDing_0AB10216_1575517463459_o7001c163g;
Received: from WS-web ([W4_5657687_v5ForWebDing_0AB10216_1575517463459_o7001c163g]) by e01l10423.eu6 at Thu, 05 Dec 2019 11:44:23 +0800
Date: Thu, 05 Dec 2019 11:44:23 +0800
From: "徐小虎(义先)" <>
To: Idr <>, idr wg <>
Reply-To: "徐小虎(义先)" <>
Message-ID: <>
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Safari]
MIME-Version: 1.0
References: <>
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NjATW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfNikgQXBwbGVXZWJLaXQvNjA1LjEuMTUgKEtIVE1MLCBsaWtlIEdlY2tvKSBWZXJzaW9uLzEyLjAuMyBTYWZhcmkvNjA1LjEuMTU=XQ
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_31813_502a7940_5de87d17_88a1d4"
Archived-At: <>
Subject: Re: [Idr] BGP autodiscovery design team
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Dec 2019 03:44:29 -0000

Hi John,

I volunteer as well.

Best regards,

From:John Scudder <>
Send Time:2019年12月5日(星期四) 03:33
To:idr wg <>
Subject:[Idr] BGP autodiscovery design team

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 (


• 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.)


Idr mailing list