[Ohai] RFC 9540 on Discovery of Oblivious Services via Service Binding Records
rfc-editor@rfc-editor.org Thu, 22 February 2024 02:32 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 A5010C151083; Wed, 21 Feb 2024 18:32: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 IlMndaZ-980z; Wed, 21 Feb 2024 18:32:02 -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 035CBC151996; Wed, 21 Feb 2024 18:32:01 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id CBC861BA42E8; Wed, 21 Feb 2024 18:32:01 -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: <20240222023201.CBC861BA42E8@rfcpa.amsl.com>
Date: Wed, 21 Feb 2024 18:32:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohai/Dt7-bDkrz6cXfdh6BvPSa2Fp2lM>
Subject: [Ohai] RFC 9540 on Discovery of Oblivious Services via Service Binding Records
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: Thu, 22 Feb 2024 02:32:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9540
Title: Discovery of Oblivious Services via
Service Binding Records
Author: T. Pauly,
T. Reddy.K
Status: Standards Track
Stream: IETF
Date: February 2024
Mailbox: tpauly@apple.com,
kondtir@gmail.com
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ohai-svcb-config-07.txt
URL: https://www.rfc-editor.org/info/rfc9540
DOI: 10.17487/RFC9540
This document defines a parameter that can be included in Service
Binding (SVCB) and HTTPS DNS resource records to denote that a
service is accessible using Oblivious HTTP, by offering an Oblivious
Gateway Resource through which to access the target. This document
also defines a mechanism for learning the key configuration of the
discovered Oblivious Gateway Resource.
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