| 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 |
| 2397 | The "data" URL schemeL. Masinter | Proposed Standard | August 1998 |
| 3339 | Date and Time on the Internet: TimestampsG. Klyne, C. Newman | Proposed Standard | July 2002 |
| 3986 | Uniform Resource Identifier (URI): Generic SyntaxT. Berners-Lee, R. Fielding, L. Masinter | Internet Standard | January 2005 |
| 4122 | A Universally Unique IDentifier (UUID) URN NamespaceP. Leach, M. Mealling, R. Salz · obsoleted by RFC 9562 | Proposed Standard | July 2005 |
| 4589 | Location Types RegistryH. Schulzrinne, H. Tschofenig | Proposed Standard | July 2006 |
| 4648 | The Base16, Base32, and Base64 Data EncodingsS. Josefsson | Proposed Standard | October 2006 |
| 5234 | Augmented BNF for Syntax Specifications: ABNFD. Crocker, Ed., P. Overell | Internet Standard | January 2008 |
| 5322 | Internet Message FormatP. Resnick, Ed. | Draft Standard | October 2008 |
| 5545 | Internet Calendaring and Scheduling Core Object Specification (iCalendar)B. Desruisseaux, Ed. | Proposed Standard | September 2009 |
| 5546 | iCalendar Transport-Independent Interoperability Protocol (iTIP)C. Daboo, Ed. | Proposed Standard | December 2009 |
| 5646 | Tags for Identifying LanguagesA. Phillips, Ed., M. Davis, Ed. | Best Current Practice | September 2009 |
| 5870 | A Uniform Resource Identifier for Geographic Locations ('geo' URI)A. Mayrhofer, C. Spanring | Proposed Standard | June 2010 |
| 6047 | iCalendar Message-Based Interoperability Protocol (iMIP)A. Melnikov, Ed. | Proposed Standard | December 2010 |
| 6376 | DomainKeys Identified Mail (DKIM) SignaturesD. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed. | Internet Standard | September 2011 |
| 6838 | Media Type Specifications and Registration ProceduresN. Freed, J. Klensin, T. Hansen | Best Current Practice | January 2013 |
| 6901 | JavaScript Object Notation (JSON) PointerP. Bryan, Ed., K. Zyp, M. Nottingham, Ed. | Proposed Standard | April 2013 |
| 7265 | jCal: The JSON Format for iCalendarP. Kewisch, C. Daboo, M. Douglass | Proposed Standard | May 2014 |
| 7493 | The I-JSON Message FormatT. Bray, Ed. | Proposed Standard | March 2015 |
| 7529 | Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)C. Daboo, G. Yakushev | Proposed Standard | May 2015 |
| 7808 | Time Zone Data Distribution ServiceM. Douglass, C. Daboo | Proposed Standard | March 2016 |
| 7841 | RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed. | Informational | May 2016 |
| 7986 | New Properties for iCalendarC. Daboo | Proposed Standard | October 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 |
| 8259 | The JavaScript Object Notation (JSON) Data Interchange FormatT. Bray, Ed. | Internet Standard | December 2017 |
| 8288 | Web LinkingM. Nottingham | Proposed Standard | October 2017 |