GMPLS RSVP-TE extensions for OAM Configuration
draft-ietf-ccamp-oam-configuration-fwk-12

The information below is for an old version of the document
Document Type Active Internet-Draft (ccamp WG)
Last updated 2014-01-23 (latest revision 2014-01-13)
Replaces draft-takacs-ccamp-oam-configuration-fwk
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Deborah Brungard
Shepherd write-up Show (last changed 2013-10-25)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES. Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Adrian Farrel
Send notices to ccamp-chairs@tools.ietf.org, draft-ietf-ccamp-oam-configuration-fwk@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                          A. Takacs
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                D. Fedyk
Expires: July 16, 2014                                    Alcatel-Lucent
                                                                   J. He
                                                                  Huawei
                                                        January 12, 2014

             GMPLS RSVP-TE extensions for OAM Configuration
               draft-ietf-ccamp-oam-configuration-fwk-12

Abstract

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

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Takacs, et al.            Expires July 16, 2014                 [Page 1]
Internet-Draft       RSVP-TE based OAM Configuration        January 2014

   This Internet-Draft will expire on July 16, 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 restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  RSVP-TE based OAM Configuration . . . . . . . . . . . . . . .   6
     3.1.  Establishment of OAM Entities and Functions . . . . . . .   8
     3.2.  Adjustment of OAM Parameters  . . . . . . . . . . . . . .   9
     3.3.  Deleting OAM Entities . . . . . . . . . . . . . . . . . .  10
   4.  RSVP-TE Extensions  . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  LSP Attributes Flags  . . . . . . . . . . . . . . . . . .  11
     4.2.  OAM Configuration TLV . . . . . . . . . . . . . . . . . .  12
       4.2.1.  OAM Function Flags Sub-TLV  . . . . . . . . . . . . .  14
       4.2.2.  Technology Specific Sub-TLVs  . . . . . . . . . . . .  14
     4.3.  Administrative Status Information . . . . . . . . . . . .  15
     4.4.  Handling OAM Configuration Errors . . . . . . . . . . . .  15
     4.5.  Considerations on Point-to-Multipoint OAM Configuration .  16
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  ADMIN_STATUS Object Bit Flags . . . . . . . . . . . . . .  17
     5.2.  LSP Attributes Flags  . . . . . . . . . . . . . . . . . .  17
     5.3.  New LSP Attributes  . . . . . . . . . . . . . . . . . . .  18
     5.4.  RSVP Error Code . . . . . . . . . . . . . . . . . . . . .  18
     5.5.  RSVP-TE OAM Configuration Registry  . . . . . . . . . . .  19
       5.5.1.  OAM Types Sub-Registry  . . . . . . . . . . . . . . .  19
Show full document text