>so, link-local addresses for interface N appears in the host looking like:
>	fe80:N::wwww:xxxx:yyyy:zzzz
>but on the wire as:
>	fe80::wwww:xxxx:yyyy:zzzz
>I got the impression from earlier discussions on the topic that this
>is one of those "seemed like a good idea at the time..." hacks.

	I believe the specification itself is realy twisted.  No other protocol
	suite introduced fully scoped address yet, so how to handle those
	scopes and boundaries need further study and experiences.  The
	solution KAME team came up with is to embed interface index in the
	kernel, because we can only pass in6_addr in most of the kenrel code.
	(another option was to use sockaddr_in6 everywhere in the kernel code,
	but it needed really too much amount of changes - I once tried this
	but stopped this)

	Maybe we'll need to put a hack into ifconfig(8) to print decoded
	version (like printing "fe80::wwww:xxxx:yyyy:zzzz on de0") rather
	than the raw data from the kernel.  From normal users perspetive
	it may be better.

itojun