RFC 9440 on Client-Cert HTTP Header Field

rfc-editor@rfc-editor.org Sat, 22 July 2023 07:09 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C862C14CE2E for <ietf-announce@ietfa.amsl.com>; Sat, 22 Jul 2023 00:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level:
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 C1okEHxoXJSe for <ietf-announce@ietfa.amsl.com>; Sat, 22 Jul 2023 00:09:42 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [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 C08B8C14CF1F for <ietf-announce@ietf.org>; Sat, 22 Jul 2023 00:09:42 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A88A4E7093; Sat, 22 Jul 2023 00:09:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9440 on Client-Cert HTTP Header Field
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: <20230722070942.A88A4E7093@rfcpa.amsl.com>
Date: Sat, 22 Jul 2023 00:09:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GXQmWULq0-sM28WOfA5XjjV0dVQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2023 07:09:46 -0000

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

        
        RFC 9440

        Title:      Client-Cert HTTP Header Field 
        Author:     B. Campbell,
                    M. Bishop
        Status:     Informational
        Stream:     IETF
        Date:       July 2023
        Mailbox:    bcampbell@pingidentity.com,
                    mbishop@evequefou.be
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpbis-client-cert-field-06.txt

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

        DOI:        10.17487/RFC9440

This document describes HTTP extension header fields that allow a TLS
terminating reverse proxy (TTRP) to convey the client certificate
information of a mutually authenticated TLS connection to the origin
server in a common and predictable manner.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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