draft-ietf-mpls-p2mp-lsp-ping-14.txt   draft-ietf-mpls-p2mp-lsp-ping-15.txt 
Network Working Group S. Saxena, Ed. Network Working Group S. Saxena, Ed.
Internet-Draft Cisco Systems, Inc. Internet-Draft G. Swallow
Intended Status: Standards Track A. Farrel Intended Status: Standards Track Z. Ali
Updates: 4379 (if approved) Old Dog Consulting Updates: 4379 (if approved) Cisco Systems, Inc.
Expires: July 24, 2011 S. Yasukawa Expires: July 25, 2011 A. Farrel
Old Dog Consulting
S. Yasukawa
NTT Corporation NTT Corporation
January 25, 2011 T. Nadeau
LucidVision
January 26, 2011
Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol
Label Switching (MPLS) - Extensions to LSP Ping Label Switching (MPLS) - Extensions to LSP Ping
draft-ietf-mpls-p2mp-lsp-ping-14.txt draft-ietf-mpls-p2mp-lsp-ping-15.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 2, line 26 skipping to change at page 2, line 32
Contents Contents
1. Introduction.................................................... 3 1. Introduction.................................................... 3
1.1. Design Considerations......................................... 4 1.1. Design Considerations......................................... 4
2. Notes on Motivation............................................. 4 2. Notes on Motivation............................................. 4
2.1. Basic Motivations for LSP Ping................................ 4 2.1. Basic Motivations for LSP Ping................................ 4
2.2. Motivations for LSP Ping for P2MP LSPs........................ 5 2.2. Motivations for LSP Ping for P2MP LSPs........................ 5
3. Packet Format................................................... 7 3. Packet Format................................................... 7
3.1. Identifying the LSP Under Test................................ 7 3.1. Identifying the LSP Under Test................................ 7
3.1.1. Identifying a P2MP MPLS TE LSP.............................. 7 3.1.1. Identifying a P2MP MPLS TE LSP.............................. 7
3.1.1.1. RSVP P2MP IPv4 Session Sub-TLV............................ 8 3.1.1.1. RSVP P2MP IPv4 Session Sub-TLV............................ 7
3.1.1.2. RSVP P2MP IPv6 Session Sub-TLV............................ 8 3.1.1.2. RSVP P2MP IPv6 Session Sub-TLV............................ 8
3.1.2. Identifying a Multicast LDP LSP............................. 9 3.1.2. Identifying a Multicast LDP LSP............................. 8
3.1.2.1. Multicast LDP FEC Stack Sub-TLVs.......................... 9 3.1.2.1. Multicast LDP FEC Stack Sub-TLVs.......................... 9
3.1.2.2. Applicability to Multipoint-to-Multipoint LSPs........... 11 3.1.2.2. Applicability to Multipoint-to-Multipoint LSPs........... 10
3.2. Limiting the Scope of Responses.............................. 11 3.2. Limiting the Scope of Responses.............................. 10
3.2.1. Egress Address P2MP Responder Identifier Sub-TLVs.......... 12 3.2.1. Egress Address P2MP Responder Identifier Sub-TLVs.......... 11
3.2.2. Node Address P2MP Responder Identifier Sub-TLVs............ 12 3.2.2. Node Address P2MP Responder Identifier Sub-TLVs............ 12
3.3. Preventing Congestion of Echo Responses...................... 12 3.3. Preventing Congestion of Echo Responses...................... 12
3.4. Respond Only If TTL Expired Flag............................. 13 3.4. Respond Only If TTL Expired Flag............................. 13
3.5. Downstream Detailed Mapping TLV.............................. 14 3.5. Downstream Detailed Mapping TLV.............................. 13
4. Operation of LSP Ping for a P2MP LSP........................... 14 4. Operation of LSP Ping for a P2MP LSP........................... 14
4.1. Initiating Router Operations................................. 15 4.1. Initiating Router Operations................................. 14
4.1.1. Limiting Responses to Echo Requests........................ 15 4.1.1. Limiting Responses to Echo Requests........................ 14
4.1.2. Jittered Responses to Echo Requests........................ 15 4.1.2. Jittered Responses to Echo Requests........................ 15
4.2. Responding Router Operations................................. 16 4.2. Responding Router Operations................................. 15
4.2.1. Echo Response Reporting.................................... 17 4.2.1. Echo Response Reporting.................................... 16
4.2.1.1. Responses from Transit and Branch nodes.................. 18 4.2.1.1. Responses from Transit and Branch nodes.................. 17
4.2.1.2. Responses from Egress Nodes.............................. 18 4.2.1.2. Responses from Egress Nodes.............................. 17
4.2.1.3. Responses from Bud Nodes................................. 18 4.2.1.3. Responses from Bud Nodes................................. 18
4.3. Special Considerations for Traceroute........................ 20 4.3. Special Considerations for Traceroute........................ 19
4.3.1. End of Processing for Traceroutes.......................... 20 4.3.1. End of Processing for Traceroutes.......................... 20
4.3.2. Multiple responses from Bud and Egress Nodes............... 21 4.3.2. Multiple responses from Bud and Egress Nodes............... 20
4.3.3. Non-Response to Traceroute Echo Requests................... 21 4.3.3. Non-Response to Traceroute Echo Requests................... 21
4.3.4. Use of Downstream Detailed Mapping TLV in Echo Request..... 21 4.3.4. Use of Downstream Detailed Mapping TLV in Echo Request..... 21
4.3.5 Cross Over Node Processing.................................. 22 4.3.5 Cross Over Node Processing.................................. 21
5. Non-compliant Routers.......................................... 22 5. Non-compliant Routers.......................................... 22
6. OAM Considerations............................................. 23 6. OAM Considerations............................................. 22
7. IANA Considerations............................................ 23 7. IANA Considerations............................................ 23
7.1. New Sub-TLV Types............................................ 24 7.1. New Sub-TLV Types............................................ 23
7.2. New TLVs..................................................... 24 7.2. New TLVs..................................................... 23
8. Security Considerations........................................ 24 8. Security Considerations........................................ 24
9. Acknowledgements............................................... 25 9. Acknowledgements............................................... 24
10. References.................................................... 25 10. References.................................................... 24
10.1. Normative References........................................ 25 10.1. Normative References........................................ 24
10.2. Informative References...................................... 25 10.2. Informative References...................................... 25
11. Authors' Addresses............................................ 26 11. Authors' Addresses............................................ 25
12. Full Copyright Statement...................................... 27 12. Full Copyright Statement...................................... 26
1. Introduction 1. Introduction
Simple and efficient mechanisms that can be used to detect data plane Simple and efficient mechanisms that can be used to detect data plane
failures in point-to-point (P2P) Multiprotocol Label Switching (MPLS) failures in point-to-point (P2P) Multiprotocol Label Switching (MPLS)
Label Switched Paths (LSP) are described in [RFC4379]. The Label Switched Paths (LSP) are described in [RFC4379]. The
techniques involve information carried in MPLS "Echo Request" and techniques involve information carried in MPLS "Echo Request" and
"Echo Reply" messages, and mechanisms for transporting them. The "Echo Reply" messages, and mechanisms for transporting them. The
echo request and reply messages provide sufficient information to echo request and reply messages provide sufficient information to
check correct operation of the data plane, as well as a mechanism to check correct operation of the data plane, as well as a mechanism to
skipping to change at page 26, line 50 skipping to change at page 26, line 20
Phone: 613-889-6158 Phone: 613-889-6158
Email: zali@cisco.com Email: zali@cisco.com
George Swallow George Swallow
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave 1414 Massachusetts Ave
Boxborough, MA 01719 Boxborough, MA 01719
Email: swallow@cisco.com Email: swallow@cisco.com
Thomas D. Nadeau Thomas D. Nadeau
British Telecom Email: tnadeau@lucidvision.com
BT Centre
81 Newgate Street
EC1A 7AJ
London
Email: tom.nadeau@bt.com
Shaleen Saxena Shaleen Saxena
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave 1414 Massachusetts Ave
Boxborough, MA 01719 Boxborough, MA 01719
Email: ssaxena@cisco.com Email: ssaxena@cisco.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
 End of changes. 18 change blocks. 
36 lines changed or deleted 35 lines changed or added

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