RFC 8662 on Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels
rfc-editor@rfc-editor.org Fri, 06 December 2019 21:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054EB1201AA; Fri, 6 Dec 2019 13:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEW4uJ4ZQajl; Fri, 6 Dec 2019 13:53:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27B6C120800; Fri, 6 Dec 2019 13:53:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E1BCFF40742; Fri, 6 Dec 2019 13:53:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8662 on Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191206215329.E1BCFF40742@rfc-editor.org>
Date: Fri, 06 Dec 2019 13:53:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dvItjOGMEXa-5uhg2WfDTO9Dx2k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2019 21:53:40 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8662 Title: Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels Author: S. Kini, K. Kompella, S. Sivabalan, S. Litkowski, R. Shakir, J. Tantsura Status: Standards Track Stream: IETF Date: December 2019 Mailbox: sriganeshkini@gmail.com, kireeti@juniper.net, msiva@cisco.com, slitkows.ietf@gmail.com, robjs@google.com, jefftant.ietf@gmail.com Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-spring-entropy-label-12.txt URL: https://www.rfc-editor.org/info/rfc8662 DOI: 10.17487/RFC8662 Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions, called segments. Segment Routing can be applied to the Multiprotocol Label Switching (MPLS) data plane. Entropy labels (ELs) are used in MPLS to improve load-balancing. This document examines and describes how ELs are to be applied to Segment Routing MPLS. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC