Re: [mpls] Feedback for WG DOC status of draft-nitinb-lsp-ping-over-mpls-tunnel-01

Yakov Rekhter <yakov@juniper.net> Wed, 19 December 2007 00:19 UTC

Return-path: <mpls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4mf9-0006k5-1x; Tue, 18 Dec 2007 19:19:51 -0500
Received: from mpls by megatron.ietf.org with local (Exim 4.43) id 1J4mf8-0006iH-6u for mpls-confirm+ok@megatron.ietf.org; Tue, 18 Dec 2007 19:19:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4mf7-0006i8-Lk for mpls@ietf.org; Tue, 18 Dec 2007 19:19:49 -0500
Received: from exprod7og107.obsmtp.com ([64.18.2.167]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4mf7-0003ce-6r for mpls@ietf.org; Tue, 18 Dec 2007 19:19:49 -0500
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP; Tue, 18 Dec 2007 16:19:40 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Dec 2007 16:19:25 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBJ0JPE64825; Tue, 18 Dec 2007 16:19:25 -0800 (PST) (envelope-from yakov@juniper.net)
Message-Id: <200712190019.lBJ0JPE64825@magenta.juniper.net>
To: Nitin Bahadur <nitinb@juniper.net>
Subject: Re: [mpls] Feedback for WG DOC status of draft-nitinb-lsp-ping-over-mpls-tunnel-01
In-Reply-To: Your message of "Tue, 18 Dec 2007 14:08:20 PST." <7FA0C743C38E5340BFC2873488FA1E8E8B2287@emailcorp3.jnpr.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <51756.1198023564.1@juniper.net>
Date: Tue, 18 Dec 2007 16:19:25 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 19 Dec 2007 00:19:25.0071 (UTC) FILETIME=[CF87B9F0:01C841D4]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mpls@ietf.org
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Errors-To: mpls-bounces@lists.ietf.org

Nitin, George, and Kireeti,

> WG,
> 
>   We had presented draft-nitinb-lsp-ping-over-mpls-tunnel-01 at the
> Vancouver IETF. The abstract is enclosed below for reference. We would
> like WG feedback on whether the draft is ready to be adopted as a WG
> document. If it is not, what needs to be addressed to make it one? 
> 
> Thanks
> Nitin, George, Kireeti.

I think the draft is ready to be accepted as an MPLS WG document.

Yakov.

> 
> Abstract:
> This document describes methods for performing lsp-ping traceroute over
> mpls tunnels and stitched LSPs.  The techniques outlined in RFC 4379 are
> insufficient to perform correct traceroute validation and path discovery
> for a LSP that goes over other mpls tunnels. RFC 4379 also does not have
> any procedures for tracing stitched LSPs. This document describes new
> procedures that can be used in conjunction with the standard procedures
> described in RFC 4379 to trace such LSPs.
> 
> http://tools.ietf.org/wg/mpls/draft-nitinb-lsp-ping-over-mpls-tunnel-01.
> txt
> 
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls