What a week we had in Montreal for IETF 102! With a newly renovated
venue ideally suited to the needs of the IETF community and the
convergence of research, operational, and development communities all in
one spot, attendees were able to make tremendous progress in a short
amount of time.
If ever there was an IETF meeting embodying the
Always be Closing (ABC) strategy, this was it. The number of working
groups that closed out or nearly closed out the last remaining issues on
their current core deliverables was significant. These included:
Application-Layer Traffic Optimization (ALTO), which is finishing extensions to its base protocol for communicating cost metrics between the network and applications;
Automated Certificate Management Environment (ACME), which is finishing off its base protocol to automate the process of X.509 certificate verification and issuance;
CURves, Deprecating and a Little more Encryption (CURDLE), which has added a small set of broadly implemented cryptographic mechanisms to existing IETF protocols;
Interactive Connectivity Establishment (ICE), which has nearly completed its work on updates and enhancements to the original ICE protocol documented in RFC 5245;
JSON Mail Access Protocol (JMAP), which is completing the base specifications for a JSON-based alternative to IMAP and SMTP Submission;
Layer Two Tunneling Protocol Extensions (L2TPEXT) completed its work on the L2TP protocol and enhancements which provides a means for tunneling PPP over IP.
Public Notary Transparency (TRANS), which has nearly finished specifying Certificate Transparency, a protocol for publicly logging the existence of Transport Layer Security (TLS) server certificates as they are issued;
Multipath TCP (MPTCP), which is finishing off the latest version of its core protocol allowing TCP connections to simultaneously use multiple paths between peers; and
Token Binding (TOKBIND), which has nearly concluded its work on a protocol to prevent unauthorized replay of security tokens on the web.
this emphasis on finishing existing work, there was plenty of
exploration of new ideas and potential new work. In the routing area
there was discussion of a new data center proposal to support link
discovery based on Link State Over Ethernet (LSOE) as well as novel ideas about the application of LISP and BGP to mobile routing of airplanes. Of interest to application and transport people was a new proposal for tunneling UDP/IP over HTTP (see the documents here and here).
And particularly notable at this meeting was the volume of interaction
between the DNS and HTTP communities, from the ICANN DNS Symposium that
took place just prior to the IETF meeting, to the DNS Resolver Identification and Use (DRIU) Birds-of-a-Feather
(BOF) session that looked at resolver configuration issues in light of
DNS-over-TLS and DNS-over-HTTPS, to multiple working group and side
meetings. It is clear that the convergence of these two protocols is
providing ample fodder for IETF participants to evaluate how the
protocols' engineering and operational assumptions intersect; to
identify potential performance, security, and privacy gains; and to
contemplate the broader implications of changes in this part of the