Telechat Review of draft-ietf-drip-auth-46
review-ietf-drip-auth-46-dnsdir-telechat-ma-2024-01-31-00
| Request | Review of | draft-ietf-drip-auth |
|---|---|---|
| Requested revision | No specific revision (document currently at 49) | |
| Type | Telechat Review | |
| Team | DNS Directorate (dnsdir) | |
| Deadline | 2024-01-30 | |
| Requested | 2024-01-17 | |
| Authors | Adam Wiethuechter , Stuart W. Card , Robert Moskowitz | |
| I-D last updated | 2024-06-26 (Latest revision 2024-02-21) | |
| Completed reviews |
Tsvart IETF Last Call review of -43
by Gorry Fairhurst
(diff)
Dnsdir IETF Last Call review of -43 by Di Ma (diff) Dnsdir Telechat review of -46 by Di Ma (diff) Iotdir Telechat review of -45 by Behcet Sarikaya (diff) Intdir Telechat review of -46 by Carlos J. Bernardos (diff) Secdir Early review of -05 by Rich Salz (diff) Genart Early review of -24 by Matt Joras (diff) |
|
| Assignment | Reviewer | Di Ma |
| State | Completed | |
| Request | Telechat review on draft-ietf-drip-auth by DNS Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/dnsdir/I8Q-zw1XkLwjF5rRkx3wHDvK55I | |
| Reviewed revision | 46 (document currently at 49) | |
| Result | Ready w/nits | |
| Completed | 2024-01-31 |
review-ietf-drip-auth-46-dnsdir-telechat-ma-2024-01-31-00
I think this document is ready with clarification on DNS transport and security options in Section 3.1. Yet I still suggest adding RFC1035 as normative reference to the term 'DNS' in this document to differentiate from stateful DNS (rfc8490) which is not about transport and security options but a totally different DNS operation model.