[core] #374 (interfaces): Expand function set and OMA Object discussion

"core issue tracker" <trac+core@zinfandel.tools.ietf.org> Wed, 23 July 2014 19:29 UTC

Return-Path: <trac+core@trac.tools.ietf.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6096A1B2C10 for <core@ietfa.amsl.com>; Wed, 23 Jul 2014 12:29:17 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 WE6_RULO3lpr for <core@ietfa.amsl.com>; Wed, 23 Jul 2014 12:29:16 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 282FE1B2C07 for <core@ietf.org>; Wed, 23 Jul 2014 12:29:16 -0700 (PDT)
Received: from localhost ([::1]:54646 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+core@trac.tools.ietf.org>) id 1XA2Dw-00064Q-38; Wed, 23 Jul 2014 12:29:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: core issue tracker <trac+core@zinfandel.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-core-interfaces@tools.ietf.org, zach@sensinode.com
X-Trac-Project: core
Date: Wed, 23 Jul 2014 19:29:12 -0000
X-URL: http://tools.ietf.org/core/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/374
Message-ID: <057.9e5d86d763642b8b7fdbf48acb4a7f1d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 374
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-core-interfaces@tools.ietf.org, zach@sensinode.com, core@ietf.org
X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: matthieu.vial@schneider-electric.com, zach.shelby@arm.com
Archived-At: http://mailarchive.ietf.org/arch/msg/core/sEBWzTizZVHnigUKYrksSY6mst8
Cc: core@ietf.org
Subject: [core] #374 (interfaces): Expand function set and OMA Object discussion
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: trac+core@zinfandel.tools.ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jul 2014 19:29:17 -0000

#374: Expand function set and OMA Object discussion

 Section 3 currently discusses an example of the use of a function set (RD
 interfaces) and OMA Objects. These should be expanded into their own sub-
 sections with more details and discussion. OMA references need to be
 updated to the final specification and registry. When does it make sense
 to use a standard object vs. standardise a function set in a spec vs.
 create a custom function set for a device?

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-core-
  zach@sensinode.com     |  interfaces@tools.ietf.org
     Type:  editorial    |     Status:  new
 Priority:  minor        |  Milestone:
Component:  interfaces   |    Version:
 Severity:  -            |   Keywords:
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/core/trac/ticket/374>
core <http://tools.ietf.org/core/>