--- 1/draft-ietf-ippm-lmap-path-03.txt 2014-06-19 09:14:29.343356193 -0700 +++ 2/draft-ietf-ippm-lmap-path-04.txt 2014-06-19 09:14:29.375356975 -0700 @@ -1,25 +1,25 @@ Network Working Group M. Bagnulo Internet-Draft UC3M Intended status: Informational T. Burbridge -Expires: November 29, 2014 BT +Expires: December 21, 2014 BT S. Crawford SamKnows P. Eardley BT A. Morton AT&T Labs - May 28, 2014 + June 19, 2014 A Reference Path and Measurement Points for LMAP - draft-ietf-ippm-lmap-path-03 + draft-ietf-ippm-lmap-path-04 Abstract This document defines a reference path for Large-scale Measurement of Broadband Access Performance (LMAP) and measurement points for commonly used performance metrics. The methods for measurement point location may be applicable to similar measurement projects using the extensions described here. Status of This Memo @@ -30,48 +30,49 @@ 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 November 29, 2014. + This Internet-Draft will expire on December 21, 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 - 3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 3 - 3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 3 + 3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 4 + 3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 4 3.2. Subscriber . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Dedicated Component (Links or Nodes) . . . . . . . . . . 4 3.4. Shared Component (Links or Nodes) . . . . . . . . . . . . 4 3.5. Resource Transition Point . . . . . . . . . . . . . . . . 4 - 3.6. Managed and Un-Managed Sub-paths . . . . . . . . . . . . 4 + 3.6. Managed and Un-Managed Sub-paths . . . . . . . . . . . . 5 4. Reference Path . . . . . . . . . . . . . . . . . . . . . . . 5 5. Measurement Points . . . . . . . . . . . . . . . . . . . . . 6 6. Translation Between Reference Path and Various Technologies . 10 7. Example Resource Transition . . . . . . . . . . . . . . . . . 11 8. Security considerations . . . . . . . . . . . . . . . . . . . 12 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 11.2. Informative References . . . . . . . . . . . . . . . . . 13 @@ -99,43 +100,53 @@ Measurement points and the paths they cover are often described in general terms, like "end-to-end", "user-to-user", or "access". These terms alone are insufficient for scientific method: What is an end? Where is a user located? Is the home network included? The motivation for this memo is to provide an unambiguous framework to describe measurement coverage, or scope of the reference path. This is an essential part of the meta-data to describe measurement results. Measurements conducted over different path scopes are not a - valid basis for performance comparisons. + valid basis for performance comparisons. We note that additional + measurement context information may be necessary to support a valid + comparison of results. + +1.1. Requirements Language + + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", + "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this + document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Purpose and Scope The scope of this memo is to define a reference path for LMAP activities with sufficient level of detail to determine the location of different measurement points along a path without ambiguity. + These conventions are likely to be useful in other measurement + projects as well. The connection between the reference path and specific network technologies (with differing underlying architectures) is within the scope of this method, and examples are provided. Both wired and wireless technologies are in-scope. The purpose is to create an efficient way to describe the location of the measurement point(s) used to conduct a particular measurement so that the measurement result will adequately described in terms of scope or coverage. This should serve many measurement uses, including: - diagnostic where the same metric may be measured over many different - path scopes + diagnostic: where the same metric may be measured over many + different path scopes - comparison where the same metric may be measured on equivalent + comparison: where the same metric may be measured on equivalent portions of different network infrastructures 3. Terms and Definitions This section defines key terms and concepts for the purposes of this memo. 3.1. Reference Path A reference path is a serial combination of routers, switches, links, @@ -420,22 +431,21 @@ Subscriber -- Private --- Service ------------- GRA --- Transit ... device Net #1 Demarc. GW GRA GW mp000 mp100 mp190 mp200 |_____________UE______________|___RAN+Core____|___GGSN__| |_____Un-managed sub-path_____|____Managed sub-path_____| GRA = Globally Routable Address, GW = Gateway, UE = User Equipment, RAN = Radio Access Network, GGSN = Gateway GPRS Support Node. - We next provide a few examples of DSL access. Consider first the - case where: + We next provide an example of DSL access. Consider the case where: o The Customer Premises Equipment (CPE) has a NAT device that is configured with a public IP address. o The CPE is a home router that has also an incorporated a WiFi access point and this is the only networking device in the home network, all endpoints attach directly to the CPE though the WiFi access. We believe this is a fairly common configuration in some parts of the @@ -447,44 +457,44 @@ Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit device Net #1 Net #2 Demarc. Access GW GRA GW mp000 mp100 mp150 mp190 mp200 |--UE--|------------CPE/NAT--------|------|-BRAS-|------| |------DSL Network---| |_______Un-managed sub-path________|__Managed sub-path__| GRA = Globally Routable Address, GW = Gateway, BRAS = Broadband Remote Acess Server - Consider next the case where: + Consider next another access network case where: o The Customer Premises Equipment (CPE) is a NAT device that is configured with a private IP address. - o There is a Carrier Grade NAT (CGN) located deep into the Access - ISP network. + o There is a Carrier Grade NAT (CGN) located deep in the Access ISP + network. o The CPE is a home router that has also an incorporated a WiFi access point and this is the only networking device in the home network, all endpoints attach directly to the CPE though the WiFi access. We believe this is becoming a fairly common configuration in some parts of the world. This case would map into the defined reference measurement points as follows: Subsc. -- Private ------------- Service-- Intra IP -- GRA -- Transit device Net #1 Demarc. Access GW GRA GW mp000 mp100 mp150 mp190 mp200 |--UE--|------------CPE/NAT--------|------|-CGN-|------| - |-----DSL Network---| + |--Access Network---| |_______Un-managed sub-path________|_Managed sub-path__| GRA = Globally Routable Address, GW = Gateway 7. Example Resource Transition This section gives an example of Shared and Dedicated portions with the reference path. This example shows two Resource Transition Points. @@ -512,21 +522,21 @@ We believe this is a fairly common configuration in parts of the world. This case would map into the defined reference measurement points as follows: Subsc. -- Private -- Private -- Access -- Intra IP -- GRA -- Transit device Net #1 Net #2 Demarc. Access GW GRA GW mp000 mp100 mp150 mp190 mp200 |--UE--|------------CPE/NAT--------|------|-CGN-|------| - | Wi-Fi | 1000Base-T |-----DSL Network---| + | Wi-Fi | 1000Base-T |--Access Network---| |-Shared--|RT|------Dedicated------| RT |-----Shared------... |_______Un-managed sub-path________|_Managed sub-path__| GRA = Globally Routable Address, GW = Gateway, RT = Resource Transition Point 8. Security considerations Specification of a Reference Path and identification of measurement @@ -553,34 +563,37 @@ for review and comments. 11. References 11.1. Normative References [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, "Framework for IP Performance Metrics", RFC 2330, May 1998. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, March 1997. + [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network performance measurement with periodic streams", RFC 3432, November 2002. [RFC5835] Morton, A. and S. Van den Berghe, "Framework for Metric Composition", RFC 5835, April 2010. 11.2. Informative References [I-D.ietf-lmap-framework] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., Aitken, P., and A. Akhter, "A framework for large-scale measurement platforms (LMAP)", draft-ietf-lmap- - framework-05 (work in progress), May 2014. + framework-06 (work in progress), June 2014. [SK] Crawford, Sam., "Test Methodology White Paper", SamKnows Whitebox Briefing Note http://www.samknows.com/broadband/index.php, July 2011. [Q1741] Q.1741.7, , "IMT-2000 references to Release 9 of GSM- evolved UMTS core network", http://www.itu.int/rec/T-REC-Q.1741.7/en, November 2011. Authors' Addresses