Home › Entities › request_for_comments › RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint

RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint

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

RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint

Summary

RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint is a Request for Comments[1].

Key Facts

  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's instance of is recorded as IPng Requirements: A Cable Television Industry Viewpoint — instance of (P31): Request for Comments[2].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's publisher is recorded as IPng Requirements: A Cable Television Industry Viewpoint — publisher (P123): Internet Engineering Task Force[3].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's DOI is recorded as 10.17487/RFC1686[4].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's language of work or name is recorded as IPng Requirements: A Cable Television Industry Viewpoint — language of work or name (P407): English[5].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's publication date is recorded as +1994-08-01T00:00:00Z[6].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's RfC ID is recorded as 1686[7].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's main subject is recorded as IPng Requirements: A Cable Television Industry Viewpoint — main subject (P921): IPv6[8].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's work available at URL is recorded as https://tools.ietf.org/html/rfc1686[9].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's work available at URL is recorded as https://tools.ietf.org/rfc/rfc1686.txt[10].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1686.txt[11].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1686.txt.pdf[12].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's number of pages is recorded as {'unit': '1', 'amount': '+14'}[13].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's title is recorded as IPng Requirements: A Cable Television Industry Viewpoint[14].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's author name string is recorded as M. Vecchi[15].
  • RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's DBLP publication ID is recorded as journals/rfc/rfc1686[16].

Body

Designation and Status

RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint's instance of is recorded as IPng Requirements: A Cable Television Industry Viewpoint — 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] ↑ . 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] ↑ . 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] ↑ . 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 1686: IPng Requirements: A Cable Television Industry Viewpoint. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint
MLA “RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint.
BibTeX @misc{4ortxyz_rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 1686: IPng Requirements: A Cable Television Industry Viewpoint — https://4ort.xyz/entity/rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-1686-ipng-requirements-a-cable-television-industry-viewpoint · Last refreshed: