Robin, >-----Original Message----- >From: Robin Whittle [mailto:[EMAIL PROTECTED] >Sent: Tuesday, April 01, 2008 4:37 PM >To: [email protected] >Cc: Templin, Fred L; Xu Xiaohu; Dino Farinacci; Noel Chiappa >Subject: Re: [RRG] What does incremental deployment mean > >Hi Fred, > >Thanks - I should have remembered this: > >> ISATAP allows dual-stack nodes to discover routers that >> can reach destinations on the global IPv6 Internet. >> >> ISATAP is already widely implemented and deployed; in >> many deployments it is even turned on by default. > >but it doesn't alter my understanding that it is not a solution to >the IPv4 routing scaling problem, because the only way it helps is >with hosts which are dual-stack and with applications which in fact >communicate via IPv6.
The "domain of applicability" does not explicitly say this, but dual-stack routers (or "hosts" that forward packets on behalf of other nodes) are also within the realm of application. That means that you can stack up an arbitrarily large IPv6 network behind an ISATAP "host". >Also, ISATAP is a transition mechanism, requiring an IPv4 address. A private IPv4 address; yes. There are lots of those available within end sites without impacting routing scaling within the core. >So its only contribution to the IPv4 routing and addressing problem >would be to facilitate wide enough adoption of IPv6 that significant >numbers of end-users would be happy to have IPv6-only addresses, >with no IPv4 direct connectivity. No; not IPv6-only. Use address selection rules to determine the appropriate address for use under the appropriate circumstances. Sometimes that means IPv6 and other times that means IPv4. Fred [EMAIL PROTECTED] >That won't I happen, I think, >until some very large proportion of hosts in general have IPv6 >connectivity - 90%? 99%? 99.9%? > > - Robin > > -- to unsubscribe send a message to [EMAIL PROTECTED] with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
