draft-ietf-mpls-targeted-mldp-01.txt   draft-ietf-mpls-targeted-mldp-02.txt 
MPLS Working Group Maria Napierala MPLS Working Group Maria Napierala
Internet Draft AT&T Internet Draft AT&T
Intended Status: Standards Track Intended Status: Standards Track
Expires: July 28, 2013 Eric C. Rosen Expires: December 24, 2013 Eric C. Rosen
IJsbrands Wijnands IJsbrands Wijnands
Cisco Systems, Inc. Cisco Systems, Inc.
January 28, 2013 June 24, 2013
Using LDP Multipoint Extensions on Targeted LDP Sessions Using LDP Multipoint Extensions on Targeted LDP Sessions
draft-ietf-mpls-targeted-mldp-01.txt draft-ietf-mpls-targeted-mldp-02.txt
Abstract Abstract
Label Distribution Protocol (LDP) can be used to set up As specified in RFC 6388, Label Distribution Protocol (LDP) can be
Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) Label used to set up Point-to-Multipoint (P2MP) and Multipoint-to-
Switched Paths. The existing specification for this functionality Multipoint (MP2MP) Label Switched Paths. However, RFC 6388
assumes that a pair of LDP neighbors are directly connected. presupposes that the two endpoints of an LDP session are directly
However, the LDP base specification allows for the case where a pair connected. The LDP base specification (RFC 5036) allows for the case
of LDP neighbors are not directly connected; the LDP session between where the two endpoints of an LDP session are not directly connected;
such a pair of neighbors is known as a "Targeted LDP" session. This such a session is known as a "Targeted LDP" session. This document
document provides the specification for using the LDP P2MP/MP2MP provides the specification for using the LDP P2MP/MP2MP extensions
extensions over a Targeted LDP session. over a Targeted LDP session.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 3, line 15 skipping to change at page 3, line 15
1. Introduction 1. Introduction
1.1. Targeted mLDP 1.1. Targeted mLDP
The Label Distribution Protocol (LDP) extensions for setting up The Label Distribution Protocol (LDP) extensions for setting up
Point-to-MultiPoint (P2MP) Label Switched Paths (LSPs) and Point-to-MultiPoint (P2MP) Label Switched Paths (LSPs) and
Multipoint-to-Multipoint (MP2MP) LSPs are specified in [mLDP]. This Multipoint-to-Multipoint (MP2MP) LSPs are specified in [mLDP]. This
set of extensions is generally known as "Multipoint LDP" (mLDP). set of extensions is generally known as "Multipoint LDP" (mLDP).
A pair of Label Switched Routers (LSRs) that are the endpoints of an A pair of Label Switched Routers (LSRs) that are the endpoints of an
LDP session are considered to be "LDP neighbors". When a pair of LDP LDP session are considered to be "LDP peers". When a pair of LDP
neighbors are "directly connected" (e.g., they are connected by a peers are "directly connected" (e.g., they are connected by a layer 2
layer 2 medium, or are otherwise considered to be neighbors by the a medium, or are otherwise considered to be neighbors by the network's
network's interior routing protocol), the LDP session is said to be a interior routing protocol), the LDP session is said to be a "directly
"directly connected" LDP session. When the pair of LDP neighbors are connected" LDP session. When the pair of LDP peers are not directly
not directly connected, the session between them is said to be a connected, the session between them is said to be a "Targeted" LDP
"Targeted" LDP session. session.
The base specification for mLDP does not explicitly cover the case The base specification for mLDP does not explicitly cover the case
where the LDP multipoint extensions are used over a targeted LDP where the LDP multipoint extensions are used over a targeted LDP
session. This document provides that specification. session. This document provides that specification.
We will use the term "Multipoint" to mean "either P2MP or MP2MP". We will use the term "Multipoint" to mean "either P2MP or MP2MP".
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
 End of changes. 5 change blocks. 
19 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/