Return-Path: 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 649D21200DF for ; Tue, 11 Jun 2019 02:53:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 fl9wEfDtc517 for ; Tue, 11 Jun 2019 02:53:01 -0700 (PDT) Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AA5712004B for ; Tue, 11 Jun 2019 02:53:01 -0700 (PDT) Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 45NQKl2XTFz4wbL; Tue, 11 Jun 2019 11:52:59 +0200 (CEST) Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 45NQKk68CczDq7q; Tue, 11 Jun 2019 11:52:58 +0200 (CEST) Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM34.corporate.adroot.infra.ftgroup ([fe80::7873:1668:636f:52c%21]) with mapi id 14.03.0439.000; Tue, 11 Jun 2019 11:52:59 +0200 From: To: Susan Hares CC: "idr@ietf.org" Thread-Topic: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] Thread-Index: AdUe6OUjvDIGwFT+SrOBwJKEuiJdmwBT9r1Q Date: Tue, 11 Jun 2019 09:52:58 +0000 Message-ID: <22122_1560246778_5CFF79FA_22122_424_1_53C29892C857584299CBF5D05346208A48B13411@OPEXCAUBM43.corporate.adroot.infra.ftgroup> References: <094d01d51ee9$7329cc30$597d6490$@ndzh.com> In-Reply-To: <094d01d51ee9$7329cc30$597d6490$@ndzh.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.114.13.247] Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A48B13411OPEXCAUBM43corp_" MIME-Version: 1.0 Archived-At: Subject: Re: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] X-BeenThere: idr@ietf.org 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: Tue, 11 Jun 2019 09:53:04 -0000 --_000_53C29892C857584299CBF5D05346208A48B13411OPEXCAUBM43corp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Support. Thanks --Bruno From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares Sent: Sunday, June 9, 2019 7:33 PM To: idr@ietf.org Subject: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC [= ]6/9/2019 to 6/16/2019] This begins a 2 week IDR WG Last Call (LC) on ft-ietf-idr-capabilities-reg= istry-change-05.txt. The document is at: https://datatracker.ietf.org/doc/draft-ietf-idr-capabilities-registry-chang= e/ As registration document, there is no implementation report. Please indicate in comments to the IDR "support" or "no support" for WG LC. Consider: 1) Does this change to registration procedures for BGP capability code= s help speed up processing? 2) Is there any technical or operational issue in making this change? 3) Do we need to pass this to the IESG at the same time as any GROW do= cument? John Scudder is an author so I am the shepherd/chair on this draft. Cheerily, Susan Hares ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_53C29892C857584299CBF5D05346208A48B13411OPEXCAUBM43corp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Support.

 

Thanks

--Bruno

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Sunday, June 9, 2019 7:33 PM
To: idr@ietf.org
Subject: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - = WG LC []6/9/2019 to 6/16/2019]

 

This begins a 2 week IDR  WG Last Call= (LC) on ft-ietf-idr-capabilities-registry-change-05.txt.  =

 

The document is at:

https://datatracker.ietf.org= /doc/draft-ietf-idr-capabilities-registry-change/

 

As registration document, there is no imple= mentation report. 

 

Please indicate in comments to the IDR R= 20;support” or “no support” for WG LC.

Consider:

 

1)    &nbs= p; Does this change to registration procedures for BGP capability c= odes help speed up processing?

2)    &nbs= p; Is there any technical or operational issue in making this chang= e?

3)    &nbs= p; Do we need to pass this to the IESG at the same time as any GROW= document?

 

John Scudder is an author so I am the sheph= erd/chair on this draft. 

 

Cheerily, Susan Hares 

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
--_000_53C29892C857584299CBF5D05346208A48B13411OPEXCAUBM43corp_--