[Enum] "This is a contribution to educate us..." ?

"Jim Fleming" <JimFleming@ameritech.net> Thu, 20 February 2003 16:41 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20597 for <enum-archive@odin.ietf.org>; Thu, 20 Feb 2003 11:41:29 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KGm8327424 for enum-archive@odin.ietf.org; Thu, 20 Feb 2003 11:48:08 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGm7p27419; Thu, 20 Feb 2003 11:48:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGl2p27338 for <enum@optimus.ietf.org>; Thu, 20 Feb 2003 11:47:02 -0500
Received: from mailhost.chi1.ameritech.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20528 for <enum@ietf.org>; Thu, 20 Feb 2003 11:39:52 -0500 (EST)
Received: from repligate ([67.36.179.41]) by mailhost.chi1.ameritech.net (InterMail vM.4.01.02.17 201-229-119) with SMTP id <20030220160248.FJGT3860.mailhost.chi1.ameritech.net@repligate> for <enum@ietf.org>; Thu, 20 Feb 2003 10:02:48 -0600
Message-ID: <1b7e01c2d8f9$91e5fba0$8500a8c0@repligate>
From: Jim Fleming <JimFleming@ameritech.net>
To: enum@ietf.org
References: <90B62898D7B43B448D1A7297980A8C5F6CE5B1@opwinex01.corp.illuminet.com>
Date: Thu, 20 Feb 2003 10:03:04 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Enum] "This is a contribution to educate us..." ?
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Id: Enum Discussion List <enum.ietf.org>
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-Transfer-Encoding: 7bit

From: "Kevin McCandless" <KMcCandless@verisign.com>
"This is a contribution to educate us..."
================================

It appears that education, especially in the .US, is very one-sided...
...do you really think enlightened people are fooled any more ?

Jim Fleming
http://IPv8.isfun.net


----- Original Message ----- 
From: "Kevin McCandless" <KMcCandless@verisign.com>
To: "Jeff Williams" <jwkckid1@ix.netcom.com>
Cc: <enum@ietf.org>
Sent: Thursday, February 20, 2003 8:37 AM
Subject: RE: [Enum] RFC 3482 on Number Portability in the Global Switched Telephone Network (GSTN): An Overview


