Home › Entities › request_for_comments › RFC 4873: GMPLS Segment Recovery

RFC 4873: GMPLS Segment Recovery

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

RFC 4873: GMPLS Segment Recovery

Summary

RFC 4873: GMPLS Segment Recovery is a Request for Comments[1].

Key Facts

  • RFC 4873: GMPLS Segment Recovery authored GMPLS Segment Recovery — author (P50): Adrian Farrel[2].
  • RFC 4873: GMPLS Segment Recovery authored GMPLS Segment Recovery — author (P50): Lou Berger[3].
  • RFC 4873: GMPLS Segment Recovery authored GMPLS Segment Recovery — author (P50): Dimitri Papadimitriou[4].
  • RFC 4873: GMPLS Segment Recovery's instance of is recorded as GMPLS Segment Recovery — instance of (P31): Request for Comments[5].
  • RFC 4873: GMPLS Segment Recovery's publisher is recorded as GMPLS Segment Recovery — publisher (P123): Internet Engineering Task Force[6].
  • RFC 4873: GMPLS Segment Recovery's based on is recorded as GMPLS Segment Recovery — based on (P144): RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions[7].
  • RFC 4873: GMPLS Segment Recovery's based on is recorded as GMPLS Segment Recovery — based on (P144): RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery[8].
  • RFC 4873: GMPLS Segment Recovery's DOI is recorded as 10.17487/RFC4873[9].
  • RFC 4873: GMPLS Segment Recovery's language of work or name is recorded as GMPLS Segment Recovery — language of work or name (P407): English[10].
  • RFC 4873: GMPLS Segment Recovery's publication date is recorded as +2007-05-01T00:00:00Z[11].
  • RFC 4873: GMPLS Segment Recovery's RfC ID is recorded as 4873[12].
  • RFC 4873: GMPLS Segment Recovery's main subject is recorded as GMPLS Segment Recovery — main subject (P921): Generalized Multi-Protocol Label Switching[13].
  • RFC 4873: GMPLS Segment Recovery's work available at URL is recorded as https://tools.ietf.org/html/rfc4873[14].
  • RFC 4873: GMPLS Segment Recovery's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4873.txt[15].
  • RFC 4873: GMPLS Segment Recovery's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4873.txt[16].
  • RFC 4873: GMPLS Segment Recovery's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4873.txt.pdf[17].
  • RFC 4873: GMPLS Segment Recovery's number of pages is recorded as {'unit': '1', 'amount': '+25'}[18].
  • RFC 4873: GMPLS Segment Recovery's title is recorded as GMPLS Segment Recovery[19].
  • RFC 4873: GMPLS Segment Recovery's author name string is recorded as I. Bryskin[20].
  • RFC 4873: GMPLS Segment Recovery's amended by is recorded as GMPLS Segment Recovery — amended by (P2567): RFC 9270: GMPLS Signaling Extensions for Shared Mesh Protection[21].
  • RFC 4873: GMPLS Segment Recovery's DBLP publication ID is recorded as journals/rfc/rfc4873[22].

Body

Designation and Status

RFC 4873: GMPLS Segment Recovery's instance of is recorded as GMPLS Segment Recovery — 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] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . 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 4873: GMPLS Segment Recovery. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-4873-gmpls-segment-recovery
MLA “RFC 4873: GMPLS Segment Recovery.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-4873-gmpls-segment-recovery.
BibTeX @misc{4ortxyz_rfc-4873-gmpls-segment-recovery_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 4873: GMPLS Segment Recovery}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-4873-gmpls-segment-recovery}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 4873: GMPLS Segment Recovery — https://4ort.xyz/entity/rfc-4873-gmpls-segment-recovery (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-4873-gmpls-segment-recovery · Last refreshed: