Internet DRAFT - draft-li-mpls-mna-nffrr
draft-li-mpls-mna-nffrr
MPLS Working Group T. Saad
Internet-Draft Cisco Systems
Intended status: Informational I. Meilik
Expires: 24 April 2023 Broadcom
T. Li
J. Drake
Juniper Networks
21 October 2022
MPLS Network Actions for No Further Fast Reroute
draft-li-mpls-mna-nffrr-01
Abstract
Protection switching for MPLS traffic was first introduced in "Fast
Reroute Extensions to RSVP-TE for LSP Tunnels". 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. 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 action for identifying such traffic
to be used in conjunction with "MPLS Network Action (MNA) Header
Encodings".
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.
Saad, et al. Expires 24 April 2023 [Page 1]
Internet-Draft MNA NFFRR October 2022
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirement Language . . . . . . . . . . . . . . . . . . 3
2. The No Further Fast Reroute (NFFRR) Action . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Normative References . . . . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
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]
Saad, et al. Expires 24 April 2023 [Page 2]
Internet-Draft MNA NFFRR October 2022
1.1. Requirement Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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.
5. Normative References
[I-D.ietf-mpls-miad-mna-requirements]
Bocci, M. and S. Bryant, "Requirements for MPLS Network
Action Indicators and MPLS Ancillary Data", Work in
Progress, Internet-Draft, draft-ietf-mpls-miad-mna-
Saad, et al. Expires 24 April 2023 [Page 3]
Internet-Draft MNA NFFRR October 2022
requirements-00, 5 May 2022,
<https://www.ietf.org/archive/id/draft-ietf-mpls-miad-mna-
requirements-00.txt>.
[I-D.ietf-mpls-mna-fwk]
Andersson, L., Bryant, S., Bocci, M., and T. Li, "MPLS
Network Actions Framework", Work in Progress, Internet-
Draft, draft-ietf-mpls-mna-fwk-01, 8 September 2022,
<https://www.ietf.org/archive/id/draft-ietf-mpls-mna-fwk-
01.txt>.
[I-D.jags-mpls-mna-hdr]
Rajamanickam, J., Gandhi, R., Zigler, R., Song, H., and K.
Kompella, "MPLS Network Action (MNA) Header Encodings",
Work in Progress, Internet-Draft, draft-jags-mpls-mna-hdr-
02, 10 October 2022, <https://www.ietf.org/archive/id/
draft-jags-mpls-mna-hdr-02.txt>.
[I-D.kompella-mpls-nffrr]
Kompella, K. and W. Lin, "No Further Fast Reroute", Work
in Progress, Internet-Draft, draft-kompella-mpls-nffrr-03,
8 July 2022, <https://www.ietf.org/archive/id/draft-
kompella-mpls-nffrr-03.txt>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast
Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
DOI 10.17487/RFC4090, May 2005,
<https://www.rfc-editor.org/info/rfc4090>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Authors' Addresses
Tarek Saad
Cisco Systems
Email: tsaad.net@gmail.com
Israel Meilik
Broadcom
Email: israel.meilik@broadcom.com
Saad, et al. Expires 24 April 2023 [Page 4]
Internet-Draft MNA NFFRR October 2022
Tony Li
Juniper Networks
Email: tony.li@tony.li
John Drake
Juniper Networks
Email: jdrake@juniper.net
Saad, et al. Expires 24 April 2023 [Page 5]
