Re: [Idr] Revised text for the 4-byte AS draft - IANA Considerations

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPu1F-0007MS-13; Wed, 12 Oct 2005 23:44:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPu1B-0007MC-G1 for idr@megatron.ietf.org; Wed, 12 Oct 2005 23:44:33 -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 XAA20834 for <idr@ietf.org>; Wed, 12 Oct 2005 23:44:29 -0400 (EDT)
Received: from kahuna.telstra.net ([203.50.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPuBb-0005Dn-DI for idr@ietf.org; Wed, 12 Oct 2005 23:55:21 -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 j9D3i2Xt069127; Thu, 13 Oct 2005 13:44:07 +1000 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20051013132547.02c62550@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Thu, 13 Oct 2005 13:38:14 +1000
To: Jeffrey Haas <jhaas@nexthop.com>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Idr] Revised text for the 4-byte AS draft - IANA Considerations
In-Reply-To: <20051012165343.GU25945@nexthop.com>
References: <200510071641.j97GfgG21459@merlot.juniper.net> <Pine.LNX.4.63.0510100013110.3396@sheen.jakma.org> <434ABA2C.1070608@cisco.com> <434C66AC.7080506@cisco.com> <6.2.0.14.2.20051013014830.02e5db68@localhost> <20051012165343.GU25945@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

At 02:53 AM 13/10/2005, Jeffrey Haas wrote:
>Geoff,
>
>On Thu, Oct 13, 2005 at 02:01:35AM +1000, Geoff Huston wrote:
> > The alternative is to propose an augmentation of the existing AS number
> > registry where the first 65536 numbers are noted as "2-Byte compliant"
> > numbers, and the remainder of the registry are "4-Byte-only" values.
>
>I prefer this option.  While mistakes are probably rare at best,
>this narrows (eliminates) the chances of a mistake causing a conflict
>between the registries.

I'm personally not willing to write text for this option, as I feel that it
makes the 2-byte registry ambiguous in terms of interpretation. What I
have drafted is text that refers to the inclusion of the 2-Byte registry's
contents in the low (0:0 - 0:65,535) number block of the the 4-Byte registry
by reference. If you have alternate text as clear IANA instructions that
preserves the appropriate distinction between the 2-Byte and 4-Byte AS
number registries while co-existing in a single protocol parameter
register then a request for your text that achieves this would be
appropriate.


Geoff Huston
APNIC






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