draft-ietf-ippm-lmap-path-00.txt   draft-ietf-ippm-lmap-path-01.txt 
Network Working Group M. Bagnulo Network Working Group M. Bagnulo
Internet-Draft UC3M Internet-Draft UC3M
Intended status: Standards Track T. Burbridge Intended status: Standards Track T. Burbridge
Expires: January 09, 2014 BT Expires: March 28, 2014 BT
S. Crawford S. Crawford
SamKnows SamKnows
P. Eardley P. Eardley
BT BT
A. Morton A. Morton
AT&T Labs AT&T Labs
July 08, 2013 September 24, 2013
A Reference Path and Measurement Points for LMAP A Reference Path and Measurement Points for LMAP
draft-ietf-ippm-lmap-path-00 draft-ietf-ippm-lmap-path-01
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. commonly used performance metrics.
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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 January 09, 2014. This Internet-Draft will expire on March 28, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 23 skipping to change at page 2, line 23
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3
3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 3 3. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 3
3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 3 3.1. Reference Path . . . . . . . . . . . . . . . . . . . . . 3
3.2. Subscriber . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Subscriber . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . 4
4. Reference Path . . . . . . . . . . . . . . . . . . . . . . . 4 4. Reference Path . . . . . . . . . . . . . . . . . . . . . . . 4
5. Measurement Points . . . . . . . . . . . . . . . . . . . . . 6 5. Measurement Points . . . . . . . . . . . . . . . . . . . . . 6
6. Translation Between Ref. Path and Tech. X . . . . . . . . . . 7 6. Translation Between Ref. Path and Tech. X . . . . . . . . . . 7
7. Security considerations . . . . . . . . . . . . . . . . . . . 9 7. Example Resource Transition . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8. Security considerations . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . 9 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . 10 11.1. Normative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 11.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
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). The series of IP Performance Broadband Access Performance (LMAP). The series of IP Performance
Metrics (IPPM) RFCs have developed terms that are generally useful Metrics (IPPM) RFCs have developed terms that are generally useful
for path description (section 5 of [RFC2330]). There are a limited for path description (section 5 of [RFC2330]). There are a limited
number of additional terms needing definition here, and they will be number of additional terms needing definition here, and they will be
defined in this memo. defined in this memo.
skipping to change at page 4, line 4 skipping to change at page 4, line 4
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 possessing one or more hosts participating in an Internet An entity (associated with one or more users) that is engaged in a
access service. subscription with a service provider. The subscriber is allowed to
subscribe and un-subscribe services, and to register a user or a list
of users authorized to enjoy these services. [Q1741] Both the
subscriber and service provider are allowed to set the limits
relative to the use that associated users make of subscribed
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
translation, and others. A Dedicated component can affect the translation, and others. A Dedicated component can affect the
performance of the Reference Path, or the performance of any sub-path performance of the Reference Path, or the performance of any sub-path
where the component is involved. where the component is involved.
skipping to change at page 9, line 9 skipping to change at page 9, line 21
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-|------|
|---Access Network--| |---Access Network--|
GRA = Globally Routable Address, GW = Gateway GRA = Globally Routable Address, GW = Gateway
7. Security considerations 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.
Consider the case where:
o The CPE is wired Residential GW and modem (Private Net#2)
connected to a WiFi access point (Private Net#1). The Subscriber
device (UE) attachs to the CPE though the WiFi access.
o The Wi-Fi subnetwork (Private Net#1) shares unliscened radio
channel resources with other W-Fi access networks (and potentially
other sources of interference), thus this is a Shared portion of
the path.
o The wired subnetwork (Private Net#2) and a portion of the Access
Network are Dedicated Resources (for a single Subscriber), thus
there is a Resource Transition Point between (Private Net#1) and
(Private Net#2).
o Subscriber traffic shares common resources with other subscribers
upon reaching the Carrier Grade NAT (CGN), thus there is a
Resource Transition Point and further network components are
designated as Shared Resources.
We believe is becoming 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 wired |---Access Network--|
|-Shared--|RT|------Dedicated------| RT |-----Shared------...
GRA = Globally Routable Address, GW = Gateway, RT = Resource
Transition Point
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.
8. IANA Considerations 9. IANA Considerations
TBD TBD
9. Acknowledgements 10. Acknowledgements
Thanks to Matt Mathis for review and comments. Thanks to Matt Mathis for review and comments.
10. References 11. References
10.1. Normative References 11.1. Normative References
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis, [RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
"Framework for IP Performance Metrics", RFC 2330, May "Framework for IP Performance Metrics", RFC 2330, May
1998. 1998.
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network [RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
performance measurement with periodic streams", RFC 3432, performance measurement with periodic streams", RFC 3432,
November 2002. November 2002.
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip
skipping to change at page 10, line 18 skipping to change at page 11, line 28
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393, Metric for IP Performance Metrics (IPPM)", RFC 3393,
November 2002. November 2002.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
[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.
10.2. Informative References 11.2. Informative References
[RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics [RFC4148] Stephan, E., "IP Performance Metrics (IPPM) Metrics
Registry", BCP 108, RFC 4148, August 2005. Registry", BCP 108, RFC 4148, August 2005.
[RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics [RFC6248] Morton, A., "RFC 4148 and the IP Performance Metrics
(IPPM) Registry of Metrics Are Obsolete", RFC 6248, April (IPPM) Registry of Metrics Are Obsolete", RFC 6248, April
2011. 2011.
[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.
Authors' Addresses [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
Marcelo Bagnulo Marcelo Bagnulo
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad 30 Av. Universidad 30
Leganes, Madrid 28911 Leganes, Madrid 28911
SPAIN SPAIN
Phone: 34 91 6249500 Phone: 34 91 6249500
Email: marcelo@it.uc3m.es Email: marcelo@it.uc3m.es
URI: http://www.it.uc3m.es URI: http://www.it.uc3m.es
 End of changes. 14 change blocks. 
20 lines changed or deleted 73 lines changed or added

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