From nobody Fri Jul  9 09:12:58 2021
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 BC5043A2631
 for <idr@ietfa.amsl.com>; Fri,  9 Jul 2021 09:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.347
X-Spam-Level: *
X-Spam-Status: No, score=1.347 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001,
 KHOP_HELO_FCRDNS=0.398, 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 dZickLQBqPao for <idr@ietfa.amsl.com>;
 Fri,  9 Jul 2021 09:12:54 -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 4725F3A2629
 for <idr@ietf.org>; Fri,  9 Jul 2021 09:12:54 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS))
 x-ip-name=50.107.119.54; 
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Fri, 9 Jul 2021 12:12:35 -0400
Message-ID: <003701d774dd$40d62750$c28275f0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0038_01D774BB.B9C52390"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Add027Ka2GLiFo9SQMipht4eRgNPJA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZG6qr0qcszPfeCwVuFCPJu9YpTU>
Subject: [Idr] WG adoption and IPR call for
 draft-ietf-idr-bgp-autoconf-considerations-01.txt (7/9/2021 to 7/23/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: Fri, 09 Jul 2021 16:12:57 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0038_01D774BB.B9C52390
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This begins a 2 week WG adoption call and IPR call for 

the requirements and considerations for BGP Auto-configuration 

(draft-ietf-idr-bgp-autoconf-considerations-01.txt). 

 

The authors should respond to this call indicating whether 

they know of IPR regarding this draft.  

 

The WG should consider if this draft in its current form

provides the appropriate requirements and considerations 

for protocol proposals for BGP auto-configuration 

within the data center.  

 

The June 21, 2021 Auto-Configuration interim had

discussed this draft.  You can obtain information 

on the interim on the IDR wiki page at: 

https://trac.ietf.org/trac/idr/wiki/June%2021%2C%202021%20-%20AutoConfigurat
ion%20Feedback%20

 

Adoption of this draft does not preclude 

developing requirements for BGP auto-configuration

outside the data center.  If you are interested in 

BGP auto-configuration outside the data center, 

please also indicate that in your adoption comments. 

 

Comment early and often on this draft.  

 

Cheers, Sue 

 

 

 


------=_NextPart_000_0038_01D774BB.B9C52390
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>This =
begins a 2 week WG adoption call and IPR call for <o:p></o:p></p><p =
class=3DMsoNormal>the requirements and considerations for BGP =
Auto-configuration <o:p></o:p></p><p =
class=3DMsoNormal>(draft-ietf-idr-bgp-autoconf-considerations-01.txt). =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The authors should respond to this call indicating =
whether <o:p></o:p></p><p class=3DMsoNormal>they know of IPR regarding =
this draft.&nbsp; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The WG =
should consider if this draft in its current form<o:p></o:p></p><p =
class=3DMsoNormal>provides the appropriate requirements and =
considerations <o:p></o:p></p><p class=3DMsoNormal>for protocol =
proposals for BGP auto-configuration <o:p></o:p></p><p =
class=3DMsoNormal>within the data center. &nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The June 21, =
2021 Auto-Configuration interim had<o:p></o:p></p><p =
class=3DMsoNormal>discussed this draft. &nbsp;You can obtain information =
<o:p></o:p></p><p class=3DMsoNormal>on the interim on the IDR wiki page =
at: <o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"https://trac.ietf.org/trac/idr/wiki/June%2021%2C%202021%20-%20Aut=
oConfiguration%20Feedback%20">https://trac.ietf.org/trac/idr/wiki/June%20=
21%2C%202021%20-%20AutoConfiguration%20Feedback%20</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Adoption of =
this draft does not preclude <o:p></o:p></p><p =
class=3DMsoNormal>developing requirements for BGP =
auto-configuration<o:p></o:p></p><p class=3DMsoNormal>outside the data =
center. &nbsp;If you are interested in <o:p></o:p></p><p =
class=3DMsoNormal>BGP auto-configuration outside the data center, =
<o:p></o:p></p><p class=3DMsoNormal>please also indicate that in your =
adoption comments. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Comment =
early and often on this draft.&nbsp; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Cheers, Sue =
<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0038_01D774BB.B9C52390--

