Inter-Chassis Communication Protocol for L2VPN PE Redundancy
draft-ietf-pwe3-iccp-09
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (pwe3 WG) | |
| Last updated | 2013-01-31 (latest revision 2012-07-30) | ||
| Replaces | draft-martini-pwe3-iccp | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | None | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-pwe3-iccp-09.txt
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 amongst the systems. It accommodates multi-chassis attachment circuit as well as pseudowire redundancy mechanisms.
Authors
Luca Martini
(lmartini@cisco.com)
Samer Salam
(ssalam@cisco.com)
Ali Sajassi
(sajassi@cisco.com)
Satoru Matsushima
(satoru.matsushima@tm.softbank.co.jp)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)