Re: [Idr] community of the day - common header

[Jared Mauch <[e-mail]>]

> On Sep 9, 2016, at 11:33 AM, Jeffrey Haas <[e-mail]> wrote:
> 
> On Thu, Sep 08, 2016 at 07:18:40PM -0400, Jared Mauch wrote:
>> On Thu, Sep 08, 2016 at 05:40:31PM -0400, Jeffrey Haas wrote:
>>> - We shouldn't be burning path attributes for it.  While the code space for
>>>  it isn't being exhausted fast, it means the only way to discard
>>>  unparseable attributes (implementation doesn't support) is a general path
>>>  attribute filtering mechanism.  Such filtering mechanisms are hazardous to
>>>  the incremental deployment of new BGP features.
>> 
>> 	Is there a particular shortcoming in rfc7606 that creates this
>> [moral] hazard, or are you speaking of the difficulty of writing
>> the code as referenced below?
> 
> You cite the issue yourself below with the example of attr 128.  In the
> absence of any ability to parse the attribute, your choice is to blindly
> pass it along or to drop it.
> 
> We know these things are community-like.  Stick them under a common type and
> let people's policy engines filter them.

Sure, implementations compliant with 7606 should do
treat-as-withdrawl if they encounter something they
can recover from.

>> Any code received today will take me ~12 months to deploy.  If wide
>> communities is ready to WGLC and ship with 3.1, I'd like to see movement
>> immediately so we can test and plan accordingly.  ~6+ years is quite a
>> long gestation period for the IETF.
> 
> This thread isn't about wide communities.  Stop making it about that.

Well, is it about rate of consumption of attributes, any new
route coloring/community-type thing?  It’s clear from me watching
the live stream of operator events today account teams are going to face
a number of requests about implementation details.

Please don’t trim too much of my operational grouse here, we should seek
consensus on *something* without prescribing what it is, wide, jumbo,
skinny or otherwise.  We as operators need something, i’m less worried
about the wire encoding than a viable solution.

>> P.S. Jeff, lets get together in person next week if you have time.
> 
> I'm available, but at this point it's unclear if you can afford that much
> beer.

I’ll take on this challenge. :)  I’ll message you privately about details
and if you’re local to me, feel free to inquire as well.

- Jared