idnits 2.17.1 draft-ietf-ippm-storetraceroutes-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 2072. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2083. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2090. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2096. 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 261 has weird spacing: '...A |Set the t...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 22, 2007) is 6273 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '1-9' is mentioned on line 955, but not defined == Missing Reference: '0-9' is mentioned on line 956, but not defined == Missing Reference: '0-4' is mentioned on line 956, but not defined == Missing Reference: '0-5' is mentioned on line 956, but not defined == Unused Reference: 'I-D.ietf-disman-remops-mib-v2' is defined on line 1958, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-ipfix-info-14 == Outdated reference: A later version (-26) exists of draft-ietf-ipfix-protocol-24 Summary: 1 error (**), 0 flaws (~~), 9 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPPM Working Group S. Niccolini 3 Internet-Draft S. Tartarelli 4 Intended status: Standards Track J. Quittek 5 Expires: August 26, 2007 NEC 6 M. Swany 7 UDel 8 February 22, 2007 10 Traceroute Measurements Information Model and XML Data Model 11 draft-ietf-ippm-storetraceroutes-03 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on August 26, 2007. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2007). 42 Abstract 44 This memo describes a standard way to store traceroute measurements. 45 To better address the traceroute measurements storing issue, the 46 authors first of all give a definition of the traceroute tool, 47 describe the tool itself as well as its parameters and the default 48 values on the most common operating systems and the output results 49 that can be stored. Afterwards, the common information model with 50 the base elements of the traceroute measurement storing is defined 51 dividing the information elements in two semantically separated 52 groups (configuration elements and results ones). Moreover an 53 additional element is defined to relate configuration elements and 54 results ones by means of a common unique identifier. On the basis of 55 the information model a data model is then proposed in order to 56 actually store the traceroute measurements. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Definition of Traceroute . . . . . . . . . . . . . . . . . . . 3 62 2.1. Traceroute Configuration Parameters . . . . . . . . . . . 4 63 3. Known Problems with Traceroute . . . . . . . . . . . . . . . . 8 64 3.1. Accuracy of Results . . . . . . . . . . . . . . . . . . . 8 65 3.2. Alternative traceroute Implementations . . . . . . . . . . 8 66 4. Reports/results . . . . . . . . . . . . . . . . . . . . . . . 8 67 5. Information Model for Storing Traceroute Measurements . . . . 9 68 5.1. Data Types . . . . . . . . . . . . . . . . . . . . . . . . 9 69 5.2. Information Elements . . . . . . . . . . . . . . . . . . . 10 70 5.2.1. Configuration Information Elements . . . . . . . . . . 11 71 5.2.2. Results Information Elements . . . . . . . . . . . . . 15 72 5.2.3. Information Element Correlating Configuration and 73 Results Elements . . . . . . . . . . . . . . . . . . . 18 74 6. Data Model for Storing Traceroute Measurements . . . . . . . . 19 75 7. XML Schema for traceroute Measurements . . . . . . . . . . . . 20 76 8. Differences to DISMAN-TRACEROUTE-MIB . . . . . . . . . . . . . 38 77 8.1. Naming . . . . . . . . . . . . . . . . . . . . . . . . . . 39 78 8.2. Semantics . . . . . . . . . . . . . . . . . . . . . . . . 39 79 8.3. Additional Information Elements . . . . . . . . . . . . . 40 80 9. Security Considerations . . . . . . . . . . . . . . . . . . . 40 81 9.1. Conducting Traceroute Measurements . . . . . . . . . . . . 40 82 9.2. Securing Traceroute Measurement Results . . . . . . . . . 41 83 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 84 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 85 11.1. Normative References . . . . . . . . . . . . . . . . . . . 42 86 11.2. Informative References . . . . . . . . . . . . . . . . . . 42 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 88 Intellectual Property and Copyright Statements . . . . . . . . . . 45 90 1. Introduction 92 Traceroutes are being used by lots of measurement efforts, either as 93 an independent measurement or to get path information to support 94 other measurement efforts. That is why there is the need to 95 standardize the way traceroute measurements are stored and the 96 related metrics associated with such measurements. Since traceroute 97 is a tool that has built-in configurable mechanisms like time-outs 98 and can experience problems related to the crossing of firewalls thus 99 experiencing fake losses or incomplete delay information. The 100 standard metrics defined by IPPM working group in matter of delay, 101 connectivity and losses do not apply to the metrics returned by the 102 traceroute tool; therefore, in order to compare results of traceroute 103 measurements, the solution is to add to the stored results a 104 specification of the operating system and version for the tool used. 105 Moreover there is a need to better define the traceroute tool as well 106 as its parameters and the results it outputs since, to the authors' 107 knowledge, there is so far no standard describing these. These are 108 the motivations that moved the authors to write this draft in the 109 context of the IPPM working group even if other working groups (like 110 DISMAN) have already addressed similar issues related to the 111 definition of the MIB for configuring and retrieving traceroute 112 measurements results. This draft, in order to store traceroute 113 results and allow comparison of them, defines a standard way to store 114 traceroute measurements using a XML schema. The draft is organised 115 as follows: Section 2 gives the definition of traceroute used as 116 reference in the rest of the draft as well as the traceroute 117 configurable parameters and their default values for the most common 118 operating systems. Section 3 reports on both traceroute accuracy of 119 results and existing alternatives for traceroute implementations. 120 Section 4 describes the results available from the traceroute output 121 screen. Section 5 and Section 6 respectively describe our proposed 122 Information model and Data model for storing traceroute measurements. 123 Section 8 reports the differences to [RFC4560]. The draft ends with 124 security considerations and IANA considerations in Section 9 and 125 Section 10 respectively. 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 129 document are to be interpreted as described in RFC 2119. 131 2. Definition of Traceroute 133 Traceroute is a network diagnostic tool used to determine the hop by 134 hop path from a source to a destination and the Round Trip Time (RTT) 135 from the source to each hop. Traceroute can therefore be used to 136 discover where and how a host is connected to the Internet and can be 137 usefully employed to troubleshoot network connections. 139 Typically, traceroute attemps to discover the path to a destination 140 by sending UDP probes with specific time-to-live (TTL) values in the 141 IP packet header and trying to elicit an ICMP TIME_EXCEEDED response 142 from each gateway along the path to some host. 144 More in detail, the host running the traceroute sends the first set 145 of probes with TTL equal to one (some implementations allow setting 146 the initial TTL to a value equal to "n" different from one, so that 147 the first "n-1" hops are skipped and the first hop that will be 148 traced is the "n-th" in the path). Upon receiving a probe, the first 149 hop host decreases the TTL value by one. By observing a TTL value 150 equal to zero, the host rejects the probe and typically returns an 151 ICMP message with a TIME_EXCEEDED value. Traceroute can therefore 152 derive the IP address of the first hop from the header of the ICMP 153 message and evaluate the RTT between the source and the first hop. 154 The next hops are discovered following the same procedure, taking 155 care of increasing at each step the TTL value of the outgoing probes 156 by one. The TTL value is increased until either an ICMP 157 PORT_UNREACHABLE message is received, meaning that the destination 158 has been reached, or the maximum configured number of hops has been 159 hit. 161 Some implementations, use ICMP Echos, instead of UDP datagrams. 162 However, many routers do not return ICMP messages about ICMP 163 messages, i.e. no ICMP TIME_EXCEEDED is returned for an ICMP Echo. 164 Therefore, in this draft we RECOMMEND to base implementations on UDP 165 datagrams. 167 2.1. Traceroute Configuration Parameters 169 In order to define an information model for storing traceroutes, we 170 first investigated which configuration parameters are relevant when 171 running traceroute. We considered four major traceroute 172 implementations and compared them based on configurable parameters 173 and default values. The LINUX (SUSE 9.1), BSD (FreeBSD 7.0) and UNIX 174 (SunOS 5.9) implemetations are based on UDP datagrams, while the 175 WINDOWS (XP SP2) one uses ICMP Echos. The comparison is summarized 176 in the following table, where an N/A in the option column, means that 177 such parameter is not configurable for the specific implementation. 178 A comprehensive comparison of available implementations is outside 179 the scope of this draft; however, already by sampling a few different 180 implementations, we can observe that they can differ quite 181 significantly in terms of configurable parameters and also default 182 values. Note that in the following table we reported only those 183 options which are available in at least two of the considered 184 implementations. 186 +---------------------------------------------------------+ 187 | OS |Option| Description | Default | 188 +--------+------+-------------------------------+---------+ 189 | LINUX | -m |Specify the maximum TTL used | 30 | 190 |--------+------|in outgoing probes. |---------| 191 | FreeBSD| -m | | OS var | 192 |--------+------| |---------| 193 | UNIX | -m | | 30 | 194 |--------+------| |---------| 195 | WINDOWS| -h | | 30 | 196 +--------+------+-------------------------------+---------+ 197 | LINUX | -n |Display hop addresses | - | 198 |--------+------|numerically rather than |---------| 199 | FreeBSD| -n |simbolically. | - | 200 |--------+------| |---------| 201 | UNIX | -n | | - | 202 |--------+------| |---------| 203 | WINDOWS| -d | | - | 204 +--------+------+-------------------------------+---------+ 205 | LINUX | -w |Set the time to wait for a | 3 sec | 206 |--------+------|response to a probe. |---------| 207 | FreeBSD| -w | | 5 sec | 208 |--------+------| |---------| 209 | UNIX | -w | | 5 sec | 210 |--------+------| |---------| 211 | WINDOWS| -w | | 4 sec | 212 +--------+------+-------------------------------+---------+ 213 | LINUX | N/A |Specify a loose source route | - | 214 |--------+------|gateway (to direct the |---------| 215 | FreeBSD| -g |traceroute through routers not | - | 216 |--------+------|necessarily in the path). |---------| 217 | UNIX | -g | | - | 218 |--------+------| |---------| 219 | WINDOWS| -g | | - | 220 +--------+------+-------------------------------+---------+ 221 | LINUX | -p |Set the base UDP port number | 33434 | 222 |------- +------|used in probes |---------| 223 | FreeBSD| -p |(UDP port = base + nhops - 1). | 33434 | 224 |--------+------| |---------| 225 | UNIX | -p | | 33434 | 226 |--------+------| |---------| 227 | WINDOWS| N/A | | - | 228 +--------+------+-------------------------------+---------+ 229 | LINUX | -q |Set the number of probes per | 3 | 230 |--------+------|TTL. |---------| 231 | FreeBSD| -q | | 3 | 232 |--------+------| |---------| 233 | UNIX | -q | | 3 | 234 |--------+------| |---------| 235 | WINDOWS| N/A | | 3 | 236 +--------+------+-------------------------------+---------+ 237 | LINUX | -S |Set the IP source address in |IP | 238 |--------+------|outgoing probes to the |address | 239 | FreeBSD| -s |specified value. |of the | 240 |--------+------| |out | 241 | UNIX | -s | |interface| 242 |--------+------| | | 243 | WINDOWS| N/A | | | 244 +--------+------+-------------------------------+---------+ 245 | LINUX | -t |Set the type-of-service (TOS) | 0 | 246 |--------+------|in the probes to the specified |---------| 247 | FreeBSD| -t |value. | 0 | 248 |--------+------| |---------| 249 | UNIX | -t | | 0 | 250 |--------+------| |---------| 251 | WINDOWS| N/A | | 0 | 252 +--------+------+-------------------------------+---------+ 253 | LINUX | -v |Verbose output: received ICMP | - | 254 |--------+------|packets other than |---------| 255 | FreeBSD| -v |TIME_EXCEEDED and | - | 256 |--------+------|UNREACHABLE are listed. |---------| 257 | UNIX | -v | | - | 258 |--------+------| |---------| 259 | WINDOWS| N/A | | - | 260 +--------+------+-------------------------------+---------+ 261 | LINUX | N/A |Set the time (in msec) to | - | 262 |--------+------|pause between probes. |---------| 263 | FreeBSD| -z | | 0 | 264 |--------+------| |---------| 265 | UNIX | -P | | 0 | 266 |--------+------| |---------| 267 | WINDOWS| N/A | | - | 268 +--------+------+-------------------------------+---------+ 269 | LINUX | -r |Bypass the normal routing | - | 270 |--------+------|tables and send directly to a |---------| 271 | FreeBSD| -r |host on attached network. | - | 272 |--------+------| |---------| 273 | UNIX | -r | | - | 274 |--------+------| |---------| 275 | WINDOWS| N/A | | - | 276 +--------+------+-------------------------------+---------+ 277 | LINUX | -f |Set the initial TTL for the | 1 | 278 |--------+------|first probe. |---------| 279 | FreeBSD| -f | | 1 | 280 |--------+------| |---------| 281 | UNIX | -f | | 1 | 282 |--------+------| |---------| 283 | WINDOWS| N/A | | 1 | 284 +--------+------+-------------------------------+---------+ 285 | LINUX | -F |Set the "don't fragment" bit. | - | 286 |--------+------| |---------| 287 | FreeBSD| -F | | - | 288 |--------+------| |---------| 289 | UNIX | -F | | - | 290 |--------+------| |---------| 291 | WINDOWS| N/A | | - | 292 +--------+------+-------------------------------+---------+ 293 | LINUX | N/A |Enables socket level debugging.| - | 294 |--------+------| |---------| 295 | FreeBSD| -d | | - | 296 |--------+------| |---------| 297 | UNIX | -d | | - | 298 |--------+------| |---------| 299 | WINDOWS| N/A | | - | 300 +--------+------+-------------------------------+---------+ 301 | LINUX | N/A |Use ICMP ECHO instead of UDP | - | 302 |--------+------|datagrams. |---------| 303 | FreeBSD| -I | | - | 304 |--------+------| |---------| 305 | UNIX | -I | | - | 306 |--------+------| |---------| 307 | WINDOWS| N/A | | - | 308 +--------+------+-------------------------------+---------+ 309 | LINUX | -I |Specify a network interface to | - | 310 |--------+------|obtain the IP address for |---------| 311 | FreeBSD| -i |outgoing IP packets | - | 312 |--------+------|(alternative to option -s). |---------| 313 | UNIX | -i | | - | 314 |--------+------| |---------| 315 | WINDOWS| N/A | | - | 316 +--------+------+-------------------------------+---------+ 317 | LINUX | N/A |Toggle checksum. | - | 318 |--------+------| |---------| 319 | FreeBSD| -x | | - | 320 |--------+------| |---------| 321 | UNIX | -x | | - | 322 |--------+------| |---------| 323 | WINDOWS| N/A | | - | 324 +--------+------+-------------------------------+---------+ 325 | LINUX | - |As optional last paramater, |Depends | 326 |--------+------|LINUX, FreeBSD and UNIX |on | 327 | FreeBSD| - |implementations allow |implement| 328 |--------+------|specifying the probe datagram |ation. | 329 | UNIX | - |length for outgoing probes. | | 330 |--------+------| | | 331 | WINDOWS| N/A | | | 332 +--------+------+-------------------------------+---------+ 334 3. Known Problems with Traceroute 336 3.1. Accuracy of Results 338 A known inconsistency exists between the round-trip delay metric 339 defined by the IPPM working group and the results returned by the 340 current traceroute implementations. Unfortunately, it is unlikely 341 that the traceroute implementations will implement the standard 342 definition in the near future. In order to compare results of 343 different traceroute measurements, specifications both of the 344 operating system (name and version) and of the traceroute tool 345 version used are added to the metadata elements in order to help in 346 comparing metrics. Moreover, the traceroute has built-in 347 configurable mechanisms like time-outs and can experience problems 348 related to the crossing of firewalls; therefore some of the packets 349 that traceroute sends out end up being time-out or filtered. As a 350 consequence, it might not be possible to trace the path to a node or 351 there might not be a complete set of probes describing the RTT to 352 reach it. 354 3.2. Alternative traceroute Implementations 356 As stated above, the widespred use of firewalls might prevent UDP or 357 ICMP based traceroutes to completely trace the path to a destination, 358 since traceroute probes might end up being filtered. In some cases, 359 such limitation might be overcome by sending instead TCP packets to 360 specific ports that hosts located behind the firewall are listening 361 for connections on. TCP based implementations use TCP SYN or FYN 362 probes and listen for TIME_EXCEEDED messages, TCP RESET and other 363 messages from firewalls and gateways on the path. On the other hand, 364 some firewalls filter out TCP SYN packets to prevent denial of 365 service attacks, therefore the actual advantage of using TCP instead 366 of UDP traceroute depends mainly on firewall configurations, which 367 are not known in adavance. A detailed analysis of TCP based 368 traceroutes is outside the scope of this draft, therefore in the 369 sequel, we will restrict our focus to the most commonly implemented 370 UDP based traceroute. 372 4. Reports/results 374 The following list reports the information fields provided by all 375 traceroute implementations considered. The order in which they are 376 reported here is not relevant and it changes in different 377 implementations. For each hop the information reported is: 378 o the hop index; 379 o the host symbolical address, provided that at least one of the 380 probes received a response, the symbolic address could be resolved 381 at the correponding host and that the option to display only 382 numerical addresses was not set; 383 o the host IP address, provided that at least one of the probes 384 received a response; 385 o the RTT for each response to a probe. 386 Depending on the traceroute implementation, additional information 387 might be displayed in the output (for instance MPLS-related 388 information). 390 It might happen that some probes do not receive a response within the 391 configured time-out (for instance if the probe is filtered out by a 392 firewall). In this case, an "*" is displayed in place of the RTT. 393 Besides, for delays below 1 ms, some implementations reports 0 ms 394 (f.i. UNIX and LINUX) while WINDOWS tracert reports "< 1 ms". 396 5. Information Model for Storing Traceroute Measurements 398 This section describes the information model for the traceroute 399 measurements data storing. The information model is composed of 400 information elements; for defining these information elements, a 401 template is used. Such template is specified in the list below: 403 o name - A unique and meaningful name for the information element. 404 The preferred spelling for the name is to use mixed case if the 405 name is compound, with an initial lower case letter, e.g., 406 "sourceIpAddress". 407 o description - The semantics of this information element. 408 o dataType - One of the types listed in Section 5.1 of this document 409 or in an extension of the information model. The type space for 410 attributes is constrained to facilitate implementation. 411 o units - If the element is a measure of some kind, the units 412 identify what the measure is. 413 o default value - The default value for the element (where 414 applicable). 416 5.1. Data Types 418 This section describes the set of valid data types of the information 419 model. 421 o String - The type "String" represents a finite length string of 422 valid characters from the Unicode character encoding set. Unicode 423 allows for ASCII and many other international character sets to be 424 used. It is expected that strings will be encoded in UTF-8 425 format, which is identical in encoding for USASCII characters, but 426 also accomodates other Unicode multibyte characters. 427 o InetAddressType - The type "InetAddressType" represents a type of 428 Internet address. The allowed values are to be intended as 429 imported from [RFC4001]; an additional allowed value is 430 "asnumber". 431 o InetAddress - The type "InetAddress" denotes a generic Internet 432 address. The allowed values are to be intended as imported from 433 [RFC4001]; an additional allowed value is the AS number to be 434 indicated as the actual number plus the indication how the mapping 435 from IP address to AS number was performed. 436 o TruthValue - The type "TruthValue" represents a boolean value. 437 The allowed values are to be intended as imported from [RFC2579]. 438 o Unsigned32 - The type "Unsigned32" represents a value in the range 439 (0..4294967295). 440 o InterfaceIndexOrZero - The type "InterfaceIndexOrZero" is an 441 extension of the InterfaceIndex convention. The latter defines a 442 greater than zero value used to identify an interface or interface 443 sub-layer in the system. This extension permits the additional 444 value of zero. Examples of the usage of zero might include 445 situations where interface was unknown, or when none or all 446 interfaces need to be referenced. The allowed values are to be 447 intended as imported from [RFC2863]. 448 o ProbesType - The type "ProbesType" represents a way of indicating 449 the protocol used for the traceroute probes. Allowed values are 450 UDP, TCP, ICMP. 451 o DateAndTime - The type "DateAndTime" represents a date-time 452 specification. The allowed values are to be intended as imported 453 from [RFC2579] apart from the fact that in this document there is 454 the need to use a milli-second resolution instead a deci-second 455 one. 456 o OperationResponseStatus - The type "OperationResponseStatus" is 457 used to report the result of an operation. The allowed values are 458 to be intended as imported from [RFC4560]. 460 5.2. Information Elements 462 This section describes the elements of the traceroute measurement. 463 The elements are grouped in two groups (Configuration and Results) 464 according to their semantics. In order to relate configuration and 465 results elements by means of a common unique identifier, an 466 additional element is defined belonging to both the two groups. 468 5.2.1. Configuration Information Elements 470 This section describes the elements of the traceroute measurement 471 that are specific to traceroute configuration. 473 5.2.1.1. CtlTargetAddressType 475 o name - CtlTargetAddressType 476 o description - Specifies the type of host address used in the 477 traceroute command. 478 o dataType - InetAddressType 479 o units - N/A 480 o default value - N/A 482 5.2.1.2. CtlTargetAddress 484 o name - CtlTargetAddress 485 o description - Specifies the host address used in the traceroute 486 command. The host address type can be determined by the examining 487 the value of the corresponding CtlTargetAddressType. 488 o dataType - InetAddress 489 o units - N/A 490 o default value - N/A 492 5.2.1.3. CtlByPassRouteTable 494 o name - CtlByPassRouteTable 495 o description - Specifies if the optional bypassing of the route 496 table was enabled or not. If enabled, the traceroute will bypass 497 the normal routing tables and send directly to a host on an 498 attached network. If the host is not on a directly-attached 499 network, an error is returned. This option can be used to perform 500 the traceroute operation to a local host through an interface that 501 has no route defined. 502 o dataType - TruthValue 503 o units - N/A 504 o default value - false 506 5.2.1.4. CtlProbeDataSize 508 o name - CtlProbeDataSize 509 o description - Specifies the size of the data portion of a 510 traceroute operation in octets. If the RECOMMENDED traceroute 511 method (UDP datagrams as probes) is used, then the value contained 512 in this object is exact. If another traceroute method is used for 513 which the specified size is not appropriate, then the 514 implementation should have used whatever size (appropriate to the 515 method) is closest to the specified size. The maximum value for 516 this object was computed by substracting the smallest possible IP 517 header size of 20 octets (IPv4 header with no options) and the UDP 518 header size of 8 octets from the maximum IP packet size. An IP 519 packet has a maximum size of 65535 octets (excluding IPv6 520 Jumbograms). 521 o dataType - Unsigned32 522 o units - octects 523 o default value - 0 525 5.2.1.5. CtlTimeOut 527 o name - CtlTimeOut 528 o description - Specifies the time-out value, in seconds, for the 529 traceroute operation. 530 o dataType - Unsigned32 531 o units - seconds 532 o default value - 3 534 5.2.1.6. CtlProbesPerHop 536 o name - CtlProbesPerHop 537 o description - Specifies the number of times to reissue a 538 traceroute request with the same time-to-live (TTL) value. 539 o dataType - Unsigned32 540 o units - probes 541 o default value - 3 543 5.2.1.7. CtlPort 545 o name - CtlPort 546 o description - Specifies the base UDP port used by the traceroute 547 operation. Need to specify a port that is not in use at the 548 destination (target) host. The default value for this object is 549 the IANA assigned port, 33434, for the traceroute function. 550 o dataType - Unsigned32 551 o units - UDP Port 552 o default value - 33434 554 5.2.1.8. CtlMaxTtl 556 o name - CtlMaxTtl 557 o description - Specifies the maximum TTL value for the traceroute 558 operation. 559 o dataType - Unsigned32 560 o units - time-to-live value 561 o default value - 30 563 5.2.1.9. CtlDSField 565 o name - CtlDSField 566 o description - Specifies the value that was stored in the 567 Differentiated Services (DS) field in the IP packet used to 568 encapsulate the traceroute probe. The DS Field is defined as the 569 Type of Service (TOS) octet in a IPv4 header or as the Traffic 570 Class octet in a IPv6 header. The value of this object must be a 571 decimal integer in the range from 0 to 255. This option can be 572 used to determine what effect an explicit DS field setting has on 573 a traceroute response. Not all values are legal or meaningful. 574 Useful TOS octet values are probably '16' (low delay) and '8' 575 (high throughput). Further references can be found in [RFC2474] 576 for the definition of the Differentiated Services (DS) field and 577 to [RFC1812] Section 5.3.2 for Type of Service (TOS). 578 o dataType - Unsigned32 579 o units - N/A 580 o default value - 0 582 5.2.1.10. CtlSourceAddressType 584 o name - CtlSourceAddressType 585 o description - Specifies the type of the source address, 586 CtlSourceAddress, used when performing the traceroute operation. 587 o dataType - InetAddressType 588 o units - N/A 589 o default value - N/A 591 5.2.1.11. CtlSourceAddress 593 o name - CtlSourceAddress 594 o description - Specifies the IP address (which has to be given as 595 an IP number, not a hostname) as the source address used in 596 outgoing probe packets. On hosts with more than one IP address, 597 this option can be used to force the source address to be 598 something other than the primary IP address of the interface the 599 probe packet is sent on. A zero length octet string value for 600 this object means that source address specification was disabled. 601 The address type (InetAddressType) that relates to this object is 602 specified by the corresponding value of CtlSourceAddressType. 603 o dataType - InetAddress 604 o units - N/A 605 o default value - N/A 607 5.2.1.12. CtlIfIndex 608 o name - CtlIfIndex 609 o description - Specifies the inferface index used in the traceroute 610 operation for sending the traceroute probes. A value of zero for 611 this object implies that the interface was unknown. 612 o dataType - InterfaceIndexOrZero 613 o units - N/A 614 o default value - 0 616 5.2.1.13. CtlMiscOptions 618 o name - CtlMiscOptions 619 o description - Specifies implementation dependent options. 620 o dataType - String 621 o units - N/A 622 o default value - N/A 624 5.2.1.14. CtlMaxFailures 626 o name - CtlMaxFailures 627 o description - Specifies the maximum number of consecutive timeouts 628 allowed before terminating a traceroute operation. A value of 629 either 255 (maximum hop count/possible TTL value) or a 0 indicates 630 that the function of terminating a remote traceroute operation 631 when a specific number of consecutive timeouts are detected was 632 disabled. This element is included to give full compatibility 633 with [RFC4560]. No known implementation of traceroute currently 634 supports it. 635 o dataType - Unsigned32 636 o units - timeouts 637 o default value - 5 639 5.2.1.15. CtlDontFragment 641 o name - CtlDontFragment 642 o description - Specifies if the don't fragment flag (DF) in the IP 643 header for a probe was enabled or not. Setting the DF flag can be 644 used for performing a manual PATH MTU test. 645 o dataType - TruthValue 646 o units - N/A 647 o default value - false 649 5.2.1.16. CtlInitialTtl 651 o name - CtlInitialTtl 652 o description - Specifies the initial TTL value used in a traceroute 653 operation. Such TTL setting is intended to bypass the initial 654 (often well known) portion of a path. 656 o dataType - Unsigned32 657 o units - N/A 658 o default value - 1 660 5.2.1.17. CtlDescr 662 o name - CtlDescr 663 o description - The purpose of this element is to provide a 664 description of the traceroute test. 665 o dataType - String 666 o units - N/A 667 o default value - N/A 669 5.2.1.18. CtlType 671 o name - CtlType 672 o description - Specifies the implementation method used for the 673 traceroute operation. It specifies if the traceroute is using 674 TCP, UDP or ICMP probes. 675 o dataType - ProbesType 676 o units - N/A 677 o default value - UDP 679 5.2.2. Results Information Elements 681 This section describes the elements of the traceroute measurement 682 that are specific to the results of a traceroute operation. 684 5.2.2.1. ResultsStartDateAndTime 686 o name - ResultsStartDateAndTime 687 o description - Specifies the date and start time of the traceroute 688 operation. This is the time when the first probe was seen at the 689 sending interface. 690 o dataType - DateAndTime 691 o units - N/A 692 o default value - N/A 694 5.2.2.2. ResultsIpTgtAddrType 696 o name - ResultsIpTgtAddrType 697 o description - Specifies the type of address stored in the 698 corresponding ResultsIpTgtAddr element. 699 o dataType - InetAddressType 700 o units - N/A 701 o default value - N/A 703 5.2.2.3. ResultsIpTgtAddr 705 o name - ResultsIpTgtAddr 706 o description - Specifies the IP address associated with a 707 CtlTargetAddress value when the destination address is specified 708 as a DNS name. The value of this object should be a zero length 709 octet string when a DNS name is not specified or when a specified 710 DNS name fails to resolve. 711 o dataType - InetAddress 712 o units - N/A 713 o default value - N/A 715 5.2.2.4. Index 717 o name - Index 718 o description - Specifies an index that consecutively numbers all 719 probes for which a reply was received in the sequential order in 720 which the replies were received. The maximum value for this 721 object is CtlMaxTtl*CtlProbesPerHop. 722 o dataType - Unsigned32 723 o units - N/A 724 o default value - N/A 726 5.2.2.5. HopIndex 728 o name - HopIndex 729 o description - Specifies which hop in a traceroute path that the 730 probe's results are for. 731 o dataType - Unsigned32 732 o units - N/A 733 o default value - N/A 735 5.2.2.6. IndexPerHop 737 o name - IndexPerHop 738 o description - Specifies the index of a probe for a particular hop 739 in a traceroute path. The number of probes per hop is determined 740 by the value of the corresponding CtlProbesPerHop element. 741 o dataType - Unsigned32 742 o units - N/A 743 o default value - N/A 745 5.2.2.7. HopAddrType 747 o name - HopAddrType 748 o description - Specifies the type of address stored in the 749 corresponding HopAddr element. 751 o dataType - InetAddressType 752 o units - N/A 753 o default value - N/A 755 5.2.2.8. HopAddr 757 o name - HopAddr 758 o description - Specifies the address of a hop in the traceroute 759 path. This object is not allowed to be a DNS name. The value of 760 the corresponding object, HopAddrType, indicates this object's IP 761 address type. 762 o dataType - InetAddress 763 o units - N/A 764 o default value - N/A 766 5.2.2.9. HopGeoLocation 768 o name - HopGeoLocation 769 o description - Specifies the geo location of a hop in the 770 traceroute path. 771 o dataType - String 772 o units - N/A 773 o default value - N/A 775 5.2.2.10. MPLSTopLabel 777 o name - MPLSTopLabel 778 o description - Specifies the top entry of the MPLS label stack of a 779 probe observed when the probe arrived at the hop that replied to 780 the probe. This object contains the top MPLS label stack entry as 781 32 bit value as it is observed on the MPLS label stack. Contained 782 in this single number are the MPLS label, the Exp field, the S 783 flag, and the MPLS TTL value as specified in RFC 3032 [RFC3032]. 784 o dataType - Unsigned32 785 o units - N/A 786 o default value - N/A 788 5.2.2.11. RoundTripTime 790 o name - RoundTripTime 791 o description - Specifies the amount of time measured in 792 milliseconds from when a probe was sent to when its response was 793 received or when it timed out. The value of this element is 794 reported as the truncation of the number reported by the 795 traceroute tool (the output "< 1 ms" is therefore encoded as 0 796 ms). A string with the value of "RoundTripTimeNotAvailable" means 797 either the probe was lost because of a timeout or it was not 798 possible to transmit a probe. 800 o dataType - Unsigned32 or String 801 o units - milliseconds or N/A 802 o default value - N/A 804 5.2.2.12. ResponseStatus 806 o name - ResponseStatus 807 o description - Specifies the result of a traceroute operation made 808 by the host for a particular probe. 809 o dataType - OperationResponseStatus 810 o units - N/A 811 o default value - N/A 813 5.2.2.13. Time 815 o name - Time 816 o description - Specifies the timestamp for when the response to the 817 probe was received interface. 818 o dataType - DateAndTime 819 o units - N/A 820 o default value - N/A 822 5.2.2.14. ResultsHopRawOutputData 824 o name - ResultsHopRawOutputData 825 o description - Specifies the raw output data returned by the 826 traceroute operation for a certain hop in a traceroute path. 827 o dataType - String 828 o units - N/A 829 o default value - N/A 831 5.2.2.15. ResultsEndDateAndTime 833 o name - ResultsEndDateAndTime 834 o description - Specifies the date and end time of the traceroute 835 operation. It is either the time when the response to the last 836 probe of the traceroute operation was received or the time when 837 the last probe of the traceroute operation was sent plus the 838 relative timeout (in case of missing response). 839 o dataType - DateAndTime 840 o units - N/A 841 o default value - N/A 843 5.2.3. Information Element Correlating Configuration and Results 844 Elements 846 This section defines an additional element belonging to both the two 847 previous groups. This element is defined in order to relate 848 configuration elements and results ones by means of a common unique 849 identifier. 851 5.2.3.1. TestName 853 o name - TestName 854 o description - Specifies the name of a traceroute test. This is 855 locally unique. 856 o dataType - String 857 o units - N/A 858 o default value - N/A 860 6. Data Model for Storing Traceroute Measurements 862 For storing and transmitting information according to the information 863 model defined in the previous section, a data model is required that 864 specifies how to encode the elements of the information model. 866 There are several design choices for a data model. It can use a 867 binary or textual representation and it can be defined from scratch 868 or use already existing frameworks and data models. In general, the 869 use of already existing frameworks and models should be preferred. 871 Binary and textual representation both have advantages and 872 disadvantages. Textual representions are (with some limitations) 873 human readable while a binary representation consumes less resources 874 for storing, transmitting and parsing data. 876 An already existing and closely related data model is the DISMAN- 877 TRACEROUTE-MIB module [RFC4560], that specifies a BER encoding 878 [RFC3417] used by the Simple Network Management Protocol (SNMP) 879 [RFC3410] for transmitting traceroute information. This data model 880 is well suited and supported within network management systems, but 881 as a general format for storing and transmitting traceroute results 882 it is not easily applicable. 884 Another binary representation would be an extension of traffic flow 885 information encodings as specified for the IPFIX protocol 886 [I-D.ietf-ipfix-protocol], [I-D.ietf-ipfix-info]. The IPFIX protocol 887 is extensible. However, the architecture behind this protocol 888 [I-D.ietf-ipfix-architecture] is targeted at exporting passively 889 measured flow information. Therefore, some obstacles are expected 890 when trying to use it for transmitting traceroute measurement 891 results. 893 For textual representations, using the eXtensible Markup Language 894 (XML) [XML] is an obvious choice. XML supports clean structuring of 895 data and syntax checking of records. With some limitations it is 896 human readable. It is supported well by a huge pool of tools and 897 standards for generating, transmitting, parsing and converting it to 898 other data formats. Its disadvantages is the resource comsumption 899 for processing, storing, and transmitting information. Since the 900 expected data volumes of traceroute data in network operation and 901 maintenance is not expected to be extremly high, the inefficient 902 usage of resources is not a significant disadvantage. Therefore, XML 903 was chosen as basis for the traceroute information model that is 904 specified in this section. 906 Section 7 contains the XML schema to be used as a template for 907 storing and/or exchanging traceroute measurements. The schema was 908 designed in order to use an extensible approach based on templates 909 (pretty similar to how IPFIX protocol is designed) where the 910 traceroute configuration elements (both the requested parameters, 911 Request, and the actual parameters used, MeasurementMetadata) are 912 metadata to be referenced by results information elements (data) by 913 means of the TestName element (used as unique identifier). Currently 914 Global Grid Forum (GGF) is also using this approach and cross- 915 requirements have been analyzed. As a result of this analysis the 916 XML schema contained in Section 7 is compatible with GGF schema since 917 it was designed in a way that both limits the unecessary redundancy 918 and a simple one-to-one trasformation between the two exist. 920 7. XML Schema for traceroute Measurements 922 923 926 927 928 929 930 931 932 933 934 936 937 938 939 940 941 942 943 944 946 947 948 949 950 952 953 954 957 958 960 961 962 964 965 967 968 969 970 971 973 974 975 977 978 979 980 981 982 983 984 985 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1003 1004 1005 1007 1008 1009 1010 1011 1013 1014 1015 Specifies the name of a traceroute 1016 test. This is locally unique. 1017 1018 1019 1020 1021 1022 1024 1025 1026 Specifies the name of the operating 1027 system on which the traceroute was launched. 1028 1029 1030 1031 1032 1033 1035 1036 1037 Specifies the OS version on which the 1038 traceroute was launched. 1039 1040 1041 1042 1043 1044 1046 1047 1048 Specifies the version of the traceroute 1049 tool used. 1050 1051 1052 1053 1054 1055 1057 1058 1059 Specifies if the optional bypassing 1060 of the route table was enabled or not. If enabled, 1061 the traceroute will bypass the normal routing tables 1062 and send directly to a host on an attached network. 1063 If the host is not on a directly-attached network, 1064 an error is returned. This option can be used to 1065 perform the traceroute operation to a local host 1066 through an interface that has no route defined. 1067 1068 1069 1070 1072 1073 1074 Specifies the size of the data 1075 portion of a traceroute operation in octets. If the 1076 RECOMMENDED traceroute method (UDP datagrams as probes) 1077 is used, then the value contained in this object is 1078 exact. If another traceroute method is used for which 1079 the specified size is not appropriate, then the 1080 implementation should have used whatever size (appropriate 1081 to the method) is closest to the specified size. 1082 The maximum value for this object was computed by 1083 substracting the smallest possible IP header size of 20 1084 octets (IPv4 header with no options) and the UDP header 1085 size of 8 octets from the maximum IP packet size. An IP 1086 packet has a maximum size of 65535 octets (excluding IPv6 1087 jumbograms). Units are: octects. 1088 1089 1090 1091 1092 1093 1095 1096 1097 Specifies the time-out value, in 1098 seconds, for the traceroute operation. 1099 Units are: seconds. 1100 1101 1102 1103 1104 1105 1106 1108 1109 1110 Specifies the number of times to 1111 reissue a traceroute request with the same time-to-live 1112 (TTL) value. Units are: probes. 1113 1114 1115 1116 1117 1118 1119 1121 1122 1123 Specifies the base UDP port used by 1124 the traceroute operation. Need to specify a port that 1125 is not in use at the destination (target) host. 1126 The default value for this object is the IANA assigned 1127 port, 33434, for the traceroute function. 1128 Units are: UDP port. 1129 1130 1131 1132 1133 1135 1137 1138 1139 Specifies the maximum TTL value for 1140 the traceroute operation. 1141 Units are: time-to-live value. 1142 1143 1144 1145 1146 1147 1149 1150 1151 Specifies the value that was stored in 1152 the Differentiated Services (DS) field in the IP packet 1153 used to encapsulate the traceroute probe. The DS Field 1154 is defined as the Type of Service (TOS) octet in a IPv4 1155 header or as the Traffic Class octet in a IPv6 header. 1156 The value of this object must be a decimal integer in the 1157 range from 0 to 255. This option can be used to determine 1158 what effect an explicit DS field setting has on a 1159 traceroute response. Not all values are legal or 1160 meaningful. Useful TOS octet values are probably 1161 '16' (low delay) and '8' (high throughput). 1162 Further references can be found in the 1163 RFC 2474 for the definition of the Differentiated 1164 Services (DS) field and to the RFC 1812 Section 5.3.2 1165 for Type of Service (TOS). 1166 1167 1168 1169 1171 1172 1173 Specifies the inferface index used in the 1174 traceroute operation for sending the traceroute 1175 probes. A value of zero for this object implies 1176 that the interface was unknown. 1177 1178 1179 1180 1182 1183 1184 Specifies implementation dependent 1185 options. 1186 1187 1188 1189 1190 1192 1193 1194 Specifies the maximum number of 1195 consecutive timeouts allowed before terminating a 1196 traceroute operation. A value of either 255 1197 (maximum hop count/possible TTL value) or a 0 indicates 1198 that the function of terminating a remote traceroute 1199 operation when a specific number of consecutive 1200 timeouts are detected was disabled. This element is 1201 included to give full compatibility with DISMAN working 1202 group documents. No known implementation of traceroute 1203 currently supports it. 1204 Units are: timeouts. 1205 1206 1207 1208 1210 1211 1212 Specifies if the don't fragment flag 1213 (DF) in the IP header for a probe was enabled or not. 1214 Setting the DF flag can be used for performing 1215 a manual PATH MTU test. 1216 1217 1218 1219 1221 1222 1223 Specifies the initial TTL value 1224 used in a traceroute operation. Such 1225 TTL setting is intended to bypass the initial 1226 (often well known) portion of a path. 1227 1228 1229 1230 1232 1233 1235 1236 1237 The purpose of this element is to 1238 provide a description of the traceroute test. 1239 1240 1241 1242 1243 1244 1246 1247 1248 Specifies the implementation method 1249 used for the traceroute operation. It specifies if 1250 the traceroute is using TCP, UDP or ICMP probes. 1251 1252 1253 1254 1255 1256 1257 1258 1260 1261 1262 Specifies an index that consecutively 1263 numbers all probes for which a reply was received in the 1264 sequential order in which the replies were received. 1265 The maximum value for this object is 1266 CtlMaxTtl*CtlProbesPerHop. 1267 1268 1269 1270 1271 1272 1273 1275 1276 1277 Specifies which hop in a traceroute 1278 path that the probe's results are for. The value of 1279 this element is initially determined by the value of 1280 CtlInitialTtl. 1281 1282 1283 1284 1285 1286 1288 1289 1290 Specifies the index of a probe for 1291 a particular hop in a traceroute path. The number of 1292 probes per hop is determined by the value of the 1293 corresponding CtlProbesPerHop element. 1294 1295 1296 1297 1298 1299 1300 1302 1303 1304 Specifies the geo location of a hop 1305 in the traceroute path. 1306 1307 1308 1309 1310 1311 1313 1314 1315 Specifies the top entry of the MPLS label 1316 stack of a probe observed when the probe arrived at the hop 1317 that replied to the probe. This object contains the top 1318 MPLS label stack entry as 32 bit value as it is observed on 1319 the MPLS label stack. Contained in this single number are 1320 the MPLS label, the Exp field, the S flag, and the MPLS TTL 1321 value as specified in RFC 3032 [RFC3032]. 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1334 1335 1336 1337 1338 1340 1341 1342 Specifies the raw output data returned 1343 by the traceroute operation for a certain hop in a 1344 traceroute path. 1345 1346 1347 1348 1349 1350 1352 1353 1354 Specifies the AS number of a hop in the 1355 traceroute path as a 24 bit number and the indication how 1356 the mapping from IP address to AS number was performed. 1357 1358 1359 1361 1363 1364 1366 1367 1368 1370 1372 1374 1377 1379 1380 1382 1383 1384 1386 1388 1390 1392 1394 1395 1397 1398 1399 1401 1403 1404 1406 1407 1408 Specifies the type of host address 1409 used in the traceroute command. 1410 1411 1412 1413 1415 1416 1418 1419 1420 Specifies the host address used in 1421 the traceroute command. The host address type can be 1422 determined by the examining the value of the 1423 corresponding CtlTargetAddressType. 1424 1426 1427 1428 1429 1430 1432 1433 1434 Specifies the type of the source address, 1435 CtlSourceAddress, used when performing the 1436 traceroute operation. 1437 1438 1439 1440 1442 1443 1445 1446 1447 Specifies the IP address (which has 1448 to be given as an IP number, not a hostname) as the 1449 source address used in outgoing probe packets. On hosts 1450 with more than one IP address, this option can be used 1451 to force the source address to be something other than 1452 the primary IP address of the interface the probe packet 1453 is sent on. A zero length octet string value for this 1454 object means that source addres specification was disabled. 1455 The address type (InetAddressType) that relates to this 1456 object is specified by the corresponding value of 1457 CtlSourceAddressType. 1458 1459 1460 1461 1463 1464 1466 1467 1468 Specifies the date and start time of the 1469 traceroute operation. This is the time when the first probe 1470 was sent. 1471 1472 1473 1474 1475 1476 1478 1479 1480 Specifies the type of address stored 1481 in the corresponding ResultsIpTgtAddr element. 1482 1483 1484 1485 1487 1488 1490 1491 1492 Specifies the IP address associated 1493 with a CtlTargetAddress value when the 1494 destination address is specified as a DNS name. 1495 The value of this object should be a zero length octet 1496 string when a DNS name is not specified or when a 1497 specified DNS name fails to resolve. 1498 1499 1500 1501 1503 1504 1506 1507 1508 Specifies the type of address stored 1509 in the corresponding HopAddr element. 1510 1511 1512 1513 1515 1516 1518 1519 1520 Specifies the address of a hop in 1521 the traceroute path. This object is not allowed to 1522 be a DNS name. The value of the corresponding object, 1523 HopAddrType, indicates this object's IP address type. 1524 1525 1526 1527 1529 1530 1532 1533 1534 Specifies the amount of time measured 1535 in milliseconds from when a probe was sent to when its 1536 response was received or when it timed out. The value 1537 of this element is reported as the truncation of the 1538 number reported by the traceroute tool (the output 1539 "<1 ms" is therefore encoded as 0 ms). 1540 A string with the value of "RoundTripTimeNotAvailable" 1541 means either the probe was lost because of a timeout 1542 or it was not possible to transmit a probe. 1543 Units are: milliseconds. 1544 1545 1546 1547 1549 1551 1552 1554 1555 1556 Specifies the result of a traceroute 1557 operation made by the host for a particular probe. 1558 1559 1560 1561 1563 1564 1566 1567 1568 Specifies the timestamp when the 1569 response to the probe was received. 1571 1572 1573 1574 1575 1576 1578 1579 1580 1582 1584 1586 1588 1590 1593 1596 1598 1600 1602 1603 1605 1606 1607 Specifies the date and end time of 1608 the traceroute operation. It is either the time when 1609 the response to the last probe of the traceroute 1610 operation was received or the time when the last 1611 probe of the traceroute operation was sent plus the 1612 relative timeout (in case of missing response). 1613 1614 1615 1616 1617 1618 1619 1620 1621 Specifies the metadata for a 1622 traceroute operation. In a request, these are the 1623 requested parameters. In a response, they are the 1624 actual parameters used. 1625 1626 1627 1628 1630 1633 1636 1639 1641 1643 1647 1650 1653 1656 1659 1662 1665 1668 1670 1673 1676 1679 1682 1685 1688 1692 1693 1695 1696 1697 1698 Contains the actual traceroute measurement. 1699 1700 1701 1702 1704 1706 1708 1710 1713 1717 1719 1720 1722 1723 1724 1725 1727 1728 1729 1731 1732 1733 1735 1736 1737 1739 1741 1742 1743 1745 1747 1748 1749 1751 1753 1754 1755 1757 1759 1761 1762 1763 1764 1765 1767 1769 8. Differences to DISMAN-TRACEROUTE-MIB 1771 For performing remote traceroute operations at managed node, the IETF 1772 has standardized the DISMAN-TRACEROUTE-MIB module in RFC 4560 1773 [RFC4560]. This module allows: 1775 o retrieving capability information of the traceroute implementation 1776 at the managed node, 1777 o configuring traceroute operations to be prformed, 1778 o retrieving information about ongoing and completed traceroute 1779 measurements, 1780 o retrieving traceroute measurement statistics. 1782 The traceroute storage format described in this document has 1783 significant overlaps with this MIB module. Particularly, the models 1784 for the traceroute measurement configuration and for the result from 1785 completed measurements are almost identical. But for other pats of 1786 the DISMAN-TRACEROUTE MIB module there is no need to model them in a 1787 traceroute storage format. Particularly, the capability information, 1788 information about ongoing measurements and measurement statistics are 1789 not covered by the traceroute storage model. 1791 Concerning traceroute measurements and results, there are structural 1792 differences between the two models caused by the different choices 1793 for the encoding of the specification. For DISMAN-TRACEROUTE-MIB, 1794 the Structure of Management Information (SMIv2, STD 58, RFC 2578 1795 [RFC2578]) was used, while for the traceroute storage format is 1796 encoded using XML. 1798 This difference in structure implies that the DISMAN-TRACEROUTE-MIB 1799 module contains SMI-specific information element (managed objects) 1800 that concern tables of managed objects (specification, entry creation 1801 and delection, status retrieval) that are not required for the XML- 1802 encoded traceroute storage format. 1804 But for most of the remaining information elements that concern 1805 configuration of traceroute measurements and results of completed 1806 measurements, the semantics is identical between the DISMAN- 1807 TRACEROUTE-MIB module and the traceroute storage format. There are 1808 very few exceptions to this which are listed below. Also naming of 1809 information elements is identical between both models with a few 1810 exceptions. For the traceroute storage model, a few information 1811 elements have been added, some because of the different structure and 1812 some to provide additional information on completed measurements. 1814 8.1. Naming 1816 Basically, names in both models are chosen using the same naming 1817 conventions. 1819 For the traceroute measurement configuration information all names, 1820 such as CtlProbesPerHop, are identical in both models except for the 1821 traceRoute prefix that was removed to avoid unecessary redundancy in 1822 the XML file and for CtlDataSize which was renamed to 1823 CtlProbeDataSize for clarification in the traceroute storage model. 1825 Results of measurements in the DISMAN-TRACEROUTE-MIB modules are 1826 distributed over two tables, the traceRouteResultsTable containing 1827 mainly information about ongoing measurements and the 1828 traceRouteProbeHistoryTable containing only information about 1829 completed measurements. According to the SMIv2 naming conventions 1830 names of information elements in these tables have different prefixes 1831 (traceRouteResults and traceRouteProbeHistory). Since the traceroute 1832 storage format only reports on completed measurements, this 1833 separation is not needed anymore and the prefix "Results" is used for 1834 all related information elements. 1836 Beyond that, there are only a few changes in element names. The 1837 renaming actions include: 1839 o traceRouteProbeHistoryProbeIndex to IndexPerHop, 1840 o traceRouteProbeHistoryResponse to RoundTripTime, 1841 o traceRouteProbeHistoryTime to ResultsEndDateAndTime, 1842 o traceRouteProbeHistoryLastRC to ResultsHopRawOutputData. 1844 8.2. Semantics 1846 The semantics was changed for two information elements only. 1848 For traceRouteProbeHistoryResponse in the DISMAN-TRACEROUTE-MIB, a 1849 value of 0 indicated, that it was not possible to transmit a probe. 1850 For the traceroute strorage format, a value of 0 for element 1851 RoundTripTime indicates that the measured time was less than one 1852 millisecond, while for the case that it was not possible to transmit 1853 a probe a string is used that indicates the problem. 1855 For traceRouteCtlIfIndex in the DISMAN-TRACEROUTE-MIB, a value of 0 1856 indicated, that it the option to set the index is not available. 1857 This was translated to the traceroute strorage format, such that a 1858 value of 0 for this element indicates that the used interface is 1859 unknown. 1861 The element traceRouteProbeHistoryLastRC in the DISMAN-TRACEROUTE-MIB 1862 was replaced by element ResultsHopRawOutputData. While 1863 traceRouteProbeHistoryLastRC just reports a reply code, 1864 ResultsHopRawOutputData reports the full raw output data produced by 1865 the traceroute instance that was used. 1867 8.3. Additional Information Elements 1869 Only a few information elements have been added to the model of the 1870 DISMAN-TRACEROUTE-MIB module. 1872 o For providing geographical information about hops in the 1873 traceroute path, HopGeoLocation was added. 1874 o For providing the top MPLS label stack entry of a probe in the 1875 traceroute path MPLSTopLabel was added. 1876 o For providing additional timestamp beyond ResultsEndDateAndTime, 1877 ResultsStartDateAndTime and Time were added. 1879 9. Security Considerations 1881 Security considerations in this section discuss are grouped into 1882 considerations related to conducting traceroute measurements and 1883 considerations related to storing and transmitting results of 1884 measurements. 1886 This memo does not specify an implementation of a traceroute 1887 measurements. Neither does it specify a certain procedure for 1888 storing traceroute measurement results. Still it is considered 1889 desirable to discuss related security issues below. 1891 9.1. Conducting Traceroute Measurements 1893 Conducting Internet measurements can raise both security and privacy 1894 concerns. Traceroute measurements, in which traffic is injected into 1895 the network, can be abused for denial-of-service attacks disguised as 1896 legitimate measurement activity. 1898 Measurement parameters MUST be carefully selected so that the 1899 measurements inject trivial amounts of additional traffic into the 1900 networks they measure. If they inject "too much" traffic, they can 1901 skew the results of the measurement, and in extreme cases cause 1902 congestion and denial of service. 1904 The measurements themselves could be harmed by routers giving 1905 measurement traffic a different priority than "normal" traffic, or by 1906 an attacker injecting artificial measurement traffic. If routers can 1907 recognize measurement traffic and treat it separately, the 1908 measurements will not reflect actual user traffic. If an attacker 1909 injects artificial traffic that is accepted as legitimate, the loss 1910 rate will be artificially lowered. Therefore, the measurement 1911 methodologies SHOULD include appropriate techniques to reduce the 1912 probability measurement traffic can be distinguished from "normal" 1913 traffic. 1915 Authentication techniques, such as digital signatures, may be used 1916 where appropriate to guard against injected traffic attacks. 1918 9.2. Securing Traceroute Measurement Results 1920 Traceroute results are not considered highly sensible. Still, they 1921 may contain sensible information on network paths, routing states, 1922 use IP addresses, and roundtrip times, that the operator a networks 1923 may want to detect for business or security reasons. 1925 It is thus important to control access to Information acquired by 1926 conducting traceroute measurement, particularly when transmitting it 1927 over a networks but also when storing it. It is RECOMMENDED that 1928 transmission of traceroute measurement results over a network uses 1929 appropriate protection mechanisms for preserving privacy, integrity 1930 and authenticity. It is further RECOMMENDED that secure 1931 authentication and authorization are used for protecting stored 1932 traceroute results. 1934 10. IANA Considerations 1936 This document uses URNs to describe an XML namespace and an XML 1937 schema for traceroute measurements conforming to a registry mechanism 1938 described in [RFC3688]. Two URI assignments are requested. 1939 1. Registration request for the IPPM traceroute measurements 1940 namespace 1941 * URI: urn:ietf:params:xml:ns:traceroute-1.0 1942 * Registrant Contact: TBD. 1943 * XML: None. Namespace URIs do not represent an XML 1944 2. Registration request for the IPPM traceroute measurements schema 1945 * URI: urn:ietf:params:xml:schema:traceroute-1.0 1946 * Registrant Contact: TBD. 1947 * XML: See the section Section 7 of this document. 1949 11. References 1950 11.1. Normative References 1952 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1953 Schoenwaelder, "Textual Conventions for Internet Network 1954 Addresses", RFC 4001, February 2005. 1956 11.2. Informative References 1958 [I-D.ietf-disman-remops-mib-v2] 1959 Quittek, J. and K. White, "Definitions of Managed Objects 1960 for Remote Ping, Traceroute, and Lookup Operations", 1961 draft-ietf-disman-remops-mib-v2-09 (work in progress), 1962 February 2006. 1964 [I-D.ietf-ipfix-architecture] 1965 Sadasivan, G., "Architecture for IP Flow Information 1966 Export", draft-ietf-ipfix-architecture-12 (work in 1967 progress), September 2006. 1969 [I-D.ietf-ipfix-info] 1970 Quittek, J., "Information Model for IP Flow Information 1971 Export", draft-ietf-ipfix-info-14 (work in progress), 1972 October 2006. 1974 [I-D.ietf-ipfix-protocol] 1975 Claise, B., "Specification of the IPFIX Protocol for the 1976 Exchange", draft-ietf-ipfix-protocol-24 (work in 1977 progress), November 2006. 1979 [RFC1812] Baker, F., "Requirements for IP Version 4 Routers", 1980 RFC 1812, June 1995. 1982 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 1983 "Definition of the Differentiated Services Field (DS 1984 Field) in the IPv4 and IPv6 Headers", RFC 2474, 1985 December 1998. 1987 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1988 Schoenwaelder, Ed., "Structure of Management Information 1989 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1991 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1992 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1993 STD 58, RFC 2579, April 1999. 1995 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1996 MIB", RFC 2863, June 2000. 1998 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 1999 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 2000 Encoding", RFC 3032, January 2001. 2002 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2003 "Introduction and Applicability Statements for Internet- 2004 Standard Management Framework", RFC 3410, December 2002. 2006 [RFC3417] Presuhn, R., "Transport Mappings for the Simple Network 2007 Management Protocol (SNMP)", STD 62, RFC 3417, 2008 December 2002. 2010 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2011 January 2004. 2013 [RFC4560] Quittek, J. and K. White, "Definitions of Managed Objects 2014 for Remote Ping, Traceroute, and Lookup Operations", 2015 RFC 4560, June 2006. 2017 [XML] Yergeau et al., F., "Extensible Markup Language (XML) 1.0 2018 (Third Edition)", W3C Recommendation, February 2004. 2020 Authors' Addresses 2022 Saverio Niccolini 2023 Network Laboratories, NEC Europe Ltd. 2024 Kurfuersten-Anlage 36 2025 Heidelberg 69115 2026 Germany 2028 Phone: +49 (0) 6221 4342 118 2029 Email: saverio.niccolini@netlab.nec.de 2030 URI: http://www.netlab.nec.de 2032 Sandra Tartarelli 2033 Network Laboratories, NEC Europe Ltd. 2034 Kurfuersten-Anlage 36 2035 Heidelberg 69115 2036 Germany 2038 Phone: +49 (0) 6221 4342 132 2039 Email: sandra.tartarelli@netlab.nec.de 2040 URI: http://www.netlab.nec.de 2041 Juergen Quittek 2042 Network Laboratories, NEC Europe Ltd. 2043 Kurfuersten-Anlage 36 2044 Heidelberg 69115 2045 Germany 2047 Phone: +49 (0) 6221 4342 115 2048 Email: quittek@netlab.nec.de 2049 URI: http://www.netlab.nec.de 2051 Martin Swany 2052 Dept. of Computer and Information Sciences, University of Delaware 2053 Newark DE 19716 2054 U.S.A. 2056 Email: swany@UDel.Edu 2058 Full Copyright Statement 2060 Copyright (C) The IETF Trust (2007). 2062 This document is subject to the rights, licenses and restrictions 2063 contained in BCP 78, and except as set forth therein, the authors 2064 retain all their rights. 2066 This document and the information contained herein are provided on an 2067 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2068 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2069 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2070 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2071 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2072 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2074 Intellectual Property 2076 The IETF takes no position regarding the validity or scope of any 2077 Intellectual Property Rights or other rights that might be claimed to 2078 pertain to the implementation or use of the technology described in 2079 this document or the extent to which any license under such rights 2080 might or might not be available; nor does it represent that it has 2081 made any independent effort to identify any such rights. Information 2082 on the procedures with respect to rights in RFC documents can be 2083 found in BCP 78 and BCP 79. 2085 Copies of IPR disclosures made to the IETF Secretariat and any 2086 assurances of licenses to be made available, or the result of an 2087 attempt made to obtain a general license or permission for the use of 2088 such proprietary rights by implementers or users of this 2089 specification can be obtained from the IETF on-line IPR repository at 2090 http://www.ietf.org/ipr. 2092 The IETF invites any interested party to bring to its attention any 2093 copyrights, patents or patent applications, or other proprietary 2094 rights that may cover technology that may be required to implement 2095 this standard. Please address the information to the IETF at 2096 ietf-ipr@ietf.org. 2098 Acknowledgment 2100 Funding for the RFC Editor function is provided by the IETF 2101 Administrative Support Activity (IASA).