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

Fred Baker <fredbaker.ietf@gmail.com> Thu, 28 June 2018 12:40 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 3A7E4130EFC for <v6ops@ietfa.amsl.com>; Thu, 28 Jun 2018 05:40:19 -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 0qN-NGUk2vOe for <v6ops@ietfa.amsl.com>; Thu, 28 Jun 2018 05:40:17 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (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 68201130F91 for <v6ops@ietf.org>; Thu, 28 Jun 2018 05:40:17 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id g18-v6so716149uak.0 for <v6ops@ietf.org>; Thu, 28 Jun 2018 05:40:17 -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=UPuIpkZwyImvkSJjQq9ZythWlIJ1so8lwN0qvpJbPfs=; b=lczCTKkzFg7CmVfzwJ0gGvU6ZMhcq8QVAwuniH+vnsB2rbaDJ4ukwVgpeR17At4Hvl uxgcYGMiia6a534zXLdbt9nMVhtaRTc0NAp7Oqv3F0cnpKehmO0Iko0TLjwMwQBNCy9L ysHAgqXCuxSyaZfoyRRJgcQskJpt5Hrs8quiGN7YdnQN364YQ8vxfnVjPy/Hi/A+5jOF hjt6Zwxn/HIF0Q3octJPxUrqkaBzN18C8itBKM2z+Y+U8KZmdKN9wQ2F5isNfNGch9E8 Y7mSw51mqbhmtLpUKj3m8AE24W/buAqO0rWmse8bvAbHbvRe40I/oyyTMsyQepV0S8HH mUyA==
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=UPuIpkZwyImvkSJjQq9ZythWlIJ1so8lwN0qvpJbPfs=; b=X7NRR6cZXoVSEbHU1jEdTf/kZc7a+pqN9UQcq/8+lb95YrV4+5Wg3xfrzmCwXuU7t6 l+IpraO8qDs21TCzP7b+sP7d/w4Dmjj0ZO3XTcQWiX91YojsweXQoUpDTl/HcXg2Chx8 lGJQesmvGY1O46KAlMpRaV5/q/Sjgu6+aK4iO9tkAdIaMh8iA2RWPjsRiZj7WpQD+Gso PaVk8vyfN1zg7PoIa+f3e8X1eFwV6g2sKlKfgBo0UT2bcvwCK78tpLuQz8Y1MY8nUBit VtdpMnRGIHa1KRzVX0+FLHS/pHBmaoFZ/81V44jbUP04GvIy7qcv1vmeN+mj52S/L1iJ RScw==
X-Gm-Message-State: APt69E3UZZawJMwQN1WAQ4ohi+6NYDCFFSr4GfwgXKNwgAPMC8dlnRXj iyOATY4dMHEzaVseTkvyNdE=
X-Google-Smtp-Source: AAOMgpeGE/Yp9dtPhtXBcQdvD8m9gmn321doBtDPtgNWn6LK8EHemepZPqyk7iIwHVCni4EQxAq4qQ==
X-Received: by 2002:ab0:4a53:: with SMTP id r19-v6mr6292919uae.98.1530189616469; Thu, 28 Jun 2018 05:40:16 -0700 (PDT)
Received: from [10.196.220.133] (41-197.icannmeeting.org. [199.91.197.41]) by smtp.gmail.com with ESMTPSA id c10-v6sm1956359vka.56.2018.06.28.05.40.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jun 2018 05:40:15 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <591F72A8-0E55-462E-BE4F-F1EB00E93FFC@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7F04217C-E0D3-4BFC-9FEC-E5502B91CE38"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 28 Jun 2018 07:40:13 -0500
In-Reply-To: <A85DCA2A-6204-4132-A936-CFAEAB6BED2F@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> <9921F0BA-F2A5-4214-A133-1C8F4AF7CB6A@gmail.com> <D8CD13C6-FA27-47F8-A18E-AE696C343539@consulintel.es> <CD5C71C5-418A-4CB1-8F47-28C33FBB28CA@gmail.com> <A85DCA2A-6204-4132-A936-CFAEAB6BED2F@consulintel.es>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yWSnHN-F8BvC1PbPK8T-myGorMI>
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 12:40:19 -0000


On Jun 28, 2018, at 7:30 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> Do you think it makes sense today for a smart OS or app provider, knowing that that app need to talk to IPv4-only hosts, to make that app or OS, IPv6-only?

I'm not making a market statement. I'm looking at a technical scenario, which I laid out in email yesterday. It could be IPv6-only because the network didn't give it an IPv4 address, to pick one possible reason out of a cloud of possible ones. The point is, it *is*, and if the peer it wants to talk with doesn't have a AAAA record, whether native or DNS64, it can't.

So the failure of DNSSEC when DNS64 is used isn't the only issue. Connectivity is also an issue. That's my whole point.