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

Jeffrey Haas <jhaas@pfrc.org> Fri, 09 September 2016 17:04 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 5E9A212B12D for <idr@ietfa.amsl.com>; Fri, 9 Sep 2016 10:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level:
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-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 seEprMCvrItu for <idr@ietfa.amsl.com>; Fri, 9 Sep 2016 10:04:07 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6017D12B05A for <idr@ietf.org>; Fri, 9 Sep 2016 10:04:07 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 5B3951E331; Fri, 9 Sep 2016 13:05:13 -0400 (EDT)
Date: Fri, 09 Sep 2016 13:05:13 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Gert Doering <gert@space.net>
Message-ID: <20160909170513.GE12105@pfrc.org>
References: <20160908214031.GA23544@pfrc.org> <20160908231840.GB16775@puck.nether.net> <20160909153317.GC8370@pfrc.org> <8C072797-55A7-4D1A-87E4-67551953EF22@puck.nether.net> <20160909155952.GE8370@pfrc.org> <20160909164640.GE79185@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160909164640.GE79185@Space.Net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/hRjyyO4tkxON0lDDRjJNoh-GkSs>
Cc: idr@ietf.org
Subject: Re: [Idr] community of the day - common header
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Sep 2016 17:04:08 -0000

On Fri, Sep 09, 2016 at 06:46:40PM +0200, Gert Doering wrote:
> Hi,
> 
> On Fri, Sep 09, 2016 at 11:59:53AM -0400, Jeffrey Haas wrote:
> > As an operator, do you want to play long-term whack-a-mole with the
> > attribute set of the week, worrying about whether something you filter today
> > may need to get through later, or would you prefer we make that job easier
> > but trying to move "color" into a common bucket?
> 
> I'd love to have something minimal ASAP, and the kitchen sink bucket thingie
> can then take until I'm retired to materialize.

I suspect your 3 implementations in flight can add 64 bits of header on top
of the existing code without too much headache.  They should already have
transitivity checks in the code for extended communities they can lift.

And if those 3 implementations in flight ship on squatted code points
without appropriate plans to change per IDR standardization, they've learned
nothing about the foibles of what happens when you ship too early.

-- Jeff