RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words

RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE…

Read RFC 8174 on the RFC Editor

Outgoing relationships (1 related RFC)

Updates, Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels

Incoming relationships (933 related RFCs)

Showing 50 of 933 related RFCs.

Normatively referenced by — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Normatively referenced by — RFC 8341: Network Configuration Access Control Model
Normatively referenced by — RFC 8342: Network Management Datastore Architecture (NMDA)
Normatively referenced by — RFC 8949: Concise Binary Object Representation (CBOR)
Normatively referenced by — RFC 9147: The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
Normatively referenced by — RFC 8343: A YANG Data Model for Interface Management
Normatively referenced by — RFC 8349: A YANG Data Model for Routing Management (NMDA Version)
Normatively referenced by — RFC 8754: IPv6 Segment Routing Header (SRH)
Normatively referenced by — RFC 9256: Segment Routing Policy Architecture
Normatively referenced by — RFC 9293: Transmission Control Protocol (TCP)
Normatively referenced by — RFC 8660: Segment Routing with the MPLS Data Plane
Normatively referenced by — RFC 8392: CBOR Web Token (CWT)
Normatively referenced by — RFC 8664: Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
Normatively referenced by — RFC 8843: Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
Normatively referenced by — RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports
Normatively referenced by — RFC 8152: CBOR Object Signing and Encryption (COSE)
Normatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 8305: Happy Eyeballs Version 2: Better Connectivity Using Concurrency
Normatively referenced by — RFC 8365: A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)
Normatively referenced by — RFC 9052: CBOR Object Signing and Encryption (COSE): Structures and Process
Normatively referenced by — RFC 8277: Using BGP to Bind MPLS Labels to Address Prefixes
Normatively referenced by — RFC 8362: OSPFv3 Link State Advertisement (LSA) Extensibility
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 8177: YANG Data Model for Key Chains
Normatively referenced by — RFC 8345: A YANG Data Model for Network Topologies
Normatively referenced by — RFC 8866: SDP: Session Description Protocol
Normatively referenced by — RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Normatively referenced by — RFC 8667: IS-IS Extensions for Segment Routing
Normatively referenced by — RFC 8684: TCP Extensions for Multipath Operation with Multiple Addresses
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 8226: Secure Telephone Identity Credentials: Certificates
Normatively referenced by — RFC 8791: YANG Data Structure Extensions
Normatively referenced by — RFC 8926: Geneve: Generic Network Virtualization Encapsulation
Normatively referenced by — RFC 8939: Deterministic Networking (DetNet) Data Plane: IP
Normatively referenced by — RFC 8941: Structured Field Values for HTTP
Normatively referenced by — RFC 8955: Dissemination of Flow Specification Rules
Normatively referenced by — RFC 9053: CBOR Object Signing and Encryption (COSE): Initial Algorithms
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Normatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Normatively referenced by — RFC 8214: Virtual Private Wire Service Support in Ethernet VPN
Normatively referenced by — RFC 8669: Segment Routing Prefix Segment Identifier Extensions for BGP
Normatively referenced by — RFC 8725: JSON Web Token Best Current Practices
Normatively referenced by — RFC 8827: WebRTC Security Architecture
Normatively referenced by — RFC 8839: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
Normatively referenced by — RFC 8900: IP Fragmentation Considered Fragile