Home › Entities › request_for_comments › RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol

RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol

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

RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol

Summary

RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol is a Request for Comments[1].

Key Facts

  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol authored Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — author (P50): Henning Schulzrinne[2].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol authored Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — author (P50): Hannes Tschofenig[3].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's instance of is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — instance of (P31): Request for Comments[4].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's publisher is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — publisher (P123): Internet Engineering Task Force[5].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's DOI is recorded as 10.17487/RFC6739[6].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's language of work or name is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — language of work or name (P407): English[7].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's publication date is recorded as +2012-10-01T00:00:00Z[8].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's RfC ID is recorded as 6739[9].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's work available at URL is recorded as https://tools.ietf.org/html/rfc6739[10].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6739.txt[11].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6739.txt[12].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6739.txt.pdf[13].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's number of pages is recorded as {'unit': '1', 'amount': '+25'}[14].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's title is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol[15].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's amended by is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — amended by (P2567): RFC 8996: Deprecating TLS 1.0 and TLS 1.1[16].
  • RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's DBLP publication ID is recorded as journals/rfc/rfc6739[17].

Body

Designation and Status

RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol's instance of is recorded as Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol — 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] ↑ . 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 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol
MLA “RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol.
BibTeX @misc{4ortxyz_rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 6739: Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) Protocol — https://4ort.xyz/entity/rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-6739-synchronizing-service-boundaries-and-mapping-elements-based-on-the-location-to-service-translation-lost-protocol · Last refreshed: