{"id":66287,"date":"2017-11-12T12:00:31","date_gmt":"2017-11-12T12:00:31","guid":{"rendered":"https:\/\/www.internetsociety.org\/?p=66287"},"modified":"2025-06-06T20:31:04","modified_gmt":"2025-06-06T20:31:04","slug":"deploy360ietf100-day-1-ipv6-iot","status":"publish","type":"post","link":"https:\/\/www.internetsociety.org\/es\/blog\/2017\/11\/deploy360ietf100-day-1-ipv6-iot\/","title":{"rendered":"Deploy360 at IETF 100, Day 1: IPv6 and IoT"},"content":{"rendered":"
\n

This week is the one hundredth meeting of the IETF<\/a>\u00a0in Singapore, and to celebrate the occasion we’re bringing you daily blog posts highlighting some of the topics that Deploy360<\/a>\u00a0is interested in. And once again, Monday is our busiest day with no fewer than 7 working groups covering the areas of IPv6 and the Internet-of-Things.<\/p>\n

The day kicks off at 09.30 SGT\/UTC+8 with DNSOP<\/a>\u00a0(which continues on Thursday) and has a full agenda with 11 drafts up for discussion. An important draft<\/a> discussing the\u00a0RFC5011<\/a> rollover strategy has failed to reach consensus, with another draft defining and clarifying DNS terminology<\/a> requiring further review.<\/p>\n

The Working Group has picked up a draft on extending error messages to\u00a0better report the cause\u00a0of DNS and DNSSEC failures, whilst the draft updating\u00a0RFC6761<\/a> to ensure \u00ablocalhost\u00bb can be safely relied upon as a name for the local host’s loopback interface<\/a> should now be close to WGLC.\u00a0There’s also Deploy360 involvement in a new draft on the\u00a0requirements for a\u00a0validator to be able to perform accurate validation<\/a>, with Dan York<\/a> being one of the co-authors.<\/p>\n

\n

NOTE:<\/strong>\u00a0If you are unable to attend IETF 100 in person,\u00a0there are multiple ways to participate remotely<\/a>.<\/p>\n

\n

Running at the same time is LPWAN<\/a> that also has a busy agenda with 8 drafts being discussed. This includes an informational overview of the LPWAN technologies being considered by the IETF<\/a>, and others related to IPv6 header fragmentation and compression<\/a>\u00a0and\u00a0ICMPv6 usage over LPWANs<\/a>.<\/p>\n<\/div>\n

\n

After lunch is V6OPS<\/a> at 13.30 SGT\/UTC+8 (which continues on Thursday). This will start with a case on\u00a0study on IPv6-only deployment at Cisco, before moving to discussing\u00a0common scenarios for connecting an enterprise network to multiple ISPs using address space assigned by an ISP<\/a>. Another interesting draft is\u00a0an extension to the Happy Eyeballs protocol<\/a> in order to report IPv6 failures that force the fall-back to IPv4 and facilitate the troubleshooting of IPv6 network<\/p>\n

Also running in parallel is IDR<\/a>, that has two\u00a0proposals for addressing the problem of route leaks – Methods for Detection and Mitigation of BGP Route Leaks<\/a>, and Route Leak Prevention using Roles in Update and Open messages<\/a>.<\/p>\n

Following the afternoon break, there’s a choice of two IoT and IPv6 related Working Groups at 15.50 SGT\/UTC+8.\u00a0Homenet<\/a>\u00a0develops protocols for residential networks based on IPv6, and is discussing a variety of updated and new drafts. How the Babel routing protocol can be used in conjunction with the HNCP protocol in a Homenet scenario<\/a>\u00a0is currently in WGLC, whilst there\u2019s a new version of the name resolution and service discovery architecture for homenets<\/a>.<\/p>\n

Over at 6TiSCH<\/a>, the main items for discussion are related to the 6top protocol<\/a> that enables distributed scheduling, and defining the security functionality<\/a>.<\/p>\n

The day concludes with IPWAVE<\/a>\u00a0at 17.40 SGT\/UTC+8. This is discussing\u00a0a specification for transmitting IPv6 datagrams over IEEE 802.11-OCB in Vehicle-to-Internet and Vehicle-to-Infrastructure communications<\/a>,\u00a0defining the use cases for IP-based vehicular networks,<\/a>\u00a0and will cover\u00a0IPv6 Neighbour Discovery in Vehicle Networks\u00a0time permitting.<\/p>\n

Please note that the TLS<\/a> meeting scheduled for today has been cancelled, although the planned session on Wednesday (09.30-12.00 SGT\/UTC+8) will still go ahead.\u00a0<\/strong><\/p>\n

For more background, please read the\u00a0Rough Guide to IETF 100<\/a>\u00a0from Olaf, Dan, Andrei, Steve, Karen and myself.<\/p>\n

Relevant Working Groups<\/h3>\n