% Sat, Apr 19, 2003 at 05:24:39PM -0700, Bill Manning:
% > % >>> So, unless there's some routing revolution, you're just going to have
% > % >>> to learn to deal with multiple addresses, and unless LL addresses go
% > % >>> away, you're also going to have to deal with scoped addresses.
% > % >>
% > % >> LL use can and should be reserved for bootstrapping and diagnostics.
% > % >
% > % > LL is used in applications already. e.g LL addresses are commonly used
% > % > to address BGP endpoints on exchanges.
% > %
% > % What exchanges do that?
% > %
% > %
% > % Joe
% >
% >
% > Akira Kato and I had a draft out on how this could be done
% > and had working, inter-operable implementations (zebra, cisco)
% > in two locations, NSPIXP3 and LAIIX.
%
% but, why?
why not? back in the day, the pier wg identified several
apps that did not take to renumbering well. BGP was one.
couple that with the oddities of small bits of address
space that are needed at exchanges (and do not play well
w/ the (non)compelling arguements for aggregation) and it
seemed reasonable that, if massive aggregation was an
inevitable feature of IPv6, that moving exchange point
communications to linklocal addresses would make many
things simpler. No "special-use" ranges in v6 land
for exchanges. But it was not to be. Check the IDR
archives for details.
we now have special blocks of IPv6 space that are not
supposed to be aggregated for things like exchanges.
massive aggregation is expected, except for these "special
prefixes". One more administrative thing to track. :(
--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).