From exim@www1.ietf.org  Fri Dec  5 08:49:50 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05801
	for <enum-archive@odin.ietf.org>; Fri, 5 Dec 2003 08:49:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASGKt-0004lx-0L
	for enum-archive@odin.ietf.org; Fri, 05 Dec 2003 08:49:35 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5DnYOT018295
	for enum-archive@odin.ietf.org; Fri, 5 Dec 2003 08:49:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASGKL-0004kK-7L; Fri, 05 Dec 2003 08:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASGJj-0004jZ-1Y
	for enum@optimus.ietf.org; Fri, 05 Dec 2003 08:48:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05751
	for <enum@ietf.org>; Fri, 5 Dec 2003 08:48:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASGJh-0001bR-00
	for enum@ietf.org; Fri, 05 Dec 2003 08:48:21 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASGJg-0001ay-00
	for enum@ietf.org; Fri, 05 Dec 2003 08:48:21 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (h-68-165-240-35.MCLNVA23.covad.net [68.165.240.35])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hB5Dsef17619
	for <enum@ietf.org>; Fri, 5 Dec 2003 05:54:40 -0800
Message-Id: <6.0.1.1.2.20031205084416.03e67ec0@popd.ix.netcom.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 05 Dec 2003 08:47:00 -0500
To: enum@ietf.org
From: Richard Shockey <richard@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Enum] Word from the IESG is the 2916bis has been approved
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>


as well as the sip and h.323 registration documents and the IANA registry 
has been approved as well.  The other registration documents are now in review.


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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



From exim@www1.ietf.org  Mon Dec  8 13:50:49 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23829
	for <enum-archive@odin.ietf.org>; Mon, 8 Dec 2003 13:50:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQSo-0007Wv-QL
	for enum-archive@odin.ietf.org; Mon, 08 Dec 2003 13:50:35 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8IoYaf028894
	for enum-archive@odin.ietf.org; Mon, 8 Dec 2003 13:50:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQSK-0007Rl-6Q; Mon, 08 Dec 2003 13:50:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQSB-0007PC-Ce
	for enum@optimus.ietf.org; Mon, 08 Dec 2003 13:49:55 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23775
	for <enum@odin.ietf.org>; Mon, 8 Dec 2003 13:49:39 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1ATQP4-0007yU-EW; Mon, 08 Dec 2003 13:46:42 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <enum@ietf.org>
Message-Id: <E1ATQP4-0007yU-EW@asgard.ietf.org>
Date: Mon, 08 Dec 2003 13:46:42 -0500
Subject: [Enum] Protocol Action: 'The E.164 to URI DDDS Application (ENUM)'
 to Proposed Standard
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>

The IESG has approved following document:

- 'The E.164 to URI DDDS Application (ENUM) '
   <draft-ietf-enum-rfc2916bis-07.txt> as a Proposed Standard

This document is the product of the Telephone Number Mapping Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary

This document specifies how DNS can be used for identifying available
services connected to one E.164 number. It specifically obsoletes RFC
2916 to bring it in line with the Dynamic Delegation Discovery System
(DDDS) Application specification found in RFC 3401 and its companion
RFCs.
 
Working Group Summary
 
  The working group strongly supported advancement of the draft, after
  careful technical review.
 
Protocol Quality
 
  There are currently in prototype use several implementations of this
  draft, and registries of services following the format here are under
  active development. The document was reviewed for the IESG by Allison
  Mankin.


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



From exim@www1.ietf.org  Mon Dec  8 13:59:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24051
	for <enum-archive@odin.ietf.org>; Mon, 8 Dec 2003 13:59:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQb1-0007vX-9i
	for enum-archive@odin.ietf.org; Mon, 08 Dec 2003 13:59:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8Ix3qP030446
	for enum-archive@odin.ietf.org; Mon, 8 Dec 2003 13:59:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQaz-0007uH-CL; Mon, 08 Dec 2003 13:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQau-0007tW-MW
	for enum@optimus.ietf.org; Mon, 08 Dec 2003 13:58:56 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24033
	for <enum@odin.ietf.org>; Mon, 8 Dec 2003 13:58:39 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1ATQaY-0008Fo-1D; Mon, 08 Dec 2003 13:58:34 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <enum@ietf.org>
Message-Id: <E1ATQaY-0008Fo-1D@asgard.ietf.org>
Date: Mon, 08 Dec 2003 13:58:34 -0500
Subject: [Enum] Protocol Action: 'enumservice registration for SIP
 Addresses-of-Record' to Proposed Standard
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>

The IESG has approved following document:

- 'enumservice registration for SIP Addresses-of-Record '
   <draft-ietf-enum-sip-01.txt> as a Proposed Standard

