IETF 101, Day 4: The Brass Tacks about DNS and Routing
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. And Thursday is probably the busiest day for us, covering the whole range of our interests.
ROLL has its first of two sessions starting at 09.30 GMT/UTC; continuing on Friday morning. There are several drafts being discussed dealing with the issues of routing over resource constrained networks where limited updates are possible.
NOTE: If you are unable to attend IETF 101 in person, there are multiple ways to participate remotely.
There’s a choice between a couple of working groups after lunch, starting at 13.30 GMT/UTC.
DOH was chartered to create a single RFC, so clearly the draft DNS queries over HTTPS is going to be the primary focus of discussion. However, there will also be updates on the practical implementation work, and a discussion about possible future work if there is a decision to re-charter the group.
6LO runs in parallel and has a fairly busy agenda with Registration Extensions for 6LoWPAN Neighbor Discovery, and Address Protected Neighbor Discovery for Low-power and Lossy Networks having received feedback from the IESG. The drafts related to IPv6 Backbone Router and Packet Delivery Deadline time in 6LoWPAN Routing Header are being prepared for Working Group Last Calls, and there will also be updates on the 6LO applicability and use cases and from the fragmentation design team (draft-watteyne-6lo-minimal-fragment-00 and draft-thubert-6lo-forwarding-fragments-04). Finally, there’s a proposed update to RFCs 6550 and 6775 where 6LoWPAN ND nodes in a RPL domain do not participate in the routing protocol.
Following the afternoon break there’s the choice of SIDROPS, T2TRG or a joint NTP/TICTOC meeting, commencing at 15.50 GMT/UTC.
SIDROPS will be discussing several drafts related to the operational management of certificates in the RPKI, and in particular how to perform RPKI checks via a route server. There are also two drafts related to Trust Anchor Locators – one defining a TAL for RPKI with support for HTTPS URIs, whilst RPKI signed object for TAL defines how a RPKI signed object can be used to communicate a new Trust Anchor Locator to already deployed Relying Parties. There’s a working group sponsored draft on Requirements for RPKI Relying Parties, and finally a new proposed draft on Origin Validation Policy Considerations for Dropping Invalid Routes (not yet published).
T2TRG researches the issues of turning the IoT into reality, and will be discussing a key draft State-of-the-Art and Challenges for the Internet of Things Security. There will also be presentations on Deep learning on microcontrollers, Secure Computations in Decentralized Environments, and Semantic Interoperability Testing.
The NTP/TICTOC joint session is focusing on Network Time Security (NTS). This represents a significant update for NTP server authentication as secure and accurate time synchronization is vitally important for the proper operation of security protocols.
If you still have any remaining energy, there’s a couple of evening sessions starting at 18.10 GMT/UTC.
Last but not least, UTA will be discussing drafts on Strict Transport Security (STS) for mail (SMTP) transfer agents and mail user agents as well as SMTP Require TLS Option.
Relevant Working Groups
- Routing Over Low power and Lossy networks (roll) – Park Suite @ 09.30-12.00 GMT/UTC
- DNS Over HTTPS (doh) – Blenheim @ 13.30-15.30 GMT/UTC
- IPv6 over Networks of Resource-constrained Nodes (6lo) – Buckingham @ 13.30-15.30 GMT/UTC
- SIDR Operations (sidrops) – Park Suite @ 15.50-17.50 GMT/UTC
- Thing-to-Thing (t2trg) – Blenheim @ 15.50-17.50 GMT/UTC
- Network Time Protocol Joint session with TICTOC (ntp) – Palace C @ 15.50-17.50 GMT/UTC
- Domain Name System Operations (dnsop) – Sandringham @ 18.10-19.10 GMT/UTC
- Using TLS in Applications (uta) – Blenheim @ 18.10-19.10 GMT/UTC
The post IETF 101, Day 4: The Brass Tacks about DNS and Routing appeared first on Internet Society.