[Add] draft-ietf-add-resolver-info: next steps after IESG evaluation

["Eric Vyncke (evyncke)" <[e-mail]>]

You may be aware of the new status ‘revised I-D needed’ for draft-ietf-add-resolver-info after the IESG telechat of 4th of April 2024:
https://datatracker.ietf.org/doc/draft-ietf-add-resolver-info/ballot/

I.e., more work to do by the authors and the ADD WG:


  1.  Adding context for the I-D, i.e., describing one or more use cases as some IESG members were unable to understand how this can be used (notably by OS and/or browsers/apps)
  2.  Can a human end-user make use of this information ? Again lack of context/use cases
  3.  This is also linked on whether this I-D is providing a client policy (or just hints). The former is out of scope of the ADD charter, but use case(s) could help to clear this issue.
  4.  As the infourl can be hosted in a different server (or even organization) than the DNS server, how can the validity be ensured ? (e.g., there could be some discrepancies after a couple of years)

It was proposed to either have a real ADD WG interim with the DISCUSS holders and the WG (and possibly other topics) or simply a *public* Webex (happy to organize it) with DISCUSS holders, authors, chairs (plus any IETF participants of course). My own take is that the I-D can progress over email during April and then have this interim/Webex mid-May for a final check.

All in all, with the number of requested changes, the I-D will most probably undergo another IESG telechat (and possibly another IETF Last Call)

The problem is solvable but will require more work.

Regards

-éric