Document Action: 'Operations, Administration and Maintenance Framework for MPLS-based Transport Networks' to Informational RFC (draft-ietf-mpls-tp-oam-framework-11.txt)
The IESG <iesg-secretary@ietf.org> Mon, 14 February 2011 19:46 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B5333A67DF; Mon, 14 Feb 2011 11:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level:
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id geYS2goNMzZx; Mon, 14 Feb 2011 11:46:55 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 604463A6AB9; Mon, 14 Feb 2011 11:46:55 -0800 (PST)
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: Document Action: 'Operations, Administration and Maintenance Framework for MPLS-based Transport Networks' to Informational RFC (draft-ietf-mpls-tp-oam-framework-11.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110214194655.10345.51750.idtracker@localhost>
Date: Mon, 14 Feb 2011 11:46:55 -0800
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Feb 2011 19:46:56 -0000
The IESG has approved the following document: - 'Operations, Administration and Maintenance Framework for MPLS-based Transport Networks' (draft-ietf-mpls-tp-oam-framework-11.txt) as an Informational RFC 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-oam-framework/ Technical Summary This MPLS-TP OAM Framework defines the mechanisms and procedures for alarm, fault, performance and protection-switching management for an MPLS based packet transport applications. Care has been taken to make sure the OAM for MPLS based packet transport networks is backwards compatible with existing MPLS OAM tools, New OAM mechanisms have only been defined when existing mechanisms are not sufficient to meet the MPLS-TP requirements. This document includes a comprehensive set of OAM procedures that satisfy the requirements mentioned above. The docement defines a set of functions that has great affinity with comparable functions in existing transport networks, e.g. SONET/SDH and OTN. The MPLS-TP OAM framework discusses mechanisms that are applicable to LSPs and/or (MS-)PWs. Co-routed and associated bidirectional p2p transport paths as well as unidirectional p2p and p2mp transport paths are within scope of the document. Working Group Summary Since the document is an output from the MPLS-TP project it is the joint output of several IETF working groups and Qustion 9, 10, 12 and 14 of ITU-T SG15. Document Quality The document is well reviewed in all the groups mentioned above Personnel Loa Andersson (loa@pi.nu) is the Document Shepherd Adrian Farrel (adrian.farrel@huawei.com) is the responsible AD