< draft-svshah-tsvwg-lln-diffserv-recommendations-02.txt		draft-svshah-tsvwg-lln-diffserv-recommendations-03.txt >
	Network Working Group S. Shah		Network Working Group S. Shah
	Internet-Draft P. Thubert		Internet-Draft P. Thubert
	Intended status: Informational Cisco Systems		Intended status: Informational Cisco Systems
	Expires: August 15, 2014 February 11, 2014		Expires: February 15, 2015 August 14, 2014
	Differentiated Service Class Recommendations for LLN Traffic		Differentiated Service Class Recommendations for LLN Traffic
	draft-svshah-tsvwg-lln-diffserv-recommendations-02		draft-svshah-tsvwg-lln-diffserv-recommendations-03
	Abstract		Abstract
	Differentiated services architecture is widely deployed in		Differentiated services architecture is widely deployed in
	traditional networks. There exist well defined recommendations for		traditional networks. There exist well defined recommendations for
	the use of appropriate differentiated service classes for different		the use of appropriate differentiated service classes for different
	types of traffic (eg. audio, video) in these networks. Per-Hop		types of traffic (eg. audio, video) in these networks. Per-Hop
	Behaviors are typically defined based on this recommendations. With		Behaviors are typically defined based on this recommendations. With
	emerging Low-power and Lossy Networks (LLNs), it is important to have		emerging Low-power and Lossy Networks (LLNs), it is important to have
	similar defined differentiated services recommendations for LLN		similar defined differentiated services recommendations for LLN
	traffic. Defined recommendations are for LLN class of traffic		traffic. Defined recommendations are for LLN class of traffic
	exiting out of LLNs towards high-speed backbones, converged campus		exiting out of LLNs towards high-speed backbones, converged campus
	network and for the traffic in the reverse direction.		network and for the traffic in the reverse direction.
	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 August 15, 2014.		This Internet-Draft will expire on February 15, 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 3, line 7 ¶		skipping to change at page 2, line 24 ¶
	modifications of such material outside the IETF Standards Process.		modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling		Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified		the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may		outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5		1.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Application Types and Traffic Patterns . . . . . . . . . . . . 6		3. Application Types and Traffic Patterns . . . . . . . . . . . 5
	3.1. Alert signals . . . . . . . . . . . . . . . . . . . . . . 6		3.1. Alert signals . . . . . . . . . . . . . . . . . . . . . . 5
	3.2. Control signals . . . . . . . . . . . . . . . . . . . . . 7		3.2. Control signals . . . . . . . . . . . . . . . . . . . . . 6
	3.2.1. Deterministic control signals . . . . . . . . . . . . 7		3.2.1. Deterministic control signals . . . . . . . . . . . . 6
	3.3. Monitoring data . . . . . . . . . . . . . . . . . . . . . 8		3.3. Monitoring data . . . . . . . . . . . . . . . . . . . . . 7
	3.3.1. Video data . . . . . . . . . . . . . . . . . . . . . . 8		3.3.1. Video data . . . . . . . . . . . . . . . . . . . . . 7
	3.3.2. Query based data . . . . . . . . . . . . . . . . . . . 8		3.3.2. Query based data . . . . . . . . . . . . . . . . . . 7
	3.3.3. Periodic reporting/logging, Software downloads . . . . 8		3.3.3. Periodic reporting/logging, Software downloads . . . 8
	3.4. Traffic Class Characteristics Table . . . . . . . . . . . 10		3.4. Traffic Class Characteristics Table . . . . . . . . . . . 8
	4. Differentiated Service recommendations for LLN traffic . . . . 10		4. Differentiated Service recommendations for LLN traffic . . . 9
	4.1. Alert signals . . . . . . . . . . . . . . . . . . . . . . 10		4.1. Alert signals . . . . . . . . . . . . . . . . . . . . . . 9
	4.2. Control signals . . . . . . . . . . . . . . . . . . . . . 11		4.2. Control signals . . . . . . . . . . . . . . . . . . . . . 10
	4.2.1. Deterministic Control Signals . . . . . . . . . . . . 11		4.2.1. Deterministic Control Signals . . . . . . . . . . . . 10
	4.3. Monitoring Data . . . . . . . . . . . . . . . . . . . . . 11		4.3. Monitoring Data . . . . . . . . . . . . . . . . . . . . . 10
	4.3.1. Video Data . . . . . . . . . . . . . . . . . . . . . . 11		4.3.1. Video Data . . . . . . . . . . . . . . . . . . . . . 10
	4.3.2. Query based data . . . . . . . . . . . . . . . . . . . 11		4.3.2. Query based data . . . . . . . . . . . . . . . . . . 10
	4.3.3. Periodic reporting/logging, Software downloads . . . . 11		4.3.3. Periodic reporting/logging, Software downloads . . . 10
	4.4. Summary of Differentiated Code-points and QoS		4.4. Summary of Differentiated Code-points and QoS Mechanics
	Mechanics for them . . . . . . . . . . . . . . . . . . . . 12		for them . . . . . . . . . . . . . . . . . . . . . . . . 10
	5. Deployment Scenario . . . . . . . . . . . . . . . . . . . . . 12		5. Deployment Scenario . . . . . . . . . . . . . . . . . . . . . 11
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 14		6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 14		8.1. Normative References . . . . . . . . . . . . . . . . . . 13
	8.2. Informative References . . . . . . . . . . . . . . . . . . 15		8.2. Informative References . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	With emerging LLN applications, it is anticipated that more and more		With emerging LLN applications, it is anticipated that more and more
	LLNs will be federated by high-speed backbones, possibly supporting		LLNs will be federated by high-speed backbones, possibly supporting
	deterministic Ethernet service, and be further connected to some		deterministic Ethernet service, and be further connected to some
	converged campus networks for less demanding usages such as		converged campus networks for less demanding usages such as
	supervisory control like traffic originated in a LLN, such as		supervisory control like traffic originated in a LLN, such as
	metering, command and control, may transit over a converged campus IP		metering, command and control, may transit over a converged campus IP
	network.		network.
	skipping to change at page 11, line 20 ¶		skipping to change at page 10, line 20 ¶
	delay. Service requirement for later class of control signals is		delay. Service requirement for later class of control signals is
	very similar to service for signaling traffic in the traditional		very similar to service for signaling traffic in the traditional
	networks. Recommendation for this class of control signals is to use		networks. Recommendation for this class of control signals is to use
	Diffserv code-point CS5.		Diffserv code-point CS5.
	4.2.1. Deterministic Control Signals		4.2.1. Deterministic Control Signals
	PHB for this class of traffic is defined as forwarding of a packet at		PHB for this class of traffic is defined as forwarding of a packet at
	determined/scheduled time providing no jitter service.		determined/scheduled time providing no jitter service.
	Recommended DSCP code-point for this class of traffic is EF. Since		Recommended DSCP code-point for this class of traffic is DF [DF-PHB].
	this class of traffic is not expected to co-exist with voice like
	traffic, that implements EF code-point as used in traditional Campus
	and WAN networks, the same code-point is re-used here for the purpose
	of deterministic control signals. However, a note to be made for
	defined PHB for this code-point as deterministic forwarding behavior
	as defined in this document.
	Scheduling MUST pre-empt service of any other class of traffic during		Scheduling MUST pre-empt service of any other class of traffic during
	the scheduled time for this class of traffic.		the scheduled time for this class of traffic.
	4.3. Monitoring Data		4.3. Monitoring Data
	4.3.1. Video Data		4.3.1. Video Data
	RFC4594 has well documented recommendations for different types of		RFC4594 has well documented recommendations for different types of
	Video traffic. If there is any Video traffic from/to LLNs to/from		Video traffic. If there is any Video traffic from/to LLNs to/from
	outside of LLNs, they should use same recommended dscp from RFC4594.		outside of LLNs, they should use same recommended dscp from RFC4594.
	skipping to change at page 12, line 6 ¶		skipping to change at page 11, line 4 ¶
	periodic reporting/logging data that are critical to be reported with		periodic reporting/logging data that are critical to be reported with
	regular interval with relatively low jitter is recommended to use		regular interval with relatively low jitter is recommended to use
	AF2x service.		AF2x service.
	4.3.3. Periodic reporting/logging, Software downloads		4.3.3. Periodic reporting/logging, Software downloads
	Non-critical periodic reporting/logging and rest all other data MAY		Non-critical periodic reporting/logging and rest all other data MAY
	use AF1x or BE service class.		use AF1x or BE service class.
	4.4. Summary of Differentiated Code-points and QoS Mechanics for them		4.4. Summary of Differentiated Code-points and QoS Mechanics for them
	- Alert Signals CS5		- Alert Signals CS5
	- Control Signaling CS5		- Control Signaling CS5
	- Deterministic Control Signals EF		- Deterministic Control Signals DF
	- Video broadcast/feed CS3		- Video broadcast/feed CS3
	- Query-based data AF2x		- Query-based data AF2x
	- Assured monitoring data AF1x		- Assured monitoring data AF1x
	high throughput		high throughput
	- Best Effort monitoring data BE		- Best Effort monitoring data BE
	Reporting (periodic reporting.certain types of periodic monitoring		Reporting (periodic reporting.certain types of periodic monitoring
	MAY require assured forwarding)		MAY require assured forwarding)
	------------------------------------------------------------------		------------------------------------------------------------------
	| Service | DSCP | Conditioning at | PHB | Queuing| AQM|		| Service | DSCP | Conditioning at | PHB | Queuing| AQM|
	| Class | | DS Edge | Used | | |		| Class | | DS Edge | Used | | |
	|===============+======+===================+=========+========+====|		|===============+======+===================+=========+========+====|
	| Deterministic | EF | | |Time | No |		| Deterministic | DF | | |Time | No |
	|control signals| |Police using sr+bs | |Schedule| |		|control signals| |Police using sr+bs | |Schedule| |
	|---------------+------+-------------------+---------+--------+----|		|---------------+------+-------------------+---------+--------+----|
	|Alert signals/| | | | | |		|Alert signals/| | | | | |
	|Control signals| CS5 |Police using sr+bs | RFC2474 | Rate | No |		|Control signals| CS5 |Police using sr+bs | RFC2474 | Rate | No |
	|---------------+------+-------------------+---------+--------+----|		|---------------+------+-------------------+---------+--------+----|
	| Video feed | CS3 |Police using sr+bs | RFC2474 | Rate | No |		| Video feed | CS3 |Police using sr+bs | RFC2474 | Rate | No |
	|---------------+------+-------------------+---------+--------+----|		|---------------+------+-------------------+---------+--------+----|
	| Query- | AF21 | Using single-rate,| | | Yes|		| Query- | AF21 | Using single-rate,| | | Yes|
	| based | AF22 |three-color marker | RFC2597 | Rate | per|		| based | AF22 |three-color marker | RFC2597 | Rate | per|
	| Data | AF23 | (such as RFC 2697)| | |DSCP|		| Data | AF23 | (such as RFC 2697)| | |DSCP|
	skipping to change at page 13, line 40 ¶		skipping to change at page 12, line 40 ¶
	wireless network or a multihop network, unless tight mechanisms are		wireless network or a multihop network, unless tight mechanisms are
	put in place such as TDM and frequency hopping. Today this class of		put in place such as TDM and frequency hopping. Today this class of
	traffic is expected to use other tightly managed method outside of		traffic is expected to use other tightly managed method outside of
	IP networks. Excluding class 0 traffic, following table maps Class 1		IP networks. Excluding class 0 traffic, following table maps Class 1
	thru Class 5 service classes to Diffserv code-point.		thru Class 5 service classes to Diffserv code-point.
	-------------------------		-------------------------
	| Service | DSCP |		| Service | DSCP |
	| Class | |		| Class | |
	|===============+=========|		|===============+=========|
	| Class 1 | EF |		| Class 1 | DF |
	+-------------------------+		+-------------------------+
	| Class 2 | CS5 |		| Class 2 | CS5 |
	+-------------------------+		+-------------------------+
	| Class 3 | CS5 |		| Class 3 | CS5 |
	+-------------------------+		+-------------------------+
	| Class 4 | AF2x |		| Class 4 | AF2x |
	+-------------------------+		+-------------------------+
	| class 5 | AF1x/BE |		| class 5 | AF1x/BE |
	+-------------------------+		+-------------------------+
	skipping to change at page 14, line 31 ¶		skipping to change at page 13, line 31 ¶
	suggestions.		suggestions.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4594] Babiarz, J., Chan, K., and F. Baker, "Configuration		[RFC4594] Babiarz, J., Chan, K., and F. Baker, "Configuration
	Guidelines for DiffServ Service Classes", RFC 4594,		Guidelines for DiffServ Service Classes", RFC 4594, August
	August 2006.		2006.
	[RFC5127] Chan, K., Babiarz, J., and F. Baker, "Aggregation of		[RFC5127] Chan, K., Babiarz, J., and F. Baker, "Aggregation of
	Diffserv Service Classes", RFC 5127, February 2008.		Diffserv Service Classes", RFC 5127, February 2008.
	[RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,		[RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,
	"Routing Requirements for Urban Low-Power and Lossy		"Routing Requirements for Urban Low-Power and Lossy
	Networks", RFC 5548, May 2009.		Networks", RFC 5548, May 2009.
	[RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney,		[RFC5673] Pister, K., Thubert, P., Dwars, S., and T. Phinney,
	"Industrial Routing Requirements in Low-Power and Lossy		"Industrial Routing Requirements in Low-Power and Lossy
	Networks", RFC 5673, October 2009.		Networks", RFC 5673, October 2009.
	[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation		[RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation
	Routing Requirements in Low-Power and Lossy Networks",		Routing Requirements in Low-Power and Lossy Networks", RFC
	RFC 5826, April 2010.		5826, April 2010.
	[RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen,		[RFC5867] Martocci, J., De Mil, P., Riou, N., and W. Vermeylen,
	"Building Automation Routing Requirements in Low-Power and		"Building Automation Routing Requirements in Low-Power and
	Lossy Networks", RFC 5867, June 2010.		Lossy Networks", RFC 5867, June 2010.
			[DFPHB] Shah, S. and P. Thubert, "Deterministic Forwarding Per Hop
			Behavior, I-D.svshah-tsvwg-deterministic-forwarding",
			March 2014.
	8.2. Informative References		8.2. Informative References
	[ISA100.11a]		[ISA100.11a]
	ISA, "ISA-100.11a-2011 - Wireless systems for industrial		ISA, "ISA-100.11a-2011 - Wireless systems for industrial
	automation: Process control and related applications",		automation: Process control and related applications", May
	May 2011.		2011.
	[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,		[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
	"Definition of the Differentiated Services Field (DS		"Definition of the Differentiated Services Field (DS
	Field) in the IPv4 and IPv6 Headers", RFC 2474,		Field) in the IPv4 and IPv6 Headers", RFC 2474, December
	December 1998.		1998.
	[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,		[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,
	and W. Weiss, "An Architecture for Differentiated		and W. Weiss, "An Architecture for Differentiated
	Services", RFC 2475, December 1998.		Services", RFC 2475, December 1998.
	[RFC6272] Baker, F. and D. Meyer, "Internet Protocols for the Smart		[RFC6272] Baker, F. and D. Meyer, "Internet Protocols for the Smart
	Grid", RFC 6272, June 2011.		Grid", RFC 6272, June 2011.
	Authors' Addresses		Authors' Addresses
End of changes. 15 change blocks.
	53 lines changed or deleted		50 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/