| < draft-ietf-ippm-lmap-path-04.txt | draft-ietf-ippm-lmap-path-05.txt > | |||
|---|---|---|---|---|
| Network Working Group M. Bagnulo | Network Working Group M. Bagnulo | |||
| Internet-Draft UC3M | Internet-Draft UC3M | |||
| Intended status: Informational T. Burbridge | Intended status: Informational T. Burbridge | |||
| Expires: December 21, 2014 BT | Expires: February 6, 2015 BT | |||
| S. Crawford | S. Crawford | |||
| SamKnows | SamKnows | |||
| P. Eardley | P. Eardley | |||
| BT | BT | |||
| A. Morton | A. Morton | |||
| AT&T Labs | AT&T Labs | |||
| June 19, 2014 | August 5, 2014 | |||
| A Reference Path and Measurement Points for LMAP | A Reference Path and Measurement Points for LMAP | |||
| draft-ietf-ippm-lmap-path-04 | draft-ietf-ippm-lmap-path-05 | |||
| Abstract | Abstract | |||
| This document defines a reference path for Large-scale Measurement of | This document defines a reference path for Large-scale Measurement of | |||
| Broadband Access Performance (LMAP) and measurement points for | Broadband Access Performance (LMAP) and measurement points for | |||
| commonly used performance metrics. The methods for measurement point | commonly used performance metrics. Other similar measurement | |||
| location may be applicable to similar measurement projects using the | projects may also be able to use the extensions described here for | |||
| extensions described here. | measurement point location. | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| 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 December 21, 2014. | This Internet-Draft will expire on February 6, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 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 2, line 22 ¶ | skipping to change at page 2, line 22 ¶ | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 4 | 3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 4 | 3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.2. Subscriber . . . . . . . . . . . . . . . . . . . . . . . 4 | 3.2. Subscriber . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 3.3. Dedicated Component (Links or Nodes) . . . . . . . . . . 4 | 3.3. Dedicated Component (Links or Nodes) . . . . . . . . . . 4 | |||
| 3.4. Shared Component (Links or Nodes) . . . . . . . . . . . . 4 | 3.4. Shared Component (Links or Nodes) . . . . . . . . . . . . 4 | |||
| 3.5. Resource Transition Point . . . . . . . . . . . . . . . . 4 | 3.5. Resource Transition Point . . . . . . . . . . . . . . . . 5 | |||
| 3.6. Managed and Un-Managed Sub-paths . . . . . . . . . . . . 5 | 3.6. Managed and Un-Managed Sub-paths . . . . . . . . . . . . 5 | |||
| 4. Reference Path . . . . . . . . . . . . . . . . . . . . . . . 5 | 4. Reference Path . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 5. Measurement Points . . . . . . . . . . . . . . . . . . . . . 6 | 5. Measurement Points . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 6. Translation Between Reference Path and Various Technologies . 10 | 6. Translation Between Reference Path and Various Technologies . 10 | |||
| 7. Example Resource Transition . . . . . . . . . . . . . . . . . 11 | 7. Example Resource Transition . . . . . . . . . . . . . . . . . 12 | |||
| 8. Security considerations . . . . . . . . . . . . . . . . . . . 12 | 8. Security considerations . . . . . . . . . . . . . . . . . . . 13 | |||
| 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 | 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 | 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 | 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 | 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 | |||
| 11.2. Informative References . . . . . . . . . . . . . . . . . 13 | 11.2. Informative References . . . . . . . . . . . . . . . . . 14 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 1. Introduction | 1. Introduction | |||
| This document defines a reference path for Large-scale Measurement of | This document defines a reference path for Large-scale Measurement of | |||
| Broadband Access Performance (LMAP) or similar measurement projects. | Broadband Access Performance (LMAP) or similar measurement projects. | |||
| The series of IP Performance Metrics (IPPM) RFCs have developed terms | The series of IP Performance Metrics (IPPM) RFCs have developed terms | |||
| that are generally useful for path description (section 5 of | that are generally useful for path description (section 5 of | |||
| [RFC2330]). There are a limited number of additional terms needing | [RFC2330]). There are a limited number of additional terms needing | |||
| definition here, and they will be defined in this memo. | definition here, and they will be defined in this memo. | |||
| skipping to change at page 3, line 46 ¶ | skipping to change at page 3, line 46 ¶ | |||
| technologies (with differing underlying architectures) is within the | technologies (with differing underlying architectures) is within the | |||
| scope of this method, and examples are provided. Both wired and | scope of this method, and examples are provided. Both wired and | |||
| wireless technologies are in-scope. | wireless technologies are in-scope. | |||
| The purpose is to create an efficient way to describe the location of | The purpose is to create an efficient way to describe the location of | |||
| the measurement point(s) used to conduct a particular measurement so | the measurement point(s) used to conduct a particular measurement so | |||
| that the measurement result will adequately described in terms of | that the measurement result will adequately described in terms of | |||
| scope or coverage. This should serve many measurement uses, | scope or coverage. This should serve many measurement uses, | |||
| including: | including: | |||
| diagnostic: where the same metric may be measured over many | diagnostic: where the same metric would be measured on different | |||
| different path scopes | sub-paths bounded by measurement points (see Section 4.10 | |||
| of[RFC5835]), for example to isolate the sub-path contributing the | ||||
| majority of impairment levels observed on a path. | ||||
| 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 | portions of different network infrastructures, for example to | |||
| compare the performance of wired and wireless home network | ||||
| technologies. | ||||
| 3. Terms and Definitions | 3. Terms and Definitions | |||
| This section defines key terms and concepts for the purposes of this | This section defines key terms and concepts for the purposes of this | |||
| memo. | memo. | |||
| 3.1. Reference Path | 3.1. Reference Path | |||
| A reference path is a serial combination of routers, switches, links, | A reference path is a serial combination of routers, switches, links, | |||
| radios, and processing elements that comprise all the network | radios, and processing elements that comprise all the network | |||
| elements traversed by each packet between the source and destination | elements traversed by each packet between the source and destination | |||
| hosts. The reference path is intended to be equally applicable to | hosts. The reference path is intended to be equally applicable to | |||
| all networking technologies, therefore the components are generically | all networking technologies, therefore the components are generically | |||
| defined, but their functions should have a clear counterpart or be | defined, but their functions should have a clear counterpart or be | |||
| obviously omitted in any network technology. | obviously omitted in any network technology. | |||
| 3.2. Subscriber | 3.2. Subscriber | |||
| An entity (associated with one or more users) that is engaged in a | An entity (associated with one or more users) that is engaged in a | |||
| subscription with a service provider. The subscriber is allowed to | subscription with a service provider. The subscriber is allowed to | |||
| subscribe and un-subscribe services, and to register a user or a list | subscribe and un-subscribe to services, and to register a user or a | |||
| of users authorized to enjoy these services. [Q1741] Both the | list of users authorized to enjoy these services. [Q1741] Both the | |||
| subscriber and service provider are allowed to set the limits | subscriber and service provider are allowed to set the limits | |||
| relative to the use that associated users make of subscribed | relative to the use that associated users make of subscribed | |||
| services. | services. | |||
| 3.3. Dedicated Component (Links or Nodes) | 3.3. Dedicated Component (Links or Nodes) | |||
| All resources of a Dedicated component (typically a link or node on | All resources of a Dedicated component (typically a link or node on | |||
| the Reference Path) are allocated to serving the traffic of an | the Reference Path) are allocated to serving the traffic of an | |||
| individual Subscriber. Resources include transmission time-slots, | individual Subscriber. Resources include transmission time-slots, | |||
| queue space, processing for encapsulation and address/port | queue space, processing for encapsulation and address/port | |||
| skipping to change at page 5, line 19 ¶ | skipping to change at page 5, line 25 ¶ | |||
| management of the subscriber's service provider. This means that | management of the subscriber's service provider. This means that | |||
| private networks, wireless networks using unlicensed frequencies, and | private networks, wireless networks using unlicensed frequencies, and | |||
| the networks of other service are designated as un-managed sub-paths. | the networks of other service are designated as un-managed sub-paths. | |||
| The Service demarcation point always divides managed and un-managed | The Service demarcation point always divides managed and un-managed | |||
| sub-paths. | sub-paths. | |||
| 4. Reference Path | 4. Reference Path | |||
| This section defines a reference path for Internet communication. | This section defines a reference path for Internet communication. | |||
| Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit | Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit ... | |||
| device Net #1 Net #2 Demarc. Access GW GRA GW | device Net #1 Net #2 Demarc. Access GW GRA GW | |||
| ... Transit -- GRA -- Service -- Private -- Private -- Destination | ... Transit -- GRA -- Service -- Private -- Private -- Destination | |||
| GRA GW GW Demarc. Net #n Net #n+1 Host | GRA GW GW Demarc. Net #n Net #n+1 Host | |||
| GRA = Globally Routable Address, GW = Gateway | GRA = Globally Routable Address, GW = Gateway | |||
| The following are descriptions of reference path components that may | The following are descriptions of reference path components that may | |||
| not be clear from their name alone. | not be clear from their name alone. | |||
| o Subsc. (Subscriber) device - This is a host that normally | o Subsc. (Subscriber) device - This is a host that normally | |||
| originates and terminates communications conducted over the IP | originates and terminates communications conducted over the IP | |||
| packet transfer service. | packet transfer service. | |||
| o Private Net #x - This is a network of devices owned and operated | o Private Net #x - This is a network of devices owned and operated | |||
| by the Internet Service Subscriber. In some configurations, one | by the Internet Service Subscriber. In some configurations, one | |||
| or more private networks and the device that provides the Service | or more private networks and the device that provides the Service | |||
| Demarcation point are collapsed in a single device (and ownership | Demarcation point are collapsed in a single device (and ownership | |||
| may shift to the service provider), and this should be noted as | may shift to the service provider), and this should be noted as | |||
| part of the path description. | part of the path description. | |||
| o Service Demarcation point - This is the point where service | o Service Demarcation point - This is the point where service | |||
| managed by the serivce provider begins (or ends), and varies by | managed by the service provider begins (or ends), and varies by | |||
| technology. For example, this point is usually defined as the | technology. For example, this point is usually defined as the | |||
| Ethernet interface on a residential gateway or modem where the | Ethernet interface on a residential gateway or modem where the | |||
| scope of a packet transfer service begins and ends. In the case | scope of a packet transfer service begins and ends. In the case | |||
| of a WiFi Service, this would be an Air Interface within the | of a WiFi Service, this would be an Air Interface within the | |||
| intended service boundary (e.g., walls of the coffee shop). The | intended service boundary (e.g., walls of the coffee shop). The | |||
| Demarcation point may be within an integrated endpoint using an | Demarcation point may be within an integrated endpoint using an | |||
| Air Interface (e.g., LTE UE). Ownership may not affect the | Air Interface (e.g., LTE UE). Ownership does not necessarily | |||
| demarcation point; a Subscriber may own all equipment on their | affect the demarcation point; a Subscriber may own all equipment | |||
| premises, but it is likely that the service provider will certify | on their premises, but it is likely that the service provider will | |||
| such equipment for connection to their network, or a third-party | certify such equipment for connection to their network, or a | |||
| will certify standards compliance. | third-party will certify standards compliance. | |||
| o Intra IP Access - This is the first point in the access | o Intra IP Access - This is the first point in the access | |||
| architecture beyond the Service Demarc. where a globally routable | architecture beyond the Service Demarc. where a globally routable | |||
| IP address is exposed and used for routing. In architectures that | IP address is exposed and used for routing. In architectures that | |||
| use tunneling, this point may be equivalent to the GRA GW. This | use tunneling, this point may be equivalent to the GRA GW. This | |||
| point could also collapse to the device providing the Service | point could also collapse to the device providing the Service | |||
| Demarc., in principle. Only one Intra IP Access point is shown, | Demarc., in principle. Only one Intra IP Access point is shown, | |||
| but they can be identified in any access network. | but they can be identified in any access network. | |||
| o GRA GW - the point of interconnection between a Service Provider's | o GRA GW - the point of interconnection between a Service Provider's | |||
| skipping to change at page 6, line 30 ¶ | skipping to change at page 6, line 36 ¶ | |||
| o Transit GRA GW - If one or more networks intervene between the | o Transit GRA GW - If one or more networks intervene between the | |||
| Service Provider's access networks of the Subscriber and of the | Service Provider's access networks of the Subscriber and of the | |||
| Destination Host, then such networks are designated "transit" and | Destination Host, then such networks are designated "transit" and | |||
| are bounded by two Transit GRA GW. | are bounded by two Transit GRA GW. | |||
| Use of multiple IP address families in the measurement path must be | Use of multiple IP address families in the measurement path must be | |||
| noted, as the conversions between IPv4 and IPv6 certainly influence | noted, as the conversions between IPv4 and IPv6 certainly influence | |||
| the visibility of a GRA for each family. | the visibility of a GRA for each family. | |||
| In the case that a private address space is used throughout an access | In the case that a private address space is used throughout an access | |||
| architecture, then the Service Demarc. and the Intra IP Access points | architecture, then the Intra IP Access points must use the same | |||
| must use the same address space and be separated by the shared and | address space as the Service Demarcation point, and the Intra IP | |||
| dedicated access link infrastructure, such that a test between these | Access points must be selected such that a test between these points | |||
| points produces a useful assessment of access performance. | produces a useful assessment of access performance (e.g., includes | |||
| both shared and dedicated access link infrastructure). | ||||
| 5. Measurement Points | 5. Measurement Points | |||
| A key aspect of measurement points, beyond the definition in section | A key aspect of measurement points, beyond the definition in section | |||
| 4.1 of [RFC5835], is that the innermost IP header and higher layer | 4.1 of [RFC5835], is that the innermost IP header and higher layer | |||
| information must be accessible through some means. This is essential | information must be accessible through some means. This is essential | |||
| to measure IP metrics. There may be tunnels and/or other layers | to measure IP metrics. There may be tunnels and/or other layers | |||
| which encapsulate the innermost IP header, even adding another IP | which encapsulate the innermost IP header, even adding another IP | |||
| header of their own. | header of their own. | |||
| In general, measurement points cannot always be located exactly where | In general, measurement points cannot always be located exactly where | |||
| desired. However, the definition in [RFC5835] and the discussion in | desired. However, the definition in [RFC5835] and the discussion in | |||
| section 5.1 of [RFC3432] indicate that allowances can be made: for | section 5.1 of [RFC3432] indicate that allowances can be made: for | |||
| example, it is nearly ideal when there are deterministic errors that | example, it is nearly ideal when there are deterministic errors that | |||
| can be quantified between desired and actual measurement point. | can be quantified between desired and actual measurement point. | |||
| The Figure below illustrates the assignment of measurement points to | The Figure below illustrates the assignment of measurement points to | |||
| selected components of the reference path. | selected components of the reference path. | |||
| Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit | Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit ... | |||
| device Net #1 Net #2 Demarc. Access GW GRA GW | device Net #1 Net #2 Demarc. Access GW GRA GW | |||
| mp000 mp100 mp150 mp190 mp200 | mp000 mp100 mp150 mp190 mp200 | |||
| ... Transit -- GRA -- Service -- Private -- Private -- Destination | ... Transit -- GRA -- Service -- Private -- Private -- Destination | |||
| GRA GW GW Demarc. Net #n Net #n+1 Host | GRA GW GW Demarc. Net #n Net #n+1 Host | |||
| mpX90 mp890 mp800 mp900 | mpX90 mp890 mp800 mp900 | |||
| GRA = Globally Routable Address, GW = Gateway | GRA = Globally Routable Address, GW = Gateway | |||
| Figure 1 | Figure 1 | |||
| When communicating the results of measurements using the measurement | Each measurement point on a specific reference path MUST be assigned | |||
| point designations described here, the measuring organization SHOULD | a unique number. To facilitate interpretation of the results, the | |||
| supply a diagram similar to Figure 1 (and the technology-specific | measuring organisation (and whoever it shares results with) MUST have | |||
| examples that follow), and MUST supply it when additional measurement | an unambiguous understanding of what path or point was measured. In | |||
| point numbers have been defined and used, with sufficient detail to | order to achieve this, a set of numbering recommendations follow. | |||
| identify measurement locations in the path. Organizations with | ||||
| similar technologies and architectures are encouraged to coordinate | When communicating the results of measurements, the measuring | |||
| on local numbering and diagrams, when possible. | organization SHOULD supply a diagram similar to Figure 1 (with the | |||
| technology-specific information in examples that follow), and MUST | ||||
| supply it when additional measurement point numbers have been defined | ||||
| and used, with sufficient detail to identify measurement locations in | ||||
| the path. | ||||
| Ideally, the consumer of measurement results would know the location | ||||
| of a measurement point on the reference path from the measurement | ||||
| point number alone, and the recommendations below provide a way to | ||||
| accomplish this goal. Although the initial numbering may be fully | ||||
| compliant with this system, network growth, consolidation, and re- | ||||
| arrangement, or circumstances such as ownership changes, could cause | ||||
| gaps in network numbers or non-monotonic measurement point number | ||||
| assignments along the path over time. These are examples of | ||||
| reasonable causes for numbering deviations which must be identified | ||||
| on the reference path diagram, as required above. | ||||
| Whilst the numbering of a measurement point is in the context of a | ||||
| particular path, for simplicity the measuring organisation SHOULD use | ||||
| the same numbering for a device (playing the same role) on all the | ||||
| measurement paths through it. Similarly, whilst the measurement | ||||
| point numbering is in the context of a particular measuring | ||||
| organisation, organizations with similar technologies and | ||||
| architectures are encouraged to coordinate on local numbering and | ||||
| diagrams. | ||||
| The measurement point numbering system, mpXnn, has two independent | The measurement point numbering system, mpXnn, has two independent | |||
| parts: | parts: | |||
| 1. The X in mpXnn indicates the network number. The network with | 1. The X in mpXnn indicates the network number. The network with | |||
| the Subscriber's device is network 0. The network of a different | the Subscriber's device is network 0. The network of a different | |||
| organization (administrative or ownership domains) SHOULD be | organization (administrative or ownership domains) SHOULD be | |||
| assigned a different number. Each successive network number | assigned a different number. Each successive network number | |||
| SHOULD be one greater than the previous network's number. Two | SHOULD be one greater than the previous network's number. Two | |||
| circumstances make it necessary to designate X=9 in the | circumstances make it necessary to designate X=9 in the | |||
| skipping to change at page 8, line 14 ¶ | skipping to change at page 8, line 46 ¶ | |||
| B. 90 SHOULD be used for a measurement point at the GW of a | B. 90 SHOULD be used for a measurement point at the GW of a | |||
| network (opposite from the Subscriber's device or Service | network (opposite from the Subscriber's device or Service | |||
| Demarc.). | Demarc.). | |||
| C. In most networks, measurement point numbers SHOULD | C. In most networks, measurement point numbers SHOULD | |||
| monotonically increase from point nearest the Subscriber's | monotonically increase from point nearest the Subscriber's | |||
| device to the opposite network boundary on the path (see | device to the opposite network boundary on the path (see | |||
| below). | below). | |||
| D. When a Detination host is part of the path, 00 SHOULD be used | D. When a Destination host is part of the path, 00 SHOULD be | |||
| for a measurement point at the Destination host and at the | used for a measurement point at the Destination host and at | |||
| the Destination's Service Demarcation point. Measurement | the Destination's Service Demarcation point. Measurement | |||
| point numbers SHOULD monotonically increase from point | point numbers SHOULD monotonically increase from point | |||
| nearest the Destination's host to the opposite network | nearest the Destination's host to the opposite network | |||
| boundary on the path ONLY in these networks. This | boundary on the path ONLY in these networks. This | |||
| directional numbering reversal allows consistent 00 | directional numbering reversal allows consistent 00 | |||
| designation for end hosts and Service Demarcs. | designation for end hosts and Service Demarcs. | |||
| E. 50 MAY be used for an intermediate measurement point of | E. 50 MAY be used for an intermediate measurement point of | |||
| significance, such as a Network Address Translator (NAT). | significance, such as a Network Address Translator (NAT). | |||
| skipping to change at page 8, line 37 ¶ | skipping to change at page 9, line 21 ¶ | |||
| DSLAM within a network. | DSLAM within a network. | |||
| G. Any other measurement points SHOULD be assigned unused | G. Any other measurement points SHOULD be assigned unused | |||
| integers between 01 and 99. The assignment SHOULD be stable | integers between 01 and 99. The assignment SHOULD be stable | |||
| for at least the duration of a particular measurement study, | for at least the duration of a particular measurement study, | |||
| and SHOULD avoid numbers that have been assigned to other | and SHOULD avoid numbers that have been assigned to other | |||
| locations within network X (unless the assignment is | locations within network X (unless the assignment is | |||
| considered sufficiently stale). Sub-networks or domains | considered sufficiently stale). Sub-networks or domains | |||
| within a network are useful locations for measurement points. | within a network are useful locations for measurement points. | |||
| In order to define the measurement points and the scope of | When supplying a diagram of the reference path and measurement | |||
| measurements without ambiguity, the operator of the measurement | points, the operator of the measurement system MUST indicate: the | |||
| system SHOULD indicate on a diagram (similar to those in this | reference path, the numbers (mpXnn) of the measurement points, and | |||
| document): the reference path, the numbers (mpXnn) of the measurement | the technology-specific definition of any measurement point other | |||
| points, and the definition of any measurement point other than 00 and | than X00 and X90 with sufficient detail to clearly define its | |||
| 90 (with sufficient detail to clearly define its location). | location (similar to the technology-specific examples in Section 6 of | |||
| this document). | ||||
| If the number of intermediate networks (between the source and | If the number of intermediate networks (between the source and | |||
| destination) is not known or is unstable, then this SHOULD be | destination) is not known or is unstable, then this SHOULD be | |||
| indicated on the diagram and results from measurement points within | indicated on the diagram and results from measurement points within | |||
| those networks need to be treated with caution. | those networks need to be treated with caution. | |||
| Notes: | Notes: | |||
| o Some use the terminology "on-net" and "off-net" when referring to | o Some use the terminology "on-net" and "off-net" when referring to | |||
| the Subscriber's Internet Service Provider (ISP) measurement | the Subscriber's Internet Service Provider (ISP) measurement | |||
| skipping to change at page 10, line 7 ¶ | skipping to change at page 10, line 38 ¶ | |||
| mp150, then the private address side of the CGN could be | mp150, then the private address side of the CGN could be | |||
| designated mp149 for tests with mp100. | designated mp149 for tests with mp100. | |||
| o Measurement points at Transit GRA GWs are numbered mpX00 and | o Measurement points at Transit GRA GWs are numbered mpX00 and | |||
| mpX90, where X is the lowest positive integer not already used in | mpX90, where X is the lowest positive integer not already used in | |||
| the path. The GW of first transit network is shown, with point | the path. The GW of first transit network is shown, with point | |||
| mp200 and the last transit network GW with mpX90. | mp200 and the last transit network GW with mpX90. | |||
| 6. Translation Between Reference Path and Various Technologies | 6. Translation Between Reference Path and Various Technologies | |||
| This section and those that follow are intended to provide a more | This section and those that follow are intended to provide example | |||
| exact mapping between particular network technologies and the | mappings between particular network technologies and the reference | |||
| reference path. | path. | |||
| We provide an example for 3G Cellular access below. | We provide an example for 3G Cellular access below. | |||
| Subscriber -- Private --- Service ------------- GRA --- Transit ... | Subscriber -- Private --- Service ------------- GRA --- Transit ... | |||
| device Net #1 Demarc. GW GRA GW | device Net #1 Demarc. GW GRA GW | |||
| mp000 mp100 mp190 mp200 | mp000 mp100 mp190 mp200 | |||
| |_____________UE______________|___RAN+Core____|___GGSN__| | |_____________UE______________|___RAN+Core____|___GGSN__| | |||
| |_____Un-managed sub-path_____|____Managed sub-path_____| | |_____Un-managed sub-path_____|____Managed sub-path_____| | |||
| skipping to change at page 10, line 39 ¶ | skipping to change at page 11, line 31 ¶ | |||
| access point and this is the only networking device in the home | access point and this is the only networking device in the home | |||
| network, all endpoints attach directly to the CPE though the WiFi | network, all endpoints attach directly to the CPE though the WiFi | |||
| access. | access. | |||
| We believe this is a fairly common configuration in some parts of the | We believe this is a fairly common configuration in some parts of the | |||
| world and fairly simple as well. | world and fairly simple as well. | |||
| This case would map into the defined reference measurement points as | This case would map into the defined reference measurement points as | |||
| follows: | follows: | |||
| Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit | Subsc. -- Private -- Private -- Service-- Intra IP -- GRA -- Transit ... | |||
| device Net #1 Net #2 Demarc. Access GW GRA GW | device Net #1 Net #2 Demarc. Access GW GRA GW | |||
| mp000 mp100 mp150 mp190 mp200 | mp000 mp100 mp150 mp190 mp200 | |||
| |--UE--|------------CPE/NAT--------|------|-BRAS-|------| | |--UE--|------------CPE/NAT--------|------|-BRAS-|------| | |||
| |------DSL Network---| | |------DSL Network---| | |||
| |_______Un-managed sub-path________|__Managed sub-path__| | |_______Un-managed sub-path________|__Managed sub-path__| | |||
| GRA = Globally Routable Address, GW = Gateway, BRAS = Broadband | GRA = Globally Routable Address, GW = Gateway, BRAS = Broadband | |||
| Remote Acess Server | Remote Access Server | |||
| Consider next another access network case where: | Consider next another access network case where: | |||
| o The Customer Premises Equipment (CPE) is a NAT device that is | o The Customer Premises Equipment (CPE) is a NAT device that is | |||
| configured with a private IP address. | configured with a private IP address. | |||
| o There is a Carrier Grade NAT (CGN) located deep in the Access ISP | o There is a Carrier Grade NAT (CGN) located deep in the Access ISP | |||
| network. | network. | |||
| o The CPE is a home router that has also an incorporated a WiFi | 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 | access point and this is the only networking device in the home | |||
| network, all endpoints attach directly to the CPE though the WiFi | network, all endpoints attach directly to the CPE though the WiFi | |||
| access. | access. | |||
| We believe this is becoming a fairly common configuration in some | We believe this is becoming a fairly common configuration in some | |||
| parts of the world. | parts of the world. | |||
| This case would map into the defined reference measurement points as | This case would map into the defined reference measurement points as | |||
| follows: | follows: | |||
| Subsc. -- Private ------------- Service-- Intra IP -- GRA -- Transit | Subsc. -- Private ------------- Service-- Intra IP -- GRA -- Transit ... | |||
| device Net #1 Demarc. Access GW GRA GW | device Net #1 Demarc. Access GW GRA GW | |||
| mp000 mp100 mp150 mp190 mp200 | mp000 mp100 mp150 mp190 mp200 | |||
| |--UE--|------------CPE/NAT--------|------|-CGN-|------| | |--UE--|------------CPE/NAT--------|------|-CGN-|------| | |||
| |--Access Network---| | |--Access Network---| | |||
| |_______Un-managed sub-path________|_Managed sub-path__| | |_______Un-managed sub-path________|_Managed sub-path__| | |||
| GRA = Globally Routable Address, GW = Gateway | GRA = Globally Routable Address, GW = Gateway | |||
| 7. Example Resource Transition | 7. Example Resource Transition | |||
| This section gives an example of Shared and Dedicated portions with | This section gives an example of Shared and Dedicated portions with | |||
| the reference path. This example shows two Resource Transition | the reference path. This example shows two Resource Transition | |||
| Points. | Points. | |||
| Consider the case where: | Consider the case where: | |||
| skipping to change at page 12, line 16 ¶ | skipping to change at page 13, line 8 ¶ | |||
| upon reaching the Carrier Grade NAT (CGN), thus there is a | upon reaching the Carrier Grade NAT (CGN), thus there is a | |||
| Resource Transition Point and further network components are | Resource Transition Point and further network components are | |||
| designated as Shared Resources. | designated as Shared Resources. | |||
| We believe this is a fairly common configuration in parts of the | We believe this is a fairly common configuration in parts of the | |||
| world. | world. | |||
| This case would map into the defined reference measurement points as | This case would map into the defined reference measurement points as | |||
| follows: | follows: | |||
| Subsc. -- Private -- Private -- Access -- Intra IP -- GRA -- Transit | Subsc. -- Private -- Private -- Access -- Intra IP -- GRA -- Transit ... | |||
| device Net #1 Net #2 Demarc. Access GW GRA GW | device Net #1 Net #2 Demarc. Access GW GRA GW | |||
| mp000 mp100 mp150 mp190 mp200 | mp000 mp100 mp150 mp190 mp200 | |||
| |--UE--|------------CPE/NAT--------|------|-CGN-|------| | |--UE--|------------CPE/NAT--------|------|-CGN-|------| | |||
| | Wi-Fi | 1000Base-T |--Access Network---| | | Wi-Fi | 1000Base-T |--Access Network---| | |||
| |-Shared--|RT|------Dedicated------| RT |-----Shared------... | |-Shared--|RT|------Dedicated------| RT |-----Shared------... | |||
| |_______Un-managed sub-path________|_Managed sub-path__| | |_______Un-managed sub-path________|_Managed sub-path__| | |||
| GRA = Globally Routable Address, GW = Gateway, RT = Resource | GRA = Globally Routable Address, GW = Gateway, RT = Resource | |||
| Transition Point | Transition Point | |||
| 8. Security considerations | 8. Security considerations | |||
| Specification of a Reference Path and identification of measurement | Specification of a Reference Path and identification of measurement | |||
| points on the path represent agreements among interested parties, and | points on the path represent agreements among interested parties, and | |||
| they present no threat to the readers of this memo or to the Internet | they present no threat to the readers of this memo or to the Internet | |||
| itself. | itself. | |||
| skipping to change at page 13, line 34 ¶ | skipping to change at page 14, line 21 ¶ | |||
| [RFC5835] Morton, A. and S. Van den Berghe, "Framework for Metric | [RFC5835] Morton, A. and S. Van den Berghe, "Framework for Metric | |||
| Composition", RFC 5835, April 2010. | Composition", RFC 5835, April 2010. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [I-D.ietf-lmap-framework] | [I-D.ietf-lmap-framework] | |||
| Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., | Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., | |||
| Aitken, P., and A. Akhter, "A framework for large-scale | Aitken, P., and A. Akhter, "A framework for large-scale | |||
| measurement platforms (LMAP)", draft-ietf-lmap- | measurement platforms (LMAP)", draft-ietf-lmap- | |||
| framework-06 (work in progress), June 2014. | framework-07 (work in progress), June 2014. | |||
| [SK] Crawford, Sam., "Test Methodology White Paper", SamKnows | [SK] Crawford, Sam., "Test Methodology White Paper", SamKnows | |||
| Whitebox Briefing Note | Whitebox Briefing Note | |||
| http://www.samknows.com/broadband/index.php, July 2011. | http://www.samknows.com/broadband/index.php, July 2011. | |||
| [Q1741] Q.1741.7, , "IMT-2000 references to Release 9 of GSM- | [Q1741] Q.1741.7, , "IMT-2000 references to Release 9 of GSM- | |||
| evolved UMTS core network", | evolved UMTS core network", | |||
| http://www.itu.int/rec/T-REC-Q.1741.7/en, November 2011. | http://www.itu.int/rec/T-REC-Q.1741.7/en, November 2011. | |||
| Authors' Addresses | Authors' Addresses | |||
| End of changes. 28 change blocks. | ||||
| 78 lines changed or deleted | 108 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||