Visual RFC.
ALL RFCs / RFC 5246
Read the RFC ↗
RFC 5246 / MECHANISMS

Records protect fragments

03

The record layer frames fragments and applies the chosen protection construction.

This guide explains the 2008 publication. Superseded by RFC 8446, RFC 9846.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 5246 · § 6.2.3EXAMPLE
3 / 3
Records protect fragmentsThe record layer frames fragments and applies the chosen protection construction. Current state: Verify.Records protect fragmentshigher-layer fragmentAEADvisible headerciphertext + tagauthenticate before releasingIllustrated AEAD construction; TLS 1.2 also defined older modes.
03
Verify

The receiver checks authentication before releasing the plaintext.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

TLS 1.2 supports different protection constructions; AEAD is a distinct case.

  • TLS 1.2 supports different protection constructions; AEAD is a distinct case.
  • The record header remains visible.
  • A failed integrity check must not release unauthenticated application data.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A TLS 1.2 handshake
  2. Pending and current keys
  3. Records protect fragments
  4. Finished checks the transcript
  5. TLS 1.3 changes the design

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