[art] Revising BCP56: On the use of HTTP as a Substrate

Mark Nottingham <mnot@mnot.net> Tue, 11 July 2017 04:14 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970D712ECC1 for <art@ietfa.amsl.com>; Mon, 10 Jul 2017 21:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=jg612XIG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=n+po/1z1
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 Bjl8Y6EkZfjn for <art@ietfa.amsl.com>; Mon, 10 Jul 2017 21:14:08 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C49DF12EC19 for <art@ietf.org>; Mon, 10 Jul 2017 21:14:08 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2363220616; Tue, 11 Jul 2017 00:14:08 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 11 Jul 2017 00:14:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=UN5HwSToGIjujPD21bDfJPex/zNto5EN02MbWnQpw FY=; b=jg612XIGGfhP86jk9KhgxFzE0XXafU2bxT9x/1243Z3fhKWu5mIRUahGk cJW3gVtIZ4vfVXZtTbzPESv2WoCzgII1k0cWoxzzX39xDgZ/1mEUanKyldFEB1tA tXO3SzN72p1XhqlpyXoOvyQFHbeaWkQES5a9UOQ+tE1jfc3kOwijy3Ray46M3Qpp 8gQr/eXEoVLN3fIpQez0rEBpN8qRcExNAI1o0XjJt+ntW9e8j1uNJUCy0Fiju5X5 gCN3Qyw9NnayKAbGQPw+ZgyPnkWJu2pyIUYDJWH30q+FR8Rm1NIF7nfAY8VzyrE0 Aui19iuHeKw7jDbfM7dDEGUJEFCYA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=UN5HwSToGIjujPD21b DfJPex/zNto5EN02MbWnQpwFY=; b=n+po/1z1XtzDdx+/7extOk8QCru5dh+JtS ZYttnKap4XkL274FahIeV5k+Yx/CI/foYzbQN2DEgVzdhYLn6890xvzQQGsmsZZj ll1RStBBxC/Q+FkUzfpOFPI17CLnFZuTSS+aPMhiol4hB5PDM3FjleSY+Ek/n5jn +0yoY4rBa+ypf86+bcuQ/beRhu5P9ZKsq3bkCX2gCFEzDY9GKqDiVwH5XB2PI4/L Wz775CXZTlEYHJY3ks5H2kPiutNLWNZAbVFq+ErQoUH84TWss0yUzYkJSBSoFrfk 0Flml3VW72UTMwdh0xUuqhm2VjXFqfvqMNg/pYvZYDBB0xQUxBsw==
X-ME-Sender: <xms:kFBkWdpLOsRLEltl0zwFP--PRw14PVW_Pb7T3TrjH2Q_n8OWKHDAJA>
X-Sasl-enc: EcblV7QHmkbgWHj13vnsJ3Yc7MJGJgLuj6djs1Bak9dR 1499746447
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id F1AF37E809; Tue, 11 Jul 2017 00:14:06 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <83273F06-63D3-41C1-BC3C-9ECE401C2279@mnot.net>
Date: Tue, 11 Jul 2017 14:14:04 +1000
Cc: Patrick McManus <mcmanus@ducksong.com>, Alexey Melnikov <alexey.melnikov@isode.com>
To: art@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Y_hKHfQnIP-TwIji8DgRFrLi3Hs>
Subject: [art] Revising BCP56: On the use of HTTP as a Substrate
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jul 2017 04:14:11 -0000

A number of folks have recently noted that BCP56 addresses the problems of using HTTP for protocols in the early 2000's, but we've moved on considerably since then. 

Given the number of IETF protocols being build upon HTTP these days, it seems timely to reconsider it. I've been working on a candidate for replacing it for a little while; see:
  https://tools.ietf.org/html/draft-nottingham-bcp56bis
  https://mnot.github.io/I-D/bcp56bis/

I have a small-ish slot in the HTTP WG session on Wednesday to discuss this. 

Cheers,

--
Mark Nottingham   https://www.mnot.net/