< draft-braun-core-compressed-ipfix-02.txt		draft-braun-core-compressed-ipfix-03.txt >
	Network Working Group L. Braun		Network Working Group L. Braun
	Internet-Draft C. Schmitt		Internet-Draft C. Schmitt
	Intended status: Standards Track TU Muenchen		Intended status: Standards Track TU Muenchen
	Expires: September 15, 2011 B. Claise		Expires: March 22, 2012 B. Claise
	Cisco Systems, Inc.		Cisco Systems, Inc.
	G. Carle		G. Carle
	TU Muenchen		TU Muenchen
	March 14, 2011		September 21, 2011
	Compressed IPFIX for smart meters in constrained networks		Compressed IPFIX for smart meters in constrained networks
	<draft-braun-core-compressed-ipfix-02>		<draft-braun-core-compressed-ipfix-03>
	Abstract		Abstract
	This document specifies the Compressed IPFIX protocol that serves for		This document specifies the Compressed IPFIX protocol that serves for
	transmitting smart metering data in 6LoWPAN networks [RFC4944].		transmitting smart metering data in 6LoWPAN networks [RFC4944].
	Compressed IPFIX is derived from IPFIX [RFC5101] and adopted to the		Compressed IPFIX is derived from IPFIX [RFC5101] and adopted to the
	needs of constrained networks. This documents specifies how the		needs of constrained networks. This documents specifies how the
	Compressed IPFIX Data and Template Records are transmitted in 6LoWPAN		Compressed IPFIX Data and Template Records are transmitted in 6LoWPAN
	networks and how Compressed IPFIX data can be converted into		networks and how Compressed IPFIX data can be converted into
	uncompressed IPFIX data in a proxy device.		uncompressed IPFIX data in a proxy device.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 September 15, 2011.		This Internet-Draft will expire on March 22, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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 8, line 7 ¶		skipping to change at page 8, line 7 ¶
	flash memory (128 kb) and radio frequency transceiver, which are		flash memory (128 kb) and radio frequency transceiver, which are
	located on the board.		located on the board.
	Network protocols used on such hardware need to respect these		Network protocols used on such hardware need to respect these
	constraints. They must be simple to implement using little code and		constraints. They must be simple to implement using little code and
	little run time memory and should produce little overhead when		little run time memory and should produce little overhead when
	encoding the application payload.		encoding the application payload.
	3.2. Energy constraints		3.2. Energy constraints
	Smart meters that are battery powered have hard energy constraints.		Smart meters that are battery powered have hard energy constraints
	[Schmitt09]. If they run out of power, their battery has to be		[Schmitt09]. By power supply of two 2 AA 2,800-mAh batteries this
	changed, which means physical manipulation to the device is		means approximately 30,240J. If they run out of power, their battery
			Has to be changed, which means physical manipulation to the device is
	necessary. Using as little energy as possible for network		necessary. Using as little energy as possible for network
	communication is therefore desired.		communication is therefore desired.
	A smart metering device can save a lot of energy, if it powers down		A smart metering device can save a lot of energy, if it powers down
	its radio frequency transceiver. Such devices do not have permanent		its radio frequency transceiver. Such devices do not have permanent
	network connectivity but are only part of the network as needed. A		network connectivity but are only part of the network as needed. A
	push protocol, where only one side is sending data, is suitable for		push protocol, where only one side is sending data, is suitable for
	transmitting application data under such circumstances. As the		transmitting application data under such circumstances. As the
	communication is unidirectional, a meter can completely power down		communication is unidirectional, a meter can completely power down
	its radio frequency transceivers as long as it does not have any data		its radio frequency transceivers as long as it does not have any data
End of changes. 5 change blocks.
	7 lines changed or deleted		8 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/