[Enum] Future outlook for ENUM WG

Cullen Jennings <fluffy@cisco.com> Fri, 29 May 2009 01:51 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: enum@core3.amsl.com
Delivered-To: enum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CE043A6BBC for <enum@core3.amsl.com>; Thu, 28 May 2009 18:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level:
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofpyVkrM-e6G for <enum@core3.amsl.com>; Thu, 28 May 2009 18:51:43 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 69C133A6831 for <enum@ietf.org>; Thu, 28 May 2009 18:51:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,268,1241395200"; d="scan'208";a="312691350"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 29 May 2009 01:53:26 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n4T1rQCo023195; Thu, 28 May 2009 18:53:26 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n4T1rPpC013584; Fri, 29 May 2009 01:53:26 GMT
Message-Id: <3488F382-51CB-4994-8CA4-3DE1040B06F5@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: enum@ietf.org
Impp: xmpp:cullenfluffyjennings@jabber.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 28 May 2009 19:53:25 -0600
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1611; t=1243562006; x=1244426006; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Future=20outlook=20for=20ENUM=20WG |Sender:=20; bh=LfYf6lsKu3mIGrc37udyugI8zpOa9sju/LtlyZYPRaw=; b=HF/hBXu+EtFx4YbibtT5Hv3MdeFwO/aB+hBnbQ29XP8j4cPX/KZ49wdi2d QiipuL+gKlelEe8yjt6GOtZyAXkPaJvNoHCv9FtB4n+14KdwTRGayApUeP3f KZQ90phpYF;
Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: enum-chairs@tools.ietf.org
Subject: [Enum] Future outlook for ENUM WG
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/enum>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2009 01:51:44 -0000

With the publication of the 3761bis, and the enum services guide, I  
view the key work of this WG pretty much done and hope to close the WG  
when the current things in the queue get approved. This does not mean  
I don't expect more ENUM registrations and extensions - I do expect  
many but we should have the expertise to handles these without a WG.  
The enum services guide is the key thing to both make it easier to  
create a registration and provide the advice to make sure that an we  
get it right and only require the resources of an good expert review  
instead of a whole WG.

This does lead to the topic of what about trunk groups. The key  
questions for me as an AD are:

1) are there people that have a need for the trunk groups in enum

2) are there solutions that are architecturally sane and not going to  
cause harm

3) is the approach in draft-malas-enum-trunk-sip the right one to use  
as starting point for the solution

4) where does the expertise exist to make sure the right people are  
involved with the discussions and review

Right now I don't know enough to be able to answer these but my  
current leaning is

1) probably yes

2) yes

3) probably yes - seems like bulk of folks prefer draft-malas to draft- 
ietf-enum-trunkgroup

4) If the answers to the above are yes, where to do the work is easy  
to figure out and no big deal. We will have a place to do the work. It  
is very unlikely it would be done as an enum WG document but I have no  
problem with having the discussion happening on enum list for now.


Cullen <RAI AD>