> - 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.
As I said at the meeting, I agree with the idea.
Some isssues:
- need to define the mapping between scope and top 4 bit?
my guess is yes. MIB peaple may want to map a value
into alias (e.g. "link") from a remote system.
- should care existing implementations?
yes. But I guess most of such applications use a interface
index for scope_id, so it can be saved either:
- assign scope value (4bit) 0 to link-local.
or
- implementation MAY accept the value 0 in implementation-
specific manner, but SHOULD NOT return 0 for scope (4bit).
- need to introduce new functions to map scope-name and the value?
I hope not to define new functions, so want to _define_
the textual representation (e.g. "link", "site", ...)
instead.
Atsushi Onoe
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
