Agenda ADD@IETF121

Meeting Materials, Links

Materials, Charter, Documents

Session times

Agenda

1 Administration [10 min]

2 Announcements from Chairs

3 Document status

3.1 IETF LCs

3.2 ADD WG LCs

3.3 ADD Adoption Calls

4 Docs

4.1 WG Doc - Handling Encrypted DNS Server Redirection
https://datatracker.ietf.org/doc/draft-ietf-add-encrypted-dns-server-redirection/

Add RESINFO to add EDSR

option 1 - do nothing

option 2 - add a simple flag

option 3 - add a key with data

Marco Davids: Stephane Bortzmeyer working on adding flags

Ben Schwartz: I don't really care

4.2 DNS Resolver Information Key for DNSSEC Validation
https://datatracker.ietf.org/doc/draft-bortzmeyer-resinfo-dnssecval/

– Stephane Bortzmeyer

Andrew Campling: Expert Review leans toward Internet Draft quickly.

Stephane Bortzmeyer: Specification Required used to be just a draft.

Eric Venkye: Definition of "Specificed Required" is wrong in the IETF,
but are being addressed.

SB: Seems silly to take 1, 2 3 years for something simple

Tommy Jensen: Simple Flag should be simple to address.

Petr Spacek: DNSOP RR Type registry has a very simple "submit a draft
and folks thinks its good and give it out"

SB: Not trying to change 9606.

Chris Box: Does this resolver validate or not

SB: Needs to be something clear for the user.

CB: RESINFO not presented to user, more debugging tool.

Tommy Pauly: Verify from the client perspective what value they will
get.

Dave Lawrence (no hats): For information distribution purposes, provide
more than a flag.

Ralf Weber: We should make this easy, prefer just a flag.

4.3 DNS Resolver Information Key for DNS64
https://datatracker.ietf.org/doc/draft-fobser-resinfo-dns64/
Florian Obser

Tommy Jensen: Shame not to push this

5 Architectural Directions Discussion

Interim on add-encrypted-dns-forwarders to address this

BS: after alldispatch this seems to be change this conversation

EV: Too Early to make a WG draft but can work on outside.

6 AOB / Discussion (all)

7 Planning & Wrap up