IETF Logo Mail Archive

Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 24 November 2021 11:24 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 C29DF3A0D90 for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 03:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.184
X-Spam-Level:
X-Spam-Status: No, score=-1.184 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.852, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 EXNLkWbZ7ceh for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 03:24:04 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 7396B3A0D8E for <v6ops@ietf.org>; Wed, 24 Nov 2021 03:24:04 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 1AOBO1Pv007280 for <v6ops@ietf.org>; Wed, 24 Nov 2021 12:24:01 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BAD14205507 for <v6ops@ietf.org>; Wed, 24 Nov 2021 12:24:01 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B093A205504 for <v6ops@ietf.org>; Wed, 24 Nov 2021 12:24:01 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 1AOBO1w2024880 for <v6ops@ietf.org>; Wed, 24 Nov 2021 12:24:01 +0100
Message-ID: <a00af37c-6fc2-0122-2cdc-55f49ff61d02@gmail.com>
Date: Wed, 24 Nov 2021 12:24:01 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
Content-Language: fr
To: v6ops@ietf.org
References: <CAKD1Yr0z-XckGv5L_9qu5w_6mU=O1h5nZWoTNw6GmStHQ8tzYA@mail.gmail.com> <932B1725-6BA9-4C2E-AE45-6C8DECB640B5@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <932B1725-6BA9-4C2E-AE45-6C8DECB640B5@employees.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UxX8urwBQXfS9K7W0GY1SS3_mUk>
Subject: Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2021 11:24:09 -0000


Le 24/11/2021 à 09:03, Ole Troan a écrit :
> 
> 
>> On 24 Nov 2021, at 03:26, Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org> wrote:
>>
>> Is there any data on what IPv4aaS transition mechanisms are deployed by ISPs today? I was approached by a router vendor asking me "how they should provide IPv6-only" and I was looking for data on which mechanisms are most common
> 
> IPv4aaS != IPv6 only.

I agree.

If I were an ISP and wanted to give an 'IPv6-only' connection to an 
in-residence network then I would just put IPv6 on it, not IPv4. 
Further, one might even block any form of IPv4 traffic be that native or 
carried in IPv6 packets.

This is why it is important to know what do they mean by 'IPv6-only'.

Alex

> 
> I doubt you will get an answer here. This is a bike shedding argument as good as any.
> 
> They should check out what’s deployed in their target market. Just like any other feature.
> 
> O.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email