Application-Aware Targeted LDP
RFC 8223
| Document | Type |
RFC - Proposed Standard
(August 2017; Errata)
Updates RFC 7473
|
|
|---|---|---|---|
| Last updated | 2018-12-28 | ||
| Replaces | draft-esale-mpls-app-aware-tldp | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Loa Andersson | ||
| Shepherd write-up | Show (last changed 2016-07-17) | ||
| IESG | IESG state | RFC 8223 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) S. Esale
Request for Comments: 8223 R. Torvi
Updates: 7473 Juniper Networks
Category: Standards Track L. Jalil
ISSN: 2070-1721 Verizon
U. Chunduri
Huawei
K. Raza
Cisco Systems, Inc.
August 2017
Application-Aware Targeted LDP
Abstract
Recent Targeted Label Distribution Protocol (tLDP) applications, such
as remote Loop-Free Alternates (LFAs) and BGP auto-discovered
pseudowires, may automatically establish a tLDP session with any
Label Switching Router (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 the Targeted
Application Capability (TAC) 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. This document updates RFC 7473 for
enabling advertisement of LDP FEC label bindings over the session.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8223.
Esale, et al. Standards Track [Page 1]
RFC 8223 Application-Aware tLDP August 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
1.1. Conventions Used in This Document ..........................4
1.2. Terminology ................................................4
2. Targeted Application Capability .................................5
2.1. Encoding ...................................................5
2.2. Procedures .................................................5
2.3. LDP Message Procedures .....................................8
2.3.1. Initialization Message ..............................8
2.3.2. Capability Message ..................................8
3. Targeted Application FEC Advertisement Procedures ...............9
4. Interaction of Targeted Application Capabilities and State
Advertisement Control Capabilities .............................10
5. Use Cases ......................................................12
5.1. Remote LFA Automatic Targeted Session .....................12
5.2. FEC 129 Auto-discovery Targeted Session ...................13
5.3. LDP over RSVP and Remote LFA Targeted Session .............13
5.4. mLDP Node Protection Targeted Session .....................13
6. Security Considerations ........................................14
7. IANA Considerations ............................................14
8. References .....................................................15
8.1. Normative References ......................................15
8.2. Informative References ....................................16
Acknowledgments ...................................................17
Contributors ......................................................17
Show full document text