RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs

Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do…

Read RFC 8126 on the RFC Editor

Outgoing relationships (45 related RFCs)

Obsoletes, Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 2026: The Internet Standards Process -- Revision 3
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 791: Internet Protocol
Informative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 6838: Media Type Specifications and Registration Procedures
Informative reference — RFC 3748: Extensible Authentication Protocol (EAP)
Informative reference — RFC 4340: Datagram Congestion Control Protocol (DCCP)
Informative reference — RFC 4288: Media Type Specifications and Registration Procedures
Informative reference — RFC 4422: Simple Authentication and Security Layer (SASL)
Informative reference — RFC 6275: Mobility Support in IPv6
Informative reference — RFC 3864: Registration Procedures for Message Header Fields
Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
Informative reference — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Informative reference — RFC 4727: Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
Informative reference — RFC 4446: IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
Informative reference — RFC 6709: Design Considerations for Protocol Extensions
Informative reference — RFC 2860: Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority
Informative reference — RFC 4520: Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)
Informative reference — RFC 1591: Domain Name System Structure and Delegation
Informative reference — RFC 5378: Rights Contributors Provide to the IETF Trust
Informative reference — RFC 7120: Early IANA Allocation of Standards Track Code Points
Informative reference — RFC 3575: IANA Considerations for RADIUS (Remote Authentication Dial In User Service)
Informative reference — RFC 6895: Domain Name System (DNS) IANA Considerations
Informative reference — RFC 5795: The RObust Header Compression (ROHC) Framework
Informative reference — RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
Informative reference — RFC 4283: Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
Informative reference — RFC 5771: IANA Guidelines for IPv4 Multicast Address Assignments
Informative reference — RFC 3968: The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)
Informative reference — RFC 4044: Fibre Channel Management MIB
Informative reference — RFC 4025: A Method for Storing IPsec Keying Material in DNS
Informative reference — RFC 5742: IESG Procedures for Handling of Independent and IRTF Stream Submissions
Informative reference — RFC 7595: Guidelines and Registration Procedures for URI Schemes
Informative reference — RFC 8141: Uniform Resource Names (URNs)
Informative reference — RFC 2939: Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types
Informative reference — RFC 4589: Location Types Registry
Informative reference — RFC 7564: PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
Informative reference — RFC 3942: Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options
Informative reference — RFC 6994: Shared Use of Experimental TCP Options
Informative reference — RFC 6230: Media Control Channel Framework
Informative reference — RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC
Informative reference — RFC 3228: IANA Considerations for IPv4 Internet Group Management Protocol (IGMP)
Informative reference — RFC 4169: Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2

Incoming relationships (259 related RFCs)

Showing 50 of 259 related RFCs.

Updated by, Normatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Normatively referenced by — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Normatively referenced by — RFC 8949: Concise Binary Object Representation (CBOR)
Normatively referenced by — RFC 9256: Segment Routing Policy Architecture
Normatively referenced by — RFC 8300: Network Service Header (NSH)
Normatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 8665: OSPF Extensions for Segment Routing
Normatively referenced by — RFC 8859: A Framework for Session Description Protocol (SDP) Attributes When Multiplexing
Normatively referenced by — RFC 8866: SDP: Session Description Protocol
Normatively referenced by — RFC 9260: Stream Control Transmission Protocol
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 8926: Geneve: Generic Network Virtualization Encapsulation
Normatively referenced by — RFC 8955: Dissemination of Flow Specification Rules
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 8214: Virtual Private Wire Service Support in Ethernet VPN
Normatively referenced by — RFC 8296: Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks
Normatively referenced by — RFC 8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
Normatively referenced by — RFC 8669: Segment Routing Prefix Segment Identifier Extensions for BGP
Normatively referenced by — RFC 9300: The Locator/ID Separation Protocol (LISP)
Normatively referenced by — RFC 8747: Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
Normatively referenced by — RFC 9010: Routing for RPL (Routing Protocol for Low-Power and Lossy Networks) Leaves
Normatively referenced by — RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 9301: Locator/ID Separation Protocol (LISP) Control Plane
Normatively referenced by — RFC 8554: Leighton-Micali Hash-Based Signatures
Normatively referenced by — RFC 8841: Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport
Normatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Normatively referenced by — RFC 8879: TLS Certificate Compression
Normatively referenced by — RFC 9176: Constrained RESTful Environments (CoRE) Resource Directory
Normatively referenced by — RFC 9513: OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)
Normatively referenced by — RFC 9830: Advertising Segment Routing Policies in BGP
Normatively referenced by — RFC 8210: The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
Normatively referenced by — RFC 8745: Path Computation Element Communication Protocol (PCEP) Extensions for Associating Working and Protection Label Switched Paths (LSPs) with Stateful PCE
Normatively referenced by — RFC 8846: An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
Normatively referenced by — RFC 8847: Protocol for Controlling Multiple Streams for Telepresence (CLUE)
Normatively referenced by — RFC 8972: Simple Two-Way Active Measurement Protocol Optional Extensions
Normatively referenced by — RFC 9209: The Proxy-Status HTTP Response Header Field
Normatively referenced by — RFC 9258: Importing External Pre-Shared Keys (PSKs) for TLS 1.3
Normatively referenced by — RFC 9528: Ephemeral Diffie-Hellman Over COSE (EDHOC)
Normatively referenced by — RFC 9613: Requirements for Solutions that Support MPLS Network Actions (MNAs)
Normatively referenced by — RFC 8208: BGPsec Algorithms, Key Formats, and Signature Formats
Normatively referenced by — RFC 8801: Discovering Provisioning Domain Names and Data
Normatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Normatively referenced by — RFC 8855: The Binary Floor Control Protocol (BFCP)
Normatively referenced by — RFC 8911: Registry for Performance Metrics
Normatively referenced by — RFC 8966: The Babel Routing Protocol
Normatively referenced by — RFC 9174: Delay-Tolerant Networking TCP Convergence-Layer Protocol Version 4
Normatively referenced by — RFC 9240: An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
Normatively referenced by — RFC 9297: HTTP Datagrams and the Capsule Protocol
Normatively referenced by — RFC 9457: Problem Details for HTTP APIs