< draft-yourtchenko-cisco-ies-10.txt		draft-yourtchenko-cisco-ies-11.txt >
	Network Working Group A. Yourtchenko		Network Working Group A. Yourtchenko
	Internet-Draft P. Aitken		Internet-Draft P. Aitken
	Intended status: Informational B. Claise		Intended status: Informational B. Claise
	Expires: August 17, 2014 Cisco Systems, Inc.		Expires: September 26, 2014 Cisco Systems, Inc.
	February 13, 2014		March 25, 2014
	Cisco Specific Information Elements reused in IPFIX		Cisco Specific Information Elements reused in IPFIX
	draft-yourtchenko-cisco-ies-10		draft-yourtchenko-cisco-ies-11
	Abstract		Abstract
	This document describes some additional IPFIX Information Elements in		This document describes some additional IPFIX Information Elements in
	the range of 1-127, which is the range compatible with field types		the range of 1-127, which is the range compatible with field types
	used by NetFlow version 9 in RFC3954, as specified in the IPFIX		used by NetFlow version 9 in RFC3954, as specified in the IPFIX
	Information Model RFC 7012.		Information Model RFC 7012.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 17, 2014.		This Internet-Draft will expire on September 26, 2014.
	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 2, line 35 ¶		skipping to change at page 2, line 35 ¶
	4.15. className . . . . . . . . . . . . . . . . . . . . . . . . 8		4.15. className . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.16. layer2packetSectionOffset . . . . . . . . . . . . . . . . 9		4.16. layer2packetSectionOffset . . . . . . . . . . . . . . . . 9
	4.17. layer2packetSectionSize . . . . . . . . . . . . . . . . . 9		4.17. layer2packetSectionSize . . . . . . . . . . . . . . . . . 9
	4.18. layer2packetSectionData . . . . . . . . . . . . . . . . . 9		4.18. layer2packetSectionData . . . . . . . . . . . . . . . . . 9
	5. Other Information Elements . . . . . . . . . . . . . . . . . 9		5. Other Information Elements . . . . . . . . . . . . . . . . . 9
	5.1. Performance Metrics IEs . . . . . . . . . . . . . . . . . 9		5.1. Performance Metrics IEs . . . . . . . . . . . . . . . . . 9
	5.2. Application Information IEs . . . . . . . . . . . . . . . 9		5.2. Application Information IEs . . . . . . . . . . . . . . . 9
	5.3. IEs assigned for NetFlow v9 compatibility . . . . . . . . 10		5.3. IEs assigned for NetFlow v9 compatibility . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 10		7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	8.1. Normative References . . . . . . . . . . . . . . . . . . 11		8.1. Normative References . . . . . . . . . . . . . . . . . . 10
	8.2. Informative References . . . . . . . . . . . . . . . . . 11		8.2. Informative References . . . . . . . . . . . . . . . . . 11
	Appendix A. XML Specification of IPFIX Information Elements . . 12		Appendix A. XML Specification of IPFIX Information Elements . . 12
	Appendix B. Changes . . . . . . . . . . . . . . . . . . . . . . 18		Appendix B. Changes . . . . . . . . . . . . . . . . . . . . . . 18
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
	1. Introduction		1. Introduction
	The section 4 of [RFC7012] defines the IPFIX Information Elements in		The section 4 of [RFC7012] defines the IPFIX Information Elements in
	the range of 1-127 to be compatible with the NetFlow version 9		the range of 1-127 to be compatible with the NetFlow version 9
	fields, as specified in the "Cisco Systems NetFlow Services Export		fields, as specified in the "Cisco Systems NetFlow Services Export
	skipping to change at page 9, line 51 ¶		skipping to change at page 9, line 51 ¶
	Performance metrics will need a consolidation in the industry, based		Performance metrics will need a consolidation in the industry, based
	on RFC6390. Once this consolidation happens, via a separate document		on RFC6390. Once this consolidation happens, via a separate document
	the IEs 65-69 will either be assigned in the IANA registry or their		the IEs 65-69 will either be assigned in the IANA registry or their
	status will be deprecated.		status will be deprecated.
	5.2. Application Information IEs		5.2. Application Information IEs
	ElementId: 101		ElementId: 101
	ElementId: 94 .. 97		ElementId: 94 .. 96
	Please refer to the RFC 6759 [RFC6759]		Please refer to the RFC 6759 [RFC6759]
	5.3. IEs assigned for NetFlow v9 compatibility		5.3. IEs assigned for NetFlow v9 compatibility
	ElementId: 105..127		ElementId: 105..127
	These element IDs are not covered by this draft and left "as is",		These element IDs are not covered by this draft and left "as is",
	i.e. for NetFlow v9 compatibility.		i.e. for NetFlow v9 compatibility.
	6. IANA Considerations		6. IANA Considerations
	skipping to change at page 10, line 45 ¶		skipping to change at page 10, line 45 ¶
	o IE Number 103 for the layer2packetSectionSize IE		o IE Number 103 for the layer2packetSectionSize IE
	o IE Number 104 for the layer2packetSectionData IE		o IE Number 104 for the layer2packetSectionData IE
	7. Security Considerations		7. Security Considerations
	This document specifies the definitions of several Information		This document specifies the definitions of several Information
	Elements and does not alter the security considerations of the base		Elements and does not alter the security considerations of the base
	protocol. Please refer to the security considerations sections of		protocol. Please refer to the security considerations sections of
	RFC 3954 [RFC3954] and RFC 7012 [RFC7012].		RFC 3954 [RFC3954] and RFC 7012 [RFC7012].
	However, the export of the sections of the packet payload may
	unintentionally change the security assumptions of other protocols.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of		[RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of
	the IP Flow Information Export (IPFIX) Protocol for the		the IP Flow Information Export (IPFIX) Protocol for the
	Exchange of Flow Information", STD 77, RFC 7011, September		Exchange of Flow Information", STD 77, RFC 7011, September
	2013.		2013.
	8.2. Informative References		8.2. Informative References
	skipping to change at page 19, line 30 ¶		skipping to change at page 19, line 25 ¶
	09: now that IANA assigned the IPFIX Information Elements in draft-		09: now that IANA assigned the IPFIX Information Elements in draft-
	ietf-ipfix-data-link-layer-monitoring, this draft is updated to		ietf-ipfix-data-link-layer-monitoring, this draft is updated to
	simplify IANA's/editor's work, with changes as follows. TBD02 became		simplify IANA's/editor's work, with changes as follows. TBD02 became
	409 as sectionOffset is now assigned by IANA. Removed "EDITOR's		409 as sectionOffset is now assigned by IANA. Removed "EDITOR's
	NOTE" for layer2packetSectionOffset, layer2packetSectionSize,		NOTE" for layer2packetSectionOffset, layer2packetSectionSize,
	layer2packetSectionData, ietf-ipfix-data-link-layer-monitoring.		layer2packetSectionData, ietf-ipfix-data-link-layer-monitoring.
	10: reflect the comments from GEN-ART / LC reviews. Change the		10: reflect the comments from GEN-ART / LC reviews. Change the
	wording in abstract/introduction, add required clarifications. Per		wording in abstract/introduction, add required clarifications. Per
	Andrew Peren, the semantic for ipv4RouterSc should be "default", not		Andrew Feren, the semantic for ipv4RouterSc should be "default", not
	"identifier" - fixed. Alas, unfortunately no way to affect how		"identifier" - fixed. Alas, unfortunately no way to affect how
	xml2rfc trims the super-long URLs, so I could not make splitting of		xml2rfc trims the super-long URLs, so I could not make splitting of
	the URLs nicer.		the URLs nicer.
			11: remove the sentence from 'security considerations' per thread
			about Alissa Cooper's DISCUSS thread. Remove the #97, which is not
			in RFC6759.
	Authors' Addresses		Authors' Addresses
	Andrew Yourtchenko		Andrew Yourtchenko
	Cisco Systems, Inc.		Cisco Systems, Inc.
	De Kleetlaan, 7		De Kleetlaan, 7
	Brussels, Diegem B-1831		Brussels, Diegem B-1831
	Belgium		Belgium
	Phone: +32 2 704 5494		Phone: +32 2 704 5494
	Email: ayourtch@cisco.com		Email: ayourtch@cisco.com
End of changes. 8 change blocks.
	11 lines changed or deleted		12 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/