rfc9710v4.txt		rfc9710.txt
	skipping to change at line 105 ¶		skipping to change at line 105 ¶
	9. IANA Considerations		9. IANA Considerations
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	10.2. Informative References		10.2. Informative References
	Acknowledgments		Acknowledgments
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	When the Operations and Management Area Working Group (OPSAWG) was		When the Operations and Management Area Working Group (OPSAWG) was
	considering [RFC9565], which updates [RFC7125], the WG realized that		considering [RFC9565], which obsoletes [RFC7125], the WG realized
	some parts of the IANA "IP Flow Information Export (IPFIX) Entities"		that some parts of the IANA "IP Flow Information Export (IPFIX)
	registry [IANA-IPFIX] were not up to date. This document updates the		Entities" registry [IANA-IPFIX] were not up to date. This document
	IANA registry and brings some consistency among the entries of the		updates the IANA registry and brings some consistency among the
	registry.		entries of the registry.
	As discussed with IANA during the development of [RFC9487], the		As discussed with IANA during the development of [RFC9487], the
	"Additional Information" entry in [IANA-IPFIX] should contain a link		"Additional Information" entry in [IANA-IPFIX] should contain a link
	to an existing registry, when applicable, as opposed to having:		to an existing registry, when applicable, as opposed to having:
	* A link to an existing registry in the "Description" entry.		* A link to an existing registry in the "Description" entry.
	* The registry detailed values repeated in the "Description" entry.		* The registry detailed values repeated in the "Description" entry.
	This practice has the drawback that the description must be		This practice has the drawback that the description must be
	updated each time the registry is updated.		updated each time the registry is updated.
	skipping to change at line 811 ¶		skipping to change at line 811 ¶
	There is a broad variety of possible parameters that could be used		There is a broad variety of possible parameters that could be used
	for Property Match Filtering (5) but currently there are no agreed		for Property Match Filtering (5) but currently there are no agreed
	parameters specified.		parameters specified.
	Additional Information: See the "Packet Sampling (PSAMP) Parameters"		Additional Information: See the "Packet Sampling (PSAMP) Parameters"
	registry [https://www.iana.org/assignments/psamp-parameters].		registry [https://www.iana.org/assignments/psamp-parameters].
	6.12. informationElementDataType		6.12. informationElementDataType
	Note that the "informationElementDataType” registry has been renamed		Note that the "informationElementDataType" registry has been renamed
	as the "IPFIX Information Element Data Types” registry.		as the "IPFIX Information Element Data Types" registry.
	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] subregistry. 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
	skipping to change at line 885 ¶		skipping to change at line 885 ¶
	The "IPFIX Information Element Semantics" registry is intended to		The "IPFIX Information Element Semantics" registry is intended to
	assign numbers for semantics names, not to provide a mechanism for		assign numbers for semantics names, not to provide a mechanism for
	adding semantics to the IPFIX Protocol; as such, modifications		adding semantics to the IPFIX Protocol; as such, modifications
	require Standards Action [RFC8126].		require Standards Action [RFC8126].
	Additional Information: See the "IPFIX Information Element		Additional Information: See the "IPFIX Information Element
	Semantics" registry [https://www.iana.org/assignments/ipfix].		Semantics" registry [https://www.iana.org/assignments/ipfix].
	6.14. informationElementUnits		6.14. informationElementUnits
	Note that the "informationElementsUnits” registry has been renamed as		Note that the "informationElementsUnits" registry has been renamed as
	the "IPFIX Information Element Units” registry.		the "IPFIX Information Element Units" registry.
	6.14.1. OLD		6.14.1. OLD
	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 informationElementsUnits		on the types described in the informationElementsUnits
	subregistry. This field may take the values in Table 3 below; the		subregistry. This field may take the values in Table 3 below; the
	special value 0x00 (none) is used to note that the field is		special value 0x00 (none) is used to note that the field is
End of changes. 3 change blocks.
	9 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.48.