From mailman-owner@ietf.org  Mon May  1 05:13:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22598
	for <enum-archive@odin.ietf.org>; Mon, 1 May 2000 05:13:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA18110
	for <enum-web-archive@www.ietf.org>; Mon, 1 May 2000 05:13:11 -0400 (EDT)
Date: Mon, 1 May 2000 05:13:11 -0400 (EDT)
Message-Id: <200005010913.FAA18110@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: enum-web-archive@ns.ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Diffserv Discussion List <diffserv.ietf.org>

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, enum-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for enum-web-archive@www.ietf.org:

List                                     Password // URL
----                                     --------  
enum@ietf.org                            i7hy      
http://www1.ietf.org/mailman/options/enum/enum-web-archive@www.ietf.org


From enum-admin@ietf.org  Mon May  1 11:03:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27700
	for <enum-archive@odin.ietf.org>; Mon, 1 May 2000 11:03:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27676;
	Mon, 1 May 2000 11:03:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27644
	for <enum@ns.ietf.org>; Mon, 1 May 2000 11:03:20 -0400 (EDT)
Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27697
	for <enum@ietf.org>; Mon, 1 May 2000 11:03:18 -0400 (EDT)
Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id LAA29964
	for <enum@ietf.org>; Mon, 1 May 2000 11:03:19 -0400 (EDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id LAA29945
	for <enum@ietf.org>; Mon, 1 May 2000 11:03:19 -0400 (EDT)
Received: from buzz.ons.octel.com by ihrh1.emsr.lucent.com (SMI-8.6/EMS-1.5 Solaris/emsr)
	id KAA16624 for <enum@ietf.org>; Mon, 1 May 2000 10:03:16 -0500
Received: from exdal1.ons.octel.com (exdal1 [155.184.13.201])
	by buzz.ons.octel.com (8.8.8+Sun/8.8.6) with ESMTP id KAA04727
	for <enum@ietf.org>; Mon, 1 May 2000 10:03:17 -0500 (CDT)
Received: by exdal1.ons.octel.com with Internet Mail Service (5.5.2448.0)
	id <HYV12JKV>; Mon, 1 May 2000 10:00:38 -0500
Message-ID: <6B57F36F4FF9D111B30A0008C7F4133703704992@exdal1.ons.octel.com>
From: "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>
To: enum@ietf.org
Date: Mon, 1 May 2000 10:00:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Enum] FW: I-D ACTION:draft-vaudreuil-enum-e164dir-01.txt
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: ENUM Service Specific Provisioning:
                          Principles of Operation
	Author(s)	: A. Brown, G. Vaudreuil
	Filename	: draft-vaudreuil-enum-e164dir-01.txt
	Pages		: 9
	Date		: 27-Apr-00
	
This document outlines the principles for the operation of a
telephone number directory service.  This service provides for the
resolution of telephone numbers into Internet domain name addresses
and service specific directory discovery.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vaudreuil-enum-e164dir-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-vaudreuil-enum-e164dir-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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


From enum-admin@ietf.org  Wed May  3 06:36:26 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28282
	for <enum-archive@odin.ietf.org>; Wed, 3 May 2000 06:36:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA04806;
	Wed, 3 May 2000 06:35:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA04775
	for <enum@ns.ietf.org>; Wed, 3 May 2000 06:35:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28260;
	Wed, 3 May 2000 06:35:21 -0400 (EDT)
Message-Id: <200005031035.GAA28260@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: enum@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 03 May 2000 06:35:21 -0400
Subject: [Enum] I-D ACTION:draft-ietf-enum-e164-dns-00.txt
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Telephone Number Mapping Working Group of the IETF.

	Title		: E.164 number and DNS
	Author(s)	: P. Faltstrom
	Filename	: draft-ietf-enum-e164-dns-00.txt
	Pages		: 11
	Date		: 02-May-00
	
This document discusses the use of DNS for storage of E.164 numbers.
More specifically, how DNS can be used for identifying available
services connected to one E.164 number. Routing of the actual
connection using the service selected using these methods is not
discussed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-enum-e164-dns-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-enum-e164-dns-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-enum-e164-dns-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000502132616.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-enum-e164-dns-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-enum-e164-dns-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000502132616.I-D@ietf.org>

