Home › Entities › request_for_comments › RFC 3548: The Base16, Base32, and Base64 Data Encodings

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

request for comments publication
Place request_for_comments Q47463861
Press Enter · cited answer in seconds

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

Summary

RFC 3548: The Base16, Base32, and Base64 Data Encodings is a Request for Comments[1].

Key Facts

  • RFC 3548: The Base16, Base32, and Base64 Data Encodings authored The Base16, Base32, and Base64 Data Encodings — author (P50): Simon Josefsson[2].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's instance of is recorded as The Base16, Base32, and Base64 Data Encodings — instance of (P31): Request for Comments[3].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's publisher is recorded as The Base16, Base32, and Base64 Data Encodings — publisher (P123): Internet Engineering Task Force[4].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's DOI is recorded as 10.17487/RFC3548[5].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's language of work or name is recorded as The Base16, Base32, and Base64 Data Encodings — language of work or name (P407): English[6].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's publication date is recorded as +2003-07-01T00:00:00Z[7].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's RfC ID is recorded as 3548[8].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's main subject is recorded as The Base16, Base32, and Base64 Data Encodings — main subject (P921): Base16[9].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's main subject is recorded as The Base16, Base32, and Base64 Data Encodings — main subject (P921): Base32[10].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's main subject is recorded as The Base16, Base32, and Base64 Data Encodings — main subject (P921): Q726780[11].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's work available at URL is recorded as https://tools.ietf.org/html/rfc3548[12].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3548.txt[13].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3548.txt[14].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3548.txt.pdf[15].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's number of pages is recorded as {'unit': '1', 'amount': '+13'}[16].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's replaced by is recorded as The Base16, Base32, and Base64 Data Encodings — replaced by (P1366): RFC 4648: The Base16, Base32, and Base64 Data Encodings[17].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's title is recorded as The Base16, Base32, and Base64 Data Encodings[18].
  • RFC 3548: The Base16, Base32, and Base64 Data Encodings's DBLP publication ID is recorded as journals/rfc/rfc3548[19].

Body

Designation and Status

RFC 3548: The Base16, Base32, and Base64 Data Encodings's instance of is recorded as The Base16, Base32, and Base64 Data Encodings — instance of (P31): Request for Comments[3].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . wikidata.org.
  9. [10] ↑ . wikidata.org.
  10. [11] ↑ . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . DBLP Dataset 2021-01-02. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 3548: The Base16, Base32, and Base64 Data Encodings. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-3548-the-base16-base32-and-base64-data-encodings
MLA “RFC 3548: The Base16, Base32, and Base64 Data Encodings.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-3548-the-base16-base32-and-base64-data-encodings.
BibTeX @misc{4ortxyz_rfc-3548-the-base16-base32-and-base64-data-encodings_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 3548: The Base16, Base32, and Base64 Data Encodings}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-3548-the-base16-base32-and-base64-data-encodings}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 3548: The Base16, Base32, and Base64 Data Encodings — https://4ort.xyz/entity/rfc-3548-the-base16-base32-and-base64-data-encodings (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-3548-the-base16-base32-and-base64-data-encodings · Last refreshed: