[Iotops] Alissa Cooper's Block on charter-ietf-iotops-00-09: (with BLOCK and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Thu, 21 January 2021 13:53 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: iotops@ietf.org
Delivered-To: iotops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26BF13A0DEB; Thu, 21 Jan 2021 05:53:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: iotops-chairs@ietf.org, iotops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <161123720749.26475.15346633681665853684@ietfa.amsl.com>
Date: Thu, 21 Jan 2021 05:53:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/cA-fQbTc0ZqCS8HvN6LRj6YtyVA>
Subject: [Iotops] Alissa Cooper's Block on charter-ietf-iotops-00-09: (with BLOCK and COMMENT)
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 13:53:34 -0000
Alissa Cooper has entered the following ballot position for charter-ietf-iotops-00-09: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-iotops/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- (1) I agree with Alvaro that the reference to RFC 8799 is not appropriate in this charter. Using the well understood "administrative domain" terminology would be better. (2) The charter contains some contradictory language about its scope. Looking at this: "The IETF is or has worked on a number of technologies related to IoT. These include work done in ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, and 6TISCH. IOTOPS is intended to be a discussion venue where people can discuss how the various technologies developed in these WGs fit together, what gaps remain, what has been learnt from deploying these, etc. IOTOPS will solicit input on IoT-device-related operational issues and practices, and existing and proposed technologies related to the deployment, operational management, and lifecycle management of IoT devices. IOTOPS provides a venue for IoT experts and other interested parties to engage in discussions of IoT requirements of networking standards, as well as proposals for new uses of IP technology in IoT specific scenarios." Comparing this to the numbered list of work areas at the end of the charter, it seems that the objective is to be much more focused than the text above implies. I would suggest some edits to the text above, condensing down to one paragraph: The IETF is or has worked on a number of technologies related to IoT. These include work done in ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, and 6TISCH. IOTOPS will solicit input on IoT-device-related operational issues and practices, and existing and proposed technologies related to the deployment, operational management, and lifecycle management of IoT devices. IOTOPS provides a venue for IoT experts and other interested parties to engage in discussions of operational IoT requirements, as well as proposals for new uses of IP technology related to IoT device and network operations. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- s/The IETF is or has worked on/The IETF works on/ OLD These include work done in ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, and 6TISCH. NEW This includes work done in ANIMA, CBOR, CORE, DRIP, LAKE, LPWAN, LWIG, ROLL, SUIT, 6TISCH, and other working groups. Is the list of WGs supposed to be limited or exhaustive? In addition to the missing ones others have pointed out there is TEEP. OLD Revision, updates, and extensions related to existing WGs will be done in those WGs. NEW Revision, updates, and extensions related to work in existing WGs will be done in those WGs.
- [Iotops] Alissa Cooper's Block on charter-ietf-io… Alissa Cooper via Datatracker
- Re: [Iotops] Alissa Cooper's Block on charter-iet… Toerless Eckert
- Re: [Iotops] Alissa Cooper's Block on charter-iet… Michael Richardson
- Re: [Iotops] Alissa Cooper's Block on charter-iet… Rob Wilton (rwilton)
- Re: [Iotops] Alissa Cooper's Block on charter-iet… Brian E Carpenter