Re: [core] clarify resource discovery for 6LoWPAN
Zach Shelby <zach@sensinode.com> Tue, 28 September 2010 09:12 UTC
Return-Path: <zach@sensinode.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 129ED3A6D8A for <core@core3.amsl.com>; Tue, 28 Sep 2010 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level:
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0MT5B3Y9kXnW for <core@core3.amsl.com>; Tue, 28 Sep 2010 02:12:02 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 8D7403A6D90 for <core@ietf.org>; Tue, 28 Sep 2010 02:10:48 -0700 (PDT)
Received: from [62.145.172.52] ([62.145.172.52]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id o8S9At16016773 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Sep 2010 12:10:56 +0300
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; boundary="Apple-Mail-203-267695954"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <31312889.121285664567378.JavaMail.esguti@esguti-sssup>
Date: Tue, 28 Sep 2010 12:10:57 +0300
Message-Id: <E2FEA4FB-C887-4A90-899B-229DFEB21925@sensinode.com>
References: <31312889.121285664567378.JavaMail.esguti@esguti-sssup>
To: Esteban Damian Gutierrez Mlot <e.gutierrezmlot@sssup.it>
X-Mailer: Apple Mail (2.1081)
Cc: core@ietf.org
Subject: Re: [core] clarify resource discovery for 6LoWPAN
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Sep 2010 09:13:04 -0000
Estaban, Please see the draft just posted (draft-shelby-core-coap-link-format). This draft does make it possible to discover the list of resources that a CoAP server provides by doing a GET on /.well-known/core. This of course assumes that you are using CoAP and know that a CoAP server exists in your network - if you don't then some sort of service discovery might be needed first (SLP, DNS-SD etc.). The combination of these depends a lot on your application. Regards, Zach On Sep 28, 2010, at 12:02 PM, Esteban Damian Gutierrez Mlot wrote: > In order to apply a Service Oriented Architecture and made resources available for users, I would implement a discovery mechanism. I think this is a point is not clear for 6LoWPAN. Should I use SSLP (draft-daniel-6lowpan-sslp-02.txt) or I should use CoAP (draft-ietf-core-coap-01)? > > Could somebody clarify this point or give some advices? > > Regards, > Esteban > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core -- Zach Shelby, Chief Nerd, Sensinode Ltd. http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297
- [core] clarify resource discovery for 6LoWPAN Esteban Damian Gutierrez Mlot
- Re: [core] clarify resource discovery for 6LoWPAN Zach Shelby