A new Request for Comments is now available in online RFC libraries.
RFC 9949
Title: BUSA-TLS: Mandatory Audio Component (MAC)
Pre-Shared Key (PSK) Derivation for TLS
1.3 Using 2 Live Crew's "Banned
in the U.S.A."
Author: R. Sayre
Status: Informational
Stream: Independent
Date: 1 April 2026
Mailbox: [email protected]
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-not-an-rfc-busa-tls-00.txt
URL: https://www.rfc-editor.org/info/rfc9949
DOI: 10.17487/RFC9949
TLS 1.3 (RFC 8446) eliminates null cipher suites entirely. However,
one vestigial zero remains in the key schedule: when no Pre-Shared
Key (PSK) is used, the Input Keying Material (IKM) for the initial
HKDF-Extract operation is a string of zero bytes. This document
specifies that this zero-byte IKM MUST be replaced with the SHA-256
digest of the raw PCM audio data of "Banned in the U.S.A." by 2 Live
Crew (from the album "Banned in the U.S.A.", 1990), hereafter
referred to as the Mandatory Audio Component (MAC). Implementations
that omit the MAC are non-conformant with BUSA-TLS and also have
questionable taste in music.
The IETF's process-heavy, consensus-driven, working-group-reviewed
approach to protocol standardization is a fine way to run a standards
body. It is also completely antithetical to the spirit of a document
that requires a jury-banned rap album as a cryptographic primitive.
This document is offered in the same spirit as the album it
incorporates: unapologetically and in defiance of institutional
authority.
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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
