Date: Fri, 4 May 2001 11:15:21 +0300 (EEST)
From: Pekka Savola <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| When considering these options, please note that site-local addresses may
| also need to be renumbered (probably often at the same time when
| subnetting of global addresses changes).
This is certainly true, but this is a completely different kind of
event.
This one is a self-inflicted renumbering requirement, for whatever reason
a site has decided that some of its nodes have to be renumbered. This
almost always only applies to some of the nodes (a busy subnet is being
split into two nets, or whatever).
Because of this, the site can plan the event as it likes, give itself
any amount of changeover time, and assess the cost/benefit tradeoff of
doing the change in the first place.
Then, because it is the internal part of the number space that is
being altered, it is much less likely that (aside from written forms
of particular host addresses) the changes will affect other sites - that
is, it isn't very likely that someone will be filtering one subnet of
your site and not others without your knowledge, that kind of thing is
usually all or nothing. So you're not likely to suffer because of
lack of reconfig at other sites.
The renumbering that really hurts is the one you're forced into - where
you're given a period of N (days/weeks/months) and told that after that
your old number will no longer be valid. No options.
This isn't to imply that any renumbering is easy - but the (almost always)
partial renumber that results in subnet numbers changing is by far the
easier one to deal with. Most of us deal with that kind of event quite
regularly.
kre
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
