IETF Logo Mail Archive

[Idr] Adoption Call on DT document (draft-ietf-idr-bgp-autoconf-considerations-00.txt) [3/10/2021 to 3/31/2021]

Susan Hares <shares@ndzh.com> Wed, 10 March 2021 18:03 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 191EA3A14AF for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 10:03:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.95
X-Spam-Level:
X-Spam-Status: No, score=0.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 iomXg7C829vP for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 10:03:38 -0800 (PST)
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 5D88C3A14A6 for <idr@ietf.org>; Wed, 10 Mar 2021 10:03:38 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.107.94.230;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Wed, 10 Mar 2021 13:03:32 -0500
Message-ID: <010401d715d7$b061cb70$11256250$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0105_01D715AD.C78D2300"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdcV15/852cYjdzAQl+xVaaVIQkR1A==
Content-Language: en-us
X-Antivirus: AVG (VPS 210310-4, 03/10/2021), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/24jEeF6U2jiVwdu3adR0sIQDDjY>
Subject: [Idr] Adoption Call on DT document (draft-ietf-idr-bgp-autoconf-considerations-00.txt) [3/10/2021 to 3/31/2021]
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: Wed, 10 Mar 2021 18:03:40 -0000

Greetings: 

 

This is an adoption/feedback call for the DT team document:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-autoconf-considerations/

 

This call for comments will run for 3 weeks. 

 

In your feedback please let us know: 

 

1) do you think this represents a good set of requirements for bgp autoconf
protocol in the data center? 

 

2) Do you think the document should remove any requirements or add an
requirements?  

 

3) Do you think the review of the protocols should be moved to another
document? 

 

4) Should a IDR DT create the requirements for non-Data Center deployments
prior to starting work on a BGP auto-configuration protocol? If so, should a
DT start these requirements in parallel? 

 

Cheers, Sue Hares

v2.19.0 | Report a Bug | By Email