idnits 2.17.00 (12 Aug 2021) /tmp/idnits24720/draft-fan-ippm-web-metrics-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 13, 2014) is 3019 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2330' is defined on line 170, but no explicit reference was found in the text == Unused Reference: 'RFC2616' is defined on line 173, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2330 ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Fan 3 Internet-Draft China Mobile 4 Intended status: Standards Track February 13, 2014 5 Expires: August 17, 2014 7 Performance Metrics for Web Browsing 8 draft-fan-ippm-web-metrics-00 10 Abstract 12 This document specifies metrics to evaluate performance for web 13 browsing service. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on August 17, 2014. 32 Copyright Notice 34 Copyright (c) 2014 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2.1. Host Connection Delay . . . . . . . . . . . . . . . . . . 2 52 2.2. Element Request Delay . . . . . . . . . . . . . . . . . . 2 53 2.3. Element Waiting Delay . . . . . . . . . . . . . . . . . . 3 54 2.4. Element Receiving Delay . . . . . . . . . . . . . . . . . 3 55 2.5. Element Loading Success . . . . . . . . . . . . . . . . . 3 56 2.6. Web Page TTFB (Time To First Byte) . . . . . . . . . . . 4 57 2.7. Web Page Loading Time . . . . . . . . . . . . . . . . . . 4 58 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 5. Normative References . . . . . . . . . . . . . . . . . . . . 4 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 Web browsing has become a fundamental service in today's internet. 66 With its massive users, web browsing service has contributed a large 67 proportion of the total network traffic. Understanding how network 68 performance influences web browsing experience benefits both network 69 and content providers, and measurements like web page loading test 70 are frequently conducted in practice. However, there is currently no 71 standard metric to measure such performance. This document intends 72 to add metrics for web browsing to the set of IP Performance Metrics 73 (IPPM). 75 2. Metrics 77 This section gives description of a list of metrics that are used to 78 evaluate web browsing related performance. 80 2.1. Host Connection Delay 82 Host Connect Delay is the time required to create a TCP connection to 83 the web server. If a secure HTTPS connection is being used this time 84 includes the SSL handshake process. The value of a Host Connection 85 Delay is either a real number, or an undefined (informally, infinite) 86 number of seconds. Note that Keep-Alive connections are often used 87 to avoid the overhead of repeatedly connecting to the web server, so 88 this delay is not always necessarily before loading every element. 90 2.2. Element Request Delay 92 Element Request Delay indicates the time required to send the HTTP 93 request message to the server. The value of an Element Request Delay 94 is either a real number, or an undefined (informally, infinite) 95 number of seconds. An Element Request Delay for an element from a 96 web client is the time from the point when the client starts to send 97 the HTTP request message for the element to the point when the client 98 finishes sending the HTTP request message. This time will depend on 99 the amount of data that is sent to the server. For example, long 100 Send times will result from uploading files using an HTTP POST 101 method. 103 2.3. Element Waiting Delay 105 Element Waiting Delay indicates the idle time spent waiting for a 106 response message from the server. The value of an Element Waiting 107 Delay is either a real number, or an undefined (informally, infinite) 108 number of seconds. An Element Waiting Delay for an element from a 109 web client is the time from the point when the client finishes 110 sending the HTTP request message to the point when the client 111 receives the first byte of the HTTP response message. This value 112 will depend on the delays introduced due to network latency and the 113 time required to process the request on the web server. 115 2.4. Element Receiving Delay 117 Element Receiving Delay indicates the time taken to read the HTTP 118 response message from the web server. The value of an Element 119 Receiving Delay is either a real number, or an undefined (informally, 120 infinite) number of seconds. An Element Receiving Delay for an 121 element from a web client is the time from the point when the client 122 receives the first byte of the HTTP response message for the element 123 to the point when the client finishes receiving the HTTP response 124 message. This value will depend on the size of the content returned 125 and network bandwidth. 127 2.5. Element Loading Success 129 Element Loading Success indicates the result of the HTTP transaction 130 with the web server to download a web page element. The value of an 131 Element Loading Success is either a one (signifying successful 132 loading of the element) or a zero (signifying unsuccessful loading of 133 the element). An Element Loading Success for an element from a web 134 client is 1 exactly when the Element Request Delay, Element Waiting 135 Delay and Element Receiving Delay are all a finite value; An Element 136 Loading Success for an element from a web client is 0 exactly when 137 any of the Element Request Delay, Element Waiting Delay and Element 138 Receiving Delay is undefined. 140 2.6. Web Page TTFB (Time To First Byte) 142 Web Page TTFB indicates the duration needed to receive the first byte 143 from the web server when loading a web page. The value of a Web Page 144 TTFB is either a real number, or an undefined (informally, infinite) 145 number of seconds. A Web Page TTFB for a web page from a web client 146 is the time from the point when the client starts to send the first 147 HTTP request message to the point when the client receives the first 148 byte of the first HTTP response message. 150 2.7. Web Page Loading Time 152 Web Page Loading Time indicates the duration needed to receive all 153 the elements from the web server when loading a web page. The value 154 of a Web Page Loading Time is either a real number, or an undefined 155 (informally, infinite) number of seconds. A Web Page Loading Time 156 for a web page from a web client is the time from the point when the 157 client starts to send the first HTTP request message to the point 158 when the client finishes receiving the last HTTP response message. 160 3. Security Considerations 162 TBD. 164 4. IANA Considerations 166 The document makes no request for IANA action at this time. 168 5. Normative References 170 [RFC2330] Paxson, V., Almes, G., and J. Mahdavi, "Framework for IP 171 Performance Metrics", RFC 2330, May 1998. 173 [RFC2616] Fielding, R., Gettys, J., and J. Mogul, "Hypertext 174 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 176 Author's Address 178 Peng Fan 179 China Mobile 180 32 Xuanwumen West Street, Xicheng District 181 Beijing 100053 182 P.R. China 184 Email: fanpeng@chinamobile.com