Alexandru Petrescu <[EMAIL PROTECTED]> writes:
> Francis Dupont <[EMAIL PROTECTED]> writes:
> > Have you read draft-dupont-ipv6-imei-00.txt?
>
> Hi Francis, thanks for putting the IMEI idea on paper, it's been long
> expected by many circles. I have a remark below, please correct me if
> I misunderstood the conversion.
>
> > The IMEI 330001 53 007826 gives the 0333:0001:5300:7826 (usually
> > written 333:1:5300:7826) interface identifier.
>
> Since IMEI is represented in decimal and addresses in hexa, by doing
> the above it effectively leads to impossibility of use of parts of
> address space. I mean, all IMEI's can be represented into an IPv6
> Interface ID, but certain IPv6 Interface ID's will never have a
> correspondent IMEI. Maybe better can be done.
...I would suggest re-phrasing the following:
"The IMEI 330001 53 007826 gives the 0333:0001:5300:7826 (usually
written 333:1:5300:7826) interface identifier."
into:
"For example, the IMEI 330001 53 007826 gives the Interface ID
300:6072:9ed2. The maximum IMEI 999999 99 999999 is Interface ID
5af3:107a:3fff. The space in the Interface ID starting at
5af3:107a:4000 inclusive and up to ffff:ffff:ffff inclusive can
not represent an Interface ID derived from an IMEI."
Alex
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
