Re: [Enum] Re: URI Portability

james.f.baskin@verizon.com Wed, 08 February 2006 17:06 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6sm9-0002WK-Fm; Wed, 08 Feb 2006 12:06:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6sm6-0002VX-Vd for enum@megatron.ietf.org; Wed, 08 Feb 2006 12:06:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10091 for <enum@ietf.org>; Wed, 8 Feb 2006 12:04:55 -0500 (EST)
From: james.f.baskin@verizon.com
Received: from tpamail2.verizon.com ([192.76.82.136]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6syg-0004Ca-9r for enum@ietf.org; Wed, 08 Feb 2006 12:19:42 -0500
Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92]) by tpamail2.verizon.com (8.13.3/8.13.3) with ESMTP id k18H6HIu001106 for <enum@ietf.org>; Wed, 8 Feb 2006 12:06:19 -0500 (EST)
Received: from irvp1cvmma01.vzh.ent.verizon.com (irvp1cvmma01.verizon.com [138.83.34.82]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id k18H5x9m010860 for <enum@ietf.org>; Wed, 8 Feb 2006 12:06:17 -0500 (EST)
Received: from 138.83.34.22 by irvp1cvmma01.vzh.ent.verizon.com with ESMTP (SMTP Relay); Wed, 08 Feb 2006 12:06:01 -0500
X-Server-Uuid: 33D99CC3-91DD-4C5F-B3C4-DE0A72F86AF5
Received: from dwsmtp01.core.verizon.com (dwsmtp01.verizon.com [138.83.35.62]) by coregate1.verizon.com (8.13.3/8.13.3) with ESMTP id k18H5xLi014723 for <enum@ietf.org>; Wed, 8 Feb 2006 11:05:59 -0600 ( CST)
To: Stastny Richard <Richard.Stastny@oefeg.at>
Subject: Re: [Enum] Re: URI Portability
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002
Message-ID: <OFFD6D8F8B.8A667CF3-ON8525710F.005CB3F4-8525710F.005E1CEB@CORE.VERIZON.COM>
Date: Wed, 08 Feb 2006 12:05:51 -0500
X-MIMETrack: Serialize by Router on DWSMTP01/HSVR/Verizon(Release 6.5.4HF453 | August 4, 2005) at 02/08/2006 11:05:59, Serialize complete at 02/08/2006 11:05:59
X-WSS-ID: 6FF4FB7267W439413-01-01
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: enum@ietf.org
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1811698947=="
Sender: enum-bounces@ietf.org
Errors-To: enum-bounces@ietf.org

Richard,

I must be missing something.  As far as I know, individually-owned 
or company-owned domain names ARE portable.  I can have any service 
provider run a web server for my domain.  I can have a separate 
provider handle my email.  I can have lots of providers handle lots 
of different services for me, and I can switch any particular 
service from any provider to any other at any time. 

What kind of portability isn't already implemented?  What portability 
functions are you looking for that aren't available today?

Jim

==========================
Richard Stastny wrote:

IMHO "portability" of domains held by individuals or companies
must be implemented, but not portability within domains held
by an ISP or VoIP SP such as yahoo.com or verizon.net
_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum