RFC 5919 on Signaling LDP Label Advertisement Completion

rfc-editor@rfc-editor.org Mon, 16 August 2010 23:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 440583A698C; Mon, 16 Aug 2010 16:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.038
X-Spam-Level:
X-Spam-Status: No, score=-102.038 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jh3nPqMOvRfg; Mon, 16 Aug 2010 16:52:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 61EC53A698A; Mon, 16 Aug 2010 16:52:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 831D9E06D9; Mon, 16 Aug 2010 16:53:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5919 on Signaling LDP Label Advertisement Completion
From: rfc-editor@rfc-editor.org
Message-Id: <20100816235315.831D9E06D9@rfc-editor.org>
Date: Mon, 16 Aug 2010 16:53:15 -0700 (PDT)
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 16 Aug 2010 23:52:40 -0000

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

        
        RFC 5919

        Title:      Signaling LDP Label Advertisement Completion 
        Author:     R. Asati, P. Mohapatra,
                    E. Chen, B. Thomas
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    rajiva@cisco.com, 
                    pmohapat@cisco.com, 
                    chenying220@huawei.com,  bobthomas@alum.mit.edu
        Pages:      9
        Characters: 19455
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-ldp-end-of-lib-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5919.txt

There are situations following Label Distribution Protocol (LDP)
session establishment where it would be useful for an LDP speaker to
know when its peer has advertised all of its labels.  The LDP
specification provides no mechanism for an LDP speaker to notify a
peer when it has completed its initial label advertisements to that
peer.  This document specifies means for an LDP speaker to signal
completion of its initial label advertisements following session
establishment.  [STANDARDS TRACK]

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard Protocol.

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/rfcsearch.html.
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