[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    6renum [was Re: SAILing LAPs - longer prefixes not about address conservation.]
From:       Brian E Carpenter <brian.e.carpenter () gmail ! com>
Date:       2018-06-27 21:30:32
Message-ID: 05010d85-f53f-d184-42e8-1d0277145c81 () gmail ! com
[Download RAW message or body]

We did discuss all this in 6renum. There's still unfinished business
from https://tools.ietf.org/html/rfc7010 and of course prefix-per-host
would add to that list.

Regards
   Brian

On 28/06/2018 06:50, Fred Baker wrote:
> 
> 
> > On Jun 26, 2018, at 6:11 PM, Nick Hilliard <nick@foobar.org> wrote:
> > 
> > The difficulty with renumbering relates to how to reconfigure all of the devices \
> > where the address / netmask tuple has been pinned down manually.  E.g. in an isp \
> > provisioning system, or on HR's printer configuration on their laptops, or on the \
> > corporate firewalls or whatever.
> 
> Thanks for pointing this out. When we were writing what is now RFC 4192, I think \
> you and I spoke at some length on this exact topic. The introduction of that note \
> starts out: 
> The Prussian military theorist Carl von Clausewitz [Clausewitz]
> wrote, "Everything is very simple in war, but the simplest thing is
> difficult.  These difficulties accumulate and produce a friction,
> which no man can imagine exactly who has not seen war....  So in war,
> through the influence of an 'infinity of petty circumstances' which
> cannot properly be described on paper, things disappoint us and we
> fall short of the mark".  Operating a network is aptly compared to
> conducting a war.  The difference is that the opponent has the futile
> expectation that homo ignoramus will behave intelligently.
> ....
> This document addresses the key procedural issues in renumbering an
> IPv6 [RFC2460] network without a "flag day".  The procedure is
> straightforward to describe, but operationally can be difficult to
> automate or execute due to issues of statically configured network
> state, which one might aptly describe as "an infinity of petty
> circumstances".  As a result, in certain areas, this procedure is
> necessarily incomplete, as network environments vary widely and no
> one solution fits all.
> 
> Yes, static configuration. It's everywhere, and it means that one cannot \
> automatically do very much with addresses or prefixes without taking the static \
> configuration into account. 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]