RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.rfc-editor.org/rfc/rfc7840.txt below:

Additional Element for HELD Routing Information

message containing default routing information and an HTTPS location URI. https://ls.example.com:9768/357yc6s64ceyoiuy5ax3o sip:112@example.com sips:112@example.com xmpp:112@example.com Figure 5: Example Location Response with Default Routing Information 8. Privacy Considerations This document makes no changes that require privacy considerations beyond those already described in [RFC5985]. It does, however, extend those described in [RFC6155]. [RFC5985] describes the privacy considerations surrounding the HELD location configuration protocol, and this document makes no specific changes to these considerations. [RFC6155] extends HELD beyond a simple LCP by enabling authorized third parties to acquire location information and describing the issues in Section 4. The HELD routing extension supports returning URIs that represent specific services operating in the Target's vicinity. This represents additional information about the Target; as a consequence, it is recommended that this option only be used when the LIS returns a location URI, not a location value. 9. Security Considerations This document imposes no additional security considerations beyond those already described in [RFC5985] and [RFC6155]. Winterbottom, et al. Standards Track [Page 12] RFC 7840 HELD Routing May 2016 10. IANA Considerations 10.1. URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:geopriv:held:ri' Per this document, IANA has registered a new XML namespace, following the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:held:ri Registrant Contact: IETF ECRIT working group (ecrit@ietf.org), James Winterbottom (a.james.winterbottom@gmail.com). XML: BEGIN HELD Routing Information Extensions Additional Element for HELD Routing Information urn:ietf:params:xml:ns:geopriv:held:ri

See RFC 7840.

END 10.2. XML Schema Registration This section registers an XML schema as per the procedures in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:held:ri Registrant Contact: IETF ECRIT working group (ecrit@ietf.org), James Winterbottom (a.james.winterbottom@gmail.com). XML: The XML for this schema can be found as the entirety of Section 6 of this document. Winterbottom, et al. Standards Track [Page 13] RFC 7840 HELD Routing May 2016 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5985] Barnes, M., Ed., "HTTP-Enabled Location Delivery (HELD)", RFC 5985, DOI 10.17487/RFC5985, September 2010, . [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in Support of Emergency Calling", BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, . 11.2. Informative References [M493] European Telecommunications Standards Institute, "Functional architecture to support European requirements on emergency caller location determination and transport", ES 203 178, V1.1.1, February 2015. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, DOI 10.17487/RFC5031, January 2008, . [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig, "LoST: A Location-to-Service Translation Protocol", RFC 5222, DOI 10.17487/RFC5222, August 2008, . [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and Framework", RFC 5582, DOI 10.17487/RFC5582, September 2009, . [RFC5687] Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements", RFC 5687, DOI 10.17487/RFC5687, March 2010, . Winterbottom, et al. Standards Track [Page 14] RFC 7840 HELD Routing May 2016 [RFC5986] Thomson, M. and J. Winterbottom, "Discovering the Local Location Information Server (LIS)", RFC 5986, DOI 10.17487/RFC5986, September 2010, . [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. Barnes, "Use of Device Identity in HTTP-Enabled Location Delivery (HELD)", RFC 6155, DOI 10.17487/RFC6155, March 2011, . [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework for Emergency Calling Using Internet Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 2011, . [RFC6915] Bellis, R., "Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)", RFC 6915, DOI 10.17487/RFC6915, April 2013, . [RFC7216] Thomson, M. and R. Bellis, "Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS", RFC 7216, DOI 10.17487/RFC7216, April 2014, . Acknowledgements We would like to thank Wilfried Lange for sharing his views with us. We would also like to thank Bruno Chatras for his early review comments and Keith Drage for his more detailed review. Thanks to Roger Marshall and Randy Gellens for their helpful suggestions. Winterbottom, et al. Standards Track [Page 15] RFC 7840 HELD Routing May 2016 Authors' Addresses James Winterbottom Winterb Consulting Services Gwynneville, NSW 2500 Australia Phone: +61 448 266004 Email: a.james.winterbottom@gmail.com Hannes Tschofenig Hall in Tirol 6060 Austria Email: Hannes.Tschofenig@gmx.net URI: http://www.tschofenig.priv.at Laura Liess Deutsche Telekom Networks Deutsche Telekom Allee 7 Darmstadt, Hessen 64295 Germany Email: L.Liess@telekom.de URI: http://www.telekom.de Winterbottom, et al. Standards Track [Page 16]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4