draft-ietf-mboned-mtrace-v2-10.txt   draft-ietf-mboned-mtrace-v2-11.txt 
MBONED Working Group H. Asaeda MBONED Working Group H. Asaeda
Internet-Draft NICT Internet-Draft NICT
Intended status: Standards Track W. Lee, Ed. Intended status: Standards Track W. Lee, Ed.
Expires: January 10, 2014 Juniper Networks, Inc. Expires: April 29, 2015
July 09, 2013 October 26, 2014
Mtrace Version 2: Traceroute Facility for IP Multicast Mtrace Version 2: Traceroute Facility for IP Multicast
draft-ietf-mboned-mtrace-v2-10 draft-ietf-mboned-mtrace-v2-11
Abstract Abstract
This document describes the IP multicast traceroute facility, named This document describes the IP multicast traceroute facility, named
Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2 Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2
requires special implementations on the part of routers. This requires special implementations on the part of routers. This
specification describes the required functionality in multicast specification describes the required functionality in multicast
routers, as well as how an Mtrace2 client invokes a query and routers, as well as how an Mtrace2 client invokes a query and
receives a reply. receives a reply.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 10, 2014. This Internet-Draft will expire on April 29, 2015.
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 18 skipping to change at page 2, line 18
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5
3. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 6 3. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Mtrace2 TLV format . . . . . . . . . . . . . . . . . . . 7 3.1. Mtrace2 TLV format . . . . . . . . . . . . . . . . . . . 7
3.2. Defined TLVs . . . . . . . . . . . . . . . . . . . . . . 7 3.2. Defined TLVs . . . . . . . . . . . . . . . . . . . . . . 7
3.2.1. Mtrace2 Query . . . . . . . . . . . . . . . . . . . . 8 3.2.1. Mtrace2 Query . . . . . . . . . . . . . . . . . . . . 8
3.2.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . 10 3.2.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . 10
3.2.3. Mtrace2 Reply . . . . . . . . . . . . . . . . . . . . 10 3.2.3. Mtrace2 Reply . . . . . . . . . . . . . . . . . . . . 10
3.2.4. IPv4 Mtrace2 Standard Response Block . . . . . . . . 10 3.2.4. IPv4 Mtrace2 Standard Response Block . . . . . . . . 11
3.2.5. IPv6 Mtrace2 Standard Response Block . . . . . . . . 14 3.2.5. IPv6 Mtrace2 Standard Response Block . . . . . . . . 14
3.2.6. Mtrace2 Augmented Response Block . . . . . . . . . . 17 3.2.6. Mtrace2 Augmented Response Block . . . . . . . . . . 17
3.2.7. Mtrace2 Extended Query Block . . . . . . . . . . . . 18 3.2.7. Mtrace2 Extended Query Block . . . . . . . . . . . . 18
4. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 19 4. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 19
4.1. Receiving Mtrace2 Query . . . . . . . . . . . . . . . . . 19 4.1. Receiving Mtrace2 Query . . . . . . . . . . . . . . . . . 19
4.1.1. Query Packet Verification . . . . . . . . . . . . . . 19 4.1.1. Query Packet Verification . . . . . . . . . . . . . . 19
4.1.2. Query Normal Processing . . . . . . . . . . . . . . . 20 4.1.2. Query Normal Processing . . . . . . . . . . . . . . . 20
4.2. Receiving Mtrace2 Request . . . . . . . . . . . . . . . . 20 4.2. Receiving Mtrace2 Request . . . . . . . . . . . . . . . . 20
4.2.1. Request Packet Verification . . . . . . . . . . . . . 20 4.2.1. Request Packet Verification . . . . . . . . . . . . . 20
4.2.2. Request Normal Processing . . . . . . . . . . . . . . 20 4.2.2. Request Normal Processing . . . . . . . . . . . . . . 20
4.3. Forwarding Mtrace2 Request . . . . . . . . . . . . . . . 22 4.3. Forwarding Mtrace2 Request . . . . . . . . . . . . . . . 22
4.3.1. Destination Address . . . . . . . . . . . . . . . . . 22 4.3.1. Destination Address . . . . . . . . . . . . . . . . . 22
4.3.2. Source Address . . . . . . . . . . . . . . . . . . . 22 4.3.2. Source Address . . . . . . . . . . . . . . . . . . . 23
4.3.3. Appending Standard Response Block . . . . . . . . . . 23 4.3.3. Appending Standard Response Block . . . . . . . . . . 23
4.4. Sending Mtrace2 Reply . . . . . . . . . . . . . . . . . . 23 4.4. Sending Mtrace2 Reply . . . . . . . . . . . . . . . . . . 23
4.4.1. Destination Address . . . . . . . . . . . . . . . . . 23 4.4.1. Destination Address . . . . . . . . . . . . . . . . . 23
4.4.2. Source Address . . . . . . . . . . . . . . . . . . . 23 4.4.2. Source Address . . . . . . . . . . . . . . . . . . . 23
4.4.3. Appending Standard Response Block . . . . . . . . . . 23 4.4.3. Appending Standard Response Block . . . . . . . . . . 24
4.5. Proxying Mtrace2 Query . . . . . . . . . . . . . . . . . 24 4.5. Proxying Mtrace2 Query . . . . . . . . . . . . . . . . . 24
4.6. Hiding Information . . . . . . . . . . . . . . . . . . . 24 4.6. Hiding Information . . . . . . . . . . . . . . . . . . . 24
5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 25 5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 25
5.1. Sending Mtrace2 Query . . . . . . . . . . . . . . . . . . 25 5.1. Sending Mtrace2 Query . . . . . . . . . . . . . . . . . . 25
5.1.1. Destination Address . . . . . . . . . . . . . . . . . 25 5.1.1. Destination Address . . . . . . . . . . . . . . . . . 25
5.1.2. Source Address . . . . . . . . . . . . . . . . . . . 25 5.1.2. Source Address . . . . . . . . . . . . . . . . . . . 25
5.2. Determining the Path . . . . . . . . . . . . . . . . . . 25 5.2. Determining the Path . . . . . . . . . . . . . . . . . . 25
5.3. Collecting Statistics . . . . . . . . . . . . . . . . . . 25 5.3. Collecting Statistics . . . . . . . . . . . . . . . . . . 25
5.4. Last Hop Router (LHR) . . . . . . . . . . . . . . . . . . 25 5.4. Last Hop Router (LHR) . . . . . . . . . . . . . . . . . . 26
5.5. First Hop Router (FHR) . . . . . . . . . . . . . . . . . 26 5.5. First Hop Router (FHR) . . . . . . . . . . . . . . . . . 26
5.6. Broken Intermediate Router . . . . . . . . . . . . . . . 26 5.6. Broken Intermediate Router . . . . . . . . . . . . . . . 26
5.7. Non-Supported Router . . . . . . . . . . . . . . . . . . 26 5.7. Non-Supported Router . . . . . . . . . . . . . . . . . . 26
5.8. Mtrace2 Termination . . . . . . . . . . . . . . . . . . . 27 5.8. Mtrace2 Termination . . . . . . . . . . . . . . . . . . . 27
5.8.1. Arriving at Source . . . . . . . . . . . . . . . . . 27 5.8.1. Arriving at Source . . . . . . . . . . . . . . . . . 27
5.8.2. Fatal Error . . . . . . . . . . . . . . . . . . . . . 27 5.8.2. Fatal Error . . . . . . . . . . . . . . . . . . . . . 27
5.8.3. No Upstream Router . . . . . . . . . . . . . . . . . 27 5.8.3. No Upstream Router . . . . . . . . . . . . . . . . . 27
5.8.4. Reply Timeout . . . . . . . . . . . . . . . . . . . . 27 5.8.4. Reply Timeout . . . . . . . . . . . . . . . . . . . . 27
5.9. Continuing after an Error . . . . . . . . . . . . . . . . 27 5.9. Continuing after an Error . . . . . . . . . . . . . . . . 27
6. Protocol-Specific Considerations . . . . . . . . . . . . . . 28 6. Protocol-Specific Considerations . . . . . . . . . . . . . . 28
skipping to change at page 7, line 26 skipping to change at page 7, line 17
the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2 the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2
messages MUST have a valid UDP checksum. messages MUST have a valid UDP checksum.
Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed. Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed.
For example, if an Mtrace2 Query or Request message arrives in as an For example, if an Mtrace2 Query or Request message arrives in as an
IPv4 packet, all addresses specified in the Mtrace2 messages MUST be IPv4 packet, all addresses specified in the Mtrace2 messages MUST be
IPv4 as well. Same rule applies to IPv6 Mtrace2 messages. IPv4 as well. Same rule applies to IPv6 Mtrace2 messages.
3.1. Mtrace2 TLV format 3.1. Mtrace2 TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value .... | | Type | Length | Value .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 8 bits Type: 8 bits
Describes the format of the Value field. For all the available Describes the format of the Value field. For all the available
types, please see Section 3.2 types, please see Section 3.2
Length: 16 bits Length: 16 bits
Length of Type, Length, and Value fields in octets. Minimum Length of Type, Length, and Value fields in octets. Minimum
length required is 6 octets. The maximum TLV length is not length required is 6 octets. The maximum TLV length is not
skipping to change at page 8, line 4 skipping to change at page 7, line 42
defined; however the entire Mtrace2 packet length should not defined; however the entire Mtrace2 packet length should not
exceed the available MTU. exceed the available MTU.
Value: variable length Value: variable length
The format is based on the Type value. The length of the value The format is based on the Type value. The length of the value
field is Length field minus 3. All reserved fields in the Value field is Length field minus 3. All reserved fields in the Value
field MUST be transmitted as zeros and ignored on receipt. field MUST be transmitted as zeros and ignored on receipt.
3.2. Defined TLVs 3.2. Defined TLVs
The following TLV Types are defined: The following TLV Types are defined:
Code Type Code Type
==== ================================ ==== ================================
0x01 Mtrace2 Query 0x01 Mtrace2 Query
0x02 Mtrace2 Request 0x02 Mtrace2 Request
0x03 Mtrace2 Reply 0x03 Mtrace2 Reply
0x04 Mtrace2 Standard Response Block 0x04 Mtrace2 Standard Response Block
0x05 Mtrace2 Augmented Response Block 0x05 Mtrace2 Augmented Response Block
0x06 Mtrace2 Extended Query Block 0x06 Mtrace2 Extended Query Block
Each Mtrace2 message MUST begin with either a Query, Request or Reply Each Mtrace2 message MUST begin with either a Query, Request or Reply
TLV. The first TLV determines the type of each Mtrace2 message. TLV. The first TLV determines the type of each Mtrace2 message.
Following a Query TLV, there can be a sequence of optional Extended Following a Query TLV, there can be a sequence of optional Extended
Query Blocks. In the case of a Request or a Reply TLV, it is then Query Blocks. In the case of a Request or a Reply TLV, it is then
followed by a sequence of Standard Response Blocks, each from a followed by a sequence of Standard Response Blocks, each from a
multicast router on the path towards the source or the RP. In the multicast router on the path towards the source or the RP. In the
case more information is needed, a Standard Response Block can be case more information is needed, a Standard Response Block can be
followed by one or multiple Augmented Response Blocks. followed by one or multiple Augmented Response Blocks.
skipping to change at page 8, line 36 skipping to change at page 9, line 5
3.2.1. Mtrace2 Query 3.2.1. Mtrace2 Query
An Mtrace2 Query is usually originated by an Mtrace2 client which An Mtrace2 Query is usually originated by an Mtrace2 client which
sends an Mtrace2 Query message to the LHR. When tracing towards the sends an Mtrace2 Query message to the LHR. When tracing towards the
source or the RP, the intermediate routers MUST NOT modify the Query source or the RP, the intermediate routers MUST NOT modify the Query
message except the Type field. message except the Type field.
An Mtrace2 Query message is shown as follows: An Mtrace2 Query message is shown as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | # Hops | | Type | Length | # Hops |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Multicast Address | | Multicast Address |
| | | |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| | | |
| Source Address | | Source Address |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Mtrace2 Client Address | | Mtrace2 Client Address |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Query ID | Client Port # | | Query ID | Client Port # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
# Hops: 8 bits # Hops: 8 bits
This field specifies the maximum number of hops that the Mtrace2 This field specifies the maximum number of hops that the Mtrace2
client wants to trace. If there are some error conditions in the client wants to trace. If there are some error conditions in the
middle of the path that prevent an Mtrace2 Reply from being middle of the path that prevent an Mtrace2 Reply from being
received by the client, the client MAY issues another Mtrace2 received by the client, the client MAY issues another Mtrace2
Query with the lower number of hops until it receives a Reply. Query with the lower number of hops until it receives a Reply.
skipping to change at page 10, line 39 skipping to change at page 11, line 10
There are a number of cases an intermediate router might return a There are a number of cases an intermediate router might return a
Reply before a Request reaches the FHR or the RP. See Section 4.1.1, Reply before a Request reaches the FHR or the RP. See Section 4.1.1,
Section 4.2.2, Section 4.3.3, and Section 4.5 for more details. Section 4.2.2, Section 4.3.3, and Section 4.5 for more details.
3.2.4. IPv4 Mtrace2 Standard Response Block 3.2.4. IPv4 Mtrace2 Standard Response Block
This section describes the message format of an IPv4 Mtrace2 Standard This section describes the message format of an IPv4 Mtrace2 Standard
Response Block. The Type field is 0x04. Response Block. The Type field is 0x04.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | MBZ | | Type | Length | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Query Arrival Time | | Query Arrival Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Incoming Interface Address | | Incoming Interface Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Outgoing Interface Address | | Outgoing Interface Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Upstream Router Address | | Upstream Router Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Input packet count on incoming interface . . Input packet count on incoming interface .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Output packet count on outgoing interface . . Output packet count on outgoing interface .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Total number of packets for this source-group pair . . Total number of packets for this source-group pair .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rtg Protocol | Multicast Rtg Protocol | | Rtg Protocol | Multicast Rtg Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Fwd TTL | MBZ |S| Src Mask |Forwarding Code| | Fwd TTL | MBZ |S| Src Mask |Forwarding Code|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MBZ: 8 bits MBZ: 8 bits
This field must be zeroed on transmission and ignored on This field must be zeroed on transmission and ignored on
reception. reception.
Query Arrival Time: 32 bits Query Arrival Time: 32 bits
The Query Arrival Time is a 32-bit NTP timestamp specifying the The Query Arrival Time is a 32-bit NTP timestamp specifying the
arrival time of the Mtrace2 Query or Request packet at this arrival time of the Mtrace2 Query or Request packet at this
router. The 32-bit form of an NTP timestamp consists of the router. The 32-bit form of an NTP timestamp consists of the
middle 32 bits of the full 64-bit form; that is, the low 16 bits middle 32 bits of the full 64-bit form; that is, the low 16 bits
skipping to change at page 12, line 19 skipping to change at page 12, line 36
Outgoing Interface Address: 32 bits Outgoing Interface Address: 32 bits
This field specifies the address of the interface on which packets This field specifies the address of the interface on which packets
from the source or the RP are expected to transmit towards the from the source or the RP are expected to transmit towards the
receiver, or 0 if unknown or unnumbered. This is also the address receiver, or 0 if unknown or unnumbered. This is also the address
of the interface on which the Mtrace2 Query or Request arrives. of the interface on which the Mtrace2 Query or Request arrives.
Upstream Router Address: 32 bits Upstream Router Address: 32 bits
This field specifies the address of the upstream router from which This field specifies the address of the upstream router from which
this router expects packets from this source. This may be a this router expects packets from this source. This may be a
multicast group (e.g. ALL-[protocol]-ROUTERS.MCAST.NET) if the multicast group (e.g. ALL-[protocol]-ROUTERS.MCAST.NET) if the
upstream router is not known because of the workings of the upstream router is not known because of the workings of the
multicast routing protocol. However, it should be 0 if the multicast routing protocol. However, it should be 0 if the
incoming interface address is unknown or unnumbered. incoming interface address is unknown or unnumbered.
Input packet count on incoming interface: 64 bits Input packet count on incoming interface: 64 bits
This field contains the number of multicast packets received for This field contains the number of multicast packets received for
all groups and sources on the incoming interface, or all 1's if no all groups and sources on the incoming interface, or all 1's if no
count can be reported. This counter may have the same value as count can be reported. This counter may have the same value as
ifHCInMulticastPkts from the IF-MIB [10] for this interface. ifHCInMulticastPkts from the IF-MIB [10] for this interface.
skipping to change at page 14, line 34 skipping to change at page 15, line 5
the message to it. the message to it.
0x81 NO_SPACE There was not enough room to insert another 0x81 NO_SPACE There was not enough room to insert another
Standard Response Block in the packet. Standard Response Block in the packet.
0x83 ADMIN_PROHIB Mtrace2 is administratively prohibited. 0x83 ADMIN_PROHIB Mtrace2 is administratively prohibited.
3.2.5. IPv6 Mtrace2 Standard Response Block 3.2.5. IPv6 Mtrace2 Standard Response Block
This section describes the message format of an IPv6 Mtrace2 Standard This section describes the message format of an IPv6 Mtrace2 Standard
Response Block. The Type field is also 0x04. Response Block. The Type field is also 0x04.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | MBZ | | Type | Length | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Query Arrival Time | | Query Arrival Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Incoming Interface ID | | Incoming Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Outgoing Interface ID | | Outgoing Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
* Local Address * * Local Address *
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
* Remote Address * * Remote Address *
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Input packet count on incoming interface . . Input packet count on incoming interface .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Output packet count on outgoing interface . . Output packet count on outgoing interface .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. Total number of packets for this source-group pair . . Total number of packets for this source-group pair .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rtg Protocol | Multicast Rtg Protocol | | Rtg Protocol | Multicast Rtg Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ 2 |S|Src Prefix Len |Forwarding Code| | MBZ 2 |S|Src Prefix Len |Forwarding Code|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MBZ: 8 bits MBZ: 8 bits
This field must be zeroed on transmission and ignored on This field must be zeroed on transmission and ignored on
reception. reception.
Query Arrival Time: 32 bits Query Arrival Time: 32 bits
Same definition as in IPv4. Same definition as in IPv4.
Incoming Interface ID: 32 bits Incoming Interface ID: 32 bits
This field specifies the interface ID on which packets from the This field specifies the interface ID on which packets from the
skipping to change at page 16, line 13 skipping to change at page 16, line 28
Remote Address: 128 bits Remote Address: 128 bits
This field specifies the address of the upstream router, which, in This field specifies the address of the upstream router, which, in
most cases, is a link-local unicast address for the upstream most cases, is a link-local unicast address for the upstream
router. router.
Although a link-local address does not have enough information to Although a link-local address does not have enough information to
identify a node, it is possible to detect the upstream router with identify a node, it is possible to detect the upstream router with
the assistance of Incoming Interface ID and the current router the assistance of Incoming Interface ID and the current router
address (i.e., Local Address). address (i.e., Local Address).
Note that this may be a multicast group (e.g., Note that this may be a multicast group (e.g., ALL-[protocol]-
ALL-[protocol]-ROUTERS.MCAST.NET) if the upstream router is not ROUTERS.MCAST.NET) if the upstream router is not known because of
known because of the workings of a multicast routing protocol. the workings of a multicast routing protocol. However, it should
However, it should be the unspecified address (::) if the incoming be the unspecified address (::) if the incoming interface address
interface address is unknown. is unknown.
Input packet count on incoming interface: 64 bits Input packet count on incoming interface: 64 bits
Same definition as in IPv4. Same definition as in IPv4.
Output packet count on outgoing interface: 64 bits Output packet count on outgoing interface: 64 bits
Same definition as in IPv4. Same definition as in IPv4.
Total number of packets for this source-group pair: 64 bits Total number of packets for this source-group pair: 64 bits
Same definition as in IPv4, except if the S bit is set (see Same definition as in IPv4, except if the S bit is set (see
below), the count is for the source network, as specified by the below), the count is for the source network, as specified by the
skipping to change at page 17, line 18 skipping to change at page 17, line 32
3.2.6. Mtrace2 Augmented Response Block 3.2.6. Mtrace2 Augmented Response Block
In addition to the Standard Response Block, a multicast router on the In addition to the Standard Response Block, a multicast router on the
traced path can optionally add one or multiple Augmented Response traced path can optionally add one or multiple Augmented Response
Blocks before sending the Request to its upstream router. Blocks before sending the Request to its upstream router.
The Augmented Response Block is flexible for various purposes such as The Augmented Response Block is flexible for various purposes such as
providing diagnosis information (see Section 7) and protocol providing diagnosis information (see Section 7) and protocol
verification. Its Type field is 0x05, and its format is as follows: verification. Its Type field is 0x05, and its format is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | MBZ | | Type | Length | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Augmented Response Type | Value .... | | Augmented Response Type | Value .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MBZ: 8 bits MBZ: 8 bits
This field must be zeroed on transmission and ignored on This field must be zeroed on transmission and ignored on
reception. reception.
Augmented Response Type: 16 bits Augmented Response Type: 16 bits
This field specifies the type of various responses from a This field specifies the type of various responses from a
multicast router that might need to communicate back to the multicast router that might need to communicate back to the
Mtrace2 client as well as the multicast routers on the traced Mtrace2 client as well as the multicast routers on the traced
path. path.
The Augmented Response Type is defined as follows: The Augmented Response Type is defined as follows:
Code Type Code Type
==== =============================================== ==== ===============================================
0x01 # of the returned Standard Response Blocks 0x01 # of the returned Standard Response Blocks
When the NO_SPACE error occurs on a router, the router should send When the NO_SPACE error occurs on a router, the router should send
the original Mtrace2 Request received from the downstream router the original Mtrace2 Request received from the downstream router
as a Reply back to the Mtrace2 client, and continue with a new as a Reply back to the Mtrace2 client, and continue with a new
Mtrace2 Request. In the new Request, the router would add a Mtrace2 Request. In the new Request, the router would add a
Standard Response Block followed by an Augmented Response Block Standard Response Block followed by an Augmented Response Block
with 0x01 as the Augmented Response Type, and the number of the with 0x01 as the Augmented Response Type, and the number of the
returned Mtrace2 Standard Response Blocks as the Value. returned Mtrace2 Standard Response Blocks as the Value.
Each upstream router would recognize the total number of hops the Each upstream router would recognize the total number of hops the
skipping to change at page 18, line 34 skipping to change at page 18, line 46
Query. For example, an Mtrace2 client might be interested in tracing Query. For example, an Mtrace2 client might be interested in tracing
the path the specified source and group would take based on a certain the path the specified source and group would take based on a certain
topology. In which case, the client can pass in the multi-topology topology. In which case, the client can pass in the multi-topology
ID as the Value for an Extended Query Type (see below). The Extended ID as the Value for an Extended Query Type (see below). The Extended
Query Type is extensible and the behavior of the new types will be Query Type is extensible and the behavior of the new types will be
addressed by separate documents. addressed by separate documents.
The Mtrace2 Extended Query Block's Type field is 0x06, and is The Mtrace2 Extended Query Block's Type field is 0x06, and is
formatted as follows: formatted as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | MBZ |T| | Type | Length | MBZ |T|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extended Query Type | Value .... | | Extended Query Type | Value .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MBZ: 7 bits MBZ: 7 bits
This field must be zeroed on transmission and ignored on This field must be zeroed on transmission and ignored on
reception. reception.
T-bit (Transitive Attribute): 1 bit T-bit (Transitive Attribute): 1 bit
If the TLV type is unrecognized by the receiving router, then this If the TLV type is unrecognized by the receiving router, then this
TLV is either discarded or forwarded along with the Query, TLV is either discarded or forwarded along with the Query,
depending on the value of this bit. If this bit is set, then the depending on the value of this bit. If this bit is set, then the
router MUST forward this TLV. If this bit is clear, the router router MUST forward this TLV. If this bit is clear, the router
skipping to change at page 32, line 18 skipping to change at page 32, line 18
Jacobson's slides from the 30th IETF, and the implementation in Jacobson's slides from the 30th IETF, and the implementation in
mrouted 3.3 by Ajit Thyagarajan. Van's original slides credit Steve mrouted 3.3 by Ajit Thyagarajan. Van's original slides credit Steve
Casner, Steve Deering, Dino Farinacci and Deb Agrawal. The original Casner, Steve Deering, Dino Farinacci and Deb Agrawal. The original
multicast traceroute client, mtrace (version 1), has been implemented multicast traceroute client, mtrace (version 1), has been implemented
by Ajit Thyagarajan, Steve Casner and Bill Fenner. The idea of the by Ajit Thyagarajan, Steve Casner and Bill Fenner. The idea of the
"S" bit to allow statistics for a source subnet is due to Tom "S" bit to allow statistics for a source subnet is due to Tom
Pusateri. Pusateri.
For the Mtrace version 2 specification, the authors would like to For the Mtrace version 2 specification, the authors would like to
give special thanks to Tatsuya Jinmei, Bill Fenner, and Steve Casner. give special thanks to Tatsuya Jinmei, Bill Fenner, and Steve Casner.
Also, extensive comments were received from David L. Black, Ronald Also, extensive comments were received from David L. Black, Ronald
Bonica, Yiqun Cai, Liu Hui, Bharat Joshi, Robert W. Kebler, Heidi Ou, Bonica, Yiqun Cai, Liu Hui, Bharat Joshi, Robert W. Kebler, Heidi
Pekka Savola, Shinsuke Suzuki, Dave Thaler, Achmad Husni Thamrin, and Ou, Pekka Savola, Shinsuke Suzuki, Dave Thaler, Achmad Husni Thamrin,
Cao Wei. and Cao Wei.
11. References 11. References
11.1. Normative References 11.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to indicate [1] Bradner, S., "Key words for use in RFCs to indicate
requirement levels", RFC 2119, March 1997. requirement levels", RFC 2119, March 1997.
[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [2] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
skipping to change at page 32, line 49 skipping to change at page 32, line 49
[5] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [5] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol Specification (Revised)", RFC 4601, August 2006.
[6] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, [6] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR- "Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, October 2007. PIM)", RFC 5015, October 2007.
[7] Fenner, B., He, H., Haberman, B., and H. Sandick, [7] Fenner, B., He, H., Haberman, B., and H. Sandick,
"Internet Group Management Protocol (IGMP) / Multicast "Internet Group Management Protocol (IGMP) / Multicast
Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP Listener Discovery (MLD)-Based Multicast Forwarding
/MLD Proxying")", RFC 4605, August 2006. ("IGMP/MLD Proxying")", RFC 4605, August 2006.
11.2. Informative References 11.2. Informative References
[8] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [8] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, October 2002. 3", RFC 3376, October 2002.
[9] Draves, R. and D. Thaler, "Default Router Preferences and [9] Draves, R. and D. Thaler, "Default Router Preferences and
More-Specific Routes", RFC 4191, November 2005. More-Specific Routes", RFC 4191, November 2005.
skipping to change at page 33, line 39 skipping to change at line 1532
Hitoshi Asaeda Hitoshi Asaeda
National Institute of Information and Communications Technology National Institute of Information and Communications Technology
4-2-1 Nukui-Kitamachi 4-2-1 Nukui-Kitamachi
Koganei, Tokyo 184-8795 Koganei, Tokyo 184-8795
Japan Japan
Email: asaeda@nict.go.jp Email: asaeda@nict.go.jp
WeeSan Lee (editor) WeeSan Lee (editor)
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089-1206
US
Email: weesan@juniper.net
 End of changes. 22 change blocks. 
134 lines changed or deleted 135 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/