On Sep 11, 2020, at 4:24 PM, Patrick Mevzek <mev...@uniregistry.com> wrote: > > On 11/09/2020 15:37, Paul Hoffman wrote: >> Greetings. Puneet and I have an new draft, >> <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-pp-dnsop-authinfo__;!!PtGJab4!tA3Rg8zYWrkxVj0XhVFgOSw3njnqVfZ1lZb89fZi40rNWqnTDHsqJvazW8HMMZej0qCL5X79cg$ >> >, that we would like DNSOP to consider. From the abstract: >> This document defines a new DNS RRtype, AUTHINFO, that is used by > > [..] > >> We would like DNSOP to adopt this, and of course we are open to suggestions >> on how to improve the protocol. > > I know it is unrelated, but EPP uses authInfo term extensively (for > authentication purposes and in practice basically as synonym of "password"), > so I really recommend using another name for this record type, because > otherwise I am pretty sure somewhere somehow someone will confuse both things.
The name can be bikeshedded, but "authinfo" is used in multiple protocols because it is quite descriptive. > Plus, why couldn't this be extended in the future to recursive nameservers as > well? In which case, the name should be resolver genre agnostic. There is already a draft for RESINFO. The difference is important, because a single host might be both a resolver and an authoritative server. > Maybe something like "CAPABILITIES" or "ABILITIES"? > (or shorter version) And you're thinking those aren't used in other protocols? :-) --Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
