Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - 2 weeks Early Allocation Call [6/2/2019 to 6/16/2019]

Jeff:

100% agree on alignment.  In fact at IETF 105,  John and I suggested to the
LSR chairs that they utilize a single draft with ISIS, OSPF, and BGP if the
BGP-LS or SR function is a "simple" copy of TLVs.   Chris and Acee have our
blessing to make it one draft - just as long as it is reviewed in IDR and
LSR.   

Sue  

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jeffrey Haas
Sent: Monday, June 3, 2019 1:43 PM
To: Susan Hares
Cc: idr@ietf.org; idr-chairs@ietf.org
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - 2 weeks Early
Allocation Call [6/2/2019 to 6/16/2019]

Sue,

On Sun, Jun 02, 2019 at 10:27:11PM -0400, Susan Hares wrote:
> This begins a 2 week Early Allocation call for parameters from: 
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-app-specif
> ic-attr-00
> 
> The authors are requesting for early code point allocation from
> 
> IANA to enable implementations with suggested code points as indicated 
> below.

I support early code point adoption.  In general, we should keep BGP-LS docs
in sync with LSR adopted drafts that have sufficient traction.

-- Jeff

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