MPLS Network Action for Entropy

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 27 December 2024.¶

Copyright Notice

Copyright (c) 2024 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

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

2. The Entropy Action

• Name: Entropy Action¶

• Network Action Indication: The Entropy Action is opcode TBA1.¶

• Scope: The Entropy Action is valid in Hop-by-Hop (HBH) and Select scopes.¶

• In-Stack Data: The Entropy Action carries 20 bits of ancillary data, known as the Entropy Value.¶

• Processing: The semantics of the Entropy Value are identical to the semantics of the Entropy Label as found in [RFC6790], but the Entropy Value is not found in the Label field of the Label Stack Entry (LSE). While the RFC 6790 Entropy Label has some restrictions to avoid collisions with the reserved label space (0-15) [RFC3032], those restrictions are not necessary for the Entropy Value and do not apply. A forwarding node should incorporate the Entropy Value into its forwarding decision when the Entropy Action is evaluated.¶

• LSE Format: C. There is no additional data. The Network Action Length (NAL) field SHOULD be sent as zero.¶

• Interactions: None¶

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 "Multiprotocol Label Switching Architecture (MPLS)"/"MPLS Network Actions Parameters"/"Network Action Opcodes Registry" registry for the Entropy Action. The allocation should reference this document.¶

Authors' Addresses