DNSOP, Just before IETF 120 we published a draft "Integration of DNS Domain Names into Application Environments: Motivations and Considerations<https://datatracker.ietf.org/doc/draft-sheth-dns-integration/>" along with co-authors from Bluesky and Ethereum Name Service. You may have seen us socializing it at the hackathon and HotRFC<https://datatracker.ietf.org/meeting/120/materials/slides-120-hotrfc-sessa-03-integration-of-dns-domain-names-into-application-environments-motivations-and-considerations> or heard the request for feedback during Thursday's DNSOP session when the chairs mentioned it during the "Drafts of Note" of section.
During IETF 120 we received a lot of good feedback around this draft and would like further feedback! Since the initial 00 version, we have changed the draft to informational and are in the process of evaluating how best to incorporate the other feedback we received. The goal of this draft is to provide informational guidance to communities who are trying to incorporate DNS domain names into their applications. The draft currently provides motivations for why applications opt to utilize domain names and qualities that applications should consider as they build and maintain their integrations, e.g., having processes in place to account for domain name lifecycle events or DNS protocol evolution. We would appreciate feedback on the current draft and other motivations/qualities we should consider including that would make this draft as useful as possible to these communities. We would be happy to take feedback here on the mailing list. Thanks, Swapneel Sheth
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
