| rfc1455 |
May 1993 |
Physical Link Security Type of Service |
| rfc1750 |
Dec 1994 |
Randomness Recommendations for Security |
| rfc1898 |
Feb 1996 |
CyberCash Credit Card Protocol Version 0.8 |
| rfc2065 |
Jan 1997 |
Domain Name System Security Extensions |
| rfc2137 |
Apr 1997 |
Secure Domain Name System Dynamic Update |
| rfc2535 |
Mar 1999 |
Domain Name System Security Extensions |
| rfc2536 |
Mar 1999 |
DSA KEYs and SIGs in the Domain Name System (DNS) |
| rfc2537 |
Mar 1999 |
RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) |
| rfc2538 |
Mar 1999 |
Storing Certificates in the Domain Name System (DNS) |
| rfc2539 |
Mar 1999 |
Storage of Diffie-Hellman Keys in the Domain Name System (DNS) |
| rfc2540 |
Mar 1999 |
Detached Domain Name System (DNS) Information |
| rfc2541 |
Mar 1999 |
DNS Security Operational Considerations |
| rfc2606 |
Jun 1999 |
Reserved Top Level DNS Names |
| rfc2706 |
Oct 1999 |
ECML v1: Field Names for E-Commerce |
| rfc2777 |
Feb 2000 |
Publicly Verifiable Nomcom Random Selection |
| rfc2845 |
May 2000 |
Secret Key Transaction Authentication for DNS (TSIG) |
| rfc2929 |
Sep 2000 |
Domain Name System (DNS) IANA Considerations |
| rfc2930 |
Sep 2000 |
Secret Key Establishment for DNS (TKEY RR) |
| rfc2931 |
Sep 2000 |
DNS Request and Transaction Signatures ( SIG(0)s ) |
| rfc2935 |
Sep 2000 |
Internet Open Trading Protocol (IOTP) HTTP Supplement |
| rfc2936 |
Sep 2000 |
HTTP MIME Type Handler Detection |
| rfc3075 |
Mar 2001 |
XML-Signature Syntax and Processing |
| rfc3092 |
Apr 2001 |
Etymology of "Foo" |
| rfc3098 |
Apr 2001 |
How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$ |
| rfc3106 |
Apr 2001 |
ECML v1.1: Field Specifications for E-Commerce |
| rfc3110 |
May 2001 |
RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) |
| rfc3174 |
Sep 2001 |
US Secure Hash Algorithm 1 (SHA1) |
| rfc3275 |
Mar 2002 |
(Extensible Markup Language) XML-Signature Syntax and Processing |
| rfc3354 |
Aug 2002 |
Internet Open Trading Protocol Version 2 Requirements |
| rfc3504 |
Mar 2003 |
Internet Open Trading Protocol (IOTP) Version 1, Errata |
| rfc3505 |
Mar 2003 |
Electronic Commerce Modeling Language (ECML): Version 2 Requirements |
| rfc3506 |
Mar 2003 |
Requirements and Design for Voucher Trading System (VTS) |
| rfc3675 |
Feb 2004 |
.sex Considered Dangerous |
| rfc3741 |
Mar 2004 |
Exclusive XML Canonicalization, Version 1.0 |
| rfc3797 |
Jun 2004 |
Publicly Verifiable Nominations Committee (NomCom) Random Selection |
| rfc3930 |
Oct 2004 |
The Protocol versus Document Points of View in Computer Protocols |
| rfc4051 |
Apr 2005 |
Additional XML Security Uniform Resource Identifiers (URIs) |
| rfc4086 |
Jun 2005 |
Randomness Requirements for Security |
| rfc4112 |
Jun 2005 |
Electronic Commerce Modeling Language (ECML) Version 2 Specification |
| rfc4144 |
Sep 2005 |
How to Gain Prominence and Influence in Standards Organizations |
| rfc4153 |
Sep 2005 |
XML Voucher: Generic Voucher Language |
| rfc4305 |
Dec 2005 |
Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) |
| rfc4343 |
Jan 2006 |
Domain Name System (DNS) Case Insensitivity Clarification |
| rfc4634 |
Aug 2006 |
US Secure Hash Algorithms (SHA and HMAC-SHA) |
| rfc4635 |
Aug 2006 |
HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers |
| rfc5303 |
Oct 2008 |
Three-Way Handshake for IS-IS Point-to-Point Adjacencies |
| rfc5342 |
Sep 2008 |
IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters |
| rfc5395 |
Nov 2008 |
Domain Name System (DNS) IANA Considerations |
| rfc6066 |
Jan 2011 |
Transport Layer Security (TLS) Extensions: Extension Definitions |
| rfc6195 |
Mar 2011 |
Domain Name System (DNS) IANA Considerations |
| rfc6234 |
May 2011 |
US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) |
| rfc6325 |
Jul 2011 |
Routing Bridges (RBridges): Base Protocol Specification |
| rfc6326 |
Jul 2011 |
Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS |
| rfc6327 |
Jul 2011 |
Routing Bridges (RBridges): Adjacency |
| rfc6328 |
Jul 2011 |
IANA Considerations for Network Layer Protocol Identifiers |
| rfc6361 |
Aug 2011 |
PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol |
| rfc6439 |
Nov 2011 |
Routing Bridges (RBridges): Appointed Forwarders |
| rfc6604 |
Apr 2012 |
xNAME RCODE and Status Bits Clarification |
| rfc6847 |
Jan 2013 |
Fibre Channel over Ethernet (FCoE) over Transparent Interconnection of Lots of Links (TRILL) |
| rfc6895 |
Apr 2013 |
Domain Name System (DNS) IANA Considerations |
| rfc6931 |
Apr 2013 |
Additional XML Security Uniform Resource Identifiers (URIs) |
| rfc7042 |
Oct 2013 |
IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters |
| rfc7067 |
Nov 2013 |
Directory Assistance Problem and High-Level Design Proposal |
| rfc7172 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling |
| rfc7173 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL) Transport Using Pseudowires |
| rfc7174 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) Framework |
| rfc7175 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): Bidirectional Forwarding Detection (BFD) Support |
| rfc7176 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS |
| rfc7177 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): Adjacency |
| rfc7178 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support |
| rfc7179 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): Header Extension |
| rfc7180 |
May 2014 |
Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates |
| rfc7319 |
Jul 2014 |
IANA Considerations for Connectivity Fault Management (CFM) Code Points |
| rfc7357 |
Sep 2014 |
Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol |
| rfc7455 |
Mar 2015 |
Transparent Interconnection of Lots of Links (TRILL): Fault Management |
| rfc7456 |
Mar 2015 |
Loss and Delay Measurement in Transparent Interconnection of Lots of Links (TRILL) |
| rfc7780 |
Feb 2016 |
Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates |
| rfc7873 |
May 2016 |
Domain Name System (DNS) Cookies |
| rfc7961 |
Aug 2016 |
Transparent Interconnection of Lots of Links (TRILL): Interface Addresses APPsub-TLV |
| rfc7968 |
Aug 2016 |
Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination Data |
| rfc7978 |
Sep 2016 |
Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension |
| rfc8139 |
Jun 2017 |
Transparent Interconnection of Lots of Links (TRILL): Appointed Forwarders |
| rfc8171 |
Jun 2017 |
Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance Mechanisms |
| rfc8243 |
Sep 2017 |
Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL) |
| rfc8249 |
Sep 2017 |
Transparent Interconnection of Lots of Links (TRILL): MTU Negotiation |
| rfc8302 |
Jan 2018 |
Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization |
| rfc8380 |
May 2018 |
Directory-Assisted Transparent Interconnection of Lots of Links (TRILL) Encapsulation |
| rfc8381 |
May 2018 |
Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol |
| rfc8383 |
May 2018 |
Transparent Interconnection of Lots of Links (TRILL): Address Flush Message |
| rfc8384 |
Jul 2018 |
Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes |
| rfc8385 |
Jun 2018 |
Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLS |
| rfc8394 |
May 2018 |
Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements |
| rfc8397 |
May 2018 |
Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames |
