draft-ietf-bmwg-sip-bench-term-05.txt   draft-ietf-bmwg-sip-bench-term-06.txt 
Benchmarking Methodology Working Group C. Davids Benchmarking Methodology Working C. Davids
Internet-Draft Illinois Institute of Technology Group Illinois Institute of Technology
Expires: April 25, 2013 V. Gurbani Internet-Draft V. Gurbani
Bell Laboratories, Expires: May 12, 2013 Bell Laboratories, Alcatel-Lucent
Alcatel-Lucent
S. Poretsky S. Poretsky
Allot Communications Allot Communications
October 22, 2012 November 8, 2012
Terminology for Benchmarking Session Initiation Protocol (SIP) Terminology for Benchmarking Session Initiation Protocol (SIP)
Networking Devices Networking Devices
draft-ietf-bmwg-sip-bench-term-05 draft-ietf-bmwg-sip-bench-term-06
Abstract Abstract
This document provides a terminology for benchmarking the SIP This document provides a terminology for benchmarking the SIP
performance of networking devices. The term performance in this performance of networking devices. The term performance in this
context means the capacity of the device- or system-under-test to context means the capacity of the device- or system-under-test to
process SIP messages. Terms are included for test components, test process SIP messages. Terms are included for test components, test
setup parameters, and performance benchmark metrics for black-box setup parameters, and performance benchmark metrics for black-box
benchmarking of SIP networking devices. The performance benchmark benchmarking of SIP networking devices. The performance benchmark
metrics are obtained for the SIP signaling plane only. The terms are metrics are obtained for the SIP signaling plane only. The terms are
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2013. This Internet-Draft will expire on May 12, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 15, line 12 skipping to change at page 15, line 12
term "dialog" to refer to a signaling-only relationship between term "dialog" to refer to a signaling-only relationship between
User Agent peers. SIP reserves the term "transaction" to refer to User Agent peers. SIP reserves the term "transaction" to refer to
the brief communication between a client and a server that lasts the brief communication between a client and a server that lasts
only until the final response to the SIP request. None of these only until the final response to the SIP request. None of these
terms describes the entity whose performance we want to benchmark. terms describes the entity whose performance we want to benchmark.
For example, the MESSAGE request does not create a dialog and can For example, the MESSAGE request does not create a dialog and can
be sent either within or outside of a dialog. It is not be sent either within or outside of a dialog. It is not
associated with media, but it resembles a phone call in its associated with media, but it resembles a phone call in its
dependence on human rather than machine initiated responses. The dependence on human rather than machine initiated responses. The
SUBSCRIBE method does create a dialog between the originating end- SUBSCRIBE method does create a dialog between the originating end-
user and the subscription service. It too is not associated with user and the subscription service. It, too, is not associated
a media session. In light of these observations we have extended with a media session.
the term "session" to include SIP-based services that are not In light of the above observations we have extended the term
initiated by INVITE requests and that do not have associated "session" to include SIP-based services that are not initiated by
media. In this extended definition, a session always has a INVITE requests and that do not have associated media. In this
signaling component and may also have a media component. Thus, a extended definition, a session always has a signaling component
session can be defined as signaling-only or a combination of and may also have a media component. Thus, a session can be
signaling and media. We define the term "Associated Media", see defined as signaling-only or a combination of signaling and media.
Section 3.1.4, to describe the situation in which media is We define the term "Associated Media", see Section 3.1.4, to
associated with a SIP dialog. The terminology "Invite-initiated describe the situation in which media is associated with a SIP
Session" (IS) Section 3.1.8 and "Non-invite-Initiated Session" dialog. The terminology "Invite-initiated Session" (IS)
(NS) (add xref target="NS") are used to distinguish between these Section 3.1.8 and "Non-invite-Initiated Session" (NS)
two types of session. An Invite-initiated Session is a session as Section 3.1.9 are used to distinguish between these two types of
defined in SIP. The performance of a device or system that session. An Invite-initiated Session is a session as defined in
supports Invite-initiated Sessions that do not create media SIP. The performance of a device or system that supports Invite-
sessions, "Invite-initiated Sessions without Associated Media", initiated Sessions that do not create media sessions, "Invite-
can be measured and is of interest for comparison and as a initiated Sessions without Associated Media", can be measured and
limiting case. The REGISTER request can be considered to be a is of interest for comparison and as a limiting case. The
"Non-invite-initiated Session without Associated Media." A REGISTER request can be considered to be a "Non-invite-initiated
separate set of benchmarks is provided for REGISTER requests since Session without Associated Media." A separate set of benchmarks
most implementations of SIP-based services require this request is provided for REGISTER requests since most implementations of
and since a registrar may be a device under test. SIP-based services require this request and since a registrar may
be a device under test.
A Session in the context of this document, can be considered to be A Session in the context of this document, can be considered to be
a vector with three components: a vector with three components:
1. A component in the signaling plane (SIP messages), sess.sig; 1. A component in the signaling plane (SIP messages), sess.sig;
2. A media component in the media plane (RTP and SRTP streams for 2. A media component in the media plane (RTP and SRTP streams for
example), sess.med (which may be null); example), sess.med (which may be null);
3. A control component in the media plane (RTCP messages for 3. A control component in the media plane (RTCP messages for
example), sess.medc (which may be null). example), sess.medc (which may be null).
skipping to change at page 36, line 9 skipping to change at page 36, line 9
[RFC3711] and various other drafts. This document attempts to [RFC3711] and various other drafts. This document attempts to
formalize a set of common terminology for benchmarking SIP networks. formalize a set of common terminology for benchmarking SIP networks.
Packets with unintended and/or unauthorized DSCP or IP precedence Packets with unintended and/or unauthorized DSCP or IP precedence
values may present security issues. Determining the security values may present security issues. Determining the security
consequences of such packets is out of scope for this document. consequences of such packets is out of scope for this document.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Keith Drage, Cullen Jennings, Daryl The authors would like to thank Keith Drage, Cullen Jennings, Daryl
Malas, Al Morton, and Henning Schulzrinne for invaluable Malas, Al Morton, and Henning Schulzrinne for invaluable
contributions to this document. contributions to this document. Dale Worley provided an extensive
review that lead to improvements in the documents.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, March 1999. Network Interconnect Devices", RFC 2544, March 1999.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[I-D.ietf-bmwg-sip-bench-meth] [I-D.ietf-bmwg-sip-bench-meth]
Davids, C., Gurbani, V., and S. Poretsky, "Methodology for Davids, C., Gurbani, V., and S. Poretsky, "Methodology for
Benchmarking SIP Networking Devices", Benchmarking SIP Networking Devices",
draft-ietf-bmwg-sip-bench-meth-04 (work in progress), draft-ietf-bmwg-sip-bench-meth-05 (work in progress),
March 2012. October 2012.
7.2. Informational References 7.2. Informational References
[RFC2285] Mandeville, R., "Benchmarking Terminology for LAN [RFC2285] Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, February 1998. Switching Devices", RFC 2285, February 1998.
[RFC1242] Bradner, S., "Benchmarking terminology for network [RFC1242] Bradner, S., "Benchmarking terminology for network
interconnection devices", RFC 1242, July 1991. interconnection devices", RFC 1242, July 1991.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
 End of changes. 7 change blocks. 
33 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/