This document is the product of the Telephone Number Mapping Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary
 
   This document registers an ENUM service for SIP (the Session
   Initiation Protocol), pursuant to the guidelines in RFC2916bis.
   Specifically, this document focuses on provisioning SIP addresses-of-
   record in ENUM.  In particular it registers the E2U+SIP service.

  Working Group Summary
 
 There was no working group dissent about specifying this service, or
 about the particulars of the specification.  It was well-reviewed in the
 Working Group.

 Protocol Quality

 The specification was reviewed for the IESG by Allison Mankin.  It takes
 some care to lay out privacy in addition to security considerations.  

RFC Editor Note

Add to the end of the Security Considerations:

  An analysis of threats specific to the dependence of ENUM on
  the DNS, and the applicability of DNSSEC [##] to these, is
  provided in [1].

Append to the Informative References:

[##]  R. Arends, et al, Protocol Modifications for the DNS Security
         Extensions, draft-ietf-dnsext-dnssec-protocol-03.txt


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



From exim@www1.ietf.org  Mon Dec  8 14:01:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24138
	for <enum-archive@odin.ietf.org>; Mon, 8 Dec 2003 14:01:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQcy-00087o-4r
	for enum-archive@odin.ietf.org; Mon, 08 Dec 2003 14:01:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8J13wu031115
	for enum-archive@odin.ietf.org; Mon, 8 Dec 2003 14:01:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQcx-00084a-0w; Mon, 08 Dec 2003 14:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATQcp-00082f-7m
	for enum@optimus.ietf.org; Mon, 08 Dec 2003 14:00:55 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24110
	for <enum@odin.ietf.org>; Mon, 8 Dec 2003 14:00:39 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1ATQbq-0008JC-CF; Mon, 08 Dec 2003 13:59:54 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <enum@ietf.org>
Message-Id: <E1ATQbq-0008JC-CF@asgard.ietf.org>
Date: Mon, 08 Dec 2003 13:59:54 -0500
Subject: [Enum] Protocol Action: 'ENUM Service Registration for H.323 URL'
 to Proposed Standard
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>

The IESG has approved following document:

- 'ENUM Service Registration for H.323 URL '
   <draft-ietf-enum-h323-01.txt> as a Proposed Standard

This document is the product of the Telephone Number Mapping Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary

This document registers an ENUM service for  ITU-T Recommendation
H.323 according to specifications and guidelines in RFC2916bis. 
In particular it is the specification of the E2U+H23 ENUM service.  It 
provides ENUM support for multimedia communications deployed using
H.323.

Working Group Summary

There was no working group dissent about specifying this service, or
about the particulars of the specification.  It was well-reviewed in the
Working Group.

Protocol Quality

The specification was reviewed for the IESG by Allison Mankin.

RFC Editor Note

Remove the word URL from the title so that the title becomes
"ENUM Service Registration for H.323".

Remove the citations for RFC 2916bis and H.323 in the abstract.  They
can be silently removed without any replacement.

Add to the end of the Security Considerations:

  An analysis of threats specific to the dependence of ENUM on
  the DNS, and the applicability of DNSSEC [##] to these, is
  provided in [3].

Append to the Informative References:

[##]  R. Arends, et al, Protocol Modifications for the DNS Security
         Extensions, draft-ietf-dnsext-dnssec-protocol-03.txt


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



From exim@www1.ietf.org  Thu Dec 11 09:43:58 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02365
	for <enum-archive@odin.ietf.org>; Thu, 11 Dec 2003 09:43:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUS2N-00078l-Am
	for enum-archive@odin.ietf.org; Thu, 11 Dec 2003 09:43:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBBEhVOi027442
	for enum-archive@odin.ietf.org; Thu, 11 Dec 2003 09:43:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUS1t-00077u-Gd; Thu, 11 Dec 2003 09:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUS0y-00076T-23
	for enum@optimus.ietf.org; Thu, 11 Dec 2003 09:42:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02292
	for <enum@ietf.org>; Thu, 11 Dec 2003 09:42:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUS0v-00059b-00
	for enum@ietf.org; Thu, 11 Dec 2003 09:42:01 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUS0u-00058i-00
	for enum@ietf.org; Thu, 11 Dec 2003 09:42:00 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hBBEmNf23630
	for <enum@ietf.org>; Thu, 11 Dec 2003 06:48:23 -0800
Message-Id: <6.0.0.22.2.20031119130438.032b4200@popd.ix.netcom.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 10 Dec 2003 12:24:21 -0500
To: enum@ietf.org
From: Richard Shockey <richard@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Enum] Preliminary ENUM WG Minutes IETF 58 Minneapolis
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>


If there are any corrections or additions to this let me know ASAP.

************

IETF 58 Minneapolis Telephone Number Mapping (ENUM) WG  Meeting

TUESDAY, November 11, 2003

Break 1300-1400 Afternoon Sessions I

TSV enum Telephone Number Mapping WG


Chair(s):
Patrik Faltstrom <paf@cisco.com>
Richard Shockey <rich.shockey@neustar.biz>

Transport Area Advisor:
Allison Mankin  <mankin@psg.com>

Mailing Lists:
General Discussion:enum@ietf.org
To Subscribe: enum-request@ietf.org
In Body: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/

Minutes taken by Scott Hollenbeck [shollenbeck@verisign.com]


-
Agenda description by Rich Shockey


Status of 2916bis (Michael Mealling): comments about typos and
clarifications not yet in, will send in as soon as possible after the 
embargo is over.
Nothing substantive in the IESG comments.


1.  Applicability Statement of CRISP work to ENUM - 15 Min

  Title           : IRIS - An ENUM Registry (ereg) Type for the Internet 
Registry Information Service
         Author(s)       : A. Newton
         Filename        : draft-newton-iris-ereg-01.txt
         Pages           : 33
         Date            : 2003-10-24

This document describes an IRIS (draft-ietf-crisp-iris-core-02.txt )
registry schema for ENUM administrative information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-newton-iris-ereg-01.txt

IRIS for ENUM presentation (Andrew Newton)

CRISP WG update provided; moving forward with IRIS

Applicability (why, who, what): look at use cases

Why: Is a whois service needed for ENUM?

Who: Who will resolve ENUM problems?  Who do you contact?

What: What can go wrong?  What will be done about abuse?

Andy's proposal: specifies a vector for coordination.  Is one part
of a possible answer.  Attempts to be policy neutral.

Applicability: public facing, features for privacy, structured.

Questions/comments:

Lawrence Conroy: Need DNS provider or something else.  May be a tie to the
provisioning system.  Andy: not intended to be tightly coupled.
Publish zone authority information?

Rich Shockey: just as applicable for ENUM as DNS.  Is there a right to find 
zone
authority information: Rich: how implemented is a national
matter.

Willy Wertmueller: Why can't we align both ENUM and DNS?  Andy: that's a
policy decision.  Suggestion: spell it out in the draft.

2.  Potential Informational Document  15 min

Title           : Numbering for VoIP and other IP Communications
>         Author(s)       : R. Stastny
>         Filename        : draft-stastny-enum-numbering-voip-00.txt
>         Pages           : 43
>         Date            : 2003-10-20
>
>This document gives advice in setting up E.164 compatible numbering
>and dialing plans in administrative domains set up for IP
>Communications in general and VoIP applications in detail. After
>explaining numbering and dialing plans in principle, it discusses
>which types of E.164 numbers should be used for IP based terminals,
>to achieve proper routing of calls and other communications on the
>PSTN/ISDN and also on the Internet, using ENUM technology.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-stastny-enum-numbering-voip-00.txt


Description of draft...

SIP-based communications use their own naming and addressing schemes.
Different communities started to use numeric user IDs.

Problem: how to dial other communities or the PSTN.  Quick and dirty
solutions are possible, but not feasible.

Other solutions have been proposed, including standard prefixes,
new numbering and dialing plan for IP, use existing E.164 resource.
The E.164 proposal is the one described.

ENUM Trial lessons learned: basic issues solved, original business
model has problems.  Metcalfe's Law applies.  New approaches needed
(some described).

Questions/comments:

Jon Peterson: Is this an IETF draft?

Richard Shockey: maybe informational
eventually.  Jon: security requirements? Richard: not really, but open to 
input from others.


ENUM Implementation Issues (Lawrence Conroy)


Problem Statement : "This summarizes our experiences of what's "out there" 
in ENUM, and some implementation choices that need to be made. It is 
intended as a guide to what we found when querying different ENUM domains 
(and what we misunderstood at first reading of the standards). Note that 
this covers implementation issues only, NOT protocol issues. However, if 
different implementations share common choices, then behavior can be better 
predicted".


NOT PROTOCOL ISSUES, but no document is completely unambiguous.
Described things seen in practice.  You will hit these, and you will
find some strange things.  Proposal: keep a "living" document to
capture issues and sensible ways of dealing with them.

Described issues: case sensitivity, E2U at which end?

Jon Peterson: should shame people using old 2916 ENUM records!

Michael Mealling: being liberal in what you accept doesn't mean
accept broken stuff.

More issues: non-finals with or without empty service field?

Michael: Not very many cases in ENUM.

Does Order "count" across domains?

Non-final loop treatment
Michael: can detect loop.

Lawrence: yes, but there are choices.

Non-final loop detection

Treatment of NAPTRs with identical preferences

L2R or R2L processing of service field

Richard Shockey: are you planning on writing these up as a draft?
Lawrence: yes.


ENUM Trial updates: Poland (Andrzej Bartosiewicz)
NASK is the admin and tech contact for 8.4.e164.arpa.  Follows national
regulator's guidelines and expectations.

This is first trial attempt.  Present registration policy is based
on administrative decisions.

Operators not involved on the technical side -- not interested?
Some operators involved in defining administrative stuff.

Internet-Draft available

Poland - Use of EPP in provisioning. 10+

http://www.ietf.org/internet-drafts/draft-bartosiewicz-enum-48tld-00.txt

No direct registrations -- only via telecom operators.
Registrar (operator) MUST NOT register numbers administered by
other operators.

Some EPP modifications are used.

Questions:

Lawrence Conroy: do you have any delegations published?  Can I look
at NAPTRs?

Andrzej: yes.  Lawrence: can I see some?  Andrzej: info
is on the RIPE web site.

Korean ENUM Trial Update (Jeonghyun Lee)
ENUM Service Council exists (MIC, Telcos, KRNIC); sets goals

Launched 13 October 2003, API available, www.enum.or.kr

Status: about 2,000 registrations as of 5 November 2003

Both land-line and mobile numbers can be registered

Next steps: trials through end of 2004; commercial in 2005.
Planning to submit I-Ds to IETF.

Questions: (none)


Rich Shockey: out of time, but we need to discuss next steps.

Allison Mankin: need to talk about planned documents.

Rich: also security and privacy.  Allison: OK for WG to exist as mailing
list only.

Rich: is this OK with the group?  Patrik: is it OK to request short slots 
like this one?  Rich  There are also issues involving ongoing Liaison with 
ITU SG2 that may require the WG to stay open but dormant.

Allison: it's reasonable to do this.  The more we hear about issues the better.

Patrik/Richard: Any final issues?  (None raised).

End of meeting.



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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



From exim@www1.ietf.org  Thu Dec 11 16:01:58 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23503
	for <enum-archive@odin.ietf.org>; Thu, 11 Dec 2003 16:01:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUXwA-0008Hv-2k
	for enum-archive@odin.ietf.org; Thu, 11 Dec 2003 16:01:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBBL1T8A031806
	for enum-archive@odin.ietf.org; Thu, 11 Dec 2003 16:01:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUXvh-0008GI-Gp; Thu, 11 Dec 2003 16:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUXv5-0008FJ-2G
	for enum@optimus.ietf.org; Thu, 11 Dec 2003 16:00:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23184
	for <enum@ietf.org>; Thu, 11 Dec 2003 16:00:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUXv3-0000VH-00
	for enum@ietf.org; Thu, 11 Dec 2003 16:00:21 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUXv2-0000TE-00
	for enum@ietf.org; Thu, 11 Dec 2003 16:00:20 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hBBL6jf15153
	for <enum@ietf.org>; Thu, 11 Dec 2003 13:06:45 -0800
Message-Id: <6.0.1.1.2.20031211154447.040f9760@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Thu, 11 Dec 2003 15:45:01 -0500
To: enum@ietf.org
From: Richard Shockey <richard@shockey.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Enum] Fwd: Document Action: 'Using E.164 numbers with the Session
 Initiation Protocol (SIP)' to Informational RFC
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>


FYI

>X-test-idtracker: no
>From: The IESG <iesg-secretary@ietf.org>
>To: IETF-Announce:;
>Cc: Internet Architecture Board <iab@iab.org>,
>    RFC Editor <rfc-editor@rfc-editor.org>, <sipping@ietf.org>
>Subject: Document Action: 'Using E.164 numbers with the Session
>          Initiation Protocol (SIP)' to Informational RFC
>Date: Mon, 08 Dec 2003 15:32:18 -0500
>Sender: owner-ietf-announce@ietf.org
>
>
>The IESG has approved following document:
>
>- 'Using E.164 numbers with the Session Initiation Protocol (SIP) '
>    <draft-ietf-sipping-e164-04.txt> as an Informational RFC
>
>This document is the product of the Session Initiation Proposal
>Investigation Working Group.
>
>The IESG contact persons are Allison Mankin and Jon Peterson.
>
>RFC Editor Note
>
>Add to the end of the Security Considerations:
>
>   An analysis of threats specific to the dependence of ENUM on
>   the DNS, and the applicability of DNSSEC [##] to these, is
>   provided in [1].
>
>Append to the Informative References:
>
>[##]  R. Arends, et al, Protocol Modifications for the DNS Security
>          Extensions, draft-ietf-dnsext-dnssec-protocol-03.txt


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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



From exim@www1.ietf.org  Mon Dec 15 13:55:01 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20326
	for <enum-archive@odin.ietf.org>; Mon, 15 Dec 2003 13:55:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVxrU-0001Pu-Sp
	for enum-archive@odin.ietf.org; Mon, 15 Dec 2003 13:54:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFIsWUG005393
	for enum-archive@odin.ietf.org; Mon, 15 Dec 2003 13:54:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVxqz-0001M2-3g; Mon, 15 Dec 2003 13:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVxqu-0001Lf-1i
	for enum@optimus.ietf.org; Mon, 15 Dec 2003 13:53:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20251;
	Mon, 15 Dec 2003 13:53:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVxqr-0002gu-00; Mon, 15 Dec 2003 13:53:53 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVxqr-0002fy-00; Mon, 15 Dec 2003 13:53:53 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hBFJ0Pf22454;
	Mon, 15 Dec 2003 11:00:25 -0800
Message-Id: <6.0.1.1.2.20031215135226.040c39b8@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 15 Dec 2003 13:53:06 -0500
To: proceedings@ietf.org
From: Richard Shockey <richard@shockey.us>
Cc: enum@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Enum] FINAL: ENUM WG Minutes IETF 58 Minneapolis
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>



IETF 58 Minneapolis Telephone Number Mapping (ENUM) WG  Meeting

TUESDAY, November 11, 2003

Break 1300-1400 Afternoon Sessions I

TSV enum Telephone Number Mapping WG


Chair(s):
Patrik Faltstrom <paf@cisco.com>
Richard Shockey <rich.shockey@neustar.biz>

Transport Area Advisor:
Allison Mankin  <mankin@psg.com>

Mailing Lists:
General Discussion:enum@ietf.org
To Subscribe: enum-request@ietf.org
In Body: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/

Minutes taken by Scott Hollenbeck [shollenbeck@verisign.com]


-
Agenda description by Rich Shockey


Status of 2916bis (Michael Mealling): comments about typos and
clarifications not yet in, will send in as soon as possible after the 
embargo is over.
Nothing substantive in the IESG comments.


1.  Applicability Statement of CRISP work to ENUM - 15 Min

  Title           : IRIS - An ENUM Registry (ereg) Type for the Internet 
Registry Information Service
         Author(s)       : A. Newton
         Filename        : draft-newton-iris-ereg-01.txt
         Pages           : 33
         Date            : 2003-10-24

This document describes an IRIS (draft-ietf-crisp-iris-core-02.txt )
registry schema for ENUM administrative information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-newton-iris-ereg-01.txt

IRIS for ENUM presentation (Andrew Newton)

CRISP WG update provided; moving forward with IRIS

Applicability (why, who, what): look at use cases

Why: Is a whois service needed for ENUM?

Who: Who will resolve ENUM problems?  Who do you contact?

What: What can go wrong?  What will be done about abuse?

Andy's proposal: specifies a vector for coordination.  Is one part
of a possible answer.  Attempts to be policy neutral.

Applicability: public facing, features for privacy, structured.

Questions/comments:

Lawrence Conroy: Need DNS provider or something else.  May be a tie to the
provisioning system.  Andy: not intended to be tightly coupled.
Publish zone authority information?

Rich Shockey: just as applicable for ENUM as DNS.  Is there a right to find 
zone
authority information: Rich: how implemented is a national
matter.

Willy Wertmueller: Why can't we align both ENUM and DNS?  Andy: that's a
policy decision.  Suggestion: spell it out in the draft.

2.  Potential Informational Document  15 min

Title           : Numbering for VoIP and other IP Communications
>         Author(s)       : R. Stastny
>         Filename        : draft-stastny-enum-numbering-voip-00.txt
>         Pages           : 43
>         Date            : 2003-10-20
>
>This document gives advice in setting up E.164 compatible numbering
>and dialing plans in administrative domains set up for IP
>Communications in general and VoIP applications in detail. After
>explaining numbering and dialing plans in principle, it discusses
>which types of E.164 numbers should be used for IP based terminals,
>to achieve proper routing of calls and other communications on the
>PSTN/ISDN and also on the Internet, using ENUM technology.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-stastny-enum-numbering-voip-00.txt


Description of draft...

SIP-based communications use their own naming and addressing schemes.
Different communities started to use numeric user IDs.

Problem: how to dial other communities or the PSTN.  Quick and dirty
solutions are possible, but not feasible.

Other solutions have been proposed, including standard prefixes,
new numbering and dialing plan for IP, use existing E.164 resource.
The E.164 proposal is the one described.

ENUM Trial lessons learned: basic issues solved, original business
model has problems.  Metcalfe's Law applies.  New approaches needed
(some described).

Questions/comments:

Jon Peterson: Is this an IETF draft?

Richard Shockey: maybe informational
eventually.  Jon: security requirements? Richard: not really, but open to 
input from others.


ENUM Implementation Issues (Lawrence Conroy)


Problem Statement : "This summarizes our experiences of what's "out there" 
in ENUM, and some implementation choices that need to be made. It is 
intended as a guide to what we found when querying different ENUM domains 
(and what we misunderstood at first reading of the standards). Note that 
this covers implementation issues only, NOT protocol issues. However, if 
different implementations share common choices, then behavior can be better 
predicted".


NOT PROTOCOL ISSUES, but no document is completely unambiguous.
Described things seen in practice.  You will hit these, and you will
find some strange things.  Proposal: keep a "living" document to
capture issues and sensible ways of dealing with them.

Described issues: case sensitivity, E2U at which end?

Jon Peterson: should shame people using old 2916 ENUM records!

Michael Mealling: being liberal in what you accept doesn't mean
accept broken stuff.

More issues: non-finals with or without empty service field?

Michael: Not very many cases in ENUM.

Does Order "count" across domains?

Non-final loop treatment
Michael: can detect loop.

Lawrence: yes, but there are choices.

Non-final loop detection

Treatment of NAPTRs with identical preferences

L2R or R2L processing of service field

Richard Shockey: are you planning on writing these up as a draft?
Lawrence: yes.


ENUM Trial updates: Poland (Andrzej Bartosiewicz)
NASK is the admin and tech contact for 8.4.e164.arpa.  Follows national
regulator's guidelines and expectations.

This is first trial attempt.  Present registration policy is based
on administrative decisions.

Operators not involved on the technical side -- not interested?
Some operators involved in defining administrative stuff.

Internet-Draft available

Poland - Use of EPP in provisioning. 10+

http://www.ietf.org/internet-drafts/draft-bartosiewicz-enum-48tld-00.txt

No direct registrations -- only via telecom operators.
Registrar (operator) MUST NOT register numbers administered by
other operators.

Some EPP modifications are used.

Questions:

Lawrence Conroy: do you have any delegations published?  Can I look
at NAPTRs?

Andrzej: yes.  Lawrence: can I see some?  Andrzej: info
is on the RIPE web site.

Korean ENUM Trial Update (Jeonghyun Lee)
ENUM Service Council exists (MIC, Telcos, KRNIC); sets goals

Launched 13 October 2003, API available, www.enum.or.kr

Status: about 2,000 registrations as of 5 November 2003

Both land-line and mobile numbers can be registered

Next steps: trials through end of 2004; commercial in 2005.
Planning to submit I-Ds to IETF.

Questions: (none)


Rich Shockey: out of time, but we need to discuss next steps.

Allison Mankin: need to talk about planned documents.

Rich: also security and privacy.  Allison: OK for WG to exist as mailing
list only.

Rich: is this OK with the group?  Patrik: is it OK to request short slots 
like this one?  Rich  There are also issues involving ongoing Liaison with 
ITU SG2 that may require the WG to stay open but dormant.

Allison: it's reasonable to do this.  The more we hear about issues the better.

Patrik/Richard: Any final issues?  (None raised).

End of meeting.



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


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



From exim@www1.ietf.org  Wed Dec 17 13:28:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24824
	for <enum-archive@odin.ietf.org>; Wed, 17 Dec 2003 13:28:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWgP3-0000P4-L6
	for enum-archive@odin.ietf.org; Wed, 17 Dec 2003 13:28:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBHIS9jL001497
	for enum-archive@odin.ietf.org; Wed, 17 Dec 2003 13:28:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWgNw-0000N8-BK; Wed, 17 Dec 2003 13:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWgNg-0000MW-Is
	for enum@optimus.ietf.org; Wed, 17 Dec 2003 13:26:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24688
	for <enum@ietf.org>; Wed, 17 Dec 2003 13:26:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWgNX-0002W3-00
	for enum@ietf.org; Wed, 17 Dec 2003 13:26:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWgN7-0002VI-00
	for enum@ietf.org; Wed, 17 Dec 2003 13:26:09 -0500
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWgN6-0002Qt-00
	for enum@ietf.org; Wed, 17 Dec 2003 13:26:08 -0500
Received: from attrh3i.attrh.att.com ([135.38.62.9])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id hBHIKkAC030495
	for <enum@ietf.org>; Wed, 17 Dec 2003 12:25:11 -0600
Received: from KCCLUST05EVS1.ugd.att.com (135.38.164.87) by attrh3i.attrh.att.com (6.5.032)
        id 3FC0E8E40074024B; Wed, 17 Dec 2003 13:23:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Enum] FINAL: ENUM WG Minutes IETF 58 Minneapolis
Date: Wed, 17 Dec 2003 12:25:11 -0600
Message-ID: <C5ADFC6170F1244CAC760E4204FDC76E1F6AC2@KCCLUST05EVS1.ugd.att.com>
Thread-Topic: [Enum] FINAL: ENUM WG Minutes IETF 58 Minneapolis
Thread-Index: AcPDSVg7YMyBahrBSjaGDJEdKpXKtQBgSX7g
From: "Lind, Steven D, ALABS" <sdlind@att.com>
To: "Richard Shockey" <richard@shockey.us>
Cc: <enum@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
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: quoted-printable



> -----Original Message-----
> From: Richard Shockey [mailto:richard@shockey.us]
> Sent: Monday, December 15, 2003 1:53 PM
> To: proceedings@ietf.org
> Cc: enum@ietf.org
> Subject: [Enum] FINAL: ENUM WG Minutes IETF 58 Minneapolis
[snip]
>=20
> ENUM Trial updates: [snip]
>=20
> Korean ENUM Trial Update (Jeonghyun Lee)
> ENUM Service Council exists (MIC, Telcos, KRNIC); sets goals
>=20
> Launched 13 October 2003, API available, www.enum.or.kr
>=20
> Status: about 2,000 registrations as of 5 November 2003
>=20
> Both land-line and mobile numbers can be registered
>=20
> Next steps: trials through end of 2004; commercial in 2005.
> Planning to submit I-Ds to IETF.
>=20

Just curious: I don't find a delegation for Korea listed on the ITU's
list of approved delegations. Is the Korean trial using a private tree?

Steve Lind

[snip]

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



From exim@www1.ietf.org  Wed Dec 17 19:39:05 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16115
	for <enum-archive@odin.ietf.org>; Wed, 17 Dec 2003 19:39:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWmBZ-00076A-LT
	for enum-archive@odin.ietf.org; Wed, 17 Dec 2003 19:38:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBI0cbNC027285
	for enum-archive@odin.ietf.org; Wed, 17 Dec 2003 19:38:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWmB0-00070n-5I; Wed, 17 Dec 2003 19:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWmAA-0006nz-IW
	for enum@optimus.ietf.org; Wed, 17 Dec 2003 19:37:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16060
	for <enum@ietf.org>; Wed, 17 Dec 2003 19:37:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWmA8-0002Sa-00
	for enum@ietf.org; Wed, 17 Dec 2003 19:37:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWmA7-0002SJ-00
	for enum@ietf.org; Wed, 17 Dec 2003 19:37:08 -0500
Received: from ns1.nic.or.kr ([202.30.50.51] helo=mail.nic.or.kr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWmA6-0002Ry-00
	for enum@ietf.org; Wed, 17 Dec 2003 19:37:06 -0500
Received: from LocalHost ([203.255.208.246])
	by mail.nic.or.kr (v3smtp 8.11.6.9/8.11.0) with SMTP id hBI0ZgK03538;
	Thu, 18 Dec 2003 09:35:43 +0900 (KST)
Message-ID: <00a501c3c4fe$fad66e00$f6d0ffcb@LocalHost>
From: "Sungwoo Shin" <ssw@nic.or.kr>
To: <enum@ietf.org>
Cc: <sdlind@att.com>
Subject: Fw: [Enum] FINAL: ENUM WG Minutes IETF 58 Minneapolis
Date: Thu, 18 Dec 2003 09:36:30 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: base64
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: base64

RGVhciBNci4gTGluZCBldCBhbA0KDQpUaGVyZSdzIG5vIHByaXZhdGUgdHJlZSBhbmQgbm8gcGxh
biB0byB1c2UgYW55dGhpbmcgb3RoZXIgdGhhbiBlMTY0LmFycGEuDQpJbiB0aGUgS29yZWFuIEVO
VU0gdHJpYWwsIGxpa2UgeW91ciBwb2ludGluZyBvdXQsIGUxNjQuYXJwYSBpcyBub3QgYmVpbmcN
CiB1c2VkIGF0IHRoaXMgbW9tZW50ICwgYXMgd2UgYXJlIHN0aWxsIGluIHRoZSBkZWxlZ2F0aW9u
IHByb2Nlc3MgaW50ZXJuYWxseS4NCg0KU2V2ZXJhbCB0eXBlcyBvZiBFTlVNIFVzZXIgQVBJIGhh
ZCBiZWVuIGRldmVsb3BlZCBmb3IgdGhlIHRyaWFsIA0KYW5kIGN1cnJlbnQgc2V0LXVwIG1ha2Vz
IHF1ZXJpZXMgdG8gYmUgYm91bmQgZm9yIEtvcmVhbiBFTlVNIEROUy4NCklmIEVOVU0gbmF0aW9u
YWwgY29kZSBpcyBkZWxlZ2F0ZWQsIHRoZXJlJ3Mgbm8gd29uZGVyIHRoYXQgd2Ugd2lsbCANCmNo
YW5nZSBBUElzIHNldHRpbmcgYW5kIG1ha2UgY29ubmVjdGlvbiB0byBFTlVNIHJvb3QgZG9tYWlu
LiAgDQoNCkkgaG9wZSB0aGlzIHdpbGwgaGVscCB5b3UgdG8gdW5kZXJzdGFuZC4gIA0KDQpTdW5n
d29vIFNoaW4gIA0KSkggTGVlDQoNCj4gDQo+IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0g
DQo+IEZyb206ICJMaW5kLCBTdGV2ZW4gRCwgQUxBQlMiIDxzZGxpbmRAYXR0LmNvbT4NCj4gVG86
ICJSaWNoYXJkIFNob2NrZXkiIDxyaWNoYXJkQHNob2NrZXkudXM+DQo+IENjOiA8ZW51bUBpZXRm
Lm9yZz4NCj4gU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDE4LCAyMDAzIDM6MjUgQU0NCj4gU3Vi
amVjdDogUkU6IFtFbnVtXSBGSU5BTDogRU5VTSBXRyBNaW51dGVzIElFVEYgNTggTWlubmVhcG9s
aXMNCj4gDQo+IA0KPiA+IA0KPiA+IA0KPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cj4gPiA+IEZyb206IFJpY2hhcmQgU2hvY2tleSBbbWFpbHRvOnJpY2hhcmRAc2hvY2tleS51c10N
Cj4gPiA+IFNlbnQ6IE1vbmRheSwgRGVjZW1iZXIgMTUsIDIwMDMgMTo1MyBQTQ0KPiA+ID4gVG86
IHByb2NlZWRpbmdzQGlldGYub3JnDQo+ID4gPiBDYzogZW51bUBpZXRmLm9yZw0KPiA+ID4gU3Vi
amVjdDogW0VudW1dIEZJTkFMOiBFTlVNIFdHIE1pbnV0ZXMgSUVURiA1OCBNaW5uZWFwb2xpcw0K
PiA+IFtzbmlwXQ0KPiA+ID4gDQo+ID4gPiBFTlVNIFRyaWFsIHVwZGF0ZXM6IFtzbmlwXQ0KPiA+
ID4gDQo+ID4gPiBLb3JlYW4gRU5VTSBUcmlhbCBVcGRhdGUgKEplb25naHl1biBMZWUpDQo+ID4g
PiBFTlVNIFNlcnZpY2UgQ291bmNpbCBleGlzdHMgKE1JQywgVGVsY29zLCBLUk5JQyk7IHNldHMg
Z29hbHMNCj4gPiA+IA0KPiA+ID4gTGF1bmNoZWQgMTMgT2N0b2JlciAyMDAzLCBBUEkgYXZhaWxh
YmxlLCB3d3cuZW51bS5vci5rcg0KPiA+ID4gDQo+ID4gPiBTdGF0dXM6IGFib3V0IDIsMDAwIHJl
Z2lzdHJhdGlvbnMgYXMgb2YgNSBOb3ZlbWJlciAyMDAzDQo+ID4gPiANCj4gPiA+IEJvdGggbGFu
ZC1saW5lIGFuZCBtb2JpbGUgbnVtYmVycyBjYW4gYmUgcmVnaXN0ZXJlZA0KPiA+ID4gDQo+ID4g
PiBOZXh0IHN0ZXBzOiB0cmlhbHMgdGhyb3VnaCBlbmQgb2YgMjAwNDsgY29tbWVyY2lhbCBpbiAy
MDA1Lg0KPiA+ID4gUGxhbm5pbmcgdG8gc3VibWl0IEktRHMgdG8gSUVURi4NCj4gPiA+IA0KPiA+
IA0KPiA+IEp1c3QgY3VyaW91czogSSBkb24ndCBmaW5kIGEgZGVsZWdhdGlvbiBmb3IgS29yZWEg
bGlzdGVkIG9uIHRoZSBJVFUncw0KPiA+IGxpc3Qgb2YgYXBwcm92ZWQgZGVsZWdhdGlvbnMuIElz
IHRoZSBLb3JlYW4gdHJpYWwgdXNpbmcgYSBwcml2YXRlIHRyZWU/DQo+ID4gDQo+ID4gU3RldmUg
TGluZA0KPiA+IA0KPiA+IFtzbmlwXQ0KPiA+IA0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gZW51bSBtYWlsaW5nIGxpc3QNCj4gPiBlbnVt
QGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZW51
bQ0K


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



From exim@www1.ietf.org  Thu Dec 18 15:33:01 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15560
	for <enum-archive@odin.ietf.org>; Thu, 18 Dec 2003 15:33:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4oy-0006lT-8t
	for enum-archive@odin.ietf.org; Thu, 18 Dec 2003 15:32:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIKWWrG025954
	for enum-archive@odin.ietf.org; Thu, 18 Dec 2003 15:32:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4oU-0006WB-Kl; Thu, 18 Dec 2003 15:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4nz-0006NN-0S
	for enum@optimus.ietf.org; Thu, 18 Dec 2003 15:31:31 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15329;
	Thu, 18 Dec 2003 15:31:28 -0500 (EST)
Message-Id: <200312182031.PAA15329@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: Thu, 18 Dec 2003 15:31:28 -0500
Subject: [Enum] I-D ACTION:draft-ietf-enum-pres-00.txt
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>

--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		: Enumservice Registration for Presence Services
	Author(s)	: J. Peterson
	Filename	: draft-ietf-enum-pres-00.txt
	Pages		: 8
	Date		: 2003-12-18
	
This document registers an ENUM service for presence services (as
   described in RFC2778 [2]) pursuant to the guidelines in RFC2916bis
   [1].  Specifically, this document focuses on provisioning pres URIs
   in ENUM.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-pres-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-pres-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:	<2003-12-18142928.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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



