See RFC 6915.
END 5.2. XML Schema Registration This section registers an XML Schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:held:flow Registrant Contact: IETF GEOPRIV Working Group (geopriv@ietf.org), Ray Bellis (ray.bellis@nominet.org.uk) Schema: The XML for this schema can be found as the entirety of Section 4 of this document. 6. Privacy Considerations All of the considerations in [RFC6155] apply to the use of the mechanism defined in this document. Like [RFC6155], this specification assumes that the Location Server being queried already has access to the internal state of the network near one end of the flow being queried (for instance, access to the bindings in a NAT in the path of the flow). Clients making queries using this specification in environments where that assumption may not be true should be aware that the request provides information about that client's communications that the Location Server would not otherwise be able to discern and may represent additional privacy exposure for that client. Bellis Standards Track [Page 7] RFC 6915 Flow Identity for HELD April 2013 7. Security Considerations This document introduces no new security considerations beyond those in [RFC6155]. 8. Acknowledgements The author wishes to thank the members of the NICC Emergency Location Task Group, the IETF GeoPriv Working Group, and the authors of [RFC6155], from which the text for the URN and XML Schema Registrations were derived. 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 5985, September 2010. [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. Barnes, "Use of Device Identity in HTTP-Enabled Location Delivery (HELD)", RFC 6155, March 2011. 9.2. Informative References [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980. [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981. [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram Congestion Control Protocol (DCCP)", RFC 4340, March 2006. [RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007. Bellis Standards Track [Page 8] RFC 6915 Flow Identity for HELD April 2013 [RFC6280] Barnes, R., Lepinski, M., Cooper, A., Morris, J., Tschofenig, H., and H. Schulzrinne, "An Architecture for Location and Location Privacy in Internet Applications", BCP 160, RFC 6280, July 2011. Author's Address Ray Bellis Nominet UK Edmund Halley Road Oxford OX4 4DQ United Kingdom Phone: +44 1865 332211 EMail: ray.bellis@nominet.org.uk URI: http://www.nominet.org.uk/ Bellis Standards Track [Page 9]-- Leo's gemini proxy
-- Connecting to gemini.bortzmeyer.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/plain
-- Response ended
-- Page fetched on Mon May 6 18:58:13 2024