Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orie Steele COMMENT (via Mucherawy) (with Joe Abley) #15

Open
vixie opened this issue Jan 7, 2024 · 0 comments
Open

Orie Steele COMMENT (via Mucherawy) (with Joe Abley) #15

vixie opened this issue Jan 7, 2024 · 0 comments

Comments

@vixie
Copy link
Contributor

vixie commented Jan 7, 2024

Forwarded comments from Orie Steele, incoming ART Area Director:

"Recommendations for zone operators and DNS server operators"

  • Define "large / small" better.

"Protocol compliance considerations"

  • Would be nice to see reporting recommendations, perhaps that make the failure
    an internal cost for the failing component?... would not want a repeat of dmarc
    though.

--

"Recommendations for zone operators and DNS server operators"

For what it's worth, and warning! this is a small thing, I think "zone operators" is a bit vague.

The presumed intent of the phrase given the recommendations in the document is to identify people responsible for the choice of records in a DNS zone as part of the target audience. However, in my experience

  • "zone" has many meanings outside of the DNS
  • "zone" as a concept is poorly understood amongst people who fit the implied target audience but who are not protocol afficionados
  • "zone operator" is not a term of art and could (I think) mean different things to different people

I think the intended group is "people who publish information in the DNS".

paulwouters added a commit to paulwouters/draft-ietf-dnsop-avoid-fragmentation that referenced this issue Feb 12, 2024
Use "DNS content operator".

Resvoles: ietf-wg-dnsop#15
(at least the non-meta question part of it)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant