Re: [Idr] IDR Charter discussion

Jared Mauch <jared@puck.nether.net> Tue, 23 July 2019 19:32 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 8AF04120382 for <idr@ietfa.amsl.com>; Tue, 23 Jul 2019 12:32:10 -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 reeJADenEsAw for <idr@ietfa.amsl.com>; Tue, 23 Jul 2019 12:32:08 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::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 730D71202CF for <idr@ietf.org>; Tue, 23 Jul 2019 12:32:08 -0700 (PDT)
Received: by puck.nether.net (Postfix, from userid 162) id E11155401AF; Tue, 23 Jul 2019 15:32:07 -0400 (EDT)
Date: Tue, 23 Jul 2019 15:32:07 -0400
From: Jared Mauch <jared@puck.nether.net>
To: Susan Hares <shares@ndzh.com>
Cc: "'Neil J. McRae'" <neil@domino.org>, 'Job Snijders' <job@ntt.net>, jared@puck.nether.net, idr@ietf.org
Message-ID: <20190723193207.GB16221@puck.nether.net>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com> <20190722151151.GS33367@vurt.meerval.net> <04D143A8-FCFF-4FCD-A6FE-7446B1E86617@domino.org> <007201d54163$8b404370$a1c0ca50$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <007201d54163$8b404370$a1c0ca50$@ndzh.com>
User-Agent: Mutt/1.12.0 (2019-05-25)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/X-gZPRsv7PeV2eAB6e2zUmon_dM>
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:32:11 -0000

On Tue, Jul 23, 2019 at 10:33:05AM -0400, Susan Hares wrote:
> Neil:
> 
> On 1 + 2:  NM/OPS groups such as GROW have more expertise to decide requirements regarding E-BGP maximum prefixes and appropriate actions. IDR will be glad to review proposed requirements, appropriate action and any proposals on BGP changes.   

	I have partial XML for something doing this but think as it's a protcol extension it will end up in IDR vs GROW.  I'll try to finish getting the text done and send it to both lists.  If you want a private copy to help make sense of it - ping me off-list.

	think route-refresh type message that provides info on-demand.

	- jared

> On 3, proposals on sending key contact info over BGP have been proposed for 15 years.   People in operations have stated: "Please do not put this information in".  Other operations have stated - "Please put contact info" so I can survive outages without looking up phone numbers. Unless there are clear operational requirements,  IDR working on protocol changes will end up in the same debates.   So we will look to NM/OPS WGs to provide better requirements. 
> 
> Sue 
> 
> 
> -----Original Message-----
> From: Neil J. McRae [mailto:neil@domino.org] 
> Sent: Tuesday, July 23, 2019 8:37 AM
> To: Job Snijders; Susan Hares; jared@puck.nether.net
> Cc: idr@ietf.org
> Subject: Re: [Idr] IDR Charter discussion
> 
> I think 1+2 have some merit but 3 is not managing routing at a human level and shouldn't be here. IMO
> 
> 
> 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:
> 
> It may be good to consider some operations and management functions to be specced out in IDR.
> 
> >From the operational side of the house I recall a few long-standing
> wishes:
> 
>     - ability to see which prefixes are accepted/rejected by the
>       EBGP neighbor
>     - ability to see the maximum prefix limits configured by the
>       EBGP neighbor
>     - ability to relay some contact / circuit details over an EBGP
>       session to facilitate inter-organization coordination
> 
> All of the above can be accomplished in non-realtime through out-of-band mechanisms like e-mail and phone; but this type of out-of-band channels often are error-prone.
> 
> I think we would benefit from actively shifting some of this OAM from out-of-band into the BGP protocol itself so less coordination is needed between autonomous system operators.
> 
> I am not sure how to exactly word a high level milestone suitable for the charter. "Add more OAM"? "Add more operational debugging capabilities"? 
> 
> Kind regards,
> 
> Job
> 
> _______________________________________________
> 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.