rfc.dk

Cited in: RFC 7840

14 RFCs mentioned in the text of RFC 7840 (A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol)

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
3688The IETF XML RegistryM. MeallingBest Current PracticeJanuary 2004
5031A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesH. SchulzrinneProposed StandardJanuary 2008
5222LoST: A Location-to-Service Translation ProtocolT. Hardie, A. Newton, H. Schulzrinne, H. TschofenigProposed StandardAugust 2008
5582Location-to-URL Mapping Architecture and FrameworkH. SchulzrinneInformationalSeptember 2009
5687GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and RequirementsH. Tschofenig, H. SchulzrinneInformationalMarch 2010
5741RFC Streams, Headers, and BoilerplatesL. Daigle, Ed., O. Kolkman, Ed., IAB · obsoleted by RFC 7841InformationalDecember 2009
5985HTTP-Enabled Location Delivery (HELD)M. Barnes, Ed.Proposed StandardSeptember 2010
5986Discovering the Local Location Information Server (LIS)M. Thomson, J. WinterbottomProposed StandardSeptember 2010
6155Use of Device Identity in HTTP-Enabled Location Delivery (HELD)J. Winterbottom, M. Thomson, H. Tschofenig, R. BarnesProposed StandardMarch 2011
6443Framework for Emergency Calling Using Internet MultimediaB. Rosen, H. Schulzrinne, J. Polk, A. NewtonInformationalDecember 2011
6881Best Current Practice for Communications Services in Support of Emergency CallingB. Rosen, J. PolkBest Current PracticeMarch 2013
6915Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)R. BellisProposed StandardApril 2013
7216Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNSM. Thomson, R. BellisProposed StandardApril 2014