rfc9710v3.txt		rfc9710.txt
	Internet Engineering Task Force (IETF) M. Boucadair		Internet Engineering Task Force (IETF) M. Boucadair
	Request for Comments: 9710 Orange		Request for Comments: 9710 Orange
	Category: Standards Track B. Claise		Category: Standards Track B. Claise
	ISSN: 2070-1721 Huawei		ISSN: 2070-1721 Huawei
	January 2025		February 2025
	Simple Fixes to the IP Flow Information Export (IPFIX) Entities IANA		Simple Fixes to the IP Flow Information Export (IPFIX) Entities IANA
	Registry		Registry
	Abstract		Abstract
	This document provides simple fixes to the IANA "IP Flow Information		This document provides simple fixes to the IANA "IP Flow Information
	Export (IPFIX) Entities" registry. Specifically, this document		Export (IPFIX) Entities" registry. Specifically, this document
	provides updates to fix shortcomings in the description of some		provides updates to fix shortcomings in the description of some
	Information Elements (IEs), to ensure a consistent structure when		Information Elements (IEs), to ensure a consistent structure when
	skipping to change at line 189 ¶		skipping to change at line 189 ¶
	4.1. sourceTransportPort		4.1. sourceTransportPort
	4.1.1. OLD		4.1.1. OLD
	Description: The source port identifier in the transport header.		Description: The source port identifier in the transport header.
	For the transport protocols UDP, TCP, and SCTP, this is the source		For the transport protocols UDP, TCP, and SCTP, this is the source
	port number given in the respective header. This field MAY also		port number given in the respective header. This field MAY also
	be used for future transport protocols that have 16-bit source		be used for future transport protocols that have 16-bit source
	port identifiers.		port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of SCTP.		See [RFC9260] for the definition of SCTP.
	Additional information on defined UDP and TCP port numbers can be		Additional information on defined UDP and TCP port numbers can be
	found at [https://www.iana.org/assignments/service-names-port-		found at [https://www.iana.org/assignments/service-names-port-
	numbers].		numbers].
	4.1.2. NEW		4.1.2. NEW
	Description: The source port identifier in the transport protocol		Description: The source port identifier in the transport protocol
	header. For transport protocols such as UDP, TCP, SCTP, and DCCP,		header. For transport protocols such as UDP, TCP, SCTP, and DCCP,
	this is the source port number given in the respective header.		this is the source port number given in the respective header.
	This field MAY also be used for future transport protocols that		This field MAY also be used for future transport protocols that
	have 16-bit source port identifiers.		have 16-bit source port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of the SCTP source port number		See [RFC9260] for the definition of the SCTP source port number
	field.		field.
	See [RFC4340] for the definition of the DCCP source port field.		See [RFC4340] for the definition of the DCCP source port field.
	See the assigned transport protocol (e.g., UDP, TCP, SCTP, and		See the assigned transport protocol (e.g., UDP, TCP, SCTP, and
	skipping to change at line 232 ¶		skipping to change at line 232 ¶
	4.2. destinationTransportPort		4.2. destinationTransportPort
	4.2.1. OLD		4.2.1. OLD
	Description: The destination port identifier in the transport		Description: The destination port identifier in the transport
	header. For the transport protocols UDP, TCP, and SCTP, this is		header. For the transport protocols UDP, TCP, and SCTP, this is
	the destination port number given in the respective header. This		the destination port number given in the respective header. This
	field MAY also be used for future transport protocols that have		field MAY also be used for future transport protocols that have
	16-bit destination port identifiers.		16-bit destination port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of SCTP.		See [RFC9260] for the definition of SCTP.
	Additional information on defined UDP and TCP port numbers can be		Additional information on defined UDP and TCP port numbers can be
	found at https://www.iana.org/assignments/service-names-port-		found at https://www.iana.org/assignments/service-names-port-
	numbers.		numbers.
	4.2.2. NEW		4.2.2. NEW
	Description: The destination port identifier in the transport		Description: The destination port identifier in the transport
	protocol header. For transport protocols such as UDP, TCP, SCTP,		protocol header. For transport protocols such as UDP, TCP, SCTP,
	and DCCP, this is the destination port number given in the		and DCCP, this is the destination port number given in the
	respective header. This field MAY also be used for future		respective header. This field MAY also be used for future
	transport protocols that have 16-bit destination port identifiers.		transport protocols that have 16-bit destination port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	destination port field.		destination port field.
	See [RFC9293] for the definition of the TCP destination port		See [RFC9293] for the definition of the TCP destination port
	field.		field.
	See [RFC9260] for the definition of the SCTP destination port		See [RFC9260] for the definition of the SCTP destination port
	number field.		number field.
	See [RFC4340] for the definition of the DCCP destination port		See [RFC4340] for the definition of the DCCP destination port
	field.		field.
	skipping to change at line 355 ¶		skipping to change at line 355 ¶
	4.4. collectorTransportPort		4.4. collectorTransportPort
	4.4.1. OLD		4.4.1. OLD
	Description: The destination port identifier to which the Exporting		Description: The destination port identifier to which the Exporting
	Process sends Flow information. For the transport protocols UDP,		Process sends Flow information. For the transport protocols UDP,
	TCP, and SCTP, this is the destination port number. This field		TCP, and SCTP, this is the destination port number. This field
	MAY also be used for future transport protocols that have 16-bit		MAY also be used for future transport protocols that have 16-bit
	source port identifiers.		source port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of SCTP.		See [RFC9260] for the definition of SCTP.
	Additional information on defined UDP and TCP port numbers can be		Additional information on defined UDP and TCP port numbers can be
	found at [https://www.iana.org/assignments/service-names-port-		found at [https://www.iana.org/assignments/service-names-port-
	numbers].		numbers].
	4.4.2. NEW		4.4.2. NEW
	Description: The destination port identifier to which the Exporting		Description: The destination port identifier to which the Exporting
	Process sends Flow information. For transport protocols such as		Process sends Flow information. For transport protocols such as
	UDP, TCP, and SCTP, this is the destination port number. This		UDP, TCP, and SCTP, this is the destination port number. This
	field MAY also be used for future transport protocols that have		field MAY also be used for future transport protocols that have
	16-bit source port identifiers.		16-bit source port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	destination port field.		destination port field.
	See [RFC9293] for the definition of the TCP destination port		See [RFC9293] for the definition of the TCP destination port
	field.		field.
	See [RFC9260] for the definition of the SCTP destination port		See [RFC9260] for the definition of the SCTP destination port
	number field.		number field.
	See the assigned transport protocol (e.g., UDP, TCP, and SCTP)		See the assigned transport protocol (e.g., UDP, TCP, and SCTP)
	port numbers [https://www.iana.org/assignments/service-names-port-		port numbers [https://www.iana.org/assignments/service-names-port-
	skipping to change at line 399 ¶		skipping to change at line 399 ¶
	4.5.1. OLD		4.5.1. OLD
	Description: The source port identifier from which the Exporting		Description: The source port identifier from which the Exporting
	Process sends Flow information. For the transport protocols UDP,		Process sends Flow information. For the transport protocols UDP,
	TCP, and SCTP, this is the source port number. This field MAY		TCP, and SCTP, this is the source port number. This field MAY
	also be used for future transport protocols that have 16-bit		also be used for future transport protocols that have 16-bit
	source port identifiers. This field may be useful for		source port identifiers. This field may be useful for
	distinguishing multiple Exporting Processes that use the same IP		distinguishing multiple Exporting Processes that use the same IP
	address.		address.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of SCTP.		See [RFC9260] for the definition of SCTP.
	Additional information on defined UDP and TCP port numbers can be		Additional information on defined UDP and TCP port numbers can be
	found at [https://www.iana.org/assignments/service-names-port-		found at [https://www.iana.org/assignments/service-names-port-
	numbers].		numbers].
	4.5.2. NEW		4.5.2. NEW
	Description: The source port identifier from which the Exporting		Description: The source port identifier from which the Exporting
	Process sends Flow information. For transport protocols such as		Process sends Flow information. For transport protocols such as
	UDP, TCP, and SCTP, this is the source port number. This field		UDP, TCP, and SCTP, this is the source port number. This field
	MAY also be used for future transport protocols that have 16-bit		MAY also be used for future transport protocols that have 16-bit
	source port identifiers.		source port identifiers.
	Additional Information: See [RFC0768] for the definition of the UDP		Additional Information: See [RFC768] for the definition of the UDP
	source port field.		source port field.
	See [RFC9293] for the definition of the TCP source port field.		See [RFC9293] for the definition of the TCP source port field.
	See [RFC9260] for the definition of the SCTP source port number		See [RFC9260] for the definition of the SCTP source port number
	field.		field.
	See the assigned transport protocol (e.g., UDP, TCP, and SCTP)		See the assigned transport protocol (e.g., UDP, TCP, and SCTP)
	port numbers [https://www.iana.org/assignments/service-names-port-		port numbers [https://www.iana.org/assignments/service-names-port-
	numbers].		numbers].
	skipping to change at line 740 ¶		skipping to change at line 740 ¶
	Additional Information: See [RFC3022] for the definition of NAT.		Additional Information: See [RFC3022] for the definition of NAT.
	See [RFC1631] for the definition of NAT44.		See [RFC1631] for the definition of NAT44.
	See [RFC6144] for the definition of NAT64.		See [RFC6144] for the definition of NAT64.
	See [RFC6146] for the definition of NAT46.		See [RFC6146] for the definition of NAT46.
	See [RFC6296] for the definition of NAT66.		See [RFC6296] for the definition of NAT66.
	See [RFC0791] for the definition of IPv4.		See [RFC791] for the definition of IPv4.
	See [RFC8200] for the definition of IPv6.		See [RFC8200] for the definition of IPv6.
	6.10.2. NEW		6.10.2. NEW
	Description: This Information Element identifies the NAT type		Description: This Information Element identifies the NAT type
	applied to packets of the Flow.		applied to packets of the Flow.
	Values are listed in the natType registry.		Values are listed in the natType registry.
	skipping to change at line 762 ¶		skipping to change at line 762 ¶
	[https://www.iana.org/assignments/ipfix].		[https://www.iana.org/assignments/ipfix].
	See [RFC3022] for the definition of NAT (commonly named NAT44).		See [RFC3022] for the definition of NAT (commonly named NAT44).
	See [RFC6144] for the definition of NAT46.		See [RFC6144] for the definition of NAT46.
	See [RFC6146] for the definition of NAT64.		See [RFC6146] for the definition of NAT64.
	See [RFC6296] for the definition of NPTv6.		See [RFC6296] for the definition of NPTv6.
	See [RFC0791] for the definition of IPv4.		See [RFC791] for the definition of IPv4.
	See [RFC8200] for the definition of IPv6.		See [RFC8200] for the definition of IPv6.
	6.11. selectorAlgorithm		6.11. selectorAlgorithm
	6.11.1. OLD		6.11.1. OLD
	Description: This Information Element identifies the packet		Description: This Information Element identifies the packet
	selection methods (e.g., Filtering, Sampling) that are applied by		selection methods (e.g., Filtering, Sampling) that are applied by
	the Selection Process. Most of these methods have parameters.		the Selection Process. Most of these methods have parameters.
	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
			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
	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. These types
	the "informationElementDataType" registry). These types are		are registered in the "IPFIX Information Element Data Types"
	registered in the "IPFIX Information Element Data Types" registry.		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].
	6.13. informationElementSemantics		6.13. informationElementSemantics
	skipping to change at line 882 ¶		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
			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
	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" registry).		registry. These types can take the values in the "IPFIX
	These types can take the values in the "IPFIX Information Element		Information Element Units" registry. The special value 0x00
	Units" registry. The special value 0x00 (none) is used to note		(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
	Description: The port number identifying the start of a range of		Description: The port number identifying the start of a range of
	ports. A value of zero indicates that the range start is not		ports. A value of zero indicates that the range start is not
	skipping to change at line 1161 ¶		skipping to change at line 1166 ¶
	6.23. natQuotaExceededEvent		6.23. natQuotaExceededEvent
	6.23.1. OLD		6.23.1. OLD
	Description: This Information Element identifies the type of a NAT		Description: This Information Element identifies the type of a NAT
	Quota Exceeded event. Values for this Information Element are		Quota Exceeded event. Values for this Information Element are
	listed in the "NAT Quota Exceeded Event Type" registry, see		listed in the "NAT Quota Exceeded Event Type" registry, see
	https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-		https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-
	quota-exceeded-event.		quota-exceeded-event.
	Additional Information: See [RFC0791] for the definition of the IPv4		Additional Information: See [RFC791] for the definition of the IPv4
	source address field.		source address field.
	See [RFC3022] for the definition of NAT.		See [RFC3022] for the definition of NAT.
	See [RFC3234] for the definition of middleboxes.		See [RFC3234] for the definition of middleboxes.
	6.23.2. NEW		6.23.2. NEW
	Description: This Information Element identifies the type of a NAT		Description: This Information Element identifies the type of a NAT
	Quota Exceeded event. Values for this Information Element are		Quota Exceeded event. Values for this Information Element are
	skipping to change at line 1190 ¶		skipping to change at line 1195 ¶
	6.24. natThresholdEvent		6.24. natThresholdEvent
	6.24.1. OLD		6.24.1. OLD
	Description: This Information Element identifies a type of a NAT		Description: This Information Element identifies a type of a NAT
	Threshold event. Values for this Information Element are listed		Threshold event. Values for this Information Element are listed
	in the "NAT Threshold Event Type" registry, see		in the "NAT Threshold Event Type" registry, see
	https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-		https://www.iana.org/assignments/ipfix/ipfix.xhtml#ipfix-nat-
	threshold-event.		threshold-event.
	Additional Information: See [RFC0791] for the definition of the IPv4		Additional Information: See [RFC791] for the definition of the IPv4
	source address field.		source address field.
	See [RFC3022] for the definition of NAT.		See [RFC3022] for the definition of NAT.
	See [RFC3234] for the definition of middleboxes.		See [RFC3234] for the definition of middleboxes.
	6.24.2. NEW		6.24.2. NEW
	Description: This Information Element identifies a type of a NAT		Description: This Information Element identifies a type of a NAT
	Threshold event. Values for this Information Element are listed		Threshold event. Values for this Information Element are listed
	skipping to change at line 1402 ¶		skipping to change at line 1407 ¶
	See the internalAddressRealm IE for the detailed definition.		See the internalAddressRealm IE for the detailed definition.
	8. Security Considerations		8. Security Considerations
	This document does not add new security considerations to those		This document does not add new security considerations to those
	already discussed for IPFIX in Section 8 of [RFC7012].		already discussed for IPFIX in Section 8 of [RFC7012].
	9. IANA Considerations		9. IANA Considerations
	Sections 4 to 7 include actions for IANA. These actions are not		Sections 4 to 7 include actions for IANA. These actions are not
	repeated here.		repeated here. IANA has added a reference to this document for each
			of the entries updated per this document.
	IANA has updated the note in the "IPFIX Information Elements"		IANA has updated the note in the "IPFIX Information Elements"
	registry under the "IP Flow Information Export (IPFIX) Entities"		registry under the "IP Flow Information Export (IPFIX) Entities"
	registry group [IANA-IPFIX] as follows:		registry group [IANA-IPFIX] as follows:
	OLD: The columns previously titled "References" and "Requester" have		OLD: The columns previously titled "References" and "Requester" have
	been renamed "Additional Information" and "Reference",		been renamed "Additional Information" and "Reference",
	respectively.		respectively.
	NEW: The columns previously titled "References" and "Requester" have		NEW: The columns previously titled "References" and "Requester" have
	skipping to change at line 1477 ¶		skipping to change at line 1483 ¶
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	10.2. Informative References		10.2. Informative References
	[CCO-NF9FMT]		[CCO-NF9FMT]
	Cisco, "NetFlow Version 9 Flow-Record Format", May 2011,		Cisco, "NetFlow Version 9 Flow-Record Format", May 2011,
	<https://www.cisco.com/en/US/technologies/tk648/tk362/		<https://www.cisco.com/en/US/technologies/tk648/tk362/
	technologies_white_paper09186a00800a3db9.html>.		technologies_white_paper09186a00800a3db9.html>.
	[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,		[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
	DOI 10.17487/RFC0768, August 1980,		DOI 10.17487/RFC0768, August 1980,
	<https://www.rfc-editor.org/info/rfc768>.		<https://www.rfc-editor.org/info/rfc768>.
	[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,		[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791,
	DOI 10.17487/RFC0791, September 1981,		DOI 10.17487/RFC0791, September 1981,
	<https://www.rfc-editor.org/info/rfc791>.		<https://www.rfc-editor.org/info/rfc791>.
	[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,		[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
	DOI 10.17487/RFC1321, April 1992,		DOI 10.17487/RFC1321, April 1992,
	<https://www.rfc-editor.org/info/rfc1321>.		<https://www.rfc-editor.org/info/rfc1321>.
	[RFC1631] Egevang, K. and P. Francis, "The IP Network Address		[RFC1631] Egevang, K. and P. Francis, "The IP Network Address
	Translator (NAT)", RFC 1631, DOI 10.17487/RFC1631, May		Translator (NAT)", RFC 1631, DOI 10.17487/RFC1631, May
	1994, <https://www.rfc-editor.org/info/rfc1631>.		1994, <https://www.rfc-editor.org/info/rfc1631>.
End of changes. 20 change blocks.
	23 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.48.