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

Cullen Jennings <fluffy@cisco.com> Wed, 29 September 2010 14:43 UTC

Return-Path: <fluffy@cisco.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 E8D2B3A6CF1 for <core@core3.amsl.com>; Wed, 29 Sep 2010 07:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.504
X-Spam-Level:
X-Spam-Status: No, score=-110.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 6hW8pSYyApYA for <core@core3.amsl.com>; Wed, 29 Sep 2010 07:43:14 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 55F0F3A6CEB for <core@ietf.org>; Wed, 29 Sep 2010 07:43:14 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAI7tokyrR7Ht/2dsb2JhbACiHnGqMZxphUQEhFCFaoJ/
X-IronPort-AV: E=Sophos;i="4.57,253,1283731200"; d="scan'208";a="596571420"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 29 Sep 2010 14:43:58 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o8TEhvpt015613; Wed, 29 Sep 2010 14:43:57 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Sep 2010 08:43:57 -0600
Message-Id: <4F4FC690-504D-483F-BACE-EE9BABA456D6@cisco.com>
To: core@ietf.org, Zach Shelby <zach@sensinode.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [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 14:43:16 -0000

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>