IETF Logo Mail Archive

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

Peter Thomassen <peter@desec.io> Thu, 04 July 2024 09:02 UTC

Return-Path: <peter@desec.io>
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 9AA4AC169414; Thu, 4 Jul 2024 02:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, 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=desec.io
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 5cJQ3D-wID7k; Thu, 4 Jul 2024 02:02:09 -0700 (PDT)
Received: from mail.a4a.de (mail.a4a.de [IPv6:2a01:4f8:10a:1d5c:8000::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B078C169411; Thu, 4 Jul 2024 02:02:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=desec.io; s=20170825; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=0W6kY8JDIWtpSwUar6r42OpGMLAr8J01Aj2iF/Nxy54=; b=s+1IIBkdDp7Yhq3oCEaelgvB8B ra6/IuYm2E2QTyTRfLFbcr67QzY4QTgrojarpB01ORkCS9WELppEYr0SS/t6bUtOy6YxRgDJYLEP+ f1Mzd5/mmxo2LHcIvLk74zG/rz+f/8mUzafCxjptZZpiubfMsXcgSHZccQdZjlZRVE8vJ768rM171 hEw/AsvNyIQzlggpO3jjdq5PB/Ee6lGmVKv01eppQz5cBY+fbo48FWUi83rinzNCV5x3Bt6ex4eR9 uQxkMoCs1rf0FODtYLTp16RJnX0TjY3fjI242A3gdihle+Nuf/pJVk+4JU9ws54qW3bkvnAL6+tgX vm89E9Ow==;
Received: from [2a02:8109:9283:8800:51f4:8982:c9fe:cdb1] by mail.a4a.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <peter@desec.io>) id 1sPILo-00BTYV-2k; Thu, 04 Jul 2024 11:02:00 +0200
Message-ID: <3ada11b4-96d7-4f3d-871c-10defea1a316@desec.io>
Date: Thu, 04 Jul 2024 11:01:59 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Joe Abley <jabley@strandkip.nl>, Petr Špaček <pspacek@isc.org>
References: <8e769ae8-cb99-425c-adfe-4440f67e6a10@isc.org> <A5099CBA-AE2C-4857-A642-3730EA544320@strandkip.nl>
Content-Language: en-US
From: Peter Thomassen <peter@desec.io>
In-Reply-To: <A5099CBA-AE2C-4857-A642-3730EA544320@strandkip.nl>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: MJTQZIBTPK373CT3HNM57FA7FN2LYWK7
X-Message-ID-Hash: MJTQZIBTPK373CT3HNM57FA7FN2LYWK7
X-MailFrom: peter@desec.io
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/UVrlJm_omvg4OUEwRrIgOA861OQ>
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>


On 7/4/24 10:00, Joe Abley wrote:
>> ---
>> 3.2. Responders
>>
>> ... 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.
>> ---
>>
>> The current option cannot be used to represent version info for answer like this:
[...]
>> When the responder is authoritative for both zones - zone1.test. and zone2.test. - then there's no way to represent ZONEVERSION for zone2.test.
[...]
> I think the intention is that if the server is authoritative for zone1.example and zone2.zone1.example then a query for label.zone2.zone1.example could return ZONEVERSION data for both zone1.example and zone2.zone1.example using LABELCOUNT == 2 and 3, respectively.

NEW
    [...]  A name server MAY also
    include additional ZONEVERSION options with reduced LABELCOUNT if, in
    addition to the zone corresponding to the QNAME, it is also
    authoritative for any of its parents.  [...]

Best,
Peter

-- 
https://desec.io/

v2.37.1 | Report a Bug | By Email | System Status