Agenda IETF106: hotrfc
agenda-106-hotrfc-00

HotRFC @ IETF-106, Singapore
Sunday, Nov 17, 2019, 1800-2000
Info: https://www.ietf.org/how/meetings/106/hotrfc/
Materials: https://datatracker.ietf.org/meeting/106/session/hotrfc

=====================================================================

1. Adaptive DNS Privacy

Tommy Pauly <tpauly@apple.com>

While using HTTPS to encrypt DNS is becoming more widely used to
improve privacy, the policies for how and when to use this protocol
aren't standardized yet. Adaptive DNS Privacy is a proposal from the
client operating system perspective, aimed at creating a scalable
ecosystem for encrypted DNS that works with many providers, both
locally-provisioned, and on the web. It allows deployments to
designate DoH servers to be used for their zones; local network
providers to prove authority over certain names; and also allows
clients to discover more capabilities of the server deployments.

Drafts are available here:

https://tools.ietf.org/html/draft-pauly-dprive-adaptive-dns-privacy
https://tools.ietf.org/html/draft-pauly-dprive-oblivious-doh

=====================================================================

2. Abstract of Deadline-aware Transport Protocol (DTP)

Zhiwen <liuzhw3.16@sem.tsinghua.edu.cn>

Deadline-aware Transport Protocol (DTP) is a transport protocol that
provides deliver-before-deadline service and has following features:

* Support the block-based deadline delivery.  By mapping block to QUIC
  stream one to one, DTP supports the timeliness and dynamic of block
  delivery very well.

* Prefer timeliness than reliability.  The deadline means the block
  completion time. DTP will optimize before-deadline delivery instead
  of reliability, which means some blocks may get dropped.

* Support HTTP/3 based on its unreliable transport mechanism.  DTP
  makes several extensions to QUIC and HTTP/3 stack. One block is
  mapping to one QUIC stream and one HTTP/3 stream. DTP reuses
  handshake, encryption and some other features of QUIC as well as
  adds deadline and timestamp to each stream frame.

Feel free to contact me by sending email if anyone wants to talk about
DTP:) My email address is liuzhw3.16@sem.tsinghua.edu.cn

=====================================================================

3. Formal languages in IETF documents

Stephen McQuistin <sm@smcquistin.uk>
Marc Petit-Huguenin <marc@petit-huguenin.org>

Formal and structured languages have seen slow and limited adoption in
standards documents. We believe that this is to their detriment:
documents often contain inconsistencies and bugs that could be
detected using formal approaches. To encourage the adoption of such
approaches, we must understand their social and technical
limitations. We will be holding an informal side meeting about this
topic, which we encourage interested people to attend, to discuss how
to take work forward.

=====================================================================

4. MathMesh

Phillip Hallam-Baker <phill@hallambaker.com>

=====================================================================