Inter-Chassis Communication Protocol for Layer 2 Virtual Private Network (L2VPN) Provider Edge (PE) Redundancy
RFC 7275
| Document | Type |
RFC - Proposed Standard
(June 2014; No errata)
Was draft-ietf-pwe3-iccp (pwe3 WG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-martini-pwe3-iccp | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Andrew Malis | ||
| Shepherd write-up | Show (last changed 2013-12-09) | ||
| IESG | IESG state | RFC 7275 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alia Atlas | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) L. Martini
Request for Comments: 7275 S. Salam
Category: Standards Track A. Sajassi
ISSN: 2070-1721 Cisco
M. Bocci
Alcatel-Lucent
S. Matsushima
Softbank Telecom
T. Nadeau
Brocade
June 2014
Inter-Chassis Communication Protocol for
Layer 2 Virtual Private Network (L2VPN) Provider Edge (PE) Redundancy
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
among the systems. It accommodates multi-chassis attachment circuit
redundancy mechanisms as well as pseudowire redundancy mechanisms.
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/rfc7275.
Martini, et al. Standards Track [Page 1]
RFC 7275 ICCP for L2VPN PE Redundancy 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 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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Martini, et al. Standards Track [Page 2]
RFC 7275 ICCP for L2VPN PE Redundancy June 2014
Table of Contents
1. Introduction ....................................................5
2. Specification of Requirements ...................................5
3. ICCP Overview ...................................................5
3.1. Redundancy Model and 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 .......................11
4.1. LDP ICCP Capability Advertisement .........................12
4.2. RG Membership Management ..................................12
4.2.1. ICCP Connection State Machine ......................13
4.3. Redundant Object Identification ...........................17
Show full document text