rfc9963v1.txt		rfc9963.txt
	skipping to change at line 49 ¶		skipping to change at line 49 ¶
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Revised BSD License text as described in Section 4.e of the		include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described		Trust Legal Provisions and are provided without warranty as described
	in the Revised BSD License.		in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction
	2. Conventions and Definitions		2. Conventions and Definitions
	3. PKCS#1 v1.5 SignatureScheme Types		3. PKCS #1 v1.5 SignatureScheme Types
	4. Security Considerations		4. Security Considerations
	5. IANA Considerations		5. IANA Considerations
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	6.2. Informative References		6.2. Informative References
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	skipping to change at line 111 ¶		skipping to change at line 111 ¶
	unblocks TLS 1.3 deployment.		unblocks TLS 1.3 deployment.
	2. Conventions and Definitions		2. Conventions and Definitions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in
	BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	3. PKCS#1 v1.5 SignatureScheme Types		3. PKCS #1 v1.5 SignatureScheme Types
	The following SignatureScheme values are defined for use with TLS		The following SignatureScheme values are defined for use with TLS
	1.3.		1.3.
	enum {		enum {
	rsa_pkcs1_sha256_legacy(0x0420),		rsa_pkcs1_sha256_legacy(0x0420),
	rsa_pkcs1_sha384_legacy(0x0520),		rsa_pkcs1_sha384_legacy(0x0520),
	rsa_pkcs1_sha512_legacy(0x0620),		rsa_pkcs1_sha512_legacy(0x0620),
	} SignatureScheme;		} SignatureScheme;
	skipping to change at line 143 ¶		skipping to change at line 143 ¶
	Servers that wish to support clients authenticating with legacy		Servers that wish to support clients authenticating with legacy
	RSASSA-PKCS1-v1_5-only keys MAY send these values in the		RSASSA-PKCS1-v1_5-only keys MAY send these values in the
	signature_algorithms extension of the CertificateRequest message and		signature_algorithms extension of the CertificateRequest message and
	accept them in the client CertificateVerify message. Servers MUST		accept them in the client CertificateVerify message. Servers MUST
	NOT accept these code points if not offered in the CertificateRequest		NOT accept these code points if not offered in the CertificateRequest
	message.		message.
	Clients with such legacy keys MAY negotiate the use of these		Clients with such legacy keys MAY negotiate the use of these
	signature algorithms if offered by the server. Clients SHOULD NOT		signature algorithms if offered by the server. Clients SHOULD NOT
	negotiate them with keys that support RSASSA-PSS, though this may not		negotiate the use of these signature algorithms with keys that
	be practical to determine in all applications. For example,		support RSASSA-PSS, though this may not be practical to determine in
	attempting to test a key for support might display a message to the		all applications. For example, attempting to test a key for support
	user or have other side effects.		might result in a message to the user or have other side effects.
	TLS implementations SHOULD disable these code points by default. See		TLS implementations SHOULD disable these code points by default. See
	Section 4.		Section 4.
	4. Security Considerations		4. Security Considerations
	The considerations in Section 1 do not apply to server keys, so these		The considerations in Section 1 do not apply to server keys, so these
	new code points are forbidden for use with server certificates.		new code points are forbidden for use with server certificates.
	RSASSA-PSS continues to be required for TLS 1.3 servers using RSA		RSASSA-PSS continues to be required for TLS 1.3 servers using RSA
	keys. This minimizes the impact to only those cases in which it is		keys. This minimizes the impact to only those cases in which it is
End of changes. 3 change blocks.
	6 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48.