idnits 2.17.1 draft-ietf-mboned-mtrace-v2-21.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2, 2017) is 2367 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MBONED Working Group H. Asaeda 3 Internet-Draft NICT 4 Intended status: Standards Track K. Meyer 5 Expires: May 6, 2018 Cisco 6 W. Lee, Ed. 7 November 2, 2017 9 Mtrace Version 2: Traceroute Facility for IP Multicast 10 draft-ietf-mboned-mtrace-v2-21 12 Abstract 14 This document describes the IP multicast traceroute facility, named 15 Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2 16 requires special implementations on the part of routers. This 17 specification describes the required functionality in multicast 18 routers, as well as how an Mtrace2 client invokes a query and 19 receives a reply. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 6, 2018. 38 Copyright Notice 40 Copyright (c) 2017 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 This document may contain material from IETF Documents or IETF 54 Contributions published or made publicly available before November 55 10, 2008. The person(s) controlling the copyright in some of this 56 material may not have granted the IETF Trust the right to allow 57 modifications of such material outside the IETF Standards Process. 58 Without obtaining an adequate license from the person(s) controlling 59 the copyright in such materials, this document may not be modified 60 outside the IETF Standards Process, and derivative works of it may 61 not be created outside the IETF Standards Process, except to format 62 it for publication as an RFC or to translate it into languages other 63 than English. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 6 70 3. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 7 71 3.1. Mtrace2 TLV format . . . . . . . . . . . . . . . . . . . 8 72 3.2. Defined TLVs . . . . . . . . . . . . . . . . . . . . . . 8 73 3.2.1. Mtrace2 Query . . . . . . . . . . . . . . . . . . . . 9 74 3.2.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . 11 75 3.2.3. Mtrace2 Reply . . . . . . . . . . . . . . . . . . . . 11 76 3.2.4. IPv4 Mtrace2 Standard Response Block . . . . . . . . 12 77 3.2.5. IPv6 Mtrace2 Standard Response Block . . . . . . . . 15 78 3.2.6. Mtrace2 Augmented Response Block . . . . . . . . . . 18 79 3.2.7. Mtrace2 Extended Query Block . . . . . . . . . . . . 19 80 4. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 20 81 4.1. Receiving Mtrace2 Query . . . . . . . . . . . . . . . . . 20 82 4.1.1. Query Packet Verification . . . . . . . . . . . . . . 20 83 4.1.2. Query Normal Processing . . . . . . . . . . . . . . . 21 84 4.2. Receiving Mtrace2 Request . . . . . . . . . . . . . . . . 21 85 4.2.1. Request Packet Verification . . . . . . . . . . . . . 21 86 4.2.2. Request Normal Processing . . . . . . . . . . . . . . 22 87 4.3. Forwarding Mtrace2 Request . . . . . . . . . . . . . . . 23 88 4.3.1. Destination Address . . . . . . . . . . . . . . . . . 24 89 4.3.2. Source Address . . . . . . . . . . . . . . . . . . . 24 90 4.3.3. Appending Standard Response Block . . . . . . . . . . 24 91 4.4. Sending Mtrace2 Reply . . . . . . . . . . . . . . . . . . 25 92 4.4.1. Destination Address . . . . . . . . . . . . . . . . . 25 93 4.4.2. Source Address . . . . . . . . . . . . . . . . . . . 25 94 4.4.3. Appending Standard Response Block . . . . . . . . . . 25 95 4.5. Proxying Mtrace2 Query . . . . . . . . . . . . . . . . . 25 96 4.6. Hiding Information . . . . . . . . . . . . . . . . . . . 26 98 5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 26 99 5.1. Sending Mtrace2 Query . . . . . . . . . . . . . . . . . . 26 100 5.1.1. Destination Address . . . . . . . . . . . . . . . . . 27 101 5.1.2. Source Address . . . . . . . . . . . . . . . . . . . 27 102 5.2. Determining the Path . . . . . . . . . . . . . . . . . . 27 103 5.3. Collecting Statistics . . . . . . . . . . . . . . . . . . 27 104 5.4. Last Hop Router (LHR) . . . . . . . . . . . . . . . . . . 27 105 5.5. First Hop Router (FHR) . . . . . . . . . . . . . . . . . 28 106 5.6. Broken Intermediate Router . . . . . . . . . . . . . . . 28 107 5.7. Non-Supported Router . . . . . . . . . . . . . . . . . . 28 108 5.8. Mtrace2 Termination . . . . . . . . . . . . . . . . . . . 28 109 5.8.1. Arriving at Source . . . . . . . . . . . . . . . . . 28 110 5.8.2. Fatal Error . . . . . . . . . . . . . . . . . . . . . 29 111 5.8.3. No Upstream Router . . . . . . . . . . . . . . . . . 29 112 5.8.4. Reply Timeout . . . . . . . . . . . . . . . . . . . . 29 113 5.9. Continuing after an Error . . . . . . . . . . . . . . . . 29 114 6. Protocol-Specific Considerations . . . . . . . . . . . . . . 29 115 6.1. PIM-SM . . . . . . . . . . . . . . . . . . . . . . . . . 30 116 6.2. Bi-Directional PIM . . . . . . . . . . . . . . . . . . . 30 117 6.3. PIM-DM . . . . . . . . . . . . . . . . . . . . . . . . . 30 118 6.4. IGMP/MLD Proxy . . . . . . . . . . . . . . . . . . . . . 30 119 7. Problem Diagnosis . . . . . . . . . . . . . . . . . . . . . . 31 120 7.1. Forwarding Inconsistencies . . . . . . . . . . . . . . . 31 121 7.2. TTL or Hop Limit Problems . . . . . . . . . . . . . . . . 31 122 7.3. Packet Loss . . . . . . . . . . . . . . . . . . . . . . . 31 123 7.4. Link Utilization . . . . . . . . . . . . . . . . . . . . 32 124 7.5. Time Delay . . . . . . . . . . . . . . . . . . . . . . . 32 125 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 126 8.1. "Mtrace2 Forwarding Codes" Registry . . . . . . . . . . . 32 127 8.2. "Mtrace2 TLV Types" registry . . . . . . . . . . . . . . 32 128 8.3. UDP Destination Port . . . . . . . . . . . . . . . . . . 33 129 9. Security Considerations . . . . . . . . . . . . . . . . . . . 33 130 9.1. Addresses in Mtrace2 Header . . . . . . . . . . . . . . . 33 131 9.2. Filtering of Clients . . . . . . . . . . . . . . . . . . 33 132 9.3. Topology Discovery . . . . . . . . . . . . . . . . . . . 33 133 9.4. Characteristics of Multicast Channel . . . . . . . . . . 33 134 9.5. Limiting Query/Request Rates . . . . . . . . . . . . . . 33 135 9.6. Limiting Reply Rates . . . . . . . . . . . . . . . . . . 34 136 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 137 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 138 11.1. Normative References . . . . . . . . . . . . . . . . . . 34 139 11.2. Informative References . . . . . . . . . . . . . . . . . 35 140 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 142 1. Introduction 144 Given a multicast distribution tree, tracing from a multicast source 145 to a receiver is difficult, since we do not know on which branch of 146 the multicast tree the receiver lies. This means that we have to 147 flood the whole tree to find the path from a source to a receiver. 148 On the other hand, walking up the tree from a receiver to a source is 149 easy, as most existing multicast routing protocols know the upstream 150 router for each source. Tracing from a receiver to a source can 151 involve only the routers on the direct path. 153 This document specifies the multicast traceroute facility named 154 Mtrace version 2 or Mtrace2 which allows the tracing of an IP 155 multicast routing path. Mtrace2 is usually initiated from an Mtrace2 156 client by sending an Mtrace2 Query to a Last Hop Router (LHR) or to a 157 Rendezvous Point (RP). The RP is a special router where sources and 158 receivers meet in PIM-SM [5]. From the LHR/RP receiving the query, 159 the tracing is directed towards a specified source if a source 160 address is specified and source specific state exists on the 161 receiving router. If no source address is specified or if no source 162 specific state exists on a receiving LHR, the tracing is directed 163 toward the RP for the specified group address. Moreover, Mtrace2 164 provides additional information such as the packet rates and losses, 165 as well as other diagnostic information. Mtrace2 is primarily 166 intended for the following purposes: 168 o To trace the path that a packet would take from a source to a 169 receiver. 171 o To isolate packet loss problems (e.g., congestion). 173 o To isolate configuration problems (e.g., TTL threshold). 175 Figure 1 shows a typical case on how Mtrace2 is used. FHR represents 176 the first-hop router, LHR represents the last-hop router, and the 177 arrow lines represent the Mtrace2 messages that are sent from one 178 node to another. The numbers before the Mtrace2 messages represent 179 the sequence of the messages that would happen. Source, Receiver and 180 Mtrace2 client are typically hosts. 182 2. Request 2. Request 183 +----+ +----+ 184 | | | | 185 v | v | 186 +--------+ +-----+ +-----+ +----------+ 187 | Source |----| FHR |----- The Internet -----| LHR |----| Receiver | 188 +--------+ +-----+ | +-----+ +----------+ 189 \ | ^ 190 \ | / 191 \ | / 192 \ | / 193 3. Reply \ | / 1. Query 194 \ | / 195 \ | / 196 \ +---------+ / 197 v | Mtrace2 |/ 198 | client | 199 +---------+ 201 Figure 1 203 When an Mtrace2 client initiates a multicast trace, it sends an 204 Mtrace2 Query packet to the LHR or RP for a multicast group and, 205 optionally, a source address. The LHR/RP turns the Query packet into 206 a Request. The Request message type enables each of the upstream 207 routers processing the message to apply different packet and message 208 validation rules than those required for handling of a Query message. 209 The LHR/RP then appends a standard response block containing its 210 interface addresses and packet statistics to the Request packet, then 211 forwards the packet towards the source/RP. The Request packet is 212 either unicasted to its upstream router towards the source/RP, or 213 multicasted to the group if the upstream router's IP address is not 214 known. In a similar fashion, each router along the path to the 215 source/RP appends a standard response block to the end of the Request 216 packet before forwarding it to its upstream router. When the FHR 217 receives the Request packet, it appends its own standard response 218 block, turns the Request packet into a Reply, and unicasts the Reply 219 back to the Mtrace2 client. 221 The Mtrace2 Reply may be returned before reaching the FHR under some 222 circumstances. This can happen if a Request packet is received at an 223 RP or gateway, or when any of several types of error or exception 224 conditions occur which prevent sending of a request to the next 225 upstream router. 227 The Mtrace2 client waits for the Mtrace2 Reply message and displays 228 the results. When not receiving an Mtrace2 Reply message due to 229 network congestion, a broken router (see Section 5.6), or a non- 230 responding router (see Section 5.7), the Mtrace2 client may resend 231 another Mtrace2 Query with a lower hop count (see Section 3.2.1), and 232 repeat the process until it receives an Mtrace2 Reply message. The 233 details are Mtrace2 client specific and outside the scope of this 234 document. 236 Note that when a router's control plane and forwarding plane are out 237 of sync, the Mtrace2 Requests might be forwarded based on the control 238 states instead. In this case, the traced path might not represent 239 the real path the data packets would follow. 241 Mtrace2 supports both IPv4 and IPv6. Unlike the previous version of 242 Mtrace, which implements its query and response as IGMP messages [8], 243 all Mtrace2 messages are UDP-based. Although the packet formats of 244 IPv4 and IPv6 Mtrace2 are different because of the address families, 245 the syntax between them is similar. 247 This document describes the base specification of Mtrace2 that can 248 serve as a basis for future proposals such as Mtrace2 for AMT [9] and 249 Mtrace2 for MVPN [10]. They are therefore out of the scope of this 250 document. 252 2. Terminology 254 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 255 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 256 and "OPTIONAL" are to be interpreted as described in RFC 2119 [1], 257 and indicate requirement levels for compliant Mtrace2 258 implementations. 260 2.1. Definitions 262 Since Mtrace2 Queries and Requests flow in the opposite direction to 263 the data flow, we refer to "upstream" and "downstream" with respect 264 to data, unless explicitly specified. 266 Incoming interface 267 The interface on which data is expected to arrive from the 268 specified source and group. 270 Outgoing interface 271 This is one of the interfaces to which data from the source or RP 272 is expected to be transmitted for the specified source and group. 273 It is also the interface on which the Mtrace2 Request was 274 received. 276 Upstream router 277 The router, connecting to the Incoming interface of the current 278 router, which is responsible for forwarding data for the specified 279 source and group to the current router. 281 First-hop router (FHR) 282 The router that is directly connected to the source the Mtrace2 283 Query specifies. 285 Last-hop router (LHR) 286 A router that is directly connected to a receiver. It is also the 287 router that receives the Mtrace2 Query from an Mtrace2 client. 289 Group state 290 It is the state a shared-tree protocol, such as PIM-SM [5], uses 291 to choose the upstream router towards the RP for the specified 292 group. In this state, source-specific state is not available for 293 the corresponding group address on the router. 295 Source-specific state 296 It is the state that is used to choose the path towards the source 297 for the specified source and group. 299 ALL-[protocol]-ROUTERS group 300 It is a link-local multicast address for multicast routers to 301 communicate with their adjacent routers that are running the same 302 routing protocol. For instance, the IPv4 'ALL-PIM-ROUTERS' group 303 is '224.0.0.13', and the IPv6 'ALL-PIM-ROUTERS' group is 'ff02::d' 304 [5]. 306 3. Packet Formats 308 This section describes the details of the packet formats for Mtrace2 309 messages. 311 All Mtrace2 messages are encoded in TLV format (see Section 3.1). 312 The first TLV of a message is a message header TLV specifying the 313 type of message and additional context information required for 314 processing of the message and for parsing of subsequent TLVs in the 315 message. Subsequent TLVs in a message, referred to as Blocks, are 316 appended after the header TLV to provide additional information 317 associated with the message. If an implementation receives an 318 unknown TLV type for the first TLV in a message, it SHOULD ignore and 319 silently discard the TLV and any subsequent TLVs in the packet 320 containing the TLV. If an implementation receives an unknown TLV 321 type for a subsequent TLV within a message, it SHOULD ignore and 322 silently discard the TLV. If the length of a TLV exceeds the 323 available space in the containing packet, the implementation MUST 324 ignore and silently discard the TLV and any remaining portion of the 325 containing packet. Any data in the packet after the specified TLV 326 length is considered to be outside the boundary of the TLV and MUST 327 be ignored during processing of the TLV. 329 All Mtrace2 messages are UDP packets. For IPv4, Mtrace2 Query and 330 Request messages MUST NOT be fragmented. For IPv6, the packet size 331 for the Mtrace2 messages MUST NOT exceed 1280 bytes, which is the 332 smallest MTU for an IPv6 interface [2]. The source port is uniquely 333 selected by the local host operating system. The destination port is 334 the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2 335 messages MUST have a valid UDP checksum. 337 Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed. 338 For example, if an Mtrace2 Query or Request message arrives in as an 339 IPv4 packet, all addresses specified in the Mtrace2 messages MUST be 340 IPv4 as well. Same rule applies to IPv6 Mtrace2 messages. 342 3.1. Mtrace2 TLV format 344 0 1 2 3 345 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 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | Type | Length | Value .... | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 Type: 8 bits 352 Describes the format of the Value field. For all the available 353 types, please see Section 3.2 355 Length: 16 bits 357 Length of Type, Length, and Value fields in octets. Minimum 358 length required is 3 octets. The maximum TLV length is not 359 defined; however the entire Mtrace2 packet length SHOULD NOT 360 exceed the available MTU. 362 Value: variable length 364 The format is based on the Type value. The length of the value 365 field is Length field minus 3. All reserved fields in the Value 366 field MUST be transmitted as zeros and ignored on receipt. 368 3.2. Defined TLVs 370 The following TLV Types are defined: 372 Code Type 373 ==== ================================ 374 0x01 Mtrace2 Query 375 0x02 Mtrace2 Request 376 0x03 Mtrace2 Reply 377 0x04 Mtrace2 Standard Response Block 378 0x05 Mtrace2 Augmented Response Block 379 0x06 Mtrace2 Extended Query Block 381 Each Mtrace2 message MUST begin with either a Query, Request or Reply 382 TLV. The first TLV determines the type of each Mtrace2 message. 383 Following a Query TLV, there can be a sequence of optional Extended 384 Query Blocks. In the case of a Request or a Reply TLV, it is then 385 followed by a sequence of Standard Response Blocks, each from a 386 multicast router on the path towards the source or the RP. In the 387 case more information is needed, a Standard Response Block can be 388 followed by one or multiple Augmented Response Blocks. 390 We will describe each message type in detail in the next few 391 sections. 393 3.2.1. Mtrace2 Query 395 An Mtrace2 Query is usually originated by an Mtrace2 client which 396 sends an Mtrace2 Query message to the LHR. When tracing towards the 397 source or the RP, the intermediate routers MUST NOT modify the Query 398 message except the Type field. If the actual number of hops is not 399 known, an Mtrace2 client could send an initial Query message with a 400 large # Hops (e.g., 0xffffffff), in order to try to trace the full 401 path. 403 An Mtrace2 Query message is shown as follows: 405 0 1 2 3 406 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 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 408 | Type | Length | # Hops | 409 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 410 | | 411 | Multicast Address | 412 | | 413 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 414 | | 415 | Source Address | 416 | | 417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 418 | | 419 | Mtrace2 Client Address | 420 | | 421 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 422 | Query ID | Client Port # | 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 Figure 2 427 # Hops: 8 bits 428 This field specifies the maximum number of hops that the Mtrace2 429 client wants to trace. If there are some error conditions in the 430 middle of the path that prevent an Mtrace2 Reply from being 431 received by the client, the client MAY issue another Mtrace2 Query 432 with a lower number of hops until it receives a Reply. 434 Multicast Address: 32 bits or 128 bits 435 This field specifies an IPv4 or IPv6 address, which can be either: 437 m-1: a multicast group address to be traced; or, 439 m-2: all 1's in case of IPv4 or the unspecified address (::) in 440 case of IPv6 if no group-specific information is desired. 442 Source Address: 32 bits or 128 bits 443 This field specifies an IPv4 or IPv6 address, which can be either: 445 s-1: an unicast address of the source to be traced; or, 447 s-2: all 1's in case of IPv4 or the unspecified address (::) in 448 case of IPv6 if no source-specific information is desired. 449 For example, the client is tracing a (*,g) group state. 451 Note that it is invalid to have a source-group combination of 452 (s-2, m-2). If a router receives such combination in an Mtrace2 453 Query, it MUST silently discard the Query. 455 Mtrace2 Client Address: 32 bits or 128 bits 456 This field specifies the Mtrace2 client's IPv4 address or IPv6 457 global address. This address MUST be a valid unicast address, and 458 therefore, MUST NOT be all 1's or an unspecified address. The 459 Mtrace2 Reply will be sent to this address. 461 Query ID: 16 bits 462 This field is used as a unique identifier for this Mtrace2 Query 463 so that duplicate or delayed Reply messages may be detected. 465 Client Port #: 16 bits 466 This field specifies the destination UDP port number for receiving 467 the Mtrace2 Reply packet. 469 3.2.2. Mtrace2 Request 471 The format of an Mtrace2 Request message is similar to an Mtrace2 472 Query except the Type field is 0x02. 474 When a LHR receives an Mtrace2 Query message, it would turn the Query 475 into a Request by changing the Type field of the Query from 0x01 to 476 0x02. The LHR would then append an Mtrace2 Standard Response Block 477 (see Section 3.2.4) of its own to the Request message before sending 478 it upstream. The upstream routers would do the same without changing 479 the Type field until one of them is ready to send a Reply. 481 3.2.3. Mtrace2 Reply 483 The format of an Mtrace2 Reply message is similar to an Mtrace2 Query 484 except the Type field is 0x03. 486 When a FHR or a RP receives an Mtrace2 Request message which is 487 destined to itself, it would append an Mtrace2 Standard Response 488 Block (see Section 3.2.4) of its own to the Request message. Next, 489 it would turn the Request message into a Reply by changing the Type 490 field of the Request from 0x02 to 0x03. The Reply message would then 491 be unicasted to the Mtrace2 client specified in the Mtrace2 Client 492 Address field. 494 There are a number of cases in which an intermediate router might 495 return a Reply before a Request reaches the FHR or the RP. See 496 Section 4.1.1, Section 4.2.2, Section 4.3.3, and Section 4.5 for more 497 details. 499 3.2.4. IPv4 Mtrace2 Standard Response Block 501 This section describes the message format of an IPv4 Mtrace2 Standard 502 Response Block. The Type field is 0x04. 504 0 1 2 3 505 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 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | Type | Length | MBZ | 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | Query Arrival Time | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | Incoming Interface Address | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Outgoing Interface Address | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 515 | Upstream Router Address | 516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 517 | | 518 . Input packet count on incoming interface . 519 | | 520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 521 | | 522 . Output packet count on outgoing interface . 523 | | 524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 525 | | 526 . Total number of packets for this source-group pair . 527 | | 528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 529 | Rtg Protocol | Multicast Rtg Protocol | 530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 531 | Fwd TTL | MBZ |S| Src Mask |Forwarding Code| 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 534 MBZ: 8 bits 535 This field MUST be zeroed on transmission and ignored on 536 reception. 538 Query Arrival Time: 32 bits 539 The Query Arrival Time is a 32-bit NTP timestamp specifying the 540 arrival time of the Mtrace2 Query or Request packet at this 541 router. The 32-bit form of an NTP timestamp consists of the 542 middle 32 bits of the full 64-bit form; that is, the low 16 bits 543 of the integer part and the high 16 bits of the fractional part. 545 The following formula converts from a UNIX timeval to a 32-bit NTP 546 timestamp: 548 query_arrival_time 549 = ((tv.tv_sec + 32384) << 16) + ((tv.tv_nsec << 7) / 1953125) 551 The constant 32384 is the number of seconds from Jan 1, 1900 to 552 Jan 1, 1970 truncated to 16 bits. ((tv.tv_nsec << 7) / 1953125) 553 is a reduction of ((tv.tv_nsec / 1000000000) << 16). 555 Note that Mtrace2 does not require all the routers on the path to 556 have synchronized clocks in order to measure one-way latency. 558 Additionally, Query Arrival Time is useful for measuring the 559 packet rate. For example, suppose that a client issues two 560 queries, and the corresponding requests R1 and R2 arrive at router 561 X at time T1 and T2, then the client would be able to compute the 562 packet rate on router X by using the packet count information 563 stored in the R1 and R2, and the time T1 and T2. 565 Incoming Interface Address: 32 bits 566 This field specifies the address of the interface on which packets 567 from the source or the RP are expected to arrive, or 0 if unknown 568 or unnumbered. 570 Outgoing Interface Address: 32 bits 571 This field specifies the address of the interface on which packets 572 from the source or the RP are expected to transmit towards the 573 receiver, or 0 if unknown or unnumbered. This is also the address 574 of the interface on which the Mtrace2 Query or Request arrives. 576 Upstream Router Address: 32 bits 577 This field specifies the address of the upstream router from which 578 this router expects packets from this source. This may be a 579 multicast group (e.g., ALL-[protocol]-ROUTERS group) if the 580 upstream router is not known because of the workings of the 581 multicast routing protocol. However, it should be 0 if the 582 incoming interface address is unknown or unnumbered. 584 Input packet count on incoming interface: 64 bits 585 This field contains the number of multicast packets received for 586 all groups and sources on the incoming interface, or all 1's if no 587 count can be reported. This counter may have the same value as 588 ifHCInMulticastPkts from the IF-MIB [12] for this interface. 590 Output packet count on outgoing interface: 64 bit 591 This field contains the number of multicast packets that have been 592 transmitted or queued for transmission for all groups and sources 593 on the outgoing interface, or all 1's if no count can be reported. 594 This counter may have the same value as ifHCOutMulticastPkts from 595 the IF-MIB [12] for this interface. 597 Total number of packets for this source-group pair: 64 bits 598 This field counts the number of packets from the specified source 599 forwarded by the router to the specified group, or all 1's if no 600 count can be reported. If the S bit is set (see below), the count 601 is for the source network, as specified by the Src Mask field (see 602 below). If the S bit is set and the Src Mask field is 127, 603 indicating no source-specific state, the count is for all sources 604 sending to this group. This counter should have the same value as 605 ipMcastRoutePkts from the IPMROUTE-STD-MIB [13] for this 606 forwarding entry. 608 Rtg Protocol: 16 bits 609 This field describes the unicast routing protocol running between 610 this router and the upstream router, and it is used to determine 611 the RPF interface for the specified source or RP. This value 612 should have the same value as ipMcastRouteRtProtocol from the 613 IPMROUTE-STD-MIB [13] for this entry. If the router is not able 614 to obtain this value, all 0's must be specified. 616 Multicast Rtg Protocol: 16 bits 617 This field describes the multicast routing protocol in use between 618 the router and the upstream router. This value should have the 619 same value as ipMcastRouteProtocol from the IPMROUTE-STD-MIB [13] 620 for this entry. If the router cannot obtain this value, all 0's 621 must be specified. 623 Fwd TTL: 8 bits 624 This field contains the configured multicast TTL threshold, if 625 any, of the outgoing interface. 627 S: 1 bit 628 If this bit is set, it indicates that the packet count for the 629 source-group pair is for the source network, as determined by 630 masking the source address with the Src Mask field. 632 Src Mask: 7 bits 633 This field contains the number of 1's in the netmask the router 634 has for the source (i.e. a value of 24 means the netmask is 635 0xffffff00). If the router is forwarding solely on group state, 636 this field is set to 127 (0x7f). 638 Forwarding Code: 8 bits 639 This field contains a forwarding information/error code. Values 640 with the high order bit set (0x80-0xff) are intended for use as 641 error or exception codes. Section 4.1 and Section 4.2 explain how 642 and when the Forwarding Code is filled. Defined values are as 643 follows: 645 Value Name Description 646 ----- -------------- ---------------------------------------------- 647 0x00 NO_ERROR No error 648 0x01 WRONG_IF Mtrace2 Request arrived on an interface 649 to which this router would not forward for 650 the specified group towards the source or RP. 651 0x02 PRUNE_SENT This router has sent a prune upstream which 652 applies to the source and group in the 653 Mtrace2 Request. 654 0x03 PRUNE_RCVD This router has stopped forwarding for this 655 source and group in response to a request 656 from the downstream router. 657 0x04 SCOPED The group is subject to administrative 658 scoping at this router. 659 0x05 NO_ROUTE This router has no route for the source or 660 group and no way to determine a potential 661 route. 662 0x06 WRONG_LAST_HOP This router is not the proper LHR. 663 0x07 NOT_FORWARDING This router is not forwarding this source and 664 group out the outgoing interface for an 665 unspecified reason. 666 0x08 REACHED_RP Reached the Rendezvous Point. 667 0x09 RPF_IF Mtrace2 Request arrived on the expected 668 RPF interface for this source and group. 669 0x0A NO_MULTICAST Mtrace2 Request arrived on an interface 670 which is not enabled for multicast. 671 0x0B INFO_HIDDEN One or more hops have been hidden from this 672 trace. 673 0x0C REACHED_GW Mtrace2 Request arrived on a gateway (e.g., 674 a NAT or firewall) that hides the 675 information between this router and the 676 Mtrace2 client. 677 0x0D UNKNOWN_QUERY A non-transitive Extended Query Type was 678 received by a router which does not support 679 the type. 680 0x80 FATAL_ERROR A fatal error is one where the router may 681 know the upstream router but cannot forward 682 the message to it. 683 0x81 NO_SPACE There was not enough room to insert another 684 Standard Response Block in the packet. 685 0x83 ADMIN_PROHIB Mtrace2 is administratively prohibited. 687 3.2.5. IPv6 Mtrace2 Standard Response Block 689 This section describes the message format of an IPv6 Mtrace2 Standard 690 Response Block. The Type field is also 0x04. 692 0 1 2 3 693 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 694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 695 | Type | Length | MBZ | 696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 697 | Query Arrival Time | 698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 | Incoming Interface ID | 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 | Outgoing Interface ID | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 | | 704 * Local Address * 705 | | 706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 707 | | 708 * Remote Address * 709 | | 710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 711 | | 712 . Input packet count on incoming interface . 713 | | 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 715 | | 716 . Output packet count on outgoing interface . 717 | | 718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 719 | | 720 . Total number of packets for this source-group pair . 721 | | 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 723 | Rtg Protocol | Multicast Rtg Protocol | 724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 725 | MBZ 2 |S|Src Prefix Len |Forwarding Code| 726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 MBZ: 8 bits 729 This field MUST be zeroed on transmission and ignored on 730 reception. 732 Query Arrival Time: 32 bits 733 Same definition as in IPv4. 735 Incoming Interface ID: 32 bits 736 This field specifies the interface ID on which packets from the 737 source or RP are expected to arrive, or 0 if unknown. This ID 738 should be the value taken from InterfaceIndex of the IF-MIB [12] 739 for this interface. 741 Outgoing Interface ID: 32 bits 742 This field specifies the interface ID to which packets from the 743 source or RP are expected to transmit, or 0 if unknown. This ID 744 should be the value taken from InterfaceIndex of the IF-MIB [12] 745 for this interface 747 Local Address: 128 bits 748 This field specifies a global IPv6 address that uniquely 749 identifies the router. An unique local unicast address [11] 750 SHOULD NOT be used unless the router is only assigned link-local 751 and unique local addresses. If the router is only assigned link- 752 local addresses, its link-local address can be specified in this 753 field. 755 Remote Address: 128 bits 756 This field specifies the address of the upstream router, which, in 757 most cases, is a link-local unicast address for the upstream 758 router. 760 Although a link-local address does not have enough information to 761 identify a node, it is possible to detect the upstream router with 762 the assistance of Incoming Interface ID and the current router 763 address (i.e., Local Address). 765 Note that this may be a multicast group (e.g., ALL-[protocol]- 766 ROUTERS group) if the upstream router is not known because of the 767 workings of a multicast routing protocol. However, it should be 768 the unspecified address (::) if the incoming interface address is 769 unknown. 771 Input packet count on incoming interface: 64 bits 772 Same definition as in IPv4. 774 Output packet count on outgoing interface: 64 bits 775 Same definition as in IPv4. 777 Total number of packets for this source-group pair: 64 bits 778 Same definition as in IPv4, except if the S bit is set (see 779 below), the count is for the source network, as specified by the 780 Src Prefix Len field. If the S bit is set and the Src Prefix Len 781 field is 255, indicating no source-specific state, the count is 782 for all sources sending to this group. This counter should have 783 the same value as ipMcastRoutePkts from the IPMROUTE-STD-MIB [13] 784 for this forwarding entry. 786 Rtg Protocol: 16 bits 787 Same definition as in IPv4. 789 Multicast Rtg Protocol: 16 bits 790 Same definition as in IPv4. 792 MBZ 2: 15 bits 793 This field MUST be zeroed on transmission and ignored on 794 reception. 796 S: 1 bit 797 Same definition as in IPv4, except the Src Prefix Len field is 798 used to mask the source address. 800 Src Prefix Len: 8 bits 801 This field contains the prefix length this router has for the 802 source. If the router is forwarding solely on group state, this 803 field is set to 255 (0xff). 805 Forwarding Code: 8 bits 806 Same definition as in IPv4. 808 3.2.6. Mtrace2 Augmented Response Block 810 In addition to the Standard Response Block, a multicast router on the 811 traced path can optionally add one or multiple Augmented Response 812 Blocks before sending the Request to its upstream router. 814 The Augmented Response Block is flexible for various purposes such as 815 providing diagnosis information (see Section 7) and protocol 816 verification. Its Type field is 0x05, and its format is as follows: 818 0 1 2 3 819 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 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 | Type | Length | MBZ | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 | Augmented Response Type | Value .... | 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 826 MBZ: 8 bits 827 This field MUST be zeroed on transmission and ignored on 828 reception. 830 Augmented Response Type: 16 bits 831 This field specifies the type of various responses from a 832 multicast router that might need to communicate back to the 833 Mtrace2 client as well as the multicast routers on the traced 834 path. 836 The Augmented Response Type is defined as follows: 838 Code Type 839 ==== =============================================== 840 0x01 # of the returned Standard Response Blocks 842 When the NO_SPACE error occurs on a router, the router should send 843 the original Mtrace2 Request received from the downstream router 844 as a Reply back to the Mtrace2 client and continue with a new 845 Mtrace2 Request. In the new Request, the router would add a 846 Standard Response Block followed by an Augmented Response Block 847 with 0x01 as the Augmented Response Type, and the number of the 848 returned Mtrace2 Standard Response Blocks as the Value. 850 Each upstream router would recognize the total number of hops the 851 Request has been traced so far by adding this number and the 852 number of the Standard Response Block in the current Request 853 message. 855 This document only defines one Augmented Response Type in the 856 Augmented Response Block. The description on how to provide 857 diagnosis information using the Augmented Response Block is out of 858 the scope of this document, and will be addressed in separate 859 documents. 861 Value: variable length 862 The format is based on the Augmented Response Type value. The 863 length of the value field is Length field minus 6. 865 3.2.7. Mtrace2 Extended Query Block 867 There may be a sequence of optional Extended Query Blocks that follow 868 an Mtrace2 Query to further specify any information needed for the 869 Query. For example, an Mtrace2 client might be interested in tracing 870 the path the specified source and group would take based on a certain 871 topology. In this case, the client can pass in the multi-topology ID 872 as the Value for an Extended Query Type (see below). The Extended 873 Query Type is extensible and the behavior of the new types will be 874 addressed by separate documents. 876 The Mtrace2 Extended Query Block's Type field is 0x06, and is 877 formatted as follows: 879 0 1 2 3 880 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 881 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 882 | Type | Length | MBZ |T| 883 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 884 | Extended Query Type | Value .... | 885 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 887 MBZ: 7 bits 888 This field MUST be zeroed on transmission and ignored on 889 reception. 891 T-bit (Transitive Attribute): 1 bit 892 If the TLV type is unrecognized by the receiving router, then this 893 TLV is either discarded or forwarded along with the Query, 894 depending on the value of this bit. If this bit is set, then the 895 router MUST forward this TLV. If this bit is clear, the router 896 MUST send an Mtrace2 Reply with an UNKNOWN_QUERY error. 898 Extended Query Type: 16 bits 899 This field specifies the type of the Extended Query Block. 901 Value: 16 bits 902 This field specifies the value of this Extended Query. 904 4. Router Behavior 906 This section describes the router behavior in the context of Mtrace2 907 in detail. 909 4.1. Receiving Mtrace2 Query 911 An Mtrace2 Query message is an Mtrace2 message with no response 912 blocks filled in, and uses TLV type of 0x01. 914 4.1.1. Query Packet Verification 916 Upon receiving an Mtrace2 Query message, a router MUST examine 917 whether the Multicast Address and the Source Address are a valid 918 combination as specified in Section 3.2.1, and whether the Mtrace2 919 Client Address is a valid IP unicast address. If either one is 920 invalid, the Query MUST be silently ignored. 922 Mtrace2 supports a non-local client to the LHR/RP. A router SHOULD, 923 however, support a mechanism to filter out queries from clients 924 beyond a specified administrative boundary. The potential approaches 925 are described in Section 9.2. 927 In the case where a local LHR client is required, the router must 928 then examine the Query to see if it is the proper LHR/RP for the 929 destination address in the packet. It is the proper local LHR if it 930 has a multicast-capable interface on the same subnet as the Mtrace2 931 Client Address and is the router that would forward traffic from the 932 given (S,G) or (*,G) onto that subnet. It is the proper RP if the 933 multicast group address specified in the query is 0 and if the IP 934 header destination address is a valid RP address on this router. 936 If the router determines that it is not the proper LHR/RP, or it 937 cannot make that determination, it does one of two things depending 938 on whether the Query was received via multicast or unicast. If the 939 Query was received via multicast, then it MUST be silently discarded. 940 If it was received via unicast, the router turns the Query into a 941 Reply message by changing the TLV type to 0x03 and appending a 942 Standard Response Block with a Forwarding Code of WRONG_LAST_HOP. 943 The rest of the fields in the Standard Response Block MUST be zeroed. 944 The router then sends the Reply message to the Mtrace2 Client Address 945 on the Client Port # as specified in the Mtrace2 Query. 947 Duplicate Query messages as identified by the tuple (Mtrace2 Client 948 Address, Query ID) SHOULD be ignored. This MAY be implemented using 949 a cache of previously processed queries keyed by the Mtrace2 Client 950 Address and Query ID pair. The duration of the cached entries is 951 implementation specific. Duplicate Request messages MUST NOT be 952 ignored in this manner. 954 4.1.2. Query Normal Processing 956 When a router receives an Mtrace2 Query and it determines that it is 957 the proper LHR/RP, it turns the Query to a Request by changing the 958 TLV type from 0x01 to 0x02, and performs the steps listed in 959 Section 4.2. 961 4.2. Receiving Mtrace2 Request 963 An Mtrace2 Request is an Mtrace2 message that uses TLV type of 0x02. 964 With the exception of the LHR, whose Request was just converted from 965 a Query, each Request received by a router should have at least one 966 Standard Response Block filled in. 968 4.2.1. Request Packet Verification 970 If the Mtrace2 Request does not come from an adjacent router, or if 971 the Request is not addressed to this router, or if the Request is 972 addressed to a multicast group which is not a link-scoped group 973 (i.e., 224.0.0.0/24 for IPv4, FFx2::/16 [3] for IPv6), it MUST be 974 silently ignored. GTSM [14] SHOULD be used by the router to 975 determine whether the router is adjacent or not. 977 If the sum of the number of the Standard Response Blocks in the 978 received Mtrace2 Request and the value of the Augmented Response Type 979 of 0x01, if any, is equal or more than the # Hops in the Mtrace2 980 Request, it MUST be silently ignored. 982 4.2.2. Request Normal Processing 984 When a router receives an Mtrace2 Request message, it performs the 985 following steps. Note that it is possible to have multiple 986 situations covered by the Forwarding Codes. The first one 987 encountered is the one that is reported, i.e. all "note Forwarding 988 Code N" should be interpreted as "if Forwarding Code is not already 989 set, set Forwarding Code to N". Note that in the steps described 990 below the "Outgoing Interface" is the one on which the Mtrace2 991 Request message arrives. 993 1. Prepare a Standard Response Block to be appended to the packet, 994 setting all fields to an initial default value of zero. 996 2. If Mtrace2 is administratively prohibited, note the Forwarding 997 Code of ADMIN_PROHIB and skip to step 4. 999 3. In the Standard Response Block, fill in the Query Arrival Time, 1000 Outgoing Interface Address (for IPv4) or Outgoing Interface ID 1001 (for IPv6), Output Packet Count, and Fwd TTL (for IPv4). 1003 4. Attempt to determine the forwarding information for the 1004 specified source and group, using the same mechanisms as would 1005 be used when a packet is received from the source destined for 1006 the group. A state need not be instantiated, it can be a 1007 "phantom" state created only for the purpose of the trace, such 1008 as "dry-run." 1010 If using a shared-tree protocol and there is no source-specific 1011 state, or if no source-specific information is desired (i.e., 1012 all 1's for IPv4 or unspecified address (::) for IPv6), group 1013 state should be used. If there is no group state or no group- 1014 specific information is desired, potential source state (i.e., 1015 the path that would be followed for a source-specific Join) 1016 should be used. 1018 5. If no forwarding information can be determined, the router notes 1019 a Forwarding Code of NO_ROUTE, sets the remaining fields that 1020 have not yet been filled in to zero, and then sends an Mtrace2 1021 Reply back to the Mtrace2 client. 1023 6. If a Forwarding Code of ADMIN_PROHIB has been set, skip to step 1024 7. Otherwise, fill in the Incoming Interface Address (or 1025 Incoming Interface ID and Local Address for IPv6), Upstream 1026 Router Address (or Remote Address for IPv6), Input Packet Count, 1027 Total Number of Packets, Routing Protocol, S, and Src Mask (or 1028 Src Prefix Len for IPv6) using the forwarding information 1029 determined in step 4. 1031 7. If the Outgoing interface is not enabled for multicast, note 1032 Forwarding Code of NO_MULTICAST. If the Outgoing interface is 1033 the interface from which the router would expect data to arrive 1034 from the source, note forwarding code RPF_IF. If the Outgoing 1035 interface is not one to which the router would forward data from 1036 the source or RP to the group, a Forwarding code of WRONG_IF is 1037 noted. In the above three cases, the router will return an 1038 Mtrace2 Reply and terminate the trace. 1040 8. If the group is subject to administrative scoping on either the 1041 Outgoing or Incoming interfaces, a Forwarding Code of SCOPED is 1042 noted. 1044 9. If this router is the RP for the group for a non-source-specific 1045 query, note a Forwarding Code of REACHED_RP. The router will 1046 send an Mtrace2 Reply and terminate the trace. 1048 10. If this router is directly connected to the specified source or 1049 source network on the Incoming interface, it sets the Upstream 1050 Router Address (for IPv4) or the Remote Address (for IPv6) of 1051 the response block to zero. The router will send an Mtrace2 1052 Reply and terminate the trace. 1054 11. If this router has sent a prune upstream which applies to the 1055 source and group in the Mtrace2 Request, it notes a Forwarding 1056 Code of PRUNE_SENT. If the router has stopped forwarding 1057 downstream in response to a prune sent by the downstream router, 1058 it notes a Forwarding Code of PRUNE_RCVD. If the router should 1059 normally forward traffic downstream for this source and group 1060 but is not, it notes a Forwarding Code of NOT_FORWARDING. 1062 12. If this router is a gateway (e.g., a NAT or firewall) that hides 1063 the information between this router and the Mtrace2 client, it 1064 notes a Forwarding Code of REACHED_GW. The router continues the 1065 processing as described in Section 4.5. 1067 13. If the total number of the Standard Response Blocks, including 1068 the newly prepared one, and the value of the Augmented Response 1069 Type of 0x01, if any, is less than the # Hops in the Request, 1070 the packet is then forwarded to the upstream router as described 1071 in Section 4.3; otherwise, the packet is sent as an Mtrace2 1072 Reply to the Mtrace2 client as described in Section 4.4. 1074 4.3. Forwarding Mtrace2 Request 1076 This section describes how an Mtrace2 Request should be forwarded. 1078 4.3.1. Destination Address 1080 If the upstream router for the Mtrace2 Request is known for this 1081 request, the Mtrace2 Request is sent to that router. If the Incoming 1082 interface is known but the upstream router is not, the Mtrace2 1083 Request is sent to an appropriate multicast address on the Incoming 1084 interface. The multicast address SHOULD depend on the multicast 1085 routing protocol in use, such as ALL-[protocol]-ROUTERS group. It 1086 MUST be a link-scoped group (i.e., 224.0.0.0/24 for IPv4, FF02::/16 1087 for IPv6), and MUST NOT be the all-systems multicast group 1088 (224.0.0.1) for IPv4 and All Nodes Address (FF02::1) for IPv6. It 1089 MAY also be the all-routers multicast group (224.0.0.2) for IPv4 or 1090 All Routers Address (FF02::2) for IPv6 if the routing protocol in use 1091 does not define a more appropriate multicast address. 1093 4.3.2. Source Address 1095 An Mtrace2 Request should be sent with the address of the Incoming 1096 interface. However, if the Incoming interface is unnumbered, the 1097 router can use one of its numbered interface addresses as the source 1098 address. 1100 4.3.3. Appending Standard Response Block 1102 An Mtrace2 Request MUST be sent upstream towards the source or the RP 1103 after appending a Standard Response Block to the end of the received 1104 Mtrace2 Request. The Standard Response Block includes the multicast 1105 states and statistics information of the router described in 1106 Section 3.2.4. 1108 If appending the Standard Response Block would make the Mtrace2 1109 Request packet longer than the MTU of the Incoming Interface, or, in 1110 the case of IPv6, longer than 1280 bytes, the router MUST change the 1111 Forwarding Code in the last Standard Response Block of the received 1112 Mtrace2 Request into NO_SPACE. The router then turns the Request 1113 into a Reply and sends the Reply as described in Section 4.4. 1115 The router will continue with a new Request by copying from the old 1116 Request excluding all the response blocks, followed by the previously 1117 prepared Standard Response Block, and an Augmented Response Block 1118 with Augmented Response Type of 0x01 and the number of the returned 1119 Standard Response Blocks as the value. The new Request is then 1120 forwarded upstream. 1122 4.4. Sending Mtrace2 Reply 1124 An Mtrace2 Reply MUST be returned to the client by a router if any of 1125 the following conditions occur: 1127 1. The total number of the traced routers are equal to the # of hops 1128 in the request (including the one just added) plus the number of 1129 the returned blocks, if any. 1131 2. Appending the Standard Response Block would make the Mtrace2 1132 Request packet longer than the MTU of the Incoming interface. 1133 (In case of IPv6 not more than 1280 bytes; see Section 4.3.3 for 1134 additional details on handling of this case.) 1136 3. The request has reached the RP for a non source specific query or 1137 has reached the first hop router for a source specific query (see 1138 Section 4.2.2, items 9 and 10 for additional details). 1140 4.4.1. Destination Address 1142 An Mtrace2 Reply MUST be sent to the address specified in the Mtrace2 1143 Client Address field in the Mtrace2 Request. 1145 4.4.2. Source Address 1147 An Mtrace2 Reply SHOULD be sent with the address of the router's 1148 Outgoing interface. However, if the Outgoing interface address is 1149 unnumbered, the router can use one of its numbered interface 1150 addresses as the source address. 1152 4.4.3. Appending Standard Response Block 1154 An Mtrace2 Reply MUST be sent with the prepared Standard Response 1155 Block appended at the end of the received Mtrace2 Request except in 1156 the case of NO_SPACE forwarding code. 1158 4.5. Proxying Mtrace2 Query 1160 When a gateway (e.g., a NAT or firewall), which needs to block 1161 unicast packets to the Mtrace2 client, or hide information between 1162 the gateway and the Mtrace2 client, receives an Mtrace2 Query from an 1163 adjacent host or Mtrace2 Request from an adjacent router, it appends 1164 a Standard Response Block with REACHED_GW as the Forwarding Code. It 1165 turns the Query or Request into a Reply, and sends the Reply back to 1166 the client. 1168 At the same time, the gateway originates a new Mtrace2 Query message 1169 by copying the original Mtrace2 header (the Query or Request without 1170 any of the response blocks), and makes the changes as follows: 1172 o sets the RPF interface's address as the Mtrace2 Client Address; 1174 o uses its own port number as the Client Port #; and, 1176 o decreases # Hops by ((number of the Standard Response Blocks that 1177 were just returned in a Reply) - 1). The "-1" in this expression 1178 accounts for the additional Standard Response Block appended by 1179 the gateway router. 1181 The new Mtrace2 Query message is then sent to the upstream router or 1182 to an appropriate multicast address on the RPF interface. 1184 When the gateway receives an Mtrace2 Reply whose Query ID matches the 1185 one in the original Mtrace2 header, it MUST relay the Mtrace2 Reply 1186 back to the Mtrace2 client by replacing the Reply's header with the 1187 original Mtrace2 header. If the gateway does not receive the 1188 corresponding Mtrace2 Reply within the [Mtrace Reply Timeout] period 1189 (see Section 5.8.4), then it silently discards the original Mtrace2 1190 Query or Request message, and terminates the trace. 1192 4.6. Hiding Information 1194 Information about a domain's topology and connectivity may be hidden 1195 from the Mtrace2 Requests. The Forwarding Code of INFO_HIDDEN may be 1196 used to note that. For example, the incoming interface address and 1197 packet count on the ingress router of a domain, and the outgoing 1198 interface address and packet count on the egress router of the domain 1199 can be specified as all 1's. Additionally, the source-group packet 1200 count (see Section 3.2.4 and Section 3.2.5) within the domain may be 1201 all 1's if it is hidden. 1203 5. Client Behavior 1205 This section describes the behavior of an Mtrace2 client in detail. 1207 5.1. Sending Mtrace2 Query 1209 An Mtrace2 client initiates an Mtrace2 Query by sending the Query to 1210 the LHR of interest. 1212 5.1.1. Destination Address 1214 If an Mtrace2 client knows the proper LHR, it unicasts an Mtrace2 1215 Query packet to that router; otherwise, it MAY send the Mtrace2 Query 1216 packet to the all-routers multicast group (224.0.0.2) for IPv4 or All 1217 Routers Address (FF02::2) for IPv6. This will ensure that the packet 1218 is received by the LHR on the subnet. 1220 See also Section 5.4 on determining the LHR. 1222 5.1.2. Source Address 1224 An Mtrace2 Query MUST be sent with the client's interface address, 1225 which would be the Mtrace2 Client Address. 1227 5.2. Determining the Path 1229 An Mtrace2 client could send an initial Query messages with a large # 1230 Hops, in order to try to trace the full path. If this attempt fails, 1231 one strategy is to perform a linear search (as the traditional 1232 unicast traceroute program does); set the # Hops field to 1 and try 1233 to get a Reply, then 2, and so on. If no Reply is received at a 1234 certain hop, the hop count can continue past the non-responding hop, 1235 in the hopes that further hops may respond. These attempts should 1236 continue until the [Mtrace Reply Timeout] timeout has occurred. 1238 See also Section 5.6 on receiving the results of a trace. 1240 5.3. Collecting Statistics 1242 After a client has determined that it has traced the whole path or as 1243 much as it can expect to (see Section 5.8), it might collect 1244 statistics by waiting a short time and performing a second trace. If 1245 the path is the same in the two traces, statistics can be displayed 1246 as described in Section 7.3 and Section 7.4. 1248 5.4. Last Hop Router (LHR) 1250 The Mtrace2 client may not know which is the last-hop router, or that 1251 router may be behind a firewall that blocks unicast packets but 1252 passes multicast packets. In these cases, the Mtrace2 Request should 1253 be multicasted to the all-routers multicast group (224.0.0.2) for 1254 IPv4 or All Routers Address (FF02::2) for IPv6. All routers except 1255 the correct last-hop router SHOULD ignore any Mtrace2 Request 1256 received via multicast. 1258 5.5. First Hop Router (FHR) 1260 The IANA assigned 224.0.1.32 as the default multicast group for old 1261 IPv4 mtrace (v1) responses, in order to support mtrace clients that 1262 are not unicast reachable from the first-hop router. Mtrace2, 1263 however, does not require any IPv4/IPv6 multicast addresses for the 1264 Mtrace2 Replies. Every Mtrace2 Reply is sent to the unicast address 1265 specified in the Mtrace2 Client Address field of the Mtrace2 Reply. 1267 5.6. Broken Intermediate Router 1269 A broken intermediate router might simply not understand Mtrace2 1270 packets, and drop them. The Mtrace2 client will get no Reply at all 1271 as a result. It should then perform a hop-by-hop search by setting 1272 the # Hops field until it gets an Mtrace2 Reply. The client may use 1273 linear or binary search; however, the latter is likely to be slower 1274 because a failure requires waiting for the [Mtrace Reply Timeout] 1275 period. 1277 5.7. Non-Supported Router 1279 When a non-supported router receives an Mtrace2 Query or Request 1280 message whose destination address is a multicast address, the router 1281 will silently discard the message. 1283 When the router receives an Mtrace2 Query which is destined to 1284 itself, the router would return an ICMP port unreachable to the 1285 Mtrace2 client. On the other hand, when the router receives an 1286 Mtrace2 Request which is destined to itself, the router would return 1287 an ICMP port unreachable to its adjacent router from which the 1288 Request receives. Therefore, the Mtrace2 client needs to terminate 1289 the trace when the [Mtrace Reply Timeout] timeout has occurred, and 1290 may then issue another Query with a lower number of # Hops. 1292 5.8. Mtrace2 Termination 1294 When performing an expanding hop-by-hop trace, it is necessary to 1295 determine when to stop expanding. 1297 5.8.1. Arriving at Source 1299 A trace can be determined to have arrived at the source if the 1300 Incoming Interface of the last router in the trace is non-zero, but 1301 the Upstream Router is zero. 1303 5.8.2. Fatal Error 1305 A trace has encountered a fatal error if the last Forwarding Error in 1306 the trace has the 0x80 bit set. 1308 5.8.3. No Upstream Router 1310 A trace cannot continue if the last Upstream Router in the trace is 1311 set to 0. 1313 5.8.4. Reply Timeout 1315 This document defines the [Mtrace Reply Timeout] value, which is used 1316 to time out an Mtrace2 Reply as seen in Section 4.5, Section 5.2, and 1317 Section 5.7. The default [Mtrace Reply Timeout] value is 10 1318 (seconds), and can be manually changed on the Mtrace2 client and 1319 routers. 1321 5.9. Continuing after an Error 1323 When the NO_SPACE error occurs, as described in Section 4.2, a router 1324 will send back an Mtrace2 Reply to the Mtrace2 client, and continue 1325 with a new Request (see Section 4.3.3). In this case, the Mtrace2 1326 client may receive multiple Mtrace2 Replies from different routers 1327 along the path. When this happens, the client MUST treat them as a 1328 single Mtrace2 Reply message. 1330 If a trace times out, it is very likely that a router in the middle 1331 of the path does not support Mtrace2. That router's address will be 1332 in the Upstream Router field of the last Standard Response Block in 1333 the last received Reply. A client may be able to determine (via 1334 mrinfo or SNMP [11][13]) a list of neighbors of the non-responding 1335 router. The neighbors obtained in this way could then be probed (via 1336 the multicast MIB [13]) to determine which one is the upstream (RPF) 1337 neighbor of the non-responding router. This algorithm can identify 1338 the upstream neighbor because, even though there may be multiple 1339 neighbors, the non-responding router should only have sent a "join" 1340 to the one neighbor corresponding to its selected RPF path. Because 1341 of this, only the RPF neighbor should contain the non-responding 1342 router as a multicast next hop in its MIB output list for the 1343 affected multicast route. 1345 6. Protocol-Specific Considerations 1347 This section describes the Mtrace2 behavior with the presence of 1348 different multicast protocols. 1350 6.1. PIM-SM 1352 When an Mtrace2 reaches a PIM-SM RP, and the RP does not forward the 1353 trace on, it means that the RP has not performed a source-specific 1354 join so there is no more state to trace. However, the path that 1355 traffic would use if the RP did perform a source-specific join can be 1356 traced by setting the trace destination to the RP, the trace source 1357 to the traffic source, and the trace group to 0. This Mtrace2 Query 1358 may be unicasted to the RP, and the RP takes the same actions as an 1359 LHR. 1361 6.2. Bi-Directional PIM 1363 Bi-directional PIM [6] is a variant of PIM-SM that builds bi- 1364 directional shared trees connecting multicast sources and receivers. 1365 Along the bi-directional shared trees, multicast data is natively 1366 forwarded from the sources to the Rendezvous Point Link (RPL), and 1367 from which, to receivers without requiring source-specific state. In 1368 contrast to PIM-SM, Bi-directional PIM always has the state to trace. 1370 A Designated Forwarder (DF) for a given Rendezvous Point Address 1371 (RPA) is in charge of forwarding downstream traffic onto its link, 1372 and forwarding upstream traffic from its link towards the RPL that 1373 the RPA belongs to. Hence Mtrace2 Reply reports DF addresses or RPA 1374 along the path. 1376 6.3. PIM-DM 1378 Routers running PIM Dense Mode [15] do not know the path packets 1379 would take unless traffic is flowing. Without some extra protocol 1380 mechanism, this means that in an environment with multiple possible 1381 paths with branch points on shared media, Mtrace2 can only trace 1382 existing paths, not potential paths. When there are multiple 1383 possible paths but the branch points are not on shared media, the 1384 upstream router is known, but the LHR may not know that it is the 1385 appropriate last hop. 1387 When traffic is flowing, PIM Dense Mode routers know whether or not 1388 they are the LHR for the link (because they won or lost an Assert 1389 battle) and know who the upstream router is (because it won an Assert 1390 battle). Therefore, Mtrace2 is always able to follow the proper path 1391 when traffic is flowing. 1393 6.4. IGMP/MLD Proxy 1395 When an IGMP/MLD Proxy [7] receives an Mtrace2 Query packet on an 1396 incoming interface, it notes a WRONG_IF in the Forwarding Code of the 1397 last Standard Response Block (see Section 3.2.4), and sends the 1398 Mtrace2 Reply back to the Mtrace2 client. On the other hand, when an 1399 Mtrace2 Query packet reaches an outgoing interface of the IGMP/MLD 1400 proxy, it is forwarded onto its incoming interface towards the 1401 upstream router. 1403 7. Problem Diagnosis 1405 This section describes different scenarios Mtrace2 can be used to 1406 diagnose the multicast problems. 1408 7.1. Forwarding Inconsistencies 1410 The Forwarding Error code can tell if a group is unexpectedly pruned 1411 or administratively scoped. 1413 7.2. TTL or Hop Limit Problems 1415 By taking the maximum of hops from the source and forwarding TTL 1416 threshold over all hops, it is possible to discover the TTL or hop 1417 limit required for the source to reach the destination. 1419 7.3. Packet Loss 1421 By taking multiple traces, it is possible to find packet loss 1422 information by tracking the difference between the output packet 1423 count for the specified source-group address pair at a given upstream 1424 router and the input packet count on the next hop downstream router. 1425 On a point-to-point link, any steadily increasing difference in these 1426 counts implies packet loss. Although the packet counts will differ 1427 due to Mtrace2 Request propagation delay, the difference should 1428 remain essentially constant (except for jitter caused by differences 1429 in propagation time among the trace iterations). However, this 1430 difference will display a steady increase if packet loss is 1431 occurring. On a shared link, the count of input packets can be 1432 larger than the number of output packets at the previous hop, due to 1433 other routers or hosts on the link injecting packets. This appears 1434 as "negative loss" which may mask real packet loss. 1436 In addition to the counts of input and output packets for all 1437 multicast traffic on the interfaces, the Standard Response Block 1438 includes a count of the packets forwarded by a node for the specified 1439 source-group pair. Taking the difference in this count between two 1440 traces and then comparing those differences between two hops gives a 1441 measure of packet loss just for traffic from the specified source to 1442 the specified receiver via the specified group. This measure is not 1443 affected by shared links. 1445 On a point-to-point link that is a multicast tunnel, packet loss is 1446 usually due to congestion in unicast routers along the path of that 1447 tunnel. On native multicast links, loss is more likely in the output 1448 queue of one hop, perhaps due to priority dropping, or in the input 1449 queue at the next hop. The counters in the Standard Response Block 1450 do not allow these cases to be distinguished. Differences in packet 1451 counts between the incoming and outgoing interfaces on one node 1452 cannot generally be used to measure queue overflow in the node. 1454 7.4. Link Utilization 1456 Again, with two traces, you can divide the difference in the input or 1457 output packet counts at some hop by the difference in time stamps 1458 from the same hop to obtain the packet rate over the link. If the 1459 average packet size is known, then the link utilization can also be 1460 estimated to see whether packet loss may be due to the rate limit or 1461 the physical capacity on a particular link being exceeded. 1463 7.5. Time Delay 1465 If the routers have synchronized clocks, it is possible to estimate 1466 propagation and queuing delay from the differences between the 1467 timestamps at successive hops. However, this delay includes control 1468 processing overhead, so is not necessarily indicative of the delay 1469 that data traffic would experience. 1471 8. IANA Considerations 1473 The following new registries are to be created and maintained under 1474 the "RFC Required" registry policy as specified in [4]. 1476 8.1. "Mtrace2 Forwarding Codes" Registry 1478 This is an integer in the range 0-255. Assignment of a Forwarding 1479 Code requires specification of a value and a name for the Forwarding 1480 Code. Initial values for the forwarding codes are given in the table 1481 at the end of Section 3.2.4. Additional values (specific to IPv6) 1482 may also be specified at the end of Section 3.2.5. Any additions to 1483 this registry are required to fully describe the conditions under 1484 which the new Forwarding Code is used. 1486 8.2. "Mtrace2 TLV Types" registry 1488 Assignment of a TLV Type requires specification of an integer value 1489 "Code" in the range 0-255 and a name ("Type"). Initial values for 1490 the TLV Types are given in the table at the beginning of Section 3.2. 1492 8.3. UDP Destination Port 1494 The Mtrace2 UDP destination port is assigned when this document is 1495 published as RFC. 1497 9. Security Considerations 1499 This section addresses some of the security considerations related to 1500 Mtrace2. 1502 9.1. Addresses in Mtrace2 Header 1504 An Mtrace2 header includes three addresses, source address, multicast 1505 address, and Mtrace2 client address. These addresses MUST be 1506 congruent with the definition defined in Section 3.2.1 and forwarding 1507 Mtrace2 messages having invalid addresses MUST be prohibited. For 1508 instance, if Mtrace2 Client Address specified in an Mtrace2 header is 1509 a multicast address, then a router that receives the Mtrace2 message 1510 MUST silently discard it. 1512 9.2. Filtering of Clients 1514 A router SHOULD support a mechanism to filter out queries from 1515 clients beyond a specified administrative boundary. Such a boundary 1516 could, for example, be specified via a list of allowed/disallowed 1517 client addresses or subnets. If a query is received from beyond the 1518 specified administrative boundary, the Query MUST NOT be processed. 1519 The router MAY, however, perform rate limited logging of such events. 1521 9.3. Topology Discovery 1523 Mtrace2 can be used to discover any actively-used topology. If your 1524 network topology is a secret, Mtrace2 may be restricted at the border 1525 of your domain, using the ADMIN_PROHIB forwarding code. 1527 9.4. Characteristics of Multicast Channel 1529 Mtrace2 can be used to discover what sources are sending to what 1530 groups and at what rates. If this information is a secret, Mtrace2 1531 may be restricted at the border of your domain, using the 1532 ADMIN_PROHIB forwarding code. 1534 9.5. Limiting Query/Request Rates 1536 A router may limit Mtrace2 Queries and Requests by ignoring some of 1537 the consecutive messages. The router MAY randomly ignore the 1538 received messages to minimize the processing overhead, i.e., to keep 1539 fairness in processing queries, or prevent traffic amplification. 1540 The rate limit is left to the router's implementation. 1542 9.6. Limiting Reply Rates 1544 The proxying and NO_SPACE behaviors may result in one Query returning 1545 multiple Reply messages. In order to prevent abuse, the routers in 1546 the traced path MAY need to rate-limit the Replies. The rate limit 1547 function is left to the router's implementation. 1549 10. Acknowledgements 1551 This specification started largely as a transcription of Van 1552 Jacobson's slides from the 30th IETF, and the implementation in 1553 mrouted 3.3 by Ajit Thyagarajan. Van's original slides credit Steve 1554 Casner, Steve Deering, Dino Farinacci and Deb Agrawal. The original 1555 multicast traceroute client, mtrace (version 1), has been implemented 1556 by Ajit Thyagarajan, Steve Casner and Bill Fenner. The idea of the 1557 "S" bit to allow statistics for a source subnet is due to Tom 1558 Pusateri. 1560 For the Mtrace version 2 specification, the authors would like to 1561 give special thanks to Tatsuya Jinmei, Bill Fenner, and Steve Casner. 1562 Also, extensive comments were received from David L. Black, Ronald 1563 Bonica, Yiqun Cai, Liu Hui, Bharat Joshi, Robert Kebler, John 1564 Kristoff, Mankamana Mishra, Heidi Ou, Pekka Savola, Shinsuke Suzuki, 1565 Dave Thaler, Achmad Husni Thamrin, Stig Venaas, and Cao Wei. 1567 11. References 1569 11.1. Normative References 1571 [1] Bradner, S., "Key words for use in RFCs to indicate 1572 requirement levels", RFC 2119, March 1997. 1574 [2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1575 (IPv6) Specification", RFC 8200, July 2017. 1577 [3] Hinden, R. and S. Deering, "IP Version 6 Addressing 1578 Architecture", RFC 4291, February 2006. 1580 [4] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1581 Writing an IANA Considerations Section in RFCs", RFC 8126, 1582 June 2017. 1584 [5] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 1585 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 1586 Multicast - Sparse Mode (PIM-SM): Protocol Specification 1587 (Revised)", RFC 7761, March 2016. 1589 [6] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 1590 "Bidirectional Protocol Independent Multicast (BIDIR- 1591 PIM)", RFC 5015, October 2007. 1593 [7] Fenner, B., He, H., Haberman, B., and H. Sandick, 1594 "Internet Group Management Protocol (IGMP) / Multicast 1595 Listener Discovery (MLD)-Based Multicast Forwarding 1596 ("IGMP/MLD Proxying")", RFC 4605, August 2006. 1598 11.2. Informative References 1600 [8] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 1601 Thyagarajan, "Internet Group Management Protocol, Version 1602 3", RFC 3376, October 2002. 1604 [9] Bumgardner, G., "Automatic Multicast Tunneling", RFC 7450, 1605 February 2015. 1607 [10] Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP 1608 VPNs", RFC 6513, February 2012. 1610 [11] Draves, R. and D. Thaler, "Default Router Preferences and 1611 More-Specific Routes", RFC 4191, November 2005. 1613 [12] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1614 MIB", RFC 2863, June 2000. 1616 [13] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1617 MIB", RFC 5132, December 2007. 1619 [14] Gill, V., Heasley, J., Meyer, D., Savola, P., and C. 1620 Pignataro, "The Generalized TTL Security Mechanism 1621 (GTSM)", RFC 5082, October 2007. 1623 [15] Adams, A., Nicholas, J., and W. Siadak, "Protocol 1624 Independent Multicast - Dense Mode (PIM-DM): Protocol 1625 Specification (Revised)", RFC 3973, January 2005. 1627 Authors' Addresses 1628 Hitoshi Asaeda 1629 National Institute of Information and Communications Technology 1630 4-2-1 Nukui-Kitamachi 1631 Koganei, Tokyo 184-8795 1632 Japan 1634 Email: asaeda@nict.go.jp 1636 Kerry Meyer 1637 Cisco Systems, Inc. 1638 510 McCarthy Blvd. 1639 Milpitas, CA 95035 1640 USA 1642 Email: kerrymey@cisco.com 1644 WeeSan Lee (editor) 1646 Email: weesan@weesan.com