Date: Tue, 12 Jun 2001 08:56:29 -0700
From: "Christian Huitema" <[EMAIL PROTECTED]>
Message-ID:
<[EMAIL PROTECTED]>
| But first, let's agree on the scenarios. Do we believe that they are
| realistic?
They look reasonable to me.
| Can we qualify them with a "frequency indicator," e.g. once
| in a life-time, once a year, once a month, once a day?
Given that #5 needs to be N times a day (twice as stated), if we can
handle that one, then we should be able to handle all the others up to
at least once a day frequency, even if they're not likely to occur
nearly that often.
| Is there a big scenario that we are missing,
I'm sure there are other rationales for renumbering that can be invented,
but (other than as noted below) they all turn into add a prefix and/or
delete a prefix, and those seem to be covered...
| such as maybe provider mandated renumbering,
Aside from having less other (unrelated to addressing) configuration
changes to manage (no new leased lines, or changed phone numbers, etc)
this is no different from changing providers. So it is covered.
But ...
| or the merging of independent sites?
This one is the noticeably different case. That's where the internal
numbering of a site may need to be radically altered (there isn't one
change that applies everywhere). So, this one can be noticeably harder,
at the very least, a new addressing plan needs to be created. That's
not needed for any kind of external prefix change (another of the benefits
of having fixed sized address block allocations from all providers).
Fortunately though, this one generally is a rare event, is usually known
and can be planned for well in advance, and the disruptions that occur
are usually occurring in all kinds of other fields as well, not just the
network, so people tend to be a little more forgiving (eg: people are more
likely to curse when the merged payroll division doesn't manage to get
anyone's salary paid on time, than when the net is flaky for half a day
due to the numbering changes not having propagated properly).
Lots of other internal renumbering events follow much the same pattern.
These ones are the ones least worth worrying about (not that making them
easier won't be a benefit, just they're not the highest priority).
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]
--------------------------------------------------------------------
