[spring] RFC 8403 on A Scalable and Topology-Aware MPLS Data-Plane Monitoring System
rfc-editor@rfc-editor.org Tue, 24 July 2018 22:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB1413123C; Tue, 24 Jul 2018 15:45:59 -0700 (PDT)
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 R5ZZC0KZY1A5; Tue, 24 Jul 2018 15:45:57 -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 C80E113121C; Tue, 24 Jul 2018 15:45:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 612CEB81643; Tue, 24 Jul 2018 15:45:49 -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, spring@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180724224549.612CEB81643@rfc-editor.org>
Date: Tue, 24 Jul 2018 15:45:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/mNrkaif231hOhN71blkpwVzliBg>
Subject: [spring] RFC 8403 on A Scalable and Topology-Aware MPLS Data-Plane Monitoring System
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 22:46:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8403
Title: A Scalable and Topology-Aware MPLS
Data-Plane Monitoring System
Author: R. Geib, Ed.,
C. Filsfils,
C. Pignataro, Ed.,
N. Kumar
Status: Informational
Stream: IETF
Date: July 2018
Mailbox: Ruediger.Geib@telekom.de,
cfilsfil@cisco.com,
cpignata@cisco.com,
naikumar@cisco.com
Pages: 19
Characters: 45212
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-spring-oam-usecase-10.txt
URL: https://www.rfc-editor.org/info/rfc8403
DOI: 10.17487/RFC8403
This document describes features of an MPLS path monitoring system
and related use cases. Segment-based routing enables a scalable and
simple method to monitor data-plane liveliness of the complete set of
paths belonging to a single domain. The MPLS monitoring system adds
features to the traditional MPLS ping and Label Switched Path (LSP)
trace, in a very complementary way. MPLS topology awareness reduces
management and control-plane involvement of Operations,
Administration, and Maintenance (OAM) measurements while enabling new
OAM features.
This document is a product of the Source Packet Routing in Networking Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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