| 2119 | Key words for use in RFCs to Indicate Requirement LevelsS. Bradner | Best Current Practice | March 1997 |
| 2392 | Content-ID and Message-ID Uniform Resource LocatorsE. Levinson | Proposed Standard | August 1998 |
| 2818 | HTTP Over TLSE. Rescorla · obsoleted by RFC 9110 | Informational | May 2000 |
| 3261 | SIP: Session Initiation ProtocolJ. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler | Proposed Standard | July 2002 |
| 3262 | Reliability of Provisional Responses in Session Initiation Protocol (SIP)J. Rosenberg, H. Schulzrinne | Proposed Standard | July 2002 |
| 3325 | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted NetworksC. Jennings, J. Peterson, M. Watson | Informational | December 2002 |
| 3428 | Session Initiation Protocol (SIP) Extension for Instant MessagingB. Campbell, Ed., J. Rosenberg, H. Schulzrinne, C. Huitema, D. Gurle | Proposed Standard | December 2002 |
| 3550 | RTP: A Transport Protocol for Real-Time ApplicationsH. Schulzrinne, S. Casner, R. Frederick, V. Jacobson | Internet Standard | July 2003 |
| 3629 | UTF-8, a transformation format of ISO 10646F. Yergeau | Internet Standard | November 2003 |
| 3986 | Uniform Resource Identifier (URI): Generic SyntaxT. Berners-Lee, R. Fielding, L. Masinter | Internet Standard | January 2005 |
| 4119 | A Presence-based GEOPRIV Location Object FormatJ. Peterson | Proposed Standard | December 2005 |
| 5031 | A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesH. Schulzrinne | Proposed Standard | January 2008 |
| 5222 | LoST: A Location-to-Service Translation ProtocolT. Hardie, A. Newton, H. Schulzrinne, H. Tschofenig | Proposed Standard | August 2008 |
| 5234 | Augmented BNF for Syntax Specifications: ABNFD. Crocker, Ed., P. Overell | Internet Standard | January 2008 |
| 6442 | Location Conveyance for the Session Initiation ProtocolJ. Polk, B. Rosen, J. Peterson | Proposed Standard | December 2011 |
| 6443 | Framework for Emergency Calling Using Internet MultimediaB. Rosen, H. Schulzrinne, J. Polk, A. Newton | Informational | December 2011 |
| 6881 | Best Current Practice for Communications Services in Support of Emergency CallingB. Rosen, J. Polk | Best Current Practice | March 2013 |
| 7303 | XML Media TypesH. Thompson, C. Lilley | Proposed Standard | July 2014 |
| 7378 | Trustworthy LocationH. Tschofenig, H. Schulzrinne, B. Aboba, Ed. | Informational | December 2014 |
| 7841 | RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed. | Informational | May 2016 |
| 7852 | Additional Data Related to an Emergency CallR. Gellens, B. Rosen, H. Tschofenig, R. Marshall, J. Winterbottom | Proposed Standard | July 2016 |
| 8126 | Guidelines for Writing an IANA Considerations Section in RFCsM. Cotton, B. Leiba, T. Narten | Best Current Practice | June 2017 |
| 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. Leiba | Best Current Practice | May 2017 |
| 8224 | Authenticated Identity Management in the Session Initiation Protocol (SIP)J. Peterson, C. Jennings, E. Rescorla, C. Wendt | Proposed Standard | February 2018 |
| 8225 | PASSporT: Personal Assertion TokenC. Wendt, J. Peterson | Proposed Standard | February 2018 |