[DNSOP] Re: draft-ietf-dnsop-zoneversion maybe does handle this OK
Hugo Salgado <hsalgado@vulcano.cl> Mon, 17 June 2024 22:13 UTC
Return-Path: <hsalgado@vulcano.cl>
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 1E015C14F60A for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2024 15:13:35 -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, 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=vulcano.cl
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 6JV0XV_Rgrr6 for <dnsop@ietfa.amsl.com>; Mon, 17 Jun 2024 15:13:30 -0700 (PDT)
Received: from correo.vulcano.cl (correo.vulcano.cl [200.14.81.199]) (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 3ACE8C14F601 for <dnsop@ietf.org>; Mon, 17 Jun 2024 15:13:29 -0700 (PDT)
Received: from pepino (unknown [186.11.56.21]) by correo.vulcano.cl (Postfix) with ESMTPSA id 9A9666EDBF; Mon, 17 Jun 2024 18:13:26 -0400 (-04)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vulcano.cl; s=mail; t=1718662407; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=oQvveKuATrLUFcWK/Yn9JPi2+s4aj6nh3RVHneZcwXI=; b=RQOHe8aHNoNqsoN1SeJa2Qsp8dQl1vNzhuSGnEgqIbf7g9fzW76D0eCug8TTPjspntZPvT 212v2dRbjX3e9F1M4gE0G7rvF2dEuuVEyIN+15dzkUAwJh30e1QgsiEibg3OYNj0KFlZYD jQqm4j9M0YmNHVQT5qUjjzP/CqjMVRsw6QFh0l1XyVKC4RHZUa+ZwU2o5GrvHizTYRUqsY TkUJHJR0NUexRhany7gNIY3P2GD+8xpzo1q6TP3GHkIc08nZZwYI8BUP4DmFYfmtyOMyG6 be03UZ6xYf7TwY5zN+x+0tZB5DYMDZuYJGVtS1BPQAQ8i84uI4Wi7w/5Y4E0eQ==
Date: Mon, 17 Jun 2024 18:13:25 -0400
From: Hugo Salgado <hsalgado@vulcano.cl>
To: John Levine <johnl@taugh.com>
Message-ID: <ZnC1BUkp53lp7PNR@pepino>
References: <CAHw9_iJMCxSdXM3DKP1yN8mk-05App-CAEYnZ5xMnNOnkR3WGw@mail.gmail.com> <cb32865e-ac5b-5145-c5ef-23866f58170c@iecc.com> <v4q419$9sv$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <v4q419$9sv$1@gal.iecc.com>
Message-ID-Hash: 2FGOS5XM3HHLTNCATZOVPUGXE5FC7HZF
X-Message-ID-Hash: 2FGOS5XM3HHLTNCATZOVPUGXE5FC7HZF
X-MailFrom: hsalgado@vulcano.cl
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: draft-ietf-dnsop-zoneversion maybe does handle this OK
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Q0KS1-dKZ_BiSf53axkY5eGZowE>
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 19:50 17/06, John Levine wrote: > According to John R. Levine <johnl@iecc.com>: > >It currently says: > > > > A name server MAY include more than one ZONEVERSION option in the > > response if it supports multiple TYPEs. A name server MUST NOT include > > more than one ZONEVERSION option for a given TYPE. ... > >;; QUESTION SECTION: > >;com.ws.sp.am. IN A > > > >;; ANSWER SECTION: > >ws.sp.am. 300 IN DNAME whois.services.net. > >com.ws.sp.am. 300 IN CNAME com.whois.services.net. > >com.whois.services.net. 300 IN CNAME whois.verisign-grs.com. > > Hmmn. I think it means it should only return a zoneversion for > ws.sp.am because it matches the query, and if I want info on the > second CNAME I should ask for it separately. > Yes, that's right. The zoneversion response must match the "original QNAME" zone, meaning "the name actually sent in the Question section in the original query". Also note that the "TYPE" mentioned in this paragraph: > A name server MAY include more than one ZONEVERSION option in the > response if it supports multiple TYPEs. A name server MUST NOT include > more than one ZONEVERSION option for a given TYPE. is the *zoneversion* type. Not the QTYPE of the query. This is to allow the server to return more than one zoneversion "formats" in a single answer. > Might be worth adding that it MUST NOT return version info for any > records that don't match the original query. Yeah, it should be > obvious, but at least one person (me) got confused. > Thank you, we will look into adding it. Regards, Hugo
- [DNSOP] draft-ietf-dnsop-zoneversion, draft-ietf-… Warren Kumari
- [DNSOP] draft-ietf-dnsop-zoneversion doesn't hand… John R. Levine
- [DNSOP] Re: draft-ietf-dnsop-zoneversion maybe do… John Levine
- [DNSOP] Re: draft-ietf-dnsop-zoneversion maybe do… Hugo Salgado