[Lsr] RFC 8667 on IS-IS Extensions for Segment Routing
rfc-editor@rfc-editor.org Fri, 06 December 2019 22:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66CAE1200CD; Fri, 6 Dec 2019 14:34:19 -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 TQUyJ4Mvtit9; Fri, 6 Dec 2019 14:34:17 -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 713D512002F; Fri, 6 Dec 2019 14:34:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 591A6F406F6; Fri, 6 Dec 2019 14:34:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, lsr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191206223412.591A6F406F6@rfc-editor.org>
Date: Fri, 06 Dec 2019 14:34:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/7f_2W6t3isSLJyPaswGHy7X8cUc>
Subject: [Lsr] RFC 8667 on IS-IS Extensions for Segment Routing
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2019 22:34:19 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8667
Title: IS-IS Extensions for Segment Routing
Author: S. Previdi, Ed.,
L. Ginsberg, Ed.,
C. Filsfils,
A. Bashandy,
H. Gredler,
B. Decraene
Status: Standards Track
Stream: IETF
Date: December 2019
Mailbox: stefano@previdi.net,
ginsberg@cisco.com,
cfilsfil@cisco.com,
abashandy.ietf@gmail.com,
hannes@rtbrick.com,
bruno.decraene@orange.com
Pages: 28
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-isis-segment-routing-extensions-25.txt
URL: https://www.rfc-editor.org/info/rfc8667
DOI: 10.17487/RFC8667
Segment Routing (SR) allows for a flexible definition of end-to-end
paths within IGP topologies by encoding paths as sequences of
topological sub-paths, called "segments". These segments are
advertised by the link-state routing protocols (IS-IS and OSPF).
This document describes the IS-IS extensions that need to be
introduced for Segment Routing operating on an MPLS data plane.
This document is a product of the Link State Routing 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