Re: [Idr] WG Last Call on draft-ietf-idr-as4bytes-11.txt

Geoff Huston <gih@apnic.net> Thu, 13 October 2005 04:39 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPusb-0004Fw-8n; Thu, 13 Oct 2005 00:39:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPusZ-0004Fr-U5 for idr@megatron.ietf.org; Thu, 13 Oct 2005 00:39:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23079 for <idr@ietf.org>; Thu, 13 Oct 2005 00:39:40 -0400 (EDT)
Received: from kahuna.telstra.net ([203.50.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPv30-0006Wh-El for idr@ietf.org; Thu, 13 Oct 2005 00:50:32 -0400
Received: from gihm3.apnic.net (kahuna.telstra.net [203.50.0.6]) by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id j9D4dKXt069767; Thu, 13 Oct 2005 14:39:24 +1000 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20051013143340.02e25900@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Thu, 13 Oct 2005 14:39:16 +1000
To: John Leslie <john@jlc.net>, Paul Jakma <paul@clubi.ie>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Idr] WG Last Call on draft-ietf-idr-as4bytes-11.txt
In-Reply-To: <20051012204719.GC27304@verdi>
References: <200510071641.j97GfgG21459@merlot.juniper.net> <Pine.LNX.4.63.0510100013110.3396@sheen.jakma.org> <20051010151650.GB45489@verdi> <Pine.LNX.4.63.0510101622220.3396@sheen.jakma.org> <20051011155325.GI45489@verdi> <Pine.LNX.4.63.0510111919200.3396@sheen.jakma.org> <20051012204719.GC27304@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

> > It's the other way around more likely. The edges of the internet are
> > more likely to go NEW first...
>
>    We've agreed that we should spec a transition which can work
>either way (backbone going 4-byte first or edges going 4-byte first).

I do not understand this. Surprisingly, he earth is not flat. What is an 
'edge' and
what is a 'backbone' are from an individual network operator's perspective 
often
arbitrary distinctions, and then talking about which is these "goes first" 
is perhaps
unhelpful What I like about the draft as it stands is that it views transition
as a set of OLD / NEW and NEW / OLD transitions. That's simple and effective.
I would not readily ascribe attributes to a transition spec that starts 
from a premise
of "backbones" and "edges" and then starts to talk about which "goes first".

regards,

     Geoff





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