Re: [v6ops] reclassify 464XLAT as standard instead of info - double stack coexistence

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 25 September 2017 12:00 UTC

Return-Path: <alexandre.petrescu@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 031591332E3 for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 05:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 5qK5WUj_kxTe for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 05:00:56 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 C8D361321A1 for <v6ops@ietf.org>; Mon, 25 Sep 2017 05:00:55 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8PC0rBB073907; Mon, 25 Sep 2017 14:00:53 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 724CA201902; Mon, 25 Sep 2017 14:00:53 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 61D3F20943F; Mon, 25 Sep 2017 14:00:53 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8PC0rW4029476; Mon, 25 Sep 2017 14:00:53 +0200
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: v6ops@ietf.org
References: <D5E8043B.86B21%lee@asgard.org> <de6b9aac-a3cc-0915-77c7-9fb880c3a16a@gmail.com> <20170921223305.B72A8878E716@rock.dv.isc.org> <122454EE-64C5-4768-A6A9-1AD0E872F5F9@employees.org> <2a879713-bfd0-2ba0-cb67-53726f6e1faf@gmail.com> <41c808ef-b2c0-6e74-e61d-e89fcebe5e0a@gmail.com> <FA8911A1-CE3E-40E2-A11F-12303A3B4D1C@asgard.org> <e38bb7d2-1376-e790-8c20-19d54ec6b163@gmail.com> <alpine.DEB.2.20.1709251025270.18564@uplift.swm.pp.se> <30eddc4a-c2cc-0e6a-9a39-7db255705b16@gmail.com> <alpine.DEB.2.20.1709251152340.18564@uplift.swm.pp.se> <e5e878a2-c26e-57d4-5e23-718a16e7bc5a@gmail.com> <7CBE3779-8A7F-4A77-A83A-A73B20600C92@consulintel.es> <1130b720-3b6c-11ed-10dc-35dc4591e402@gmail.com> <254C395D-5903-4C40-857A-24AB396BA1FA@consulintel.es> <dc7cf11f-c184-6872-da29-f3892c373d77@gmail.com> <alpine.DEB.2.20.1709251244490.18564@uplift.swm.pp.se> <c75d178b-47ad-d062-e1f5-5fb57f848961@gmail.com> <alpine.DEB.2.20.1709251300210.18564@uplift.swm.pp.se>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5355a79c-27ae-942c-a970-6f847a181eea@gmail.com>
Date: Mon, 25 Sep 2017 14:00:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1709251300210.18564@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uV3O3f-BDWso7kbO-i58bQVuu54>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info - double stack coexistence
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: Mon, 25 Sep 2017 12:00:59 -0000


Le 25/09/2017 à 13:09, Mikael Abrahamsson a écrit :
> On Mon, 25 Sep 2017, Alexandre Petrescu wrote:
> 
>> On another hand, "double stack" is IPv4 and IPv6 at the same time,
>>  without any encapsulation nor translation, nor DNS-v4-v6.  Just
>> IPv4, IPv6 and DNS.
> 
> Where is this defined?

In my emails.

> I googled for "double stack" and IETF and I got ~900 hits.

So it's a place to grab.

I relate "double stack" to a "coexistence" item C) in an earlier RFC
INFORMATIONAL by B. Carpenter.

With that, I can put up a draft, if you are interested to participate.

This kind of "double stack" is what many deployments do, and easier to
tell than twisting one's tongue around v6v4v6v4.

> A lot of them seems to be from native french speakers, so I'd imagine
> there is some kind of translation from french that means some tend to
> use "double stack" instead of "dual stack"? "double stack" and IPv6
> yields 4k hits.

Well, I am not a native french speaker, but because you make a 
speculation on how it came up here is an explanation: I wanted to say 
"dual stack" in our email exchanges, but then I realized some people say 
"dual stack" to mean simultaneous IPv4 and IPv6 involving some 
translation/encap/DNSv4v6/sharing (RFCs like RFC6333, RFC5555, RFC4213, 
RFC4241).

On another hand, no RFC talks about "dual stack" as simultaneous use of 
IPv4 and IPv6 without any form of translation, encap, RH, DNSv4v6, 
address sharing, etc.

So I propose "double stack" for that.

At least it's clear what I talk about.

Also, if you have some other more English term to denote that, (more 
English than "double stack"), then I am willing to use it.

Alex

> 
> "Dual stack" and ietf yields 75k hits and replacing ietf with ipv6 
> yields 364k hits.
>