Re: [Idr] draft-ietf-idr-bgp-attribute-announcement dead on arrival?

Jeffrey Haas <jhaas@pfrc.org> Wed, 12 October 2016 13:49 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 A1A2012950B for <idr@ietfa.amsl.com>; Wed, 12 Oct 2016 06:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.898
X-Spam-Level:
X-Spam-Status: No, score=-4.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.996, 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 uwrIp7UTIVwn for <idr@ietfa.amsl.com>; Wed, 12 Oct 2016 06:49:57 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 652E9129480 for <idr@ietf.org>; Wed, 12 Oct 2016 06:49:57 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CED3D1E32B; Wed, 12 Oct 2016 09:51:55 -0400 (EDT)
Date: Wed, 12 Oct 2016 09:51:55 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Acee Lindem (acee)" <acee@cisco.com>
Message-ID: <20161012135155.GF22695@pfrc.org>
References: <0E9469C4-2B72-484A-9C93-BC13401F6889@pfrc.org> <003901d21f20$95ece2f0$c1c6a8d0$@ndzh.com> <CAHxMReZQ-t6dFY--CYw-NomyD=Z8uq2p=sjCj99J2Sa6wZDDCw@mail.gmail.com> <D423912E.825A6%acee@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D423912E.825A6%acee@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DQBpdl1Uskajh_ui_g1GJrgNy4o>
Cc: IETF IDR WG <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] draft-ietf-idr-bgp-attribute-announcement dead on arrival?
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: Wed, 12 Oct 2016 13:49:58 -0000

Acee (and Sue earlier)

On Wed, Oct 12, 2016 at 11:11:38AM +0000, Acee Lindem (acee) wrote:
> I agree with Rob that WG adoption of large communities in no way implies that attribute scoping is not a requirement and should not also be pursued.
> 
> In fact, there may even be hope for wide communities to evolve into the long term solution.

I would honestly prefer this conversation pretends the wide community draft
doesn't exist.  People keep getting hung up on it.

This is more the general long term question.

My intention a day after Sue's response had been to scrub the list of
pending path attribute features in IDR, BESS, etc., but I've not found the
time to do that yet.

WRT large communities, the main reason I cite that conversation is not an
attempt to "beat the dead horse", but to point out what was brought up as
technical objections to such header mechanisms.  If the WG simply wants to
declare what was raised as technical objections as non-technical objections
(i.e. "we simply didn't want to") - so be it.  But that's not how the
narrative ran.

-- Jeff