Re: [Idr] Request to adopt draft-heitz-idr-large-community

Thanks for your support David.
My code so far supports the draft in its entirety. Not just the attribute encoding, but a full set of route-policy statements, show commands and aggregation code to make it a useable BGP feature. It is not production ready, but the support here will certainly help push it through the process.

Thanks,
Jakob.

On Sep 6, 2016, at 7:45 PM, David Farmer <farmer@umn.edu<mailto:farmer@umn.edu>> wrote:

Thanks for the response, more below.

On Tue, Sep 6, 2016 at 5:46 PM, Job Snijders <job@ntt.net<mailto:job@ntt.net>> wrote:
Hi David,

On Tue, Sep 06, 2016 at 05:37:31PM -0500, David Farmer wrote:
> As an operator and someone involved in RIR policy, I support this and
> most any solution that provides usable communities for 4-byte ASNs.
>
> However, communities for 4-byte ASNs are not a new issue and there
> have been several solutions proposed over the past couple years.  The
> blocking issue seems to have been implementations, or the lack of
> them.

You make a valid point. Without implementations this thread is worthless.

I have hope that this time around it'll be different: the specification
is so simple it is almost in-excusable to not implement it. Having no
extendability is also a feature: there will be no suprises, what is
written down is what it is.

I like the simplicity, I hope it gets implemented.  A solution to this problem is desperately needed, but I think you know that. :)

I'm tracking implementations here: http://largebgpcommunities.net/implementations/
(and ofcourse in the RFC7942 section of the draft). I rely on what
people tell me, but you are probably best off to engage with your
vendors directly.

I encourage implementors to state whether this is on the roadmap and
what the ETAs will be for GM releases (if they are known yet).

Kind regards,

Job

Thank you for the pointer to the web site and the implementation tracking information in particular; while not yet sufficient to guarantee success, the current list seems encouraging.  Maybe you should add a pointer to the website and the implementation tracking information as an appendix to be deleted once published.

I have a few other thoughts on the content of the draft, but I'll take them outside of this thread.

Thanks.

--
===============================================
David Farmer               Email:farmer@umn.edu<mailto:Email%3Afarmer@umn.edu>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr