Tech-invite3GPPspecsSIPRFCs
898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100

reverse index of all RFC numbers

This is a comprehensive list of all RFC numbers in reverse order, by one hundred rows, starting from the highest issued RFC number. An issued RFC number links to a dedicated HTML page for this RFC. It can be a valid RFC (in this color), an obsoleted RFC (in this color) or also a first April RFC (in this color). Out of 8940 numbers, 7383 are for valid RFCs, 1239 for obsoleted RFCs, 61 for "first April" RFCs, and 257 are not issued. Regarding the status of the valid RFCs, the distribution is as follows: Internet Standard (109), Draft Standard (77), Proposed Standard (3134), Best Current Practice (252), Informational (2497), Experimental (417), Historic (180), unclassified early RFCs (717).
RFC 8940

to-Top


RFC 8939
RFC 8938
RFC 8937
RFC 8936
RFC 8935
RFC 8934
RFC 8933
RFC 8932
Best Current Practice: 232  34 p.
Recommendations for DNS Privacy Service Operators
RFC 8931
RFC 8930

to-Top


RFC 8929
RFC 8928
RFC 8927
Experimental  51 p.
JSON Type Definition
RFC 8926
RFC 8925
Proposed Standard  12 p.
IPv6-Only Preferred Option for DHCPv4
RFC 8924
RFC 8923
RFC 8922
RFC 8921
RFC 8920
Proposed Standard  19 p.
OSPF Application-Specific Link Attributes

to-Top


RFC 8919
Proposed Standard  20 p.
IS-IS Application-Specific Link Attributes
RFC 8918
Proposed Standard  8 p.
Invalid TLV Handling in IS-IS
RFC 8917
RFC 8916
RFC 8915
RFC 8914
Proposed Standard  13 p.
Extended DNS Errors
RFC 8913
RFC 8912
RFC 8911
RFC 8910

to-Top


RFC 8909
RFC 8908
Proposed Standard  11 p.
Captive Portal API
RFC 8907
RFC 8906
RFC 8905
Informational  12 p.
The 'payto' URI Scheme for Payments
RFC 8904
RFC 8903
RFC 8902
RFC 8901
Informational  13 p.
Multi-Signer DNSSEC Models
RFC 8900
Best Current Practice: 230  23 p.
IP Fragmentation Considered Fragile

to-Top


to-Top