Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt

Nick Hilliard <nick@foobar.org> Wed, 05 October 2016 16:43 UTC

Return-Path: <nick@foobar.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 9024B129796 for <idr@ietfa.amsl.com>; Wed, 5 Oct 2016 09:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 jt1tvZgF7zms for <idr@ietfa.amsl.com>; Wed, 5 Oct 2016 09:43:51 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 810EB12978A for <idr@ietf.org>; Wed, 5 Oct 2016 09:43:51 -0700 (PDT)
X-Envelope-To: idr@ietf.org
Received: from crumpet.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id u95Ghm1Z038295 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2016 17:43:48 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be crumpet.local
Message-ID: <57F52DC2.40809@foobar.org>
Date: Wed, 05 Oct 2016 17:43:46 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.3 (Macintosh/20160930)
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
References: <147531113077.4216.12599976309263776317.idtracker@ietfa.amsl.com> <20161001085434.GW20697@Vurt.local> <005b01d21d58$aaf869e0$4001a8c0@gateway.2wire.net> <20161003095936.GC20697@Vurt.local> <57F51937.70103@foobar.org> <4C5E4C28-E26F-44C3-A661-514328180F6E@pfrc.org>
In-Reply-To: <4C5E4C28-E26F-44C3-A661-514328180F6E@pfrc.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UX3UmVTOHyIUnwuOex1baOXdYYU>
Cc: idr@ietf.org
Subject: Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt
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, 05 Oct 2016 16:43:53 -0000

Jeffrey Haas wrote:
> I'd drop the "and BGP Extended Communities".

you're correct on this on the grounds stated, i.e. there is no
widespread use of extcomms for inter-as signaling.

I added that line in there, and have an item on my todo list to get a
couple of lines of text together in the next couple of days to explain
in the Introduction section why extcomms are unsuitable for solving the
problem at hand.

The plan behind this was that when this draft goes through iesg review,
the first question that's going to be asked is: "pls explain why
extcomms won't work for your use case?", so given that that is likely to
precipitate a couple of lines of explanation, the secdir review will
then ask, "why didn't you mention extcomms in the security section when
you mentioned rfc1997 both here and in the intro?".

That, at least, was the rationale.  The thing about this draft is that
the principal is so easy to understand that a lot of people in the
review process are likely to want to bikeshed it.

So there are two options open regarding this:

1. omit everything about extcomms and face a likely barrage of nits from
post-wglc review, and also don't explain to posterity why they were
considered a non-viable solution to the problem at hand, or

2. put in an honorary mention of extcomms and in no more than a tiny
number of lines, explain why they are unsuitable.

I'd appreciate your input on this though.  If you think it's unnecessary
or counterproductive, that might save me word-whacking time which could
be productively spent tilting at other windmills.

Nick