Session Initiation Protocol (SIP) Torture Test Messages
RFC 4475
Document | Type | RFC - Informational (May 2006; No errata) | |
---|---|---|---|
Authors | Henning Schulzrinne , Jonathan Rosenberg , Alan Hawrylyshen , Alan Johnston , Robert Sparks | ||
Last updated | 2015-10-14 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4475 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Jon Peterson | ||
Send notices to | rohan@ekabal.com, rsparks@nostrum.com, dean.willis@softarmor.com |
Network Working Group R. Sparks, Ed. Request for Comments: 4475 Estacado Systems Category: Informational A. Hawrylyshen Ditech Networks A. Johnston Avaya J. Rosenberg Cisco Systems H. Schulzrinne Columbia University May 2006 Session Initiation Protocol (SIP) Torture Test Messages Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This informational document gives examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" a SIP implementation. Table of Contents 1. Overview ........................................................3 2. Document Conventions ............................................3 2.1. Representing Long Lines ....................................4 2.2. Representing Non-printable Characters ......................4 2.3. Representing Long Repeating Strings ........................5 3. SIP Test Messages ...............................................5 3.1. Parser Tests (syntax) ......................................5 3.1.1. Valid Messages ......................................5 3.1.1.1. A Short Tortuous INVITE ....................5 3.1.1.2. Wide Range of Valid Characters .............8 3.1.1.3. Valid Use of the % Escaping Mechanism ......9 3.1.1.4. Escaped Nulls in URIs .....................11 3.1.1.5. Use of % When It Is Not an Escape .........11 3.1.1.6. Message with No LWS between Display Name and < ........................12 Sparks, et al. Informational [Page 1] RFC 4475 SIP Torture Test Messages May 2006 3.1.1.7. Long Values in Header Fields ..............12 3.1.1.8. Extra Trailing Octets in a UDP Datagram ...14 3.1.1.9. Semicolon-Separated Parameters in URI User Part .............................16 3.1.1.10. Varied and Unknown Transport Types .......16 3.1.1.11. Multipart MIME Message ...................17 3.1.1.12. Unusual Reason Phrase ....................18 3.1.1.13. Empty Reason Phrase ......................19 3.1.2. Invalid Messages ...................................20 3.1.2.1. Extraneous Header Field Separators ........20 3.1.2.2. Content Length Larger Than Message ........20 3.1.2.3. Negative Content-Length ...................21 3.1.2.4. Request Scalar Fields with Overlarge Values ..........................22 3.1.2.5. Response Scalar Fields with Overlarge Values ..........................23 3.1.2.6. Unterminated Quoted String in Display Name ..............................24 3.1.2.7. <> Enclosing Request-URI ..................25 3.1.2.8. Malformed SIP Request-URI (embedded LWS) ..26 3.1.2.9. Multiple SP Separating Request-Line Elements .....................27 3.1.2.10. SP Characters at End of Request-Line .....28 3.1.2.11. Escaped Headers in SIP Request-URI .......29 3.1.2.12. Invalid Timezone in Date Header Field ....30 3.1.2.13. Failure to Enclose name-addr URI in <> ...31 3.1.2.14. Spaces within addr-spec ..................31 3.1.2.15. Non-token Characters in Display Name .....32 3.1.2.16. Unknown Protocol Version .................32 3.1.2.17. Start Line and CSeq Method Mismatch ......33 3.1.2.18. Unknown Method with CSeq Method Mismatch .33 3.1.2.19. Overlarge Response Code ..................34 3.2. Transaction Layer Semantics ...............................34 3.2.1. Missing Transaction Identifier .....................34 3.3. Application-Layer Semantics ...............................35Show full document text