Re: [Idr] IDR Charter discussion

Jared Mauch <jared@puck.nether.net> Tue, 23 July 2019 19:38 UTC

Return-Path: <jared@puck.nether.net>
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 EAD6A1202CF for <idr@ietfa.amsl.com>; Tue, 23 Jul 2019 12:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 2eabwQCtEaUc for <idr@ietfa.amsl.com>; Tue, 23 Jul 2019 12:38:17 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B56312029C for <idr@ietf.org>; Tue, 23 Jul 2019 12:38:17 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id CF4EB5401B8; Tue, 23 Jul 2019 15:38:16 -0400 (EDT)
Date: Tue, 23 Jul 2019 15:38:16 -0400
From: Jared Mauch <jared@puck.nether.net>
To: Job Snijders <job@instituut.net>
Cc: Susan Hares <shares@ndzh.com>, idr@ietf.org
Message-ID: <20190723193816.GD16221@puck.nether.net>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com> <20190723193643.GB81521@vurt.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190723193643.GB81521@vurt.meerval.net>
User-Agent: Mutt/1.12.0 (2019-05-25)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UmWe1TM9hbI5hGAkLfLMHicr0io>
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: Tue, 23 Jul 2019 19:38:20 -0000

On Tue, Jul 23, 2019 at 07:36:43PM +0000, Job Snijders wrote:
> 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

	I would like to see that work proceed.

	- jared

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

-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.