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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 28 June 2018 06:14 UTC

Return-Path: <prvs=17172b6c16=jordi.palet@consulintel.es>
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 9018E130DF7 for <v6ops@ietfa.amsl.com>; Wed, 27 Jun 2018 23:14:38 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 x5Xkvb7sYqVt for <v6ops@ietfa.amsl.com>; Wed, 27 Jun 2018 23:14:36 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF5B126F72 for <v6ops@ietf.org>; Wed, 27 Jun 2018 23:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1530166473; x=1530771273; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=BWctOGFFaZnWYfyjn/MoWOPKt5y/hMecmpyrBwPzDWY=; b=syHLyCjLfhUKq R8TWrsFKdvQ6aEp/qoj9PjOUGhnasu5rx1G9BJDk4h2k0ylHiCeiBRaGr4ZD8lgc usIC9Ki6EPUBVZ+IJ6AZJhdwbHWC6olLlQ5PDkYFVFmqQxUKH9014PefvxNi0u2w MCFq+bOjVKGA+Y7EXKqOl68quf5/ug=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 28 Jun 2018 08:14:33 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 28 Jun 2018 08:14:33 +0200
Received: from [10.10.10.130] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50005799421.msg for <v6ops@ietf.org>; Thu, 28 Jun 2018 08:14:32 +0200
X-MDRemoteIP: 2001:470:1f09:495:882e:62f3:2f4:887c
X-MDHelo: [10.10.10.130]
X-MDArrival-Date: Thu, 28 Jun 2018 08:14:32 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=17172b6c16=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.e.1.180613
Date: Thu, 28 Jun 2018 08:14:28 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: "v6ops@ietf.org list" <v6ops@ietf.org>
Message-ID: <D8CD13C6-FA27-47F8-A18E-AE696C343539@consulintel.es>
Thread-Topic: [v6ops] draft-palet-v6ops-nat64-deployment-02 comments
References: <663F489C-7F63-4B0C-A5E6-F7EE4634E62B@gmail.com> <ED663F6E-C63B-4FEC-913C-2CFF16249E93@consulintel.es> <9921F0BA-F2A5-4214-A133-1C8F4AF7CB6A@gmail.com>
In-Reply-To: <9921F0BA-F2A5-4214-A133-1C8F4AF7CB6A@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mQeEmPlp7gzgw0Yo0c3--2GOc_s>
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 06:14:39 -0000

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





-> Understood. I will improve the text to avoid that trivialization. However, I don't agree it doesn't works. What happens is that in that case, the connection in that case is done using the IPv4 stack of both peers (so the dual-stack host behind the CLAT CE, only see an "A" record, so naturally use only that one).

    




**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.