IETF Logo Mail Archive

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

Jen Linkova <furry13@gmail.com> Tue, 02 July 2019 00:48 UTC

Return-Path: <furry13@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 C327412019F for <ipv6@ietfa.amsl.com>; Mon, 1 Jul 2019 17:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 gnFRFmGEEtu2 for <ipv6@ietfa.amsl.com>; Mon, 1 Jul 2019 17:48:02 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 EB4B71201AA for <6man@ietf.org>; Mon, 1 Jul 2019 17:48:01 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id p144so12586350qke.11 for <6man@ietf.org>; Mon, 01 Jul 2019 17:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bt+Igr/ERhbSSOEV09BY12d1WnCfdsihVbQSNKdIYQo=; b=JF4yuGMdcfeAolpbfhob1UdVv1CigLFpm7LzPiaUBvGFDvOba+0PEZg09BuZzHOQq8 ECMKgX5hRsobFNz0KPmBDtZ6Fsb6gWY4XYzsqh3niyf+qI8h0hkPNeF2zkvbINkOrQeg UP59gAFqY8hnu34qShlrLLedYXCdkg6PcHgkmQwMHjgwuqI8QoxQB/AdkQ3YXAiR7T3I kuxWHuGFwiRfdHP1zC6P6f79FfrLU5DPPslxQ795B5X/R9Llg6FjqG/PrXMRw7es0CTR PS2w8zdefqYT3lIFhjgHi7ZiSFX8CdZreGN8/urM4oXBmoLLeG3PCV3SdyhUC6nprhHu Cocw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bt+Igr/ERhbSSOEV09BY12d1WnCfdsihVbQSNKdIYQo=; b=Vd+1ZFECiuvV4/lhNVsiPsmoOIvPMaKKm7cdwNdFiPjnBfxcvmC7o4ynCnlzrjXqFi oWD4/otmZNHENYj3LN4ErGw+Fg3ZjSbKkhB613AwrgVnpAodYbpM9qWZxRgRdPGYZqeE zqTPu5pWWnuWCgh5NPXV6wa4djmbqrfdr0zPdao/LyUl46y/ukZuhc43Q8/HJmlQI3Ms b8UtoPdCg+0aUCSh1ni/JtKVz6m3eOdJogasLQ5FPDDCKDFJnWJTFS7XfDV1m3Cvyalf YTHqYRu8LBrGsUmWaiSCktc1IaJeTf1Hjn9ljzvbUYg96fUVYu1GH6ijWGa2wJqK0Bw2 M7hw==
X-Gm-Message-State: APjAAAXULg6tSXaI+ZLmKCzTP+5dozbOoVOh5/178eWvcE8kM2WJfuxF 551OEQhuiU2oAQylXfz9dDl7MGsIkbazlde0AjE=
X-Google-Smtp-Source: APXvYqzPxEPP1bdatOBLn92pSAtIyQgAR0aTV90MqzEONnVYjOLGSxOwGoq1ZwRYNkfFMN9aZDSXb6Nl2h8qypBV0Kk=
X-Received: by 2002:a37:98e:: with SMTP id 136mr21977382qkj.444.1562028480722; Mon, 01 Jul 2019 17:48:00 -0700 (PDT)
MIME-Version: 1.0
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> <0167874A-F2B4-434A-B674-792FE3AD0E2D@gmail.com>
In-Reply-To: <0167874A-F2B4-434A-B674-792FE3AD0E2D@gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 02 Jul 2019 10:47:49 +1000
Message-ID: <CAFU7BAT2zw2+EnLW_MZnj2L9RBwH2DyStgRUbaY6bCZLuJwG9g@mail.gmail.com>
Subject: Re: NAT64 in RA, draft-ietf-6man-ra-pref64
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: 6man <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/A_J-MDmuvVVJBzBBR35Og0UAPCk>
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:48:16 -0000

On Tue, Jul 2, 2019 at 10:29 AM Fred Baker <fredbaker.ietf@gmail.com> wrote:
> 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.

I totally agree. it was my understanding of IPv6-only as well.
So - back to the original problem of excluding some addresses from
DNS64 synthesis/NAT64 translation - I've been told that an IPv6-only
host might want to exclude some addresses from synthesis and use IPv4
to reach them, so I'm trying to understand how *an IPv6-only* host
(which, IMHO, can only use IPv6) reach anything using IPv4.

-- 
SY, Jen Linkova aka Furry

v2.23.0 | Report a Bug | By Email