The
<address>%<scope_type>.<id_in_the_scope>
just does not feel right to me. I don't like notations which allow
writing erroneous expressions, whenever it can be avoided. And, I'm
not yet quite convinced, that this case needs such "error-allowing"
notation.
Thus I prefer
<address>%<id_in_the_scope>
and scope type is from address. And, then make sure every address has
a definite scope designated (the ones for which scope is a bit unclear
are/were :: and "::/3" (eg. those pesky IPv4 mappen and kind
addresses).
[note, currently I plan to use scope=16 internally for those IPv4
addresses, that is outside and above IPv6 scopes. One major use for
this is to distinguish between different 10/8 networks, if they are
connected to node at same time, directly or tunnels]
I thought my proposal was nice for listen sockets, you don't need a
special separate socket option to set the scope, if you want to limit
your listen to any address of specificic scope. With definitions
fe80::%<zoneid> - ANY address in specified link local zone
fec0::%<zoneid> - ANY address in specified site zone
and normal bind as before, the process seems very simple (how this is
reflected in internal data structures of listen socket is different,
implementation matter).
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
