Network Working Group P. Fan Internet-Draft China Mobile Intended status: Standards Track February 13, 2014 Expires: August 17, 2014 Performance Metrics for Web Browsing draft-fan-ippm-web-metrics-00 Abstract This document specifies metrics to evaluate performance for web browsing service. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on August 17, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Fan Expires August 17, 2014 [Page 1] Internet-Draft Web Browsing Metrics February 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1. Host Connection Delay . . . . . . . . . . . . . . . . . . 2 2.2. Element Request Delay . . . . . . . . . . . . . . . . . . 2 2.3. Element Waiting Delay . . . . . . . . . . . . . . . . . . 3 2.4. Element Receiving Delay . . . . . . . . . . . . . . . . . 3 2.5. Element Loading Success . . . . . . . . . . . . . . . . . 3 2.6. Web Page TTFB (Time To First Byte) . . . . . . . . . . . 4 2.7. Web Page Loading Time . . . . . . . . . . . . . . . . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. Normative References . . . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction Web browsing has become a fundamental service in today's internet. With its massive users, web browsing service has contributed a large proportion of the total network traffic. Understanding how network performance influences web browsing experience benefits both network and content providers, and measurements like web page loading test are frequently conducted in practice. However, there is currently no standard metric to measure such performance. This document intends to add metrics for web browsing to the set of IP Performance Metrics (IPPM). 2. Metrics This section gives description of a list of metrics that are used to evaluate web browsing related performance. 2.1. Host Connection Delay Host Connect Delay is the time required to create a TCP connection to the web server. If a secure HTTPS connection is being used this time includes the SSL handshake process. The value of a Host Connection Delay is either a real number, or an undefined (informally, infinite) number of seconds. Note that Keep-Alive connections are often used to avoid the overhead of repeatedly connecting to the web server, so this delay is not always necessarily before loading every element. 2.2. Element Request Delay Element Request Delay indicates the time required to send the HTTP request message to the server. The value of an Element Request Delay is either a real number, or an undefined (informally, infinite) Fan Expires August 17, 2014 [Page 2] Internet-Draft Web Browsing Metrics February 2014 number of seconds. An Element Request Delay for an element from a web client is the time from the point when the client starts to send the HTTP request message for the element to the point when the client finishes sending the HTTP request message. This time will depend on the amount of data that is sent to the server. For example, long Send times will result from uploading files using an HTTP POST method. 2.3. Element Waiting Delay Element Waiting Delay indicates the idle time spent waiting for a response message from the server. The value of an Element Waiting Delay is either a real number, or an undefined (informally, infinite) number of seconds. An Element Waiting Delay for an element from a web client is the time from the point when the client finishes sending the HTTP request message to the point when the client receives the first byte of the HTTP response message. This value will depend on the delays introduced due to network latency and the time required to process the request on the web server. 2.4. Element Receiving Delay Element Receiving Delay indicates the time taken to read the HTTP response message from the web server. The value of an Element Receiving Delay is either a real number, or an undefined (informally, infinite) number of seconds. An Element Receiving Delay for an element from a web client is the time from the point when the client receives the first byte of the HTTP response message for the element to the point when the client finishes receiving the HTTP response message. This value will depend on the size of the content returned and network bandwidth. 2.5. Element Loading Success Element Loading Success indicates the result of the HTTP transaction with the web server to download a web page element. The value of an Element Loading Success is either a one (signifying successful loading of the element) or a zero (signifying unsuccessful loading of the element). An Element Loading Success for an element from a web client is 1 exactly when the Element Request Delay, Element Waiting Delay and Element Receiving Delay are all a finite value; An Element Loading Success for an element from a web client is 0 exactly when any of the Element Request Delay, Element Waiting Delay and Element Receiving Delay is undefined. Fan Expires August 17, 2014 [Page 3] Internet-Draft Web Browsing Metrics February 2014 2.6. Web Page TTFB (Time To First Byte) Web Page TTFB indicates the duration needed to receive the first byte from the web server when loading a web page. The value of a Web Page TTFB is either a real number, or an undefined (informally, infinite) number of seconds. A Web Page TTFB for a web page from a web client is the time from the point when the client starts to send the first HTTP request message to the point when the client receives the first byte of the first HTTP response message. 2.7. Web Page Loading Time Web Page Loading Time indicates the duration needed to receive all the elements from the web server when loading a web page. The value of a Web Page Loading Time is either a real number, or an undefined (informally, infinite) number of seconds. A Web Page Loading Time for a web page from a web client is the time from the point when the client starts to send the first HTTP request message to the point when the client finishes receiving the last HTTP response message. 3. Security Considerations TBD. 4. IANA Considerations The document makes no request for IANA action at this time. 5. Normative References [RFC2330] Paxson, V., Almes, G., and J. Mahdavi, "Framework for IP Performance Metrics", RFC 2330, May 1998. [RFC2616] Fielding, R., Gettys, J., and J. Mogul, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Author's Address Peng Fan China Mobile 32 Xuanwumen West Street, Xicheng District Beijing 100053 P.R. China Email: fanpeng@chinamobile.com Fan Expires August 17, 2014 [Page 4]