RFC 4648: The Base16, Base32, and Base64 Data Encodings

This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of…

Read RFC 4648 on the RFC Editor

Outgoing relationships (8 related RFCs)

Obsoletes — RFC 3548: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 20: ASCII format for network interchange
Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 4033: DNS Security Introduction and Requirements
Informative reference — RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
Informative reference — RFC 2440: OpenPGP Message Format
Informative reference — RFC 1421: Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
Informative reference — RFC 2938: Identifying Composite Media Features

Incoming relationships (128 related RFCs)

Showing 50 of 128 related RFCs.

Normatively referenced by — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Normatively referenced by — RFC 7950: The YANG 1.1 Data Modeling Language
Normatively referenced by — RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core
Normatively referenced by — RFC 7515: JSON Web Signature (JWS)
Normatively referenced by — RFC 7858: Specification for DNS over Transport Layer Security (TLS)
Normatively referenced by — RFC 8949: Concise Binary Object Representation (CBOR)
Normatively referenced by — RFC 5155: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence
Normatively referenced by — RFC 7517: JSON Web Key (JWK)
Normatively referenced by — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Normatively referenced by — RFC 5958: Asymmetric Key Packages
Normatively referenced by — RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Normatively referenced by — RFC 7030: Enrollment over Secure Transport
Normatively referenced by — RFC 7468: Textual Encodings of PKIX, PKCS, and CMS Structures
Normatively referenced by — RFC 7493: The I-JSON Message Format
Normatively referenced by — RFC 4954: SMTP Service Extension for Authentication
Normatively referenced by — RFC 7469: Public Key Pinning Extension for HTTP
Normatively referenced by — RFC 5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms
Normatively referenced by — RFC 7617: The 'Basic' HTTP Authentication Scheme
Normatively referenced by — RFC 8941: Structured Field Values for HTTP
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 5801: Using Generic Security Service Application Program Interface (GSS-API) Mechanisms in Simple Authentication and Security Layer (SASL): The GS2 Mechanism Family
Normatively referenced by — RFC 6184: RTP Payload Format for H.264 Video
Normatively referenced by — RFC 7022: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 6920: Naming Things with Hashes
Normatively referenced by — RFC 6031: Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type
Normatively referenced by — RFC 6591: Authentication Failure Reporting Using the Abuse Reporting Format
Normatively referenced by — RFC 8489: Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 4870: Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)
Normatively referenced by — RFC 6030: Portable Symmetric Key Container (PSKC)
Normatively referenced by — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Normatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Normatively referenced by — RFC 6940: REsource LOcation And Discovery (RELOAD) Base Protocol
Normatively referenced by — RFC 7129: Authenticated Denial of Existence in the DNS
Normatively referenced by — RFC 7636: Proof Key for Code Exchange by OAuth Public Clients
Normatively referenced by — RFC 7798: RTP Payload Format for High Efficiency Video Coding (HEVC)
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9711: The Entity Attestation Token (EAT)
Normatively referenced by — RFC 4643: Network News Transfer Protocol (NNTP) Extension for Authentication
Normatively referenced by — RFC 5034: The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism
Normatively referenced by — RFC 5804: A Protocol for Remotely Managing Sieve Scripts
Normatively referenced by — RFC 6321: xCal: The XML Format for iCalendar
Normatively referenced by — RFC 6590: Redaction of Potentially Sensitive Data from Mail Abuse Reports
Normatively referenced by — RFC 7143: Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)
Normatively referenced by — RFC 7486: HTTP Origin-Bound Authentication (HOBA)
Normatively referenced by — RFC 8844: Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
Normatively referenced by — RFC 4959: IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response
Normatively referenced by — RFC 6222: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Normatively referenced by — RFC 7635: Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization
Normatively referenced by — RFC 7643: System for Cross-domain Identity Management: Core Schema