Re: [Idr] BGP autodiscovery design team

"UTTARO, JAMES" <> Thu, 05 December 2019 13:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0134F120104 for <>; Thu, 5 Dec 2019 05:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cpcSjIp8QFK0 for <>; Thu, 5 Dec 2019 05:37:44 -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 4868D1200C5 for <>; Thu, 5 Dec 2019 05:37:44 -0800 (PST)
Received: from pps.filterd ( []) by ( with SMTP id xB5Da0lH016332; Thu, 5 Dec 2019 08:37:41 -0500
Received: from ( []) by with ESMTP id 2wq21s94v6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 05 Dec 2019 08:37:41 -0500
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id xB5Dbfum022323; Thu, 5 Dec 2019 08:37:41 -0500
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id xB5DbYU5022217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Dec 2019 08:37:35 -0500
Received: from ( []) by (Service) with ESMTP id 2BC3A4014C33; Thu, 5 Dec 2019 13:37:34 +0000 (GMT)
Received: from (unknown []) by (Service) with ESMTPS id 180D64014C32; Thu, 5 Dec 2019 13:37:34 +0000 (GMT)
Received: from ([]) by ([]) with mapi id 14.03.0468.000; Thu, 5 Dec 2019 08:37:33 -0500
From: "UTTARO, JAMES" <>
To: John Scudder <>, idr wg <>
Thread-Topic: BGP autodiscovery design team
Thread-Index: AQHVqtmqrRq1UF+NcE2nCZoCamlAGKerjFbg
Date: Thu, 05 Dec 2019 13:37:33 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-05_03:2019-12-04,2019-12-05 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 phishscore=0 malwarescore=0 mlxlogscore=999 clxscore=1031 priorityscore=1501 impostorscore=0 mlxscore=0 adultscore=0 spamscore=0 bulkscore=0 suspectscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912050115
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 13:37:46 -0000


	I will volunteer..

	Jim Uttaro

-----Original Message-----
From: Idr <> On Behalf Of John Scudder
Sent: Wednesday, December 04, 2019 2:33 PM
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