Re: NAT64 in RA, draft-ietf-6man-ra-pref64

Fred Baker <fredbaker.ietf@gmail.com> Tue, 02 July 2019 00:29 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F7C12018A for <ipv6@ietfa.amsl.com>; Mon, 1 Jul 2019 17:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hu4vMW8_RVc0 for <ipv6@ietfa.amsl.com>; Mon, 1 Jul 2019 17:29:22 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095BA1200CE for <6man@ietf.org>; Mon, 1 Jul 2019 17:29:22 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id u15so11432369oiv.0 for <6man@ietf.org>; Mon, 01 Jul 2019 17:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=KLSdVJtSXy8T4j2SCA9E7OGRtOGFJlaTXU0wgfEM3hE=; b=QecAbREDkbgrcxGct9vX+wZsR5VGM/MxjTlBcNTP2Ve1tscWczJ+nkDK088DJyqM4L 79B0sFGVw9qJVK8INpc1G1t0uPC4ArI1Z6PAUxKPU63NExxfBlRkBjKWkGSawsZ9jKe6 8ypV6fCKWMVAGjyf6BpitEBlTbYNvPfOgYO7ODAY1Qs+8/u9YpgQoyhsmwB7QDqeMd2s fyxSR9upP1W2GTreDs72ZrgV5oMzIj2s1rf8i5gBz646XoCsEw7Q90ZyFGL0lJxqHDv+ zisX8VNPbnI5eGINiUFpKNNsNEICdhbA13E0cvlXXvpcE1DG5XRs3AIkShqIdKKAmiKB jpOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=KLSdVJtSXy8T4j2SCA9E7OGRtOGFJlaTXU0wgfEM3hE=; b=hEYGSmEzED4ekmg//GfB6R3Dplpwvn4+4qzYCgDi/G2Z2Er5YvLJCMnGiR1H+XSSJq XS4HkUlkSs7HjYsAmHCthsGXlsU1PTlWXr0BjWubO6xUZDNv4L2m6Cs8BTtkus27BcKp s6x7zMQUGSJ25VP/LYws/cid67dRL2yf+r6fGJOnG0AuVXamKudEZxHHnv3UmJbWZn+Q n6iD1JIUom89/oGCgHCirxoHBWAV8LPXnd8fOf/bybwR5XiyRsXmLMf9iqF4g+jX6tOA +18X2uIXZKJzIjrAV4zRvmT08FAVxjtP9xujxQO41BauOcvI8qh459xQVPJh/LqSh+uo L8qg==
X-Gm-Message-State: APjAAAX0ypXSDva+2bVTz8e3oXqh05oyEyiiS/7a9YHpsPr+1T5oSmh4 NuOY0v4CsRNDXjCC10MeU7dPpJ2n
X-Google-Smtp-Source: APXvYqxxd+B3FJ3VFVCxLP9PYxpAET1FG8tlIq24PFj6ibDDwAuAaPRtymJKaem8JLtbaeAdmqw8qg==
X-Received: by 2002:aca:5a56:: with SMTP id o83mr1324272oib.130.1562027361362; Mon, 01 Jul 2019 17:29:21 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::101e? ([2600:8802:5903:df16::101e]) by smtp.gmail.com with ESMTPSA id e78sm4855486oib.50.2019.07.01.17.29.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Jul 2019 17:29:20 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <0167874A-F2B4-434A-B674-792FE3AD0E2D@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D315F99B-AAFC-49A1-90D4-6A733500C081"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
Date: Mon, 01 Jul 2019 17:29:18 -0700
In-Reply-To: <CAFU7BAR9kmnk3Q9aOpsqGFVRZkiRXb0FkZjMXWG2gN0-o1MjGw@mail.gmail.com>
Cc: 6man <6man@ietf.org>
To: Jen Linkova <furry13@gmail.com>
References: <12187.1558972629@localhost> <D3C7EB41-02E8-48D6-9335-26A041FD64C2@isc.org> <00C00FE5-C7CD-4B99-A2C9-CCBFCB1E4850@isc.org> <CAFU7BASfJ4YS6xBzK8hNJRSMnFZmdn3VE5A=sPCC3JqRa8SQEQ@mail.gmail.com> <EC63A89D-26CD-4093-8814-4461B6D3D327@isc.org> <CAFU7BASsAwitEc==Zj6qT4izy-tFosg23DHXFVVzOixidEfMFA@mail.gmail.com> <CAKD1Yr3jDTS25ERGZYDDM9yRRTxEfY4Ltcd-QgFNor6ze2G7xA@mail.gmail.com> <6053.1561748461@localhost> <CAFU7BAR9kmnk3Q9aOpsqGFVRZkiRXb0FkZjMXWG2gN0-o1MjGw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TMfgVKVHCxjZ-4LBqcl06aCX6Lg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 00:29:24 -0000


On Jun 30, 2019, at 8:06 PM, Jen Linkova <furry13@gmail.com> wrote:
> First I think we need to clarify what  'IPv6-only' means.

To my mind, that is mostly complex because people make it complex, or because we allow them to.

Imagine I have two hosts, each of which can only communicate using IPv6. They only have IPv6 addresses, and they possibly only have IPv6 stacks, but they don't have anything else. If they can communicate in a domain, from their perspective it is a domain that will support end to end IPv6 communication. If they have to do something in addition, the domain doesn't work for IPv6-only hosts.

Now, it could be that the communications are translated to IPv4, X.25, or SNA in between. Yup, could happen. But we can communicate end to end using only IPv6, right?

And, oh yes, someone using IPv4 (or X.25, or SNA) could go through a translator and communicate with an IPv6-only host in such a domain. It's IPv6-only up to that translator.

The question boils down to - imagine I had only IPv6 to work with. Could we communicate? An IPv6-only host, or IPv6-only network, could communicate with that restriction. Everything else is noise - and if I have to deal with noise, it's not IPv6-only.
--------------------------------------------------------------------------------
The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume...