[DNSOP] Re: Last Call: <draft-ietf-dnsop-zoneversion-09.txt> (The DNS Zone Version (ZONEVERSION) Option) to Informational RFC

Joe Abley <jabley@strandkip.nl> Thu, 04 July 2024 08:29 UTC

Return-Path: <jabley@strandkip.nl>
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 AFA3FC151524 for <dnsop@ietfa.amsl.com>; Thu, 4 Jul 2024 01:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.102
X-Spam-Level:
X-Spam-Status: No, score=-7.102 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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_BLOCKED=0.001, 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=strandkip.nl
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 HsVRtjzxp3Xw for <dnsop@ietfa.amsl.com>; Thu, 4 Jul 2024 01:29:10 -0700 (PDT)
Received: from qs51p00im-qukt01071902.me.com (qs51p00im-qukt01071902.me.com [17.57.155.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B91E4C151077 for <dnsop@ietf.org>; Thu, 4 Jul 2024 01:29:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=sig1; t=1720081750; bh=oyFe5mDyZo5TF24Ez85GTFXeedB9Ak3XnQp/uaJrvNI=; h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To; b=Gw8eUXKplzD3ETPa+FImPxjb2FodDFia6wf2vKPUUStDNv++xpW9zmCyli0aCxGAI PcE01YBGFQ/2ufks1XHZ3wPweLmndFAYhKf89Chdxn7uLohrIBmJ5JhB7/LIrhfnpd HOqBtZ9gLt/LhPkrJjlm920t9cM58+A7YmfEx8W3QaltfSJ3Ih/gevrRdF8oRdzN0d BWXpB+iTZiS6aETDa23g5zVUjdA2SDJ3WvNcXAD5MPxzKYRMvvUaZ1D7ovFGSWpZb/ GwdUlgwMiwgNtHiXR1mZWbzzVXH1KpJyBqtw31YD02bdO4D7hgNWLbn1eguBqoxtj/ aq4iMIL2zIh5Q==
Received: from smtpclient.apple (qs51p00im-dlb-asmtp-mailmevip.me.com [17.57.155.28]) by qs51p00im-qukt01071902.me.com (Postfix) with ESMTPSA id 5FF725EC0797; Thu, 4 Jul 2024 08:29:08 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-3E7C71A9-4574-4241-A47B-86E9D2CE0D59"
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@strandkip.nl>
Mime-Version: 1.0 (1.0)
Date: Thu, 04 Jul 2024 09:28:36 +0100
Message-Id: <B5D55688-06AA-491A-AD12-1E1A998CF7B0@strandkip.nl>
References: <abce75c4-af10-4fd1-9e99-8c4718996eec@isc.org>
In-Reply-To: <abce75c4-af10-4fd1-9e99-8c4718996eec@isc.org>
To: Petr Špaček <pspacek@isc.org>
X-Mailer: iPad Mail (21F90)
X-Proofpoint-ORIG-GUID: q41YptUtlw7NI4hbRYd5Z9Ifg0G4Ep5R
X-Proofpoint-GUID: q41YptUtlw7NI4hbRYd5Z9Ifg0G4Ep5R
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-07-03_18,2024-07-03_01,2024-05-17_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 suspectscore=0 spamscore=0 mlxlogscore=999 adultscore=0 clxscore=1030 malwarescore=0 mlxscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2308100000 definitions=main-2407040058
Message-ID-Hash: VJVOBFYDNI5EHESNPPD2I337B2OD3EDQ
X-Message-ID-Hash: VJVOBFYDNI5EHESNPPD2I337B2OD3EDQ
X-MailFrom: jabley@strandkip.nl
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: dnsop@ietf.org, draft-ietf-dnsop-zoneversion@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: Last Call: <draft-ietf-dnsop-zoneversion-09.txt> (The DNS Zone Version (ZONEVERSION) Option) to Informational RFC
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r-OvAC0lUlR2IlMBuk453MHTuqg>
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>

Hey,

On 4 Jul 2024, at 09:15, Petr Špaček <pspacek@isc.org> wrote:

> To be clear:
> Let's not hang too tight on this particular example. It could be something crazy like
> 
> qname.zone1.test. CNAME target2.example.
> target2.example. CNAME final.example.net.
> final.example.net. A 192.0.2.1
> 
> (i.e. zone names have nothing in common except for the root)

Yep. I still think the language you quoted would benefit from some clarification though. Perhaps:

1.2. Terminology

ADD:

In this document, an "enclosing zone" of a domain name means a zone in which the domain name is present as an owner name, or any parent of that zone. For example, if B.C.EXAMPLE and EXAMPLE are zones, but C.EXAMPLE is not, the domain name A.B.C.EXAMPLE would have the enclosing zones B.C.EXAMPLE, EXAMPLE and the root zone.

3.2 Responders

OLD:

   A name server that (a) understands the ZONEVERSION option, (b)
   receives a query with the ZONEVERSION option, (c) is authoritative
   for the zone of the original QNAME, and (d) chooses to honor a
   particular ZONEVERSION request responds by including a TYPE and
   corresponding VERSION value in a ZONEVERSION option in an EDNS(0) OPT
   pseudo-RR in the response message.

NEW:

   A name server that (a) understands the ZONEVERSION option, (b)
   receives a query with the ZONEVERSION option, (c) is authoritative
   for one or more enclosing zones of the original QNAME, and (d) chooses to honor a
   particular ZONEVERSION request responds by including a TYPE and
   corresponding VERSION value in one or more ZONEVERSION options in an EDNS(0) OPT
   pseudo-RR in the response message.

OLD:

   A name server MAY include more than one ZONEVERSION option in the
   response if it supports multiple TYPEs.  A name server MAY also
   include more than one ZONEVERSION option in the response if it is
   authoritative for more than one zone of the corresponding QNAME.  A
   name server MUST NOT include more than one ZONEVERSION option for a
   given TYPE and LABELCOUNT.

NEW:

   A name server MAY include more than one ZONEVERSION option in the
   response if it supports multiple TYPEs.  A name server MAY also
   include more than one ZONEVERSION option in the response if it is
   authoritative for more than one enclosing zone of the corresponding QNAME.  A
   name server MUST NOT include more than one ZONEVERSION option for a
   given TYPE and LABELCOUNT.


Joe