RFC 8339 on Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms
rfc-editor@rfc-editor.org Tue, 13 March 2018 22:40 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 35B4A12E055; Tue, 13 Mar 2018 15:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 3hmFFaMtRc29; Tue, 13 Mar 2018 15:40:56 -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 244B612E049; Tue, 13 Mar 2018 15:40:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0FDFBB81F36; Tue, 13 Mar 2018 15:40:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8339 on Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms
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, pals@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180313224033.0FDFBB81F36@rfc-editor.org>
Date: Tue, 13 Mar 2018 15:40:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/TKUFTgfCwQaInmPW_tOOgxCp7is>
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: Tue, 13 Mar 2018 22:41:00 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8339 Title: Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms Author: P. Jain, Ed., S. Boutros, S. Aldrin Status: Standards Track Stream: IETF Date: March 2018 Mailbox: paragj@cisco.com, sboutros@vmware.com, aldrin.ietf@gmail.com Pages: 10 Characters: 18964 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pals-p2mp-pw-lsp-ping-05.txt URL: https://www.rfc-editor.org/info/rfc8339 DOI: 10.17487/RFC8339 Label Switched Path (LSP) Ping is a widely deployed Operation, Administration, and Maintenance (OAM) mechanism in MPLS networks. This document describes a mechanism to verify connectivity of Point-to-Multipoint (P2MP) Pseudowires (PWs) using LSP Ping. This document is a product of the Pseudowire And LDP-enabled Services 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