RFC 6398: IP Router Alert Considerations and Usage
In plain English — editorial summary, not part of the RFC
The IP Router Alert Option is an IP option that alerts transit routers to more closely examine the contents of an IP packet. The Resource reSerVation Protocol (RSVP), Pragmatic General Multicast (PGM), the Internet Group Management Protocol (IGMP), Multicast Listener Discovery (MLD), Multicast Router Discovery (MRD), and General Internet Signaling Transport (GIST) are some of the protocols that make use of the IP Router Alert Option. This document discusses security aspects and usage guidelines around the use of the current IP Router Alert Option, thereby updating RFC 2113 and RFC 2711. Specifically, it provides recommendations against using the Router Alert in the end-to-end open Internet and identifies controlled environments where protocols depending on Router Alert can be used safely. It also provides recommendations about protection approaches for service providers. Finally, it provides brief guidelines for Router Alert implementation on routers. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6398
- Published
- October 2011
- Authors
- F. Le Faucheur
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- BCP168
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 6419Current Practices for Multiple-Interface HostsCurrent
November 2011
- RFC 6422Relay-Supplied DHCP OptionsCurrent
December 2011
- RFC 6434IPv6 Node RequirementsObsoleted
December 2011
- RFC 6436Rationale for Update to the IPv6 Flow Label SpecificationCurrent
November 2011
- RFC 6437IPv6 Flow Label SpecificationCurrent
November 2011
- RFC 6438Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in TunnelsCurrent
November 2011
- RFC 6355Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID)Current
August 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?