Re: [core] Suggestions re: how to implement HEAD semantics within COAP?

Likepeng <likepeng@huawei.com> Sun, 08 May 2011 06:01 UTC

Return-Path: <likepeng@huawei.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 3F393E06B0 for <core@ietfa.amsl.com>; Sat, 7 May 2011 23:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[AWL=1.475, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 odNh1m9ZQJRT for <core@ietfa.amsl.com>; Sat, 7 May 2011 23:00:57 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5BDE0662 for <core@ietf.org>; Sat, 7 May 2011 23:00:57 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKV004674PDUZ@szxga04-in.huawei.com> for core@ietf.org; Sun, 08 May 2011 14:00:49 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKV00E644PDYH@szxga04-in.huawei.com> for core@ietf.org; Sun, 08 May 2011 14:00:49 +0800 (CST)
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 08 May 2011 14:00:31 +0800
Received: from SZXEML506-MBS.china.huawei.com ([169.254.3.27]) by szxeml403-hub.china.huawei.com ([169.254.173.75]) with mapi id 14.01.0270.001; Sun, 08 May 2011 14:00:48 +0800
Date: Sun, 08 May 2011 06:00:47 +0000
From: Likepeng <likepeng@huawei.com>
In-reply-to: <E4DBD8AB11D2E54F89B23D7CD1065D8C01D4D8F8@onzosbs2k3.ONZO.local>
X-Originating-IP: [172.24.2.40]
To: Charles Palmer <charles.palmer@onzo.com>, "paduffy@cisco.com" <paduffy@cisco.com>, Carsten Bormann <cabo@tzi.org>
Message-id: <34966E97BE8AD64EAE9D3D6E4DEE36F22872CF@SZXEML506-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_f4UJJ0g685Y1sTL1ByEJXA)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: [core] Suggestions re: how to implement HEAD semantics within COAP?
Thread-index: AQHMDKE8AsUHravVjkyl8utZN2pH4ZSCcIYk
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <4DC40A9D.3060208@cisco.com> <EED8658B-8287-4AD8-993D-FC77425D0D8B@tzi.org> <4DC419B2.5080306@cisco.com> <C70FDB25-1CCD-4FBE-96D5-939B53DB38E6@tzi.org> <4DC4CA21.2000902@cisco.com> <E4DBD8AB11D2E54F89B23D7CD1065D8C01D4D8F8@onzosbs2k3.ONZO.local>
Cc: core <core@ietf.org>
Subject: Re: [core] Suggestions re: how to implement HEAD semantics within COAP?
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: Sun, 08 May 2011 06:01:10 -0000

> I guess the Size option from draft-li-core-coap-size-option-00 could be extended such that a CoAP GET request including Size=0 is treated as a request to get the size of the resource representation (but not the resource payload) and so could be translated to and from an HTTP HEAD (and could return Content-Length to a CoAP requester).



Good suggestion. I will add this in -01, if there are no other opinions.



Thanks,

Kind Regards

Kepeng

________________________________
发件人: core-bounces@ietf.org [core-bounces@ietf.org] 代表 Charles Palmer [charles.palmer@onzo.com]
发送时间: 2011年5月7日 18:25
到: paduffy@cisco.com; Carsten Bormann
Cc: core
主题: Re: [core] Suggestions re: how to implement HEAD semantics within COAP?



I guess the Size option from draft-li-core-coap-size-option-00 could be extended such that a CoAP GET request including Size=0 is treated as a request to get the size of the resource representation (but not the resource payload) and so could be translated to and from an HTTP HEAD (and could return Content-Length to a CoAP requester).