Home › Entities › request_for_comments › RFC 5305: IS-IS Extensions for Traffic Engineering

RFC 5305: IS-IS Extensions for Traffic Engineering

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

RFC 5305: IS-IS Extensions for Traffic Engineering

Summary

RFC 5305: IS-IS Extensions for Traffic Engineering is a Request for Comments[1].

Key Facts

  • RFC 5305: IS-IS Extensions for Traffic Engineering authored IS-IS Extensions for Traffic Engineering — author (P50): Tony Li[2].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's instance of is recorded as IS-IS Extensions for Traffic Engineering — instance of (P31): Request for Comments[3].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's publisher is recorded as IS-IS Extensions for Traffic Engineering — publisher (P123): Internet Engineering Task Force[4].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's DOI is recorded as 10.17487/RFC5305[5].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's language of work or name is recorded as IS-IS Extensions for Traffic Engineering — language of work or name (P407): English[6].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's publication date is recorded as +2008-10-01T00:00:00Z[7].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's RfC ID is recorded as 5305[8].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's main subject is recorded as IS-IS Extensions for Traffic Engineering — main subject (P921): Intermediate System to Intermediate System[9].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's main subject is recorded as IS-IS Extensions for Traffic Engineering — main subject (P921): traffic engineering[10].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's work available at URL is recorded as https://tools.ietf.org/html/rfc5305[11].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5305.txt[12].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5305.txt[13].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5305.txt.pdf[14].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's number of pages is recorded as {'unit': '1', 'amount': '+17'}[15].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's replaces is recorded as IS-IS Extensions for Traffic Engineering — replaces (P1365): RFC 3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)[16].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's title is recorded as IS-IS Extensions for Traffic Engineering[17].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's author name string is recorded as H. Smit[18].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's amended by is recorded as IS-IS Extensions for Traffic Engineering — amended by (P2567): RFC 5307: IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)[19].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's amended by is recorded as IS-IS Extensions for Traffic Engineering — amended by (P2567): RFC 8918: Invalid TLV Handling in IS-IS[20].
  • RFC 5305: IS-IS Extensions for Traffic Engineering's DBLP publication ID is recorded as journals/rfc/rfc5305[21].

Body

Designation and Status

RFC 5305: IS-IS Extensions for Traffic Engineering's instance of is recorded as IS-IS Extensions for Traffic Engineering — 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] ↑ . 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] ↑ . RFC Index. Retrieved . 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 5305: IS-IS Extensions for Traffic Engineering. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-5305-is-is-extensions-for-traffic-engineering
MLA “RFC 5305: IS-IS Extensions for Traffic Engineering.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-5305-is-is-extensions-for-traffic-engineering.
BibTeX @misc{4ortxyz_rfc-5305-is-is-extensions-for-traffic-engineering_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 5305: IS-IS Extensions for Traffic Engineering}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-5305-is-is-extensions-for-traffic-engineering}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 5305: IS-IS Extensions for Traffic Engineering — https://4ort.xyz/entity/rfc-5305-is-is-extensions-for-traffic-engineering (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-5305-is-is-extensions-for-traffic-engineering · Last refreshed: