draft-ietf-mboned-mtrace-v2-04.txt   draft-ietf-mboned-mtrace-v2-05.txt 
MBONED Working Group H. Asaeda MBONED Working Group H. Asaeda
Internet-Draft Keio University Internet-Draft Keio University
Intended status: Standards Track T. Jinmei Intended status: Standards Track T. Jinmei
Expires: January 14, 2010 ISC Expires: April 29, 2010 ISC
W. Fenner W. Fenner
Arastra, Inc. Arastra, Inc.
S. Casner S. Casner
Packet Design, Inc. Packet Design, Inc.
July 13, 2009 October 26, 2009
Mtrace Version 2: Traceroute Facility for IP Multicast Mtrace Version 2: Traceroute Facility for IP Multicast
draft-ietf-mboned-mtrace-v2-04 draft-ietf-mboned-mtrace-v2-05
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. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2010. This Internet-Draft will expire on April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
skipping to change at page 3, line 37 skipping to change at page 3, line 37
5.6. Client Port # . . . . . . . . . . . . . . . . . . . . . . 11 5.6. Client Port # . . . . . . . . . . . . . . . . . . . . . . 11
6. IPv4 Mtrace2 Standard Response Block . . . . . . . . . . . . . 12 6. IPv4 Mtrace2 Standard Response Block . . . . . . . . . . . . . 12
6.1. Query Arrival Time: 32 bits . . . . . . . . . . . . . . . 12 6.1. Query Arrival Time: 32 bits . . . . . . . . . . . . . . . 12
6.2. Incoming Interface Address: 32 bits . . . . . . . . . . . 13 6.2. Incoming Interface Address: 32 bits . . . . . . . . . . . 13
6.3. Outgoing Interface Address: 32 bits . . . . . . . . . . . 13 6.3. Outgoing Interface Address: 32 bits . . . . . . . . . . . 13
6.4. Previous-Hop Router Address: 32 bits . . . . . . . . . . . 13 6.4. Previous-Hop Router Address: 32 bits . . . . . . . . . . . 13
6.5. Input packet count on incoming interface: 64 bits . . . . 13 6.5. Input packet count on incoming interface: 64 bits . . . . 13
6.6. Output packet count on incoming interface: 64 bits . . . . 13 6.6. Output packet count on incoming interface: 64 bits . . . . 13
6.7. Total number of packets for this source-group pair: 64 6.7. Total number of packets for this source-group pair: 64
bits . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 bits . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.8. Rtg Protocol: 8 bits . . . . . . . . . . . . . . . . . . . 14 6.8. Rtg Protocol: 16 bits . . . . . . . . . . . . . . . . . . 14
6.9. Fwd TTL: 8 bits . . . . . . . . . . . . . . . . . . . . . 14 6.9. Multicast Rtg Protocol: 16 bits . . . . . . . . . . . . . 14
6.10. MBZ: 1 bit . . . . . . . . . . . . . . . . . . . . . . . . 14 6.10. Fwd TTL: 8 bits . . . . . . . . . . . . . . . . . . . . . 14
6.11. S: 1 bit . . . . . . . . . . . . . . . . . . . . . . . . . 14 6.11. MBZ: 8 bit . . . . . . . . . . . . . . . . . . . . . . . . 14
6.12. Src Mask: 6 bits . . . . . . . . . . . . . . . . . . . . . 14 6.12. S: 1 bit . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.13. Forwarding Code: 8 bits . . . . . . . . . . . . . . . . . 14 6.13. Src Mask: 7 bits . . . . . . . . . . . . . . . . . . . . . 14
6.14. Forwarding Code: 8 bits . . . . . . . . . . . . . . . . . 14
7. IPv6 Mtrace2 Standard Response Block . . . . . . . . . . . . . 17 7. IPv6 Mtrace2 Standard Response Block . . . . . . . . . . . . . 17
7.1. Query Arrival Time: 32 bits . . . . . . . . . . . . . . . 17 7.1. Query Arrival Time: 32 bits . . . . . . . . . . . . . . . 17
7.2. Incoming Interface ID: 32 bits . . . . . . . . . . . . . . 17 7.2. Incoming Interface ID: 32 bits . . . . . . . . . . . . . . 17
7.3. Outgoing Interface ID: 32 bits . . . . . . . . . . . . . . 18 7.3. Outgoing Interface ID: 32 bits . . . . . . . . . . . . . . 18
7.4. Local Address . . . . . . . . . . . . . . . . . . . . . . 18 7.4. Local Address . . . . . . . . . . . . . . . . . . . . . . 18
7.5. Remote Address . . . . . . . . . . . . . . . . . . . . . . 18 7.5. Remote Address . . . . . . . . . . . . . . . . . . . . . . 18
7.6. Input packet count on incoming interface . . . . . . . . . 18 7.6. Input packet count on incoming interface . . . . . . . . . 18
7.7. Output packet count on incoming interface . . . . . . . . 18 7.7. Output packet count on incoming interface . . . . . . . . 18
7.8. Total number of packets for this source-group pair . . . . 18 7.8. Total number of packets for this source-group pair . . . . 18
7.9. Rtg Protocol: 8 bits . . . . . . . . . . . . . . . . . . . 19 7.9. Rtg Protocol: 16 bits . . . . . . . . . . . . . . . . . . 19
7.10. MBZ: 7 bits . . . . . . . . . . . . . . . . . . . . . . . 19 7.10. Multicast Rtg Protocol: 16 bits . . . . . . . . . . . . . 19
7.11. S: 1 bit . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.11. MBZ: 15 bits . . . . . . . . . . . . . . . . . . . . . . . 19
7.12. Src Prefix Len: 8 bits . . . . . . . . . . . . . . . . . . 19 7.12. S: 1 bit . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.13. Forwarding Code: 8 bits . . . . . . . . . . . . . . . . . 19 7.13. Src Prefix Len: 8 bits . . . . . . . . . . . . . . . . . . 19
7.14. Forwarding Code: 8 bits . . . . . . . . . . . . . . . . . 19
8. Mtrace2 Augmented Response Block . . . . . . . . . . . . . . . 20 8. Mtrace2 Augmented Response Block . . . . . . . . . . . . . . . 20
9. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 21 9. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 21
9.1. Traceroute Query . . . . . . . . . . . . . . . . . . . . . 21 9.1. Traceroute Query . . . . . . . . . . . . . . . . . . . . . 21
9.1.1. Packet Verification . . . . . . . . . . . . . . . . . 21 9.1.1. Packet Verification . . . . . . . . . . . . . . . . . 21
9.1.2. Normal Processing . . . . . . . . . . . . . . . . . . 21 9.1.2. Normal Processing . . . . . . . . . . . . . . . . . . 21
9.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . . . 21 9.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . . . 21
9.2.1. Packet Verification . . . . . . . . . . . . . . . . . 22 9.2.1. Packet Verification . . . . . . . . . . . . . . . . . 22
9.2.2. Normal Processing . . . . . . . . . . . . . . . . . . 22 9.2.2. Normal Processing . . . . . . . . . . . . . . . . . . 22
9.3. Forwarding Mtrace2 Requests . . . . . . . . . . . . . . . 24 9.3. Forwarding Mtrace2 Requests . . . . . . . . . . . . . . . 24
9.4. Sending Mtrace2 Responses . . . . . . . . . . . . . . . . 24 9.4. Sending Mtrace2 Responses . . . . . . . . . . . . . . . . 24
skipping to change at page 12, line 34 skipping to change at page 12, line 34
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. 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 .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |M| | | | | Rtg Protocol | Multicast Rtg Protocol |
| Rtg Protocol | Fwd TTL |B|S| Src Mask |Forwarding Code| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |Z| | | | | Fwd TTL | MBZ |S| Src Mask |Forwarding Code|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6.1. Query Arrival Time: 32 bits 6.1. 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 traceroute request packet at this router. The arrival time of the traceroute request packet at this router. The
32-bit form of an NTP timestamp consists of the middle 32 bits of 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 of the integer part and full 64-bit form; that is, the low 16 bits of the integer part and
the high 16 bits of the fractional part. the high 16 bits of the fractional part.
skipping to change at page 13, line 12 skipping to change at page 13, line 12
query_arrival_time query_arrival_time
= (tv.tv_sec + 32384) << 16 + ((tv.tv_usec << 10) / 15625) = (tv.tv_sec + 32384) << 16 + ((tv.tv_usec << 10) / 15625)
The constant 32384 is the number of seconds from Jan 1, 1900 to Jan The constant 32384 is the number of seconds from Jan 1, 1900 to Jan
1, 1970 truncated to 16 bits. ((tv.tv_usec << 10) / 15625) is a 1, 1970 truncated to 16 bits. ((tv.tv_usec << 10) / 15625) is a
reduction of ((tv.tv_usec / 100000000) << 16). reduction of ((tv.tv_usec / 100000000) << 16).
6.2. Incoming Interface Address: 32 bits 6.2. Incoming 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 this source and group are expected to arrive, or 0 if unknown. from this source and group are expected to arrive, or 0 if unknown or
unnumbered.
6.3. Outgoing Interface Address: 32 bits 6.3. 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 this source and group flow to the specified destination, or 0 if from this source and group flow to the specified destination, or 0 if
unknown. unknown or unnumbered.
6.4. Previous-Hop Router Address: 32 bits 6.4. Previous-Hop Router Address: 32 bits
This field specifies the router from which this router expects This field specifies the router from which this router expects
packets from this source. This may be a multicast group (e.g. ALL- packets from this source. This may be a multicast group (e.g. ALL-
[protocol]-ROUTERS.MCAST.NET) if the previous hop is not known [protocol]-ROUTERS.MCAST.NET) if the previous hop is not known
because of the workings of the multicast routing protocol. However, because of the workings of the multicast routing protocol. However,
it should be 0 if the incoming interface address is unknown. it should be 0 if the incoming interface address is unknown or
unnumbered.
6.5. Input packet count on incoming interface: 64 bits 6.5. Input packet count on incoming interface: 64 bits
This field contains the number of multicast packets received for all This field contains the number of multicast packets received for all
groups and sources on the incoming interface, or "all 1" if no count groups and sources on the incoming interface, or "all 1" if no count
can be reported. This counter may have the same value as can be reported. This counter may have the same value as
ifHCInMulticastPkts from the IF-MIB [14] for this interface. ifHCInMulticastPkts from the IF-MIB [14] for this interface.
6.6. Output packet count on incoming interface: 64 bits 6.6. Output packet count on incoming interface: 64 bits
skipping to change at page 14, line 5 skipping to change at page 14, line 7
This field counts the number of packets from the specified source This field counts the number of packets from the specified source
forwarded by this router to the specified group, or "all 1" if no forwarded by this router to the specified group, or "all 1" if no
count can be reported. If the S bit is set, the count is for the count can be reported. If the S bit is set, the count is for the
source network, as specified by the Src Mask field. If the S bit is source network, as specified by the Src Mask field. If the S bit is
set and the Src Mask field is 63, indicating no source-specific set and the Src Mask field is 63, indicating no source-specific
state, the count is for all sources sending to this group. This state, the count is for all sources sending to this group. This
counter should have the same value as ipMcastRoutePkts from the counter should have the same value as ipMcastRoutePkts from the
IPMROUTE-STD-MIB [15] for this forwarding entry. IPMROUTE-STD-MIB [15] for this forwarding entry.
6.8. Rtg Protocol: 8 bits 6.8. Rtg Protocol: 16 bits
This field describes the routing protocol in use between this router This field describes the routing protocol used to decide an RPF
and the previous-hop router. Specified values include: interface for the requested source. This value should have the same
value as ipMcastRouteRtProtocol from the IPMROUTE-STD-MIB [15] for
this entry. If the router does not able to obtain this value, "all
0" must be specified.
0 Unknown 6.9. Multicast Rtg Protocol: 16 bits
1 PIM
2 PIM using special routing table
3 PIM using a static route
4 PIM using MBGP route
5 PIM using state created by Assert processing
6 Bi-directional PIM
7 IGMP/MLD proxy
8 AMT relay
9 AMT gateway
10 AMT gateway with IGMP/MLD proxy
To obtain these values, multicast routers access to This field describes the multicast routing protocol in use between
ipMcastRouteProtocol, ipMcastRouteRtProtocol, and ipMcastRouteRtType this router and the previous-hop router. This value should have the
in IpMcastRouteEntry specified in IPMROUTE-STD-MIB [15], and combine same value as ipMcastRouteProtocol from the IPMROUTE-STD-MIB [15] for
these MIB values to recognize above routing protocol values. this entry. If the router does not able to obtain this value, "all
0" must be specified.
6.9. Fwd TTL: 8 bits 6.10. Fwd TTL: 8 bits
This field contains the TTL that a packet is required to have before This field contains the TTL that a packet is required to have before
it will be forwarded over the outgoing interface. it will be forwarded over the outgoing interface.
6.10. MBZ: 1 bit 6.11. MBZ: 8 bit
Must be zeroed on transmission and ignored on reception. Must be zeroed on transmission and ignored on reception.
6.11. S: 1 bit 6.12. S: 1 bit
This S bit indicates that the packet count for the source-group pair This S bit indicates that the packet count for the source-group pair
is for the source network, as determined by masking the source is for the source network, as determined by masking the source
address with the Src Mask field. address with the Src Mask field.
6.12. Src Mask: 6 bits 6.13. Src Mask: 7 bits
This field contains the number of 1's in the netmask this router has This field contains the number of 1's in the netmask this router has
for the source (i.e. a value of 24 means the netmask is 0xffffff00). for the source (i.e. a value of 24 means the netmask is 0xffffff00).
If the router is forwarding solely on group state, this field is set If the router is forwarding solely on group state, this field is set
to 63 (0x3f). to 127 (0x7f).
6.13. Forwarding Code: 8 bits 6.14. Forwarding Code: 8 bits
This field contains a forwarding information/error code. Section 9.2 This field contains a forwarding information/error code. Section 9.2
explains how and when the forwarding code is filled. Defined values explains how and when the forwarding code is filled. Defined values
are as follows; are as follows;
Value Name Description Value Name Description
----- -------------- ------------------------------------------- ----- -------------- -------------------------------------------
0x00 NO_ERROR No error 0x00 NO_ERROR No error
0x01 WRONG_IF Mtrace2 request arrived on an interface 0x01 WRONG_IF Mtrace2 request arrived on an interface
to which this router would not forward for to which this router would not forward for
this source, group, destination. this source, group, destination.
0x02 PRUNE_SENT This router has sent a prune upstream which 0x02 PRUNE_SENT This router has sent a prune upstream which
applies to the source and group in the applies to the source and group in the
skipping to change at page 17, line 40 skipping to change at page 17, line 40
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
. 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 | MBZ |S|Src Prefix Len |Forwarding Code| | Rtg Protocol | Multicast Rtg Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ |S|Src Prefix Len |Forwarding Code|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7.1. Query Arrival Time: 32 bits 7.1. Query Arrival Time: 32 bits
Same definition described in Section 6.1 Same definition described in Section 6.1
7.2. Incoming Interface ID: 32 bits 7.2. Incoming Interface ID: 32 bits
This field specifies the interface ID on which packets from this This field specifies the interface ID on which packets from this
source and group are expected to arrive, or 0 if unknown. This ID source and group are expected to arrive, or 0 if unknown. This ID
skipping to change at page 19, line 4 skipping to change at page 19, line 7
Same definition described in Section 6.6 Same definition described in Section 6.6
7.8. Total number of packets for this source-group pair 7.8. Total number of packets for this source-group pair
This field counts the number of packets from the specified source This field counts the number of packets from the specified source
forwarded by this router to the specified group, or "all 1" if no forwarded by this router to the specified group, or "all 1" if no
count can be reported. If the S bit is set, the count is for the count can be reported. If the S bit is set, the count is for the
source network, as specified by the Src Prefix Len field. If the S source network, as specified by the Src Prefix Len field. If the S
bit is set and the Src Prefix Len field is 255, indicating no source- bit is set and the Src Prefix Len field is 255, indicating no source-
specific state, the count is for all sources sending to this group. specific state, the count is for all sources sending to this group.
This counter should have the same value as ipMcastRoutePkts from the This counter should have the same value as ipMcastRoutePkts from the
IPMROUTE-STD-MIB for this forwarding entry. IPMROUTE-STD-MIB for this forwarding entry.
7.9. Rtg Protocol: 8 bits 7.9. Rtg Protocol: 16 bits
Same definition described in Section 6.8 Same definition described in Section 6.8
7.10. MBZ: 7 bits 7.10. Multicast Rtg Protocol: 16 bits
Same definition described in Section 6.9
7.11. MBZ: 15 bits
Must be zeroed on transmission and ignored on reception. Must be zeroed on transmission and ignored on reception.
7.11. S: 1 bit 7.12. S: 1 bit
This S bit indicates that the packet count for the source-group pair This S bit indicates that the packet count for the source-group pair
is for the source network, as determined by masking the source is for the source network, as determined by masking the source
address with the Src Prefix Len field. address with the Src Prefix Len field.
7.12. Src Prefix Len: 8 bits 7.13. Src Prefix Len: 8 bits
This field contains the prefix length this router has for the source. This field contains the prefix length this router has for the source.
If the router is forwarding solely on group state, this field is set If the router is forwarding solely on group state, this field is set
to 255 (0xff) to 255 (0xff)
7.13. Forwarding Code: 8 bits 7.14. Forwarding Code: 8 bits
Same definition described in Section 6.13 Same definition described in Section 6.14
8. Mtrace2 Augmented Response Block 8. 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
path will be able to add "augumented response block" when it sends path will be able to add "augumented response block" when it sends
the request to its upstream router or sends the response to the the request to its upstream router or sends the response to the
Destination Address. This augmented response block is flexible to Destination Address. This augmented response block is flexible to
add various information. add various information.
0 1 2 3 0 1 2 3
skipping to change at page 22, line 11 skipping to change at page 22, line 11
response blocks filled in, and uses TLV type 0x1 for IPv4 and IPv6 response blocks filled in, and uses TLV type 0x1 for IPv4 and IPv6
mtrace2. Routers can tell the difference between Queries and mtrace2. Routers can tell the difference between Queries and
Requests by checking the length of the packet. Requests by checking the length of the packet.
9.2.1. Packet Verification 9.2.1. Packet Verification
If the mtrace2 Request does not come from an adjacent host or router, If the mtrace2 Request does not come from an adjacent host or router,
it MUST be silently ignored. If the mtrace2 Request is not addressed it MUST be silently ignored. If the mtrace2 Request is not addressed
to this router, or if the Request is addressed to a multicast group to this router, or if the Request is addressed to a multicast group
which is not a link-scoped group (i.e. 224/24 for IPv4, FFx2::/16 [3] which is not a link-scoped group (i.e. 224/24 for IPv4, FFx2::/16 [3]
for IPv6), it MUST be silently ignored. The router's neighbor for IPv6), it MUST be silently ignored. It is highly RECOMMENDED for
information, e.g. ARP database or PIM neighbor list, should be used the router to use GTSM [16] to determine whether the host or router
to determine whether the host or router is adjacent or not. is adjacent or not.
9.2.2. Normal Processing 9.2.2. Normal Processing
When a router receives an mtrace2 Request, it performs the following When a router receives an mtrace2 Request, it performs the following
steps. Note that it is possible to have multiple situations covered steps. Note that it is possible to have multiple situations covered
by the Forwarding Codes. The first one encountered is the one that by the Forwarding Codes. The first one encountered is the one that
is reported, i.e. all "note forwarding code N" should be interpreted is reported, i.e. all "note forwarding code N" should be interpreted
as "if forwarding code is not already set, set forwarding code to N". as "if forwarding code is not already set, set forwarding code to N".
1. If there is room in the current buffer (or the router can 1. If there is room in the current buffer (or the router can
skipping to change at page 29, line 52 skipping to change at page 29, line 52
When traffic is flowing, PIM Dense Mode routers know whether or not When traffic is flowing, PIM Dense Mode routers know whether or not
they are the last-hop forwarder for the link (because they won or they are the last-hop forwarder for the link (because they won or
lost an Assert battle) and know who the previous hop is (because it lost an Assert battle) and know who the previous hop is (because it
won an Assert battle). Therefore, multicast traceroute is always won an Assert battle). Therefore, multicast traceroute is always
able to follow the proper path when traffic is flowing. able to follow the proper path when traffic is flowing.
11.4. IGMP/MLD Proxy 11.4. IGMP/MLD Proxy
When a mtrace2 Query packet reaches an incoming interface of IGMP/MLD When a mtrace2 Query packet reaches an incoming interface of IGMP/MLD
Proxy [10], it put a WRONG_IF (0x01) value in Forwarding Code of Proxy [10], it puts a WRONG_IF (0x01) value in Forwarding Code of
mtrace2 standard response block (as in Section 6.13) and sends the mtrace2 standard response block (as in Section 6.14) and sends the
mtrace2 response back to the Destination Address. When a mtrace2 mtrace2 response back to the Destination Address. When a mtrace2
Query packet reaches an outgoing interface of IGMP/MLD proxy, it is Query packet reaches an outgoing interface of IGMP/MLD proxy, it is
forwarded through its incoming interface towards the upstream router. forwarded through its incoming interface towards the upstream router.
11.5. AMT 11.5. AMT
AMT [11] provides the multicast connectivity to the unicast-only AMT [11] provides the multicast connectivity to the unicast-only
inter-network. To do this, multicast packets being sent to or from a inter-network. To do this, multicast packets being sent to or from a
site are encapsulated in unicast packets. When a mtrace2 query site are encapsulated in unicast packets. When a mtrace2 query
packet reaches an AMT pseudo-interface of an AMT gateway, the AMT packet reaches an AMT pseudo-interface of an AMT gateway, the AMT
skipping to change at page 35, line 20 skipping to change at page 35, line 20
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. by Ajit Thyagarajan, Steve Casner and Bill Fenner.
The idea of unicasting a multicast traceroute Query to the The idea of unicasting a multicast traceroute Query to the
destination of the trace with Router Alert set is due to Tony destination of the trace with Router Alert set is due to Tony
Ballardie. The idea of the "S" bit to allow statistics for a source Ballardie. The idea of the "S" bit to allow statistics for a source
subnet is due to Tom Pusateri. subnet is due to Tom Pusateri.
For the mtrace version 2 specification, extensive comments were For the mtrace version 2 specification, extensive comments were
received from Yiqun Cai, Liu Hui, Bharat Joshi, Shinsuke Suzuki, received from Yiqun Cai, Liu Hui, Bharat Joshi, Pekka Savola,
Achmad Husni Thamrin, and Cao Wei. Shinsuke Suzuki, Dave Thaler, Achmad Husni Thamrin, and Cao Wei.
16. References 16. References
16.1. Normative References 16.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to indicate requirement [1] Bradner, S., "Key words for use in RFCs to indicate requirement
levels", RFC 2119, March 1997. levels", RFC 2119, March 1997.
[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) [2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998. Specification", RFC 2460, December 1998.
skipping to change at page 38, line 5 skipping to change at page 37, line 14
[13] Draves, R. and D. Thaler, "Default Router Preferences and More- [13] Draves, R. and D. Thaler, "Default Router Preferences and More-
Specific Routes", RFC 4191, November 2005. Specific Routes", RFC 4191, November 2005.
[14] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", [14] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
RFC 2863, June 2000. RFC 2863, June 2000.
[15] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast MIB", [15] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast MIB",
RFC 5132, December 2007. RFC 5132, December 2007.
[16] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. Pignataro,
"The Generalized TTL Security Mechanism (GTSM)", RFC 5082,
October 2007.
Authors' Addresses Authors' Addresses
Hitoshi Asaeda Hitoshi Asaeda
Keio University Keio University
Graduate School of Media and Governance Graduate School of Media and Governance
Fujisawa, Kanagawa 252-8520 Fujisawa, Kanagawa 252-8520
Japan Japan
Email: asaeda@wide.ad.jp Email: asaeda@wide.ad.jp
URI: http://www.sfc.wide.ad.jp/~asaeda/ URI: http://www.sfc.wide.ad.jp/~asaeda/
 End of changes. 33 change blocks. 
61 lines changed or deleted 67 lines changed or added

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