Home › Entities › request_for_comments › RFC 2732: Format for Literal IPv6 Addresses in URL's

RFC 2732: Format for Literal IPv6 Addresses in URL's

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

RFC 2732: Format for Literal IPv6 Addresses in URL's

Summary

RFC 2732: Format for Literal IPv6 Addresses in URL's is a Request for Comments[1].

Key Facts

  • RFC 2732: Format for Literal IPv6 Addresses in URL's authored Format for Literal IPv6 Addresses in URL's — author (P50): Brian Carpenter[2].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's authored Format for Literal IPv6 Addresses in URL's — author (P50): Robert M. Hinden[3].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's authored Format for Literal IPv6 Addresses in URL's — author (P50): Larry Masinter[4].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's instance of is recorded as Format for Literal IPv6 Addresses in URL's — instance of (P31): Request for Comments[5].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's publisher is recorded as Format for Literal IPv6 Addresses in URL's — publisher (P123): Internet Engineering Task Force[6].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's based on is recorded as Format for Literal IPv6 Addresses in URL's — based on (P144): RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax[7].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's DOI is recorded as 10.17487/RFC2732[8].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's language of work or name is recorded as Format for Literal IPv6 Addresses in URL's — language of work or name (P407): English[9].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's publication date is recorded as +1999-12-01T00:00:00Z[10].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's RfC ID is recorded as 2732[11].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's main subject is recorded as Format for Literal IPv6 Addresses in URL's — main subject (P921): IPv6 address[12].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's work available at URL is recorded as https://tools.ietf.org/html/rfc2732[13].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2732.txt[14].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2732.txt[15].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2732.txt.pdf[16].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's work available at URL is recorded as https://www.rfc-editor.org/info/rfc2732[17].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's number of pages is recorded as {'unit': '1', 'amount': '+5'}[18].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's replaced by is recorded as Format for Literal IPv6 Addresses in URL's — replaced by (P1366): RFC 3986: Uniform Resource Identifier (URI): Generic Syntax[19].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's title is recorded as Format for Literal IPv6 Addresses in URL's[20].
  • RFC 2732: Format for Literal IPv6 Addresses in URL's's DBLP publication ID is recorded as journals/rfc/rfc2732[21].

Body

Designation and Status

RFC 2732: Format for Literal IPv6 Addresses in URL's's instance of is recorded as Format for Literal IPv6 Addresses in URL's — instance of (P31): Request for Comments[5].

References

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

Direct Wikidata claims

  1. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [4] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . 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] ↑ . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . RFC Index. Retrieved . wikidata.org.
  19. [20] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . 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 2732: Format for Literal IPv6 Addresses in URL's. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-2732-format-for-literal-ipv6-addresses-in-url-s
MLA “RFC 2732: Format for Literal IPv6 Addresses in URL's.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-2732-format-for-literal-ipv6-addresses-in-url-s.
BibTeX @misc{4ortxyz_rfc-2732-format-for-literal-ipv6-addresses-in-url-s_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 2732: Format for Literal IPv6 Addresses in URL's}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-2732-format-for-literal-ipv6-addresses-in-url-s}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 2732: Format for Literal IPv6 Addresses in URL's — https://4ort.xyz/entity/rfc-2732-format-for-literal-ipv6-addresses-in-url-s (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-2732-format-for-literal-ipv6-addresses-in-url-s · Last refreshed: