< draft-svshah-tsvwg-deterministic-forwarding-02.txt		draft-svshah-tsvwg-deterministic-forwarding-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: March 7, 2015 September 03, 2014		Expires: September 2, 2015 March 01, 2015
	Deterministic Forwarding PHB		Deterministic Forwarding PHB
	draft-svshah-tsvwg-deterministic-forwarding-02		draft-svshah-tsvwg-deterministic-forwarding-03
	Abstract		Abstract
	This document defines a Differentiated Services Per-Hop-Behavior		This document defines a Differentiated Services Per-Hop-Behavior
	(PHB) Group called Deterministic Forwarding (DF). The document		(PHB) Group called Deterministic Forwarding (DF). The document
	describes the purpose and semantics of this PHB. It describes		describes the purpose and semantics of this PHB. It also describes
	creation and forwarding treatment of the service class. Also		creation and forwarding treatment of the service class. The document
	describes how the code-point can be mapped into one of the aggregated		also describes how the code-point can be mapped into one of the
	Diffserv service classes [RFC5127].		aggregated Diffserv service classes [RFC5127].
	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 March 7, 2015.		This Internet-Draft will expire on September 2, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 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
	skipping to change at page 2, line 21 ¶		skipping to change at page 2, line 20 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. DF Per Hop Behavior . . . . . . . . . . . . . . . . . . . . . 3		3. DF Per Hop Behavior . . . . . . . . . . . . . . . . . . . . . . 4
	4. Traffic Conditioning . . . . . . . . . . . . . . . . . . . . 4		4. Traffic Conditioning . . . . . . . . . . . . . . . . . . . . . 4
	5. Diffserv behavior through non-DF DS domain . . . . . . . . . 4		5. Diffserv behavior through non-DF DS domain . . . . . . . . . . 5
	6. Potential implementation of DF scheduling . . . . . . . . . . 5		6. Potential implementation of DF scheduling . . . . . . . . . . . 5
	7. Updates to RFC4594 and RFC5127 . . . . . . . . . . . . . . . 7		7. Updates to RFC4594 and RFC5127 . . . . . . . . . . . . . . . . 7
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 7		9. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
	10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	11.1. Normative References . . . . . . . . . . . . . . . . . . 7		11.1. Normative References . . . . . . . . . . . . . . . . . . . 8
	11.2. Informative References . . . . . . . . . . . . . . . . . 8		11.2. Informative References . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	There is a demand to provide deterministic forwarding to certain type		There is a demand to provide deterministic forwarding to certain type
	of traffic in machine to machine networks over IP. With an		of traffic in machine to machine networks over IP. With an
	introduction of machine to machine networks over IP, a new set of IP		introduction of machine to machine networks over IP, a new set of IP
	applications are emerging. Traffic types from such applications/		applications are emerging. Traffic types from such applications/
	networks are some-what different from the traditional traffic types.		networks are some-what different from the traditional traffic types.
	Though most traffic types have characteristics similar to that of		Though most traffic types have characteristics similar to that of
	traditional ones [LLN-DIFF], certain control signals for some of the		traditional ones [LLN-DIFF], certain control signals for some of the
	skipping to change at page 5, line 16 ¶		skipping to change at page 5, line 32 ¶
	Following are examples of potential implementations. They are not		Following are examples of potential implementations. They are not
	any form of guidelines or recommendations but simply a reference to		any form of guidelines or recommendations but simply a reference to
	potential implementations.		potential implementations.
	There are at least two ways to implement scheduling for DF traffic		There are at least two ways to implement scheduling for DF traffic
	class.		class.
	1) One queue to buffer and schedule all DF traffic (from all flows),		1) One queue to buffer and schedule all DF traffic (from all flows),
	2) Multiple queues for DF traffic class, one queue for each DF		2) Multiple sub-queues for DF traffic class, one queue for each DF
	provisioned micro-flow		provisioned flow
	Any chosen DF scheduling implementation MAY run Traffic Conditioning,		Any chosen DF scheduling implementation MUST run traffic conditioning
	as described in earlier section. Discussed more in later section.		at enqueue to decide if packets to be enqueued or discarded.
			Discussed more in later section.
	1) Single queue to buffer all DF traffic		1) Single queue to buffer all DF traffic
	This single queue maintains, possibly a circular, indexed buffer		This single queue maintains, possibly a circular, indexed buffer
	list. Each index logically maps to each scheduled time service. If		list. Each index logically maps to each scheduled time service. If
	conditioning results in not to discard a packet, packet gets en-		conditioning results in not to discard a packet, packet gets en-
	queued at a relevant index in the buffer list that maps to a relevant		queued at a relevant index in the buffer list that maps to a relevant
	scheduled time slot. If there is no packet(s) received for a		scheduled time slot. If there is no packet(s) received for a
	specific scheduled time service then buffer index for that scheduled		specific scheduled time service then buffer index for that scheduled
	service remains empty. This also means that during dequeue, at a		service remains empty. This also means that during dequeue, at a
	skipping to change at page 7, line 28 ¶		skipping to change at page 8, line 4 ¶
	There is no security considerations required besides ones already		There is no security considerations required besides ones already
	understood in the context of Differentiated services architecture		understood in the context of Differentiated services architecture
	10. Acknowledgements		10. Acknowledgements
	Fred Baker, Norm Finn, David Black, Brian Carpenter for their		Fred Baker, Norm Finn, David Black, Brian Carpenter for their
	comments and feed-back.		comments and feed-back.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[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, December		Field) in the IPv4 and IPv6 Headers", RFC 2474,
	1998.		December 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.
	[RFC2597] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski,
	"Assured Forwarding PHB Group", RFC 2597, June 1999.
	[RFC2598] Jacobson, V., Nichols, K., and K. Poduri, "An Expedited		[RFC2598] Jacobson, V., Nichols, K., and K. Poduri, "An Expedited
	Forwarding PHB", RFC 2598, June 1999.		Forwarding PHB", RFC 2598, June 1999.
	[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, August		Guidelines for DiffServ Service Classes", RFC 4594,
	2006.		August 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.
	11.2. Informative References		11.2. Informative References
	[TiSCH] Thubert, P., Watteyne, T., and R. Assimiti, "An		[TiSCH] Thubert, P., Watteyne, T., and R. Assimiti, "An
	Architecture for IPv6 over the TSCH mode of IEEE		Architecture for IPv6 over the TSCH mode of IEEE
	802.15.4e, I-D.draft-ietf-6tisch-architecture", Nov 2013.		802.15.4e, I-D.draft-ietf-6tisch-architecture", Nov 2013.
	[LLN-DIFF]		[LLN-DIFF]
	Shah, S. and P. Thubert, "Differentiated Service Class		Shah, S. and P. Thubert, "Differentiated Service Class
	Recommendations for LLN Traffic, I-D.draft-svshah-tsvwg-		Recommendations for LLN Traffic,
	lln-diffserv-recommendations", Aug 2013.		I-D.draft-svshah-tsvwg-lln-diffserv-recommendations",
			Aug 2013.
	Authors' Addresses		Authors' Addresses
	Shitanshu Shah		Shitanshu Shah
	Cisco Systems		Cisco Systems
	170 W. Tasman Drive		170 W. Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	US		US
	Email: svshah@cisco.com		Email: svshah@cisco.com
End of changes. 14 change blocks.
	37 lines changed or deleted		35 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/