RFC 8256 on Requirements for Hitless MPLS Path Segment Monitoring

rfc-editor@rfc-editor.org Thu, 26 October 2017 21:49 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 8B57F13F608; Thu, 26 Oct 2017 14:49:37 -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 KCPaWiDEzmiZ; Thu, 26 Oct 2017 14:49:35 -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 C84CB1397F3; Thu, 26 Oct 2017 14:49:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5B218B81847; Thu, 26 Oct 2017 14:49:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8256 on Requirements for Hitless MPLS Path Segment Monitoring
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
Message-Id: <20171026214931.5B218B81847@rfc-editor.org>
Date: Thu, 26 Oct 2017 14:49:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QHh6pSpX5mNK7-4Ejuvys2FigwE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 26 Oct 2017 21:49:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8256

        Title:      Requirements for Hitless MPLS Path 
                    Segment Monitoring 
        Author:     A. D'Alessandro, 
                    L. Andersson,
                    S. Ueno, 
                    K. Arai,
                    Y. Koike
        Status:     Informational
        Stream:     IETF
        Date:       October 2017
        Mailbox:    alessandro.dalessandro@telecomitalia.it, 
                    loa@pi.nu, 
                    ueno@nttv6.jp,  
                    arai.kaoru@lab.ntt.co.jp, 
                    y.koike@vcd.nttbiz.com
        Pages:      16
        Characters: 34052 
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-temporal-hitless-psm-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8256

        DOI:        10.17487/RFC8256

One of the most important Operations, Administration, and Maintenance
(OAM) capabilities for transport-network operation is fault
localization.  An in-service, on-demand path segment monitoring
function of a transport path is indispensable, particularly when the
service monitoring function is activated only between endpoints.
However, the current segment monitoring approach defined for MPLS
(including the MPLS Transport Profile (MPLS-TP)) in RFC 6371
"Operations, Administration, and Maintenance Framework for MPLS-Based
Transport Networks" has drawbacks.  This document provides an
analysis of the existing MPLS-TP OAM mechanisms for the path segment
monitoring and provides requirements to guide the development of new
OAM tools to support Hitless Path Segment Monitoring (HPSM).

This document is a product of the Multiprotocol Label Switching 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