-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
On 04.04.2013 17:02, Michael Richardson wrote: > I think that imadali-its-vinipv6 is the wrong idea. If it is > useful for a manufacturer to derive a subnet-ID from a VIN, that's > fine, but I think it's a private matter. Let's write a BCP on how > a manufacturer might do this in a way such that the the VIN <-> > subnet prefix mapping is neither reversable, nor is it > reproduceable. (I.e. I can't get the VIN from the subnet-ID, and I > also can't get the subnet-ID from the VIN) > > Only the manufacturer *might* know the mapping, and maybe we can > write the BCP such that the manufacturer can forget it too. The > manufacturer likely goes to get RIR space just like any other > Enterprise. Our initial proposal [1] was to use rightbits(SHA-2(VIN | OEM-specific-256bit Key), 40) to algorithmically generate the Global-ID of a ULA-Prefix. As long as the key is kept secret, it would not be reversable or derivable from the VIN. Using a global prefix from an RIR is certainly another viable alternative. [1] http://www.lara.prd.fr/_media/ipv6-its/2012-03-26-seis-kit-ietf83-its.pdf Regards, Roland -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFdo0YACgkQ1YyfLd659kfWvACgx5jchyyAQ1fR2hPVoMsD8dEp a4QAoLnEm1BhSR3piHX4nutLdBpNhRXK =2g2s -----END PGP SIGNATURE----- -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
