RFC 5118: Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)
In plain English — editorial summary, not part of the RFC
This document provides examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" the code of an IPv6-enabled SIP implementation. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5118
- Published
- February 2008
- Authors
- V. Gurbani; C. Boulton; R. Sparks
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 5390Requirements for Management of Overload in the Session Initiation ProtocolCurrent
December 2008
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 4826Extensible Markup Language (XML) Formats for Representing Resource ListsCurrent
May 2007
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 4769IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling InformationUpdated
November 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?