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

"stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com> Wed, 28 June 2017 23:01 UTC

Return-Path: <stephan.lagerholm@yahoo.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 F07C2124C27 for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 16:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level:
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, REPTO_QUOTE_YAHOO=0.646, RP_MATCHES_RCVD=-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=yahoo.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 Ci_fX6mJ6_oN for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 16:01:28 -0700 (PDT)
Received: from sonic307-14.consmr.mail.ne1.yahoo.com (sonic307-14.consmr.mail.ne1.yahoo.com [66.163.190.37]) (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 AEADB1298BA for <v6ops@ietf.org>; Wed, 28 Jun 2017 16:01:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1498690887; bh=93hQVpoWPfkFhDf62Ma6vA3NRVOp8EOrFxiLSq4Dslo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=nUgUpAiVVG2RhWukekRM6/wsUW0WSuZTwrKgUBVMMJRWMifOjS3sYfs9nEIVbZusSGtHdKlBWGqHukjqhzZ/TVYi4gxADE5upsRJ/DTZwX9GJx+UmG1McgpzWJzyVavzyASvXFWKA/DT2H+30/URTzKe2T5eKjteyeV/R14N5LYOWspwk5MwwPMxvrfLMXibCysxguo+LGrlitW3d74Z2Wavb3qCvr5ylk/LwgkMV9ODEAk9qDVki7DJHtA2Ak2o0s9u/7QKt49VN8iDiRrFzGsI+nOlRA75Ze/K2UIOI53b2/g/7xsapyg8Vz0w/M/ie3BQdyxyGWi/JtAkPNSDBw==
X-YMail-OSG: aARwFMkVM1l5BA7uWOvMeej28K1NeNw4qttfFQpNWFvKwO.8i0qe9aZkYuMxKof ry17pjPnP3jbyZ0gEQWOtANSmTZCCwVmBcVe60_c.QlpHer7zcHZCKSJO0yGOzkzutul6qPhgGZI FVMfUJe6J.RXn365r8h3cgxj4ExRojjxCvsuuRNqfUpgEvtrFFQkQkcszDgE1OQC9roHrG3iYXqK A8IYhs.Dh0YTqLRVdmSwYzN71h4FRiE4BsFGz7g9nG8Oaby_S5sAl8qivlrRQ29G_XHWOhX_SXIl tWlvh1Mrd8EXRq7.MAleLy7qSCNAOzGL9SlNQJFrkdcyPwYhv1n2TUm0jiH8k1W0JFHQucWeE3yk yAUTVBuhaYsnh9JOLzOJFtZWS5dfT68xW4jwbXk55dtDwJnYeW8SBxgtbA4OVDV.Xu9IGCVVcwQs zedyK.aKBS1uuL1DIrQk1AHnMr3Twy7sn5yafIKMpMPWBB0bGv.ula.tatFo5Cd4J65JQ84KqoDe ZmX8dBIXPgpI5APdc_QW6JfSRTRGTruexe1CqDQ--
Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ne1.yahoo.com with HTTP; Wed, 28 Jun 2017 23:01:27 +0000
Date: Wed, 28 Jun 2017 22:59:03 +0000
From: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com>
Reply-To: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com>
To: David Schinazi <dschinazi@apple.com>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <222564725.789104.1498690743587@mail.yahoo.com>
In-Reply-To: <A15C4444-B457-40B8-BCC0-3C40A4F1E3AA@apple.com>
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> <B6F787DF-E3FA-4C79-A6DC-5D17EBDCCBD5@apple.com> <546799735.505039.1498665245952@mail.yahoo.com> <A15C4444-B457-40B8-BCC0-3C40A4F1E3AA@apple.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_789103_799626798.1498690743582"
X-Mailer: WebService/1.1.9978 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qD-Cps8teXc3VujaedOV9jezqF0>
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 23:01:30 -0000

Fair enough, the Dual stack example is not applicable in this section. I'm hung up that the draft says that it requires changes on in client devices because it contradicts RFC 6174 section 2 that says that current IPv6 nodes can use this mechanism without requiring any modifications. 

The first option is to locate the DNS64 function in authoritative
   servers for a zone.  In this case, the authoritative server provides
   synthetic AAAA RRs for an IPv4-only host in its zone.  This is one
   type of DNS64 server.

   Another option is to locate the DNS64 function in recursive name
   servers serving end hosts.  In this case, when an IPv6-only host
   queries the name server for AAAA RRs for an IPv4-only host, the name
   server can perform the synthesis of AAAA RRs and pass them back to
   the IPv6-only initiator.  The main advantage of this mode is that
   current IPv6 nodes can use this mechanism without requiring any
   modification.

      From: David Schinazi <dschinazi@apple.com>
 To: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com> 
Cc: IPv6 Ops WG <v6ops@ietf.org>
 Sent: Wednesday, June 28, 2017 3:00 PM
 Subject: Re: Supporting IPv6-only Networks with NAT64 and DNS64 section of draft-ietf-v6ops-rfc6555bis-01
   
This section is titled "Supporting IPv6-only Networks with NAT64 and DNS64", dual-stack is out of scope of this section.
Am I missing something?
Thanks,David Schinazi



On Jun 28, 2017, at 08:54, stephan.lagerholm@yahoo.com wrote:
Hi David,
Yes I have. 464XLAT or anything else is not required to be able to run DNS64/NAT64. You can run DNS64/NAT64 in combination with Dual Stack if you want to. 
/S

      From: David Schinazi <dschinazi@apple.com>
 To: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com> 
Cc: IPv6 Ops WG <v6ops@ietf.org>
 Sent: Wednesday, June 28, 2017 8:37 AM
 Subject: Re: Supporting IPv6-only Networks with NAT64 and DNS64 section of draft-ietf-v6ops-rfc6555bis-01
  
Hi Stephan,
Have you read the rest of that section that details the changes required on client devices?

Thanks,
David Schinazi

On Jun 28, 2017, at 08:33, "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com> wrote:


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