IETF Logo Mail Archive

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

Bert Greevenbosch <Bert.Greevenbosch@huawei.com> Wed, 22 May 2013 06:16 UTC

Return-Path: <Bert.Greevenbosch@huawei.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 D554E21F9354 for <core@ietfa.amsl.com>; Tue, 21 May 2013 23:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.121
X-Spam-Level:
X-Spam-Status: No, score=-3.121 tagged_above=-999 required=5 tests=[AWL=-0.726, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 8wdkotGj+ilk for <core@ietfa.amsl.com>; Tue, 21 May 2013 23:16:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0A78121F8EA6 for <core@ietf.org>; Tue, 21 May 2013 23:16:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATA44562; Wed, 22 May 2013 06:15:11 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 22 May 2013 07:14:51 +0100
Received: from SZXEML451-HUB.china.huawei.com (10.82.67.194) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 22 May 2013 07:15:00 +0100
Received: from szxeml558-mbx.china.huawei.com ([169.254.7.152]) by szxeml451-hub.china.huawei.com ([10.82.67.194]) with mapi id 14.01.0323.007; Wed, 22 May 2013 14:14:54 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] draft-shelby-core-resource-directory: call for adoption
Thread-Index: AQHOVbnWG8UvoXuV20S+MiTF76ZA75kOeumAgAI/1zA=
Date: Wed, 22 May 2013 06:14:53 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB63D762BF6@szxeml558-mbx.china.huawei.com>
References: <CAPRuP3=X0owKUDVbppvcCRu149wL_EUY=s6_wo4tnujnxfBxJQ@mail.gmail.com> <D60519DB022FFA48974A25955FFEC08C0515CDFB@SAM.InterDigital.com>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C0515CDFB@SAM.InterDigital.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.162.63]
Content-Type: multipart/alternative; boundary="_000_46A1DF3F04371240B504290A071B4DB63D762BF6szxeml558mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Wed, 22 May 2013 06:16:51 -0000

+1

Bert

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Rahman, Akbar
Sent: 2013年5月21日 11:50
To: Andrew Mcgregor; core@ietf.org
Subject: Re: [core] draft-shelby-core-resource-directory: call for adoption

+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<mailto:andrewmcgr@google.com> | +61 4 8143 7128

v2.23.0 | Report a Bug | By Email