>> 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. if we annotate the table in RFC1715 section 3
for 48bit case, it should be like follows ("half of the 48-bit space
is available" looks too optimistic).
thank you for all the clarifications.
itojun
Pessimistic (0.14) Optimistic (0.26)
32 bits 3 E+4 (!) 2 E+8
48 bits 5 E+6 3 E+12 <--
64 bits 9 E+8 4 E+16
80 bits 1.6 E+11 2.6 E+20 <-- RFC has a typo
128 bits 8 E+17 2 E+33
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
