Subject: Re: [mpls] New Version Notification for draft-ietf-mpls-lsp-ping-relay-reply-07.txt

From: "[email-masked]" <[email-masked]>
Date: Sat, 7 Mar 2015 23:39:37 +0800

Hi all,
We update this draft to v7, and main changes are as below:
1. add a destination address point in stack TLV to point to the current destination address of the Relayed Echo Reply, so as to avoid potential loop.
2. add a source address in stack TLV, then the initiator could get the replying node address.
3. other text improvement.
Any comments are welcome.

Regards
Lizhong
 
From: internet-drafts
Date: 2015-03-07 23:31
To: Lizhong Jin; Lizhong Jin; George Swallow; George Swallow; Luo Jian; Thomas Nadeau; Thomas Nadeau; Jian Luo
Subject: New Version Notification for draft-ietf-mpls-lsp-ping-relay-reply-07.txt
 
A new version of I-D, draft-ietf-mpls-lsp-ping-relay-reply-07.txt
has been successfully submitted by Lizhong Jin and posted to the
IETF repository.
 
Name: draft-ietf-mpls-lsp-ping-relay-reply
Revision: 07
Title: Relayed Echo Reply mechanism for LSP Ping
Document date: 2015-03-07
Group: mpls
Pages: 16
URL:            http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsp-ping-relay-reply-07.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-relay-reply/
Htmlized:       http://tools.ietf.org/html/draft-ietf-mpls-lsp-ping-relay-reply-07
Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-lsp-ping-relay-reply-07
 
Abstract:
   In some inter autonomous system (AS) and inter-area deployment
   scenarios for RFC 4379 "Label Switched Path (LSP) Ping and
   Traceroute", a replying LSR may not have the available route to the
   initiator, and the Echo Reply message sent to the initiator would be
   discarded resulting in false negatives or complete failure of
   operation of LSP Ping and Traceroute.  This document describes
   extensions to LSP Ping mechanism to enable the replying Label
   Switching Router (LSR) to have the capability to relay the Echo
   Response by a set of routable intermediate nodes to the initiator.
   This document updates RFC 4379.

 
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
 
The IETF Secretariat