Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-deployment

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 29 March 2021 16:36 UTC

Return-Path: <giuseppe.fioccola@huawei.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 D8FEE3A1A5D; Mon, 29 Mar 2021 09:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 O4YOTXwTmB_r; Mon, 29 Mar 2021 09:36:45 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B24C3A1A5C; Mon, 29 Mar 2021 09:36:45 -0700 (PDT)
Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F8J2b57Tyz684Pj; Tue, 30 Mar 2021 00:29:59 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 29 Mar 2021 18:36:40 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2106.013; Mon, 29 Mar 2021 18:36:39 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: "STARK, BARBARA H" <bs7652@att.com>, 'Fred Baker' <fredbaker.ietf@gmail.com>, "'v6ops@ietf.org'" <v6ops@ietf.org>
CC: "'draft-lmhp-v6ops-transition-comparison@ietf.org'" <draft-lmhp-v6ops-transition-comparison@ietf.org>, "'draft-vf-v6ops-ipv6-deployment@ietf.org'" <draft-vf-v6ops-ipv6-deployment@ietf.org>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-deployment
Thread-Index: AQHXIsXkv/dCiwCMNkqKworNQJ5cEKqa9JgAgAA2X+A=
Date: Mon, 29 Mar 2021 16:36:39 +0000
Message-ID: <20a3bd8410f44f9d9673a3c79a6cc04b@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <59B5C1F7-48E4-4915-BAAC-41D8ADA29E8F@gmail.com> <18ea74665936408bb33f20630da95311@huawei.com> <E0757B36-8FFB-43A8-8F8B-A7F152F81156@gmail.com> <DM6PR02MB6924475E2A2E02BC0F79C02AC37E9@DM6PR02MB6924.namprd02.prod.outlook.com>
In-Reply-To: <DM6PR02MB6924475E2A2E02BC0F79C02AC37E9@DM6PR02MB6924.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.215.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lsb2XcVuxWlF5jeOcvwNGSbi4wM>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-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, 29 Mar 2021 16:36:48 -0000

Hi Barbara,
Thank you for being in favor of the adoption of draft-vf-v6ops-ipv6-deployment.
The fact that the configuration for 464XLAT and lw4o6 via TR-069 can be simple is relevant.

Regards,

Giuseppe

-----Original Message-----
From: STARK, BARBARA H [mailto:bs7652@att.com] 
Sent: Monday, March 29, 2021 5:12 PM
To: 'Fred Baker' <fredbaker.ietf@gmail.com>; 'v6ops@ietf.org' <v6ops@ietf.org>
Cc: 'draft-lmhp-v6ops-transition-comparison@ietf.org' <draft-lmhp-v6ops-transition-comparison@ietf.org>; 'draft-vf-v6ops-ipv6-deployment@ietf.org' <draft-vf-v6ops-ipv6-deployment@ietf.org>
Subject: RE: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-deployment

<sigh> This time with comments. </sigh>

> > For lmhp-v6ops-transition-comparison, on behalf of the authors of 
> > draft-vf-
> v6ops-ipv6-deployment I can say we are in favor of the WG adoption. 
> Not only is it a good description of the transition technologies to 
> IPv6, but it also constitutes a basis for our draft.
> 
> OK, let me put this to the working group. We asked about adoption of 
> draft- lmhp-v6ops-transition-comparison once before (in January 2020), 
> and got essentially no response. It has come up on the list twice 
> since, in July and in November. The authors of 
> draft-vf-v6ops-ipv6-deployment would like to see it adopted. The two 
> sets of authors are disjoint. I therefore have at least nine people 
> that would like to see us adopt and publish it. What other folks have opinions, pro or con?

I've looked at this draft and am not in favor of adopting it with its current scope and (lack of) focus.
I think the statistics will be stale before publication.
I was getting confused in reading various sections as to which market segment it was trying to address.
The draft jumps around various market segments in its various sections, and it's often unclear as to which market segment a section is referring to. I should point out that a lot of enterprise network equipment involved in IPv6 transition is also referred to as "CPE", since that is a generic term that means "Customer Premises Equipment". But the enterprise CPE that provides IP connectivity to the Internet and the mass market CPE that provides IP connectivity to the Internet are very dissimilar.

If this draft were to be more focused in what it wanted to accomplish, there might be something to adopt.

> Along the same lines, are there opinions regarding the adoption of 
> draft-vf- v6ops-ipv6-deployment?

I've looked at this draft and am in favor of adoption. I think it has some very useful and practical information.
One thing I'd like to mention is that if anyone wants configuration for 464XLAT and lw406 via TR-069, this is very simple to achieve. Just tell me what parameters you think are needed (like enable/disable and any parameters that need to be configured) and agree to review the proposed additions to TR-181 (which I would provide by email to specific people or I could liaise to the WG) and it can be in the next release of TR-181 (most likely end of this year).

Barbara