IPv6 remains an important aspect of the standardization work within the IETF, with much activity next week at IETF 95 in Buenos Aires. IPv6 deployment hit 10% earlier this year according to Google IPv6 statistics, and whilst other sources such as APNIC Labs and Akamai show slightly lower adoption rates, IPv6 usage continues to grow a steady rate as Regional Internet Registries assign their last remaining IPv4 addresses. There’s also evidence from both the RIRs and commercial transfer market that IPv4 address transfers as well as use of legacy addresses (i.e. those allocated before 1997) increased substantially in 2015, reflecting the limited availability of new IPv4 address blocks.
Both the IPv6 Operations (v6ops) and the IPv6 Maintenance (6man) Working Groups are meeting at IETF 95 in Buenos Aires next week. It’s perhaps worth highlighting first though, that a new draft https://tools.ietf.org/html/draft-howard-sunset4-v4historic-00 is up for discussion at the Sunsetting IPv4 Working Group on Tuesday evening. This proposes to move IPv4 (as defined by RFC 791) to historic status and thereby no longer recommended for use on the Internet. Whilst this may not reach RFC status, it has generated some interesting discussion as well as media comment as to the implications of the IETF no longer actively working on IPv4 technologies.
Returning to more practical matters, the IPv6 Operations (v6ops) Working Group has just two drafts up for discussion. The draft draft-gont-v6ops-ipv6-ehs-packet-drops-03 has been generating significant discussion on the v6ops mailing list as it concerns the observed dropping of packets with certain extension headers. The other draft under discussion draft-smith-v6ops-mitigate-rtr-dos-mld-slctd-node-02 is concerned with mitigating potential denial-of-service attacks via multicasting.
The final item on the agenda of v6ops is the LACNIC report on IPv6 deployment in Latin America and the Caribbean. This is a comprehensive survey of the current state of IPv4 exhaustion, case studies of IPv6 deployments, but perhaps more interestingly the problems, challenges and regulatory barriers that were experienced. The report also provides insight into the rationale of those ISPs not currently considering the deployment of IPv6.
The IPv6 Maintenance (6man) Working Group will be meeting on Wednesday morning and will continue to discuss the proposed updates to the IPv6 specification, addressing architecture and path MTU discovery as currently defined in RFC 2460, RFC 4291, and RFC 1981. There are also two working group drafts relating to extension headers for routing ( draft-previdi-6man-segment-routing-header-08) and hop-by-hop options ( draft-ietf-6man-hbh-header-handling-03) which allow for differential handling of packets by forwarding and control planes in routers. A further draft draft-van-beijnum-multi-mtu-05 has the aim of allowing larger packet sizes (MTUs) to be negotiated on Ethernet provisioned links that are able to support so-called jumbo frames.
The Homenet Working Group has a busy agenda on Tuesday afternoon as it continues to develop protocols for residential networks based on IPv6. The primary focus is on autoconfiguration, naming architecture and service discovery, as well as multiple interfacing support in home-type scenarios, but two important new drafts will also be discussed. The Homenet profile of the Babel routing protocol used in conjunction with the HNCP protocol defines how Babel should be used in a Homenet scenario ( draft-chroboczek-homenet-babel-profile-00), whilst the Homenet Naming and Service Discovery Architecture covers how services advertise and register themselves both on the homenet and public Internet ( draft-lemon-homenet-naming-architecture-00). The security aspects of this will also be covered in a presentation during the session.
The IETF is also looking into the issues of implementing IPv6 on nodes with limited power, memory and processing resource with a view towards the future Internet-of-Things. The IPv6 over Networks of Resource-Constrained Nodes (6lo) Working Group is scheduled to meet on Thursday afternoon, whilst the IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch) Working Group meets on Monday afternoon with a new charter and plug testing on the agenda. The Routing Over Low Power and Lossy Networks (roll) Working Group on Tuesday afternoon will also consider the usage of IPv6 in very low power devices that have differing requirements in terms of their maximum MTUs.
Whilst these are the IPv6 specific sessions, other working groups need to take IPv6 into consideration as it evolves into a core Internet protocol. The Operational Security Capabilities for IP Network Infrastructure (opsec) Working Group on Tuesday afternoon has three IPv6-specific drafts on the agenda. The draft draft-georgescu-opsec-ipv6-trans-tech-threat-model-00 outlines an approach for risk assessment of IPv6 transitional technologies using the STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of service and Elevation of Privilege) classification, whilst draft-ietf-opsec-v6-08 analyses the different security considerations between IPv4 and IPv6 in particular parts of the network. The last of the drafts under discussion draft-gont-opsec-ipv6-firewall-reqs-03 addresses the requirements for IPv6 firewalls that have not been specified or recommended in RFCs to-date.
Finally, the Routing Area Working Group (rtgwg) on Thursday morning will have a discussion around multi-homing for provider assigned IPv6 addresses as well as homenets. A related draft is draft-ietf-rtgwg-dst-src-routing-01 which covers the issue of IPv6 networks using packet source addresses for making routing decisions, especially on small multi-homed networks with dynamic addressing.
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 95 posts.
Some IPv6 Working Groups at IETF 95:
v6ops (IPv6 Operations) WG
Monday, 4 April 1400-1500 UTC-3, Buen Ayre C
6man (IPv6 Maintenance ) WG
Wednesday, 6 April 1000-1230 UTC-3, Buen Ayre C
sunset4 (Sunsetting IPv4) WG
Tuesday, 5 April 1740-1910 UTC-3, Buen Ayre C
Homenet (Home Networking) WG
Tuesday, 5 April 1400-1600 UTC-3, Pacifico A
6lo (IPv6 over Networks of Resource Constrained Nodes) WG
Thursday, 7 May 1730-1930 UTC-3, Pacifico A
6tisch (IPv6 over the TSCH mode of IEEE 802.15.4e)
Monday, 4 April 1400-1530 UTC-3, Buen Arye B
roll (Routing Over Low power and Lossy networks)
Tuesday, 5 April 1620-1720 UTC-3, Quebracho B
opsec (Operational Security Capabilities for IP Network Infrastructure)
Tuesday 5 April 1620-1720 UTC-3, Buen Ayre A
rtgwg (Routing Area Working Group)
Thursday, 7 May 1000-1230 UTC-3, Buen Ayre C
Friday, 8 May 1000-1200, Atlantico C
There’s a lot going on in Buenos Aires, 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 https://dev.internetsociety.org/tag/ietf95/.