[rfc-dist] BCP 56, RFC 9205 on Building Protocols with HTTP
rfc-editor@rfc-editor.org Wed, 08 June 2022 17:44 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECF5C2D8F37; Wed, 8 Jun 2022 10:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654710281; bh=bMII7o2eYV8+EIitf5QWVGc3cv93wJzsn/Sq1j58bL8=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=gRgCErxFzYzYkBDXfWpZrcL8gDBHu/3iEXcSpqN3b05NJtYey43k0MLQN8i/B7zec D1mOKsU3d/hucwNuxDudWJRPYDO1dANTe0UPJQ2l2hi5bBhRA7/zpUH7iqZRcD5Wm3 YWPMnonVwE90gMn+B+3ZKhqI1f24Sy8vlPf2wAcg=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Wed Jun 8 10:44:41 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6A8C06D83A; Wed, 8 Jun 2022 10:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654710280; bh=bMII7o2eYV8+EIitf5QWVGc3cv93wJzsn/Sq1j58bL8=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=GHK1gY/cVcY200ShDBCscMCxq+ANwJdQ4d9+ZS8xA81rKBufwT3ZYe1LaDul19ayC 56y18A8rQ1A9aQG0QI6YYIXr6cVHDGobpJZuG/kd7GrTwf9vJBnZnjlr5woDgRl92K vGntzFEzYkr1tpwHnU8Wkyrtzcz5TsdWCPcOnGGg=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18AA5C14CF1F; Wed, 8 Jun 2022 10:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUcbj9jx_EWR; Wed, 8 Jun 2022 10:44:31 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569B5C157B50; Wed, 8 Jun 2022 10:44:10 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 12E55CF503; Wed, 8 Jun 2022 10:44:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Message-Id: <20220608174410.12E55CF503@rfcpa.amsl.com>
Date: Wed, 08 Jun 2022 10:44:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/fPGIB6GfBbEO9DijHwkfM0ydpAw>
Subject: [rfc-dist] BCP 56, RFC 9205 on Building Protocols with HTTP
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
BCP 56
RFC 9205
Title: Building Protocols with HTTP
Author: M. Nottingham
Status: Best Current Practice
Stream: IETF
Date: June 2022
Mailbox: mnot@mnot.net
Pages: 27
Obsoletes: RFC 3205
See Also: BCP 56
I-D Tag: draft-ietf-httpbis-bcp56bis-15.txt
URL: https://www.rfc-editor.org/info/rfc9205
DOI: 10.17487/RFC9205
Applications often use HTTP as a substrate to create HTTP-based APIs.
This document specifies best practices for writing specifications
that use HTTP to define new application protocols. It is written
primarily to guide IETF efforts to define application protocols using
HTTP for deployment on the Internet but might be applicable in other
situations.
This document obsoletes RFC 3205.
This document is a product of the HTTP Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org