Re: [Idr] [Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]

Geoff Huston <gih@apnic.net> Tue, 13 February 2007 04:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGpk8-0007Uw-N9; Mon, 12 Feb 2007 23:58:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGpk7-0007Qq-CM for idr@ietf.org; Mon, 12 Feb 2007 23:58:15 -0500
Received: from geoff.telstra.net ([203.50.0.18]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGpk0-0005KL-70 for idr@ietf.org; Mon, 12 Feb 2007 23:58:15 -0500
Received: from vaioz1.apnic.net (geoff.telstra.net [203.50.0.18]) by geoff.telstra.net (8.13.6/8.13.6) with ESMTP id l1D4vwhr098110; Tue, 13 Feb 2007 15:57:58 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <7.0.0.16.2.20070213155251.042689b0@apnic.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16
Date: Tue, 13 Feb 2007 15:58:08 +1100
To: Erik Romijn <eromijn@ripe.net>, John Leslie <john@jlc.net>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Idr] [Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]
In-Reply-To: <20070209145803.GF13343@ripe.net>
References: <45CA4A4B.4040108@cisco.com> <20070208002802.GD2308@verdi> <20070209145803.GF13343@ripe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

At 01:58 AM 10/02/2007, Erik Romijn wrote:
>On Wed, Feb 07, 2007 at 07:28:02PM -0500, John Leslie wrote:
> > Enke Chen <enkechen@cisco.com> wrote:
> > >
> > > Please note these changes to the attribute names (the type codes are
> > > unchanged):
> > >
> > >     NEW_AS_PATH             --->   AS4_PATH
> > >     NEW_AGGREGATOR   --->   AS4_AGGREGATOR
>
>Perhaps a stupid question, but why not go for "AS4 speaker" and "AS2
>speaker" too instread of "NEW/OLD speaker"?


And that would change the code to support for these larger AS numbers 
in a BGP implementation in what way?

At some point its time to stop polishing documents in all kinds of 
wonderful and inventive ways and make the pragmatic judgement that 
its good enough to support running inter-operable code. I suspect 
that this particular draft got to that state of adequacy at least 4 
revs ago, and probably more. Lets face it, nothing in the 12 - 13 rev 
changes the code (and yes, I've implemented this spec, so I speak 
with some experience here). So why are we doing this document polishing?

(no, please don't tell me - sadly, I already know the answer!)

regards,

    Geoff








_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr