[core] draft-shelby-core-resource-directory-04: unclear 'rt' parameter in Update

"Dijk, Esko" <esko.dijk@philips.com> Thu, 30 August 2012 10:28 UTC

Return-Path: <esko.dijk@philips.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 7366921F84D6 for <core@ietfa.amsl.com>; Thu, 30 Aug 2012 03:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.663
X-Spam-Level:
X-Spam-Status: No, score=-3.663 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q89TOY+oAPeZ for <core@ietfa.amsl.com>; Thu, 30 Aug 2012 03:28:32 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by ietfa.amsl.com (Postfix) with ESMTP id 19CCD21F84C8 for <core@ietf.org>; Thu, 30 Aug 2012 03:28:31 -0700 (PDT)
Received: from mail120-am1-R.bigfish.com (10.3.201.249) by AM1EHSOBE010.bigfish.com (10.3.204.30) with Microsoft SMTP Server id 14.1.225.23; Thu, 30 Aug 2012 10:28:30 +0000
Received: from mail120-am1 (localhost [127.0.0.1]) by mail120-am1-R.bigfish.com (Postfix) with ESMTP id AA8521E00D4; Thu, 30 Aug 2012 10:28:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: VPS-13(zz217bL15d6O9251Jc85fhzz1202hzzz2dh2a8h668h839hd25hf0ah107ah1155h)
Received: from mail120-am1 (localhost.localdomain [127.0.0.1]) by mail120-am1 (MessageSwitch) id 1346322508961802_5499; Thu, 30 Aug 2012 10:28:28 +0000 (UTC)
Received: from AM1EHSMHS012.bigfish.com (unknown [10.3.201.246]) by mail120-am1.bigfish.com (Postfix) with ESMTP id E903A1C0047; Thu, 30 Aug 2012 10:28:28 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by AM1EHSMHS012.bigfish.com (10.3.207.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 30 Aug 2012 10:28:26 +0000
Received: from 011-DB3MMR1-013.MGDPHG.emi.philips.com (10.128.28.97) by 011-DB3MMR1-005.MGDPHG.emi.philips.com (10.128.28.55) with Microsoft SMTP Server (TLS) id 14.2.309.3; Thu, 30 Aug 2012 11:28:25 +0100
Received: from 011-DB3MPN2-081.MGDPHG.emi.philips.com ([169.254.1.216]) by 011-DB3MMR1-013.MGDPHG.emi.philips.com ([10.128.28.97]) with mapi id 14.02.0309.003; Thu, 30 Aug 2012 11:28:25 +0100
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "core@ietf.org" <core@ietf.org>, Zach Shelby <zach@sensinode.com>
Thread-Topic: draft-shelby-core-resource-directory-04: unclear 'rt' parameter in Update
Thread-Index: Ac2Gmi9tY1ioNDD2T6iNoxoWh8Qu2Q==
Date: Thu, 30 Aug 2012 10:28:24 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618AE2066@011-DB3MPN2-081.MGDPHG.emi.philips.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.101]
Content-Type: multipart/alternative; boundary="_000_031DD135F9160444ABBE3B0C36CED618AE2066011DB3MPN2081MGDP_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: [core] draft-shelby-core-resource-directory-04: unclear 'rt' parameter in Update
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: Thu, 30 Aug 2012 10:28:33 -0000

Hello Zach, all,

in section 5.3 (Update) the 'rt' parameter can be specified when doing a PUT update of registration to Resource Directory. To me it's not clear what this parameter would do. The resource types of each resource that is updated, would be already included in the payload as "rt=....." link-format parameters. I assume it should be removed from the allowed query parameters in section 5.3?

regards,
Esko

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.