[v6ops] Call for adoption: draft-peng-v6ops-hbh
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sat, 11 September 2021 13:28 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 946D43A14DB for <v6ops@ietfa.amsl.com>; Sat, 11 Sep 2021 06:28:43 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 QEKVl6-ITmmu for <v6ops@ietfa.amsl.com>; Sat, 11 Sep 2021 06:28:41 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id F1AA63A14DA for <v6ops@ietf.org>; Sat, 11 Sep 2021 06:28:38 -0700 (PDT)
Received: from GF-MBP-2.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 4DCE21B00238; Sat, 11 Sep 2021 14:28:02 +0100 (BST)
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: v6ops@ietf.org
Message-ID: <0997ef5a-e019-a120-51ec-b960b926d605@erg.abdn.ac.uk>
Date: Sat, 11 Sep 2021 14:28:01 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------CF5E0E370F4B2775C22D3CEC"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PMzgNWs_fyTdo4jJcu9qyz2C3EA>
Subject: [v6ops] Call for adoption: draft-peng-v6ops-hbh
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: Sat, 11 Sep 2021 13:28:44 -0000
I read draft-peng-v6ops-hbh as a part of thinking about the adoption call in v6OPS. * I do think that it would be useful for v6OPS to produce an Informational RFC in this topic. As someone who reviews documents across different areas, I'd be keen to understand the limitations and short-term plans for using and evolving equipment - I see WG document as important in informing the standards process, especially if it has a representative cross-section of equipment vendors/operators (which I am not). * I think the present discussion provided in the ID is likely had some particular size of router in mind, and I expect that does need to come across better in scoping the information provided. e.g. I can find a software a v6 router in my AP, and in an IoT gateway... and many other places, this I think isn't the target of this ID? Actually, I suspect the IETF just needs some (new?) commonly understood terms and I don't see this as a problem to adoption, but I think it will be a problem that needs to be addressed before WGLC, especially if this to be utilized by other WGs as an input! * I do have one issue: I realise there can be a fine line between understanding what is feasible/useful and best current preactive on one hand, and placing requirements on future specifictaions on the other. I would be concerned if such an informational draft from the OPS area attempts to constrain development of INT area standards track specs and I think the present current section 7 and 8 do have several parts that cross that line, to me, these need to be rephrased here (or omitted). I'dd hope that co-ordination with 6man can ensure that these operational considerations do reach the people developing the specs. Gorry Fairhurst
- [v6ops] Call for adoption: draft-peng-v6ops-hbh Gorry Fairhurst
- Re: [v6ops] Call for adoption: draft-peng-v6ops-h… Pengshuping (Peng Shuping)