rfc9164v3.txt		rfc9164.txt
	skipping to change at line 286 ¶		skipping to change at line 286 ¶
	54([44, h'20010db81233'])		54([44, h'20010db81233'])
	54([44, h'20010db8123f'])		54([44, h'20010db8123f'])
	54([44, h'20010db8123012'])		54([44, h'20010db8123012'])
	start with the same 44 bits but are not valid.		start with the same 44 bits but are not valid.
	(Analogous examples can be constructed for IPv4 prefixes.)		(Analogous examples can be constructed for IPv4 prefixes.)
	(2) An encoder MUST then omit any right-aligned (trailing) sequence		(2) An encoder MUST then omit any right-aligned (trailing) sequence
	of bytes that is all zero.		of bytes in which the bytes are all zeros.
	There is no relationship between the number of bytes omitted and the		There is no relationship between the number of bytes omitted and the
	prefix length. For instance, the prefix 2001:db8::/64 is encoded as:		prefix length. For instance, the prefix 2001:db8::/64 is encoded as:
	54([64, h'20010db8'])		54([64, h'20010db8'])
	4.3. Decoder Considerations for Prefixes		4.3. Decoder Considerations for Prefixes
	A decoder MUST check that all unused bits encoded in the byte string		A decoder MUST check that all unused bits encoded in the byte string
	ipv6-prefix-bytes/ipv4-prefix-bytes, i.e., the bits to the right of		ipv6-prefix-bytes/ipv4-prefix-bytes, i.e., the bits to the right of
End of changes. 1 change blocks.
	1 lines changed or deleted		1 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/