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

+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
>