Re: [Idr] IDR Charter discussion

Jeffrey Haas <jhaas@pfrc.org> Fri, 14 June 2019 17:52 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 B44171206F7 for <idr@ietfa.amsl.com>; Fri, 14 Jun 2019 10:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 nSunhKdVRV1b for <idr@ietfa.amsl.com>; Fri, 14 Jun 2019 10:52:04 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E055E1206F1 for <idr@ietf.org>; Fri, 14 Jun 2019 10:52:03 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 8F8721E2F1; Fri, 14 Jun 2019 13:53:07 -0400 (EDT)
Date: Fri, 14 Jun 2019 13:53:07 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Message-ID: <20190614175306.GS23231@pfrc.org>
References: <022b01d51fc5$d6576dd0$83064970$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <022b01d51fc5$d6576dd0$83064970$@ndzh.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/63cEa5ssBGB2gaTi9JqYPUVXwvk>
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: Fri, 14 Jun 2019 17:52:06 -0000

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.

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

I don't suggest a solution in this mail and merely note covering proposals.
Having a targeted charter item would be useful.

-- Jeff