draft-ietf-6tisch-coap-02.txt		draft-ietf-6tisch-coap-03.txt
	6TiSCH R. Sudhaakar, Ed.		6TiSCH R. Sudhaakar, Ed.
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track P. Zand		Intended status: Standards Track P. Zand
	Expires: June 7, 2015 University of Twente		Expires: September 10, 2015 University of Twente
	December 4, 2014		March 9, 2015
	6TiSCH Resource Management and Interaction using CoAP		6TiSCH Resource Management and Interaction using CoAP
	draft-ietf-6tisch-coap-02		draft-ietf-6tisch-coap-03
	Abstract		Abstract
	The [IEEE802154e] standardizes the TSCH mode of operation and defines		The [IEEE802154e] standardizes the TSCH mode of operation and defines
	the mechanisms for layer 2 communication between conforming devices.		the mechanisms for layer 2 communication between conforming devices.
	6top defines a set of commands to monitor and manage the TSCH		6top defines a set of commands to monitor and manage the TSCH
	schedule. To realize the full functionality of sensor networks and		schedule. To realize the full functionality of sensor networks and
	allow their adoption and use in real applications we need additional		allow their adoption and use in real applications we need additional
	mechanisms. Specifically, the interaction with 6top, control and		mechanisms. Specifically, the interaction with 6top, control and
	modify schedules, monitor parameters etc must be defined. Higher		modify schedules, monitor parameters etc must be defined. Higher
	skipping to change at page 2, line 7		skipping to change at page 2, line 7
	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 June 7, 2015.		This Internet-Draft will expire on September 10, 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 9, line 30		skipping to change at page 9, line 30
	As new resources are defined (both native and custom), it is		As new resources are defined (both native and custom), it is
	essential for the PCE as well peers to discover the resources. The		essential for the PCE as well peers to discover the resources. The
	CoMI draft presents methods by which standard CoAP resource discovery		CoMI draft presents methods by which standard CoAP resource discovery
	mechanisms are extended to the management of constrained devices.		mechanisms are extended to the management of constrained devices.
	The methods described in Section 4.3 of [I-D.vanderstok-core-comi]		The methods described in Section 4.3 of [I-D.vanderstok-core-comi]
	SHALL be used for discovering new resources available at a node.		SHALL be used for discovering new resources available at a node.
	4.3.4. Message Formats		4.3.4. Message Formats
			NOTE: The message formats presented in this section follow the
			specifications in the CoMI draft [I-D.vanderstok-core-comi]. In case
			of any discrepancies, the CoMI draft will take precedence.
	GET messages do not contain any payload. However, they can contain a		GET messages do not contain any payload. However, they can contain a
	query option to filter on the resource that is being retrieved. An		query option to filter on the resource that is being retrieved. An
	example query on the neighbor list is:		example query on the neighbor list is:
	+------------------------------------------+		+------------------------------------------+
	Header | GET |		Header | GET |
	+------------------------------------------+		+------------------------------------------+
	Uri-Path| /6top/nbrList |		Uri-Path| /6top/nbrList |
	+------------------------------------------+		+------------------------------------------+
	Options | Accept: application/cbor |		Options | Accept: application/cbor |
	skipping to change at page 14, line 49		skipping to change at page 14, line 49
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	5.2. Informative References		5.2. Informative References
	[I-D.ietf-6tisch-6top-interface]		[I-D.ietf-6tisch-6top-interface]
	Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH		Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
	Operation Sublayer (6top) Interface", draft-ietf-6tisch-		Operation Sublayer (6top) Interface", draft-ietf-6tisch-
	6top-interface-02 (work in progress), October 2014.		6top-interface-02 (work in progress), October 2014.
	[I-D.ietf-6tisch-architecture]		[I-D.ietf-6tisch-architecture]
	Thubert, P., Watteyne, T., and R. Assimiti, "An		Thubert, P., Watteyne, T., Struik, R., and M. Richardson,
	Architecture for IPv6 over the TSCH mode of IEEE		"An Architecture for IPv6 over the TSCH mode of IEEE
	802.15.4e", draft-ietf-6tisch-architecture-04 (work in		802.15.4e", draft-ietf-6tisch-architecture-06 (work in
	progress), October 2014.		progress), March 2015.
	[I-D.ietf-6tisch-coap]
	Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and
	Interaction using CoAP", draft-ietf-6tisch-coap-01 (work
	in progress), July 2014.
	[I-D.ietf-6tisch-minimal]		[I-D.ietf-6tisch-minimal]
	Vilajosana, X. and K. Pister, "Minimal 6TiSCH		Vilajosana, X. and K. Pister, "Minimal 6TiSCH
	Configuration", draft-ietf-6tisch-minimal-04 (work in		Configuration", draft-ietf-6tisch-minimal-06 (work in
	progress), November 2014.		progress), March 2015.
	[I-D.ietf-6tisch-terminology]		[I-D.ietf-6tisch-terminology]
	Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,		Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
	"Terminology in IPv6 over the TSCH mode of IEEE		"Terminology in IPv6 over the TSCH mode of IEEE
	802.15.4e", draft-ietf-6tisch-terminology-02 (work in		802.15.4e", draft-ietf-6tisch-terminology-03 (work in
	progress), July 2014.		progress), January 2015.
	[I-D.ietf-6tisch-tsch]		[I-D.ietf-6tisch-tsch]
	Watteyne, T., Palattella, M., and L. Grieco, "Using		Watteyne, T., Palattella, M., and L. Grieco, "Using
	IEEE802.15.4e TSCH in an IoT context: Overview, Problem		IEEE802.15.4e TSCH in an IoT context: Overview, Problem
	Statement and Goals", draft-ietf-6tisch-tsch-03 (work in		Statement and Goals", draft-ietf-6tisch-tsch-05 (work in
	progress), October 2014.		progress), January 2015.
	[I-D.ietf-core-observe]		[I-D.ietf-core-observe]
	Hartke, K., "Observing Resources in CoAP", draft-ietf-		Hartke, K., "Observing Resources in CoAP", draft-ietf-
	core-observe-15 (work in progress), October 2014.		core-observe-16 (work in progress), December 2014.
	[I-D.vanderstok-core-comi]		[I-D.vanderstok-core-comi]
	Stok, P., Greevenbosch, B., Bierman, A., Schoenwaelder,		Stok, P., Greevenbosch, B., Bierman, A., Schoenwaelder,
	J., and A. Sehgal, "CoAP Management Interface", draft-		J., and A. Sehgal, "CoAP Management Interface", draft-
	vanderstok-core-comi-05 (work in progress), October 2014.		vanderstok-core-comi-06 (work in progress), February 2015.
	[I-D.wang-6tisch-6top-sublayer]		[I-D.wang-6tisch-6top-sublayer]
	Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH		Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH
	Operation Sublayer (6top)", draft-wang-6tisch-6top-		Operation Sublayer (6top)", draft-wang-6tisch-6top-
	sublayer-01 (work in progress), July 2014.		sublayer-01 (work in progress), July 2014.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66, RFC		Resource Identifier (URI): Generic Syntax", STD 66, RFC
	3986, January 2005.		3986, January 2005.
End of changes. 11 change blocks.
	22 lines changed or deleted		21 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/