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

Zach Shelby <zach@sensinode.com> Fri, 24 May 2013 15:03 UTC

Return-Path: <zach@sensinode.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 36FF921F880F for <core@ietfa.amsl.com>; Fri, 24 May 2013 08:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 CG65WT1xTwzp for <core@ietfa.amsl.com>; Fri, 24 May 2013 08:03:05 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id F33A621F87D1 for <core@ietf.org>; Fri, 24 May 2013 08:03:04 -0700 (PDT)
Received: from [192.168.1.101] (188-67-76-50.bb.dnainternet.fi [188.67.76.50]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id r4OF31U7020731 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 18:03:02 +0300
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <cc182ea3d25a7ffd75760f7ff4d4ef30@xs4all.nl>
Date: Fri, 24 May 2013 18:03:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <15C704CA-839F-41CE-99C8-73DA52A0CBFB@sensinode.com>
References: <CAPRuP3=X0owKUDVbppvcCRu149wL_EUY=s6_wo4tnujnxfBxJQ@mail.gmail.com> <D60519DB022FFA48974A25955FFEC08C0515CDFB@SAM.InterDigital.com> <cc182ea3d25a7ffd75760f7ff4d4ef30@xs4all.nl>
To: consultancy@vanderstok.org
X-Mailer: Apple Mail (2.1503)
Cc: core@ietf.org
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: Fri, 24 May 2013 15:03:09 -0000

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

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com @SensinodeIoT
Mobile: +358 40 7796297
Twitter: @zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net