| Internet-Draft | More Secure IPv6 Routing Header Processi | February 2022 |
| Smith | Expires 21 August 2022 | [Page] |
The original IPv6 Type 0 Routing Header has been deprecated due to the security risk of a packet forwarding loop being formed, by specifying a large sequence of alternating IPv6 node addresses to visit. This memo proposes a method to prevent these forwarding loops forming, allowing the IPv6 Type 0 Routing Header to be more securely and more safely used. The method may also be applicable to other unicast source routing scenarios.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 21 August 2022.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
[RFC5095] deprecated the IPv6 Type 0 Routing Header as it could be used to create a traffic loop, by specifying a large sequence of alternating IPv6 node addresses to visit. This traffic loop could consume large amounts of network capacity, causing congestion, and possibly a network capacity denial of service attack. (The packets caught in the forwarding loop would eventually be dropped as their hop-count field will eventually reach zero.)¶
This memo specifies a method of preventing these traffic loops occurring, which allows the IPv6 Type 0 to be more securely and more safely used. This method may also be applicable to other unicast source routing scenarios.¶
The fundamental problem with the type 0 RH, and other source Routing Headers that support multiple routing hops in general, is that packets can be made to travel back towards where they've come from. This then facilitates the first step of a packet being able to enter a forwarding loop.¶
Packets need to be prevented from travelling back towards where they've come from, which then prevents a forwarding loop from being formed.¶
The problem of packets going back towards where they've come from exists in multicast, and has been solved by performing a Reverse Path Forwarding (RPF) check on a packet as part of the multicast forwarding procedure.¶
This RPF check ensures that a packet does not leave via the router in direction back towards the packet's source address. This direction back towards the packet's source may be via the packet's ingress interface, or a different egress interface back towards the packet's source in an asymmetric routing scenario.¶
This memo specifies that a Reverse Path Forwarding Check is peformed when processing the IPv6 Type 0 Routing Header to prevent the packet going back towards its source.¶
[RFC3704], although describing RPF checks to prevent source IP address spoofing, provides good descriptions of the RPF checking process.¶
The following method is used to process IPv6 Type 0 Routing Headers while also preventing their packets from entering a forwarding loop.¶
Note that an implementation could perform the RPF check against the next address specified in the Type 0 Routing Header before updating the packet's Type 0 Routing Header and Destination Address field as a processing optimisation. If the RPF check fails in this case, the packet's Type 0 Routing Header and Destination Address will need to be updated so that it can then be correctly used as the message body for the ICMPv6 Destination Unreachable error message [RFC4443].¶
A new ICMPv6 Destination Unreachable error message is defined for a "Routing Header RPF Check Failed", Type 1, Code [IANA-TBD]. Processing of this error message is as per the general Destination Unreachable message processing specified in [RFC4443]. There is no special handling of this error message at the receiver.¶
This memo makes the reason for the IPv6 Type 0 Routing Header deprecation invalid. Consequently, [RFC8200] is updated to now specify the Type 0 Routing Header formerly specified in [RFC2460].¶
The method of preventing a packet or a frame from travelling back towards its origin when being forwarded can be applied to any unicast source routing scenario where a forwarding loop is possible.¶
Examples of where it could be applied are the IPv6 Segment Routing Header [RFC8754], Segment Routing over MPLS [RFC8660], the IPv6 Compressed Rouing Header [CRH] and IPv4 [RFC0791].¶
This memo addresses the primary security issue that caused the Type 0 Routing Header to be deprecated.¶
This memo does not address other security issues related to routing headers and source routing, such as using a routing header to bypass a security policy enforcement device, or untrusted packets with routing headers entering a routing header trusting domain. Other mitigations to these security issues, such as source address filtering at ingress to the local network, or packet authentication [RFC4302], need to be deployed.¶
IANA are requested to allocate a suitable Type 1 Destination Unreachable error code for "Routing Header RPF Check Failed".¶
Review and comments were provided by YOUR NAME HERE!¶
This memo was prepared using the xml2rfc tool.¶
draft-smith-6man-more-secure-rh-00, initial version, 2022-02-14¶
draft-smith-6man-more-secure-rh-01, 2022-02-17¶