Hello Wei,
As Aftab suggested, OIDs are already globally unique identifiers. The idea of hash mapping an OID into an IPv6 address is a bad idea, because you cannot guarantee that the OID will match the IP space delegated to you. There is also no guarantee that the Secretariat will be able to delegate IP space requested from a certain block.
The customer has leveraged these IPv6 addresses to create corresponding QR codes in URL format, such as "http://[1234:5678::90AB]". This ensures a one-to-one correspondence between an item, its product code, and its IPv6 address.
If I am managing a large inventory of server components and decided to use IPv6 addresses as a unique identifier for each component, then created a QR code containing a HTTP URL which when scanned with a mobile device opened a web page that contained information about that specific component, then justification of the IP space would be to serve content over the internet, not for unique identification of my server components and IP space could be delegated under existing policies if approved by the Secretariat.
For this and other reasons as identified by other members of the community, I do not support and oppose this proposal.
Regards,
Christopher Hawker
_______________________________________________ SIG-policy - https://mailman.apnic.net/[email protected]/ To unsubscribe send an email to [email protected]
