Internet-Draft MNA Entropy October 2022
Li & Drake Expires 20 April 2023 [Page]
MPLS Working Group
Intended Status:
T. Li
Juniper Networks
J. Drake
Juniper Networks

MPLS Network Action for Entropy


Load balancing is a powerful tool for engineering traffic across a network and has been successfully used in MPLS as described in "The Use of Entropy Labels in MPLS Forwarding". With the emergence of MPLS Network Actions (MNA), there is signficant benefit in being able to invoke the same load balancing capabilities within the more general MNA infrastructure.

This document describes a network action for entropy to be used in conjunction with [I-D.jags-mpls-mna-hdr].

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

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 20 April 2023.

Table of Contents

1. Introduction

Load balancing is a powerful tool for engineering traffic across a network. The use of entropy labels within MPLS was first described in [RFC6790] and has been deployed succesfully in multiple MPLS networks.

With the emergence of MPLS Network Actions [I-D.ietf-mpls-miad-mna-requirements] [I-D.ietf-mpls-mna-fwk], there is a significant benefit to being able to describe entropy as a network action. Without this, a packet that required load balancing and network actions would need to deal with the complexity and overhead of both the MNA and Entropy Labels in the label stack. By defining an action for Entropy within the MNA infrastructure, overhead and complexity can be reduced.

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 Entropy Action

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 codepoint (TBA1) from the MPLS "HBH and Select In-Stack MPLS Network Action Indicator Opcodes" from the "IETF Review" range for the Entropy Action. The allocation should reference this document.

5. Normative References

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-requirements-00, , <>.
Andersson, L., Bryant, S., Bocci, M., and T. Li, "MPLS Network Actions Framework", Work in Progress, Internet-Draft, draft-ietf-mpls-mna-fwk-01, , <>.
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, , <>.
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <>.
Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, DOI 10.17487/RFC3032, , <>.
Kompella, K., Drake, J., Amante, S., Henderickx, W., and L. Yong, "The Use of Entropy Labels in MPLS Forwarding", RFC 6790, DOI 10.17487/RFC6790, , <>.
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <>.

Authors' Addresses

Tony Li
Juniper Networks
John Drake
Juniper Networks