< draft-ietf-ippm-lmap-path-01.txt		draft-ietf-ippm-lmap-path-02.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: March 28, 2014 BT		Expires: August 17, 2014 BT
	S. Crawford		S. Crawford
	SamKnows		SamKnows
	P. Eardley		P. Eardley
	BT		BT
	A. Morton		A. Morton
	AT&T Labs		AT&T Labs
	September 24, 2013		February 13, 2014
	A Reference Path and Measurement Points for LMAP		A Reference Path and Measurement Points for LMAP
	draft-ietf-ippm-lmap-path-01		draft-ietf-ippm-lmap-path-02
	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 March 28, 2014.		This Internet-Draft will expire on August 17, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 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
	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 . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	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 . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 4
			3.6. Managed and Un-Managed Sub-paths . . . . . . . . . . . . 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 . . . . . . . . . . 8
	7. Example Resource Transition . . . . . . . . . . . . . . . . . 9		7. Example Resource Transition . . . . . . . . . . . . . . . . . 9
	8. Security considerations . . . . . . . . . . . . . . . . . . . 10		8. Security considerations . . . . . . . . . . . . . . . . . . . 10
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10		10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	11.1. Normative References . . . . . . . . . . . . . . . . . . 10		11.1. Normative References . . . . . . . . . . . . . . . . . . 10
	11.2. Informative References . . . . . . . . . . . . . . . . . 11		11.2. Informative References . . . . . . . . . . . . . . . . . 11
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
	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 34 ¶		skipping to change at page 4, line 37 ¶
	A component on the Reference Path is designated a Shared component		A component on the Reference Path is designated a Shared component
	when the traffic associated with multiple Subscribers is served by		when the traffic associated with multiple Subscribers is served by
	common resources.		common resources.
	3.5. Resource Transition Point		3.5. Resource Transition Point
	A point between Dedicated and Shared components on a Reference Path		A point between Dedicated and Shared components on a Reference Path
	that may be a point of significance, and is identified as a		that may be a point of significance, and is identified as a
	transition between two types of resources.		transition between two types of resources.
			3.6. Managed and Un-Managed Sub-paths
			Service providers are responsible for the portion of the path they
			manage. However, most paths involve a sub-path which is beyond the
			management of the subscriber's service provider. This means that
			private networks, wireless networks using unlicensed frequencies, and
			the networks of other service are designated as un-managed sub-paths.
			The Access demarcation point always divides managed and un-managed
			sub-paths.
	4. Reference Path		4. Reference Path
	This section defines a reference path for Internet Access.		This section defines a reference path for Internet Access.
	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
	... 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
	skipping to change at page 7, line 9 ¶		skipping to change at page 7, line 24 ¶
	o Widely deployed broadband access measurements have used pass-		o Widely deployed broadband access measurements have used pass-
	through devices[SK] (at the subscriber's location) directly		through devices[SK] (at the subscriber's location) directly
	connected to the service demarcation point: this would be located		connected to the service demarcation point: this would be located
	at mp100.		at mp100.
	o The networking technology used at all measurement points must be		o The networking technology used at all measurement points must be
	indicated, especially the interface standard and configured speed.		indicated, especially the interface standard and configured speed.
	o If it can be shown that a link connecting to a measurement point		o If it can be shown that a link connecting to a measurement point
	has reliably deterministic or negilgible performance, then the		has reliably deterministic or negligible performance, then the
	remote end of the connecting link is an equivalent point for some		remote end of the connecting link is an equivalent point for some
	methods of measurement (To Be Specified Elsewhere). In any case,		methods of measurement (To Be Specified Elsewhere). In any case,
	the presence of such a link must be reported.		the presence of such a link must be reported.
	o Many access network architectures have a traffic aggregation point		o Many access network architectures have a traffic aggregation point
	(e.g., CMTS or DSLAM) between mp100 and mp150. We designate this		(e.g., CMTS or DSLAM) between mp100 and mp150. We designate this
	point mp120, but it won't currently fit in the figure.		point mp120, but it won't currently fit in the figure.
	o A Carrier Grade NAT (CGN) deployed in the Subscriber's access		o A Carrier Grade NAT (CGN) deployed in the Subscriber's access
	network would be positioned between mp100 and mp190, and the		network would be positioned between mp100 and mp190, and the
	skipping to change at page 8, line 10 ¶		skipping to change at page 8, line 18 ¶
	exact mapping between particular network technologies and the		exact mapping between particular network technologies and the
	reference path.		reference path.
	We provide an example for 3G Cellular access below.		We provide an example for 3G Cellular access below.
	Subscriber -- Private -- Access Srvc ----------- GRA --- Transit ...		Subscriber -- Private -- Access Srvc ----------- 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_____|
	GRA = Globally Routable Address, GW = Gateway, UE = User Equipment,		GRA = Globally Routable Address, GW = Gateway, UE = User Equipment,
	RAN = Radio Access Network, GGSN = Gateway GPRS Support Node.		RAN = Radio Access Network, GGSN = Gateway GPRS Support Node.
	We next provide a few examples of DSL access. Consider first the		We next provide a few examples of DSL access. Consider first the
	case where:		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 public IP address.		configured with a public IP address.
	skipping to change at page 8, line 36 ¶		skipping to change at page 8, line 45 ¶
	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 -- 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--------|-------|BRAS-|------|		|--UE--|------------CPE/NAT--------|-------|BRAS-|------|
	|----Access Network--|		|----Access Network--|
			|_______Un-managed sub-path________|__Managed sub-path__|
	GRA = Globally Routable Address, GW = Gateway		GRA = Globally Routable Address, GW = Gateway
	Consider next the case where:		Consider next the 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 into the Access		o There is a Carrier Grade NAT (CGN) located deep into the Access
	ISP network.		ISP network.
	skipping to change at page 9, line 18 ¶		skipping to change at page 9, line 27 ¶
	the world.		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 -- 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--|
			|_______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:
	o The CPE is wired Residential GW and modem (Private Net#2)		o The CPE is wired Residential GW and modem (Private Net#2)
	connected to a WiFi access point (Private Net#1). The Subscriber		connected to a WiFi access point (Private Net#1). The Subscriber
	device (UE) attachs to the CPE though the WiFi access.		device (UE) attaches to the CPE though the WiFi access.
	o The Wi-Fi subnetwork (Private Net#1) shares unliscened radio		o The Wi-Fi subnetwork (Private Net#1) shares unlicensed radio
	channel resources with other W-Fi access networks (and potentially		channel resources with other W-Fi access networks (and potentially
	other sources of interference), thus this is a Shared portion of		other sources of interference), thus this is a Shared portion of
	the path.		the path.
	o The wired subnetwork (Private Net#2) and a portion of the Access		o The wired subnetwork (Private Net#2) and a portion of the Access
	Network are Dedicated Resources (for a single Subscriber), thus		Network are Dedicated Resources (for a single Subscriber), thus
	there is a Resource Transition Point between (Private Net#1) and		there is a Resource Transition Point between (Private Net#1) and
	(Private Net#2).		(Private Net#2).
	o Subscriber traffic shares common resources with other subscribers		o Subscriber traffic shares common resources with other subscribers
	skipping to change at page 10, line 15 ¶		skipping to change at page 10, line 23 ¶
	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 wired |---Access Network--|		Wi-Fi wired |---Access Network--|
	|-Shared--|RT|------Dedicated------| RT |-----Shared------...		|-Shared--|RT|------Dedicated------| RT |-----Shared------...
			|_______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 11, line 41 ¶		skipping to change at page 12, line 5 ¶
	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.
	[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
	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. 19 change blocks.
	12 lines changed or deleted		28 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/