IETF Logo Mail Archive

Re: [core] Tr : New Version Notification for draft-vial-core-mirror-proxy-00.txt

Zach Shelby <zach@sensinode.com> Mon, 05 March 2012 15:27 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 0166521F872F for <core@ietfa.amsl.com>; Mon, 5 Mar 2012 07:27:14 -0800 (PST)
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 xWtvFqRi9gGa for <core@ietfa.amsl.com>; Mon, 5 Mar 2012 07:27:13 -0800 (PST)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id CE3C421F872D for <core@ietf.org>; Mon, 5 Mar 2012 07:27:12 -0800 (PST)
Received: from [172.20.10.4] (81-197-24-150.elisa-mobile.fi [81.197.24.150]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q25FR4Xt016522; Mon, 5 Mar 2012 17:27:09 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <OF46CB06B5.4C0D391B-ONC12579B8.004D5123-C12579B8.004FDB26@schneider-electric.com>
Date: Mon, 05 Mar 2012 17:27:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A066EF6E-A6F2-48D7-BB9C-A18FB14566C9@sensinode.com>
References: <OF46CB06B5.4C0D391B-ONC12579B8.004D5123-C12579B8.004FDB26@schneider-electric.com>
To: matthieu.vial@non.schneider-electric.com
X-Mailer: Apple Mail (2.1084)
Cc: core WG <core@ietf.org>
Subject: Re: [core] Tr : New Version Notification for draft-vial-core-mirror-proxy-00.txt
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: Mon, 05 Mar 2012 15:27:14 -0000

On Mar 5, 2012, at 4:32 PM, matthieu.vial@non.schneider-electric.com wrote:

>> Actually I have already considered including in the RD draft an id= 
> attribute that allows you to associate a unique identifier (e.g. dev-urn) 
> with an end-point. Would be happy to include that in the RD registration 
> interface if people find that useful. 
> 
> I'm worried about the length of the payload if the identifier is repeated 
> for each link.
> 
> <coap://[aaaa::ff:fe00:0001]/mp/0/dev/>;rt="profile:dev";if="core#p";id="
> urn:dev:mac:0024befffe804ff1",

I agree, which is why I wasn't suggesting putting it in the link. Instead, id= would be associated to the end-point and passed to the RD only during the initial registration. So:

POST /rd?h=powernode-005&id=urn:dev:mac:0024befffe804ff1

Now I think you might be referring to the links that an RD returns as a result of a lookup. I agree, it would be inefficient to repeat that for each resource link. I think there should be a way to return a link to the end-point itself, where such end-point specific information can be returned (e.g. id=). This could be done by providing an additional REST interface for looking up end-points rather than resources.

Zach

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297

v2.23.0 | Report a Bug | By Email