| 2026 | The Internet Standards Process -- Revision 3S. Bradner | Best Current Practice | October 1996 |
| 2119 | Key words for use in RFCs to Indicate Requirement LevelsS. Bradner | Best Current Practice | March 1997 |
| 2606 | Reserved Top Level DNS NamesD. Eastlake 3rd, A. Panitz | Best Current Practice | June 1999 |
| 2863 | The Interfaces Group MIBK. McCloghrie, F. Kastenholz | Draft Standard | June 2000 |
| 3688 | The IETF XML RegistryM. Mealling | Best Current Practice | January 2004 |
| 3849 | IPv6 Address Prefix Reserved for DocumentationG. Huston, A. Lord, P. Smith | Informational | July 2004 |
| 3986 | Uniform Resource Identifier (URI): Generic SyntaxT. Berners-Lee, R. Fielding, L. Masinter | Internet Standard | January 2005 |
| 4151 | The 'tag' URI SchemeT. Kindberg, S. Hawke | Informational | October 2005 |
| 4181 | Guidelines for Authors and Reviewers of MIB DocumentsC. Heard, Ed. | Best Current Practice | September 2005 |
| 4252 | The Secure Shell (SSH) Authentication ProtocolT. Ylonen, C. Lonvick, Ed. | Proposed Standard | January 2006 |
| 4253 | The Secure Shell (SSH) Transport Layer ProtocolT. Ylonen, C. Lonvick, Ed. | Proposed Standard | January 2006 |
| 4301 | Security Architecture for the Internet ProtocolS. Kent, K. Seo | Proposed Standard | December 2005 |
| 5378 | Rights Contributors Provide to the IETF TrustS. Bradner, Ed., J. Contreras, Ed. | Best Current Practice | November 2008 |
| 5398 | Autonomous System (AS) Number Reservation for Documentation UseG. Huston | Informational | December 2008 |
| 5612 | Enterprise Number for Documentation UseP. Eronen, D. Harrington | Informational | August 2009 |
| 5737 | IPv4 Address Blocks Reserved for DocumentationJ. Arkko, M. Cotton, L. Vegoda | Informational | January 2010 |
| 6020 | YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)M. Bjorklund, Ed. | Proposed Standard | October 2010 |
| 6021 | Common YANG Data TypesJ. Schoenwaelder, Ed. · obsoleted by RFC 6991 | Proposed Standard | October 2010 |
| 6241 | Network Configuration Protocol (NETCONF)R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder, Ed., A. Bierman, Ed. | Proposed Standard | June 2011 |
| 6991 | Common YANG Data TypesJ. Schoenwaelder, Ed. · obsoleted by RFC 9911 | Proposed Standard | July 2013 |
| 7223 | A YANG Data Model for Interface ManagementM. Bjorklund · obsoleted by RFC 8343 | Proposed Standard | May 2014 |
| 7224 | IANA Interface Type YANG ModuleM. Bjorklund | Proposed Standard | May 2014 |
| 7407 | A YANG Data Model for SNMP ConfigurationM. Bjorklund, J. Schoenwaelder | Proposed Standard | December 2014 |
| 7841 | RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed. | Informational | May 2016 |
| 7950 | The YANG 1.1 Data Modeling LanguageM. Bjorklund, Ed. | Proposed Standard | August 2016 |
| 7951 | JSON Encoding of Data Modeled with YANGL. Lhotka | Proposed Standard | August 2016 |
| 7952 | Defining and Using Metadata with YANGL. Lhotka | Proposed Standard | August 2016 |
| 8040 | RESTCONF ProtocolA. Bierman, M. Bjorklund, K. Watsen | Proposed Standard | January 2017 |
| 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 |
| 8199 | YANG Module ClassificationD. Bogdanovic, B. Claise, C. Moberg | Informational | July 2017 |
| 8299 | YANG Data Model for L3VPN Service DeliveryQ. Wu, Ed., S. Litkowski, L. Tomotaki, K. Ogaki | Proposed Standard | January 2018 |
| 8309 | Service Models ExplainedQ. Wu, W. Liu, A. Farrel | Informational | January 2018 |
| 8340 | YANG Tree DiagramsM. Bjorklund, L. Berger, Ed. | Best Current Practice | March 2018 |
| 8341 | Network Configuration Access Control ModelA. Bierman, M. Bjorklund | Internet Standard | March 2018 |
| 8342 | Network Management Datastore Architecture (NMDA)M. Bjorklund, J. Schoenwaelder, P. Shafer, K. Watsen, R. Wilton | Proposed Standard | March 2018 |
| 8343 | A YANG Data Model for Interface ManagementM. Bjorklund | Proposed Standard | March 2018 |
| 8349 | A YANG Data Model for Routing Management (NMDA Version)L. Lhotka, A. Lindem, Y. Qu | Proposed Standard | March 2018 |
| 8407 | Guidelines for Authors and Reviewers of Documents Containing YANG Data ModelsA. Bierman · obsoleted by RFC 9907 | Best Current Practice | October 2018 |
| 8446 | The Transport Layer Security (TLS) Protocol Version 1.3E. Rescorla · obsoleted by RFC 9846 | Proposed Standard | August 2018 |
| 8466 | A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service DeliveryB. Wen, G. Fioccola, Ed., C. Xie, L. Jalil | Proposed Standard | October 2018 |
| 8519 | YANG Data Model for Network Access Control Lists (ACLs)M. Jethanandani, S. Agarwal, L. Huang, D. Blair | Proposed Standard | March 2019 |
| 8675 | A YANG Data Model for Tunnel Interface TypesM. Boucadair, I. Farrer, R. Asati | Proposed Standard | November 2019 |
| 8791 | YANG Data Structure ExtensionsA. Bierman, M. Björklund, K. Watsen | Proposed Standard | June 2020 |
| 8792 | Handling Long Lines in Content of Internet-Drafts and RFCsK. Watsen, E. Auerswald, A. Farrel, Q. Wu | Informational | June 2020 |
| 8819 | YANG Module TagsC. Hopps, L. Berger, D. Bogdanovic | Proposed Standard | January 2021 |
| 8892 | Guidelines and Registration Procedures for Interface Types and Tunnel TypesD. Thaler, D. Romascanu | Proposed Standard | August 2020 |
| 8969 | A Framework for Automating Service and Network Management with YANGQ. Wu, Ed., M. Boucadair, Ed., D. Lopez, C. Xie, L. Geng | Informational | January 2021 |
| 9000 | QUIC: A UDP-Based Multiplexed and Secure TransportJ. Iyengar, Ed., M. Thomson, Ed. | Proposed Standard | May 2021 |
| 9108 | YANG Types for DNS Classes and Resource Record TypesL. Lhotka, P. Špaček | Proposed Standard | September 2021 |
| 9129 | YANG Data Model for the OSPF ProtocolD. Yeung, Y. Qu, Z. Zhang, I. Chen, A. Lindem | Proposed Standard | October 2022 |
| 9132 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationM. Boucadair, Ed., J. Shallow, T. Reddy.K | Proposed Standard | September 2021 |
| 9182 | A YANG Network Data Model for Layer 3 VPNsS. Barguil, O. Gonzalez de Dios, Ed., M. Boucadair, Ed., L. Munoz, A. Aguado | Proposed Standard | February 2022 |
| 9195 | A File Format for YANG Instance DataB. Lengyel, B. Claise | Proposed Standard | February 2022 |
| 9244 | Distributed Denial-of-Service Open Threat Signaling (DOTS) TelemetryM. Boucadair, Ed., T. Reddy.K, Ed., E. Doron, M. Chen, J. Shallow | Proposed Standard | June 2022 |
| 9291 | A YANG Network Data Model for Layer 2 VPNsM. Boucadair, Ed., O. Gonzalez de Dios, Ed., S. Barguil, L. Munoz | Proposed Standard | September 2022 |
| 9362 | Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block TransmissionM. Boucadair, J. Shallow | Proposed Standard | February 2023 |
| 9460 | Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)B. Schwartz, M. Bishop, E. Nygren | Proposed Standard | November 2023 |
| 9557 | Date and Time on the Internet: Timestamps with Additional InformationU. Sharma, C. Bormann | Proposed Standard | April 2024 |
| 9637 | Expanding the IPv6 Documentation SpaceG. Huston, N. Buraglio | Informational | August 2024 |
| 9645 | YANG Groupings for TLS Clients and TLS ServersK. Watsen | Proposed Standard | October 2024 |
| 9890 | An Update to YANG Module Names RegistrationA. Bierman, M. Boucadair, Ed., Q. Wu | Proposed Standard | October 2025 |
| 9911 | Common YANG Data TypesJ. Schönwälder, Ed. | Proposed Standard | December 2025 |