|
- IETF | RFCs
The RFC series has two subseries, STDs and BCPs, with each numbered STD and BCP comprising one or more RFCs STDs are 'Internet Standard' RFCs, and BCPs are RFCs that describe 'Best Current Practices' for the Internet, some of which are administrative processes for the IETF
- RFC 9293: Transmission Control Protocol (TCP)
RFC 5681 and RFC 6298 describe the basic algorithms on the IETF Standards Track that are broadly applicable Multiple other suitable algorithms exist and have been widely used
- IETF | Internet Engineering Task Force
Search the IETF email archive Much of the daily work of the IETF is conducted on electronic mailing lists A new mail archive tool realizing the requirements developed in RFC 6778 is now in use:
- How to Read an RFC - IETF
It’s no secret that plain text RFCs are difficult to read bordering on ugly, but things are about to improve; the RFC Editor is wrapping up a new RFC format, with much more pleasing presentation and the option for customisation
- RFC Editor - IETF
The RFC Series Consulting Editor (RSCE) is a senior technical publishing professional that provides expert advice to the RFC Production Center (RPC) and RSAB on how to implement established policies on an ongoing and operational basis
- Internet standards process - IETF
The basic formal definition of the IETF standards process is RFC 2026 (BCP 9) However, this document has been amended several times The intellectual property rules are now separate, in RFC 5378 (BCP 78) (rights in contributions) and RFC 8179 (BCP 79) (rights in technology)
- RFC 7636: Proof Key for Code Exchange by OAuth Public Clients
RFC 7636 OAUTH PKCE September 2015 [RFC6234] Eastlake 3rd, D and T Hansen, "US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)", RFC 6234, DOI 10 17487 RFC6234, May 2011, < http: www rfc-editor org info rfc6234 >
- RFC 1035 - Domain names - implementation and specification
STATUS OF THIS MEMO This RFC describes the details of the domain system and protocol, and assumes that the reader is familiar with the concepts discussed in a companion RFC, "Domain Names - Concepts and Facilities" [RFC-1034]
|
|
|