Browse Prior Art Database

GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration (RFC7260)

IP.com Disclosure Number: IPCOM000237642D
Publication Date: 2014-Jul-01
Document File: 48 page(s) / 58K

Publishing Venue

The IP.com Prior Art Database

Related People

A. Takacs: AUTHOR [+3]

Abstract

GMPLS is designed as an out-of-band control plane supporting dynamic connection provisioning for any suitable data-plane technology, including spatial switching (e.g., incoming port or fiber to outgoing port or fiber); wavelength-division multiplexing (e.g., Dense Wavelength Division Multiplexing (DWDM)); time-division multiplexing (e.g., Synchronous Optical Networking and Synchronous Digital Hierarchy (SONET/SDH), G.709); and Ethernet Provider Backbone Bridging - Traffic Engineering (PBB-TE) and MPLS. In most of these technologies, there are Operations, Administration, and Maintenance (OAM) functions employed to monitor the health and performance of the connections and to trigger data plane (DP) recovery mechanisms. Similar to connection provisioning, OAM functions follow general principles but also have some technology-specific characteristics.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                         A. Takacs Request for Comments: 7260                                      Ericsson Category: Standards Track                                       D. Fedyk ISSN: 2070-1721                                  Hewlett-Packard Company                                                                    J. He                                                                   Huawei                                                                June 2014

                       GMPLS RSVP-TE Extensions for     Operations, Administration, and Maintenance (OAM) Configuration

Abstract

   Operations, Administration, and Maintenance (OAM) is an integral part    of transport connections; hence, it is required that OAM functions be    activated/deactivated in sync with connection commissioning/    decommissioning, in order to avoid spurious alarms and ensure    consistent operation.  In certain technologies, OAM entities are    inherently established once the connection is set up, while other    technologies require extra configuration to establish and configure    OAM entities.  This document specifies extensions to Resource    Reservation Protocol - Traffic Engineering (RSVP-TE) to support the    establishment and configuration of OAM entities along with Label    Switched Path signaling.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7260.

 Takacs, et al.               Standards Track                    [Page 1]
 RFC 7260             RSVP-TE-Based OAM Configuration           June 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restri...