IETF Logo Mail Archive

Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments

Fred Baker <fredbaker.ietf@gmail.com> Thu, 28 June 2018 01:56 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6BE130E17 for <v6ops@ietfa.amsl.com>; Wed, 27 Jun 2018 18:56:06 -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_PASS=-0.001, URIBL_BLOCKED=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 c99MaA569Her for <v6ops@ietfa.amsl.com>; Wed, 27 Jun 2018 18:56:03 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (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 957C9130E79 for <v6ops@ietf.org>; Wed, 27 Jun 2018 18:56:03 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id o202-v6so2353211vko.2 for <v6ops@ietf.org>; Wed, 27 Jun 2018 18:56:03 -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=Rox7HIk2aK/RqrWQKD6ZbbqRXhav5UZMGMWHcaGnkxg=; b=Bz0RDQSVI1o4U4XFXiG2+0rUHhdNVr/UL6PRI3dO+KAcmxymrfVqz0ug9elKKSxN68 YrrHSjJWtUcZrHTbxOFVSLm9qRDG/vVZxj3r0e5GXkl3MEHG63pNi7xmrhew/+t0bt42 5rlUnPBHNVfJFI7vc59LKXxNMh+sMhdkNjz5hw0p2K2puAFRdbKOx2uuBEQYA6OJaZD5 0KlKrLgknfSb+f+cZc605N7a6BuQq2IFOXIzrc8xFBzCU6rJ2BLbWZatIx2AQ13TZkbj +UGsAvupgqAikfg7PveWdkXzbajlNFYVLtCnK1I1A4ut8C3pp1t1WyMNvxGM0mwr79AH RKQg==
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=Rox7HIk2aK/RqrWQKD6ZbbqRXhav5UZMGMWHcaGnkxg=; b=ujQ6lU/kyMt2MRbvxUeXuJFMquW2KV+kl2AIKvV8ejwvkakPnKsh5pF5FgiznIbtP2 StXcpKv5V219DJ5+w69ZfQygMw/b2PVFKk+mkADkpaE7l8c8BOmgFpELGQa4BFr31LAv aCZSkxbMTmIaA4hFlXJlF2n0fpQjKRZr5i+0fYRjKOLKVKcet5/0oxwDCunqWHzh3hSZ i1cQsy4q+Hk0uLj8GK0RMwfgX0FkHQPDWtBy3Q12SeZXFNXyzKe+BwZflVoA6q1BD/3e Vlm74Gcd6R1AB3lS23AxXe8dDDkWP/RqfnLa1qX1xm8Ghir0y3uCnP12Lm+lR1v1XW0T oaPQ==
X-Gm-Message-State: APt69E1VfDXHE0XkAt26UJHXdD3i6tGi8W2enMR+N/qfxd1WGLeJn4i3 ECd78a5wL3L/m9QOWfbV3KQ=
X-Google-Smtp-Source: AAOMgpe2ZwKc+i1Wx3N9Vt01e+qb5Yf0qU2M0RIk8wb4s177np05jP+Hv27Pva1eEwglPXq5NVvMkg==
X-Received: by 2002:a1f:8dd4:: with SMTP id p203-v6mr5075076vkd.64.1530150962663; Wed, 27 Jun 2018 18:56:02 -0700 (PDT)
Received: from [10.196.220.133] (41-197.icannmeeting.org. [199.91.197.41]) by smtp.gmail.com with ESMTPSA id j127-v6sm1607267vkd.23.2018.06.27.18.56.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jun 2018 18:56:01 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <9921F0BA-F2A5-4214-A133-1C8F4AF7CB6A@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_FBD4F64B-F006-41DD-9026-A67FF3A92C40"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 27 Jun 2018 20:55:59 -0500
In-Reply-To: <ED663F6E-C63B-4FEC-913C-2CFF16249E93@consulintel.es>
Cc: "v6ops@ietf.org list" <v6ops@ietf.org>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
References: <663F489C-7F63-4B0C-A5E6-F7EE4634E62B@gmail.com> <ED663F6E-C63B-4FEC-913C-2CFF16249E93@consulintel.es>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/2mEsIbkN7vGqt1-SzDVVsfrV07g>
Subject: Re: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 01:56:07 -0000


> On Jun 27, 2018, at 4:08 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>> 3.1.2.  Service Provider offering 464XLAT, with DNS64

> -> Are you suggesting that I should make a more detailed description in every scenario, with more figures, etc. ? Or just in the 464XLAT case ?
> 
>> 3.1.3.  Service Provider offering 464XLAT, without DNS64
> 
>    The difference from the preceding section will be connectivity between an IPv6-only device and an IPv4-only peer. In the previous section, the IPv6 device will be unable to communicate with an IPv4-only peer, and the dual stack device will use its IPv4 side, the CLAT, and the PLAT.
> 
> -> Right, again, you feel I need to add text to explain that, so same as previous question, having some extra text only for the 464XLAT cases?
> 
>>   The major advantage of this scenario, using 464XLAT without DNS64, is
>>   that the service provider ensures that DNSSEC is never broken.
> 
>    Yes, but at the cost of IPv6-IPv4 connectivity.

I suppose in part I'm thinking out loud. But I do think it's important to not trivialize the lack of connectivity in that last case, which I think your current text does. Yes, DNSSEC doesn't work (doesn't validate a signature, and probably doesn't *have* a signature) with a DNS64 IPv4 embedded IPv6 Address. But it doesn't work without one either, because in the case nothing works - there is no connectivity. It's a judgement call, I suppose, but I think it's better to say it than let the installing ISP discover it and wonder what happened.

v2.23.0 | Report a Bug | By Email