Re: a different proposal for ipv6 in bgp

Tony Li <tli@jnx.com> Tue, 31 December 1996 00:43 UTC

Received: from cnri by ietf.org id aa10079; 30 Dec 96 19:43 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa21918; 30 Dec 96 19:43 EST
Received: (from daemon@localhost) by merit.edu (8.8.4/merit-2.0) id TAA04062 for idr-outgoing; Mon, 30 Dec 1996 19:23:51 -0500 (EST)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by merit.edu (8.8.4/merit-2.0) with SMTP id TAA04057 for <bgp@merit.edu>; Mon, 30 Dec 1996 19:23:48 -0500 (EST)
Received: by interlock.ans.net id AA21419 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 30 Dec 1996 19:23:46 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Mon, 30 Dec 1996 19:23:46 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 30 Dec 1996 19:23:46 -0500
Date: Mon, 30 Dec 1996 16:22:54 -0800 (PST)
Message-Id: <199612310022.QAA17560@chimp.jnx.com>
From: Tony Li <tli@jnx.com>
To: "John W. Stewart III" <jstewart@metro.isi.edu>
Cc: bgp@ans.net
In-Reply-To: jstewart@metro.isi.edu's message of 30 Dec 96 19:05:41 GMT
Subject: Re: a different proposal for ipv6 in bgp
References: <199612301905.AA24223@metro.isi.edu>
Sender: owner-idr@merit.edu
Precedence: bulk

One of the thoughts that we had for IDRP for IPv6 was that the domain
identifiers (aka big AS numbers) should be easier to manage.  To do that,
we thought that taking an IPv6 address from your assigned prefix would be
sufficient.  This effectively eliminates administration of a number space.

I'd strongly recommend that if folks wanna "fix" the AS number problem that
they consider this solution (or something similar).

Tony