I agree of the potencial benefits of reserving bits in the IID for future "useful" use in the future, specialy in the mobility area. In that sense, i will like any references to EUI-64 based identifiers and the use of u/l bit being removed from 2473 as being already a proposal for making use of one "bit".
So my suggestion is option 4: to reserve u and g bits (call them something else, pls) and follow the normal IETF standards track process to decide the (how to) use of them. I want to stick to the question of Erik but i argue why nodes for example that want to use a privacy extension (RFC3041) have to indicate that their IID is not EUI-64 based and hence the use of the privacy extension is observable. /aep -- -------------------------------------------------------------------------- That you are not paranoid, it doesn't mean that they are not watching you! http://www.it.kth.se/~aep > The purpose of *reserving* the bit(s) is to leave the door open > to assign the bit(s) to something, hopefully useful, in the future. > But, as pointed out in my original email on the subject, any such proposal > for *using* the reserved bits for something, would need to go through > the normal IETF standards track process. > Reserving the bits just requires the analysis whether the cost of > carving off the bits is worth the potential benefits of being able to > use them for something in the future. > > Is that more clear? > > Erik > > -------------------------------------------------------------------- > 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] > -------------------------------------------------------------------- > -------------------------------------------------------------------- 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] --------------------------------------------------------------------
