RFC 4475: Session Initiation Protocol (SIP) Torture Test Messages
In plain English — editorial summary, not part of the RFC
This informational document gives examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" a SIP implementation. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4475
- Published
- May 2006
- Authors
- R. Sparks; A. Hawrylyshen; A. Johnston; J. Rosenberg; H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 53
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4474Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)Obsoleted
August 2006
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 4480RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)Current
July 2006
- RFC 4481Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time IntervalsCurrent
July 2006
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 4483A Mechanism for Content Indirection in Session Initiation Protocol (SIP) MessagesCurrent
May 2006
- RFC 4484Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)Current
August 2006
- RFC 4485Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)Current
May 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?