Home › Entities › request_for_comments › RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN

RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN

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

RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN

Summary

RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN is a Request for Comments[1].

Key Facts

  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN authored Explicit Tracking with Wildcard Routes in Multicast VPN — author (P50): Eric C. Rosen[2].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN authored Explicit Tracking with Wildcard Routes in Multicast VPN — author (P50): Zhaohui Jeffrey Zhang[3].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's instance of is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — instance of (P31): Request for Comments[4].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's publisher is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — publisher (P123): Internet Engineering Task Force[5].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's based on is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — based on (P144): RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs[6].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's based on is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — based on (P144): RFC 6625: Wildcards in Multicast VPN Auto-Discovery Routes[7].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's based on is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — based on (P144): RFC 7524: Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)[8].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's based on is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — based on (P144): RFC 7582: Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels[9].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's based on is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — based on (P144): RFC 7900: Extranet Multicast in BGP/IP MPLS VPNs[10].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's DOI is recorded as 10.17487/RFC8534[11].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's language of work or name is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — language of work or name (P407): English[12].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's publication date is recorded as +2019-02-01T00:00:00Z[13].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's RfC ID is recorded as 8534[14].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's work available at URL is recorded as https://tools.ietf.org/html/rfc8534[15].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's work available at URL is recorded as https://tools.ietf.org/rfc/rfc8534.txt[16].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc8534.txt[17].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc8534.txt.pdf[18].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's number of pages is recorded as {'unit': '1', 'amount': '+21'}[19].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's title is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN[20].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's author name string is recorded as A. Dolganow[21].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's author name string is recorded as J. Kotalwar[22].
  • RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's DBLP publication ID is recorded as journals/rfc/rfc8534[23].

Body

Designation and Status

RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN's instance of is recorded as Explicit Tracking with Wildcard Routes in Multicast VPN — 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] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . 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 8534: Explicit Tracking with Wildcard Routes in Multicast VPN. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn
MLA “RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn.
BibTeX @misc{4ortxyz_rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 8534: Explicit Tracking with Wildcard Routes in Multicast VPN — https://4ort.xyz/entity/rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-8534-explicit-tracking-with-wildcard-routes-in-multicast-vpn · Last refreshed: