IETF Logo Mail Archive

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

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 29 June 2017 00:37 UTC

Return-Path: <swmike@swm.pp.se>
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 7260D126B7F for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 17:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 9ntRgBWZzmAE for <v6ops@ietfa.amsl.com>; Wed, 28 Jun 2017 17:37:45 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C8CA1200ED for <v6ops@ietf.org>; Wed, 28 Jun 2017 17:37:45 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 61D19A7; Thu, 29 Jun 2017 02:37:42 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1498696662; bh=ndPgS0S5HaN9gxl29H/JBtQibWk7DGKuz7MmwWSr/Ag=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=j7socgjVNXxOHbE8h/iBVd4EipxMDL5/P+loZGDChcBaaNbrMmHZATYtfbxZmvm9b OC74n7EUPLgE+IZvgGsYOmKDf9XKad8vSkPlD7wpHBJLzkQuAed9kQeh7+K9a+I8mD HFMnp/UpY3cluOH7stUxipYnV3CeGRuxY1RWuT7c=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4A414A6; Thu, 29 Jun 2017 02:37:42 +0200 (CEST)
Date: Thu, 29 Jun 2017 02:37:42 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "stephan.lagerholm@yahoo.com" <stephan.lagerholm@yahoo.com>
cc: David Schinazi <dschinazi@apple.com>, IPv6 Ops WG <v6ops@ietf.org>
In-Reply-To: <222564725.789104.1498690743587@mail.yahoo.com>
Message-ID: <alpine.DEB.2.02.1706290236110.18195@uplift.swm.pp.se>
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> <222564725.789104.1498690743587@mail.yahoo.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1485285816-1498696662=:18195"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MkbhCrn9OWGtj3JE3DJejHi8_o8>
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: Thu, 29 Jun 2017 00:37:47 -0000

On Wed, 28 Jun 2017, stephan.lagerholm@yahoo.com wrote:

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

But that doesn't mean applications running on those IPv6 nodes can access 
IPv4 literals. If the node also implements a CLAT, then it can.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email