Re: [Idr] IDR Charter discussion

<bruno.decraene@orange.com> Wed, 24 July 2019 19:16 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 C1E6C120417 for <idr@ietfa.amsl.com>; Wed, 24 Jul 2019 12:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 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, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 E1Npemi88UZk for <idr@ietfa.amsl.com>; Wed, 24 Jul 2019 12:16:20 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.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 84B98120409 for <idr@ietf.org>; Wed, 24 Jul 2019 12:16:20 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 45v4nv1s2Zz2y73; Wed, 24 Jul 2019 21:16:19 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 45v4nv10ZJzCql1; Wed, 24 Jul 2019 21:16:19 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM5C.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Wed, 24 Jul 2019 21:16:19 +0200
From: <bruno.decraene@orange.com>
To: Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IDR Charter discussion
Thread-Index: AQHVQY30TmZGa5zL2USiVhafQEmZkabaJFzA
Date: Wed, 24 Jul 2019 19:16:18 +0000
Message-ID: <31830_1563995779_5D38AE83_31830_59_1_53C29892C857584299CBF5D05346208A48BB75A8@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com> <20190723193643.GB81521@vurt.meerval.net>
In-Reply-To: <20190723193643.GB81521@vurt.meerval.net>
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/hwYI6y3NvggOlpI7OoKTp1kFDBE>
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: Wed, 24 Jul 2019 19:16:24 -0000

Dear Susan,

May be adding "BGP persistence",
(possibly depending on whether we believe the charter will be updated before or after we send this draft to IESG)
possibly under the umbrella "Improving BGP resiliency" which IMHO may be a general subject which should be of interest.

Kind regards,
--Bruno

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
Sent: Tuesday, July 23, 2019 3:37 PM
To: Susan Hares
Cc: idr@ietf.org
Subject: Re: [Idr] IDR Charter discussion

Dear Susan,

Perhaps "clean-up of some old things" can be added to the charter. 

As an example, I think a draft like this should go through the WG
towards publication: https://tools.ietf.org/html/draft-kumari-deprecate-as-set-confed-set

Kind regards,

Job

On Mon, Jun 10, 2019 at 03:51:03PM -0400, Susan Hares wrote:
> The IDR Charter was last revised in March, 2010. 
> 
>  
> 
> It's time to reconsider what needs to go in the charter: 
> 
>  
> 
> 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. 
> 
>  
> 
>  
> 
> Things which will be removed because we are done: 
> 
> ..         Support for 4-octet AS numbers, 
> 
> ..         Add path related additions, 
> 
> ..         Error handling rules for BGP in general, 
> 
> ..         Revisions to the BGP 'Minimum Route Advertisement Interval', 
> 
> ..         The definition of an "Accumulated IGP Metric".
> 
>  
> 
> In 2010, IDR started an advancement of BGP to full standard, but stopped. 
> 
> WG members indicated they wanted us to focus on the feature revisions. 
> 
>  
> 
> Is there anything we missed? 
> 
>  
> 
> Please use this thread to suggest things we should keep or drop in the
> charter. 
> 
>  
> 
> Cheerily, Susan Hares
> 

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

_______________________________________________
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.