[DNSOP] Request Feedback: draft-sheth-dns-integration

"Sheth, Swapneel" <ssheth@Verisign.com> Mon, 05 August 2024 16:04 UTC

Return-Path: <ssheth@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C82C1840E7 for <dnsop@ietfa.amsl.com>; Mon, 5 Aug 2024 09:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njerz8pHCMXs for <dnsop@ietfa.amsl.com>; Mon, 5 Aug 2024 09:04:11 -0700 (PDT)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.30]) by ietfa.amsl.com (Postfix) with ESMTP id E9ACCC15108A for <dnsop@ietf.org>; Mon, 5 Aug 2024 09:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=9911; q=dns/txt; s=VRSN; t=1722873851; h=from:to:cc:subject:date:message-id:mime-version; bh=5I07ZeiPzwmpuB/nQAE0vKUlfUbO300kR2Gcoen9zAE=; b=TPDufZQBl0VBWegm+4AbQKOz9P1de38j50Er9XIpk8fac0UcqpT0dFjc ub2lEIPVbJ2W2GgVnUBJOjWGT9NEb0XTKah0IUTZVZOD35gGjjeVG9PvZ Gi3JMYFJ7SZ+yjATInX1KGu0tr6qEW3aPVuGBijtjBpx2UYNDT5Ci/AxB 7/28p2ZNYAIxBKFWbXrh8OIXLfcWk7ovzATzyM9EKOBIVwtgAVUtDAmIT Ox4ptUcGUlfWogLAX0kj05RoU9blMbOXVtMQWm5kJYebGLwSEhxEg2Fe3 Qq7H80pPxmL9OmTDztYhMR5yPpioP6urud9c9+zQEzAVHYRz76UaZt86i A==;
X-CSE-ConnectionGUID: jxklH/GZRpyorHmge9+Lsg==
X-CSE-MsgGUID: gLKAnGd/RwactVOEOtAzSA==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:hHhh/61OMp9Vq0XQM/bD5cZwkn2cJEfYwER7XKvMYLTBsI5bpzEHm 2pKWziGOPnYYDHye9t2bNvjpBgD6p/Vm9I3QVBoqSg9HnlHl5HIVI+TRqvS04F+DeWYFR46s J9OAjXkBJppJpMJjk71atANlVEliOfVAOO6ULOZUsxIbVcMYD87jh5+kPIOjIdtgNyoayuAo tqaT/f3YTdJ4BYqdDpFg06/gEk35qiq6GtF5gZWic1j5zcyqVFEVPrzGonsdxMUcqEMdsamS uDKyq2O/2+x138FFtO/n7/nRVYBS7jUMBLmoiI+t3+K20UqSoQai87XBdJEAatlo2zhc+NZk b2hgaeNpTIBZcUgrsxGCkUFTHsuVUFx0OSvzXCX6aR/xmWYKye8m60G4EseZeX08c4vaY1CG GBxxJngoXlvisrvqI9XRNWAiewhPMrvHMQwiEt43DbDLfMpTMGAZ77FsIowMDcY3qiiHN70X exAVhxCXEyZJQNEPU0PTpsy2vmynX+5eDpdwL6XjfNvpTGMl0oojeOrbIq9lt+iHK25mm6Dv WLL42TRHBwANceexjzD+XWp7gPKtXihCNxDTu3hnhJsqFK35UUVJxFRb0SyquWHrWOZR/tNE GVBr0LCqoB3riRHVOLVUxujp2asvxMAVZxXCeJSwAuX26PSywydG2UfTS9eZdZgpN4kLRQs1 1SKt97vHnpjt7icSHSGnop4thu4Iy5MMmkPdXddCBAb+Z/moZp2hBWJRMxlSeirlMbzXzr3x lhmsRQDulnatuZTv43TwLwNq2vESkThJuLt2jjqYw==
IronPort-HdrOrdr: A9a23:RjtPd6hABz9JoeheDCrr4DdjSHBQXuoji2hC6mlwRA09TyXBrb HNoBwavSWZtN9jYgBEpTngAtj4fZqyz/5ICOUqV4tKPzOWwFdATrsSjrcKqgeIc0bDH4Vmup uIBpIeNDSGNzZHZKjBjTVQWOxQpOVvuJrY4ts24U0dKz1XVw==
X-Talos-CUID: 9a23:q39zHGyFHfPYbL1gOzeIBgUWCsMhUjry/k3IMkiiKWNmRezWbUSfrfY=
X-Talos-MUID: 9a23:8+0sfgRmVyKNrpJhRXTjoBJLMuhkpJ6xAUsRr7IrnNWtJxdZbmI=
X-IronPort-AV: E=Sophos;i="6.09,265,1716249600"; d="scan'208,217";a="32869281"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.37; Mon, 5 Aug 2024 12:04:09 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2507.037; Mon, 5 Aug 2024 12:04:09 -0400
From: "Sheth, Swapneel" <ssheth@Verisign.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: Request Feedback: draft-sheth-dns-integration
Thread-Index: AQHa51EbPBaTC98DwE6V7pbO78EM9g==
Date: Mon, 05 Aug 2024 16:04:09 +0000
Message-ID: <3D071AEB-07A6-45C5-8FEA-3D07EC7451AA@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: multipart/alternative; boundary="_000_3D071AEB07A645C58FEA3D07EC7451AAverisigncom_"
MIME-Version: 1.0
Message-ID-Hash: 7LMGLYOLDNYG6OND3QCDG3J3423F2CRM
X-Message-ID-Hash: 7LMGLYOLDNYG6OND3QCDG3J3423F2CRM
X-MailFrom: ssheth@verisign.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Kaizer, Andrew" <akaizer@verisign.com>, "bryan@blueskyweb.xyz" <bryan@blueskyweb.xyz>, "nick@ens.domains" <nick@ens.domains>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Request Feedback: draft-sheth-dns-integration
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZlquT9kaUfp5VBpl6AB8nq0Qpi0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

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