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

Miika Komu <mkomu@cs.hut.fi> Thu, 30 May 2013 11:58 UTC

Return-Path: <mkomu@cs.hut.fi>
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 D42E121F930C for <core@ietfa.amsl.com>; Thu, 30 May 2013 04:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 6Vnu0mp95pCv for <core@ietfa.amsl.com>; Thu, 30 May 2013 04:57:46 -0700 (PDT)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id A896921F92FB for <core@ietf.org>; Thu, 30 May 2013 04:57:45 -0700 (PDT)
Received: from [127.0.0.1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTP id 21873308D72 for <core@ietf.org>; Thu, 30 May 2013 14:57:38 +0300 (EEST)
Message-ID: <51A73EB2.9030802@cs.hut.fi>
Date: Thu, 30 May 2013 14:57:38 +0300
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: core@ietf.org
References: <CAPRuP3=X0owKUDVbppvcCRu149wL_EUY=s6_wo4tnujnxfBxJQ@mail.gmail.com> <D60519DB022FFA48974A25955FFEC08C0515CDFB@SAM.InterDigital.com> <cc182ea3d25a7ffd75760f7ff4d4ef30@xs4all.nl> <15C704CA-839F-41CE-99C8-73DA52A0CBFB@sensinode.com> <51A45E73.80101@intec.ugent.be>
In-Reply-To: <51A45E73.80101@intec.ugent.be>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 30 May 2013 11:58:00 -0000

+1

On 05/28/2013 10:36 AM, Floris Van den Abeele wrote:
> +1
>
> Floris
> Op vr 24 mei 2013 17:03:01 CEST, Zach Shelby schreef:
>> Peter,
>>
>> I agree, as discussed in Orlando, we should integrate the DNS-SD
>> mapping to this document.
>>
>> Thanks,
>> Zach
>>
>> On May 21, 2013, at 9:47 AM, peter van der Stok <stokcons@xs4all.nl>
>> wrote:
>>
>>> I certainly support this, but with the remark that relation to DNS
>>> and DNS-SD should be clarified in the document.
>>> This concerns how to handle name resolution with respect to
>>> information stored in resource directory
>>> and text from lynn draft about conversion of attribute values to RR
>>> in DNS
>>>
>>> Peter van der Stok
>>>
>>> Rahman, Akbar schreef op 2013-05-21 05:49:
>>>> +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
>>>> _______________________________________________
>>>> core mailing list
>>>> core@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/core
>>> _______________________________________________
>>> core mailing list
>>> core@ietf.org
>>> https://www.ietf.org/mailman/listinfo/core
>>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>