rfc.dk

Cited in: RFC 8148

13 RFCs mentioned in the text of RFC 8148 (Next-Generation Vehicle-Initiated Emergency Calls)

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
5012Requirements for Emergency Context Resolution with Internet TechnologiesH. Schulzrinne, R. Marshall, Ed.InformationalJanuary 2008
5069Security Threats and Requirements for Emergency Call Marking and MappingT. Taylor, Ed., H. Tschofenig, H. Schulzrinne, M. ShanmugamInformationalJanuary 2008
5226Guidelines for Writing an IANA Considerations Section in RFCsT. Narten, H. Alvestrand · obsoleted by RFC 8126Best Current PracticeMay 2008
6086Session Initiation Protocol (SIP) INFO Method and Package FrameworkC. Holmberg, E. Burger, H. KaplanProposed StandardJanuary 2011
6443Framework for Emergency Calling Using Internet MultimediaB. Rosen, H. Schulzrinne, J. Polk, A. NewtonInformationalDecember 2011
6838Media Type Specifications and Registration ProceduresN. Freed, J. Klensin, T. HansenBest Current PracticeJanuary 2013
6881Best Current Practice for Communications Services in Support of Emergency CallingB. Rosen, J. PolkBest Current PracticeMarch 2013
7303XML Media TypesH. Thompson, C. LilleyProposed StandardJuly 2014
7378Trustworthy LocationH. Tschofenig, H. Schulzrinne, B. Aboba, Ed.InformationalDecember 2014
7841RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed.InformationalMay 2016
7852Additional Data Related to an Emergency CallR. Gellens, B. Rosen, H. Tschofenig, R. Marshall, J. WinterbottomProposed StandardJuly 2016
8147Next-Generation Pan-European eCallR. Gellens, H. TschofenigProposed StandardMay 2017