> Jeff:
> 
> This is a contribution to educate us on Number Portability.  We should be
> glad that a company like Neustar understands this complex service.  What it
> has to do with ENUM is still anyone's guess.
> 
> K...
> 
> > -----Original Message-----
> > From: Stastny Richard [mailto:Richard.Stastny@oefeg.at]
> > Sent: Thursday, February 20, 2003 3:16 AM
> > To: Jeff Williams; rfc-editor@rfc-editor.org
> > Cc: enum@ietf.org; mark.foster@neustar.biz; tom.mcgarry@neustar.biz;
> > james.yu@neustar.biz; Jeff Neuman
> > Subject: RE: [Enum] RFC 3482 on Number Portability in the Global
> > Switched Telephone Network (GSTN): An Overview
> > 
> > 
> > Jeff,
> > I do not read this.
> > So what is your problem with this informational document?
> > I there anything wrong in it?
> > Richard
> > 
> > > -----Original Message-----
> > > From: Jeff Williams [mailto:jwkckid1@ix.netcom.com] 
> > > Sent: Thursday, February 20, 2003 7:13 AM
> > > To: rfc-editor@rfc-editor.org
> > > Cc: enum@ietf.org; mark.foster@neustar.biz; 
> > > tom.mcgarry@neustar.biz; james.yu@neustar.biz; Jeff Neuman
> > > Subject: Re: [Enum] RFC 3482 on Number Portability in the 
> > > Global Switched Telephone Network (GSTN): An Overview
> > > 
> > > 
> > > RFC Editor and all,
> > > 
> > >   Looks an awful lot like a Nuestar/IEGF document/RFC to me.  
> > > Has Nuestar taken over a percentage of the IETF recently?
> > > 
> > > rfc-editor@rfc-editor.org wrote:
> > > 
> > > > A new Request for Comments is now available in online RFC 
> > libraries.
> > > >
> > > >         RFC 3482
> > > >
> > > >         Title:      Number Portability in the Global Switched
> > > >                     Telephone Network (GSTN): An Overview
> > > >         Author(s):  M. Foster, T. McGarry, J. Yu
> > > >         Status:     Informational
> > > >         Date:       February 2003
> > > >         Mailbox:    mark.foster@neustar.biz, 
> > > tom.mcgarry@neustar.biz,
> > > >                     james.yu@neustar.biz
> > > >         Pages:      30
> > > >         Characters: 78552
> > > >         Updates/Obsoletes/SeeAlso:    None
> > > >
> > > >         I-D Tag:    draft-ietf-enum-e164-gstn-np-05.txt
> > > >
> > > >         URL:       ftp://ftp.rfc-editor.org/in-notes/rfc3482.txt
> > > >
> > > > This document provides an overview of E.164 telephone number 
> > > > portability (NP) in the Global Switched Telephone Network (GSTN).
> > > >
> > > > NP is a regulatory imperative seeking to liberalize local 
> > telephony 
> > > > service competition, by enabling end-users to retain 
> > > telephone numbers 
> > > > while changing service providers.  NP changes the 
> > > fundamental nature 
> > > > of a dialed E.164 number from a hierarchical physical 
> > > routing address 
> > > > to a virtual address, thereby requiring the transparent 
> > > translation of 
> > > > the later to the former.  In addition, there are various 
> > regulatory 
> > > > constraints that establish relevant parameters for NP 
> > > implementation, 
> > > > most of which are not network technology specific.  
> > > Consequently, the 
> > > > implementation of NP behavior consistent with applicable 
> > regulatory 
> > > > constraints, as well as the need for interoperation with 
> > > the existing 
> > > > GSTN NP implementations, are relevant topics for numerous 
> > > areas of IP
> > > > telephony works-in-progress with the IETF.
> > > >
> > > > This document is a product of the Telephone Number 
> > Mapping Working 
> > > > Group of the IETF.
> > > >
> > > > This memo provides information for the Internet 
> > community.  It does 
> > > > not specify an Internet standard of any kind.  
> > Distribution of this 
> > > > memo is unlimited
> > > >
> > > > This announcement is sent to the IETF list and the RFC-DIST list. 
> > > > Requests to be added to or deleted from the IETF 
> > distribution list 
> > > > should be sent to IETF-REQUEST@IETF.ORG.  Requests to be 
> > > added to or 
> > > > deleted from the RFC-DIST distribution list should be sent to 
> > > > RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> > > >
> > > > Details on obtaining RFCs via FTP or EMAIL may be obtained 
> > > by sending 
> > > > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> > > > help: ways_to_get_rfcs.  For example:
> > > >
> > > >         To: rfc-info@RFC-EDITOR.ORG
> > > >         Subject: getting rfcs
> > > >
> > > >         help: ways_to_get_rfcs
> > > >
> > > > Requests for special distribution should be addressed to 
> > either the 
> > > > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  
> > > > Unless specifically noted otherwise on the RFC itself, 
> > all RFCs are 
> > > > for unlimited distribution.echo Submissions for Requests 
> > > for Comments 
> > > > should be sent to RFC-EDITOR@RFC-EDITOR.ORG.  Please 
> > > consult RFC 2223, 
> > > > Instructions to RFC Authors, for further information.
> > > >
> > > > Joyce K. Reynolds and Sandy Ginoza
> > > > USC/Information Sciences Institute
> > > >
> > > > ...
> > > >
> > > > Below is the data which will enable a MIME compliant Mail Reader 
> > > > implementation to automatically retrieve the ASCII version of the 
> > > > RFCs.
> > > 
> > > Regards,
> > > 
> > > --
> > > Jeffrey A. Williams
> > > Spokesman for INEGroup LLA. - (Over 129k members/stakeholders 
> > > strong!) 
> > > ================================================================
> > > CEO/DIR. Internet Network Eng. SR. Eng. Network data security 
> > > Information Network Eng. Group. INEG. INC. E-Mail 
> > > jwkckid1@ix.netcom.com Contact Number: 214-244-4827 or 214-244-3801
> > > 
> > > 
> > > _______________________________________________
> > > enum mailing list
> > > enum@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/enum
> > > 
> > _______________________________________________
> > enum mailing list
> > enum@ietf.org
> > https://www1.ietf.org/mailman/listinfo/enum
> > 
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www1.ietf.org/mailman/listinfo/enum

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum