IETF Logo Mail Archive

Re: [BEHAVE] [DNSOP] [v6ops] New Version Notification for draft-momoka-v6ops-ipv6-only-resolver-00.txt

Joe Abley <jabley@hopcount.ca> Sun, 16 October 2022 18:43 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F876C14CE23 for <behave@ietfa.amsl.com>; Sun, 16 Oct 2022 11:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 xHlqrj9TsxeQ for <behave@ietfa.amsl.com>; Sun, 16 Oct 2022 11:43:24 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 5D337C14CF19 for <behave@ietf.org>; Sun, 16 Oct 2022 11:43:24 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id 137so7571435iou.9 for <behave@ietf.org>; Sun, 16 Oct 2022 11:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=V7DSPExE3fNSKYfZ5+qbuBfB7FWSvWMpipnFxtmUjY4=; b=Gz9zsGJYNptQEKhZGqpv/aNTkRrE8b9/+HXl4z7XJLUOr4O0QHaHmD6a7Uzk1a1lTl 1kfbs2+3vKfPJ68fMRlrWFngyXHrVW+KAgTf99UvB9JQS0JX2eLxjriqHtpqdh8Xv7N1 yKVmgNKDBzqpLR/cmc5stnYKloHuRaBaaWKTc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=V7DSPExE3fNSKYfZ5+qbuBfB7FWSvWMpipnFxtmUjY4=; b=C1enJXKSpTXG+BKKANmF84N2d4G5F92OTlJVq1B4DoLsELQBXKKO7irbDQY/ixJIuG fZPj5Xjdbvj/b3qymWy4YJJ7mTw7JQ3Sp5M5F09mKx8JZVtO+wnN5W9KP/KcYK2SlaqQ e5UKOYOXHEhqfPvla7gts7OOhukuOVxO0/mrZzgCKiXIuMfF0Mi34u9lW4ZDUPamtF35 xXcFR09UfaRlsg8c84Ec5xZMloUI54JBvC3d9Le02T9QtDTmbOjty4+ahtTF7qetKreB Ox9eAbubwOrD2ggLb3ky+g4AanOBnpHdfvpw8db9ddnWZVfPzya2KkvqelqaAWg4fYvQ Qklw==
X-Gm-Message-State: ACrzQf2rYjeDBrp/ZZeyRc3f0KN1MTEnfelBV8stFyCG/Y2ZwA3TDWoh PK3UjdUKVI/7mltRMrjFl2Enuw==
X-Google-Smtp-Source: AMsMyM59f7DpdRs3J8QFaRavHYH3OJRFGP23Rb3+poS8nQjHRa51dXUBrA2e2Wo+GDY6Naxh/CM7TA==
X-Received: by 2002:a05:6638:24d1:b0:363:fa8f:1e2a with SMTP id y17-20020a05663824d100b00363fa8f1e2amr3785026jat.99.1665945803748; Sun, 16 Oct 2022 11:43:23 -0700 (PDT)
Received: from smtpclient.apple ([2a09:bac0:29::82c:3f07]) by smtp.gmail.com with ESMTPSA id a8-20020a056e02120800b002fc681a6ad8sm2968482ilq.78.2022.10.16.11.43.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 16 Oct 2022 11:43:23 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-30ED970E-D9AC-4F21-8A53-5876E45A250B"
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
Date: Sun, 16 Oct 2022 14:43:11 -0400
Message-Id: <B96102D6-878C-4BBC-A8E4-B2DE9848F584@hopcount.ca>
References: <CAD9w2qZedv6zedSkTfa=4SyhXwc2r__xccEQsJq0o4okKDtPpg@mail.gmail.com>
Cc: Mark Andrews <marka@isc.org>, dnsop <dnsop@ietf.org>, 6man list <ipv6@ietf.org>, behave@ietf.org, v6ops@ietf.org
In-Reply-To: <CAD9w2qZedv6zedSkTfa=4SyhXwc2r__xccEQsJq0o4okKDtPpg@mail.gmail.com>
To: Momoka Yamamoto <momoka.my6@gmail.com>
X-Mailer: iPhone Mail (20A392)
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/RwRZjsyDyy19M-5RaYnccXAKG04>
Subject: Re: [BEHAVE] [DNSOP] [v6ops] New Version Notification for draft-momoka-v6ops-ipv6-only-resolver-00.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2022 18:43:28 -0000

Hi again,

On Oct 16, 2022, at 13:09, Momoka Yamamoto <momoka.my6@gmail.com> wrote:

> [...] However, we thought that in theory (but maybe not currently) an iterative resolver is the only application that actually needs IPv4 to operate. 

I'm interested in this perspective. 

My feeling is that it's far more common to find dual-stack nameservers reachable directly by v6-only and v4-only clients than it is to find services that the requested names refer to that are dual-stack and similarly reachable. On the face of it this seems like the opposite assumption than the one you describe above. 

Do you have any data to support your perspective? This is an honest question; to be clear, I have no data to support mine and I am very willing to discover that I am wrong :-)


Joe

v2.23.0 | Report a Bug | By Email