IETF Logo Mail Archive

Re: [core] #117: Block Response Code Mapping

Likepeng <likepeng@huawei.com> Thu, 10 March 2011 01:15 UTC

Return-Path: <likepeng@huawei.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 4842B3A6AFE for <core@core3.amsl.com>; Wed, 9 Mar 2011 17:15:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level:
X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[AWL=2.491, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.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 Arl4XHiuB1gA for <core@core3.amsl.com>; Wed, 9 Mar 2011 17:15:08 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id A93953A6937 for <core@ietf.org>; Wed, 9 Mar 2011 17:15:08 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHT009GBI73BN@szxga03-in.huawei.com> for core@ietf.org; Thu, 10 Mar 2011 09:16:15 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHT00DCOI72YA@szxga03-in.huawei.com> for core@ietf.org; Thu, 10 Mar 2011 09:16:15 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 10 Mar 2011 09:14:27 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.92]) by SZXEML402-HUB.china.huawei.com ([10.82.67.32]) with mapi id 14.01.0270.001; Thu, 10 Mar 2011 09:16:14 +0800
Date: Thu, 10 Mar 2011 01:16:14 +0000
From: Likepeng <likepeng@huawei.com>
In-reply-to: <067.1f7d1667341a104d73de0b45e2720a0a@trac.tools.ietf.org>
X-Originating-IP: [10.70.109.110]
To: core issue tracker <trac+core@zinfandel.tools.ietf.org>, "cabo@tzi.org" <cabo@tzi.org>
Message-id: <34966E97BE8AD64EAE9D3D6E4DEE36F2259315@szxeml506-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [core] #117: Block Response Code Mapping
Thread-index: AQHL0/oTwsZT09vFYE6n50oNPfsi1pQk/doAgADQKtA=
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <058.4d72533879cfdcaa5a84e100bed80074@trac.tools.ietf.org> <067.1f7d1667341a104d73de0b45e2720a0a@trac.tools.ietf.org>
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] #117: Block Response Code Mapping
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: Thu, 10 Mar 2011 01:15:11 -0000

My original proposal is to map 4.08 "Request Entity Incomplete" into a HTTP response code, like what we did in CoAP-04, for example, CoAP 4.13 "Request Entity too Large" is mapped to HTTP 413 " Request Entity too Large ".

But I checked the HTTP response code, 408 is " Request Timeout ". It is totally different from the meaning here. Maybe we should choose another response code other than 4.08, and add one sentence to say, there is no mapped response code in HTTP? 

I don't think section 3.3 in draft-hartke-core-coap-http-00.txt is relevant to my comment.

Thanks,
Kepeng 
-----邮件原件-----
发件人: core-bounces@ietf.org [mailto:core-bounces@ietf.org] 代表 core issue tracker
发送时间: 2011年3月10日 4:10
收件人: cabo@tzi.org
抄送: core@ietf.org
主题: Re: [core] #117: Block Response Code Mapping

#117: Block Response Code Mapping

Changes (by cabo@…):

  * owner:  => cabo@…
  * status:  new => assigned


Comment:

 There is some text in section 3.3 of draft-hartke-core-coap-http-00.txt --
 do we need anything beyond that?

-- 
---------------------------------+------------------------------------------
 Reporter:  likepeng@…           |       Owner:  cabo@…      
     Type:  protocol defect      |      Status:  assigned    
 Priority:  minor                |   Milestone:              
Component:  block                |     Version:              
 Severity:  Active WG Document   |    Keywords:              
---------------------------------+------------------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/core/trac/ticket/117#comment:1>
core <http://tools.ietf.org/core/>

_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email