Re: [mpls] I-D Action: draft-ietf-mpls-app-aware-tldp-02.txt

"Shah, Himanshu" <> Tue, 23 February 2016 14:47 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5B0A61B2E80; Tue, 23 Feb 2016 06:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MRs0Vz0gXbfA; Tue, 23 Feb 2016 06:47:56 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 973871B2D39; Tue, 23 Feb 2016 06:47:56 -0800 (PST)
Received: from pps.filterd ( []) by ( with SMTP id u1NEgx5n003212; Tue, 23 Feb 2016 09:47:56 -0500
Received: from ( []) by with ESMTP id 218qy10d7p-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 23 Feb 2016 09:47:56 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id 8.3.389.2; Tue, 23 Feb 2016 09:47:53 -0500
Received: from ([::1]) by ([::1]) with mapi; Tue, 23 Feb 2016 09:47:53 -0500
From: "Shah, Himanshu" <>
To: "" <>, "" <>
Date: Tue, 23 Feb 2016 09:47:52 -0500
Thread-Topic: [mpls] I-D Action: draft-ietf-mpls-app-aware-tldp-02.txt
Thread-Index: AdFpwbevUVpoD9AlQeeZKZqH8/Dw0AEBqHcA
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
X-TM-AS-Product-Ver: SMEX-
X-TM-AS-Result: No--0.786100-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-02-23_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1601100000 definitions=main-1602230172
Archived-At: <>
Cc: "" <>
Subject: Re: [mpls] I-D Action: draft-ietf-mpls-app-aware-tldp-02.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 23 Feb 2016 14:47:58 -0000

I read this draft and agree that a mechanism is required to 
protect against onslaught of incoming uninitiated tLDP sessions,
either for security or scale reasons.

In my view, this work is something WG consider adopting.


-----Original Message-----
From: mpls [] On Behalf Of
Sent: Wednesday, February 17, 2016 3:27 PM
Subject: [mpls] I-D Action: draft-ietf-mpls-app-aware-tldp-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching of the IETF.

        Title           : Application-aware Targeted LDP
        Authors         : Santosh Esale
                          Raveendra Torvi
                          Luay Jalil
                          Uma Chunduri
                          Zhenbin Li
                          Kamran Raza
	Filename        : draft-ietf-mpls-app-aware-tldp-02.txt
	Pages           : 17
	Date            : 2016-02-17

   Recent targeted LDP applications such as remote loop-free alternate
   (LFA) and BGP auto discovered pseudowire may automatically establish
   a tLDP session to any LSR in a network.  The initiating LSR has
   information about the targeted applications to administratively
   control initiation of the session. However, the responding LSR has no
   such information to control acceptance of this session. This document
   defines a mechanism to advertise and negotiate Targeted Applications
   Capability during LDP session initialization.  As the responding LSR
   becomes aware of targeted applications, it may establish a limited
   number of tLDP sessions for certain applications. In addition, each
   targeted application is mapped to LDP Forwarding Equivalence Class
   (FEC) Elements to advertise only necessary LDP FEC-label bindings
   over the session.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

mpls mailing list