draft-ietf-mpls-proxy-lsp-ping-00.txt   draft-ietf-mpls-proxy-lsp-ping-01.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: January 06, 2014 S. Aldrin Expires: July 6, 2014 S. Aldrin
Huawei Technologies Huawei Technologies
July 05, 2013 January 02, 2014
Proxy MPLS Echo Request Proxy MPLS Echo Request
draft-ietf-mpls-proxy-lsp-ping-00 draft-ietf-mpls-proxy-lsp-ping-01
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 January 06, 2014. This Internet-Draft will expire on July 6, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Proxy Ping Overview . . . . . . . . . . . . . . . . . . . . . 4 2. Proxy Ping Overview . . . . . . . . . . . . . . . . . . . . . 5
3. Proxy MPLS Echo Request / Reply Procedures . . . . . . . . . 6 3. Proxy MPLS Echo Request / Reply Procedures . . . . . . . . . 6
3.1. Procedures for the initiator . . . . . . . . . . . . . . 6 3.1. Procedures for the initiator . . . . . . . . . . . . . . 6
3.2. Procedures for the proxy LSR . . . . . . . . . . . . . . 7 3.2. Procedures for the proxy LSR . . . . . . . . . . . . . . 7
3.2.1. Proxy LSR Handling when it is Egress for FEC . . . . 9 3.2.1. Proxy LSR Handling when it is Egress for FEC . . . . 9
3.2.2. Downstream Detailed/Downstream Maps in Proxy Reply . 10 3.2.2. Downstream Detailed/Downstream Maps in Proxy Reply . 10
3.2.3. Sending an MPLS proxy ping reply . . . . . . . . . . 10 3.2.3. Sending an MPLS proxy ping reply . . . . . . . . . . 10
3.2.4. Sending the MPLS echo requests . . . . . . . . . . . 10 3.2.4. Sending the MPLS echo requests . . . . . . . . . . . 10
3.2.4.1. Forming the base MPLS echo request . . . . . . . 11 3.2.4.1. Forming the base MPLS echo request . . . . . . . 11
3.2.4.2. Per interface sending procedures . . . . . . . . 12 3.2.4.2. Per interface sending procedures . . . . . . . . 12
4. Proxy Ping Request / Reply Messages . . . . . . . . . . . . . 12 4. Proxy Ping Request / Reply Messages . . . . . . . . . . . . . 12
4.1. Proxy Ping Request / Reply Message formats . . . . . . . 12 4.1. Proxy Ping Request / Reply Message formats . . . . . . . 12
4.2. Proxy Ping Request Message contents . . . . . . . . . . . 13 4.2. Proxy Ping Request Message contents . . . . . . . . . . . 13
4.3. Proxy Ping Reply Message Contents . . . . . . . . . . . . 14 4.3. Proxy Ping Reply Message Contents . . . . . . . . . . . . 14
5. TLV formats . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. TLV formats . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1. Proxy Echo Parameters TLV . . . . . . . . . . . . . . . . 14 5.1. Proxy Echo Parameters TLV . . . . . . . . . . . . . . . . 15
5.1.1. Next Hop sub-TLV . . . . . . . . . . . . . . . . . . 18 5.1.1. Next Hop sub-TLV . . . . . . . . . . . . . . . . . . 18
5.2. Reply-to Address TLV . . . . . . . . . . . . . . . . . . 19 5.2. Reply-to Address TLV . . . . . . . . . . . . . . . . . . 19
5.3. Upstream Neighbor Address TLV . . . . . . . . . . . . . . 19 5.3. Upstream Neighbor Address TLV . . . . . . . . . . . . . . 20
5.4. Downstream Neighbor Address TLV . . . . . . . . . . . . . 20 5.4. Downstream Neighbor Address TLV . . . . . . . . . . . . . 21
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1. Normative References . . . . . . . . . . . . . . . . . . 23 9.1. Normative References . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
This document is motivated by two broad issues in connection with This document is motivated by two broad issues in connection with
diagnosing Point-to-Multipoint (P2MP) Label Switched Paths (LSPs). diagnosing Point-to-Multipoint (P2MP) Label Switched Paths (LSPs).
The first is scalability due to the automatic replication of The first is scalability due to the automatic replication of
Multiprotocol Label Switching (MPLS) Echo Request Messages as they Multiprotocol Label Switching (MPLS) Echo Request Messages as they
proceed down the tree. The second, which is primarily motivated by proceed down the tree. The second, which is primarily motivated by
Multicast Label Distribution Protocol (mLDP), is the ability to trace Multicast Label Distribution Protocol (mLDP), is the ability to trace
a sub-LSP from leaf node to root node. a sub-LSP from leaf node to root node.
skipping to change at page 12, line 51 skipping to change at page 13, line 5
This document defines two new LSP Ping messages, the MPLS proxy ping This document defines two new LSP Ping messages, the MPLS proxy ping
request and the MPLS proxy ping reply. request and the MPLS proxy ping reply.
4.1. Proxy Ping Request / Reply Message formats 4.1. Proxy Ping Request / Reply Message formats
Except where noted, the definitions of all fields in the messages are Except where noted, the definitions of all fields in the messages are
identical to those found in [RFC4379]. The messages have the identical to those found in [RFC4379]. The messages have the
following format: following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version Number | MUST Be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Reply mode | Return Code | Return Subcode|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Handle |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLVs ... |
. .
. .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Version Number
| Version Number | MUST Be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Type | Reply mode | Return Code | Return Subcode|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Handle |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLVs ... |
. .
. .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version Number The Version Number is currently 1. (Note: the Version Number
is to be incremented whenever a change is made that affects the
ability of an implementation to correctly parse or process an
MPLS echo request/reply. These changes include any syntactic
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
certain version number. The Version Number may not need to be
changed if an optional TLV or sub-TLV is added.)
The Version Number is currently 1. (Note: the Version Number Message Type
is to be incremented whenever a change is made that affects the
ability of an implementation to correctly parse or process an
MPLS echo request/reply. These changes include any syntactic
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
certain version number. The Version Number may not need to be
changed if an optional TLV or sub-TLV is added.)
Message Type Type Message
---- -------
TBA-1 MPLS proxy ping request
(Pending IANA assignment)
Type Message TBA-2 MPLS proxy ping reply
---- ------- (Pending IANA assignment)
TBA-1 MPLS proxy ping request
(Pending IANA assignment)
TBA-2 MPLS proxy ping reply
(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
TLVs:
The MPLS proxy ping request message MAY contain the following Type TLV
TLVs: ---- -----------
1 Target FEC Stack
Type TLV 2 Downstream Mapping
---- ----------- 3 Pad
1 Target FEC Stack 5 Vendor Enterprise Number
2 Downstream Mapping 10 Reply TOS Byte
3 Pad
5 Vendor Enterprise Number
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-3 Proxy Echo Parameters (Pending IANA assignment) TBA-3 Proxy Echo Parameters (Pending IANA assignment)
TBA-4 Reply-to-Address TLV 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-3 Proxy Echo Parameters (Pending IANA assignment) TBA-3 Proxy Echo Parameters (Pending IANA assignment)
TBA-5 Upstream Neighbor Address (Pending IANA assignment) TBA-5 Upstream Neighbor Address (Pending IANA assignment)
TBA-6 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
The Proxy Echo Parameters TLV is a TLV that MUST be included in an The Proxy Echo Parameters TLV is a TLV that MUST be included in an
MPLS Proxy Echo Request message. The length of the TLV is 12 + K + MPLS Proxy Echo Request message. The length of the TLV is 12 + K +
S, where K is the length of the Destination IP Address field and S is S, where K is the length of the Destination IP Address field and S is
the total length of the sub-TLVs. The Proxy Echo Parameters TLV can the total length of the sub-TLVs. The Proxy Echo Parameters TLV can
be used to either to 1) control attributes used in Composing and be used to either to 1) control attributes used in Composing and
Sending an MPLS echo request or 2) query the Proxy LSR for Sending an MPLS echo request or 2) query the Proxy LSR for
information about the topmost FEC in the target FEC stack but not information about the topmost FEC in the target FEC stack but not
both. In the case where the Proxy LSR is being queried (ie both. In the case where the Proxy LSR is being queried (ie
information needs to be returned in a Proxy Reply), no MPLS echo information needs to be returned in a Proxy Reply), no MPLS echo
request will be sent from the Proxy LSR. The MPLS Proxy Echo request request will be sent from the Proxy LSR. The MPLS Proxy Echo request
echo header's Reply Mode should be set to "Reply with Proxy Info". echo header's Reply Mode should be set to "Reply with Proxy Info".
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Type | Reply mode | Proxy Flags | | Address Type | Reply mode | Proxy Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TTL | Rqst'd DSCP | Source UDP Port | | TTL | Rqst'd DSCP | Source UDP Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Flags | MPLS Payload size | | Global Flags | MPLS Payload size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Destination IP Address : : Destination IP Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: : : :
: Sub-TLVs : : Sub-TLVs :
: : : :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address Type Address Type
The type and length of the address found in the in the The type and length of the address found in the in the Destination
Destination IP Address and Next Hop IP Addresses fields. IP Address and Next Hop IP Addresses fields. The values are
The values are shared with the Downstream Mapping Address shared with the Downstream Mapping Address Type Registry.
Type Registry.
The type codes applicable in this case appear in the table below: The type codes applicable in this case appear in the table below:
Address Family Type Length Address Family Type Length
IPv4 1 4 IPv4 1 4
IPv6 3 16 IPv6 3 16
Reply mode Reply mode
The reply mode to be sent in the MPLS Echo Request message; the The reply mode to be sent in the MPLS Echo Request message; the
values are as specified in [RFC4379]. values are as specified in [RFC4379].
Proxy Flags Proxy Flags
The Proxy Request Initiator sets zero, one or more of these
flags to request actions at the Proxy LSR.
Request for FEC Neighbor Address info 0x01 The Proxy Request Initiator sets zero, one or more of these flags
to request actions at the Proxy LSR.
When set this requests that the proxy LSR supply the 0x01 Request for FEC Neighbor Address info
Upstream and Downstream neighbor address information in the
MPLS proxy ping reply message. This flag is only applicable
for the topmost FEC in the FEC stack if the FEC types
corresponds with a P2MP or MP2MP LSPs. The Proxy LSR MUST
respond as applicable with a Upstream Neighbor Address
TLV and Downstream Neighbor Address TLV(s) in the MPLS
Proxy ping reply message. Upstream Neighbor Address TLV
needs be included only if there is an upstream neighbor.
Similarly, one Downstream Neighbor Address TLV needs to
be included for each Downstream Neighbor for which the LSR
learned bindings from.
Setting this flag will cause the proxy LSR to cancel sending When set this requests that the proxy LSR supply the
an Echo request. Information learned with such proxy reply Upstream and Downstream neighbor address information in the
may be used by the proxy initiator to generate subsequent MPLS proxy ping reply message. This flag is only applicable
proxy requests. for the topmost FEC in the FEC stack if the FEC types
corresponds with a P2MP or MP2MP LSPs. The Proxy LSR MUST
respond as applicable with a Upstream Neighbor Address TLV
and Downstream Neighbor Address TLV(s) in the MPLS Proxy
ping reply message. Upstream Neighbor Address TLV needs be
included only if there is an upstream neighbor. Similarly,
one Downstream Neighbor Address TLV needs to be included for
each Downstream Neighbor for which the LSR learned bindings
from.
Request for Downstream Mapping 0x02 Setting this flag will cause the proxy LSR to cancel sending
an Echo request. Information learned with such proxy reply
may be used by the proxy initiator to generate subsequent
proxy requests.
When set this requests that the proxy LSR supply a 0x02 Request for Downstream Mapping
Downstream Mapping TLV see [RFC4379] in the MPLS
proxy ping reply message. It's not valid
to have Request for Downstream Detailed Mapping flag set
when this flag is set.
Setting this flag will cause the proxy LSR to cancel sending When set this requests that the proxy LSR supply a
an Echo request. Information learned with such proxy reply Downstream Mapping TLV see [RFC4379] in the MPLS proxy ping
may be used by the proxy initiator to generate subsequent reply message. It's not valid to have Request for
proxy requests. Downstream Detailed Mapping flag set when this flag is set.
Request for Downstream Detailed Mapping 0x04 Setting this flag will cause the proxy LSR to cancel sending
an Echo request. Information learned with such proxy reply
may be used by the proxy initiator to generate subsequent
proxy requests.
When set this requests that the proxy LSR supply a 0x04 Request for Downstream Detailed Mapping
Downstream Detailed Mapping TLV see [RFC6424] in the
MPLS proxy ping reply message. It's not valid
to have Request for Downstream Mapping flag set
when this flag is set.
Setting this flag will cause the proxy LSR to cancel sending When set this requests that the proxy LSR supply a
an Echo request. Information learned with such proxy reply Downstream Detailed Mapping TLV see [RFC6424] in the MPLS
may be used by the proxy initiator to generate subsequent proxy ping reply message. It's not valid to have Request
proxy requests. for Downstream Mapping flag set when this flag is set.
Explicit DSCP Request 0x08 Setting this flag will cause the proxy LSR to cancel sending
an Echo request. Information learned with such proxy reply
may be used by the proxy initiator to generate subsequent
proxy requests.
When set this requests that the proxy LSR use 0x08 Explicit DSCP Request
the supplied "Rqst'd DSCP" byte in the echo request message
TTL When set this requests that the proxy LSR use the supplied
"Rqst'd DSCP" byte in the echo request message
The TTL to be used in the label stack entry corresponding to TTL
the topmost FEC in the in the MPLS Echo Request packet. Valid
values are in the range [1,255]. A setting of 0 should be
ignored by the Proxy LSR.
Requested DSCP The TTL to be used in the label stack entry corresponding to
the topmost FEC in the in the MPLS Echo Request packet. Valid
values are in the range [1,255]. A setting of 0 should be
ignored by the Proxy LSR.
This field is valid only if the Explicit DSCP flag is set. If Requested DSCP
not set, the field MUST be zero on transmission and ignored on
receipt. When the flag is set this field contains the DSCP
value to be used in the MPLS echo request packet IP header.
Source UDP Port This field is valid only if the Explicit DSCP flag is set. If
not set, the field MUST be zero on transmission and ignored on
receipt. When the flag is set this field contains the DSCP
value to be used in the MPLS echo request packet IP header.
The source UDP port to be sent in the MPLS Echo Request packet Source UDP Port
Global Flags The source UDP port to be sent in the MPLS Echo Request packet
The Global Flags to be sent in the MPLS Echo Request message Global Flags
MPLS Payload Size The Global Flags to be sent in the MPLS Echo Request message
Used to request that the MPLS payload (IP header + UDP header MPLS Payload Size
+ MPLS echo request) be padded using a zero filled Pad TLV
so that the IP header, UDP header nad MPLS echo request total
the specified size. Field set to zero means no
size request is being made. If the requested size is less
than the minimum size required to form the MPLS echo request,
the request will be treated as a best effort request with
the Proxy LSR building the smallest possible packet (ie
not using a Pad TLV). The IP header DF bit should be set
when this field is non zero.
Destination IP Address Used to request that the MPLS payload (IP header + UDP header +
MPLS echo request) be padded using a zero filled Pad TLV so
that the IP header, UDP header nad MPLS echo request total the
specified size. Field set to zero means no size request is
being made. If the requested size is less than the minimum
size required to form the MPLS echo request, the request will
be treated as a best effort request with the Proxy LSR building
the smallest possible packet (ie not using a Pad TLV). The IP
header DF bit should be set when this field is non zero.
If the Address Type is IPv4, an address from the range 127/8; Destination IP Address
If the Address Type is IPv6, an address from the range If the Address Type is IPv4, an address from the range 127/8;
::FFFF:7F00:0/104 If the Address Type is IPv6, an address from the range
::FFFF:7F00:0/104
Sub-TLVs Sub-TLVs
A TLV encoded list of sub-TLVs. Currently one is defined. A TLV encoded list of sub-TLVs. Currently one is defined.
Sub-Type Length Value Field Sub-Type Length Value Field
-------- ------ ----------- -------- ------ -----------
1 8+ Next Hop 1 8+ Next Hop
5.1.1. Next Hop sub-TLV 5.1.1. Next Hop sub-TLV
This sub-TLV is used to describe a particular next hop towards which This sub-TLV is used to describe a particular next hop towards which
the Echo Request packet should be sent. If the topmost FEC in the the Echo Request packet should be sent. If the topmost FEC in the
FEC-stack is a multipoint LSP, this sub-TLV may appear multiple FEC-stack is a multipoint LSP, this sub-TLV may appear multiple
times. times.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Addr Type | MUST be Zero | | Addr Type | MUST be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Hop IP Address (4 or 16 octets) | | Next Hop IP Address (4 or 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Hop Interface (0, 4 or 16 octets) | | Next Hop Interface (0, 4 or 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address Type
Address Type
Type Type of Next Hop Addr Length IF Length Type Type of Next Hop Addr Length IF Length
1 IPv4 Numbered 4 4 1 IPv4 Numbered 4 4
2 IPv4 Unnumbered 4 4 2 IPv4 Unnumbered 4 4
3 IPv6 Numbered 16 16 3 IPv6 Numbered 16 16
4 IPv6 Unnumbered 16 4 4 IPv6 Unnumbered 16 4
5 IPv4 Protocol Adj 4 0 5 IPv4 Protocol Adj 4 0
6 IPv6 Protocol Adj 16 0 6 IPv6 Protocol Adj 16 0
Note: Types 1-4 correspond to the types in the DS Mapping Note: Types 1-4 correspond to the types in the DS Mapping
TLV. They are expected to populated with information TLV. They are expected to populated with information
obtained through a previously returned DS Mapping TLV. obtained through a previously returned DS Mapping TLV.
Types 5 and 6 are intended to be populated from the local Types 5 and 6 are intended to be populated from the local
address information obtained from a previously returned address information obtained from a previously returned
Downstream Neighbor Address TLV(s)/Upstream Neighbor Address TLV. Downstream Neighbor Address TLV(s)/Upstream Neighbor
Address TLV.
Next Hop IP Address Next Hop IP Address
A next hop address that the echo request message is to A next hop address that the echo request message is to
be sent towards be sent towards
Next Hop Interface Next Hop Interface
Identifier of the interface through which the echo request Identifier of the interface through which the echo request
message is to be sent. For Addr Type 5, and 6, the Next Hop message is to be sent. For Addr Type 5, and 6, the Next Hop
interface field isn't used and must of a associated byte interface field isn't used and must of a associated byte
length of "0" octets. length of "0" octets.
5.2. Reply-to Address TLV 5.2. Reply-to Address TLV
Used to specify the MPLS echo request IP source address. This Used to specify the MPLS echo request IP source address. This
address must be IP reachable via the Proxy LSR otherwise it will be address must be IP reachable via the Proxy LSR otherwise it will be
rejected. rejected.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Type | MUST be Zero | | Address Type | MUST be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Reply-to Address : : Reply-to Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address Type
Address Type
A type code as specified in the table below: A type code as specified in the table below:
Type Type of Address Type Type of Address
1 IPv4 1 IPv4
3 IPv6 3 IPv6
5.3. Upstream Neighbor Address TLV 5.3. Upstream Neighbor Address TLV
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Upst Addr Type |Local Addr Type| MUST be Zero | |Upst Addr Type |Local Addr Type| MUST be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Upstream Address : : Upstream Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Local Address : : Local Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Upst Addr Type; Local Addr Type Upst Addr Type; Local Addr Type
These two fields determine the type and length of the These two fields determine the type and length of the
respective addresses. The codes are specified in the table respective addresses. The codes are specified in the table
below: below:
Type Type of Address Length Type Type of Address Length
0 No Address Supplied 0 0 No Address Supplied 0
1 IPv4 4 1 IPv4 4
3 IPv6 16 3 IPv6 16
Upstream Address Upstream Address
The address of the immediate upstream neighbor for the topmost The address of the immediate upstream neighbor for the topmost
FEC in the FEC stack. If protocol adjacency exists by which FEC in the FEC stack. If protocol adjacency exists by which
the label for this FEC was exchanged, this address MUST be the the label for this FEC was exchanged, this address MUST be the
address used in that protocol exchange. address used in that protocol exchange.
Local Address Local Address
The local address used in the protocol adjacency exists by The local address used in the protocol adjacency exists by
which the label for this FEC was exchanged. which the label for this FEC was exchanged.
5.4. Downstream Neighbor Address TLV 5.4. Downstream Neighbor Address TLV
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Dnst Addr Type |Local Addr Type| MUST be Zero | |Dnst Addr Type |Local Addr Type| MUST be Zero |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Downstream Address : : Downstream Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
: Local Address : : Local Address :
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Dnst Addr Type; Local Addr Type Dnst Addr Type; Local Addr Type
These two fields determine the type and length of the These two fields determine the type and length of the
respective addresses. The codes are specified in the table respective addresses. The codes are specified in the table
below: below:
Type Type of Address Length Type Type of Address Length
0 No Address Supplied 0 0 No Address Supplied 0
1 IPv4 4 1 IPv4 4
3 IPv6 16 3 IPv6 16
Downstream Address Downstream Address
The address of a immediate downstream neighbor for the topmost The address of a immediate downstream neighbor for the topmost
FEC in the FEC stack. If protocol adjacency exists by which FEC in the FEC stack. If protocol adjacency exists by which
the label for this FEC was exchanged, this address MUST be the the label for this FEC was exchanged, this address MUST be the
address used in that protocol exchange. address used in that protocol exchange.
Local Address Local Address
The local address used in the protocol adjacency exists by The local address used in the protocol adjacency exists by
which the label for this FEC was exchanged. which the label for this FEC was exchanged.
6. Security Considerations 6. Security Considerations
The mechanisms described in this document are intended to be used The mechanisms described in this document are intended to be used
within a Service Provider network and to be initiated only under the within a Service Provider network and to be initiated only under the
authority of that administration. authority of that administration.
If such a network also carries internet traffic, or permits IP access If such a network also carries internet traffic, or permits IP access
from other administrations, MPLS proxy ping message SHOULD be from other administrations, MPLS proxy ping message SHOULD be
discarded at those points. This can be accomplished by filtering on discarded at those points. This can be accomplished by filtering on
skipping to change at page 22, line 19 skipping to change at page 22, line 36
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Nobo Akiya for his detailed review The authors would like to thank Nobo Akiya for his detailed review
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
---- ----------- ---- -----------
TBA-1 MPLS proxy ping request TBA-1 MPLS proxy ping request
TBA-2 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
---- -------- ----------- ---- -------- -----------
TBA-3 Proxy Echo Parameters TBA-3 Proxy Echo Parameters
1 Next Hop 1 Next Hop
TBA-4 Reply-to Address TBA-4 Reply-to Address
TBA-5 Upstream Neighbor Address TBA-5 Upstream Neighbor Address
TBA-6 Downstream Neighbor Address TBA-6 Downstream Neighbor Address
Return Code [pending IANA assignment] Return Code [pending IANA assignment]
Value Meaning Value Meaning
----- ------- ----- -------
TBA-7 Proxy ping not authorized. TBA-7 Proxy ping not authorized.
TBA-8 Proxy ping parameters need to be modified. TBA-8 Proxy ping parameters need to be modified.
TBA-9 MPLS Echo Request Could not be sent. TBA-9 MPLS Echo Request Could not be sent.
TBA-10 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
----- ------- ----- -------
TBA-11 IPv4 Protocol Adj TBA-11 IPv4 Protocol Adj
TBA-12 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. 95 change blocks. 
315 lines changed or deleted 309 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/