[core] RD Update in CoRE Resource Directory

Alessandro Ludovici <alessandro.ludovici@entel.upc.edu> Tue, 13 November 2012 11:10 UTC

Return-Path: <alessandro.ludovici@entel.upc.edu>
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 5705321F85EB for <core@ietfa.amsl.com>; Tue, 13 Nov 2012 03:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 pHAohyVPWHnB for <core@ietfa.amsl.com>; Tue, 13 Nov 2012 03:10:57 -0800 (PST)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF0521F85FC for <core@ietf.org>; Tue, 13 Nov 2012 03:10:55 -0800 (PST)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.1/8.13.1) with ESMTP id qADBAppY029697 for <core@ietf.org>; Tue, 13 Nov 2012 12:10:51 +0100
Received: from webmail.entel.upc.edu (wireless.upc.es [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 9B3392CBD0F for <core@ietf.org>; Tue, 13 Nov 2012 12:10:46 +0100 (CET)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_85ee6cd6367a67ca8d3c439a3568b3d0"
Date: Tue, 13 Nov 2012 12:10:46 +0100
From: Alessandro Ludovici <alessandro.ludovici@entel.upc.edu>
To: core@ietf.org
Message-ID: <8980058527dc9594b0e3fd194b4359d5@webmail.entel.upc.edu>
X-Sender: alessandro.ludovici@entel.upc.edu
User-Agent: RoundCube Webmail/0.5.1
X-Mail-Scanned: Criba 2.0 + Clamd
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (violet.upc.es [147.83.2.51]); Tue, 13 Nov 2012 12:10:52 +0100 (CET)
Subject: [core] RD Update in CoRE Resource Directory
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: Tue, 13 Nov 2012 11:10:58 -0000

  

Dear List, 

The actual version of the draft "CoRE Resource
Directory" (draft-shelby-core-resource-directory-04) allows updating a
resource in the RD using either POST or PUT methods. According to the
registration section (5.2), the POST method has the effect of creating
or updating a resource in the RD. Section 5.3 also defines how update a
resource using the PUT method. 

I find a bit confusing that both
methods may be used to update the RD. Wouldn't be better that only the
PUT method can update the RD? 

Regards, 

--  

Alessandro
Ludovici
Wireless Network Group(WNG), 
Department of Telematic
Engineering, 
Universitat Politècnica de Catalunya, 
C/Jordi Girona 1-3,
Mòdul C3, 08034 Barcelona, Spain; 
E-Mail:
alessandro.ludovici@entel.upc.edu 
Tel.: +34-93-401-70-41; Fax:
+34-93-401-10-58