Re: [Idr] IDR Charter discussion

<bruno.decraene@orange.com> Mon, 17 June 2019 09:37 UTC

Return-Path: <bruno.decraene@orange.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 E7DD91200D7 for <idr@ietfa.amsl.com>; Mon, 17 Jun 2019 02:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eSssx2BJnSz2 for <idr@ietfa.amsl.com>; Mon, 17 Jun 2019 02:37:24 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77E2312009E for <idr@ietf.org>; Mon, 17 Jun 2019 02:37:24 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 45S5hy5Rdtz8wV9; Mon, 17 Jun 2019 11:37:22 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.48]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 45S5hy4R6tz2xCW; Mon, 17 Jun 2019 11:37:22 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM32.corporate.adroot.infra.ftgroup ([fe80::81c9:5f:b9c5:1241%21]) with mapi id 14.03.0439.000; Mon, 17 Jun 2019 11:37:22 +0200
From: <bruno.decraene@orange.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IDR Charter discussion
Thread-Index: AQHVItnr3Hy8C2W96U+NaGah9yCU06afllow
Date: Mon, 17 Jun 2019 09:37:22 +0000
Message-ID: <14367_1560764242_5D075F52_14367_448_2_53C29892C857584299CBF5D05346208A48B22B4E@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com> <20190614175306.GS23231@pfrc.org>
In-Reply-To: <20190614175306.GS23231@pfrc.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/q4eNM_pXmP1tMx27N9-HoraVsnk>
Subject: Re: [Idr] IDR Charter discussion
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: Mon, 17 Jun 2019 09:37:27 -0000

Sue, Jeff
 
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jeffrey Haas
> 
> Sue,
> 
> On Mon, Jun 10, 2019 at 03:51:03PM -0400, Susan Hares wrote:
> > The IDR Charter was last revised in March, 2010. 
> > 
> > Somethings we might include are:
> > 
> > ..         BGP Yang modules, 
> > 
> > ..         A general BGP Layer 3 auto-configuration or liveness, 
> > 
> > ..         Additional  tunnel features for a optional tunnel encapsulation (a
> > follow-on to draft-ietf-idr-tunnel-encaps), 
> > 
> > ..         Upgrade of the base BGP specification to Full Standard, 
> > 
> > ..         Flow specification additions, 
> > 
> > ..         BGP-LS basic functions (e.g.
> > <https://datatracker.ietf.org/doc/draft-ketant-idr-rfc7752bis/>
> > draft-ketant-idr-rfc7752bis-00) error handling
> > 
> > ..         Segment routing additions to BGP, 
> > 
> > ..         Wide Communities and other "bigger" communities , 
> > 
> > ..         Revisions to Existing features. 
> 
> I'm supportive for these.
> 
> One item I'd suggest for consideration is a mechanism to handle the dynamic
> provisioning of new address families.

+1
(including removing AF if possible)
 
> IDR currently has two drafts that overlap this space:
> draft-ietf-idr-bgp-multisession
> draft-ietf-idr-dynamic-cap
> 
> However, I consider both drafts to be problematic or over-broad for the
> specific issue.  IMO:
> - Multisession lets you spin up new sessions to handle segregation of
  > address families, but complicates how routes learned across each session
  > interact.
> - Dynamic capabilities is overly general and has been noted to be
  > problematic.  (Previous e.g.: what happens if you toggle graceful restart
  > or add-paths?)

+1
 
> I don't suggest a solution in this mail and merely note covering proposals.

Possibly RFC 4724/8538 (GR) could be used (as a starting point).

> Having a targeted charter item would be useful.

+1

--Bruno
> 
> -- Jeff
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles 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 electroniques 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 information 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 delete 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.