[mpls] RFC 7876 on UDP Return Path for Packet Loss and Delay Measurement for MPLS Networks
rfc-editor@rfc-editor.org Wed, 27 July 2016 00:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8528D12DA84; Tue, 26 Jul 2016 17:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 Cuna2DOpgQd4; Tue, 26 Jul 2016 17:45:28 -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 03ECE12D1E3; Tue, 26 Jul 2016 17:45:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D99B1B811B1; Tue, 26 Jul 2016 17:45:27 -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
Message-Id: <20160727004527.D99B1B811B1@rfc-editor.org>
Date: Tue, 26 Jul 2016 17:45:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/69_aOAi0_fNpfZ06-Fc9tu2rJOw>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 7876 on UDP Return Path for Packet Loss and Delay Measurement for MPLS Networks
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2016 00:45:29 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7876
Title: UDP Return Path for Packet
Loss and Delay Measurement for MPLS
Networks
Author: S. Bryant, S. Sivabalan,
S. Soni
Status: Standards Track
Stream: IETF
Date: July 2016
Mailbox: stewart.bryant@gmail.com,
msiva@cisco.com,
sagsoni@cisco.com
Pages: 10
Characters: 21092
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-rfc6374-udp-return-path-05.txt
URL: https://www.rfc-editor.org/info/rfc7876
DOI: http://dx.doi.org/10.17487/RFC7876
RFC 6374 defines a protocol for Packet Loss and Delay Measurement for
MPLS networks (MPLS-PLDM). This document specifies the procedures to
be used when sending and processing out-of-band MPLS performance
management Responses over an UDP/IP return path.
This document is a product of the Multiprotocol Label Switching 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