itojun;
> >> and how do you plan to handle the assignment?
> >LIN6-ID should be allocated by registries as IP addresses.
> >> how can we manage the reverse lookup table? it looks close to
> >> impossible to handle reverse DNS delegation for generalized ID.
> >For reverse lookup, LIN6-ID should have hierarchical structure.
> >If we use upper 24 bits of EUI-64 for hierarchical structure,
> >we can support 2^48 (= 2.8x10^13) nodes by a single EUI-64. If the
> >half of the 48-bit space is practically available, 1.4x10^13 nodes
> >can be supported by a single EUI-64. If a single EUI-64 space is
> >exhausted, another EUI-64 can be allocated.
>
> if we do hierarchical LIN6-ID assignment, allocation efficiency will
> follow RFC1715 H-ratio.
No, not at all. ID space needs no hierarchy for routing nor allginment
for CIDR.
The space will have a few levels of organizaional hierarchy (say,
country/local_goverment/site). In each level, assignments can be
tighntly packed and returned ID may be filled.
All such points were discussed in my draft <draft-ohta-ipv6-addr-arch-00.txt>
in March 1995.
Masataka Ohta
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
