< draft-ietf-ipfix-reducing-redundancy-03.txt		draft-ietf-ipfix-reducing-redundancy-04.txt >
	IPFIX Working Group E. Boschi		IPFIX Working Group E. Boschi
	Internet-Draft Hitachi Europe		Internet-Draft Hitachi Europe
	Intended status: Informational L. Mark		Intended status: Informational L. Mark
	Expires: September 1, 2007 Fraunhofer FOKUS		Expires: November 22, 2007 Fraunhofer FOKUS
	B. Claise		B. Claise
	Cisco Systems, Inc.		Cisco Systems, Inc.
	February 28, 2007		May 21, 2007
	Reducing Redundancy in IPFIX and PSAMP Reports		Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet
	draft-ietf-ipfix-reducing-redundancy-03.txt		Sampling (PSAMP) Reports
			draft-ietf-ipfix-reducing-redundancy-04.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 38 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 1, 2007.		This Internet-Draft will expire on November 22, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document describes a bandwidth saving method for exporting flow		This document describes a bandwidth saving method for exporting flow
	or packet information using the IP Flow Information Export (IPFIX)		or packet information using the IP Flow Information Export (IPFIX)
	protocol. As the PSAMP protocol is based on IPFIX, these		protocol. As the Packet Sampling (PSAMP) protocol is based on IPFIX,
	considerations are valid for PSAMP exports as well.		these considerations are valid for PSAMP exports as well.
	This method works by separating information common to several flow		This method works by separating information common to several flow
	records from information specific to an individual flow record.		records from information specific to an individual flow record.
	Common flow information is exported only once in a data record		Common flow information is exported only once in a data record
	defined by an option template, while the rest of the specific flow		defined by an option template, while the rest of the specific flow
	information is associated with the common information via a unique		information is associated with the common information via a unique
	identifier.		identifier.
	Table of Contents		Table of Contents
	skipping to change at page 20, line 23 ¶		skipping to change at page 20, line 23 ¶
	Properties information and to assign commonPropertiesId values. The		Properties information and to assign commonPropertiesId values. The
	Collector has to process records described by two templates instead		Collector has to process records described by two templates instead
	of just one. Additional effort is also required when post processing		of just one. Additional effort is also required when post processing
	the measurement data, in order to correlate Flow Records with Common		the measurement data, in order to correlate Flow Records with Common
	Properties information.		Properties information.
	8.1. Transport Protocol Choice		8.1. Transport Protocol Choice
	The proposed method is most effective using a reliable transport		The proposed method is most effective using a reliable transport
	protocol for the transfer of the Common Properties. Therefore the		protocol for the transfer of the Common Properties. Therefore the
	use of SCTP-PR with the reliable mode or TCP is recommended.		use of PR-SCTP with the reliable mode or TCP is recommended.
	However, if the path from the Exporting Process to the Collecting		However, if the path from the Exporting Process to the Collecting
	Process is not fully reliable, the SCTP or TCP retransmission might		Process is not fully reliable, the SCTP or TCP retransmission might
	reduce the benefits of this specification. If the path from the		reduce the benefits of this specification. If the path from the
	Exporting Process to the Collecting Process is full reliable, the use		Exporting Process to the Collecting Process is full reliable, the use
	of UDP is less effective because the Common Properties have to be re-		of UDP is less effective because the Common Properties have to be re-
	sent regularly.		sent regularly.
	8.2. Reduced Size Encoding		8.2. Reduced Size Encoding
	The transfer of the commonPropertiesIDs originates some overhead and		The transfer of the commonPropertiesIDs originates some overhead and
	skipping to change at page 23, line 4 ¶		skipping to change at page 23, line 4 ¶
	Packet Selection", draft-ietf-psamp-sample-tech-07 (work		Packet Selection", draft-ietf-psamp-sample-tech-07 (work
	in progress), July 2005.		in progress), July 2005.
	[I-D.ietf-psamp-mib]		[I-D.ietf-psamp-mib]
	Dietz, T. and B. Claise, "Definitions of Managed Objects		Dietz, T. and B. Claise, "Definitions of Managed Objects
	for Packet Sampling", draft-ietf-psamp-mib-06 (work in		for Packet Sampling", draft-ietf-psamp-mib-06 (work in
	progress), June 2006.		progress), June 2006.
	[I-D.ietf-psamp-framework]		[I-D.ietf-psamp-framework]
	Duffield, N., "A Framework for Packet Selection and		Duffield, N., "A Framework for Packet Selection and
	Reporting", draft-ietf-psamp-framework-10 (work in		Reporting", draft-ietf-psamp-framework-11 (work in
	progress), January 2005.		progress), May 2007.
	[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C.,		[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C.,
	Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M.,		Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M.,
	Zhang, L., and V. Paxson, "Stream Control Transmission		Zhang, L., and V. Paxson, "Stream Control Transmission
	Protocol", RFC 2960, October 2000.		Protocol", RFC 2960, October 2000.
	[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.		[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
	Jacobson, "RTP: A Transport Protocol for Real-Time		Jacobson, "RTP: A Transport Protocol for Real-Time
	Applications", STD 64, RFC 3550, July 2003.		Applications", STD 64, RFC 3550, July 2003.
End of changes. 7 change blocks.
	10 lines changed or deleted		11 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/