[core] WG last-call (WGLC) of draft-ietf-core-http-mapping-07

Carsten Bormann <cabo@tzi.org> Tue, 15 September 2015 15:21 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0311A00BC for <core@ietfa.amsl.com>; Tue, 15 Sep 2015 08:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6RbrRN9GpMs for <core@ietfa.amsl.com>; Tue, 15 Sep 2015 08:21:02 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 680021A00C1 for <core@ietf.org>; Tue, 15 Sep 2015 08:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t8FFKqgR027181 for <core@ietf.org>; Tue, 15 Sep 2015 17:20:52 +0200 (CEST)
Received: from alma.local (p5DCCDB06.dip0.t-ipconnect.de [93.204.219.6]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3nFpD41fmtz20cB; Tue, 15 Sep 2015 17:20:52 +0200 (CEST)
Message-ID: <55F83752.3090609@tzi.org>
Date: Tue, 15 Sep 2015 17:20:50 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.4 (Macintosh/20150825)
MIME-Version: 1.0
To: "core@ietf.org WG" <core@ietf.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/cdzn9GwMGrCOZAxPlbzxXkuSj2A>
Subject: [core] WG last-call (WGLC) of draft-ietf-core-http-mapping-07
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Sep 2015 15:21:07 -0000

In Prague, we said we were going to WGLC the HTTP mapping draft after
close of the vacation period, which is now behind us.  All outstanding
tickets are closed, and there was enough time to review the current
draft.  Three people raised their hands when we asked who would submit
reviews (Michael K., Klaus, Darshak), but of course additional reviews
beyond that are also very useful.

So this starts a working group last call for
draft-ietf-core-http-mapping for submission as an informational RFC,
ending on

  24:00 PDT on Tuesday, September 29, 2015.

The draft is located at:
https://tools.ietf.org/html/draft-ietf-core-http-mapping-07

Please start a new email thread for each major issue that will need
discussion and make sure the subject line includes the draft name and
some sort of name for the issue. For minor issues such as typos and
things that are not likely to lead to much discussion, it is probably
easier to group them all in to one email but again, please make sure
the subject line includes the draft name. If you read the draft and
think it looks fine, please send a one line email to the list or to
the chairs letting us know that so we can get a feel of how broad the
review has been.

In the unlikely event that you are aware of any patent claims that
might apply to systems that implement the suggestions in this draft,
please review BCP 78 and BCP 79 and make any appropriate IPR
declaration. If you are not sure whether you need to make a
declaration or not, please talk to the chairs and we will help get you
in touch with people that can provide appropriate advice.

Grüße, Carsten