Re: [Idr] BGP in an IPv6-only environment

Enke Chen <enkechen@cisco.com> Sat, 20 May 2006 20:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhY4N-0002tn-1R; Sat, 20 May 2006 16:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhY4L-0002ti-Rf for idr@ietf.org; Sat, 20 May 2006 16:29:01 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhY4J-0006u4-HG for idr@ietf.org; Sat, 20 May 2006 16:29:01 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 20 May 2006 13:28:59 -0700
X-IronPort-AV: i="4.05,150,1146466800"; d="scan'208"; a="1809922966:sNHT52500894"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id k4KKSwk2002426; Sat, 20 May 2006 13:28:58 -0700
Received: from [10.21.97.189] (sjc-vpn1-445.cisco.com [10.21.97.189]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k4KKSwsF028870; Sat, 20 May 2006 13:28:58 -0700 (PDT)
Message-ID: <446F7C0A.9050602@cisco.com>
Date: Sat, 20 May 2006 13:28:58 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Walt Lazear <lakematesw@comcast.net>
Subject: Re: [Idr] BGP in an IPv6-only environment
References: <013901c67c47$82be7540$5100a8c0@WaltXP>
In-Reply-To: <013901c67c47$82be7540$5100a8c0@WaltXP>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1522; t=1148156938; x=1149020938; c=relaxed/simple; s=sjdkim5001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:Enke=20Chen=20<enkechen@cisco.com> |Subject:Re=3A=20[Idr]=20BGP=20in=20an=20IPv6-only=20environment; X=v=3Dcisco.com=3B=20h=3DhCdUmf6+e5Tn8EDauvri39G5Y6E=3D; b=cWULM1HgrVOVLFbQKfUwhE9S6FqOzCpaXmpM4NVPIovaDQ1yG7PsIi5uRAwbESwsiC2Fpdxt jmdGIZbJKw9bmW9yi4VqFkvow0szsO185yyKHw90n3W3y0GOj4H66g55;
Authentication-Results: sj-dkim-5.cisco.com; header.From=enkechen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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

Hi, Walt:

Please take a look at these documents:

   draft-ietf-idr-bgp-identifier-07.txt

   draft-ietf-idr-as4bytes-12.txt

-- Enke


Walt Lazear wrote:

>I was looking at RFC 2283 (Multiprotocol Extensions for BGP-4) and in
>the overview, it mentions that any BGP speaker has to have an IPv4
>address (to create the BGP Identifier attribute).  This does not bode
>well for the future of IPv6, to which I am sensitized by some ongoing
>Government work.  
>
>Talking to some who have created IPv6-only environments, it seems that
>they are only dealing with single subnets or very simple topologies, so
>BGP has not been an issue.  I also looked back in the IDR archives for a
>rationale, but could not find such a discussion recently.
>
>So, what is someone to do who wants to create an IPv6-only environment?
>Is it up to those defining (the future) version BGP-5 to create BGP
>identifiers longer than 32 bits or AS numbers longer than 16 bits (while
>we're at it), to accommodate the incredibly larger world of IPv6 (with
>128-bit addresses)?  Or was it a compromise in RFC 2283 to ignore the
>IPv6-only world (assuming it won't really happen on operational networks
>for decades) and therefore retain backward compatibility?  That's
>valuable in the short term, but not forever.
>
>Thanks in advance for any thoughts.
>
>Walt Lazear
>
>
>
>_______________________________________________
>Idr mailing list
>Idr@ietf.org
>https://www1.ietf.org/mailman/listinfo/idr
>  
>

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