[Idr] RFC 8814 on Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State
rfc-editor@rfc-editor.org Thu, 13 August 2020 04:57 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2463A16AA; Wed, 12 Aug 2020 21:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 duRudofpnTHM; Wed, 12 Aug 2020 21:57:09 -0700 (PDT)
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 764E63A16A9; Wed, 12 Aug 2020 21:57:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 94484F40721; Wed, 12 Aug 2020 21:57:02 -0700 (PDT)
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, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200813045702.94484F40721@rfc-editor.org>
Date: Wed, 12 Aug 2020 21:57:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TGMW-H6HUWdLj8xs_hlYd5WhHJI>
Subject: [Idr] RFC 8814 on Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2020 04:57:11 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8814 Title: Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State Author: J. Tantsura, U. Chunduri, K. Talaulikar, G. Mirsky, N. Triantafillis Status: Standards Track Stream: IETF Date: August 2020 Mailbox: jefftant.ietf@gmail.com, umac.ietf@gmail.com, ketant@cisco.com, gregimirsky@gmail.com, nikost@amazon.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-bgp-ls-segment-routing-msd-18.txt URL: https://www.rfc-editor.org/info/rfc8814 DOI: 10.17487/RFC8814 This document defines a way for a Border Gateway Protocol - Link State (BGP-LS) speaker to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular Segment Identifier (SID) stack can be supported in a given network. This document is a product of the Inter-Domain 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