Re: [core] Filtering in draft-shelby-core-link-format

Zach Shelby <zach@sensinode.com> Wed, 29 September 2010 16:15 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 344AB3A6D43 for <core@core3.amsl.com>; Wed, 29 Sep 2010 09:15:01 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id igXq8rBZ7Dz7 for <core@core3.amsl.com>; Wed, 29 Sep 2010 09:14:59 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by core3.amsl.com (Postfix) with ESMTP id 8C5ED3A6DF1 for <core@ietf.org>; Wed, 29 Sep 2010 09:14:57 -0700 (PDT)
Received: from [192.168.0.82] (82-128-196-163.bb.dnainternet.fi [82.128.196.163]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.4/8.13.4) with ESMTP id o8TGFY2X024467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 Sep 2010 19:15:34 +0300
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/signed; boundary="Apple-Mail-336-379575380"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <4F4FC690-504D-483F-BACE-EE9BABA456D6@cisco.com>
Date: Wed, 29 Sep 2010 19:15:36 +0300
Message-Id: <118E6191-0FA0-4D2D-A003-4CA2AD843C76@sensinode.com>
References: <4F4FC690-504D-483F-BACE-EE9BABA456D6@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: core@ietf.org
Subject: Re: [core] Filtering in draft-shelby-core-link-format
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: Wed, 29 Sep 2010 16:15:01 -0000

Thanks Cullen,

These all sound reasonable to me, I will make a ticket for link-format-02 if there are no objections.

Zach

On Sep 29, 2010, at 5:43 PM, Cullen Jennings wrote:

> 
> It seems like you should clear up the behavior of devices that do not support filtering receives a request with a filter query. For example what happens when a device that does not do filtering gets 
> 
> GET /.well-known/core?n=LightLux
> 
> I think the answer should be it ignores it and returns exactly the same things as if it had got 
> 
> GET /.well-known/core
> 
> Should also deal with what happens with a query with "*" when the device does not support it. This seems a bit harder to specify - I'd almost be tempted to say supporting * is required if you do filtering
> 
> 
> I'm a little concerned with the 
>  " If no Content-type code attribute is present then text/
>   plain is assumed. "
> 
> I think it might be better to say that nothing about the type can be assumed if the attribute is not present. 
> 
> 
> 
> Cullen <in my individual contributor roll>
> 
> 

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