[rfc-dist] RFC 8338 on Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDP
rfc-editor@rfc-editor.org Tue, 06 March 2018 23:33 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BDC1200FC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 6 Mar 2018 15:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable 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 iMDwf05PT3Q7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 6 Mar 2018 15:33:09 -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 49C19126CB6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 6 Mar 2018 15:33:09 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E58C7B80FFA; Tue, 6 Mar 2018 15:32:51 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 050ECB80FF8; Tue, 6 Mar 2018 15:32:51 -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: <20180306233251.050ECB80FF8@rfc-editor.org>
Date: Tue, 06 Mar 2018 15:32:51 -0800
Subject: [rfc-dist] RFC 8338 on Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDP
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8338
Title: Signaling Root-Initiated Point-to-Multipoint
Pseudowire Using LDP
Author: S. Boutros, Ed.,
S. Sivabalan, Ed.
Status: Standards Track
Stream: IETF
Date: March 2018
Mailbox: sboutros@vmware.com,
msiva@cisco.com
Pages: 20
Characters: 40885
Updates: RFC 7385
I-D Tag: draft-ietf-pals-p2mp-pw-04.txt
URL: https://www.rfc-editor.org/info/rfc8338
DOI: 10.17487/RFC8338
This document specifies a mechanism to signal Point-to-Multipoint
(P2MP) Pseudowire (PW) trees using LDP. Such a mechanism is suitable
for any Layer 2 VPN service requiring P2MP connectivity over an IP or
MPLS-enabled PSN. A P2MP PW established via the proposed mechanism
is root initiated. This document updates RFC 7385 by reassigning the
reserved value 0xFF to be the wildcard transport tunnel type.
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/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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org