Pekka, >> Michel Py wrote: >> My $0.02 about the hash/random/collision issue: >> It's a non-issue.
> Pekka Nikander wrote: > I would agree with you, but only if I shared the same > view of the GUPI prefix usage. This much is clear. However, I think the use you envision for GUPI is dangerous and will lead to NAT, which is also clear in the opinion you expressed about GUPI encouraging or discouraging NAT. In the example you use, a SOHO configuring their network, use of GUPI is a disaster, IMHO. Site-locals are not for SOHO sites, they need to talk to the public Internet. These people need to use global addresses. I don't challenge the need for globally unique PI addresses, but this would be GAPI not GUPI. As I mentioned before, we MUST NOT encourage the use of site-locals for people that don't understand their limitations, and this certainly applies to the SOHO example you used. GUPI still is site-local addresses, which are not routable on the public Internet, and will be successful in enterprises only if the comfort level of the administrator as reached the level that he is happy with the enforcement of non-routability. Back to what started this, the main four characteristics of GUPI are: 1. No fee and/or low fee. 2. No registration and/or easy registration. 3. Globally unique. 4. Not globally routable. I don't challenge the need for globally routable, globally unique identifiers. As a matter of fact, the scheme I proposed for GUPI is a spin-off GAPI. That being said, this is not the same battle. In the case of GUPI, we already have a block allocated for it: FEC0::/10. If we don't change the purpose of the block which is site-locals, there is a shorter path to success than GAPI that would require IANA to allocate a new block and is full of issues concerning the explosion of the global routing table. My message is: one problem at a time. GUPI is achievable short-term, not GAPI. Let's focus on what we can do now, which is globally unique, not globally routable and when this hurdle has been cleared then we can process towards globally unique and globally routable. Michel. -------------------------------------------------------------------- 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] --------------------------------------------------------------------
