Re: [v6ops] reclassify 464XLAT as standard instead of info

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 25 September 2017 10:12 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 6AC141332DA for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 03:12:31 -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 pLoGkXK12Kbh for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 03:12:30 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 E8303133210 for <v6ops@ietf.org>; Mon, 25 Sep 2017 03:12:29 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8PACRUL032840; Mon, 25 Sep 2017 12:12:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D7E1B209280; Mon, 25 Sep 2017 12:12:27 +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 C7E672091B9; Mon, 25 Sep 2017 12:12:27 +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 v8PACR5I009262; Mon, 25 Sep 2017 12:12:27 +0200
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Erik Kline <ek@google.com>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <E48DDA04-C058-4992-906E-8C8BC0E102AB@consulintel.es> <85868796-18C7-48F4-BE69-8D50A1F47EF3@jisc.ac.uk> <472CC0F7-73C2-4A21-8F96-BBC966B01B77@employees.org> <de6b9aac-a3cc-0915-77c7-9fb880c3a16a@gmail.com> <20170921223305.B72A8878E716@rock.dv.isc.org> <CAKD1Yr13ijKCB_71_2vMyGurc3-kSraLJycGxZwf121tjp8u1Q@mail.gmail.com> <20170922070719.74AA687A424E@rock.dv.isc.org> <20170922114847.GV45648@Space.Net> <369B3917-D9F3-41D4-A7BD-DAE134310004@employees.org> <20170922122146.GY45648@Space.Net> <20170922212502.E0CFF87B00BA@rock.dv.isc.org> <CAKD1Yr0VdmS0APz-G5VmxMNY1y9Kj+g0VP4Jx0_MXLkqkVyE8Q@mail.gmail.com> <4bf16a40ffd44e9498babf7094b1e526@orange.com> <f8b54014-c5af-d63f-5eed-35f19728b4f7@gmail.com> <0E9B8640-E102-4AB0-8908-28A988795861@consulintel.es> <ba63f464-cf1e-69d1-4d34-c961a8fef286@gmail.com> <CAAedzxqEeh4o4o=ZZbFh62XyjoiiKLPO__7HEE2CZxw9VWcUjw@mail.gmail.com> <9862ff34-8eea-c18a-88e5-d017630efefa@gmail.com> <alpine.DEB.2.20.1709251202500.18564@uplift.swm.pp.se>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c0fc3043-d416-aaa7-152e-89b2a7e7c53b@gmail.com>
Date: Mon, 25 Sep 2017 12:12:27 +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.1709251202500.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/Q-st8U89x7g-JY67ziNgU94zSKU>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
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 10:12:31 -0000


Le 25/09/2017 à 12:04, Mikael Abrahamsson a écrit :
> On Mon, 25 Sep 2017, Alexandre Petrescu wrote:
> 
>> I agree with this definition of "IPv6-only network".  I would stress 
>> to also mean "no IPv4" - be it encapsulation, translation, or DNS-x-y.
> 
> You're in extreme minority to have that definition.

Excuse me, but that's used in many networks.

> I don't care if my IP packet provider carries my packets over POS, 
> ethernet, if they run native IPv4, IPv6 or MPLS in their core, if they 
> use LDPv4 or LDPv6 for their control plane etc. What I care about is 
> what I need to configure my equipment with to talk to them.

If they _can_ provide IPv4 too, then use it.

Dont make funny translations.  Translations break other matters in the 
Internet, like we saw with NAT.

> So an IPv6 only access uses only IPv6 packets in the access line, that 
> the device can see. What happens in the ISP network once the packets 
> hits that part is out of scope for the definition of IPv6 only access.

I agree, but dont make it look as if the network cant do IPv4.

If it can, then use it.

This very important.

Alex



>