Re: <draft-ietf-6man-rfc4291bis-09.txt>

[Philip Homburg <[e-mail]>]

>Then you really have to answer my question: if they are not called "interface
>identifier" what are those bits called?

So let me call them 'host part'

>> What we currently have is that requirements on IID depend on the use case.
>
>If they are called something else, the requirements will still depend on
>the use case.

Basically a 'host part' doesn't have any properties. You can say it
identifies an interface, but that is not the case if a 'host part' is 
part of an anycast address.

So a host part has a specific length, which is of course related to the
prefix length. And that's it.

For manual address configuration, a host part doesn't have any properties
except that it should be unique.

For DHCP IA_NA the same applies. Though in the context of DHCP you may also
want to talk about privacy. But that goes way beyond what rfc4291 deals
with. 

Some host parts may be anycast addresses. But by and large whether an
address is anycast is a local flag that needs to be set. There are no specific
requirements for host parts that are anycast addresses.

Only when a host part happens to be used in SLAAC, we get a completely
different story.