prop-161: Using IPv6 for Internet of Things (IoT)

Proposal text prop-161-v002
Objective This proposal suggests explicitly stating in the policy document that IPv6 can be allocated to IoT objects, both electrical devices and non-electrical goods, and that the default IPv6 allocation size for IoT request is a /32.
Current status Withdrawn by the author
Authors Guangliang Pan (Benny)
Wei Wong (Wesley)
Qiang Li
Yaling Tan
Relevant forum Policy SIG
Previous versions prop-161-v001
Secretariat impact assessment

Impact assessment v002

The Secretariat notes that this proposal suggests explicitly stating in the policy document that IPv6 can be allocated to IoT objects, both electronic smart devices and/or for hosting information of non-electronic items, and Initial IPv6 allocation size for IoT request will be set to the minimum IPv6 allocation size as per the policy at the time of allocation.

Questions/Comments:

  • The usage of IPv6 for IoT is not a ground for rejection of requests for /48 assignments or /32 allocations under current APNIC policies.
  • The usage of IPv6 for “hosting information of non-electronic items on the Internet” would imply that the usage relates to connectivity which is independent of the non-electronic item itself and therefore would already be an acceptable use case. An organisation requesting IPv6 addresses for its own IoT deployment, as described, would appear to fall within the assignment criteria, rather than the allocation criteria.
  • The authors may consider suggesting updates to the IPv6 guidelines document (APNIC-114) to define different use cases and IP address planning for IoT.
  • With regard to the ‘Impact on resource holders’, the Secretariat notes that fees are set by the APNIC Executive Council and as such this policy should not be considered in the context of “help[ing] to reduce the APNIC membership fee.”

Implementation:

This proposal may require changes to APNIC systems. If this proposal reaches consensus, implementation may be completed within three months.

Proposal history
05 August 2024 Version 1 posted to the Policy SIG mailing list for discussion and community development.
19 August 2024 Version 2 posted to the Policy SIG mailing list for discussion and community development.
31 August 2024 Withdrawn by the author.