RFC 7060 on Using LDP Multipoint Extensions on Targeted LDP Sessions
rfc-editor@rfc-editor.org Mon, 25 November 2013 23:09 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CEC1AE0B2; Mon, 25 Nov 2013 15:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.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] 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 5RstW_ljelVG; Mon, 25 Nov 2013 15:09:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E9BE41AE0AF; Mon, 25 Nov 2013 15:09:55 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F17BF75E017; Mon, 25 Nov 2013 15:09:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7060 on Using LDP Multipoint Extensions on Targeted LDP Sessions
From: rfc-editor@rfc-editor.org
Message-Id: <20131125230952.F17BF75E017@rfc-editor.org>
Date: Mon, 25 Nov 2013 15:09:52 -0800
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 25 Nov 2013 23:09:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7060
Title: Using LDP Multipoint Extensions on
Targeted LDP Sessions
Author: M. Napierala, E. Rosen,
IJ. Wijnands
Status: Standards Track
Stream: IETF
Date: November 2013
Mailbox: mnapierala@att.com,
erosen@cisco.com,
ice@cisco.com
Pages: 9
Characters: 19384
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-targeted-mldp-04.txt
URL: http://www.rfc-editor.org/rfc/rfc7060.txt
Label Distribution Protocol (LDP) can be used to set up
Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP)
Label Switched Paths. However, the specification for the Multipoint
Extensions to LDP presupposes that the two endpoints of an LDP session
are directly connected. The LDP base specification allows for the
case where the two endpoints of an LDP session are not directly
connected; such a session is known as a "Targeted LDP" session.
This document provides the specification for using the LDP Multipoint
Extensions over a Targeted LDP session.
This document is a product of the Multiprotocol Label Switching 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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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