draft-ietf-mpls-lsp-ping-relay-reply-08.txt   draft-ietf-mpls-lsp-ping-relay-reply-09.txt 
Network Working Group J. Luo, Ed. Network Working Group J. Luo, Ed.
Internet-Draft ZTE Internet-Draft ZTE
Updates: 4379 (if approved) L. Jin, Ed. Updates: 4379 (if approved) L. Jin, Ed.
Intended status: Standards Track Individual Intended status: Standards Track Individual
Expires: October 30, 2015 T. Nadeau, Ed. Expires: November 26, 2015 T. Nadeau, Ed.
Lucidvision Lucidvision
G. Swallow, Ed. G. Swallow, Ed.
Cisco Cisco
April 28, 2015 May 25, 2015
Relayed Echo Reply mechanism for LSP Ping Relayed Echo Reply mechanism for LSP Ping
draft-ietf-mpls-lsp-ping-relay-reply-08 draft-ietf-mpls-lsp-ping-relay-reply-09
Abstract Abstract
In some inter autonomous system (AS) and inter-area deployment In some inter autonomous system (AS) and inter-area deployment
scenarios for RFC 4379 "Label Switched Path (LSP) Ping and scenarios for RFC 4379 "Label Switched Path (LSP) Ping and
Traceroute", a replying LSR may not have the available route to the Traceroute", a replying LSR may not have the available route to the
initiator, and the Echo Reply message sent to the initiator would be initiator, and the Echo Reply message sent to the initiator would be
discarded resulting in false negatives or complete failure of discarded resulting in false negatives or complete failure of
operation of LSP Ping and Traceroute. This document describes operation of LSP Ping and Traceroute. This document describes
extensions to LSP Ping mechanism to enable the replying Label extensions to LSP Ping mechanism to enable the replying Label
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 30, 2015. This Internet-Draft will expire on November 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 11, line 25 skipping to change at page 11, line 25
destination UDP port would be copied from the Initiator Source Port destination UDP port would be copied from the Initiator Source Port
field of the Relay Node Address Stack TLV. The source UDP port field of the Relay Node Address Stack TLV. The source UDP port
should be 3503. The TTL of the Echo Reply SHOULD be copied from the should be 3503. The TTL of the Echo Reply SHOULD be copied from the
received Relay Echo Reply and decremented by 1. The Source Address received Relay Echo Reply and decremented by 1. The Source Address
of Replying Router field is kept unmodified, and Source IP address of Replying Router field is kept unmodified, and Source IP address
field of the IP header is set to an address of the sending node. field of the IP header is set to an address of the sending node.
4.6. Sending Subsequent Echo Requests 4.6. Sending Subsequent Echo Requests
During a traceroute operation, multiple Echo Request messages are During a traceroute operation, multiple Echo Request messages are
sent. Each time the TTL is increased, the initiator could copy the sent. Each time the TTL is increased, the initiator SHOULD copy the
Relay Node Address Stack TLV received in the previous Echo Reply to Relay Node Address Stack TLV received in the previous Echo Reply to
the next Echo Request.Some modifications could also be made to the the next Echo Request. The Relay Node Address Stack TLV MUST NOT be
stack TLV. The NIL entry with K bit set SHOULD be deleted, otherwise modified except as follows. A NIL entry with K bit unset MAY be
the Echo Reply message will not be returned. The fields of Source removed. A NIL entry with K bit serves as a warning that further
Address of Replying Router and Destination Address Pointer may be Echo Request messages are likely to not result in a reply. If,
preserved or may be reset for subsequent MPLS Echo Request, and to be however, the initiator decides to continue a traceroute operation,
ignored in received MPLS Echo Request. the NIL entry with the K bit set MUST be removed. The Source Address
of Replying Router and Destination Address Pointer fields may be
preserved or reset since these fields are ignored in received MPLS
Echo Request.
4.7. Impact to Traceroute 4.7. Impact to Traceroute
Source IP address in Echo Reply and Relay Echo Reply is to be of the Source IP address in Echo Reply and Relay Echo Reply is to be of the
address of the node sending those packets, not the original address of the node sending those packets, not the original
responding node. Then the traceroute address output module will responding node. Then the traceroute address output module will
print the source IP address as below: print the source IP address as below:
if (Relay Node Address Stack TLV exists) { if (Relay Node Address Stack TLV exists) {
Print the Source Address of Replying Router in Print the Source Address of Replying Router in
 End of changes. 6 change blocks. 
11 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/