I support publication of draft-ietf-dnsop-integration-04 and have no objections.

I've read it closely — it's cited in our own
draft-barrett-dnsop-domain-set, and we designed domain-set's
DNS-discovery/HTTPS-manifest split specifically to satisfy the
considerations this document lays out (lifecycle awareness, control
validation, cross-TLD completeness). Having a clear,
working-group-vetted reference for how applications should integrate
domain names is useful well beyond our own draft, and I think it's
ready to move forward.

Thanks to the authors for the work.

Tom Barrett EnCirca, Inc.

On Mon, Aug 24, 2026 at 8:53 AM Ondřej Surý via Datatracker
<[email protected]> wrote:
>
> This message starts a WG Last Call for:
> draft-ietf-dnsop-integration-04
>
> This Working Group Last Call ends on 2026-09-07
>
> Abstract:
>    This document describes considerations when integrating a DNS domain
>    name into an application environment.  Goals of this document include
>    minimizing conflicts between the global DNS and applications that
>    integrate with the global DNS, providing a consistent user experience
>    (unique identifier across environments), and avoiding impacts to the
>    security, stability, and resiliency of the global DNS.  While all
>    sources of potential concern cannot be enumerated in one document,
>    accounting for at least the considerations discussed here should
>    improve the security posture of both the global DNS and integrating
>    applications.
>
> File can be retrieved from:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-integration-04.txt
>
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping [email protected]
> in copy. Objections should be explained and suggestions to resolve them are
> highly appreciated.
>
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [1].
> Appropriate IPR disclosures required for full conformance with the provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can be
> found at [3].
>
> Thank you.
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-integration/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-integration-04.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-integration-04
>
> _______________________________________________
> DNSOP mailing list -- [email protected]
> To unsubscribe send an email to [email protected]



-- 
Schedule a call with me.
https://calendar.app.google/BrESmtfgCG4tutSu7

Thomas Barrett
President
EnCirca, Inc
+1.781.942.9975 (office)
400 W. Cummings Park, Suite 1725
Woburn, MA 01801 USA

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to