> So, the basic idea is as follows:
>
> - take 4+28 split.
> - actual mapping from zone to the 28 bit part does not matter, but it
> should not change while the node is running (as discussed in this
> thread)
> - introduce "aliases" for numeric zone IDs to improve readability in
> the textual representation. e.g. "link2" is an alias of a link ID
> whose intra-link id is 2 (i.e. 0x20000002). "site4" is an alias of
> a site ID whose intra-site id is 4 (i.e. 0x50000004). We now allow
> fec0::1234%site4 as well as fec0::1234%1342177284 (1342177284=0x50000004)
> - when a zone ID is used with an address (typically in the sockaddr_in6
> structure), the scope type of the ID must be equal to the scope type
> of the address.
Seems like, to the extent that there are existing applications
which use if_nametoindex() -> sin6_scope_id for link-local addresses,
we need to also support the top 4 being zero as an alias for the
interface or link scope.
Does anybody know of such applications?
Does anybody know of applications doing the reverse (taking sin6_scope_id
and passing it to if_indextoname())?
If nobody on the list knows of such applications we could take the
optimistic path and ignore the existence any such applications...
Erik
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
