[6tisch] Benoit Claise's No Objection on charter-ietf-6tisch-01-00: (with COMMENT)
"Benoit Claise" <bclaise@cisco.com> Thu, 21 January 2016 13:54 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: 6tisch@ietf.org
Delivered-To: 6tisch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 039CC1A7021; Thu, 21 Jan 2016 05:54:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benoit Claise <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160121135453.31521.28387.idtracker@ietfa.amsl.com>
Date: Thu, 21 Jan 2016 05:54:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/4KZ6I30HOYxdJ97C7l5fNCxVjVk>
Cc: 6tisch@ietf.org, 6tisch-chairs@ietf.org
Subject: [6tisch] Benoit Claise's No Objection on charter-ietf-6tisch-01-00: (with COMMENT)
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2016 13:54:54 -0000
Benoit Claise has entered the following ballot position for charter-ietf-6tisch-01-00: No Objection 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-6tisch/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Not a block, but I would like to discuss the "OPS" situation in the charter/WG. Looking at this paragraph: - Produce an Information Model containing the management requirements of a 6TiSCH node. This includes describing how an entity can manage the TSCH schedule on a 6TiSCH node, and query timeslot information from that node. A data model mapping for an existing protocol (such as Concise Binary Object Representation (CBOR) over the Constrained Application Protocol (CoAP)) will be provided. This work depends on the standardization of a method to access management data resources in constrained devices, such as proposed by CoMI or COOL. I wonder if this paragraph is still accurate? There is this WG document, for a YANG data model, https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface-04, on which I commented during one of the interim call. So the YANG model should be specifically mentioned. Also, will the WG still produce an information model? If not, "information model" should be removed
- [6tisch] Benoit Claise's No Objection on charter-… Benoit Claise