--OtherAccess--

--NextPart--



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


From enum-admin@ietf.org  Mon May  8 12:42:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11684
	for <enum-archive@odin.ietf.org>; Mon, 8 May 2000 12:42:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00828;
	Mon, 8 May 2000 12:41:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00761
	for <enum@ns.ietf.org>; Mon, 8 May 2000 12:40:59 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11630;
	Mon, 8 May 2000 12:40:58 -0400 (EDT)
Received: from [169.254.205.4] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id SAA23816; 
          Mon, 8 May 2000 18:40:51 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04310103b53c9e70e55b@[169.254.205.4]>
In-Reply-To: <H0000283059bd1f6@MHS>
References: <H0000283059bd1f6@MHS>
Date: Mon, 8 May 2000 18:41:29 +0200
To: to-tamura@kdd.co.jp, rshockey@ix.netcom.com, itu+ietf@ietf.org,
        "Rosen, Brian" <brosen@fore.com>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Cc: enum@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: [Enum] Re:Re: [ITU+IETF] NNAR Workshop Issues 4 and 5
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

Has anything happned regarding this? I.e. Brian, both Toshi-san and 
myself belive that the documents are in your lap.

Let me know if you belive differently.

    Regards, Patrik

At 09.55 +0900 00-04-12, to-tamura@kdd.co.jp wrote:
>ITU-T WP1/2 management team agreed to submit the documents to make them
>be part of the IETF RFC series to share the information with the larger
>Internet community.
>
>Format of those documents can be changed and the necessary addition of
>info should be made in conformance to the IETF process.
>However, please understand that the contents cannot easily be changed
>because they have a level of official status in ITU.
>
>I appreciate Brian's very kind offer to reformat the documents.
>
>Toshi
>
>>I'd like to take the opportunity to note that the existence of these
>>documents was discussed at the ENUM WG meeting during IETF 47 in Adelaide,
>>Australia last week.
>>
>>ENUM ID authors and WG participants were asked to thoroughly read these
>>documents and keep in mind the valuable information they contain.
>>
>>I specifically asked our Area Director Scott Bradner ( and IETF-ITU liaison
>>) how we should treat these documents during our work process.
>>
>>It was suggested that these documents ( and any others the Workshop deems
>>relevant to IETF WG items) be made part of the IETF RFC series so that the
>>larger Internet community has access to them.
>>
>>If these documents can be reformatted in the appropriate IETF manner they
>>can be submitted to the IETF RFC editor for publication.
>>
>>If you need any assistance on the process by which documents are submitted
>>to the RFC Editor ..please let me know.
>>
>>http://www.rfc-editor.org/howtopub.html
>>
>>
>>
>>
>>At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote:
>>
>>>Participants in Question 1 (Numbering) of ITU-T Study Group 2 have put
>>>together
>>>some information relevant to E.164-DNS interworking (for Issue 4) during
>>>their recent meeting, and I am providing an ASCII text version of 
>>>the Carrier
>>>Selection supplement to E.164 (for Issue 5).
>>>
>>>These files may be found at the following URLs:
>>>
>>>     http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-info.txt and
>>>     http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt
>>>
>>>-Toshiyuki Tamura
>>>   KDD
>>>   Japan
>>>
>>>
>>>_______________________________________________
>>>ITU+IETF mailing list
>>>ITU+IETF@ietf.org
>>>http://www.ietf.org/mailman/listinfo/itu+ietf
>>
>>
>>Sincerely,  ENUM -WG co-chair
>>
>>
>>
>>
>>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Richard Shockey
>>Shockey Consulting LLC
>>8045 Big Bend Blvd. Suite 110
>>St. Louis, MO 63119
>>Voice 314.918.9020
>>eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
>>INTERNET Mail & IFAX : rshockey@ix.netcom.com
>>GSTN Fax 314.918.9015
>>MediaGate iPost VoiceMail and Fax 800.260.4464
>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>
>>
>
>
>_______________________________________________
>ITU+IETF mailing list
>ITU+IETF@ietf.org
>http://www1.ietf.org/mailman/listinfo/itu+ietf


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


