RFC 8223 on Application-Aware Targeted LDP

rfc-editor@rfc-editor.org Thu, 31 August 2017 23:45 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1D61329F9; Thu, 31 Aug 2017 16:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 oeAsW2ozOopR; Thu, 31 Aug 2017 16:45:22 -0700 (PDT)
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 5A357132E4F; Thu, 31 Aug 2017 16:45:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B59EBB8117C; Thu, 31 Aug 2017 16:44:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8223 on Application-Aware Targeted LDP
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Message-Id: <20170831234437.B59EBB8117C@rfc-editor.org>
Date: Thu, 31 Aug 2017 16:44:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nr4_cd-c08Q77s4FxiR75IEfdrs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 31 Aug 2017 23:45:25 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8223

        Title:      Application-Aware Targeted LDP 
        Author:     S. Esale, 
                    R. Torvi,
                    L. Jalil,
                    U. Chunduri,
                    K. Raza
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2017
        Mailbox:    sesale@juniper.net, 
                    rtorvi@juniper.net, 
                    luay.jalil@verizon.com,
                    uma.chunduri@huawei.com, 
                    skraza@cisco.com
        Pages:      18
        Characters: 41798
        Updates:    RFC 7473

        I-D Tag:    draft-ietf-mpls-app-aware-tldp-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8223

        DOI:        10.17487/RFC8223

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.

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 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