IPv6 has again been hitting the headlines this year, with several sources reporting global IPv6 adoption rates of well over 10%, but perhaps more importantly, substantial increases in IPv6 capability in major Internet markets. A number of large ISPs are actively deploying IPv6 in anticipation of IPv4 address exhaustion and in response to the costs of ever increasingly network complexity using NAT’ed private IPv4 addresses. Apple also mandated that all iOS apps support IPv6 only networks starting from 1 June, whilst there was even an Internet draft presented at the last IETF that proposed to move IPv4 (as defined by RFC 791) to historic status and therefore no longer recommended for use on the Internet.
IPv4 is likely to be around for a while yet, but both the IPv6 Operations (v6ops) and IPv6 Maintenance (6man) Working Groups will be meeting at IETF 96 in Berlin next week, along with several other working groups that are defining protocols based around IPv6.
The Homenet Working Group develops protocols for residential networks based on IPv6 and will meet on Monday afternoon. Since the last IETF, it has had RFCs 7787 (https://tools.ietf.org/html/rfc7787) and 7788 (https://tools.ietf.org/html/rfc7788) published which define the Distributed Node Consensus Protocol (DNCP) and the Home Networking Control Protocol (HNCP) that can be used for automated configuration of addresses, name resolution and service discovery. There’s also one updated draft being discussed (draft-lemon-homenet-naming-architecture-01) on the Homenet Naming and Service Discovery Architecture that covers how services advertise and register themselves both on the homenet and public Internet, as well as a further draft (draft-ietf-homenet-babel-profile-00) adopted by the working group on how the Babel routing protocol can be used in conjunction with HNCP protocol in a Homenet scenario. In addition, HNCP deployment experiences will be related, along with how the protocol interacts with .home naming.
The IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch) Working Group also meets on Monday afternoon and will discuss the results of the plug tests, as well as two drafts (draft-dujovne-6tisch-6top-sf0-01 and draft-wang-6tisch-6top-protocol-00) related to neighbour-to-neighbour negotiation. The IPv6 over Networks of Resource-Constrained Nodes (6lo) Working Group is meeting earlier the same day, and whilst there’s currently no agenda published, drafts relating to security and privacy have recently been discussed on the mailing list.
The IPv6 Maintenance (6man) Working Group meets on Tuesday morning to discuss a tranche of drafts dealing with updates to the IPv6 specification, addressing architecture and path MTU discovery as currently defined in RFC 2460 (https://tools.ietf.org/html/rfc2460), RFC 4291 (https://tools.ietf.org/html/rfc4291) and RFC 1981 (https://tools.ietf.org/html/rfc1981). There’s also a last call on the draft recommendation (draft-ietf-6man-default-iids) to change the default interface identifier (IID) generation scheme where SLAAC is used to generate a stable IPv6 address. Along similar lines is another draft on generating non-stable addresses (draft-gont-6man-non-stable-iids-00) that are not predictable for security reasons, whilst further two drafts (draft-carpenter-6man-whats-global-00 and draft-bchv-rfc6890bis-00) aim to clarify the unclear use of ‘global’ in the context of IANA special purpose IPv6 address registries. Last but not least, there’s a new draft dealing with the issue of multihoming using provider-assigned addresses without using network prefix translation.
To round off the week IPv6-wise, the IPv6 Operations (v6ops) Working Group will meet on Thursday afternoon. Again there’s no agenda published at the time of writing, although recently discussed drafts include IPv6 multicast addresses in vehicular networks, transmission of IPv6 Packets over IEEE 802.11-OCB networks, the use of unique IPv6 prefixes by hosts on a shared network, and operational security considerations when operating an IPv6 network.
At the Internet Society, we continue to promote IPv6 deployment. You can check out the World IPv6 Launch measurements for our latest measurements of IPv6 around the globe: http://www.worldipv6launch.org/measurements
You can also check out the Deploy360 online resources for getting started with IPv6 deployment:
And you can read more about other topics of interest to the technology programs of the Internet Society in the rest of our Rough Guide to IETF 96 posts.
Some IPv6 Working Groups at IETF 96:
v6ops (IPv6 Operations) WG
Thursday, 21 July 1400-1600 UTC+2, Potsdam I
6man (IPv6 Maintenance ) WG
Tuesday, 19 July 1000-1230 UTC+2, Bellevue
Homenet (Home Networking) WG
Monday, 18 July 1400-1530 UTC+2, Potsdam I
6lo (IPv6 over Networks of Resource Constrained Nodes) WG
Monday, 18 July 1000-1230 UTC+2, Potsdam III
6tisch (IPv6 over the TSCH mode of IEEE 802.15.4e)
Monday, 18 July 1400-1530 UTC+2, Bellevue
There’s a lot going on in Berlin, and whether you plan to be there or join remotely, there’s much to monitor. To follow along as we dole out this series of Rough Guide to IETF blog posts, follow us on the Internet Technology Matters blog, Twitter, Facebook, Google+, via RSS, or see http://dev.internetsociety.org/rough-guide-ietf96.