MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
draft-ietf-mpls-gach-adv-07

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2013-04-27 (latest revision 2013-04-26)
Replaces draft-fbb-mpls-gach-adv
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Doc Shepherd Follow-up Underway
Consensus Yes
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2012-12-14)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES. Needs 3 more YES or NO OBJECTION positions to pass.
Responsible AD Adrian Farrel
IESG note Loa Andersson (loa@pi.nu) is the document shepherd
Send notices to mpls-chairs@tools.ietf.org, draft-ietf-mpls-gach-adv@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
MPLS                                                            D. Frost
Internet-Draft                                                 S. Bryant
Intended status: Standards Track                           Cisco Systems
Expires: October 29, 2013                                       M. Bocci
                                                          Alcatel-Lucent
                                                          April 27, 2013

     MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
                      draft-ietf-mpls-gach-adv-07

Abstract

   The MPLS Generic Associated Channel (G-ACh) provides an auxiliary
   logical data channel associated with a Label Switched Path (LSP), a
   pseudowire, or a section (link) over which a variety of protocols may
   flow.  These protocols are commonly used to provide Operations,
   Administration, and Maintenance (OAM) mechanisms associated with the
   primary data channel.  This document specifies simple procedures by
   which an endpoint of an LSP, pseudowire, or section may inform the
   other endpoints of its capabilities and configuration parameters, or
   other application-specific information.  This information may then be
   used by the receiver to validate or adjust its local configuration,
   and by the network operator for diagnostic purposes.

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."

   This Internet-Draft will expire on October 29, 2013.

Copyright Notice

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

Frost, et al.           Expires October 29, 2013                [Page 1]
Internet-Draft     MPLS G-ACh Advertisement Protocol          April 2013

   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
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Message Format  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  GAP Message Format  . . . . . . . . . . . . . . . . . . .   7
     3.2.  Applications Data Block . . . . . . . . . . . . . . . . .   7
     3.3.  TLV Object Format . . . . . . . . . . . . . . . . . . . .   8
   4.  G-ACh Advertisement Protocol TLVs . . . . . . . . . . . . . .   9
     4.1.  Source Address TLV  . . . . . . . . . . . . . . . . . . .   9
     4.2.  GAP Request TLV . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  GAP Flush TLV . . . . . . . . . . . . . . . . . . . . . .  11
     4.4.  GAP Suppress TLV  . . . . . . . . . . . . . . . . . . . .  11
     4.5.  GAP Authentication TLV  . . . . . . . . . . . . . . . . .  12
   5.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  Message Transmission  . . . . . . . . . . . . . . . . . .  13
     5.2.  Message Reception . . . . . . . . . . . . . . . . . . . .  14
   6.  Message Authentication  . . . . . . . . . . . . . . . . . . .  15
     6.1.  Authentication Key Identifiers  . . . . . . . . . . . . .  15
     6.2.  Authentication Process  . . . . . . . . . . . . . . . . .  16
     6.3.  MAC Computation . . . . . . . . . . . . . . . . . . . . .  16
   7.  Link-Layer Considerations . . . . . . . . . . . . . . . . . .  17
   8.  Managability Considerations . . . . . . . . . . . . . . . . .  17
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     10.1.  Associated Channel Type Allocation . . . . . . . . . . .  18
Show full document text