rfc9844v1.txt		rfc9844.txt
	skipping to change at line 140 ¶		skipping to change at line 140 ¶
	identifier is present but is not recognized by appropriate		identifier is present but is not recognized by appropriate
	software.		software.
	5. The National Marine Electronics Association (NMEA) has defined		5. The National Marine Electronics Association (NMEA) has defined
	the "OneNet Marine IPv6 Ethernet Networking Standard" [ONE-NET],		the "OneNet Marine IPv6 Ethernet Networking Standard" [ONE-NET],
	which uses IPv6 link-local addresses exclusively. Proposed		which uses IPv6 link-local addresses exclusively. Proposed
	improvements to the standard include a web page for device		improvements to the standard include a web page for device
	configuration using link-local addresses.		configuration using link-local addresses.
	Such requirements have already spawned hacks to work around current		Such requirements have already spawned hacks to work around current
	limitations (e.g., [LL-HACK], which is no longer maintained and has		limitations (e.g., the hack described in [LL-HACK], which is no
	been archived).		longer maintained and has been archived).
	For all such use cases, it is highly desirable that a complete IPv6		For all such use cases, it is highly desirable that a complete IPv6
	link-local address can be cut and pasted from one UI (such as the		link-local address can be cut and pasted from one UI (such as the
	output from a system command) to another. Since such addresses may		output from a system command) to another. Since such addresses may
	include quite long hexadecimal strings, for example,		include quite long hexadecimal strings, for example,
	"fe80::8d0f:7f26:f5c8:780b%enx525400d5e0fb", any solution except cut-		"fe80::8d0f:7f26:f5c8:780b%enx525400d5e0fb", any solution except cut-
	and-paste is highly error prone.		and-paste is highly error prone.
	3. Relationship to Other Documents		3. Relationship to Other Documents
	skipping to change at line 272 ¶		skipping to change at line 272 ¶
	There is no formal limit on the length of the zone identifier string		There is no formal limit on the length of the zone identifier string
	in [RFC4007]. A UI implementation should apply an appropriate length		in [RFC4007]. A UI implementation should apply an appropriate length
	limit when inputting a zone identifier, in order to minimize the risk		limit when inputting a zone identifier, in order to minimize the risk
	of a buffer overrun. Typically, this limit would be the same as the		of a buffer overrun. Typically, this limit would be the same as the
	host operating system's limit on interface names.		host operating system's limit on interface names.
	[RFC4007] does not specify or restrict the character set allowed in a		[RFC4007] does not specify or restrict the character set allowed in a
	zone identifier. Therefore, each implementation processing zone		zone identifier. Therefore, each implementation processing zone
	identifiers needs to make checks appropriate for the environment it		identifiers needs to make checks appropriate for the environment it
	is used in. For example, a UI implementation should not allow ASCII		is used in. For example, a UI implementation should not allow ASCII
	NULL characters in a zone identifier string as this could cause		NUL characters in a zone identifier string as this could cause
	inconsistencies in subsequent string processing.		inconsistencies in subsequent string processing.
	7. IANA Considerations		7. IANA Considerations
	This document has no IANA actions.		This document has no IANA actions.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	skipping to change at line 327 ¶		skipping to change at line 327 ¶
	in URI-Based Protocols", Work in Progress, Internet-Draft,		in URI-Based Protocols", Work in Progress, Internet-Draft,
	draft-schinazi-httpbis-link-local-uri-bcp-03, 22 February		draft-schinazi-httpbis-link-local-uri-bcp-03, 22 February
	2024, <https://datatracker.ietf.org/doc/html/draft-		2024, <https://datatracker.ietf.org/doc/html/draft-
	schinazi-httpbis-link-local-uri-bcp-03>.		schinazi-httpbis-link-local-uri-bcp-03>.
	[LL-HACK] Jin, P., "Snippets: IPv6 link-local connect hack", 2021,		[LL-HACK] Jin, P., "Snippets: IPv6 link-local connect hack", 2021,
	<https://web.archive.org/web/20210725030713/		<https://web.archive.org/web/20210725030713/
	https://website.peterjin.org/wiki/		https://website.peterjin.org/wiki/
	Snippets:IPv6_link_local_connect_hack>.		Snippets:IPv6_link_local_connect_hack>.
	[ONE-NET] NMEA, "The OneNet Standard for IP Networking of Marine		[ONE-NET] NMEA, "OneNet Marine IPv6 Ethernet Networking Standard",
	Electronic Devices", 2025,		2025, <https://www.nmea.org/nmea-onenet.html>.
	<https://www.nmea.org/nmea-onenet.html>.
	[POSIX] IEEE, "IEEE/Open Group Standard for Information		[POSIX] IEEE, "IEEE/Open Group Standard for Information
	Technology--Portable Operating System Interface (POSIX™)		Technology--Portable Operating System Interface (POSIX™)
	Base Specifications, Issue 8", IEEE Std 1003.1-2024,		Base Specifications, Issue 8", IEEE Std 1003.1-2024,
	DOI 10.1109/IEEESTD.2024.10555529, June 2024,		DOI 10.1109/IEEESTD.2024.10555529, June 2024,
	<https://doi.org/10.1109/IEEESTD.2024.10555529>.		<https://doi.org/10.1109/IEEESTD.2024.10555529>.
	[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.		[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.
	J., and E. Lear, "Address Allocation for Private		J., and E. Lear, "Address Allocation for Private
	Internets", BCP 5, RFC 1918, DOI 10.17487/RFC1918,		Internets", BCP 5, RFC 1918, DOI 10.17487/RFC1918,
End of changes. 3 change blocks.
	6 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48.