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

Jeffrey Haas <jhaas@nexthop.com> Wed, 12 October 2005 16:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPjsS-0003QM-Ur; Wed, 12 Oct 2005 12:54:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPjsQ-0003Nb-5E for idr@megatron.ietf.org; Wed, 12 Oct 2005 12:54:50 -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 MAA05153 for <idr@ietf.org>; Wed, 12 Oct 2005 12:54:46 -0400 (EDT)
Received: from gateout01.mbox.net ([165.212.64.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPk2i-0000ai-AJ for idr@ietf.org; Wed, 12 Oct 2005 13:05:31 -0400
Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21]) by gateout01.mbox.net (Postfix) with SMTP id 697F412D6AB; Wed, 12 Oct 2005 16:54:21 +0000 (GMT)
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 342JJLq3T0314Mo1; Wed, 12 Oct 2005 16:54:20 GMT
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 341JJLq3s0065Mo1; Wed, 12 Oct 2005 16:54:17 GMT
X-USANET-Routed: 2 gwsout-vs R:localhost:1825
Received: from gw4.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net via smtad (C8.MAIN.3.26F); Wed, 12 Oct 2005 16:54:17 GMT
X-USANET-Source: 165.212.116.254 IN jhaas@nexthop.com gw4.EXCHPROD.USA.NET
X-USANET-MsgId: XID888JJLq3s1443Xo1
Received: from localhost ([65.247.36.31]) by gw4.EXCHPROD.USA.NET over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 10:53:44 -0600
Date: Wed, 12 Oct 2005 12:53:43 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: Geoff Huston <gih@apnic.net>
Subject: Re: [Idr] Revised text for the 4-byte AS draft - IANA Considerations
Message-ID: <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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.0.14.2.20051013014830.02e5db68@localhost>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 12 Oct 2005 16:53:44.0916 (UTC) FILETIME=[81ED2140:01C5CF4D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

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.

-- 
Jeff Haas 
NextHop Technologies



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