IETF Logo Mail Archive

Re: [v6ops] Supporting IPv6-only Networks with NAT64 and DNS64 section of draft-ietf-v6ops-rfc6555bis-01

Mark Andrews <marka@isc.org> Wed, 28 June 2017 22:00 UTC

Return-Path: <marka@isc.org>
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 C27A112EB39 for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 15:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 AY2UPU0r9VFG for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 15:00:35 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 6570612EB35 for <v6ops@ietf.org>; Wed, 28 Jun 2017 15:00:34 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 7FB4E24AE18; Wed, 28 Jun 2017 22:00:26 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 11CA4160047; Wed, 28 Jun 2017 22:00:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0160F16006D; Wed, 28 Jun 2017 22:00:30 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id C0RFaU21Sr-w; Wed, 28 Jun 2017 22:00:29 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id B553A160047; Wed, 28 Jun 2017 22:00:29 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 4FA447CB2073; Thu, 29 Jun 2017 08:00:25 +1000 (AEST)
To: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com>
Cc: IPv6 Ops WG <v6ops@ietf.org>, "dschinazi@apple.com" <dschinazi@apple.com>
From: Mark Andrews <marka@isc.org>
References: <149670589074.3841.10812713591494006570@ietfa.amsl.com> <C22244D7-ABF6-430B-8155-8D4C1C1382DF@apple.com> <FA0D06E7-47F9-4029-81D4-2D96BFDD5576@consulintel.es> <65F3C8F4-6533-4C15-83F9-64AFC0EFFA79@apple.com> <4AC6726C-142E-48E5-95CF-2C3AD3331441@consulintel.es> <738488839.469942.1498664001646@mail.yahoo.com>
In-reply-to: Your message of "Wed, 28 Jun 2017 15:33:21 +0000." <738488839.469942.1498664001646@mail.yahoo.com>
Date: Thu, 29 Jun 2017 08:00:25 +1000
Message-Id: <20170628220025.4FA447CB2073@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/h8k3onRYzc168XJnmpholIwcyiE>
Subject: Re: [v6ops] Supporting IPv6-only Networks with NAT64 and DNS64 section of draft-ietf-v6ops-rfc6555bis-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Jun 2017 22:00:37 -0000

In message <738488839.469942.1498664001646@mail.yahoo.com>, "stephan.lagerholm@
yahoo.com" writes:
> Hi David,
> Thanks for adding the Supporting IPv6-only Networks with NAT64 and DNS64
> section, I find it useful. However I don't think the below sentence from
> this section is accurate. I can't think of any changes that are needed on
> a client device to run NAT64/DNS64. 

Well you obviously don't have any devices doing DNSSEC validation.
DNS64 breaks DNSSEC as it changes the DNS responses from NOERROR
NODATA to NOERROR DATA by synthesizing a AAAA RRset.  This from the
client's perspective is not different than forging a fake AAAA RRset
that is trying to hijack the traffic stream.

Now very few, if any, mobile phones perform DNSSEC but there are
laptop and desktop machines that do.

> While many IPv6 transition protocols have been standardized and   
> deployed, most are transparent to client devices.  The combined use   of
> NAT64 [RFC6146] and DNS64 [RFC6147] is a popular solution that is   being
> deployed and requires changes in client devices.
> Thanks, Stephan

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

v2.23.0 | Report a Bug | By Email