Donate
‹ Back
Deploy360 30 March 2017

Deploy360@IETF98, Day 4: IPv6, IoT & ACME

Kevin Meynell
By Kevin MeynellManager, Technical and Operational Engagements

Thursday at week IETF 98 in Chicago is another mix of IPv6, the Internet-of-Things and TLS-related working groups. Each day we’re bringing you blog posts pointing out what Deploy360 will be focusing on.

The first session of the day is 6MAN which has a last call on updates to the IPv6 specification as currently defined in RFC 2460, RFC 4291, and RFC 1981. There are also two new drafts under discussion related to recommendations on IPv6 address usage  and temporary IPv6 interface identifiers, plus a draft describing how a Distributed Denial of Service (DDoS) Open Threat Signaling (DOTS) client can send a message over a congested network by tagging outgoing IPv6 packets in order to reach a DOTS server.

Three current drafts include a description of common functionality that should be required on all IPv6 hosts and routers that has been collected from other published IETF Standards Track documents, definition of a new control bit in an IPv6 router advertisement indicating that a receiving node is the exclusive receiver of all traffic destined to any address with that prefix, and providing a backward-compatible extension to the Redirect function in the IPv6 Neighbour Discovery protocol to allow routers to include information that a recipient can associate with the next hop.


NOTE: If you are unable to attend IETF 98 in person, there are multiple ways to participate remotely.


The afternoon sees ACME which has been developing a standards-based REST API allowing agent software to authenticate that a server controls a domain, request a certificate, and then install it on a server without human intervention. This session is discussing some changes to the ACME specification, as well as the next steps for the group with a view to re-chartering.

Finally, there are two working groups of interest during the evening session. DHC has three DHCPv6 related drafts on the agenda, whilst ROLL continues development of  several routing protocols for resource constrained nodes.

For more background, please read the Rough Guide to IETF 98 from Olaf, Dan, Andrei, Mat, Karen and myself.

Relevant Working Groups

‹ Back

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

Related articles

Rough Guide to IETF 98: All About IPv6
IETF21 March 2017

Rough Guide to IETF 98: All About IPv6

In this post for the Internet Society Rough Guide to IETF 98, I’m reviewing what’s happening related to IPv6 at...

Rough Guide to IETF 101: IPv6
Rough Guide to IETF 101: IPv6
IPv614 March 2018

Rough Guide to IETF 101: IPv6

In this post for the Internet Society Rough Guide to IETF 101, I’m reviewing what’ll be happening at the IETF...

Rough Guide to IETF 100 - IPv6
Rough Guide to IETF 100 - IPv6
IETF8 November 2017

Rough Guide to IETF 100 – IPv6

In this post for the Internet Society Rough Guide to IETF 100, I’m reviewing what’ll be happening at IETF 100...

Join the conversation with Internet Society members around the world