Visual RFC.
ALL RFCs / RFC 9051
Read the RFC ↗
RFC 9051 / MECHANISM GUIDE

UIDs versus sequence numbers

02

Sequence numbers track current positions; UIDs support persistent synchronization.

Related RFCs and changes

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

RFC 9051 · § 2.3.1EXAMPLE
3 / 3
UIDs versus sequence numbersSequence numbers track current positions; UIDs support persistent synchronization.UIDs versus sequence numberssequencestable UID11052110UIDVALIDITY + UID preserve message identity
03
Keep UID identity

UIDs for the surviving messages remain associated with their original identities.

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

A UID is a nonzero 32-bit value that increases within a mailbox.

  • A UID is a nonzero 32-bit value that increases within a mailbox.
  • UIDVALIDITY is needed to interpret persisted UID state.
  • Sequence numbers can change when messages are expunged.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Session and mailbox states
  2. UIDs versus sequence numbers
  3. Selective FETCH and SEARCH
  4. Flags and deletion
  5. Unsolicited updates and resync

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 ↗