Re: address portability

halkhatib <halkhatib@ttcinc.com> Wed, 15 July 1998 21:30 UTC

Delivery-Date: Wed, 15 Jul 1998 17:42:00 -0400
Return-Path: cclark
Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id RAA26253 for ietf-outbound.10@ietf.org; Wed, 15 Jul 1998 17:30:02 -0400 (EDT)
Received: from kudonet.com ([165.227.52.1]) by ietf.org (8.8.5/8.8.7a) with SMTP id RAA26074 for <ietf@ietf.org>; Wed, 15 Jul 1998 17:20:01 -0400 (EDT)
Received: by kudonet.com (SMI-8.6/SMI-SVR4) id OAA14106; Wed, 15 Jul 1998 14:19:52 -0700
Received: from kudo20.kudonet.com(209.133.125.67) by kudonet.com via smap (V2.0) id xma014102; Wed, 15 Jul 98 14:19:34 -0700
Received: by kudo20.kudonet.com (SMI-8.6/SMI-SVR4) id OAA29311; Wed, 15 Jul 1998 14:19:15 -0700
Received: from unknown(209.133.124.92) by mail.kudonet.com via smap (V2.0) id xma029301; Wed, 15 Jul 98 14:19:10 -0700
Message-ID: <35AD1CDA.EEDEF31@ttcinc.com>
Date: Wed, 15 Jul 1998 14:19:22 -0700
From: halkhatib <halkhatib@ttcinc.com>
Organization: TTC of Silicon Valley, Inc.
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: mpistone@eurekanet.com
CC: "Steven M. Bellovin" <smb@research.att.com>, "Perry E. Metzger" <perry@piermont.com>, ietf@ietf.org, List@giaw.org
Subject: Re: address portability
References: <35ad0da9.4c3a.0@eurekanet.com>
Content-Type: multipart/mixed; boundary="------------A84F37C4644D696B09E1FA00"

The problem of portability can be resolved by strictly using domain names as
permanent identifiers of portable devices. The dynamically assigned IP address to a
portable device is then associated with the domain name using a DNS server with
dynamic update.

Although the use of domain names has so far been limited to "convenience", we believe
that it is also key to resolving the IPv4 address depletion problem and may eliminate
the need for NAT or IPv6.

Hasan Alkhatib

mpistone@eurekanet.com wrote:

> If you follow the telco solution if would make matters a total mess.  Basicly
> (going from memory here) if the phone number is no longer served by the ILEC
> then they callers ILEC must consult one of several (5?) Natial Phone # Portabilty
> Databases and find out the CLEC that has that number.  Then the ILEC passes
> the call off to the CLEC.
>
> If you translate this to the Internet then the system would first contact the
> backbone that was assigned the original block that the address belongs to.
> If that provider realized it no longer has that network then it contacts a master
> database (or seperate routing table) and forwards the packets over to the new
> provider for that network...  Obviously that idea stinks.  I think everyone
> can agree that portiblity is ideal but not even near practicle right now.
>
> -Mike
>
> >On Wed, 15 Jul 1998, Steven M. Bellovin wrote:
> >
> >> At 09:12 AM 7/15/98 -0700, Patrick Greenwell wrote:
> >> >
> >> >Further, I would love to have a truly permanent, portable IP address(es).
>
> >> >I imagine lots of folks would.
> >>
> >> Right.  Lots of people would.  The problem is that at present, it's
> >> simply not technically feasible.  Portable IP addresses -- even on a
> >> corporate scale, where the units routed are networks, not hosts -- would
>
> >> imply a very large increase in the size of the global routing table.
> >
> >That really depends on what you consider a network. /30? /29? /24?
> >Certainly Sprint could remove their (now) assinine filter tomorrow, and I
> >don't think you would see a very large increase in the size of the global
> >routing table. Most providers announce /24's already anyways.
> >
> >At any rate, I wasn't saying that personalized, individual IP portability
> >is technically feasible at this time, just that it would be nice.
> >Perhaps we could ask the telco industry, who is working on what seems
> >to me to be a fairly similar issue with phone number portability. :-)
> >
> >/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>
> >Patrick Greenwell                                       (800) 299-1288 v
> >                          Systems Administrator         (925) 377-1414 f
> >                                NameSecure
> >\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
>
> >
> >
> >
> >