From enum-admin@ietf.org  Mon May  8 12:49:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11833
	for <enum-archive@odin.ietf.org>; Mon, 8 May 2000 12:49:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00958;
	Mon, 8 May 2000 12:49:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA00894
	for <enum@ns.ietf.org>; Mon, 8 May 2000 12:49:16 -0400 (EDT)
Received: from venus.kdd.co.jp (venus.kdd.co.jp [211.4.169.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11829;
	Mon, 8 May 2000 12:49:14 -0400 (EDT)
From: to-tamura@kdd.co.jp
Received: by venus.kdd.co.jp; id BAA32533; Tue, 9 May 2000 01:48:37 +0900 (JST)
Received: from em01sjk.kdd.co.jp (localhost [127.0.0.1])
	by jupiter.kdd.co.jp (8.8.8/3.6W) with ESMTP id BAA08215;
	Tue, 9 May 2000 01:48:36 +0900 (JST)
Received: from localhost (root@localhost)
	by kdd.co.jp (8.8.6) with SMTP id BAA29256;
	Tue, 9 May 2000 01:48:35 +0900 (JST)
X-OpenMail-Hops: 1
Date: Tue, 9 May 2000 01:48:24 +0900
Message-Id: <H000028305e36ed5@MHS>
Subject: Re:[Enum] Re:Re: [ITU+IETF] NNAR Workshop Issues 4 and 5
MIME-Version: 1.0
TO: paf@swip.net
CC: rshockey@ix.netcom.com, itu+ietf@ietf.org, brosen@fore.com, enum@ietf.org
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

Patrik

I have sent the relevant document to Brian who kindly volunteered
document conversion in personal mail last month.



>Has anything happned regarding this? I.e. Brian, both Toshi-san and 
>myself belive that the documents are in your lap.
>
>Let me know if you belive differently.
>
>    Regards, Patrik
>
>At 09.55 +0900 00-04-12, to-tamura@kdd.co.jp wrote:
>>ITU-T WP1/2 management team agreed to submit the documents to make them
>>be part of the IETF RFC series to share the information with the larger
>>Internet community.
>>
>>Format of those documents can be changed and the necessary addition of
>>info should be made in conformance to the IETF process.
>>However, please understand that the contents cannot easily be changed
>>because they have a level of official status in ITU.
>>
>>I appreciate Brian's very kind offer to reformat the documents.
>>
>>Toshi
>>
>>>I'd like to take the opportunity to note that the existence of these
>>>documents was discussed at the ENUM WG meeting during IETF 47 in Adelaide,
>>>Australia last week.
>>>
>>>ENUM ID authors and WG participants were asked to thoroughly read these
>>>documents and keep in mind the valuable information they contain.
>>>
>>>I specifically asked our Area Director Scott Bradner ( and IETF-ITU liaison
>>>) how we should treat these documents during our work process.
>>>
>>>It was suggested that these documents ( and any others the Workshop deems
>>>relevant to IETF WG items) be made part of the IETF RFC series so that the
>>>larger Internet community has access to them.
>>>
>>>If these documents can be reformatted in the appropriate IETF manner they
>>>can be submitted to the IETF RFC editor for publication.
>>>
>>>If you need any assistance on the process by which documents are submitted
>>>to the RFC Editor ..please let me know.
>>>
>>>http://www.rfc-editor.org/howtopub.html
>>>
>>>
>>>
>>>
>>>At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote:
>>>
>>>>Participants in Question 1 (Numbering) of ITU-T Study Group 2 have put
>>>>together
>>>>some information relevant to E.164-DNS interworking (for Issue 4) during
>>>>their recent meeting, and I am providing an ASCII text version of 
>>>>the Carrier
>>>>Selection supplement to E.164 (for Issue 5).
>>>>
>>>>These files may be found at the following URLs:
>>>>
>>>>     http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-info.txt and
>>>>     http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt
>>>>
>>>>-Toshiyuki Tamura
>>>>   KDD
>>>>   Japan
>>>>
>>>>
>>>>_______________________________________________
>>>>ITU+IETF mailing list
>>>>ITU+IETF@ietf.org
>>>>http://www.ietf.org/mailman/listinfo/itu+ietf
>>>
>>>
>>>Sincerely,  ENUM -WG co-chair
>>>
>>>
>>>
>>>
>>>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>Richard Shockey
>>>Shockey Consulting LLC
>>>8045 Big Bend Blvd. Suite 110
>>>St. Louis, MO 63119
>>>Voice 314.918.9020
>>>eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
>>>INTERNET Mail & IFAX : rshockey@ix.netcom.com
>>>GSTN Fax 314.918.9015
>>>MediaGate iPost VoiceMail and Fax 800.260.4464
>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>
>>>
>>
>>
>>_______________________________________________
>>ITU+IETF mailing list
>>ITU+IETF@ietf.org
>>http://www1.ietf.org/mailman/listinfo/itu+ietf
>
>
>_______________________________________________
>enum mailing list
>enum@ietf.org
>http://www1.ietf.org/mailman/listinfo/enum
>
>



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


From enum-admin@ietf.org  Tue May 16 18:24:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13439
	for <enum-archive@odin.ietf.org>; Tue, 16 May 2000 18:24:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27998;
	Tue, 16 May 2000 18:23:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27967
	for <enum@ns.ietf.org>; Tue, 16 May 2000 18:23:58 -0400 (EDT)
Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13435
	for <enum@ietf.org>; Tue, 16 May 2000 18:23:56 -0400 (EDT)
Received: from computer.ix.netcom.com ([209.138.37.239])
	by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA25991
	for <enum@ietf.org>; Tue, 16 May 2000 18:23:56 -0400 (EDT)
Message-Id: <4.3.1.2.20000516171310.00bc2dc0@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 16 May 2000 17:24:32 -0500
To: enum@ietf.org
From: Richard Shockey <rshockey@ix.netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Enum] Update of our Milestones
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org



We've had a request from the IETF Secretariat to update our milestones for 
our work.

Goals and Milestones:
Nov 99Initial draft of Service ENUM Requirements
Jan 00Initial draft of ENUM Protocol
Mar 00Revised draft of ENUM Service Requirements
Mar 00Revised draft of ENUM Protocol
Mar 00Possible draft on relation between ENUM and E.164 or other PSTN 
infrastructure
May 00Initial draft of ENUM protocol MIB.
Jul 00Submit ENUM Requirements document to IESG for publication as 
Informational
Jul 00Submit ENUM Protocol document to IESG for publication as Proposed
Jul 00Possibly submit ENUM relation with E.164 / other PSTN document
Sep 00Submit MIB document to IESG for publication as Proposed

I'd like to get a sense from our authors on where they currently stand and 
what some reasonable timetables for delivery might be.

I've had a general sense that we are not too far off on the basic protocol 
issue (Patrik) but the issues of Redirection has yet to be totally sorted out.

Clearly we need to finish up work on our Goals and Requirements ASAP...

We havent had too much comments on the list on the 3 submissions so far... 
Patrick's draft, the Brown-Vaudreio; Draft and the Peek Draft. I'm assuming 
there has not been too much discussion since these document are so well 
thought out as not to need further review ? :-)

