Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and Registration (RFC7501)
Original Publication Date: 2015-Apr-01
Included in the Prior Art Database: 2015-Apr-14
Internet Society Requests For Comment (RFCs)
C. Davids: AUTHOR [+2]
Service Providers and IT organizations deliver Voice Over IP (VoIP) and multimedia network services based on the IETF Session Initiation Protocol (SIP) [RFC3261]. SIP is a signaling protocol originally intended to be used to dynamically establish, disconnect, and modify streams of media between end users. As it has evolved, it has been adopted for use in a growing number of services and applications. Many of these result in the creation of a media session, but some do not. Examples of this latter group include text messaging and subscription services. The set of benchmarking terms provided in this document is intended for use with any SIP-enabled device
Internet Engineering Task Force (IETF) C. Davids Request for Comments: 7501 Illinois Institute of Technology Category: Informational V. Gurbani ISSN: 2070-1721 Bell Laboratories, Alcatel-Lucent S. Poretsky Allot Communications April 2015
Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and Registration
This document provides a terminology for benchmarking the Session
Initiation Protocol (SIP) performance of devices. Methodology
related to benchmarking SIP devices is described in the companion
methodology document (RFC 7502). Using these two documents,
benchmarks can be obtained and compared for different types of
devices such as SIP Proxy Servers, Registrars, and Session Border
Controllers. The term "performance" in this context means the
capacity of the Device Under Test (DUT) to process SIP messages.
Media streams are used only to study how they impact the signaling
behavior. The intent of the two documents is to provide a normalized
set of tests that will enable an objective comparison of the capacity
of SIP devices. Test setup parameters and a methodology are
necessary because SIP allows a wide range of configurations and
operational conditions that can influence performance benchmark
measurements. A standard terminology and methodology will ensure
that benchmarks have consistent definitions and were obtained
following the same procedures.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7501.
Davids, et al. Informational [Page 1]
RFC 7501 SIP Benchmarking Terminology ...