[Enum] EPP for E.164
Kevin McCandless <KMcCandless@illuminet.com> Thu, 23 May 2002 16:24 UTC
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 MAA17026 for <enum-archive@odin.ietf.org>; Thu, 23 May 2002 12:24:22 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA02604 for enum-archive@odin.ietf.org; Thu, 23 May 2002 12:24:42 -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 MAA01951; Thu, 23 May 2002 12:15:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01922 for <enum@optimus.ietf.org>; Thu, 23 May 2002 12:15:27 -0400 (EDT)
Received: from rainier.illuminet.com ([63.116.20.100]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16618 for <enum@ietf.org>; Thu, 23 May 2002 12:15:06 -0400 (EDT)
Received: from olwinexsmtp01.corp.illuminet.com (olwinexsmtp01.corp.illuminet.com [172.20.1.9]) by rainier.illuminet.com (8.8.8/8.8.8) with ESMTP id JAA05540; Thu, 23 May 2002 09:14:55 -0700 (PDT)
Received: by olwinexsmtp01.corp.illuminet.com with Internet Mail Service (5.5.2653.19) id <LB609XM0>; Thu, 23 May 2002 09:14:55 -0700
Message-ID: <1C1EEC765F843E44996971A80682118B014B1427@opwinex02.corp.illuminet.com>
From: Kevin McCandless <KMcCandless@illuminet.com>
To: "'enum@ietf.org'" <enum@ietf.org>
Cc: "'shollenbeck@verisign.com'" <shollenbeck@verisign.com>
Date: Thu, 23 May 2002 09:14:52 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C20274.F8530F10"
Subject: [Enum] EPP for E.164
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 want to bring to everyone's attention to the draft for provisioning E.164 numbers using EPP in a registry environment. http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt <http://search.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-00.txt> . This draft was accepted as an ENUM working group item at the 53rd IETF. We would like to solicit comments for this draft so we can make changes, if necessary, to the draft before the June 24th cut off date for the 54th IETF in Japan. We would like to move forward, as expediently as possible, because the ENUM forum is very interested in having this draft move to RFC before they adopt it into their provisioning process. Please note we have not received any comments from the ENUM list on this draft. So, speak up please! Thank you! Kevin McCandless Senior Network Planner Illuminet (A VeriSign Company) 913-814-6397 kmccandless@verisign.com <mailto:kmccandless@illuminet.com>
- [Enum] EPP for E.164 Kevin McCandless
- Re: [Enum] EPP for E.164 - Start Last Call ??? Richard Shockey
- Re: [Enum] EPP for E.164 - Start Last Call ??? Dave Crocker
- Re: [Enum] EPP for E.164 - Start Last Call ??? Richard Shockey
- RE: [Enum] EPP for E.164 - Start Last Call ??? Pfautz, Penn L, ALVAP
- RE: [Enum] EPP for E.164 - Start Last Call ??? Hollenbeck, Scott
- RE: [Enum] EPP for E.164 - Start Last Call ??? Richard Shockey
- RE: [Enum] EPP for E.164 - Start Last Call ??? Patrik Fältström
- RE: [Enum] EPP for E.164 - Start Last Call ??? Pfautz, Penn L, ALVAP
- RE: [Enum] EPP for E.164 - Start Last Call ??? Hollenbeck, Scott