MPLS Network Actions for No Further Fast Reroute

Status of This Memo

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 24 April 2023.¶

Copyright Notice

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.¶

Table of Contents

1. Introduction

Protection switching for MPLS traffic was first introduced in [RFC4090]. Since then, Fast Reroute (FRR) has been successfully used in many MPLS networks to help ensure high availability in the face of failures.¶

If there are multiple failures in a network, there are circumstances where FRR, if applied multiple times, can result in sub-optimal behavior, such as forwarding loops. [I-D.kompella-mpls-nffrr] Thus, it is useful to indicate in the forwarding plane that the attached traffic should not be subjected to further FRR redirection.¶

This document describes a network actions for identifying such traffic to be used in conjunction with "MPLS Network Action (MNA) Header Encodings" [I-D.jags-mpls-mna-hdr] as part of the MPLS Network Action architecture. [I-D.ietf-mpls-miad-mna-requirements] [I-D.ietf-mpls-mna-fwk]¶

2. The No Further Fast Reroute (NFFRR) Action

• Name: No Further Fast Reroute Action¶
• Network Action Indication: The No Further Fast Reroute Action indication is bit postion TBA1.¶
• Scope: The No Further Fast Reroute Action is valid in Hop-By-Hop and Select scopes.¶
• In-Stack Data: None.¶
• Post-Stack Data: None.¶

Packets that indicate the NFFRR action should not be subject to further FRR operations.¶

3. Security Considerations

The forwarding plane is insecure. If an adversary can affect the forwarding plane, then they can inject data, remove data, corrupt data, or modify data. MNA additionally allows an adversary to make packets perform arbitrary network actions.¶

Link-level security mechanisms can help mitigate some on-link attacks, but does nothing to preclude hostile nodes.¶

4. IANA Considerations

This document requests that IANA allocate a bit position (TBA1) from the MPLS "In-Stack MPLS Network Action Indicator Flags" registry for the No Further Fast Reroute Action. The allocation should reference this document.¶

Authors' Addresses