RFC 7501: Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and Registration
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7501
- Published
- April 2015
- Authors
- C. Davids; V. Gurbani; S. Poretsky
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7502Methodology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and RegistrationCurrent
April 2015
- RFC 7497Rate Measurement Test Protocol Problem Statement and RequirementsCurrent
April 2015
- RFC 7494IEEE 802.11 Medium Access Control (MAC) Profile for Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2015
- RFC 7477Child-to-Parent Synchronization in DNSUpdated
March 2015
- RFC 7526Deprecating the Anycast Prefix for 6to4 Relay RoutersCurrent
May 2015
- RFC 7534AS112 Nameserver OperationsCurrent
May 2015
- RFC 7535AS112 Redirection Using DNAMECurrent
May 2015
- RFC 7536Large-Scale Broadband Measurement Use CasesCurrent
May 2015
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?