[Pals] RFC 7727 on Spanning Tree Protocol (STP) Application of the Inter-Chassis Communication Protocol (ICCP)
rfc-editor@rfc-editor.org Sat, 23 January 2016 00:26 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C11F51B2DBB; Fri, 22 Jan 2016 16:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0L2MxIi5CdD; Fri, 22 Jan 2016 16:26:30 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 973A41B2DBA; Fri, 22 Jan 2016 16:26:30 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 80F2918045A; Fri, 22 Jan 2016 16:25:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160123002511.80F2918045A@rfc-editor.org>
Date: Fri, 22 Jan 2016 16:25:11 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/pals/NPXXlSH0KCqssAV9WViilnZ186Q>
Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pals] RFC 7727 on Spanning Tree Protocol (STP) Application of the Inter-Chassis Communication Protocol (ICCP)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2016 00:26:32 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7727
Title: Spanning Tree Protocol (STP) Application
of the Inter-Chassis Communication Protocol (ICCP)
Author: M. Zhang, H. Wen, J. Hu
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: zhangmingui@huawei.com,
wenhuafeng@huawei.com,
hujie@ctbri.com.cn
Pages: 25
Characters: 48135
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pwe3-iccp-stp-05.txt
URL: https://www.rfc-editor.org/info/rfc7727
DOI: http://dx.doi.org/10.17487/RFC7727
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.
This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC