RFC 7727: Spanning Tree Protocol (STP) Application of the Inter-Chassis Communication Protocol (ICCP)
In plain English — editorial summary, not part of the RFC
The Inter-Chassis Communication Protocol (ICCP) supports an inter-chassis redundancy mechanism that is used to support high network availability. In this document, Provider Edge (PE) devices in a Redundancy Group (RG) running ICCP are used to offer multihomed connectivity to Spanning Tree Protocol (STP) networks to improve availability of the STP networks. The ICCP TLVs and usage for the ICCP STP application are defined.
Document record
- Document ID
- RFC7727
- Published
- January 2016
- Authors
- M. Zhang; H. Wen; J. Hu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7726Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs)Current
January 2016
- RFC 7730Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
January 2016
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7722Multi-Topology Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
December 2015
- RFC 7732Forwarder Policy for Multicast with Admin-Local Scope in the Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 7734Support for Shortest Path Bridging MAC Mode over Ethernet VPN (EVPN)Current
January 2016
- RFC 7737Label Switched Path (LSP) Ping and Traceroute Reply Mode SimplificationCurrent
January 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?