Protocol Action: 'MPLS Transport Profile lock Instruct and Loopback Functions' to Proposed Standard (draft-ietf-mpls-tp-li-lb-08.txt)
The IESG <iesg-secretary@ietf.org> Tue, 25 October 2011 22:59 UTC
Return-Path: <iesg-secretary@ietf.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 662D121F8B2A; Tue, 25 Oct 2011 15:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level:
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPJhmLqCouNp; Tue, 25 Oct 2011 15:59:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D520621F8B2D; Tue, 25 Oct 2011 15:59:38 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'MPLS Transport Profile lock Instruct and Loopback Functions' to Proposed Standard (draft-ietf-mpls-tp-li-lb-08.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.61
Message-ID: <20111025225938.14470.50705.idtracker@ietfa.amsl.com>
Date: Tue, 25 Oct 2011 15:59:38 -0700
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Oct 2011 22:59:39 -0000
The IESG has approved the following document: - 'MPLS Transport Profile lock Instruct and Loopback Functions' (draft-ietf-mpls-tp-li-lb-08.txt) as a Proposed Standard This document is the product of the Multiprotocol Label Switching Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-li-lb/ Technical Summary Two useful Operations, Administration, and Maintenance (OAM) functions in a transport network are "lock" and "loopback". The lock function enables an operator to lock a transport path such that it does not carry client traffic, but can continue to carry OAM messages and may carry test traffic. The loopback function allows an operator to set a specific node on the transport path into loopback mode such that it returns all received data. This document specifies the lock function for MPLS networks and describes how the loopback function operates in MPLS networks. Working Group Summary This document is a MPLS working group document, and part of the joint IETF - ITU.T MPLS-TP project. It has been reviewed in both organizations and there is a solid support for the document. The following IPR Declarations may be related to this I-D: http://datatracker.ietf.org/ipr/1439/ The IPD disclosure was noted on the WG mailing list and in the IETF last call. No concerns were raised. Document Quality The document is well reviewed in the MPLS and PWE3 working groups, the ITU-T and the MPLS-TP project. Several implementations are under way or planned. This document updates RFC 6371 section 7.1.1. This document contains a "downref" to RFC 6371, the Informational RFC that it updates. The downref was declared in the IETF last call. Personnel Loa Andersson (loa@pi.nu) is the document shepherd Adrian Farrel (adrian@olddog.co.uk) is the Responsible AS RFC Editor Note Section 1 bullet 2 s/an bidirectional/a bidirectional/