draft-ietf-lmap-framework-13.txt   draft-ietf-lmap-framework-14.txt 
Network Working Group P. Eardley Network Working Group P. Eardley
Internet-Draft BT Internet-Draft BT
Intended status: Informational A. Morton Intended status: Informational A. Morton
Expires: October 18, 2015 AT&T Labs Expires: October 31, 2015 AT&T Labs
M. Bagnulo M. Bagnulo
UC3M UC3M
T. Burbridge T. Burbridge
BT BT
P. Aitken P. Aitken
Brocade Brocade
A. Akhter A. Akhter
Consultant Consultant
April 16, 2015 April 29, 2015
A framework for Large-Scale Measurement of Broadband Performance (LMAP) A framework for Large-Scale Measurement of Broadband Performance (LMAP)
draft-ietf-lmap-framework-13 draft-ietf-lmap-framework-14
Abstract Abstract
Measuring broadband service on a large scale requires a description Measuring broadband service on a large scale requires a description
of the logical architecture and standardisation of the key protocols of the logical architecture and standardisation of the key protocols
that coordinate interactions between the components. The document that coordinate interactions between the components. The document
presents an overall framework for large-scale measurements. It also presents an overall framework for large-scale measurements. It also
defines terminology for LMAP (Large-Scale Measurement of Broadband defines terminology for LMAP (Large-Scale Measurement of Broadband
Performance). Performance).
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 October 18, 2015. This Internet-Draft will expire on October 31, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Outline of an LMAP-based measurement system . . . . . . . . . 5 2. Outline of an LMAP-based measurement system . . . . . . . . . 5
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Constraints . . . . . . . . . . . . . . . . . . . . . . . . . 12 4. Constraints . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. The measurement system is under the direction of a single 4.1. The measurement system is under the direction of a single
organisation . . . . . . . . . . . . . . . . . . . . . . 13 organisation . . . . . . . . . . . . . . . . . . . . . . 13
4.2. Each MA may only have a single Controller at any point in 4.2. Each MA may only have a single Controller at any point in
time . . . . . . . . . . . . . . . . . . . . . . . . . . 13 time . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . 13 5. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Bootstrapping process . . . . . . . . . . . . . . . . . . 14 5.1. Bootstrapping process . . . . . . . . . . . . . . . . . . 14
5.2. Control Protocol . . . . . . . . . . . . . . . . . . . . 15 5.2. Control Protocol . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 3, line 45 skipping to change at page 3, line 45
11.3. From -02 to -03 . . . . . . . . . . . . . . . . . . . . 52 11.3. From -02 to -03 . . . . . . . . . . . . . . . . . . . . 52
11.4. From -03 to -04 . . . . . . . . . . . . . . . . . . . . 52 11.4. From -03 to -04 . . . . . . . . . . . . . . . . . . . . 52
11.5. From -04 to -05 . . . . . . . . . . . . . . . . . . . . 53 11.5. From -04 to -05 . . . . . . . . . . . . . . . . . . . . 53
11.6. From -05 to -06 . . . . . . . . . . . . . . . . . . . . 54 11.6. From -05 to -06 . . . . . . . . . . . . . . . . . . . . 54
11.7. From -06 to -07 . . . . . . . . . . . . . . . . . . . . 54 11.7. From -06 to -07 . . . . . . . . . . . . . . . . . . . . 54
11.8. From -07 to -08 . . . . . . . . . . . . . . . . . . . . 54 11.8. From -07 to -08 . . . . . . . . . . . . . . . . . . . . 54
11.9. From -08 to -09 . . . . . . . . . . . . . . . . . . . . 55 11.9. From -08 to -09 . . . . . . . . . . . . . . . . . . . . 55
11.10. From -09 to -10 . . . . . . . . . . . . . . . . . . . . 55 11.10. From -09 to -10 . . . . . . . . . . . . . . . . . . . . 55
11.11. From -10 to -11 . . . . . . . . . . . . . . . . . . . . 55 11.11. From -10 to -11 . . . . . . . . . . . . . . . . . . . . 55
11.12. From -11 to -12 . . . . . . . . . . . . . . . . . . . . 55 11.12. From -11 to -12 . . . . . . . . . . . . . . . . . . . . 55
11.13. From -12 to -13 . . . . . . . . . . . . . . . . . . . . 55
11.14. From -13 to -14 . . . . . . . . . . . . . . . . . . . . 55
12. Informative References . . . . . . . . . . . . . . . . . . . 55 12. Informative References . . . . . . . . . . . . . . . . . . . 55
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57
1. Introduction 1. Introduction
There is a desire to be able to coordinate the execution of broadband There is a desire to be able to coordinate the execution of broadband
measurements and the collection of measurement results across a large measurements and the collection of measurement results across a large
scale set of Measurement Agents (MAs). These MAs could be software scale set of Measurement Agents (MAs). These MAs could be software
based agents on PCs, embedded agents in consumer devices (such as TVs based agents on PCs, embedded agents in consumer devices (such as TVs
or gaming consoles), embedded in service provider controlled devices or gaming consoles), embedded in service provider controlled devices
skipping to change at page 9, line 5 skipping to change at page 9, line 5
that they can easily be accessed by the data analysis tools. that they can easily be accessed by the data analysis tools.
The data analysis tools receive the results from the Collector or via The data analysis tools receive the results from the Collector or via
the Results repository. They might visualise the data or identify the Results repository. They might visualise the data or identify
which component or link is likely to be the cause of a fault or which component or link is likely to be the cause of a fault or
degradation. This information could help the Controller decide what degradation. This information could help the Controller decide what
follow-up Measurement Task to perform in order to diagnose a fault. follow-up Measurement Task to perform in order to diagnose a fault.
The data analysis tools also need to understand the Subscriber's The data analysis tools also need to understand the Subscriber's
service information, for example the broadband contract. service information, for example the broadband contract.
+-----------+ +-----------+ ^ +--------+ +-----------+ +-----------+ ^
| | | | | |End user| | | Observed | End user | |
| End user | | End user | | | |<-----|-----------|---traffic--->| | |
| | | | Non-LMAP | | | | flow | | |
+-----------+ +-----------+ Scope | | | | | | Non-LMAP
^ Observed ^ ^ | | | | | Measurement | | Scope
\ traffic flow +-------------+ / / | | | | |<--traffic--->| | |
\...............|.............|..../ / Measurement | +--------+ | | +-----------+ |
| Measurement |......../ traffic v .............|...........|.................................V
| Agent | ^ <MP> |Measurement| <MP> ^
+----------------->| | | |Agent: | |
| +-------------+ | |LMAP | |
| ^ | | +----------->|interface | |
| Instruction | | Report | | +-----------+ |
| (over Control | | (over Report Channel) | | ^ | LMAP
| Channel) | +---------------+ | | Instruction | | Report Scope
| | | | | (over Control | | (over Report Channel) |
| | | | | Channel) | +-----------------------+ |
| | v LMAP | | | |
| +------------+ +------------+ Scope | | | |
| | Controller | | Collector | | | | v |
| +------------+ +------------+ v | +------------+ +------------+ |
| ^ ^ | ^ | | Controller | | Collector | |
| | | | | | +------------+ +------------+ v
| | +-------+ | | | ^ ^ | ^
| | | v | | | | | |
+------------+ +----------+ +--------+ +----------+ | | | +--------+ | |
|Bootstrapper| |Subscriber|--->| data |<---| Results | Non- | | | v |
+------------+ |parameter | |analysis| |repository| LMAP +------------+ +----------+ +--------+ +----------+ |
|database | | tools | +----------+ Scope |Bootstrapper| |Subscriber|--->| data |<---| Results | Non-
+----------+ +--------+ | +------------+ |parameter | |analysis| |repository| LMAP
| |database | | tools | +----------+ Scope
v +----------+ +--------+ |
|
v
Schematic of main elements of an LMAP-based Measurement System Schematic of main elements of an LMAP-based Measurement System
(showing the elements in and out of the scope of initial LMAP work) (showing the elements in and out of the scope of initial LMAP work)
3. Terminology 3. Terminology
This section defines terminology for LMAP. Please note that defined This section defines terminology for LMAP. Please note that defined
terms are capitalized. terms are capitalized.
Bootstrap: A process that integrates a Measurement Agent into a Bootstrap: A process that integrates a Measurement Agent into a
Measurement System. Measurement System.
Capabilities: Information about the performance measurement Capabilities: Information about the performance measurement
skipping to change at page 55, line 22 skipping to change at page 55, line 22
o More changes from the AD review (Benoit Claise). o More changes from the AD review (Benoit Claise).
11.11. From -10 to -11 11.11. From -10 to -11
o More changes from the AD review (Benoit Claise). o More changes from the AD review (Benoit Claise).
11.12. From -11 to -12 11.12. From -11 to -12
o Fixing nits from IETF Last call and authors. o Fixing nits from IETF Last call and authors.
11.13. From -12 to -13
o IESG changes.
11.14. From -13 to -14
o Fixing Figure 1.
12. Informative References 12. Informative References
[Bur10] Burkhart, M., Schatzmann, D., Trammell, B., and E. Boschi, [Bur10] Burkhart, M., Schatzmann, D., Trammell, B., and E. Boschi,
"The Role of Network Trace anonymisation Under Attack", "The Role of Network Trace anonymisation Under Attack",
January 2010. January 2010.
[TR-069] TR-069, , "CPE WAN Management Protocol", [TR-069] TR-069, , "CPE WAN Management Protocol",
http://www.broadband-forum.org/technical/trlist.php, http://www.broadband-forum.org/technical/trlist.php,
November 2013. November 2013.
 End of changes. 9 change blocks. 
40 lines changed or deleted 52 lines changed or added

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