datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Pseudowire Status for Static Pseudowires
draft-ietf-pwe3-static-pw-status-10

RFC
Document Stream: IETF
Last updated: 2011-11-15
Replaces: draft-martini-pwe3-static-pw-status
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: Submitted to IESG for Publication (pwe3)
Document shepherd:Andrew Malis
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6478
IANA Action State: RFC-Ed-Ack 
Responsible AD: Stewart Bryant
IESG Note: Andy Malis (amalis@gmail.com) is the document shepherd.
Send notices to: pwe3-chairs@tools.ietf.org, draft-ietf-pwe3-static-pw-status@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-pwe3-static-pw-status.

Abstract:
This document specifies a mechanism to signal Pseudowire (PW) status messages using a PW associated channel (ACh). Such a mechanism is suitable for use where no PW dynamic control plane exits, known as static PWs, or where a Terminating Provider Edge (T-PE) needs to send a PW status message directly to a far-end T-PE. The mechanism allows PW Operations, Administration, and Maintenance (OAM) message mapping and PW redundancy to operate on static PWs. This document also updates RFC 5885 in the case when Bi-directional Forwarding Detection (BFD) is used to convey PW status-signaling information. [STANDARDS-TRACK]

Authors:
Luca Martini <lmartini@cisco.com>
George Swallow <swallow@cisco.com>
Giles Heron <giheron@cisco.com>
Matthew Bocci <matthew.bocci@alcatel-lucent.co.uk>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)