IETF Logo Mail Archive

Re: [core] draft-castellani-core-http-mapping: call for adoption

Bert Greevenbosch <Bert.Greevenbosch@huawei.com> Wed, 22 May 2013 06:15 UTC

Return-Path: <Bert.Greevenbosch@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 EA5CA21F919D for <core@ietfa.amsl.com>; Tue, 21 May 2013 23:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.363
X-Spam-Level:
X-Spam-Status: No, score=-3.363 tagged_above=-999 required=5 tests=[AWL=-0.968, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jOFB4sHKpwgY for <core@ietfa.amsl.com>; Tue, 21 May 2013 23:15:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9DE21F8EA6 for <core@ietf.org>; Tue, 21 May 2013 23:15:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARP55537; Wed, 22 May 2013 06:15:04 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 22 May 2013 07:14:49 +0100
Received: from SZXEML449-HUB.china.huawei.com (10.82.67.192) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 22 May 2013 14:14:58 +0800
Received: from szxeml558-mbx.china.huawei.com ([169.254.7.152]) by szxeml449-hub.china.huawei.com ([10.82.67.192]) with mapi id 14.01.0323.007; Wed, 22 May 2013 14:14:53 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] draft-castellani-core-http-mapping: call for adoption
Thread-Index: AQHOVbnYaxOZdX4MH0Sk8fscpJ3e2pkOeyyAgAI+tAA=
Date: Wed, 22 May 2013 06:14:52 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB63D762BEF@szxeml558-mbx.china.huawei.com>
References: <CAPRuP3=Z85CjKzgxmTLzzrLC836Lm_OtOHmevaY3tWkj_019UA@mail.gmail.com> <D60519DB022FFA48974A25955FFEC08C0515CDFE@SAM.InterDigital.com>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C0515CDFE@SAM.InterDigital.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.162.63]
Content-Type: multipart/alternative; boundary="_000_46A1DF3F04371240B504290A071B4DB63D762BEFszxeml558mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [core] draft-castellani-core-http-mapping: call for adoption
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: Wed, 22 May 2013 06:15:12 -0000

+1

Bert

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Rahman, Akbar
Sent: 2013年5月21日 11:51
To: Andrew Mcgregor; core@ietf.org
Subject: Re: [core] draft-castellani-core-http-mapping: call for adoption

+1

Akbar

From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Andrew Mcgregor
Sent: Monday, May 20, 2013 8:24 PM
To: core@ietf.org
Subject: [core] draft-castellani-core-http-mapping: call for adoption

Consensus of the room in Orlando was to adopt draft-castellani-core-http-mapping as a working group document.  This email is a call for confirmation of that consensus.  Please respond if you support the adoption of this document.

The charter says "The WG will define a mapping from CoAP to
an HTTP REST API; this mapping will not depend on a specific
application."  We have the normative parts covered in core-coap, but
additional elucidation for implementers seems worthwhile.

* Sep 2013 Submission to IESG of "Best Practices for HTTP-CoAP Mapping
  Implementation" for Informational

(We can discuss if a non-BCP should have "Best Practices" in the
title, but the objective is to provide examples of good usage for
implementers, not to give strong recommendations.)

--
Andrew McGregor | SRE | andrewmcgr@google.com<mailto:andrewmcgr@google.com> | +61 4 8143 7128

v2.23.0 | Report a Bug | By Email