Well Pittsburgh is coming up so if we can move forward that might be helpful.

Your co-chair



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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


From enum-admin@ietf.org  Tue May 16 18:34:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13652
	for <enum-archive@odin.ietf.org>; Tue, 16 May 2000 18:34:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28212;
	Tue, 16 May 2000 18:34:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28181
	for <enum@ns.ietf.org>; Tue, 16 May 2000 18:33:58 -0400 (EDT)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13649
	for <enum@ietf.org>; Tue, 16 May 2000 18:33:57 -0400 (EDT)
Received: from mailee.research.telcordia.com (mailee [192.4.7.23])
	by thumper.research.telcordia.com (8.9.3/8.9.3) with ESMTP id SAA07392;
	Tue, 16 May 2000 18:33:28 -0400 (EDT)
Received: from research.telcordia.com (lhong-pc [192.4.8.89])
	by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id SAA10850;
	Tue, 16 May 2000 18:33:27 -0400 (EDT)
Message-ID: <3921CCB7.22AF1602@research.telcordia.com>
Date: Tue, 16 May 2000 18:33:27 -0400
From: Hong Liu <lhong@research.telcordia.com>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Richard Shockey <rshockey@ix.netcom.com>
CC: enum@ietf.org
Subject: Re: [Enum] Update of our Milestones
References: <4.3.1.2.20000516171310.00bc2dc0@127.0.0.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

