Home › Entities › request_for_comments › RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry

RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry

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

RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry

Summary

RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry is a Request for Comments[1].

Key Facts

  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's instance of is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — instance of (P31): Request for Comments[2].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's publisher is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — publisher (P123): Internet Engineering Task Force[3].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's based on is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — based on (P144): RFC 2244: ACAP -- Application Configuration Access Protocol[4].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's DOI is recorded as 10.17487/RFC6075[5].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's language of work or name is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — language of work or name (P407): English[6].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's publication date is recorded as +2010-12-01T00:00:00Z[7].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's RfC ID is recorded as 6075[8].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's main subject is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — main subject (P921): Application Configuration Access Protocol[9].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's work available at URL is recorded as https://tools.ietf.org/html/rfc6075[10].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6075.txt[11].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6075.txt[12].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6075.txt.pdf[13].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's number of pages is recorded as {'unit': '1', 'amount': '+7'}[14].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's title is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry[15].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's author name string is recorded as D. Cridland[16].
  • RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's DBLP publication ID is recorded as journals/rfc/rfc6075[17].

Body

Designation and Status

RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry's instance of is recorded as The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — instance of (P31): Request for Comments[2].

References

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

Direct Wikidata claims

  1. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [3] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . 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] ↑ . 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 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry
MLA “RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry.
BibTeX @misc{4ortxyz_rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry — https://4ort.xyz/entity/rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-6075-the-internet-assigned-number-authority-iana-application-configuration-access-protocol-acap-vendor-subtrees-registry · Last refreshed: