Re: address portability
mpistone@eurekanet.com Wed, 15 July 1998 20:20 UTC
Delivery-Date: Wed, 15 Jul 1998 16:30:13 -0400
Return-Path: cclark
Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id QAA24562 for ietf-outbound.10@ietf.org; Wed, 15 Jul 1998 16:20:03 -0400 (EDT)
Received: from sparticus.eurekanet.com (root@sparticus.eurekanet.com [206.150.170.3]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA24510 for <ietf@ietf.org>; Wed, 15 Jul 1998 16:18:23 -0400 (EDT)
From: mpistone@eurekanet.com
Received: from eurekanet.com (root@sparticus.eurekanet.com [206.150.170.3]) by sparticus.eurekanet.com (8.8.5/8.8.5) with SMTP id QAA19521; Wed, 15 Jul 1998 16:14:25 -0400 (EDT)
Sender: mpistone@eurekanet.com
Reply-to: mpistone@eurekanet.com
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: "Perry E. Metzger" <perry@piermont.com>, ietf@ietf.org, List@giaw.org
Date: Wed, 15 Jul 1998 16:14:33 +0400
Subject: Re: address portability
X-Mailer: DMailWeb Web to Mail Gateway 1.5af, http://netwinsite.com/top_mail.htm
Message-id: <35ad0da9.4c3a.0@eurekanet.com>
X-User-Info: 206.150.170.42
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 >\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > > > >
- Re: address portability mpistone
- Re: address portability halkhatib