RFC 8665 on OSPF Extensions for Segment Routing
rfc-editor@rfc-editor.org Fri, 06 December 2019 21:54 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 C73BD120A05; Fri, 6 Dec 2019 13:54:07 -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 2fpcKF1EIbHo; Fri, 6 Dec 2019 13:54:06 -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 8FC2B120AD3; Fri, 6 Dec 2019 13:53:55 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 75124F40737; Fri, 6 Dec 2019 13:53:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8665 on OSPF Extensions for Segment Routing
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: <20191206215350.75124F40737@rfc-editor.org>
Date: Fri, 06 Dec 2019 13:53:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ctkk16qoK1X0VU35trx6e9b9vEo>
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:54:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8665
Title: OSPF Extensions for Segment Routing
Author: P. Psenak, Ed.,
S. Previdi, Ed.,
C. Filsfils,
H. Gredler,
R. Shakir,
W. Henderickx,
J. Tantsura
Status: Standards Track
Stream: IETF
Date: December 2019
Mailbox: ppsenak@cisco.com,
stefano@previdi.net,
cfilsfil@cisco.com,
hannes@rtbrick.com,
robjs@google.com,
wim.henderickx@nokia.com,
jefftant.ietf@gmail.com
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ospf-segment-routing-extensions-27.txt
URL: https://www.rfc-editor.org/info/rfc8665
DOI: 10.17487/RFC8665
Segment Routing (SR) allows a flexible definition of end-to-end paths
within IGP topologies by encoding paths as sequences of topological
subpaths called "segments". These segments are advertised by the
link-state routing protocols (IS-IS and OSPF).
This document describes the OSPFv2 extensions required for Segment
Routing.
This document is a product of the Open Shortest Path First IGP 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