RFC 7501 on Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and Registration
rfc-editor@rfc-editor.org Mon, 13 April 2015 23:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E181ACE98; Mon, 13 Apr 2015 16:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDXhJKMPAk4W; Mon, 13 Apr 2015 16:35:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id F229F1AD353; Mon, 13 Apr 2015 16:35:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 63CF8180470; Mon, 13 Apr 2015 16:35:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7501 on Terminology for Benchmarking Session Initiation Protocol (SIP) Devices: Basic Session Setup and Registration
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150413233504.63CF8180470@rfc-editor.org>
Date: Mon, 13 Apr 2015 16:35:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/PePJPT0c3OdjFH-skitQcp2AItM>
Cc: bmwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2015 23:35:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7501
Title: Terminology for Benchmarking Session Initiation
Protocol (SIP) Devices: Basic Session Setup
and Registration
Author: C. Davids, V. Gurbani, S. Poretsky
Status: Informational
Stream: IETF
Date: April 2015
Mailbox: davids@iit.edu,
vkg@bell-labs.com,
sporetsky@allot.com
Pages: 20
Characters: 36573
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-sip-bench-term-12.txt
URL: https://www.rfc-editor.org/info/rfc7501
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.
This document is a product of the Benchmarking Methodology Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC