IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@nexthop.com> Tue, 11 October 2005 13:57 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPKdT-0003wl-HZ; Tue, 11 Oct 2005 09:57:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPKdR-0003wg-Pg for idr@megatron.ietf.org; Tue, 11 Oct 2005 09:57:41 -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 JAA24762 for <idr@ietf.org>; Tue, 11 Oct 2005 09:57:39 -0400 (EDT)
Received: from gateout01.mbox.net ([165.212.64.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPKnY-0001Lm-2y for idr@ietf.org; Tue, 11 Oct 2005 10:08:09 -0400
Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21]) by gateout01.mbox.net (Postfix) with SMTP id DDBB812D3E0; Tue, 11 Oct 2005 13:57:13 +0000 (GMT)
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 763JJkN6L0492Mo1; Tue, 11 Oct 2005 13:57:12 GMT
Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 756JJkN6J0492Mo1; Tue, 11 Oct 2005 13:57:10 GMT
X-USANET-Routed: 2 gwsout-vs R:localhost:1825
Received: from gw2.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net via smtad (C8.MAIN.3.26F); Tue, 11 Oct 2005 13:57:09 GMT
X-USANET-Source: 165.212.116.254 IN jhaas@nexthop.com gw2.EXCHPROD.USA.NET
X-USANET-MsgId: XID451JJkN6k1821Xo1
Received: from localhost ([65.247.36.31]) by gw2.EXCHPROD.USA.NET over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Tue, 11 Oct 2005 07:57:09 -0600
Date: Tue, 11 Oct 2005 09:57:08 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: Enke Chen <enkechen@cisco.com>
Subject: Re: [Idr] WG Last Call on draft-ietf-idr-as4bytes-11.txt
Message-ID: <20051011135708.GO25945@nexthop.com>
References: <200510071641.j97GfgG21459@merlot.juniper.net> <Pine.LNX.4.63.0510100013110.3396@sheen.jakma.org> <434ABA2C.1070608@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <434ABA2C.1070608@cisco.com>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 11 Oct 2005 13:57:09.0557 (UTC) FILETIME=[AC2FE650:01C5CE6B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: idr@ietf.org, Paul Jakma <paul@clubi.ie>
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

On Mon, Oct 10, 2005 at 11:59:56AM -0700, Enke Chen wrote:
> * There some places where AS numbers are used where it wasn't
> clear how to deal with 4-octet as-numbers (e.g. extended
> communities).
> 
> Not a problem as the extended community spec has allocated type code for 
> 4-byte ASs.

In extended communities, the type may have as much to do with the community
being unique as does the contents.

RT-100:1 != RT4-100:1

Or at least this is one way to interpret the current spec.


-- 
Jeff Haas 
NextHop Technologies



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

v2.23.0 | Report a Bug | By Email