STD 84, RFC 8077 on Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)
rfc-editor@rfc-editor.org Thu, 02 February 2017 22:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A7B12943E; Thu, 2 Feb 2017 14:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 o7KOYoKHfccz; Thu, 2 Feb 2017 14:56:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAA7A129421; Thu, 2 Feb 2017 14:56:42 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C5931B81022; Thu, 2 Feb 2017 14:56:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 84, RFC 8077 on Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170202225642.C5931B81022@rfc-editor.org>
Date: Thu, 02 Feb 2017 14:56:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vSwQqTGyq3hioVyg4ISF-akOm1Q>
Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 22:56:44 -0000
A new Request for Comments is now available in online RFC libraries.
STD 84
RFC 8077
Title: Pseudowire Setup and Maintenance Using
the Label Distribution Protocol (LDP)
Author: L. Martini, Ed.,
G. Heron, Ed.
Status: Standards Track
Stream: IETF
Date: February 2017
Mailbox: lmartini@monoski.com,
giheron@cisco.com
Pages: 35
Characters: 80972
Obsoletes: RFC 4447, RFC 6723
See Also: STD 84
I-D Tag: draft-ietf-pals-rfc4447bis-05.txt
URL: https://www.rfc-editor.org/info/rfc8077
DOI: 10.17487/RFC8077
Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode,
and Ethernet) can be emulated over an MPLS backbone by
encapsulating the Layer 2 Protocol Data Units (PDUs) and then
transmitting them over pseudowires (PWs). It is also possible to use
pseudowires to provide low-rate Time-Division Multiplexed and
Synchronous Optical NETworking circuit emulation over an MPLS-enabled
network. This document specifies a protocol for establishing and
maintaining the pseudowires, using extensions to the Label
Distribution Protocol (LDP). Procedures for encapsulating Layer 2
PDUs are specified in other documents.
This document is a rewrite of RFC 4447 for publication as an
Internet Standard.
This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.
This is now an Internet 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/retrieve/bulk
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