idnits 2.17.1 draft-ietf-sipping-torture-tests-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. == There are 9 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (August 2002) is 7924 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 section? '1' on line 44 looks like a reference -- Missing reference section? '2' on line 1273 looks like a reference -- Missing reference section? '3' on line 110 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPPING Working Group A. Johnston 3 Internet Draft WorldCom 4 Document: draft-ietf-sipping-torture-tests-00.txt J. Rosenberg 5 Expires: February 2003 dynamicsoft 6 H. Schulzrinne 7 Columbia U. 8 August 2002 10 Session Initiation Protocol Torture Test Messages 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This informational document gives examples of Session Initiation 35 Protocol (SIP) test messages designed to exercise and "torture" a 36 parser. They were developed as part of the SIPit SIP 37 interoperability testing events. 39 Conventions used in this document 41 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 42 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 43 document are to be interpreted as described in RFC-2119 [1]. 45 Table of Contents 47 1. Overview.......................................................3 48 SIP Torture Test Messages August 2002 50 2. SIP Test Messages..............................................3 51 2.1 INVITE Parser Torture Test Message.........................3 52 2.2 INVITE with Proxy-Require and Require......................4 53 2.3 INVITE with Unknown Schemes in URIs........................5 54 2.4 REGISTER with Y2038 Test...................................5 55 2.5 INVITE with inconsistent Accept and message body...........6 56 2.6 INVITE with non-SDP message body...........................6 57 2.7 Unknown Method Message.....................................7 58 2.8 Unknown Method with CSeq Error.............................7 59 2.9 REGISTER with Unknown Authorization Scheme.................8 60 2.10 Multiple SIP Request in a Single Message..................8 61 2.11 INVITE missing Required Headers...........................9 62 2.12 INVITE with Duplicate Required Headers...................10 63 2.13 INVITE with Illegal Expires Header.......................10 64 2.14 200 OK Response with Broadcast Via Header................11 65 2.15 INVITE with Invalid Via and Contact Headers..............12 66 2.16 INVITE with Incorrect Content-Length Header..............12 67 2.17 INVITE with Invalid Value for Content-Length.............13 68 2.18 INVITE with Garbage after Message Body...................14 69 2.19 INVITE with Error in Display Name in To Header...........14 70 2.20 INVITE with a Semicolon-Separated Parameter in the "user" 71 Part..........................................................15 72 2.21 INVITE with Illegal Enclosing of Request-URI in "<>"....15 73 2.22 INVITE with Illegal LWS within Elements of Request-URI...16 74 2.23 INVITE with illegal >1 SP between elements of Request URI17 75 2.24 INVITE with a legal SIP URI containing escaped characters17 76 2.25 INVITE with the illegal use of escaped headers in Request-URI 77 ..............................................................18 78 2.26 INVITE containing an unknown scheme in the Request URI...19 79 2.27 OPTIONS with no LWS between display name and <...........19 80 2.28 OPTIONS with extran LWS between display name and <.......20 81 2.29 INVITE with an illegal SIP Date format...................20 82 2.30 INVITE with Passed Expries Time..........................21 83 2.31 INVITE with Max-Forwards Set to Zero.....................21 84 2.32 REGISTER with a Escaped Header in a Legal SIP URI of a 85 Contact.......................................................22 86 2.33 REGISTER with a Escaped Header in a Illegal SIP URI of a 87 Contact.......................................................22 88 2.34 INVITE with Long Values in Headers.......................23 89 2.35 OPTIONS with multiple headers............................24 90 2.36 INVITE with large number of SDP attributes and telephone 91 subscriber Request-URI........................................25 92 2.37 REGISTER with a contact parameter........................26 93 2.38 REGISTER with a url parameter............................26 94 2.39 INVITE with an Unquoted Display Name Containing Multiple 95 Tokens........................................................26 96 2.40 INVITE with an Unquoted Display Name Containg Non-Token 97 Characters....................................................27 98 2.41 INVITE with Unknown (Higher) Protocol Version in Start Line27 99 SIP Torture Test Messages August 2002 101 2.42 INVITE with RFC2543 syntax...............................28 102 Security Considerations..........................................28 103 References.......................................................28 104 Acknowledgments..................................................29 105 Author's Addresses...............................................29 107 1. Overview 109 These SIP test messages are based on the current version 2.0 of SIP 110 in RFC 3261[2] with SDP usage described in RFC 3264[3]. 112 Note that this document is informational, and is NOT NORMATIVE on any 113 aspect of SIP syntax. 115 2. SIP Test Messages 117 The files in here are test messages for SIP servers to exercise 118 various functions. They have been used in SIPit 119 interoperability events. All messages shown here are valid, unless 120 otherwise noted. The correct behavior of servers and clients is also 121 described. 123 2.1 INVITE Parser Torture Test Message 125 This message is a correctly formatted SIP message. It contains: 127 line folding all over 128 escaped characters within quotes 129 LWS between colons, semicolons, headers, and other fields 130 both comma separated and separate listing of headers 131 mix or short and long form for the same header 132 unknown header field 133 unusual header ordering 134 unknown parameters of a known header 136 Proxies should forward message and clients should respond as to a 137 normal INVITE message. 139 Message Details 141 INVITE sip:vivekg@chair.dnrc.bell-labs.com SIP/2.0 142 TO : 143 sip:vivekg@chair.dnrc.bell-labs.com ; tag = 1918181833n 144 From : "J Rosenberg \\\"" 145 ; 146 tag = 98asjd8 147 Max-Forwards: 6 148 Call-ID: 0ha0isndaksdj@10.1.1.1 149 SIP Torture Test Messages August 2002 151 cseq: 8 152 INVITE 153 Via : SIP / 2.0 154 /UDP 155 135.180.130.133;branch=z9hG4bKkdjuw 156 Subject : 157 NewFangledHeader: newfangled value 158 more newfangled value 159 Content-Type: application/sdp 160 v: SIP / 2.0 / TCP 1192.168.156.222 ; 161 branch = 9ikj8 , 162 SIP / 2.0 / UDP 192.168.255.111 ; hidden 163 m:"Quoted string \"\"" ; newparam = 164 newvalue ; 165 secondparam = secondvalue ; q = 0.33, 166 tel:4443322 168 v=0 169 o=mhandley 29739 7272939 IN IP4 126.5.4.3 170 s=- 171 c=IN IP4 135.180.130.88 172 t=0 0 173 m=audio 492170 RTP/AVP 0 12 174 m=video 3227 RTP/AVP 31 175 a=rtpmap:31 LPC 177 2.2 INVITE with Proxy-Require and Require 179 This message tests support for Proxy-Require and Require. It is a 180 request that contains both headers, listing new features. 182 Proxies and clients should respond with a 420 Bad Extension, and an 183 Unsupported header listing these features. 185 Message Details 187 INVITE sip:user@company.com SIP/2.0 188 To: sip:j_user@company.com 189 From: sip:caller@university.edu;tag=242etr 190 Max-Forward: 6 191 Call-ID: 0ha0isndaksdj@10.1.1.1 192 Require: newfeature1, newfeature2 193 Proxy-Require: newfeature3, newfeature4 194 CSeq: 8 INVITE 195 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 196 SIP Torture Test Messages August 2002 198 2.3 INVITE with Unknown Schemes in URIs 200 This message contains unknown schemes in the Request URI, To, From 201 and Contact headers of a request. 203 A server should probably return a not found error; but other 204 behaviors are acceptable. 206 Message Details 208 INVITE name:John_Smith SIP/2.0 209 To: isbn:2983792873 210 From: ;tag=3234233 211 Call-ID: 0ha0isndaksdj@10.1.2.3 212 CSeq: 8 INVITE 213 Max-Forward: 7 214 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 215 Content-Type: application/sdp 217 v=0 218 o=mhandley 29739 7272939 IN IP4 126.5.4.3 219 s=- 220 c=IN IP4 135.180.130.88 221 t=0 0 222 m=audio 492170 RTP/AVP 0 12 223 m=video 3227 RTP/AVP 31 224 a=rtpmap:31 LPC 226 2.4 REGISTER with Y2038 Test 228 This message is a registration request with an expiration year of 229 2040. This makes sure that a server doesn't crash on seeing a date 230 past Y2038. 232 The correct behavior is probably to limit the lifetime to some 233 configured maximum. 235 Message Details 237 REGISTER sip:company.com SIP/2.0 238 To: sip:user@company.com 239 From: sip:user@company.com;tag=3411345 240 Max-Forwards: 8 241 Contact: sip:user@host.company.com 242 Call-ID: 0ha0isndaksdj@10.0.0.1 243 SIP Torture Test Messages August 2002 245 CSeq: 8 REGISTER 246 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 247 Expires: Sat, 01 Dec 2040 16:00:00 GMT 249 2.5 INVITE with inconsistent Accept and message body 251 This is a UAS test. It is a request that includes an Accept header 252 without SDP. The UAS should respond with an error. 254 Message Details 256 INVITE sip:user@company.com SIP/2.0 257 To: sip:j_user@company.com 258 From: sip:caller@university.edu;tag=234 259 Max-Forwards: 5 260 Call-ID: 0ha0isndaksdj@10.0.0.1 261 Accept: text/newformat 262 CSeq: 8 INVITE 263 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 264 Content-Type: application/sdp 266 v=0 267 c=IN IP4 135.180.130.88 268 m=audio 492170 RTP/AVP 0 12 269 m=video 3227 RTP/AVP 31 270 a=rtpmap:31 LPC 272 2.6 INVITE with non-SDP message body 274 This is a test of a user agent server. It is a request that includes 275 a body of a non-SDP type. 277 The user agent server should respond with an error. 279 Message Details 281 INVITE sip:user@comapny.com SIP/2.0 282 To: sip:j.user@company.com 283 From: sip:caller@university.edu;tag=8 284 Max-Forwards: 70 285 Call-ID: 0ha0isndaksdj@10.0.0.1 286 CSeq: 8 INVITE 287 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 288 Content-Type: application/newformat 289 SIP Torture Test Messages August 2002 291 295 2.7 Unknown Method Message 297 This request message contains a new unknown method, NEWMETHOD. 299 A proxy should forward this using the same retransmission rules as 300 BYE. A UAS should reject it with an error, and list the available 301 methods in the response. 303 Message Details 305 NEWMETHOD sip:user@comapny.com SIP/2.0 306 To: sip:j.user@company.com 307 From: sip:caller@university.edu;tag=34525 308 Max-Forwards: 6 309 Call-ID: 0ha0isndaksdj@10.0.0.1 310 CSeq: 8 NEWMETHOD 311 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 312 Content-Type: application/sdp 314 v=0 315 o=mhandley 29739 7272939 IN IP4 126.5.4.3 316 c=IN IP4 135.180.130.88 317 m=audio 492170 RTP/AVP 0 12 318 m=video 3227 RTP/AVP 31 319 a=rtpmap:31 LPC 321 2.8 Unknown Method with CSeq Error 323 This message is nearly identical to the Unknown Method message. It is 324 a request with a new unknown method, but with a CSeq method tag which 325 does not match. 327 A proxy should either respond with an error, or correct the method 328 tag. The user agent should reject it with an error, and list the 329 available methods in the response. 331 Message Details 332 SIP Torture Test Messages August 2002 334 NEWMETHOD sip:user@comapny.com SIP/2.0 335 To: sip:j.user@company.com 336 From: sip:caller@university.edu;tag=23411413 337 Max-Forwards: 3 338 Call-ID: 0ha0isndaksdj@10.0.1.1 339 CSeq: 8 INVITE 340 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 341 Content-Type: application/sdp 343 v=0 344 o=mhandley 29739 7272939 IN IP4 126.5.4.3 345 s=- 346 c=IN IP4 135.180.130.88 347 t=0 0 348 m=audio 492170 RTP/AVP 0 12 349 m=video 3227 RTP/AVP 31 350 a=rtpmap:31 LPC 352 2.9 REGISTER with Unknown Authorization Scheme 354 This message is a REGISTER request with an unknown authorization 355 scheme. 357 The server should do something reasonable, such as rejecting the 358 request. 360 Message Details 362 REGISTER sip:company.com SIP/2.0 363 To: sip:j.user@company.com 364 From: sip:j.user@company.com;tag=87321hj23128 365 Max-Forwards: 8 366 Call-ID: 0ha0isndaksdj@10.0.1.1 367 CSeq: 8 REGISTER 368 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 369 Authorization: Super-PGP ajsohdaosdh0asyhdaind08yasdknasd09asidhas0d8 371 2.10 Multiple SIP Request in a Single Message 373 This message contains two requests, separated by a bunch of 374 whitespace. Since the message exceeds the length indicated in the 375 Content-Length header, the message should be rejected. (Multiple SIP 376 requests per UDP packet are no longer allowed.) 377 SIP Torture Test Messages August 2002 379 Message Details 381 REGISTER sip:company.com SIP/2.0 382 To: sip:j.user@company.com 383 From: sip:j.user@company.com;tag=43251j3j324 384 Max-Forwards: 8 385 Call-ID: 0ha0isndaksdj@10.0.2.2 386 Contact: sip:j.user@host.company.com 387 CSeq: 8 REGISTER 388 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 389 Content-Length: 0 391 INVITE sip:joe@company.com SIP/2.0 392 To: sip:joe@company.com 393 From: sip:caller@university.edu;tag=141334 394 Max-Forwards: 8 395 Call-ID: 0ha0isnda977644900765@10.0.0.1 396 CSeq: 8 INVITE 397 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 398 Content-Type: application/sdp 400 v=0 401 o=mhandley 29739 7272939 IN IP4 126.5.4.3 402 s=- 403 c=IN IP4 135.180.130.88 404 t=0 0 405 m=audio 492170 RTP/AVP 0 12 406 m =video 3227 RTP/AVP 31 407 a=rtpmap:31 LPC 409 2.11 INVITE missing Required Headers 411 This message contains no Call-ID, From, or To header. 413 The server should not crash, and ideally should respond with an 414 error. 416 Message Details 418 INVITE sip:user@company.com SIP/2.0 419 CSeq: 0 INVITE 420 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 421 SIP Torture Test Messages August 2002 423 Content-Type: application/sdp 425 v=0 426 o=mhandley 29739 7272939 IN IP4 126.5.4.3 427 s=- 428 c=IN IP4 135.180.130.88 429 t=0 0 430 m=audio 492170 RTP/AVP 0 12 431 m=video 3227 RTP/AVP 31 432 a=rtpmap:31 LPC 434 2.12 INVITE with Duplicate Required Headers 436 The message contains a request with an extra Call-ID and To field. 438 The server should not crash, and should ideally respond with an 439 error. 441 Message Details 443 INVITE sip:user@company.com SIP/2.0 444 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 445 Max-Forwards: 70 446 CSeq: 0 INVITE 447 Call-ID: 98asdh@10.1.1.1 448 Call-ID: 98asdh@10.1.1.2 449 From: sip:caller@university.edu;tag=3413415 450 From: sip:caller@organization.org 451 To: sip:user@company.com 452 Content-Type: application/sdp 454 v=0 455 o=mhandley 29739 7272939 IN IP4 126.5.4.3 456 s=- 457 c=IN IP4 135.180.130.88 458 t=0 0 459 m=audio 492170 RTP/AVP 0 12 460 m=video 3227 RTP/AVP 31 461 a=rtpmap:31 LPC 463 2.13 INVITE with Illegal Expires Header 465 This message contains an Expires header which has illegal values for 466 a number of components, but otherwise is syntactically correct. 468 SIP Torture Test Messages August 2002 470 Message Details 472 INVITE sip:user@company.com SIP/2.0 473 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 474 Max-Forwards: 88 475 CSeq: 0 INVITE 476 Call-ID: 98asdh@10.1.1.2 477 Expires: Thu, 44 Dec 19999 16:00:00 EDT 478 From: sip:caller@university.edu;tag=3651 479 To: sip:user@company.com 480 Content-Type: application/sdp 482 v=0 483 o=mhandley 29739 7272939 IN IP4 126.5.4.3 484 s=- 485 c=IN IP4 135.180.130.88 486 t=0 0 487 m=audio 492170 RTP/AVP 0 12 488 m=video 3227 RTP/AVP 31 489 a=rtpmap:31 LPC 491 2.14 200 OK Response with Broadcast Via Header 493 This message is a response with a 2nd Via header of 255.255.255.255. 495 On receiving this response, the top Via header is stripped and the 496 packet forwarded. Since the next address is the broadcast address, 497 it causes the packet to be broadcast onto the network. A smart server 498 should ignore packets with 2nd Via headers that are 255.255.255.255 499 or 127.0.0.1. At the very least it should not crash. 501 Message Details 503 SIP/2.0 200 OK 504 Via: SIP/2.0/UDP 135.180.130.57;branch=0 505 Via: SIP/2.0/UDP 255.255.255.255;branch=0 506 Max-Forwards: 70 507 Call-ID: 0384840201@10.1.1.1 508 CSeq: 0 INVITE 509 From: sip:user@company.com;tag=11141343 510 To: sip:user@university.edu;tag=2229 511 Content-Type: application/sdp 513 v=0 514 SIP Torture Test Messages August 2002 516 o=mhandley 29739 7272939 IN IP4 126.5.4.3 517 s=- 518 c=IN IP4 224.2.17.12/127 519 t=0 0 520 m=audio 492170 RTP/AVP 0 12 521 m=video 3227 RTP/AVP 31 522 a=rtpmap:31 LPC 524 2.15 INVITE with Invalid Via and Contact Headers 526 This is a request with the Via and Contact headers incorrect. They 527 contain additional semicolons and commas without parameters or 528 values. 530 The server should respond with a Bad Request error. 532 Message Details 534 INVITE sip:user@company.com SIP/2.0 535 To: sip:j.user@company.com 536 From: sip:caller@university.edu;tag=134161461246 537 Max-Forwards: 7 538 Call-ID: 0ha0isndaksdj@10.0.0.1 539 CSeq: 8 INVITE 540 Via: SIP/2.0/UDP 135.180.130.133;;,; 541 Contact: "" <> ;,"Joe" ;;,,;; 542 Content-Type: application/sdp 544 v=0 545 o=mhandley 29739 7272939 IN IP4 126.5.4.3 546 s=- 547 c=IN IP4 135.180.130.88 548 t=0 0 549 m=audio 492170 RTP/AVP 0 12 550 m=video 3227 RTP/AVP 31 551 a=rtpmap:31 LPC 553 2.16 INVITE with Incorrect Content-Length Header 555 This is a request message with a Content Length that is much larger 556 than the length of the body. 558 When sent UDP, the server should respond with an error. With TCP, 559 there's not much you can do but wait... 561 SIP Torture Test Messages August 2002 563 Message Details 565 INVITE sip:user@company.com SIP/2.0 566 Max-Forwards: 80 567 To: sip:j.user@company.com 568 From: sip:caller@university.edu;tag=93942939o2 569 Call-ID: 0ha0isndaksdj@10.0.0.1 570 CSeq: 8 INVITE 571 Via: SIP/2.0/UDP 135.180.130.133 572 Content-Type: application/sdp 573 Content-Length: 9999 575 v=0 576 o=mhandley 29739 7272939 IN IP4 126.5.4.3 577 s=- 578 c=IN IP4 135.180.130.88 579 t=0 0 580 m=audio 492170 RTP/AVP 0 12 581 m=video 3227 RTP/AVP 31 582 a=rtpmap:31 LPC 584 2.17 INVITE with Invalid Value for Content-Length 586 This is a request message with a negative value for Content-Length. 588 The server should respond with an error. 590 Message Details 592 INVITE sip:user@company.com SIP/2.0 593 Max-Forwards: 254 594 To: sip:j.user@company.com 595 From: sip:caller@university.edu;tag=3 596 Call-ID: 0ha0isndaksdj@10.0.0.1 597 CSeq: 8 INVITE 598 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 599 Content-Type: application/sdp 600 Content-Length: -999 602 v=0 603 o=mhandley 29739 7272939 IN IP4 126.5.4.3 604 s=- 605 c=IN IP4 135.180.130.88 606 t=0 0 607 SIP Torture Test Messages August 2002 609 m=audio 492170 RTP/AVP 0 12 610 m=video 3227 RTP/AVP 31 611 a=rtpmap:31 LPC 613 2.18 INVITE with Garbage after Message Body 615 This is a request message with garbage after the end of the SDP 616 included in the body. 618 The servers should reject the request as the body is longer than the 619 Content-Length. 621 Message Details 623 INVITE sip:user@company.com SIP/2.0 624 To: sip:j.user@company.com 625 From: sip:caller@university.edu;tag=3223 626 Max-Forwards: 7 627 Call-ID: 0ha0isndaksdj@10.0.0.1 628 CSeq: 8 INVITE 629 Via: SIP/2.0/UDP 135.180.130.133 630 Content-Type: application/sdp 631 Content-Length: 138 633 v=0 634 o=mhandley 29739 7272939 IN IP4 126.5.4.3 635 s=- 636 c=IN IP4 135.180.130.88 637 t=0 0 638 m=audio 492170 RTP/AVP 0 12 639 m=video 3227 RTP/AVP 31 640 a=rtpmap:31 LPC 641 asdpasd08asdsdk:;;asd 642 a0sdjhg8a0''...'';;;; 644 2.19 INVITE with Error in Display Name in To Header 646 This is a request with an unterminated quote in the display name of 647 the To field. 649 The server can either return an error, or proxy it if it is 650 successful parsing without the terminating quote. 652 SIP Torture Test Messages August 2002 654 Message Details 656 INVITE sip:user@company.com SIP/2.0 657 To: "Mr. J. User 658 From: sip:caller@university.edu;tag=93334 659 Max-Forwards: 10 660 Call-ID: 0ha0isndaksdj@10.0.0.1 661 CSeq: 8 INVITE 662 Via: SIP/2.0/UDP 135.180.130.133:5050;branch=z9hG4bKkdjuw 663 Content-Type: application/sdp 664 Content-Length: 138 666 v=0 667 o=mhandley 29739 7272939 IN IP4 126.5.4.3 668 s=- 669 c=IN IP4 135.180.130.88 670 t=0 0 671 m=audio 492170 RTP/AVP 0 12 672 m=video 3227 RTP/AVP 31 673 a=rtpmap:31 LPC 675 2.20 INVITE with a Semicolon-Separated Parameter in the "user" Part 677 This is an INVITE request with a semicolon-separated parameter in 678 the "user" part. 680 Outbound proxies should direct it appropriately. 682 Message Details 684 INVITE sip:user;par=u%40h.com@company.com SIP/2.0 685 To: sip:j_user@company.com 686 From: sip:caller@university.edu;tag=33242 687 Max-Forwards: 3 688 Call-ID: 0ha0isndaksdj@10.1.1.1 689 CSeq: 8 INVITE 690 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 692 2.21 INVITE with Illegal Enclosing of Request-URI in "<>" 694 This INVITE is illegal because the Request-URI has been enclosed 695 within in "<>". 697 SIP Torture Test Messages August 2002 699 An intelligent server may be able to deal with this and fix up 700 athe Request-URI if acting as a Proxy. If not it should respond 400 701 with an appropriate reason phrase. 703 Message Details 705 INVITE SIP/2.0 706 To: sip:user@company.com 707 From: sip:caller@university.edu;tag=39291 708 Max-Forwards: 23 709 Call-ID: 1@10.0.0.1 710 CSeq: 1 INVITE 711 Via: SIP/2.0/UDP 135.180.130.133 712 Content-Type: application/sdp 713 Content-Length: 174 715 v=0 716 o=mhandley 29739 7272939 IN IP4 126.5.4.3 717 s=- 718 c=IN IP4 135.180.130.88 719 t=3149328700 0 720 m=audio 492170 RTP/AVP 0 12 721 m=video 3227 RTP/AVP 31 722 a=rtpmap:31 LPC 724 2.22 INVITE with Illegal LWS within Elements of Request-URI 726 This INVITE has illegal LWS within the SIP URI. 728 An intelligent server may be able to deal with this and fix up 729 the Request-URI if acting as a Proxy. If not it should respond 400 730 with an appropriate reason phrase. 732 Message Details 734 INVITE sip:user@company.com; transport=udp SIP/2.0 735 To: sip:user@company.com 736 From: sip:caller@university.edu;tag=231413434 737 Max-Forwards: 5 738 Call-ID: 2@10.0.0.1 739 CSeq: 1 INVITE 740 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 741 Content-Type: application/sdp 742 Content-Length: 174 743 SIP Torture Test Messages August 2002 745 v=0 746 o=mhandley 29739 7272939 IN IP4 126.5.4.3 747 s=- 748 c=IN IP4 135.180.130.88 749 t=3149328700 0 750 m=audio 492170 RTP/AVP 0 12 751 m=video 3227 RTP/AVP 31 752 a=rtpmap:31 LPC 754 2.23 INVITE with illegal >1 SP between elements of Request URI 756 This INVITE has illegal >1 SP between elements of the Request-URI. 758 An intelligent server may be able to deal with this and fix up 759 the Request-URI if acting as a Proxy. If not it should respond 400 760 with an appropriate reason phrase. 762 Message Details 764 INVITE sip:user@company.com SIP/2.0 765 Max-Forwards: 8 766 To: sip:user@company.com 767 From: sip:caller@university.edu;tag=8814 768 Call-ID: 3@10.0.0.1 769 CSeq: 1 INVITE 770 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 771 Content-Type: application/sdp 772 Content-Length: 174 774 v=0 775 o=mhandley 29739 7272939 IN IP4 126.5.4.3 776 s=- 777 c=IN IP4 135.180.130.88 778 t=0 0 779 m=audio 492170 RTP/AVP 0 12 780 m=video 3227 RTP/AVP 31 781 a=rtpmap:31 LPC 783 2.24 INVITE with a legal SIP URI containing escaped characters 785 This INVITE is legal and has a Request-URI with a SIP URI containing 786 escaped characters. 788 SIP Torture Test Messages August 2002 790 Message Details 792 INVITE sip:sip%3Auser%40example.com@company.com;other-param=summit 793 SIP/2.0 794 To: sip:user@company.com 795 From: sip:caller@university.edu;tag=938 796 Max-Forwards: 87 797 Call-ID: 4@10.0.0.1 798 CSeq: 1 INVITE 799 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 800 Content-Type: application/sdp 801 Content-Length: 174 803 v=0 804 o=mhandley 29739 7272939 IN IP4 126.5.4.3 805 s=- 806 c=IN IP4 135.180.130.88 807 t=0 0 808 m=audio 492170 RTP/AVP 0 12 809 m=video 3227 RTP/AVP 31 810 a=rtpmap:31 LPC 812 2.25 INVITE with the illegal use of escaped headers in Request-URI 814 This INVITE is illegal as it the Request-URI contains a SIP URI 815 containing 816 escaped headers. 818 An intelligent server may be liberal enough to accept this. A server 819 acting as a proxy should remove the escaped header before processing. 821 Message Details 823 INVITE sip:user@company.com?Route=%3Csip:sip.example.com%3E SIP/2.0 824 To: sip:user@company.com 825 From: sip:caller@university.edu;tag=341518 826 Max-Forwards: 7 827 Call-ID: 5@10.0.0.1 828 CSeq: 1 INVITE 829 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 830 Content-Type: application/sdp 831 Content-Length: 174 833 v=0 834 o=mhandley 29739 7272939 IN IP4 126.5.4.3 835 s=- 836 SIP Torture Test Messages August 2002 838 c=IN IP4 135.180.130.88 839 t=0 0 840 m=audio 492170 RTP/AVP 0 12 841 m=video 3227 RTP/AVP 31 842 a=rtpmap:31 LPC 844 2.26 INVITE containing an unknown scheme in the Request URI 846 This INVITE contains an unknown URI scheme in the Request-URI. 848 A server should reject this message with a 400 response plus an 849 appropriate reason phrase despite being able to understand the 850 To header as a SIP URI. 852 Message Details 854 INVITE name:user SIP/2.0 855 To: sip:user@company.com 856 From: sip:caller@university.edu;tag=384 857 Max-Forwards: 3 858 Call-ID: 6@10.0.0.1 859 CSeq: 1 INVITE 860 Via: SIP/2.0/UDP 135.180.130.133;branch=z9hG4bKkdjuw 861 Content-Type: application/sdp 862 Content-Length: 174 864 v=0 865 o=mhandley 29739 7272939 IN IP4 126.5.4.3 866 s=- 867 c=IN IP4 135.180.130.88 868 t=0 0 869 m=audio 492170 RTP/AVP 0 12 870 m=video 3227 RTP/AVP 31 871 a=rtpmap:31 LPC 873 2.27 OPTIONS with no LWS between display name and < 875 This OPTIONS request is legal despite there being no LWS between 876 the display name and < in the From header. 878 Message Details 880 OPTIONS sip:user@company.com SIP/2.0 881 SIP Torture Test Messages August 2002 883 To: sip:user@company.com 884 From: "caller";tag=323 885 Max-Forwards: 70 886 Call-ID: 1234abcd@10.0.0.1 887 CSeq: 1 OPTIONS 888 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 890 2.28 OPTIONS with extran LWS between display name and < 892 This OPTIONS request is legal despite there being extra LWS between 893 the display name and < in the From header. 895 Message Details 897 OPTIONS sip:user@company.com SIP/2.0 898 To: sip:user@company.com 899 From: "caller" ;tag=32 900 Max-Forwards: 70 901 Call-ID: 1234abcd@10.0.0.1 902 CSeq: 2 OPTIONS 903 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 905 2.29 INVITE with an illegal SIP Date format. 907 This INVITE is illegal as it contains a non GMT time zone in the SIP 908 Date header. 910 An intelligent server may be able to fix this up and correct the time 911 to GMT. Alternatively this message may illicit a 400 response with an 912 appropriate reason phrase. 914 Message Details 916 INVITE sip:user@company.com SIP/2.0 917 To: sip:user@company.com 918 From: sip:caller@university.edu;tag=2 919 Max-Forwards: 70 920 Call-ID: 7@10.0.0.1 921 CSeq: 1 INVITE 922 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 923 Date: Fri, 01 Jan 2010 16:00:00 EST 924 Content-Type: application/sdp 925 Content-Length: 174 926 SIP Torture Test Messages August 2002 928 v=0 929 o=mhandley 29739 7272939 IN IP4 126.5.4.3 930 s=- 931 c=IN IP4 135.180.130.88 932 t=0 0 933 m=audio 492170 RTP/AVP 0 12 934 m=video 3227 RTP/AVP 31 935 a=rtpmap:31 LPC 937 2.30 INVITE with Passed Expries Time 939 This is a legal INVITE but the message content has long since 940 expired. 942 A server should respond 408 (Timeout). 944 Message Details 946 INVITE sip:user@company.com SIP/2.0 947 To: sip:user@company.com 948 From: sip:caller@university.edu;tag=3843 949 Max-Forwards: 70 950 Call-ID: 8@10.0.0.1 951 CSeq: 1 INVITE 952 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 953 Expires: Thu, 01 Dec 1994 16:00:00 GMT 954 Content-Type: application/sdp 955 Content-Length: 174 957 v=0 958 o=mhandley 29739 7272939 IN IP4 126.5.4.3 959 s=- 960 c=IN IP4 135.180.130.88 961 t=0 0 962 m=audio 492170 RTP/AVP 0 12 963 m=video 3227 RTP/AVP 31 964 a=rtpmap:31 LPC 966 2.31 INVITE with Max-Forwards Set to Zero 968 This is a legal SIP request with the Max-Forwards header set to zero. 970 A proxy or gateway should not forward the request and respond 483 971 (Too Many Hops). 973 SIP Torture Test Messages August 2002 975 Message Details 977 INVITE sip:user@company.com SIP/2.0 978 To: sip:user@company.com 979 From: sip:caller@university.edu;tag=3ghsd41 980 Call-ID: 9@10.0.0.1 981 CSeq: 1 INVITE 982 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 983 Max-Forwards: 0 984 Content-Type: application/sdp 985 Content-Length: 174 987 v=0 988 o=mhandley 29739 7272939 IN IP4 126.5.4.3 989 s=- 990 c=IN IP4 135.180.130.88 991 t=0 0 992 m=audio 492170 RTP/AVP 0 12 993 m=video 3227 RTP/AVP 31 994 a=rtpmap:31 LPC 996 2.32 REGISTER with a Escaped Header in a Legal SIP URI of a Contact 998 This is a legal REGISTER message where the Contact header contains a 999 SIP URI with an escaped header within it. 1001 Message Details 1003 REGISTER sip:company.com SIP/2.0 1004 To: sip:user@company.com 1005 From: sip:user@company.com;tag=8 1006 Max-Forwards: 70 1007 Contact: sip:user@host.company.com 1008 Call-ID: k345asrl3fdbv@10.0.0.1 1009 CSeq: 1 REGISTER 1010 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 1011 Contact: 1013 2.33 REGISTER with a Escaped Header in a Illegal SIP URI of a Contact 1015 This is an illegal message as the REGISTER request contains a SIP 1016 SIP Torture Test Messages August 2002 1018 URI with an escaped header but it is not enclosed in <> 1020 A server should respond 400 with an appropriate reason phrase. 1022 Message Details 1024 REGISTER sip:company.com SIP/2.0 1025 To: sip:user@company.com 1026 From: sip:user@company.com;tag=998332 1027 Max-Forwards: 70 1028 Contact: sip:user@host.company.com 1029 Call-ID: k345asrl3fdbv@10.0.0.1 1030 CSeq: 1 REGISTER 1031 Via: SIP/2.0/UDP 135.180.130.133:5060;branch=z9hG4bKkdjuw 1032 Contact: sip:user@example.com?Route=%3Csip:sip.example.com%3E 1034 2.34 INVITE with Long Values in Headers 1036 This is a legal message that contains long values in many headers. 1038 Message Details 1040 INVITE sip:user@company.com SIP/2.0 1041 To: "I have a user name of extreme proportion" 1042 1044 From: sip:caller@university.edu;tag=12481841982424 1045 Call-ID: 1046 kl24ahsd546folnyt2vbak9sad98u23naodiunzds09a3bqw0sdfbsk34poouymnae004 1047 3nsed09mfkvc74bd0cuwnms05dknw87hjpobd76f 1048 CSeq: 1 INVITE 1049 P-My-State: sldkjflzdsfaret0803adgaasd0afds0asdaasd 1050 Via: SIP/2.0/TCP sip33.example.com 1051 Via: SIP/2.0/TCP sip32.example.com 1052 Via: SIP/2.0/TCP sip31.example.com 1053 Via: SIP/2.0/TCP sip30.example.com 1054 Via: SIP/2.0/TCP sip29.example.com 1055 Via: SIP/2.0/TCP sip28.example.com 1056 Via: SIP/2.0/TCP sip27.example.com 1057 Via: SIP/2.0/TCP sip26.example.com 1058 Via: SIP/2.0/TCP sip25.example.com 1059 Via: SIP/2.0/TCP sip24.example.com 1060 Via: SIP/2.0/TCP sip23.example.com 1061 Via: SIP/2.0/TCP sip22.example.com 1062 Via: SIP/2.0/TCP sip21.example.com 1063 SIP Torture Test Messages August 2002 1065 Via: SIP/2.0/TCP sip20.example.com 1066 Via: SIP/2.0/TCP sip19.example.com 1067 Via: SIP/2.0/TCP sip18.example.com 1068 Via: SIP/2.0/TCP sip17.example.com 1069 Via: SIP/2.0/TCP sip16.example.com 1070 Via: SIP/2.0/TCP sip15.example.com 1071 Via: SIP/2.0/TCP sip14.example.com 1072 Via: SIP/2.0/TCP sip13.example.com 1073 Via: SIP/2.0/TCP sip12.example.com 1074 Via: SIP/2.0/TCP sip11.example.com 1075 Via: SIP/2.0/TCP sip10.example.com 1076 Via: SIP/2.0/TCP sip9.example.com 1077 Via: SIP/2.0/TCP sip8.example.com 1078 Via: SIP/2.0/TCP sip7.example.com 1079 Via: SIP/2.0/TCP sip6.example.com 1080 Via: SIP/2.0/TCP sip5.example.com 1081 Via: SIP/2.0/TCP sip4.example.com 1082 Via: SIP/2.0/TCP sip3.example.com 1083 Via: SIP/2.0/TCP sip2.example.com 1084 Via: SIP/2.0/TCP sip1.example.com 1085 Via: SIP/2.0/TCP 1086 host.example.com;received=135.180.130.133;branch=C1C3344E2710000000E2 1087 99E568E7potato10potato0potato0 1088 Content-Type: application/sdp 1090 v=0 1091 o=mhandley 29739 7272939 IN IP4 126.5.4.3 1092 s=- 1093 c=IN IP4 135.180.130.88 1094 t=0 0 1095 m=audio 492170 RTP/AVP 0 12 1096 m=video 3227 RTP/AVP 31 1097 a=rtpmap:31 LPC 1099 2.35 OPTIONS with multiple headers. 1101 This is an illegal and badly mangled message. 1103 A server should respond 400 with an appropriate reason phrase if it 1104 can. It may just drop this message. 1106 Message Details 1108 OPTIONS sip:135.180.130.133 SIP/2.0 1109 Via: SIP/2.0/UDP company.com:5604 1110 Max-Forwards: 70 1111 SIP Torture Test Messages August 2002 1113 From: sip:iuser@company.com;tag=74345345 1114 To: sip:user@135.180.130.133 1115 Call-ID: 1804928587@company.com 1116 CSeq: 1 OPTIONS 1117 Expires: 0 0l@company.com 1118 To: sip:user@135.180.130.133 1119 Call-ID: 1804928587@company.com 1120 CSeq: 1 OPTIONS 1121 Contact: sip:host.company.com 1122 Expires: 0xpires: 0sip:host.company.com 1123 Expires: 0 1124 Contact: sip:host.company.com 1126 2.36 INVITE with large number of SDP attributes and telephone subscriber 1127 Request-URI 1129 This is a legal message with a large number of SDP attributes and a 1130 long telephone subscriber Request-URI 1132 Message Details 1134 INVITE sip:+19725552222;phone- 1135 context=name%40domain;new=user?%22Route%3a%20X%40Y%3bZ=W%22@gw1.atlan 1136 ta.com;user=phone SIP/2.0 1137 Via: SIP/2.0/UDP iftgw.biloxi.com:5060;branch=z9hG4bKjeefr3 1138 Max-Forwards: 70 1139 From: 1140 ;tag=332lflke 1141 To: sip:+16555552222@ss1.atlanta.com;user=phone 1142 Call-ID: 1717@ift.client.atlanta.com 1143 CSeq: 56 INVITE 1144 Content-Type: application/sdp 1145 Content-Length: 320 1147 v=0 1148 o=faxgw1 2890844527 2890844527 IN IP4 iftgw.biloxi.com 1149 s=- 1150 c=IN IP4 iftmg.biloxi.com 1151 t=0 0 1152 m=image 49172 udptl t38 1153 a=T38FaxVersion:0 1154 a=T38maxBitRate:14400 1155 a=T38FaxFillBitRemoval:0 1156 a=T38FaxTranscodingMMR:0 1157 a=T38FaxTranscodingJBIG:0 1158 a=T38FaxRateManagement:transferredTCF 1159 SIP Torture Test Messages August 2002 1161 a=T38FaxMaxBuffer:260 1162 a=T38FaxUdpEC:t38UDPR 1164 2.37 REGISTER with a contact parameter. 1166 This REGISTER contains a contact where the 'user' parameter should be 1167 interpreted as being a contact-param and not a url-param. 1169 The register should succeed but a subsequent retrieval of the 1170 registration must not include "user=phone" as a url-parameter. 1172 Message Details 1174 REGISTER sip:bell-tel.com SIP/2.0 1175 Via: SIP/2.0/UDP saturn.bell-tel.com:5060;branch=z9hG4bKkdjuw 1176 Max-Forwards: 70 1177 From: sip:watson@bell-tel.com;tag=DkfVgjkrtMwaerKKpe 1178 To: sip:watson@bell-tel.com 1179 Call-ID: 70710@saturn.bell-tel.com 1180 CSeq: 2 REGISTER 1181 Contact: sip:+19725552222@gw1.atlanta.com;user=phone 1183 2.38 REGISTER with a url parameter. 1185 This register contains a contact where the 'user'parameter is a url- 1186 param. 1188 The register should succeed and a subsequent retrieval of the 1189 registration must 1190 include "user=phone" as a url-parameter. 1192 Message Details 1194 REGISTER sip:bell-tel.com SIP/2.0 1195 Via: SIP/2.0/UDP saturn.bell-tel.com:5060;branch=z9hG4bKkdjuw 1196 Max-Forwards: 70 1197 From: sip:watson@bell-tel.com;tag=838293 1198 To: sip:watson@bell-tel.com 1199 Call-ID: 70710@saturn.bell-tel.com 1200 CSeq: 3 REGISTER 1201 Contact: 1203 2.39 INVITE with an Unquoted Display Name Containing Multiple Tokens 1204 SIP Torture Test Messages August 2002 1206 This is a legal INVITE where the To and From header contain display 1207 names that contain multiple tokens but are unquoted. 1209 Message Details 1211 INVITE sip:t.watson@ieee.org SIP/2.0 1212 Via: SIP/2.0/UDP c.bell-tel.com:5060;branch=z9hG4bKkdjuw 1213 Max-Forwards: 70 1214 From: A. Bell ;tag=459843 1215 To: T. Watson 1216 Call-ID: 31414@c.bell-tel.com 1217 CSeq: 1 INVITE 1219 2.40 INVITE with an Unquoted Display Name Containg Non-Token Characters 1221 This is an illegal invite at the display names in the To and From 1222 headers contain non-token characters but are unquoted. 1224 A server may be intelligent enough to cope with this but may also 1225 return a 400 response with an appropriate reason phrase. 1227 Message Details 1229 INVITE sip:t.watson@ieee.org SIP/2.0 1230 Via: SIP/2.0/UDP c.bell-tel.com:5060;branch=z9hG4bKkdjuw 1231 Max-Forwards: 70 1232 From: Bell, Alexander ;tag=43 1233 To: Watson, Thomas 1234 Call-ID: 31415@c.bell-tel.com 1235 CSeq: 1 INVITE 1237 2.41 INVITE with Unknown (Higher) Protocol Version in Start Line 1239 This is an illegal INVITE as the SIP Protocol version is unknown. 1241 The server should respond to the request with a bad version error. 1243 Message Details 1245 INVITE sip:t.watson@ieee.org SIP/7.0 1246 Via: SIP/2.0/UDP c.bell-tel.com;branch=z9hG4bKkdjuw 1247 Max-Forwards: 70 1248 SIP Torture Test Messages August 2002 1250 From: A. Bell ;tag=qweoiqpe 1251 To: T. Watson 1252 Call-ID: 31417@c.bell-tel.com 1253 CSeq: 1 INVITE 1255 2.42 INVITE with RFC2543 syntax 1257 This is a legal message per RFC 2543 which should be accepted by RFC 1258 3261 elements which want to maintain backwards compatibility. 1260 Message Details 1262 INVITE sip:UserB@biloxi.com SIP/2.0 1263 Via: SIP/2.0/UDP iftgw.biloxi.com 1264 From: ;tag=93752 1265 Record-Route: 1266 To: sip:+16505552222@ss1.atlanta.com;user=phone 1267 Call-ID: 1717@ift.client.atlanta.com 1268 CSeq: 56 INVITE 1270 Security Considerations 1272 Since this document represents NON NORMATIVE examples of SIP session 1273 establishment, the security considerations in RFC 3261 [2] apply. 1275 References 1277 1 Bradner, S., "Key words for use in RFCs to Indicate Requirement 1278 Levels", BCP 14, RFC 2119, March 1997 1280 2 J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, 1281 J. Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: 1282 Session Initiation Protocol", RFC 3261, June 2002. 1284 3 J.Rosenberg and H.Schulzrinne, "An Offer/Answer Model 1285 with SDP", Internet Engineering Task Force, RFC 3264, April 2002. 1287 SIP Torture Test Messages August 2002 1289 Acknowledgments 1291 Thanks to Rohan Mahy, Adam Roach, Gonzalo Camarillo, Cullen Jennings, 1292 and Tom Taylor for their detailed comments during the final final 1293 review. Thanks to Vijay Gurbani for his comments. 1295 The authors wish to thank Neil Deason for his additions to the 1296 Torture Test messages and Kundan Singh for performing parser 1297 validation of messages. 1299 The authors wish to thank the following individuals for their 1300 participation in the final review of this call flows document: Aseem 1301 Agarwal, Rafi Assadi, Ben Campbell, Sunitha Kumar, Jon Peterson, Marc 1302 Petit-Huguenin, Vidhi Rastogi, and Bodgey Yin Shaohua. 1304 The authors also wish to thank the following individuals for their 1305 assistance: Jean-Francois Mule, Hemant Agrawal, Henry Sinnreich, 1306 David Devanatham, Joe Pizzimenti, Matt Cannon, John Hearty, the whole 1307 MCI WorldCom IPOP Design team, Scott Orton, Greg Osterhout, Pat 1308 Sollee, Doug Weisenberg, Danny Mistry, Steve McKinnon, and Denise 1309 Ingram, Denise Caballero, Tom Redman, Ilya Slain, Pat Sollee, John 1310 Truetken, and others from MCI WorldCom, 3Com, Cisco, Lucent and 1311 Nortel. 1313 Author's Addresses 1315 Alan Johnston 1316 WorldCom 1317 100 South 4th Street 1318 St. Louis, MO 63102 1319 USA 1321 EMail: alan.johnston@wcom.com 1323 Jonathan Rosenberg 1324 dynamicsoft 1325 72 Eagle Rock Ave 1326 East Hanover, NJ 07936 1327 USA 1329 EMail: jdrosen@dynamicsoft.com 1331 Henning Schulzrinne 1332 Dept. of Computer Science 1333 Columbia University 1334 1214 Amsterdam Avenue 1335 New York, NY 10027 1336 USA 1337 SIP Torture Test Messages August 2002 1339 EMail: schulzrinne@cs.columbia.edu 1341 Copyright Notice 1343 "Copyright (C) The Internet Society 2002. All Rights Reserved. 1345 This document and translations of it may be copied and furnished to 1346 others, and derivative works that comment on or otherwise explain it 1347 or assist in its implementation may be prepared, copied, published 1348 and distributed, in whole or in part, without restriction of any 1349 kind, provided that the above copyright notice and this paragraph are 1350 included on all such copies and derivative works. However, this 1351 document itself may not be modified in any way, such as by removing 1352 the copyright notice or references to the Internet Society or other 1353 Internet organizations, except as needed for the purpose of 1354 developing Internet standards in which case the procedures for 1355 copyrights defined in the Internet Standards process must be 1356 followed, or as required to translate it into languages other than 1357 English. 1359 The limited permissions granted above are perpetual and will not be 1360 revoked by the Internet Society or its successors or assigns. 1362 This document and the information contained herein is provided on an 1363 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1364 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1365 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1366 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1367 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1369 Acknowledgement 1371 Funding for the RFC Editor function is currently provided by the 1372 Internet Society.