draft-lim-mpls-proxy-lsp-ping-02.txt   draft-lim-mpls-proxy-lsp-ping-03.txt 
Network Working Group G. Swallow Network Working Group G. Swallow
Internet-Draft V. Lim Internet-Draft V. Lim
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: November 08, 2013 S. Aldrin Expires: January 06, 2014 S. Aldrin
Huawei Technologies Huawei Technologies
May 07, 2013 July 05, 2013
Proxy MPLS Echo Request Proxy MPLS Echo Request
draft-lim-mpls-proxy-lsp-ping-02 draft-lim-mpls-proxy-lsp-ping-03
Abstract Abstract
This document defines a means of remotely initiating Multiprotocol This document defines a means of remotely initiating Multiprotocol
Label Switched Protocol Pings on Label Switched Paths. A proxy ping Label Switched Protocol Pings on Label Switched Paths. A proxy ping
request is sent to any Label Switching Routers along a Label Switched request is sent to any Label Switching Routers along a Label Switched
Path. The primary motivations for this facility are first to limit Path. The primary motivations for this facility are first to limit
the number of messages and related processing when using LSP Ping in the number of messages and related processing when using LSP Ping in
large Point-to-Multipoint LSPs, and second to enable leaf to leaf/ large Point-to-Multipoint LSPs, and second to enable leaf to leaf/
root tracing. root tracing.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 November 08, 2013. This Internet-Draft will expire on January 06, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 8, line 35 skipping to change at page 8, line 35
return codes don't match the situation. For example, when a Proxy return codes don't match the situation. For example, when a Proxy
LSR is a transit router, it's not appropriate for the return code to LSR is a transit router, it's not appropriate for the return code to
describe how the packet would transit because the Proxy Request describe how the packet would transit because the Proxy Request
doesn't contain information about what input interface the an MPLS doesn't contain information about what input interface the an MPLS
echo request would be switched from at the Proxy LSR. echo request would be switched from at the Proxy LSR.
The proxy LSR then determines if it is authorized to send the The proxy LSR then determines if it is authorized to send the
specified MPLS echo request on behalf of the initiator. A Proxy LSR specified MPLS echo request on behalf of the initiator. A Proxy LSR
MUST be capable of filtering addresses to validate initiators. Other MUST be capable of filtering addresses to validate initiators. Other
filters on FECs or MPLS echo request contents MAY be applied. If a filters on FECs or MPLS echo request contents MAY be applied. If a
filter has been invoked (i.e. configured) and an address does not filter has been invoked (i.e. configured) and an address does not
pass the filter, then an MPLS echo request message MUST NOT be sent, pass the filter, then an MPLS echo request message MUST NOT be sent,
and the event SHOULD be logged. An MPLS proxy ping reply message MAY and the event SHOULD be logged. An MPLS proxy ping reply message MAY
be sent with a Return Code of <tba>, "Proxy Ping not authorized". be sent with a Return Code of <tba>, "Proxy Ping not authorized".
The destination address specified in the Proxy Echo Parameters TLV is The destination address specified in the Proxy Echo Parameters TLV is
checked to ensure that it conforms to the address allowed IPv4 or checked to ensure that it conforms to the address allowed IPv4 or
IPv6 address range. If not, it sets the Return Code set to IPv6 address range. If not, it sets the Return Code set to
"Malformed echo request received" and the Subcode set to zero. If "Malformed echo request received" and the Subcode set to zero. If
the Reply Mode of the message header is not 1, an MPLS proxy ping the Reply Mode of the message header is not 1, an MPLS proxy ping
reply message SHOULD be sent as described below. reply message SHOULD be sent as described below.
skipping to change at page 13, line 36 skipping to change at page 13, line 36
MPLS echo request/reply. These changes include any syntactic MPLS echo request/reply. These changes include any syntactic
or semantic changes made to any of the fixed fields, or to any or semantic changes made to any of the fixed fields, or to any
TLV or sub-TLV assignment or format that is defined at a TLV or sub-TLV assignment or format that is defined at a
certain version number. The Version Number may not need to be certain version number. The Version Number may not need to be
changed if an optional TLV or sub-TLV is added.) changed if an optional TLV or sub-TLV is added.)
Message Type Message Type
Type Message Type Message
---- ------- ---- -------
3 MPLS proxy ping request TBA-1 MPLS proxy ping request
(Pending IANA assignment) (Pending IANA assignment)
4 MPLS proxy ping reply TBA-2 MPLS proxy ping reply
(Pending IANA assignment) (Pending IANA assignment)
4.2. Proxy Ping Request Message contents 4.2. Proxy Ping Request Message contents
The MPLS proxy ping request message MAY contain the following The MPLS proxy ping request message MAY contain the following
TLVs: TLVs:
Type TLV Type TLV
---- ----------- ---- -----------
1 Target FEC Stack 1 Target FEC Stack
2 Downstream Mapping 2 Downstream Mapping
3 Pad 3 Pad
5 Vendor Enterprise Number 5 Vendor Enterprise Number
10 Reply TOS Byte 10 Reply TOS Byte
11 P2MP Responder Identifier [RFC6425] 11 P2MP Responder Identifier [RFC6425]
12 Echo Jitter TLV [RFC6425] 12 Echo Jitter TLV [RFC6425]
20 Downstream Detailed Mapping 20 Downstream Detailed Mapping
tba Proxy Echo Parameters (Pending IANA assignment) TBA-3 Proxy Echo Parameters (Pending IANA assignment)
TBA-4 Reply-to-Address TLV
* Vendor Private TLVs * Vendor Private TLVs
* TLVs types in the Vendor Private TLV Space MUST be * TLVs types in the Vendor Private TLV Space MUST be
ignored if not understood ignored if not understood
4.3. Proxy Ping Reply Message Contents 4.3. Proxy Ping Reply Message Contents
The MPLS proxy ping reply message MAY contain the following TLVs: The MPLS proxy ping reply message MAY contain the following TLVs:
Type TLV Type TLV
---- ----------- ---- -----------
1 Target FEC Stack 1 Target FEC Stack
2 Downstream Mapping 2 Downstream Mapping
5 Vendor Enterprise Number 5 Vendor Enterprise Number
9 Errored TLVs 9 Errored TLVs
20 Downstream Detailed Mapping 20 Downstream Detailed Mapping
tba Proxy Echo Parameters (Pending IANA assignment) TBA-3 Proxy Echo Parameters (Pending IANA assignment)
tba Upstream Neighbor Address (Pending IANA assignment) TBA-5 Upstream Neighbor Address (Pending IANA assignment)
tba Downstream Neighbor Address (0 or more) TBA-6 Downstream Neighbor Address (0 or more)
(Pending IANA assignment) (Pending IANA assignment)
* Vendor Private TLVs * Vendor Private TLVs
* TLVs types in the Vendor Private TLV Space MUST be * TLVs types in the Vendor Private TLV Space MUST be
ignored if not understood ignored if not understood
5. TLV formats 5. TLV formats
5.1. Proxy Echo Parameters TLV 5.1. Proxy Echo Parameters TLV
skipping to change at page 22, line 23 skipping to change at page 22, line 23
and insightful comments. and insightful comments.
8. IANA Considerations 8. IANA Considerations
This document makes the following assignments (pending IANA action) This document makes the following assignments (pending IANA action)
LSP Ping Message Types LSP Ping Message Types
Type Value Field Type Value Field
---- ----------- ---- -----------
03(tba) MPLS proxy ping request TBA-1 MPLS proxy ping request
04(tba) MPLS proxy ping reply TBA-2 MPLS proxy ping reply
TLVs and Sub-TLVs TLVs and Sub-TLVs
Type Sub-Type Value Field Type Sub-Type Value Field
---- -------- ----------- ---- -------- -----------
22(tba) Proxy Echo Parameters TBA-3 Proxy Echo Parameters
1 Next Hop 1 Next Hop
23(tba) Reply-to Address TBA-4 Reply-to Address
24(tba) Upstream Neighbor Address TBA-5 Upstream Neighbor Address
25(tba) Downstream Neighbor Address TBA-6 Downstream Neighbor Address
Return Code [pending IANA assignment] Return Code [pending IANA assignment]
Value Meaning Value Meaning
----- ------- ----- -------
16(tba) Proxy ping not authorized. TBA-7 Proxy ping not authorized.
17(tba) Proxy ping parameters need to be modified. TBA-8 Proxy ping parameters need to be modified.
18(tba) MPLS Echo Request Could not be sent. TBA-9 MPLS Echo Request Could not be sent.
18(tba) Replying router has FEC mapping for topmost FEC. TBA-10 Replying router has FEC mapping for topmost FEC.
Downstream Address Mapping Registry [pending IANA assignment] Downstream Address Mapping Registry [pending IANA assignment]
Value Meaning Value Meaning
----- ------- ----- -------
5(tba) IPv4 Protocol Adj TBA-11 IPv4 Protocol Adj
6(tba) IPv6 Protocol Adj TBA-12 IPv6 Protocol Adj
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. February 2006.
[RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for
 End of changes. 14 change blocks. 
23 lines changed or deleted 24 lines changed or added

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