IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@pfrc.org> Tue, 11 October 2016 14:07 UTC

Return-Path: <jhaas@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 24E1B129548 for <idr@ietfa.amsl.com>; Tue, 11 Oct 2016 07:07:57 -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 G1nEzGQJf6Ma for <idr@ietfa.amsl.com>; Tue, 11 Oct 2016 07:07:53 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E49091294C5 for <idr@ietf.org>; Tue, 11 Oct 2016 07:07:52 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 919021E1F0; Tue, 11 Oct 2016 10:09:49 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset="us-ascii"
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <57FCC876.5090109@foobar.org>
Date: Tue, 11 Oct 2016 10:07:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52AF3F60-BC0F-44AC-89D7-8E108617162F@pfrc.org>
References: <147531113077.4216.12599976309263776317.idtracker@ietfa.amsl.com> <20161001085434.GW20697@Vurt.local> <005b01d21d58$aaf869e0$4001a8c0@gateway.2wire.net> <20161003095936.GC20697@Vurt.local> <04cf01d21d68$52c656a0$4001a8c0@gateway.2wire.net> <20161003115723.GD20697@Vurt.local> <57F27D3F.7090404@foobar.org> <00da01d22085$4f0f2ee0$4001a8c0@gateway.2wire.net> <57F78B7D.609@foobar.org> <333030E6-0422-4A34-B07B-90D5F8E9F116@gmail.com> <57F92043.20301@foobar.org> <A9BBA442-361F-444F-9AFC-33FAAF5F6061@gmail.com> <00ff01d22214$a9832440$4001a8c0@gateway.2wire.net> <57FAD3EA.6070800@foobar.org> <020b01d223a1$f0e34a20$4001a8c0@gateway.2wire.net> <57FCC876.5090109@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/doLkQ3EmmZtOWvGP6LO8POhNjEc>
Cc: idr <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: Tue, 11 Oct 2016 14:07:57 -0000

> On Oct 11, 2016, at 7:09 AM, Nick Hilliard <nick@foobar.org> wrote:
> 
> t.petch wrote:
>> I want a MUST in there so if anyone does otherwise, we can say No!, not
>> allowed.
> 
> If an operator in the far depths of inner Kaboodlestan uses an IPv4
> address instead of an ASN, the IETF can disapprove all it wants, and it
> will make no difference to anyone.

Somewhat relevant example in other extensions:
Many implementations treat an add-paths path-id as an integer and you tend to see them showing up as a int in show commands.

At least one implementation chose to use a BGP identifier/IP address in theirs.

The spec treats the value opaquely.  Both use cases make sense in their own context.

End of the day, the protocol cares that it's a 4 byte value.  Users may want a given representational syntax because it makes their life easier in their particular scenario.

Neither is solely the Right Thing.

-- Jeff

v2.23.0 | Report a Bug | By Email