Donate
IETF 101, Day 3: TLS & DPRIVE is no Diet Coke Thumbnail
‹ Back
Deploy360 20 March 2018

IETF 101, Day 3: TLS & DPRIVE is no Diet Coke

Kevin Meynell
By Kevin MeynellManager, Technical and Operational Engagements

This week is IETF 101 in London, and we’re bringing you daily blog posts highlighting the topics of interest to us in the ISOC Internet Technology Team. There’s plenty of variety on Wednesday, following the themes of Trust and Identity, IPv6 and the Internet-of-Things.

TLS has its second session of the week starting at 09.30 GMT/UTC, and will be focused on the big development of the TLS 1.3 specification being approved by the IESG. Some further work is required, but there are a number of TLS 1.3 related drafts up for discussion.

These include Datagram Transport Layer SecurityDTLS Connection Identifer,  Exported authenticators in TLSDANE Record and DNSSEC Authentication Chain Extension for TLS, TLS Certificate compression, SNI Encryption in Tunnelling via TLS, and Semi-static DH Key Establishment in TLS 1.3.


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


Running in parallel is LPWAN which is working on enabling IPv6 connectivity with very low wireless transmission rates between battery-powered devices spread across multiple kilometres. There’s a draft providing an overview of the set of LPWAN technologies under consideration by the IETF, two other working group sponsored drafts on LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP, as well as five individual drafts related to SCHC.

After lunch there’s a choice of DPRIVE or 6TiSCH starting at 13.30 GMT/UTC.

DPRIVE will have two major topics of discussion, starting with recommendations for best current practices for those operating DNS privacy servers, building on the work of the DNS Privacy Project. There will also be a discussion on how to add privacy to the communication between a DNS recursive resolver and the authoritative DNS server for a given domain.

Finally, given that original focus of the Working Group was on stub-to-recursive-resolver connections which is now basically done from a standards perspective, there is interest in moving to next phase of privacy. A discussion on how to re-charter the group has therefore been scheduled.

6TiSCH has a full agenda, with the 6top protocol that enables distributed scheduling now being targeted for an IESG Last Call, and the security functionality (https://tools.ietf.org/html/draft-ietf-6tisch-minimal-security-05 and https://tools.ietf.org/html/draft-ietf-6tisch-6top-sfx-01) being prepared for Working Group Last Calls.

ACME rounds off the day from 15.30 GMT/UTC, where the main order of business is the core specification of the Automatic Certificate Management Environments that has been submitted to the IESG for publication. The meeting will also discuss the TLS ALPN challenge that allows for domain control validation using TLS, as well as using STIR with ACME to provide cryptographic authentication for telephone calls.

For more background, please read the Rough Guide to IETF 101 from Olaf, Dan, Andrei, Steve, 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 101: Privacy, Identity, and Encryption
Rough Guide to IETF 101: Privacy, Identity, and Encryption
Encryption16 March 2018

Rough Guide to IETF 101: Privacy, Identity, and Encryption

It’s that time again! In this post of the Rough Guide to IETF 101, I’ll take a quick look at...

Rough Guide to IETF 99: A Sampling of Encryption-Related Activities
Rough Guide to IETF 99: A Sampling of Encryption-Related Activities
Encryption17 July 2017

Rough Guide to IETF 99: A Sampling of Encryption-Related Activities

Encryption is once again a hot topic, and there’s much to discuss at IETF 99 this week in Prague. This...

Deploying TLS 1.3
Deploying TLS 1.3
Deploy36026 August 2018

Deploying TLS 1.3

Last week saw the formal publication of the TLS 1.3 specification as RFC 8446. It's been a long time coming...

Join the conversation with Internet Society members around the world