[85609] in North American Network Operators' Group
Re: shim6 (was Re: IPv6 news)
daemon@ATHENA.MIT.EDU (Owen DeLong)
Fri Oct 14 15:17:11 2005
Date: Fri, 14 Oct 2005 12:16:22 -0700
From: Owen DeLong <owen@delong.com>
To: David Conrad <david.conrad@nominum.com>,
Joe Abley <jabley@isc.org>
Cc: "Christopher L.Morrow" <christopher.morrow@mci.com>,
nanog@nanog.org
In-Reply-To: <F8230CDF-2A05-42C4-B2D1-4D3A5667A1A9@nominum.com>
Errors-To: owner-nanog@merit.edu
--==========993232BBBA694884AC4D==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
BTW, as I read it, SHIM6 requires not only modification to ALL nodes at the
site,
but, modification to ALL nodes to which the node needs reliable
connectivity.
In other words, SHIM6 is not fully useful until it is fully ubiquitous in
virtually
all IPv6 stacks.
Owen
--On October 14, 2005 11:48:28 AM -0700 David Conrad
<david.conrad@nominum.com> wrote:
>
> Joe (or anyone else),
>
> On Oct 14, 2005, at 7:57 AM, Joe Abley wrote:
>> The big gap in the multi-homing story for v6 is for end sites,
>> since those are specifically excluded by all the RIRs' policies on
>> PI addressing right now. Shim6 is intended to be a solution for end
>> sites.
>
> Since shim6 requires changes in protocol stacks on nodes, my impression
> has been that it isn't a _site_ multihoming solution, but rather a
> _node_ multihoming solution. Is my impression incorrect?
>
>> Are you suggesting that something else is required for ISPs above
>> and beyond announcing PI space with BGP, or that shim6 (once baked
>> and real) would present a threat to ISPs?
>
> If my impression is correct, then my feeling is that something else is
> required. I am somewhat skeptical that shim6 will be implemented in any
> near term timeframe and it will take a very long time for existing v6
> stacks to be upgraded to support shim6. What I suspect will be required
> is real _site_ multihoming. Something that will take existing v6
> customer sites and allow them to be multi-homed without modification to
> each and every v6 stack within the site.
>
> Rgds,
> -drc
--
If it wasn't crypto-signed, it probably didn't come from me.
--==========993232BBBA694884AC4D==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
iD8DBQFDUAQKn5zKWQ/iqj0RAmPFAKCCyu6lbb6zXraLcrNDIEzxUBfXTwCfZBZA
VBaXUxp51a7b7JlwBH0C5Xs=
=z8v9
-----END PGP SIGNATURE-----
--==========993232BBBA694884AC4D==========--
