Hello Benny, - I don't support this proposal. - It doesn't solve a problem I'm experiencing. - In terms of disadvantages, I think it mis-uses the Internet Protocol. I'll expand on this.
IPv6 as defined by RFC 2460 is the successor to IPv4, which is defined by RFC 791. Quoting the latter: "The Internet Protocol is designed for use in interconnected systems of packet-switched computer communication networks." I think a change in use of the key resource of the Internet Protocol as you have suggested is out of scope for the APNIC Policy SIG, and would be better addressed through a different forum. If you think IP addresses are the right solution to your problem, my recommendation is that you withdraw the proposal, and discuss the idea with members of the IAB. If you're open to other solutions, again, withdraw the proposal and check in with W3C: https://www.w3.org/TR/2022/REC-did-core-20220719/ Some combination of IEEE-registered entities (https://standards.ieee.org/products-programs/regauth/) and Decentralised Identifiers could provide well for assigning globally unique identifiers to arbitrary objects. - The proposal is clear to me - I don't think any changes could be made to make it more effective Regards, Jon On Mon, Aug 5, 2024, at 21:09, Bertrand Cherrier via SIG-policy wrote: > Dear SIG members, > > A new proposal "prop-161-v001: Using IPv6 for Internet of Things (IoT)" > has been sent to the Policy SIG for review. > > It will be presented at the Open Policy Meeting (OPM) at APNIC 58 on > Friday, 6 September 2024. > > https://conference.apnic.net/58/program/program/index.html#/day/8/ > > We invite you to review and comment on the proposal on the mailing list > before the OPM. > > The comment period on the mailing list before the OPM is an important > part of the Policy Development > Process (PDP). We encourage you to express your views on the proposal: > > - Do you support or oppose this proposal? > - Does this proposal solve a problem you are experiencing? If so, > tell the community about your situation. > - Do you see any disadvantages in this proposal? > - Is there anything in the proposal that is not clear? > - What changes could be made to this proposal to make it more effective? > > Information about this proposal is appended below as well as available at: > > http://www.apnic.net/policy/proposals/prop-161 > > Regards, > Bertrand, Shaila, and Anupam > APNIC Policy SIG Chairs > > > ----------------------------------------------------------------------------------- > > prop-161-v001: Using IPv6 for Internet of Things (IoT) > > ----------------------------------------------------------------------------------- > > Proposers: > Guangliang Pan (Benny) [email protected] > Wei Wong (Wesley) [email protected] > Qiang Li [email protected] > Yaling Tan [email protected] > > 1. Problem statement > ----------------------- > Internet of Things (loT) is part of the future Internet. However, there > is no clear IPv6 policy for IoT in APNIC’s current policy environment. > In some of the cases, the IoT industry needs to assign IPv6 to > electronic smart devices as well as non-electronic items. The > non-electronic items include company products and assets. IPv6 addresses > will be used as universally compatible identifiers for these > non-electronic items for the purpose of identification, verification, > and tracing. It is a bit difficult for APNIC Hostmasters to evaluate > such IPv6 requests without a clear policy to allow allocating IPv6 > addresses to non-electronic items. This policy proposal aims to address > this issue and meet the needs from the IoT industry. > > > 2. Objective of policy change > ------------------------------- > Add clear clauses about how IPv6 can be allocated to Internet of Things > in IPv6 policy. > > > 3. Situation in other regions > ------------------------------ > There are some discussions about “Need IPv6 in IoT” in other regions. > RIPE NCC has an “Internet of Things Working Group”. > > > 4. Proposed policy solution > ------------------------------ > 1. Add a new clause in IPv6 policy. > 8.2.3 Using IPv6 for Internet of Things (IoT) > IPv6 addresses can be allocated to IoT Objects which include electrical > devices and non-electrical items. A default initial IPv6 allocation size > for IoT is a /32. > > 2. Add the following sentence at the end of 8.3.4. Size of subsequent > allocation > An IoT Object will be counted as a normal single host while evaluating > subsequent allocation size for IoT services according to the IPv6 policy. > > 5. Advantages / Disadvantages > --------------------------------- > Advantages: > IPv6 has huge number of IP addresses and IoT needs huge number of IP > addresses. It is a perfect match connects APNIC community with the IoT > industry. Encourage using IPv6 for IoT will help IPv6 deployment in > future Internet. > > Disadvantages: > None > Not to worry about run out of IPv6. The original design of IPv6 was for > Internet of Things. You often hear IPv6 can be assigned to every single > sand in the world :) We can trust APNIC Hostmasters will do the > evaluation properly. > > 6. Impact on resource holders > -------------------------------- > No impacts to the current resource holders in the APNIC region. > > > 7. References > -------------- > > _______________________________________________ > SIG-policy - https://mailman.apnic.net/[email protected]/ > To unsubscribe send an email to [email protected] https://jon.brewer.nz/
_______________________________________________ SIG-policy - https://mailman.apnic.net/[email protected]/ To unsubscribe send an email to [email protected]
