[Ohai] RFC 9458 on Oblivious HTTP

rfc-editor@rfc-editor.org Sat, 13 January 2024 00:43 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ohai@ietfa.amsl.com
Delivered-To: ohai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A26EC14F61D; Fri, 12 Jan 2024 16:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 Yb5Ot_ctGdPt; Fri, 12 Jan 2024 16:43:01 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 13FD6C14F5F9; Fri, 12 Jan 2024 16:43:01 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D24121A2161C; Fri, 12 Jan 2024 16:43:00 -0800 (PST)
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, ohai@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240113004300.D24121A2161C@rfcpa.amsl.com>
Date: Fri, 12 Jan 2024 16:43:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/iZlxEqrYuS__roEq9nhGJbgszCY>
Subject: [Ohai] RFC 9458 on Oblivious HTTP
X-BeenThere: ohai@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Oblivious HTTP Application Intermediation <ohai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohai>, <mailto:ohai-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohai/>
List-Post: <mailto:ohai@ietf.org>
List-Help: <mailto:ohai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohai>, <mailto:ohai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jan 2024 00:43:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9458

        Title:      Oblivious HTTP 
        Author:     M. Thomson,
                    C. A. Wood
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2024
        Mailbox:    mt@lowentropy.net,
                    caw@heapingbits.net
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ohai-ohttp-10.txt

        URL:        https://www.rfc-editor.org/info/rfc9458

        DOI:        10.17487/RFC9458

This document describes Oblivious HTTP, a protocol for forwarding
encrypted HTTP messages. Oblivious HTTP allows a client to make
multiple requests to an origin server without that server being able
to link those requests to the client or to identify the requests as
having come from the same client, while placing only limited trust in
the nodes used to forward the messages.

This document is a product of the Oblivious HTTP Application Intermediation Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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