To your last point, I've proposed some examples of how "alpn" and "tlsa" ought to work here: https://github.com/fl1ger/deleg/pull/16/files
--Ben Schwartz ________________________________ From: DNSOP <dnsop-boun...@ietf.org> on behalf of Kazunori Fujiwara <fujiw...@jprs.co.jp> Sent: Tuesday, January 30, 2024 1:55 AM To: dnsop@ietf.org <dnsop@ietf.org> Subject: [DNSOP] DELEG and parent only resolution !-------------------------------------------------------------------| This Message Is From an Untrusted Sender You have not previously corresponded with this sender. |-------------------------------------------------------------------! I read draft-dnsop-deleg-00. It proposes new name resolution using only information on the parent side. In the past, the dnsop WG debated parent centric name resolution and child centric, and some people did not like parent centric. If people prefer parent-centric/parent-only name resolution, there are solutions other than DELEG, such as parent centric name resolution, distinguishing the handling of authoritative data, referrals, and glue, and adding a signature of referral/in-domain in the parent. Is anyone interested in proceeding with minor fixes that are not DELEG? Previously, I prposed draft-fujiwara-dnsop-resolver-update and draft-fujiwara-dnsop-delegation-information-signer. (They are too old and need to be updated.) Or, I would like to read complete version of draft-dnsop-deleg that have alpn and tlsa parameters. Regards, -- Kazunori Fujiwara, JPRS <fujiw...@jprs.co.jp> _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
