RFC 9532 on HTTP Proxy-Status Parameter for Next-Hop Aliases
rfc-editor@rfc-editor.org Wed, 31 January 2024 22:02 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=ietf.org@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEBCDC14F68C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jan 2024 14:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.757
X-Spam-Level:
X-Spam-Status: No, score=-7.757 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=w3.org
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 juzL9cUobYnS for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jan 2024 14:01:57 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2561BC14F747 for <httpbisa-archive-bis2Juki@ietf.org>; Wed, 31 Jan 2024 14:00:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Subject:Date:Message-Id:Content-type:Cc:From:To:Reply-To:In-Reply-To: References:MIME-Version; bh=9XjddTNilyY+jWcX6WHR3a5rxbAhvTl3jYr1QyTHMCk=; b=o 9Pv2PSU2RXuiZ/uyhzSiET1vozt5HP4SMdmDmShpEe3CkGvof00gx6hY7HNPYIV8lcfU89/1tOzud X2lPAu3MgmIzpiepLmqfPCGwexhDrD1VtCZWigxayHDzKKx7UNHGY0P5VJvp5d9lBiBQ20X1wDsSC qchQyVKXr3AGf3AvOk7B8zRaSd7ngBpG7o9mXLU+UN9CX62VbHNu3R/VvB6kJcmAmcOHkSOjKIosN VARmd91HLf9Zyc248FHf9LxKtYKHH72Ho5TrGN+ixXVnDmKu+0dP6OlSJEaqVIO/fGnmKYhgCV9xP PPJJ9OJ0PcPSjjhWNMqurH0klqznoooSA==;
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1rVIba-0072yg-C8 for ietf-http-wg-dist@listhub.w3.org; Wed, 31 Jan 2024 21:58:50 +0000
Resent-Date: Wed, 31 Jan 2024 21:58:50 +0000
Resent-Message-Id: <E1rVIba-0072yg-C8@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1rVIbY-0072xa-10 for ietf-http-wg@listhub.w3.org; Wed, 31 Jan 2024 21:58:48 +0000
Received: from rfcpa.amsl.com ([50.223.129.200]) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1rVIbS-007GZd-0D for ietf-http-wg@w3.org; Wed, 31 Jan 2024 21:58:47 +0000
Received: by rfcpa.amsl.com (Postfix, from userid 499) id AFFEFE7C63; Wed, 31 Jan 2024 13:58:37 -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, ietf-http-wg@w3.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240131215837.AFFEFE7C63@rfcpa.amsl.com>
Date: Wed, 31 Jan 2024 13:58:37 -0800
Received-SPF: pass client-ip=50.223.129.200; envelope-from=wwwrun@rfcpa.amsl.com; helo=rfcpa.amsl.com
X-W3C-Hub-Spam-Status: No, score=-5.4
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1rVIbS-007GZd-0D e8541181abafefdb7a28f19d2de50843
X-Original-To: ietf-http-wg@w3.org
Subject: RFC 9532 on HTTP Proxy-Status Parameter for Next-Hop Aliases
Archived-At: <https://www.w3.org/mid/20240131215837.AFFEFE7C63@rfcpa.amsl.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51754
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 9532
Title: HTTP Proxy-Status Parameter for Next-Hop Aliases
Author: T. Pauly
Status: Standards Track
Stream: IETF
Date: January 2024
Mailbox: tpauly@apple.com
Pages: 7
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-alias-proxy-status-07.txt
URL: https://www.rfc-editor.org/info/rfc9532
DOI: 10.17487/RFC9532
This document defines the HTTP Proxy-Status Parameter. This
parameter carries the list of aliases and canonical names an
intermediary received during DNS resolution as part of establishing a
connection to the next hop.
This document is a product of the HTTP 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