Inter-Chassis Communication Protocol for L2VPN PE Redundancy
draft-ietf-pwe3-iccp-08

The information below is for an old version of the document
Document Type Active Internet-Draft (pwe3 WG)
Last updated 2012-06-20
Replaces draft-martini-pwe3-iccp
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                             Luca Martini
Internet Draft                                               Samer Salam
Intended status: Standards Track                             Ali Sajassi
Expires: December 20, 2012                                         Cisco

Matthew Bocci                                          Satoru Matsushima
Alcatel-Lucent                                                  Softbank

Thomas Nadeau
CA Technologies
                                                           June 20, 2012

      Inter-Chassis Communication Protocol for L2VPN PE Redundancy

                      draft-ietf-pwe3-iccp-08.txt

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 20, 2012

Abstract

   This document specifies an inter-chassis communication protocol
   (ICCP) that enables Provider Edge (PE) device redundancy for Virtual
   Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS)
   applications. The protocol runs within a set of two or more PEs,
   forming a redundancy group, for the purpose of synchronizing data

Martini, et al.                                                 [Page 1]
Internet Draft        draft-ietf-pwe3-iccp-08.txt          June 20, 2012

   amongst the systems. It accommodates multi-chassis attachment circuit
   as well as pseudowire redundancy mechanisms.

Martini, et al.                                                 [Page 2]
Internet Draft        draft-ietf-pwe3-iccp-08.txt          June 20, 2012

Table of Contents

    1        Specification of Requirements  ........................   5
    2        Introduction  .........................................   5
    3        ICCP Overview  ........................................   5
    3.1      Redundancy Model & Topology  ..........................   5
    3.2      ICCP Interconnect Scenarios  ..........................   7
    3.2.1    Co-located Dedicated Interconnect  ....................   7
    3.2.2    Co-located Shared Interconnect  .......................   8
    3.2.3    Geo-redundant Dedicated Interconnect  .................   8
    3.2.4    Geo-redundant Shared Interconnect  ....................   9
    3.3      ICCP Requirements  ....................................  10
    4        ICC LDP Protocol Extension Specification  .............  12
    4.1      LDP ICCP Capability Advertisement  ....................  12
    4.2      RG Membership Management  .............................  13
    4.2.1    ICCP Connection State Machine  ........................  13
    4.3      Redundant Object Identification  ......................  16
    4.4      Application Connection Management  ....................  16
    4.4.1    Application Versioning  ...............................  17
    4.4.2    Application Connection State Machine  .................  18
    4.5      Application Data Transfer  ............................  21
    4.6      Dedicated Redundancy Group LDP session  ...............  21
    5        ICCP PE Node Failure Detection Mechanism  .............  22
    6        ICCP Message Formats  .................................  22
    6.1      Encoding ICC into LDP Messages   ......................  23
    6.1.1    ICC Header  ...........................................  23
    6.1.2    Message Encoding  .....................................  25
    6.1.3    ROID Encoding  ........................................  26
    6.2      RG Connect Message  ...................................  26
    6.2.1    ICC Sender Name TLV  ..................................  27
    6.3      RG Disconnect Message  ................................  28
    6.4      RG Notification Message  ..............................  30
    6.4.1    Notification Message TLVs  ............................  31
    6.5      RG Application Data Message  ..........................  34
    7        Application TLVs  .....................................  34
    7.1      Pseudowire Redundancy (PW-RED) Application TLVs  ......  34
Show full document text