| RFC 0 | TLS Flag - Request mTLS | October 2023 |
| Hoyland | Expires 25 April 2024 | [Page] |
Normally in TLS there is no way for the client to signal to the server that it has been configured with a certificate suitable for mTLS. This document defines a TLS Flag [I-D.ietf-tls-tlsflags]¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://jhoyla.github.io/draft-jhoyla-req-mtls-flag/draft-jhoyla-req-mtls-flag.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-jhoyla-req-mtls-flag/.¶
Source for this draft and an issue tracker can be found at https://github.com/jhoyla/draft-jhoyla-req-mtls-flag.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 3 April 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document specifies a TLS Flag that indicates to the server that the client supports mTLS. Sometimes a server does not want to negotiate mTLS with every client, but might wish to authenticate a subset of them. In TLS 1.3 this may be done with post-handshake auth, however this adds an extra round-trip, and requires negotiation at the application layer. A client sending the request mTLS flag in the ClientHello allows the server to request authentication during the initial handshake only when it receives a hint the client supports it.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
A server receiving this flag MAY send a CertificateRequest message.¶
This flag should have no effect on the security of TLS, as the server may always send a CertificateRequest message during the handshake. This flag merely provides a hint that the client will be able to fulfil the request. If the client sets this flag but then fails to provide a certificate the server MAY terminate the connection with a bad_certificate error.¶
This document requests IANA to add an entry to the TLS Flags registry in the TLS namespace with the following values:¶
TODO acknowledge.¶