[Bp_ipv6] Call for Comments for Contents of the "Problem Definition/Introduction" [ Before Mon 8th June UTC2:00am]
pablo at apnic.net
Thu Jun 4 04:55:24 EDT 2015
I have provided small edits to the docs shared by Susan.
I hope that the document will remain open for comments throughout the
whole drafting process until publication. Ok to assume this?
On 6/4/15, 12:32 PM, "Izumi Okutani" <izumi at nic.ad.jp> wrote:
>I welcome your comments for contents to be incorporated in "Problem
>Definition/Introduction" until Mon 8th June UTC2:00am.
>Note that the text still needs to be improved in future steps but at this
>point, would like to hear your inputs on the components to be added.
>We have identified through our discussions:
> - The group's focus to be on creating an environment for IPv6 adoption
>and not IPv6 adoption itself
> - The challenge in creating such environment is : It is not effective
>enough to do it on your own, and different stakeholders need to
>collaborate (Within an organisation, within the same service layer, cross
> - As barriers of adoption/area which needs improvements, issue of
>suppliers readiness, need of more information sharing and bridge
>awareness gaps in business users (endsite networks) were raised
> - Awareness by non-technical CxOs in an organization may also be an
>issue (if reverse and try to see an issue from the target identified)
> - There are two motivation factors for IPv6:
> 1. There will be issues by not adoption it - as IPv4 runs out
> 2. Positive future factors: Large scale use (Mobile, smartgrid), new
>model of client to client communications (homenet, IoT)
>Is there anything else to be added in the Problem Statement/Definition?
>For "different stages of adoption" which has been suggested to include as
>Problem Definition, I welcome your comments based on description in [For
>[Current Draft Text]
>Widespread adoption of IPv6 is important to maintaining the global reach
>and integrity of the Internet. Following wide-spread adoption, the
>eventual transition to IPv6 will only be successful when we, as a
>community, are all moving together at the same time. Adoption of IPv6 by
>a single entity is often a challenge; it is not useful if one
>organization alone adopts IPv6 when the majority of the Internet is based
>on IPv4. The long-term sustainability of the network and success of the
>Internet to accommodate IPv6 depends on getting more organisations to
>adopt IPv6. There are ways in which different stakeholders with different
>roles can each contribute to IPv6 adoption.
>*Why Adopt IPv6? (benefits/reasons)*
>- Wider applications beyond conventional use such as homenet, which can
>lead to client to client communication rather than the client server
>- IPv4 exhaustion
>Internet Protocol (IP) addresses uniquely identify devices on the
>Internet. Currently, almost all devices connected to networks use the IP
>version 4 (IPv4) address system. IPv4 has more than 4 billion possible
>address combinations, but these are being used up quickly. APNIC reached
>its last block of IPv4 addresses in April 2011.
>[For Further Discussions]
>On different stages of adoption suggested as the problem definition,
>there was a comment that a general status description would be helpful.
>At the same time an observation was made whether this is something to be
>covered as the problem definition. A suggestion was made for an
>alternative contents to cover. Miwa - would you mind to re-share what was
>share in the chat?
>Further, a suggestion was made to touch on this as future recommended
>steps as a message to businesses.
>I'd welcome your comments on the above discussions at the call and the
>way forward in handling this.
>Suggested different stages of adoption
>Izumi on behalf of the MAG Coordinators
>Bp_ipv6 mailing list
>Bp_ipv6 at intgovforum.org
More information about the Bp_ipv6