Re: [Idr] Request to adopt draft-heitz-idr-large-community - Working Group Adoption call (9/6 to 9/20)

[Martin Millnert <[e-mail]>]

On Wed, 2016-09-14 at 20:30 +0000, Jakob Heitz (jheitz) wrote:
> I don't think it's an "or".
> Large is designed to be quick to develop and deploy for a limited use
> case, albeit a widely and strongly demanded one.

I don't see any clear objection to this part, in the thread, which did
spin off a bit from its Subject: line IMO.

> Wide is the extensible powerful that can do the rest. We can take the
> time to do that one right.

Sounds good.


Jakob: at XR, how much wall time would you bestguesstimate a first
customer release of Large would take, if you were able to independently
ship only this feature? (Like a bgpd plugin or something)

I'm asking because I expect it to be pretty harmless and easy on
vendors, leaving room/resources for more advanced implementations once
the have finished baking.

/M

> Thanks,
> Jakob.
> 
> > 
> > I think our only remaining options are wide with no extra data in
> > the common header, or just go for large which
> > already has running code and the support of a large part of the
> > intended user-base.
> > 
> > Cheers,
> > Sander
> 
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr