IETF Logo Mail Archive

Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 21 June 2022 22:14 UTC

Return-Path: <brian.e.carpenter@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 2E30DC14F72E for <v6ops@ietfa.amsl.com>; Tue, 21 Jun 2022 15:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.985
X-Spam-Level:
X-Spam-Status: No, score=-3.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.876, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEHg-wpyCSU1 for <v6ops@ietfa.amsl.com>; Tue, 21 Jun 2022 15:14:18 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 460B3C14F726 for <v6ops@ietf.org>; Tue, 21 Jun 2022 15:14:18 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id d14so10788142pjs.3 for <v6ops@ietf.org>; Tue, 21 Jun 2022 15:14:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=2rDsqEB0lAAXvJrzIx8U+W5DozNM/JVUO39hhSVdSGI=; b=l5/BlGsd38nthE9/GuwzJB2ywTJD7puD62t4JUsGzUv15JqUKSUqQ9mLfxFzjV5Fmr hXNGEa2yI3MzL4Gt8qTLEAZJsZBlugsKxVHFxF+QdK+NHpn5+KRpWxVhrLvYVB+7LTVa WDSEUolQWFyfbMtqr5s2bak9hEkD99gCavL6v+ZcmKPM8GhUd3LGxGsCxYVlYBLCX+7B 6FFJ2c1gBC6kTU4xtPU4xh3ZWHnevT+xAnRvXQpd+7FObPN1bBLndSDSrggSZJcFVtoF YWJBD1AU/UBjqWgqhpxLo8LyRmCR1p8hcyQQDLxzFrvN87oXq+YYvNKqnMYm1QQf3zo2 ig9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=2rDsqEB0lAAXvJrzIx8U+W5DozNM/JVUO39hhSVdSGI=; b=C5ctQ12wM8jCVhrIrjkjhUWWVsfO4stthQHlTkXD1HTZc2zMAKi8JFjlemk600KTvo awpxqwwUDonnxL5kvR8dPKM/6gn8GX4vUaGetk5do/hS+3DikE7D+4ztzBEu6fgLOWhd VOXsFGBZs67p5/kMw0dd+LsFD1kpWCdqFBcFGxoIfCYGVOZp81xYwogua+scLbKBKaWe 1NuXEwrkD/ZerFRZnahbsmutKDFVQh2l4H3mxAfN93CyJh0NEGV9DK8hTPohvaatZDAK W+SwttJAWkFn/q8n0Z1V/4KzNuoe0XZJUrvNE6SV5l9uwAGXeYVD2tZrH4ls5z8L8F1n BHyQ==
X-Gm-Message-State: AJIora+/EPXmVEk5/x0qSLHgKluBLbX12gtZrKPfhExe3JFPcR1lK8yA wTcpPO6S+Ku/S/0TC8xNtQzadOzLUahYAOPL
X-Google-Smtp-Source: AGRyM1sG+CC31jlAoxTZoJt5HDziIewgYFYJZAPJh5J0xd2a0dOssnmA76kTZMOhVJIOwMHgr+cBEw==
X-Received: by 2002:a17:902:e888:b0:16a:1b3d:aac4 with SMTP id w8-20020a170902e88800b0016a1b3daac4mr15752104plg.80.1655849657810; Tue, 21 Jun 2022 15:14:17 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 3-20020a621503000000b0052525ab06d5sm4545994pfv.78.2022.06.21.15.14.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Jun 2022 15:14:16 -0700 (PDT)
Message-ID: <2a300ad3-2da3-a911-4035-92f9e2481b80@gmail.com>
Date: Wed, 22 Jun 2022 10:14:11 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Chongfeng XIE <xiechf@chinatelecom.cn>
Cc: IPv6 Operations <v6ops@ietf.org>
References: <202206211427054870437@chinatelecom.cn> <CA+nkc8C89AmmrNS3ZkP=VVFt1fQ_8mHcz1YOMZi090V5Ofnbmg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CA+nkc8C89AmmrNS3ZkP=VVFt1fQ_8mHcz1YOMZi090V5Ofnbmg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/gqUXVVayXhPIJOD5TpDcbR65lgk>
Subject: Re: [v6ops] Fw: New Version Notification for draft-xie-v6ops-framework-multi-domain-ipv6only-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 21 Jun 2022 22:14:19 -0000

Hi,

I'd like to repeat my plea to *not* use the phrase "IPv6-only" in this way. It is a very misleading phrase because you do not propose to provide an IPv6-only service to users, but a dual stack service.

What you describe is an IPv6 underlay or an IPv6 transport network. It concerns internal choices by operators, not what the user sees. The title, file name, and Abstract of the draft should, in my opinion, carefully avoid the phrase "IPv6-only" to prevent irrational reactions. The objective is to provide dual-stack *service* without needing dual-stack infrastructure.

Something like:


               Framework of Multi-domain IPv6 Underlay Network
            draft-xie-v6ops-framework-multi-domain-ipv6-underlay-00

Abstract

    Dual-stack deployments originally required both IPv4 and IPv6
    transfer capabilities to be deployed in parallel.  For operators,
    supporting only IPv6 infrastructure, with global IPv4 provided
    as a an overlay service, is a preferable ultimate stage.  This
    document specifies requirements and proposes a general framework
    when deploying IPv6 as the underlay in a multi-domain network.


Regards
    Brian Carpenter

v2.23.0 | Report a Bug | By Email