IETF Logo Mail Archive

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

Andrew Mcgregor <andrewmcgr@google.com> Tue, 21 May 2013 00:24 UTC

Return-Path: <andrewmcgr@google.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 93EAF21F9714 for <core@ietfa.amsl.com>; Mon, 20 May 2013 17:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 qNxeBP+UGCz7 for <core@ietfa.amsl.com>; Mon, 20 May 2013 17:24:15 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id EBDD121F9711 for <core@ietf.org>; Mon, 20 May 2013 17:24:14 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id ox1so18564veb.8 for <core@ietf.org>; Mon, 20 May 2013 17:24:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=UssxD5bAZMh+BF5TsBfPctjr+V5+ceENknFkiX2mqBw=; b=f2/vDp8GR9u/gRY+NLH+gmTg7h9UZi55w1T9MfLaqNc8QFPWMwyks0PyfrEXrwLHgo OP3W5lA92fIxpv/b68lsRjyWOyK5khgpVg74EkhxBecYNGAye70qos+wK1FqsHf2T0fJ nib1O5K5C3t2KYjka7GQf1vmr6szw9yb3iNLnfgBT4w87iD0KJI0Ll82BYJ+QGTO4lmm lKSSnZiehvYgITw7PcOHu/0+JOvYCZQF30aOCBMQBbb7l4m3gDWBZRx4aPMkyf3CZNme +KkyyFv1KfFv655/MaThEcqk955hqypNYVbFwafSDIGU/F64k6cxXRFA2+whOHtVDchn pMTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=UssxD5bAZMh+BF5TsBfPctjr+V5+ceENknFkiX2mqBw=; b=YDHE9ZpebOwMt2eXzelRlUBCdhsyqHOsHcMzDPh/3yMjbeXbKyq78Rjr8Wf2ONpWBF usg6mvHPkj8I3rRag+hlUEszi0h5sszcJB1NuAYap7C0GdxQUs2q+cokel+iPLPRh1oz y4Ufq1eAb6L9EK/M3JLVeLLJaF6TXcvmZ70AtD9JCKjnGrvDQwt4A9Ih/CrzjLsbcPds f8WD5Iq7VM7vOYzxlLuZ/n6XUBz3GxEIjFBh78psleVnZ5EvjTBok9hSnCqZRbITTQMj CiM70BoJAeKxXyCvxlhk3kZVcr02yqF90GfkqJi6R+BvCVvDtr7otXqwZlasrKHcmN8i bZ+Q==
MIME-Version: 1.0
X-Received: by 10.58.133.81 with SMTP id pa17mr34824494veb.37.1369095854316; Mon, 20 May 2013 17:24:14 -0700 (PDT)
Received: by 10.220.238.82 with HTTP; Mon, 20 May 2013 17:24:14 -0700 (PDT)
Date: Tue, 21 May 2013 10:24:14 +1000
Message-ID: <CAPRuP3=Z85CjKzgxmTLzzrLC836Lm_OtOHmevaY3tWkj_019UA@mail.gmail.com>
From: Andrew Mcgregor <andrewmcgr@google.com>
To: core@ietf.org
Content-Type: multipart/alternative; boundary="047d7b6730040f7be804dd2f7829"
X-Gm-Message-State: ALoCoQn3KmggO2sZIWUK9NR7hFKQ8iQCycxxD+GYeIrSeCRzt6YbeaI8C41thZ+XC2FRvUKNA1SJoNglFrYqYDy2BEczXXMScg/q363PYdSOySYNiu74MotT2QrEMpMwvXBB7XVOT64V7VP4fZSuOb+JY2udt5979eXcv47VOcLCyfrqWAVwaExNqJQ+tRy7cY6Jmw4/rhPr
X-Mailman-Approved-At: Mon, 20 May 2013 17:26:15 -0700
Subject: [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: Tue, 21 May 2013 00:24:15 -0000

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 | +61 4 8143 7128

v2.23.0 | Report a Bug | By Email