IETF Logo Mail Archive

Re: [core] draft-shelby-core-resource-directory: call for adoption

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Tue, 21 May 2013 03:49 UTC

Return-Path: <Akbar.Rahman@InterDigital.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD3121F8A14 for <core@ietfa.amsl.com>; Mon, 20 May 2013 20:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fY+mk5JDW9Ax for <core@ietfa.amsl.com>; Mon, 20 May 2013 20:49:50 -0700 (PDT)
Received: from smtp-out1.interdigital.com (smtp-out1.interdigital.com [64.208.228.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1887621F8A6B for <core@ietf.org>; Mon, 20 May 2013 20:49:47 -0700 (PDT)
Received: from SAM.InterDigital.com ([10.30.2.12]) by smtp-out1.interdigital.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 20 May 2013 23:49:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE55D6.3C4B3F2C"
Date: Mon, 20 May 2013 23:49:47 -0400
Message-ID: <D60519DB022FFA48974A25955FFEC08C0515CDFB@SAM.InterDigital.com>
In-Reply-To: <CAPRuP3=X0owKUDVbppvcCRu149wL_EUY=s6_wo4tnujnxfBxJQ@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [core] draft-shelby-core-resource-directory: call for adoption
Thread-Index: Ac5VuhshktZQGQGJQq2XAAKuosju+wAG/3lg
References: <CAPRuP3=X0owKUDVbppvcCRu149wL_EUY=s6_wo4tnujnxfBxJQ@mail.gmail.com>
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: Andrew Mcgregor <andrewmcgr@google.com>, core@ietf.org
X-OriginalArrivalTime: 21 May 2013 03:49:46.0764 (UTC) FILETIME=[3C8E3CC0:01CE55D6]
Subject: Re: [core] draft-shelby-core-resource-directory: call for adoption
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 21 May 2013 03:49:55 -0000

+1

 

 

Akbar

 

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of
Andrew Mcgregor
Sent: Monday, May 20, 2013 8:26 PM
To: core@ietf.org
Subject: [core] draft-shelby-core-resource-directory: call for adoption

 

Consensus of the room in Orlando was to adopt
draft-shelby-core-resource-directory as a working group document.  This
email is a call for confirmation of that consensus.  Please respond if
you support the adoption of this document.


>From the charter:

    5) A definition of how to use CoAP to advertise about or query for a
    Device's description. This description may include the device name
and
    a list of its Resources, each with a URL, an interface description
URI
    (pointing e.g. to a Web Application Description Language (WADL)
    document) and an optional name or identifier. The name taxonomy used
    for this description will be consistent with other IETF work,
    e.g. draft-cheshire-dnsext-dns-sd.

RFC 6690 has some of this; the resource directory would add protocol
elements on top of CoAP that enhance the "advertise about or query
for" aspect.

* Feb 2014 Submission to IESG of "CoRE Resource Directory" for
  Proposed Standard

-- 

Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 8143 7128

v2.23.0 | Report a Bug | By Email