RFC 3692: Assigning Experimental and Testing Numbers Considered Useful

When experimenting with or extending protocols, it is often necessary to use some sort of protocol number or constant in order to actually test or experiment…

Read RFC 3692 on the RFC Editor

Outgoing relationships (3 related RFCs)

Updates, Normative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
Informative reference — RFC 791: Internet Protocol

Incoming relationships (33 related RFCs)

Normatively referenced by — RFC 5586: MPLS Generic Associated Channel
Normatively referenced by — RFC 5120: M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)
Normatively referenced by — RFC 4915: Multi-Topology (MT) Routing in OSPF
Normatively referenced by — RFC 7153: IANA Registries for BGP Extended Communities
Normatively referenced by — RFC 6424: Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels
Normatively referenced by — RFC 5622: Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
Normatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Normatively referenced by — RFC 4775: Procedures for Protocol Extensions and Variations
Normatively referenced by — RFC 5494: IANA Allocation Guidelines for the Address Resolution Protocol (ARP)
Normatively referenced by — RFC 5719: Updated IANA Considerations for Diameter Command Code Allocations
Normatively referenced by — RFC 7557: Extension Mechanism for the Babel Routing Protocol
Normatively referenced by — RFC 7868: Cisco's Enhanced Interior Gateway Routing Protocol (EIGRP)
Normatively referenced by — RFC 7954: Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
Normatively referenced by — RFC 9288: Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit Routers
Informatively referenced by — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 3748: Extensible Authentication Protocol (EAP)
Informatively referenced by — RFC 5357: A Two-Way Active Measurement Protocol (TWAMP)
Informatively referenced by — RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
Informatively referenced by — RFC 5102: Information Model for IP Flow Information Export
Informatively referenced by — RFC 6709: Design Considerations for Protocol Extensions
Informatively referenced by — RFC 8300: Network Service Header (NSH)
Informatively referenced by — RFC 6994: Shared Use of Experimental TCP Options
Informatively referenced by — RFC 5320: The Subnetwork Encapsulation and Adaptation Layer (SEAL)
Informatively referenced by — RFC 6013: TCP Cookie Transactions (TCPCT)
Informatively referenced by — RFC 8170: Planning for Protocol Adoption and Subsequent Transitions
Informatively referenced by — RFC 9868: Transport Options for UDP
Informatively referenced by — RFC 6580: IANA Registries for the Remote Direct Data Placement (RDDP) Protocols
Informatively referenced by — RFC 9279: Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Message Extension
Informatively referenced by — RFC 4249: Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
Informatively referenced by — RFC 6559: A Reliable Transport Mechanism for PIM
Informatively referenced by — RFC 9184: BGP Extended Community Registries Update
Informatively referenced by — RFC 9305: Locator/ID Separation Protocol (LISP) Generic Protocol Extension
Informatively referenced by — RFC 9899: Extensions to the YANG Data Model for Access Control Lists (ACLs)