[core] Benoit Claise's Block on charter-ietf-core-01-01: (with BLOCK)
"Benoit Claise" <bclaise@cisco.com> Tue, 20 October 2015 21:03 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 629C31B350B; Tue, 20 Oct 2015 14:03:04 -0700 (PDT)
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.6.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151020210304.27062.87223.idtracker@ietfa.amsl.com>
Date: Tue, 20 Oct 2015 14:03:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/e8c8bqLJRhUcq6ixzNS5FauyZe8>
Cc: core-chairs@ietf.org, core@ietf.org
Subject: [core] Benoit Claise's Block on charter-ietf-core-01-01: (with BLOCK)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 21:03:04 -0000
Benoit Claise has entered the following ballot position for charter-ietf-core-01-01: 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-core/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- Two points I would like to discuss. - "CoRE will also develop a way to make RESTCONF-style management functions available via CoAP that is appropriate for constrained node networks. This will require very close coordination with NETCONF and other operations and management working groups." What is the goal of this coordination with NETCONF? Could RESTCONF be reused? If not, why not? If yes, will RESTCONF need to be modified? - What is the data model (language) used for the resources? For example, RESTCONF uses YANG Maybe, this information is in this paragraph CoRE will work on related data formats, such as alternative representations of RFC 6690 link format and RFC 7390 group communication information. The working group will complete the SenML specification, again with consideration to its adoption in OMA LWM2M. However, I have no clue what the second sentence means.
- [core] Benoit Claise's Block on charter-ietf-core… Benoit Claise
- Re: [core] Benoit Claise's Block on charter-ietf-… Carsten Bormann
- Re: [core] Benoit Claise's Block on charter-ietf-… Benoit Claise
- Re: [core] Benoit Claise's Block on charter-ietf-… Barry Leiba
- Re: [core] Benoit Claise's Block on charter-ietf-… Carsten Bormann
- Re: [core] Benoit Claise's Block on charter-ietf-… Barry Leiba
- Re: [core] Benoit Claise's Block on charter-ietf-… Benoit Claise
- Re: [core] Benoit Claise's Block on charter-ietf-… Barry Leiba
- Re: [core] Benoit Claise's Block on charter-ietf-… Barry Leiba