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

Momoka Yamamoto <momoka.my6@gmail.com> Mon, 17 October 2022 01:20 UTC

Return-Path: <momoka.my6@gmail.com>
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 A57B0C14F747; Sun, 16 Oct 2022 18:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.855
X-Spam-Level:
X-Spam-Status: No, score=-6.855 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=gmail.com
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 Y7U6IBT80mIv; Sun, 16 Oct 2022 18:19:56 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 94B4DC14F744; Sun, 16 Oct 2022 18:19:56 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id fy4so21677848ejc.5; Sun, 16 Oct 2022 18:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RhlLYoyNn9bU37lHwV49c+UtWVnB44/dswyPh37KtP4=; b=gXgzOSA3KOZ9/ah+CX830nCqjulV4VsenJSnjtFJC/vhxb013aOyDjMFzboJV5PwQj kLstdXudscwjFmbspFT0qrZ60NOE38/TfC58ZtQKKg4DnJOzLYDaIgxNauNT3hH0ZwWT VL3jQTfFXJonhuKfCf1+o1dniamHhF/F0KzTwkW6XUvkzae26dtVFhGXVyfWh+be05rs eRc/5pdADBXmk/DS6lZYsKBj5fc0zj2bkOC96bTixX3oG3WkmdOcNy8my7qNCk5PxU5v pYrsGdfT7Tvq6nnV5q11DgloT8NAy9WGAuNmQsuESrigyqEIk4wrZUtqExpN7fydPrUb 2vkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RhlLYoyNn9bU37lHwV49c+UtWVnB44/dswyPh37KtP4=; b=eFjJPGsqciVDh8oLmM9ocU3GwTCNbmo9OI6nyL0jvGjTD4OvPf5QHvva5DNmz2SkUS 8hsAw6IXSgIiKW6a52mlENLMKlUPuwfOtJI6ew2sMGXhwzp82tO10g66y19dhA/IT43U x8N6CEIT62We1EV0lwf1BR1QN0+tvhXxsRINaTNMTNuNpsXUe2wpepDlkfpKnK0Bhc0T OFHLz/vyeJTNhPlfJwXq+m2+iasuDtvHofy35XZ8zB9as+PWKAqKzsIEbZou6haPFCKi /dw+4uipkDLvSGVYjYwXF1TZ/AhGQOI/r3P805IRrbpSUH/Bn8Yf1tNtTzBPPcw2Zeiq rRUw==
X-Gm-Message-State: ACrzQf2zjdIVui9Og0kL+40kB6qFxcJx44VX+TnOGtKfIxNSwE8Wq1Ds 9mO2WoiRhNf5FTLJmhgjHrU8OCAsVfrt0iMsqi4=
X-Google-Smtp-Source: AMsMyM7qJfG1p5sls5QhgcZj2nmL1uXR2TBpsbDESmwEb0Nz2xJmgn3XgfbymWrai3Ia2ofEuTo3J8CZVtzQQBvGBX4=
X-Received: by 2002:a17:906:ef8c:b0:78d:96b9:a0ad with SMTP id ze12-20020a170906ef8c00b0078d96b9a0admr6841869ejb.529.1665969594910; Sun, 16 Oct 2022 18:19:54 -0700 (PDT)
MIME-Version: 1.0
References: <CAD9w2qZedv6zedSkTfa=4SyhXwc2r__xccEQsJq0o4okKDtPpg@mail.gmail.com> <B96102D6-878C-4BBC-A8E4-B2DE9848F584@hopcount.ca>
In-Reply-To: <B96102D6-878C-4BBC-A8E4-B2DE9848F584@hopcount.ca>
From: Momoka Yamamoto <momoka.my6@gmail.com>
Date: Mon, 17 Oct 2022 10:19:44 +0900
Message-ID: <CAD9w2qZWwBhVEToyM64VtM-SAXAT=d1YDL1BQJDJayoqGLnSmA@mail.gmail.com>
To: Joe Abley <jabley@hopcount.ca>
Cc: Mark Andrews <marka@isc.org>, dnsop <dnsop@ietf.org>, 6man list <ipv6@ietf.org>, behave@ietf.org, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e94b9305eb30c57f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/Wy5gIfYE-g5V2LfCYAit8ilmcd0>
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: Mon, 17 Oct 2022 01:20:00 -0000

Hello,

I too believe that it's far more common to find dual stack authoritative
name servers than normal services. (number of AAAA records
https://www.employees.org/~dwing/aaaa-stats/
<https://www.employees.org/~dwing/aaaa-stats/>)

However for normal services, an IPv6 only client under a NAT64 can use a
DNS64 to acquire a translated IPv6 address to send packets to the IPv4 only
server.
There are some problems with DNS64/NAT64 that it cannot operate with
literal addresses but if domain names are used an IPv6 only client should
be able to work properly without IPv4 with the help of DNS64/NAT64.
(This is the main part of my perspective and may be wrong. I have thought
that services that do not work with DNS64/NAT64 are either using literal
addresses or do not have IPv6 support yet. Please tell me if there are any
other reasons for DNS64/NAT64 to fail)

My other understanding (that may not be true) is that an iterative resolver
is the only application that has the need to use an literal address
directly, and cannot make use of Domain names.

So my understanding is that a normal IPv6-only client doesn't need IPv4 to
connect to IPv4 servers because it can use DNS64/NAT64.
But an IPv6-only iterative resolver needs IPv4 because it cannot utilize
DNS64.

This is why we have submitted a draft to document an IPv6-only iterative
resolver to do the DNS64 translation mechanism by itself.

Currently some authoritative name servers operate only on IPv4.
An IPv6-only iterative resolver that does not perform IPv4-to-IPv6
translation by itself cannot resolve such names.
When I resolved top 500 domain names with an IPv6-only iterative resolver
that does not perform address translation, 15% of the names could not be
resolved compared to when an IPv4 iterative resolve was used.
(I have not yet published any numbers in a formal way)

Momoka



On Mon, Oct 17, 2022 at 3:43 AM Joe Abley <jabley@hopcount.ca> wrote:

> 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
>
>
>