Hi,
just a clarification, regarding the I-D
(draft-teraoka-mobility-lin6-00.txt), though we will try
to mention briefly in the presentation on Thu session.
LIN6 is not only focusing on the wireless and mobility,
rather trying to solve some technological issues (e.g.,
multihoming) around us.
regards,
Hiroshi Esaki
At 16:43 00/12/13 +0400, Faisal Al-Jundi wrote:
> Hi,
>
> I'm new here.
>
> I just want to ask a question.
>
> All of us know that all networking companies running to wireless technology,
> and as I understand there is lot of electronic machines will have IPv6
> address in the future like TV, ....etc. and the most important is the Future
> GSM, if all mobiles have IPv6 address so we can not think about hierarchy
> levels at all. Also PALM. because if I travel with my mobile from one
> country to another, I need a roaming in current technology, but in the
> future there is no roaming I think there will be like just register this
> IPv6 address with Telco. company in the country i went and it maybe
> automatically because of new features in the IPv6 [auto addressing]!!.
>
> I just ask because I dont have a complete answer for this.
>
> Regards
>
> Faisal Al-Jundi
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Masataka Ohta
> Sent: Wednesday, December 13, 2000 2:37 PM
> To: Jun-ichiro itojun Hagino
> Cc: Fumio Teraoka; [EMAIL PROTECTED]
> Subject: Re: mobility support based on e2e model
>
>
> itojun;
>
> > >> 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.
> >
> > well, if you assign it hierarchical manner, you cannot pack it that
> > well. imagine:
> > - a company asks for IDs,
>
> OK.
>
> > - one-layer-up entity assigns it 8 bit space (for 256 machines),
>
> Huh?
>
> As I wrote:
>
> > >No, not at all. ID space needs no hierarchy for routing nor allginment
> > >for CIDR.
>
> There is no need to make the figure a power of 2.
>
> > - the company actually has only 200 machines and 56 IDs are wasted.
>
> If the company request 200 IDs, the one-layer-up entity can delegate
> exactly 200 IDs.
>
> Or, if the the one-layer-up entity think 200/256 large enough (I think
> this is the case), it can delegate 256 IDs.
>
> > the situation looks exactly the same as the current IPv4 assignment.
>
> No.
>
> Read the following sentense, again and again.
>
> > >No, not at all. ID space needs no hierarchy for routing nor allginment
> ^^^^^^^^^^
> > >for CIDR.
> ^^^^^^^^^
>
> 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]
> --------------------------------------------------------------------
>
>
>
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
=======================================
Hiroshi ESAKI, Ph.D
Associate Professor, Information Technology Center,
University of Tokyo,
2-11-16 Yayoi, Bunkyo-ku,
Tokyo, 113-8658, Japan.
Email [EMAIL PROTECTED]
TEL: +81-3-5684-7303
FAX: +81-3-5684-7775
http://www.itc.u-tokyo.ac.jp
http://hiroshi1.nc.u-tokyo.ac.jp/hiroshi/index.html
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