Do you have the minutes for the Adelaide meeting? I did not see it, but I may just
miss it. Thanks!

--Hong

Richard Shockey wrote:

> We've had a request from the IETF Secretariat to update our milestones for
> our work.
>
> Goals and Milestones:
> Nov 99Initial draft of Service ENUM Requirements
> Jan 00Initial draft of ENUM Protocol
> Mar 00Revised draft of ENUM Service Requirements
> Mar 00Revised draft of ENUM Protocol
> Mar 00Possible draft on relation between ENUM and E.164 or other PSTN
> infrastructure
> May 00Initial draft of ENUM protocol MIB.
> Jul 00Submit ENUM Requirements document to IESG for publication as
> Informational
> Jul 00Submit ENUM Protocol document to IESG for publication as Proposed
> Jul 00Possibly submit ENUM relation with E.164 / other PSTN document
> Sep 00Submit MIB document to IESG for publication as Proposed
>
> I'd like to get a sense from our authors on where they currently stand and
> what some reasonable timetables for delivery might be.
>
> I've had a general sense that we are not too far off on the basic protocol
> issue (Patrik) but the issues of Redirection has yet to be totally sorted out.
>
> Clearly we need to finish up work on our Goals and Requirements ASAP...
>
> We havent had too much comments on the list on the 3 submissions so far...
> Patrick's draft, the Brown-Vaudreio; Draft and the Peek Draft. I'm assuming
> there has not been too much discussion since these document are so well
> thought out as not to need further review ? :-)
>
> Well Pittsburgh is coming up so if we can move forward that might be helpful.
>
> Your co-chair
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey
> Shockey Consulting LLC
> 8045 Big Bend Blvd. Suite 110
> St. Louis, MO 63119
> Voice 314.918.9020
> eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
> INTERNET Mail & IFAX : rshockey@ix.netcom.com
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> http://www1.ietf.org/mailman/listinfo/enum


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


From enum-admin@ietf.org  Tue May 16 18:46:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13764
	for <enum-archive@odin.ietf.org>; Tue, 16 May 2000 18:46:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28329;
	Tue, 16 May 2000 18:46:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28298
	for <enum@ns.ietf.org>; Tue, 16 May 2000 18:46:18 -0400 (EDT)
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13761
	for <enum@ietf.org>; Tue, 16 May 2000 18:46:15 -0400 (EDT)
Received: from computer.ix.netcom.com ([209.138.37.239])
	by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id SAA32766;
	Tue, 16 May 2000 18:46:10 -0400 (EDT)
Message-Id: <4.3.1.2.20000516174437.00bcbdf0@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 16 May 2000 17:46:48 -0500
To: Hong Liu <lhong@research.telcordia.com>
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: [Enum] Update of our Milestones
Cc: enum@ietf.org
In-Reply-To: <3921CCB7.22AF1602@research.telcordia.com>
References: <4.3.1.2.20000516171310.00bc2dc0@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: enum-admin@ietf.org
Errors-To: enum-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Enum Discussion List <enum.ietf.org>
X-BeenThere: enum@ietf.org

At 06:33 PM 5/16/2000 -0400, you wrote:
>Richard,
>
>Do you have the minutes for the Adelaide meeting? I did not see it, but I 
>may just
>miss it. Thanks!
>
>--Hong

Yes I have them ..I haven't finished editing them... I've been a bad boy :-(
I'm very very sorry I'll have them ready ASAP.


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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


