The Multibase Data Format
draft-multiformats-multibase-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Juan Benet  , Manu Sporny 
Last updated 2021-02-19 (latest revision 2020-08-18)
Stream (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-multiformats-multibase-02.txt

Abstract

Raw binary data is often encoded using a mechanism that enables the data to be included in human-readable text-based formats. This mechanism is often referred to as "base-encoding the data". Base- encoding is often used when expressing binary data in hyperlinks, cryptographic keys in web pages, or security tokens in application software. There are a variety of base-encodings, such as base32, base58, and base64. It is not always possible to differentiate one base-encoding from another. The purpose of this specification is to provide a mechanism to be able to deterministically identify the base-encoding for a particular string of data.

Authors

Juan Benet (juan@protocol.ai)
Manu Sporny (msporny@digitalbazaar.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)