Re: [v6ops] Call For Adoption: draft-ietf-v6ops-ipv6-deployment

Nick Hilliard <nick@foobar.org> Tue, 08 June 2021 16:30 UTC

Return-Path: <nick@foobar.org>
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 841203A35D1 for <v6ops@ietfa.amsl.com>; Tue, 8 Jun 2021 09:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 UK_p7BXOoCGg for <v6ops@ietfa.amsl.com>; Tue, 8 Jun 2021 09:30:26 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC3F73A35CD for <v6ops@ietf.org>; Tue, 8 Jun 2021 09:30:25 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 158GUBUb004275 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jun 2021 17:30:11 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <BL0PR05MB5316B21F3D035339CEE892F0AE3D9@BL0PR05MB5316.namprd05.prod.outlook.com> <7211c26d-5fe4-cf8a-f24a-afd9bb09eb64@foobar.org> <44aac8a2b6dd4b8a95e8f0499a9d631a@huawei.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <da2e3664-6766-8c3f-d004-07aa10e945a1@foobar.org>
Date: Tue, 08 Jun 2021 17:30:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.48
MIME-Version: 1.0
In-Reply-To: <44aac8a2b6dd4b8a95e8f0499a9d631a@huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RSUUQ0RyVYe_iu_sPHhNdyP_oBY>
Subject: Re: [v6ops] Call For Adoption: 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: Tue, 08 Jun 2021 16:30:28 -0000

Giuseppe Fioccola wrote on 08/06/2021 16:41:
> [GF]: I agree that the document needs to be improved but I disagree
> that this is not in scope of V6OPS WG.

The issue is not whether the content area is in scope for v6ops (clearly 
it is), just that there were enough fundamental problems with the 
structure and content of the document such that it isn't appropriate for 
adoption at the moment.  Specifically, 1. there seem to be three main 
strands in the document which don't fit together well, and 2. there's no 
beginning, middle and end to the document - after reading the document, 
I didn't have a clear picture of what it was trying to say.

I can't see a way of fixing this without complete restructuring from the 
beginning.  Maybe the individual strands could be made to work as 
standalone documents?  Possibly if the document started out with a 
formal design and was rewritten from scratch to fit inside this design, 
it would become more cohesive?  Either way, these are issues that need 
to be sorted before the document is adopted rather than after.

Nick