RFC 5095: Deprecation of Type 0 Routing Headers in IPv6
In plain English — editorial summary, not part of the RFC
The functionality provided by IPv6's Type 0 Routing Header can be exploited in order to achieve traffic amplification over a remote path for the purposes of generating denial-of-service traffic. This document updates the IPv6 specification to deprecate the use of IPv6 Type 0 Routing Headers, in light of this security concern. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5095
- Published
- December 2007
- Authors
- J. Abley; P. Savola; G. Neville-Neil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5094Mobile IPv6 Vendor Specific OptionCurrent
December 2007
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 5107DHCP Server Identifier Override SuboptionCurrent
February 2008
- RFC 5113Network Discovery and Selection ProblemCurrent
January 2008
- RFC 5075IPv6 Router Advertisement Flags OptionObsoleted
November 2007
- RFC 5072IP Version 6 over PPPUpdated
September 2007
- RFC 5071Dynamic Host Configuration Protocol Options Used by PXELINUXCurrent
December 2007
- RFC 5121Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 NetworksUpdated
February 2008
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?