< draft-aitken-ipfix-equivalent-ies-01.txt		draft-aitken-ipfix-equivalent-ies-02.txt >
	IPFIX Working Group P. Aitken		IPFIX Working Group P. Aitken
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track		Intended status: Standards Track
	Expires: July 1, 2014 December 27, 2013		Expires: July 4, 2015 July 4, 2014
	Reporting Equivalent IPFIX Information Elements		Reporting Equivalent IPFIX Information Elements
	draft-aitken-ipfix-equivalent-ies-01		draft-aitken-ipfix-equivalent-ies-02
	Abstract		Abstract
	This document specifies a method for an		This document specifies a method for an
	IPFIX Exporting Process to inform an IPFIX Collecting Process		IPFIX Exporting Process to inform an IPFIX Collecting Process
	of equivalence between different Information Elements, so		of equivalence between different Information Elements, so
	that the Collecting Process can understand the equivalence		that the Collecting Process can understand the equivalence
	and be enabled to process data across a change of		and be enabled to process data across a change of
	Information Elements.		Information Elements.
	skipping to change at page 2, line 7 ¶		skipping to change at page 2, line 7 ¶
	Internet-Drafts are draft documents valid for a maximum of		Internet-Drafts are draft documents valid for a maximum of
	six months and may be updated, replaced, or obsoleted by		six months and may be updated, replaced, or obsoleted by
	other documents at any time. It is inappropriate to use		other documents at any time. It is inappropriate to use
	Internet-Drafts as reference material or to cite them other		Internet-Drafts as reference material or to cite them other
	than as "work in progress."		than as "work in progress."
	This Internet-Draft will expire on July 1, 2014.		This Internet-Draft will expire on July 1, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as		Copyright (c) 2014 IETF Trust and the persons identified as
	the document authors. All rights reserved.		the 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		(http://trustee.ietf.org/license-info) in effect on the date
	of publication of this document. Please review these		of publication of this document. Please review these
	documents carefully, as they describe your rights and		documents carefully, as they describe your rights and
	restrictions with respect to this document. Code Components		restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD		extracted from this document must include Simplified BSD
	License text as described in Section 4.e of the Trust Legal		License text as described in Section 4.e of the Trust Legal
	skipping to change at page 6, line 21 ¶		skipping to change at page 6, line 21 ¶
	3.1.2 Equivalence Message with an Enterprise-Specific		3.1.2 Equivalence Message with an Enterprise-Specific
	Original Information Element		Original Information Element
	When the Original Information Element is enterprise-specific,		When the Original Information Element is enterprise-specific,
	the Original Information Element's E bit is set and the		the Original Information Element's E bit is set and the
	Information Element number is immediately followed by the		Information Element number is immediately followed by the
	corresponding Private Enterprise Number [PEN], as shown in		corresponding Private Enterprise Number [PEN], as shown in
	Figure 3:		Figure 3:
	+-+---------------+----------------------------------+-+---------------+		+-+---------------+----------------------------------+-+---------------+
	|1| Original IE | Private Enterprise Number |0| Equivalent IE |		|1| Original IE | Private Enterprise Number |0| Equivalent IE |
	+-+---------------+----------------------------------+-+---------------+		+-+---------------+----------------------------------+-+---------------+
			-+---------------+----------------------------------+-+---------------+
	Figure 3: Equivalence Message with an Enterprise-Specific		Figure 3: Equivalence Message with an Enterprise-Specific
	Original Information Element		Original Information Element
	This allows an enterprise-specific Information Element to be		This allows an enterprise-specific Information Element to be
	specified as equivalent to an IANA standard Information		specified as equivalent to an IANA standard Information
	Element.		Element.
	3.1.3 Equivalence Message with an Enterprise-Specific		3.1.3 Equivalence Message with an Enterprise-Specific
	Equivalent Information Element		Equivalent Information Element
	When the Equivalent Information Element is enterprise-specific,		When the Equivalent Information Element is enterprise-specific,
	the Equivalent Information Element's E bit is set and the		the Equivalent Information Element's E bit is set and the
	Information Element number is immediately followed by the		Information Element number is immediately followed by the
	corresponding Private Enterprise Number [PEN] as shown in		corresponding Private Enterprise Number [PEN] as shown in
	Figure 4:		Figure 4:
	+-+---------------+-+---------------+----------------------------------+		+-+---------------+-+---------------+----------------------------------+
	|0| Original IE |1| Equivalent IE | Private Enterprise Number |		|0| Original IE |1| Equivalent IE | Private Enterprise Number |
	+-+---------------+-+---------------+----------------------------------+		+-+---------------+-+---------------+----------------------------------+
			-+---------------+-+---------------+----------------------------------+
	Figure 4: Equivalence Message with an Enterprise-Specific		Figure 4: Equivalence Message with an Enterprise-Specific
	Equivalent Information Element		Equivalent Information Element
	This allows an IANA standard Information Element to be		This allows an IANA standard Information Element to be
	specified as equivalent to an enterprise-specific Information		specified as equivalent to an enterprise-specific Information
	Element.		Element.
	3.1.4 Equivalence Message with an		3.1.4 Equivalence Message with an
	Enterprise-Specific Original Information Element and		Enterprise-Specific Original Information Element and
	skipping to change at page 8, line 37 ¶		skipping to change at page 8, line 37 ¶
	Information Element as shown in Figure 7, or an		Information Element as shown in Figure 7, or an
	enterprise-specific Information Element as shown in Figure 8.		enterprise-specific Information Element as shown in Figure 8.
	+-+---------------+-+---------------+		+-+---------------+-+---------------+
	|0|mibObjectIdent.|0| Equivalent IE |		|0|mibObjectIdent.|0| Equivalent IE |
	+-+---------------+-+---------------+		+-+---------------+-+---------------+
	Figure 7: MIB Equivalence Message with an		Figure 7: MIB Equivalence Message with an
	IANA-standard Information Element		IANA-standard Information Element
	+-+---------------+-+---------------+----------------------------------+		+-+---------------+-+---------------+----------------------------------+
	|0|mibObjectIdent.|1| Equivalent IE | Private Enterprise Number |		|0|mibObjectIdent.|1| Equivalent IE | Private Enterprise Number |
	+-+---------------+-+---------------+----------------------------------+		+-+---------------+-+---------------+----------------------------------+
			-+---------------+-+---------------+----------------------------------+
	Figure 8: MIB Equivalence Message with an		Figure 8: MIB Equivalence Message with an
	Enterprise-Specific Information Element		Enterprise-Specific Information Element
	4 The Collecting Process's Side		4 The Collecting Process's Side
	Equivalence Messages have global scope, unless they're sent in		Equivalence Messages have global scope, unless they're sent in
	an Options Message with a more restrictive scope, e.g. an		an Options Message with a more restrictive scope, e.g. an
	Options Record Scoped to the Exporter.		Options Record Scoped to the Exporter.
End of changes. 10 change blocks.
	12 lines changed or deleted		16 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/