RFC 1812: Requirements for IP Version 4 Routers

This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK]

Read RFC 1812 on the RFC Editor

Outgoing relationships (67 related RFCs)

Showing 50 of 67 related RFCs.

Obsoletes, Informative reference — RFC 1009: Requirements for Internet gateways
Obsoletes — RFC 1716: Towards Requirements for IP Routers
Informative reference — RFC 791: Internet Protocol
Informative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Informative reference — RFC 1191: Path MTU discovery
Informative reference — RFC 1123: Requirements for Internet Hosts - Application and Support
Informative reference — RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
Informative reference — RFC 1519: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
Informative reference — RFC 896: Congestion Control in IP/TCP Internetworks
Informative reference — RFC 951: Bootstrap Protocol
Informative reference — RFC 1256: ICMP Router Discovery Messages
Informative reference — RFC 1332: The PPP Internet Protocol Control Protocol (IPCP)
Informative reference — RFC 904: Exterior Gateway Protocol formal specification
Informative reference — RFC 1071: Computing the Internet checksum
Informative reference — RFC 1108: U.S. Department of Defense Security Options for the Internet Protocol
Informative reference — RFC 1267: Border Gateway Protocol 3 (BGP-3)
Informative reference — RFC 1583: OSPF Version 2
Informative reference — RFC 1058: Routing Information Protocol
Informative reference — RFC 1349: Type of Service in the Internet Protocol Suite
Informative reference — RFC 1350: The TFTP Protocol (Revision 2)
Informative reference — RFC 1075: Distance Vector Multicast Routing Protocol
Informative reference — RFC 1229: Extensions to the generic-interface MIB
Informative reference — RFC 827: Exterior Gateway Protocol (EGP)
Informative reference — RFC 1334: PPP Authentication Protocols
Informative reference — RFC 893: Trailer encapsulations
Informative reference — RFC 1190: Experimental Internet Stream Protocol: Version 2 (ST-II)
Informative reference — RFC 817: Modularity and efficiency in protocol implementation
Informative reference — RFC 1772: Application of the Border Gateway Protocol in the Internet
Informative reference — RFC 1224: Techniques for managing asynchronously generated alerts
Informative reference — RFC 1253: OSPF Version 2 Management Information Base
Informative reference — RFC 888: "STUB" Exterior Gateway Protocol
Informative reference — RFC 796: Address mappings
Informative reference — RFC 1141: Incremental updating of the Internet checksum
Informative reference — RFC 1542: Clarifications and Extensions for the Bootstrap Protocol
Informative reference — RFC 1724: RIP Version 2 MIB Extension
Informative reference — RFC 1285: FDDI Management Information Base
Informative reference — RFC 1333: PPP Link Quality Monitoring
Informative reference — RFC 1381: SNMP MIB Extension for X.25 LAPB
Informative reference — RFC 1398: Definitions of Managed Objects for the Ethernet-Like Interface Types
Informative reference — RFC 1420: SNMP over IPX
Informative reference — RFC 975: Autonomous confederations
Informative reference — RFC 1016: Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID)
Informative reference — RFC 1038: Draft revised IP security option
Informative reference — RFC 1089: SNMP over Ethernet
Informative reference — RFC 1231: IEEE 802.5 Token Ring MIB
Informative reference — RFC 1254: Gateway Congestion Control Survey
Informative reference — RFC 1317: Definitions of Managed Objects for RS-232-like Hardware Devices
Informative reference — RFC 1382: SNMP MIB Extension for the X.25 Packet Layer
Informative reference — RFC 1512: FDDI Management Information Base
Informative reference — RFC 980: Protocol document order information

Incoming relationships (58 related RFCs)

Showing 50 of 58 related RFCs.

Updated by, Normatively referenced by — RFC 6633: Deprecation of ICMP Source Quench Messages
Updated by — RFC 2644: Changing the Default for Directed Broadcasts in Routers
Normatively referenced by — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
Normatively referenced by — RFC 7285: Application-Layer Traffic Optimization (ALTO) Protocol
Normatively referenced by — RFC 5971: GIST: General Internet Signalling Transport
Normatively referenced by — RFC 4884: Extended ICMP to Support Multi-Part Messages
Normatively referenced by — RFC 5927: ICMP Attacks against TCP
Normatively referenced by — RFC 4903: Multi-Link Subnet Issues
Normatively referenced by — RFC 8939: Deterministic Networking (DetNet) Data Plane: IP
Normatively referenced by — RFC 3360: Inappropriate TCP Resets Considered Harmful
Normatively referenced by — RFC 3871: Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure
Normatively referenced by — RFC 3684: Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)
Normatively referenced by — RFC 7126: Recommendations on Filtering of IPv4 Packets Containing IPv4 Options
Normatively referenced by — RFC 9570: Deprecating the Use of Router Alert in LSP Ping
Normatively referenced by — RFC 4450: Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents
Normatively referenced by — RFC 7789: Impact of BGP Filtering on Inter-Domain Routing Policies
Informatively referenced by — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informatively referenced by — RFC 2475: An Architecture for Differentiated Services
Informatively referenced by — RFC 2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
Informatively referenced by — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informatively referenced by — RFC 2003: IP Encapsulation within IP
Informatively referenced by — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informatively referenced by — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Informatively referenced by — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Informatively referenced by — RFC 3484: Default Address Selection for Internet Protocol version 6 (IPv6)
Informatively referenced by — RFC 5102: Information Model for IP Flow Information Export
Informatively referenced by — RFC 3819: Advice for Internet Subnetwork Designers
Informatively referenced by — RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports
Informatively referenced by — RFC 2453: RIP Version 2
Informatively referenced by — RFC 2522: Photuris: Session-Key Management Protocol
Informatively referenced by — RFC 6426: MPLS On-Demand Connectivity Verification and Route Tracing
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 3964: Security Considerations for 6to4
Informatively referenced by — RFC 2678: IPPM Metrics for Measuring Connectivity
Informatively referenced by — RFC 4782: Quick-Start for TCP and IP
Informatively referenced by — RFC 5837: Extending ICMP for Interface and Next-Hop Identification
Informatively referenced by — RFC 6192: Protecting the Router Control Plane
Informatively referenced by — RFC 2072: Router Renumbering Guide
Informatively referenced by — RFC 6540: IPv6 Support Required for All IP-Capable Nodes
Informatively referenced by — RFC 6820: Address Resolution Problems in Large Data Center Networks
Informatively referenced by — RFC 2521: ICMP Security Failures Messages
Informatively referenced by — RFC 5556: Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement
Informatively referenced by — RFC 6956: Forwarding and Control Element Separation (ForCES) Logical Function Block (LFB) Library
Informatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Informatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Informatively referenced by — RFC 2694: DNS extensions to Network Address Translators (DNS_ALG)
Informatively referenced by — RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links
Informatively referenced by — RFC 3512: Configuring Networks and Devices with Simple Network Management Protocol (SNMP)
Informatively referenced by — RFC 4562: MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network
Informatively referenced by — RFC 6814: Formally Deprecating Some IPv4 Options