Home › Entities › request_for_comments › RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

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

RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

Summary

RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP is a Request for Comments[1].

Key Facts

  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP authored North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — author (P50): Adrian Farrel[2].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP authored North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — author (P50): Stefano Previdi[3].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's instance of is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — instance of (P31): Request for Comments[4].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's publisher is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — publisher (P123): Internet Engineering Task Force[5].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's DOI is recorded as 10.17487/RFC7752[6].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's language of work or name is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — language of work or name (P407): English[7].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's publication date is recorded as +2016-03-01T00:00:00Z[8].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's RfC ID is recorded as 7752[9].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's work available at URL is recorded as https://tools.ietf.org/html/rfc7752[10].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc7752.txt[11].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc7752.txt[12].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc7752.txt.pdf[13].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's number of pages is recorded as {'unit': '1', 'amount': '+48'}[14].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's replaced by is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — replaced by (P1366): RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP[15].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's title is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP[16].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's author name string is recorded as H. Gredler[17].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's author name string is recorded as J. Medved[18].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's author name string is recorded as S. Ray[19].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's amended by is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — amended by (P2567): RFC 9029: Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries[20].
  • RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's DBLP publication ID is recorded as journals/rfc/rfc7752[21].

Body

Designation and Status

RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP's instance of is recorded as North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — instance of (P31): Request for Comments[4].

References

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

Direct Wikidata claims

  1. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [3] ↑ . 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] ↑ . 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] ↑ . 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 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp
MLA “RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp.
BibTeX @misc{4ortxyz_rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP — https://4ort.xyz/entity/rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-using-bgp · Last refreshed: