[Idr] IDR Charter discussion

"Susan Hares" <shares@ndzh.com> Mon, 10 June 2019 19:51 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 2F7371200EB for <idr@ietfa.amsl.com>; Mon, 10 Jun 2019 12:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 TrMEHe9tL3Qc for <idr@ietfa.amsl.com>; Mon, 10 Jun 2019 12:51:08 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 07BBC1200DE for <idr@ietf.org>; Mon, 10 Jun 2019 12:51:07 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.25.175.69;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Mon, 10 Jun 2019 15:51:03 -0400
Message-ID: <022b01d51fc5$d6576dd0$83064970$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_022C_01D51FA4.4F4817C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUfxcRRJjTNR9UET6u0Mkxr6DnpIw==
Content-Language: en-us
X-Antivirus: AVG (VPS 190610-6, 06/10/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lyzatmbZXOm_YbCHtFX7OWky1B4>
Subject: [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, 10 Jun 2019 19:51:09 -0000

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