rfc9710v2.txt		rfc9710.txt
	skipping to change at line 817 ¶		skipping to change at line 817 ¶
	registry [https://www.iana.org/assignments/psamp-parameters].		registry [https://www.iana.org/assignments/psamp-parameters].
	6.12. informationElementDataType		6.12. informationElementDataType
	6.12.1. OLD		6.12.1. OLD
	Description: A description of the abstract data type of an IPFIX		Description: A description of the abstract data type of an IPFIX
	information element. These are taken from the abstract data types		information element. These are taken from the abstract data types
	defined in section 3.1 of the IPFIX Information Model [RFC5102];		defined in section 3.1 of the IPFIX Information Model [RFC5102];
	see that section for more information on the types described in		see that section for more information on the types described in
	the [informationElementDataType] registry. These types are		the [informationElementDataType] subregistry. These types are
	registered in the IANA IPFIX Information Element Data Type		registered in the IANA IPFIX Information Element Data Type
	subregistry. This subregistry is intended to assign numbers for		subregistry. This subregistry is intended to assign numbers for
	type names, not to provide a mechanism for adding data types to		type names, not to provide a mechanism for adding data types to
	the IPFIX Protocol, and as such requires a Standards Action		the IPFIX Protocol, and as such requires a Standards Action
	[RFC8126] to modify.		[RFC8126] to modify.
	6.12.2. NEW		6.12.2. NEW
	Description: A description of the abstract data type of an IPFIX		Description: A description of the abstract data type of an IPFIX
	information element. These are taken from the abstract data types		information element. These are taken from the abstract data types
	defined in Section 3.1 of the IPFIX Information Model [RFC5102];		defined in Section 3.1 of the IPFIX Information Model [RFC5102];
	see that section for more information on the types described in		see that section for more information on the types described in
	the "IPFIX Information Element Data Types" registry (previously		the "IPFIX Information Element Data Types" registry (previously
	the "informationElementDataType" subregistry). These types are		the "informationElementDataType" registry). These types are
	registered in the "IPFIX Information Element Data Types" registry.		registered in the "IPFIX Information Element Data Types" registry.
	The "IPFIX Information Element Data Types" registry is intended to		The "IPFIX Information Element Data Types" registry is intended to
	assign numbers for type names, not to provide a mechanism for		assign numbers for type names, not to provide a mechanism for
	adding data types to the IPFIX Protocol; as such, modifications		adding data types to the IPFIX Protocol; as such, modifications
	require Standards Action [RFC8126].		require Standards Action [RFC8126].
	Additional Information: See the "IPFIX Information Element Data		Additional Information: See the "IPFIX Information Element Data
	Types" registry [https://www.iana.org/assignments/ipfix].		Types" registry [https://www.iana.org/assignments/ipfix].
	skipping to change at line 901 ¶		skipping to change at line 901 ¶
	unitless. These types are registered in the [IANA IPFIX		unitless. These types are registered in the [IANA IPFIX
	Information Element Units] subregistry.		Information Element Units] subregistry.
	6.14.2. NEW		6.14.2. NEW
	Description: A description of the units of an IPFIX Information		Description: A description of the units of an IPFIX Information
	Element. These correspond to the units implicitly defined in the		Element. These correspond to the units implicitly defined in the
	Information Element definitions in Section 5 of the IPFIX		Information Element definitions in Section 5 of the IPFIX
	Information Model [RFC5102]; see that section for more information		Information Model [RFC5102]; see that section for more information
	on the types described in the "IPFIX Information Element Units"		on the types described in the "IPFIX Information Element Units"
	registry (previously the informationElementsUnits subregistry).		registry (previously the "informationElementsUnits" registry).
	These types can take the values in the "IPFIX Information Element		These types can take the values in the "IPFIX Information Element
	Units" registry. The special value 0x00 (none) is used to note		Units" registry. The special value 0x00 (none) is used to note
	that the field is unitless.		that the field is unitless.
	Additional Information: See the "IPFIX Information Element Units"		Additional Information: See the "IPFIX Information Element Units"
	registry [https://www.iana.org/assignments/ipfix].		registry [https://www.iana.org/assignments/ipfix].
	6.15. portRangeStart		6.15. portRangeStart
	6.15.1. OLD		6.15.1. OLD
	skipping to change at line 1281 ¶		skipping to change at line 1281 ¶
	7.3.1. OLD		7.3.1. OLD
	+--------+----------+-----------------------------------------------+		+--------+----------+-----------------------------------------------+
	| bit(s) | name | description |		| bit(s) | name | description |
	| (LSB = | | |		| (LSB = | | |
	| 0) | | |		| 0) | | |
	+--------+----------+-----------------------------------------------+		+--------+----------+-----------------------------------------------+
	| 0-1 | SC | Stability Class: see the Stability Class |		| 0-1 | SC | Stability Class: see the Stability Class |
	| | | table below, and section Section 5.1. |		| | | table below, and section Section 5.1. |
	| 2 | PmA | Perimeter Anonymization: when set (1), |		| 2 | PmA | Perimeter Anonymization: when set (1), |
	| | | source Information Elements as described in |		| | | source- Information Elements as described in |
	| | | [RFC5103] are interpreted as external |		| | | [RFC5103] are interpreted as external |
	| | | addresses, and destination Information |		| | | addresses, and destination- Information |
	| | | Elements as described in [RFC5103] are |		| | | Elements as described in [RFC5103] are |
	| | | interpreted as internal addresses, for the |		| | | interpreted as internal addresses, for the |
	| | | purposes of associating |		| | | purposes of associating |
	| | | anonymizationTechnique to Information |		| | | anonymizationTechnique to Information |
	| | | Elements only; see Section 7.2.2 for details. |		| | | Elements only; see Section 7.2.2 for details. |
	| | | This bit MUST NOT be set when associated with |		| | | This bit MUST NOT be set when associated with |
	| | | a non-endpoint (i.e., source or |		| | | a non-endpoint (i.e., source- or |
	| | | destination) Information Element. SHOULD be |		| | | destination-) Information Element. SHOULD be |
	| | | consistent within a record (i.e., if a |		| | | consistent within a record (i.e., if a |
	| | | source Information Element has this flag |		| | | source- Information Element has this flag |
	| | | set, the corresponding destination element |		| | | set, the corresponding destination- element |
	| | | SHOULD have this flag set, and vice-versa.) |		| | | SHOULD have this flag set, and vice-versa.) |
	+--------+----------+-----------------------------------------------+		+--------+----------+-----------------------------------------------+
	7.3.2. NEW		7.3.2. NEW
	+--------+----------+-----------------------------------------------+		+--------+----------+-----------------------------------------------+
	| bit(s) | name | description |		| bit(s) | name | description |
	| (LSB = | | |		| (LSB = | | |
	| 0) | | |		| 0) | | |
	+--------+----------+-----------------------------------------------+		+--------+----------+-----------------------------------------------+
End of changes. 7 change blocks.
	9 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.48.