1. In the "be liberal what you accept" approach, solving a network problem by stating that you "should always get the same prefix" seems imprudent engineering. You have to assume that the prefix for provider-supplied address space will change from time to time, and design your network to deal with that. I am NOT suggesting that I know what the right answer is.
2. To me the scenario that is very hard to deal with given only routable space is the intermittent connection case. I think of this as a formation of cooperating nodes (the hain/templin draft uses a ship, but I am also interested in formations of data-gathering drones or satellites, or clusters of devices with wireless connections). In many cases the internal connections within the cluster are more critical than the external ones. Routable PA space won't work. Using local addresses (but not link-local, IMHO) is certainly one solution. Mobile IP may work, but I am not convinced about that, and in any case it adds "weight" to the network and the nodes.
--On Monday, August 25, 2003 19:55 +0200 Leif Johansson <[EMAIL PROTECTED]> wrote:
Tony Hain wrote:
Leif Johansson wrote:
... Patrik posed a few direct questions to this effect on the list - none of which have been answered.
I must have missed them, so please send a pointer to the questions.
Tony
Unfortunately there does not seem to be a hypertext archive of the list but the post was from 2003-07-08:
=============== paf ===========
I don't know how to attack the people which talk about "intermittent connected networks".
The problem I see is that people are locked into the IPv4 world where a DSL modem have one address which might change every connect. That is extrapolated into one IPv6 prefix which changes every connect.
Instead, to me, the user should get the _same_ IPv6 prefix every time he connects. As long as one connect to the same upstream network, the IPv6 prefix should not have to change. And, switching upstream network will force a switch in prefixes of course. The renumbering event comes when _connecting_, not disconnecting and connecting as the address can be kept until a new prefix is to be used.
Is this not true?
Further, we do not have a good session layer in the IETF which means a network _always_ have to reset the connections when a renumbering happens, which is the same as a more drastic network topology change happens. The solution to this is mobile IP.
What else? What's so difficult here?
paf
============= paf ============
-------------------------------------------------------------------- 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] --------------------------------------------------------------------
Hans Kruse, Associate Professor J. Warren McClure School of Communication Systems Management Adjunct Associate Professor of Electrical Engineering and Computer Science Ohio University, Athens, OH, 45701 740-593-4891 voice, 740-593-4889 fax -------------------------------------------------------------------- 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] --------------------------------------------------------------------
