Deploy360 IETF

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

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