Home › Entities › request_for_comments › RFC 5580: Carrying Location Objects in RADIUS and Diameter

RFC 5580: Carrying Location Objects in RADIUS and Diameter

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

RFC 5580: Carrying Location Objects in RADIUS and Diameter

Summary

RFC 5580: Carrying Location Objects in RADIUS and Diameter is a Request for Comments[1].

Key Facts

  • RFC 5580: Carrying Location Objects in RADIUS and Diameter authored Carrying Location Objects in RADIUS and Diameter — author (P50): Hannes Tschofenig[2].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter authored Carrying Location Objects in RADIUS and Diameter — author (P50): Bernard D. Aboba[3].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter authored Carrying Location Objects in RADIUS and Diameter — author (P50): Mark Jones[4].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's instance of is recorded as Carrying Location Objects in RADIUS and Diameter — instance of (P31): Request for Comments[5].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's publisher is recorded as Carrying Location Objects in RADIUS and Diameter — publisher (P123): Internet Engineering Task Force[6].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's DOI is recorded as 10.17487/RFC5580[7].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's language of work or name is recorded as Carrying Location Objects in RADIUS and Diameter — language of work or name (P407): English[8].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's publication date is recorded as +2009-08-01T00:00:00Z[9].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's RfC ID is recorded as 5580[10].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's work available at URL is recorded as https://tools.ietf.org/html/rfc5580[11].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5580.txt[12].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5580.txt[13].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5580.txt.pdf[14].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's number of pages is recorded as {'unit': '1', 'amount': '+53'}[15].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's title is recorded as Carrying Location Objects in RADIUS and Diameter[16].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's author name string is recorded as F. Adrangi[17].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's author name string is recorded as A. Lior[18].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's amended by is recorded as Carrying Location Objects in RADIUS and Diameter — amended by (P2567): RFC 8559: Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) Protocol[19].
  • RFC 5580: Carrying Location Objects in RADIUS and Diameter's DBLP publication ID is recorded as journals/rfc/rfc5580[20].

Body

Designation and Status

RFC 5580: Carrying Location Objects in RADIUS and Diameter's instance of is recorded as Carrying Location Objects in RADIUS and Diameter — 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] ↑ . 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] ↑ . 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 5580: Carrying Location Objects in RADIUS and Diameter. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-5580-carrying-location-objects-in-radius-and-diameter
MLA “RFC 5580: Carrying Location Objects in RADIUS and Diameter.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-5580-carrying-location-objects-in-radius-and-diameter.
BibTeX @misc{4ortxyz_rfc-5580-carrying-location-objects-in-radius-and-diameter_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 5580: Carrying Location Objects in RADIUS and Diameter}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-5580-carrying-location-objects-in-radius-and-diameter}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 5580: Carrying Location Objects in RADIUS and Diameter — https://4ort.xyz/entity/rfc-5580-carrying-location-objects-in-radius-and-diameter (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-5580-carrying-location-objects-in-radius-and-diameter · Last refreshed: