Pekka, > Pekka Nikander wrote: > First of all, there is no such thing as an absolute > guarantee for global uniqueness. Misconfigurations > happen. Thus, the real difference between the "split > space" and "mixed space" model is that in the split > space model, *nobody* is *supposed* to configure or > use a registered prefix, while in the mixed space > model someone *may* legitimitely use it. However, > even in the mixed space model the party having > preformed the registration has some kind of > ownership/moral property rights over the prefix, > giving them more rights over those that haven't > registered the prefix but happen to be using it > anyway.
We are not trying to design a protocol that fixes stupidity. > Now, the case seems to depend on psychology and the > formulation of rights. In the split space case the rights > are easier to formulate, more natural, and stronger in that > sense. Nobody is supposed to use your prefix, and therefore > they are wrong if they use your prefix, and you can sue them > (or, in Europe, you can dispise and ignore them :-) Exactly. And this is worth a few bucks, although I would agree that it's not worth more than a few bucks. But it would be an easier sale to lots of people, with or without good reasons for it. More on the split model deal: So far we have discussed a split model where the address allocation for the "truly unique" is the same as for the "good enough". I agree that the split model does not bring much, but I don't agree that it cancels the "use now register later" feature. Even in a split model, you could have registration of addresses in the block that is used for the random/hash algorithm, and still have the truly unique block. In other words, you could register a truly unique prefix if you register up front, and also register a "good enough" if you used it without registering and later want to register it. Note that the proposal I have for "truly unique" is based on geography and will require split space as it could also be used to seed identifiers in a dual-space identifier/locator multihoming solution. 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] --------------------------------------------------------------------
