Re: [v6ops] WGLC: draft-ietf-v6ops-ipv6-deployment

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 11 April 2022 21:20 UTC

Return-Path: <prvs=11001fae5b=jordi.palet@consulintel.es>
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 B7FED3A1BA7 for <v6ops@ietfa.amsl.com>; Mon, 11 Apr 2022 14:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.005
X-Spam-Level:
X-Spam-Status: No, score=-7.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 NISqlcJsDkl2 for <v6ops@ietfa.amsl.com>; Mon, 11 Apr 2022 14:19:56 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id C38E23A1B95 for <v6ops@ietf.org>; Mon, 11 Apr 2022 14:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1649711992; x=1650316792; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=bEiH61O/VMhvI/Y/vQ00Zgl4xRF76z55Dd D1cAEzmkA=; b=TZYqm+hvpfEr9mgv2MLTmXB2KA5yyeWz9ikhmFI6pHHvOEgfNo wPYjF3j4p9eOB+a5sndQ+GO2ChjKJUr45jEsgC5eO4/rRItJSgwV2uDHypd7i2vB r4k0tZ903Se8b6tHK80i2zt+zbG3LSflyjxzmu0ASnH0UlGk+LVXGa5GM=
X-Spam-Processed: mail.consulintel.es, Mon, 11 Apr 2022 23:19:51 +0200
Received: from [10.10.10.141] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000842840.msg for <v6ops@ietf.org>; Mon, 11 Apr 2022 23:19:51 +0200
X-MDRemoteIP: 2001:470:1f09:495:6494:ee3:77ca:bea5
X-MDHelo: [10.10.10.141]
X-MDArrival-Date: Mon, 11 Apr 2022 23:19:51 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=11001fae5b=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.60.22022702
Date: Mon, 11 Apr 2022 23:19:49 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <91FB6398-4592-4349-9FF1-1B08CD95DCB5@consulintel.es>
Thread-Topic: [v6ops] WGLC: draft-ietf-v6ops-ipv6-deployment
References: <BL0PR05MB5316218855CC3A9E72035B79AEE59@BL0PR05MB5316.namprd05.prod.outlook.com> <fc22549a-22de-0895-dbbf-2691e19a150f@gmail.com> <A8A29F5D-2BA0-4368-913F-F7B0E772587E@consulintel.es> <202204102024081707127@chinatelecom.cn> <6D2586A4-E5EE-488B-91F2-470726A23DDA@employees.org> <173b0559-6399-bbb3-cec2-1b46d7e41605@gmail.com> <EC0662E5-2633-47C8-A704-6DEAE13F3A5B@employees.org> <674A0D42-817E-4A7A-90DA-F589E2615A19@gmail.com> <CAM5+tA9LtqpgMHpnjfeQ9v8w5bEO8P=7T_BG9Vkc7mP4NoThig@mail.gmail.com>
In-Reply-To: <CAM5+tA9LtqpgMHpnjfeQ9v8w5bEO8P=7T_BG9Vkc7mP4NoThig@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3732563989_4279343953"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Fuuf_xdQiM1rTgvJHEqfeAm0rzg>
Subject: Re: [v6ops] WGLC: draft-ietf-v6ops-ipv6-deployment
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: Mon, 11 Apr 2022 21:20:02 -0000

In Spanish, migration and transition is not the same.

 

Migration is moving from Windows XP to Windows Vista, you don’t keep both together. In English may have a different connotation, but I still prefer to use “transition and coexistence” (the term that I prefer to use and teach my customers – I also tell them there are no migration mechanisms but “transition and coexistence”).

 

In scenarios for IPv4 to IPv6 “transition and coexistence”, you have different parts of the network that may be IPv4-only, IPv6-only, dual-stack, IPv4aaS or even IPv6aaS.

 

Clearly I need to retake the work on https://www.ietf.org/archive/id/draft-palet-v6ops-ipv6-only-05.txt. Will try this week, so we can reference to it in this document for a more complete definition.

 

Regards,

Jordi

@jordipalet

 

 

 

El 11/4/22, 20:15, "v6ops en nombre de Nick Buraglio" <v6ops-bounces@ietf.org en nombre de buraglio@es.net> escribió:

 

 

 

On Mon, Apr 11, 2022 at 11:09 AM Fred Baker <fredbaker.ietf@gmail.com> wrote:



> On Apr 10, 2022, at 2:43 PM, otroan@employees.org wrote:
> 
> There seems to be little agreement on what "IPv6 only" means (it's all about perspective) and there is even less for how to get there.

I dunno. I would follow the dictionary on what the word "only" means. "IPv6-only", in my mind, means that IPv4 is turned off, at least in any equipment that natively switches IPv6. When folks talk about IPv4 as a service ("IPv4AAS"), in my mind that means that if IPv4 is switched at all, it is handled in a different way than IPv6.


I get a little lost when people argue about what "IPv6-only" means. There aren't many choices.

 

I agree that "IPv6-only" should be defined in detail toward the beginning of the document. My experience with migration to IPv6-only is exactly as described in your prior email: It is interpreted as something being "taken away" (IPv4), even though that is not the case, per se, and evokes an emotional fight or flight response.  I don't know if it's useful or not, but in much of the work I have been involved in we defined "IPv6-only" as (paraphrasing): the disabling, lack of availability, or other absence of IPv4 on a system, with access to IPv4 resources provided by an alternative, intermediate mechanism. 

 

>What I am saying is that the phrase "IPv6-only" has an immediate *emotional* impact on the reader, and every time you use it, you repel exactly the people we are trying to reach: enterprise and ISP operators > whose entire job today depends on IPv4.

 

Agreed. Regardless of the definition, I have found that there is very much ambiguity in what "IPv6-only" means in the context of operational network functionality. The most common implication is that there will be no access to IPv4, and that's not generally the case, which feels like it's addressed in section 4.1, and specifically in section 5.  

 

One other suggestion:

 

 > "As noted, the pandemic may have influenced the ICT industry including the dynamic of the address allocations." 

 

Not that we want another, different pandemic, it would probably be a good idea to clarify that this was driven by the COVID-19 pandemic since this document will be long-lived.  

 

 


https://www.google.com/search?q=definition+only
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

ᐧ

_______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.