Re: [Enum] WG: New Draft: Trunk Group Use in ENUM RESTART - Secondrequest for guidence

"Richard Shockey" <richard@shockey.us> Thu, 14 May 2009 13:34 UTC

Return-Path: <richard@shockey.us>
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 BE3753A6C2B for <enum@core3.amsl.com>; Thu, 14 May 2009 06:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level:
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.389, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 kFw0O6tYrKpr for <enum@core3.amsl.com>; Thu, 14 May 2009 06:34:47 -0700 (PDT)
Received: from outbound-mail-101.bluehost.com (outbound-mail-101.bluehost.com [69.89.22.11]) by core3.amsl.com (Postfix) with SMTP id B65453A68DD for <enum@ietf.org>; Thu, 14 May 2009 06:34:47 -0700 (PDT)
Received: (qmail 15553 invoked by uid 0); 14 May 2009 13:36:20 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by outboundproxy3.bluehost.com with SMTP; 14 May 2009 13:36:20 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=EOw0bxhalDuj2xiOYX8GI/jQbHSI7nbWclhlIPM/QbNlbkQXAjOTPrTYQtr2xCzILBRkYP/D+rfdRQykIilqNHJQM65pkYt34mATLuEOIrdsfa26tTwplRoGzgJlyt8l;
Received: from pool-173-66-69-164.washdc.fios.verizon.net ([173.66.69.164] helo=rshockeyPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1M4b6i-0005qm-AH; Thu, 14 May 2009 07:36:20 -0600
From: Richard Shockey <richard@shockey.us>
To: 'Alexander Mayrhofer' <alexander.mayrhofer@enum.at>, enum@ietf.org
References: <4A0BD7C8.5050903@enum.at>
In-Reply-To: <4A0BD7C8.5050903@enum.at>
Date: Thu, 14 May 2009 09:35:45 -0400
Message-ID: <017901c9d498$e31e6fb0$a95b4f10$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnUbxcNO9ZGiUOLQyODY7VhiyLbWAAKarEw
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.66.69.164 authed with richard+shockey.us}
Subject: Re: [Enum] WG: New Draft: Trunk Group Use in ENUM RESTART - Secondrequest for guidence
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: Thu, 14 May 2009 13:34:48 -0000

Well at least I got someone on the list to finally comment .. :-) 

Its not going into DISPATCH .it will never see the light of day.



>  -----Original Message-----
>  From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf
>  Of Alexander Mayrhofer
>  Sent: Thursday, May 14, 2009 4:35 AM
>  To: enum@ietf.org
>  Subject: Re: [Enum] WG: New Draft: Trunk Group Use in ENUM RESTART -
>  Secondrequest for guidence
>  
>  
>  Richard, fellow WG members,
>  
>  I agree with Peter, as i think the real question is whether the WG
>  want
>  to continue pursue the draft-ietf-enum-trunkgroup ENUMservice or not.
>  
>  The question whether the group wants to adopt the
>  draft-malas-enum-trunk-sip is seperate from that - but i like the way
>  that Peter proposed.
>  
>  > 1) Is anybody but the authors/editors of the respective drafts
>  believes the WG
>  >    should say anything in this direction (trunk groups). [But see
>  the "price tag"
>  >    under (4)]
>  
>  I think it is somehow *related* to ENUM because of the Enumservice
>  that
>  we are trying to get rid. Otherwise, i don't see why it would fit into
>  ENUM. For example, it might well fit into DISPATCH as well?
>  
>  > 2) Do you agree to abandon the approach in draft-ietf-enum-
>  trunkgroup-00.txt?
>  
>  Yes
>  
>  > 3) Is the content of draft-malas-enum-trunk-sip-00.txt a better
>  start instead?
>  
>  Yes
>  
>  > 4) Is anybody willing to review draft-malas-enum-trunk-sip-00.txt?
>  
>  If it becomes an ENUM WG document, i might have to, being the
>  secretary
>  of the ENUM WG.
>  
>  > Then publish draft-malas-enum-trunk-sip-00.txt as draft-ietf-enum-
>  trunkgroup-01.txt,
>  > changing the intended state to Informational.
>  
>  I would prefer if the WG concensus would be to remove
>  draft-ietf-enum-trunkgroup from the WG "menu" entirely, and
>  documenting
>  the decision in draft-malas-enum-trunk-sip, but find a WG that suits
>  better such SIP operational issues than the ENUM group.
>  
>  The solution that Peter proposed is also viable, if authors and chairs
>  believe that's a faster way. I just don't think the WG should accept
>  new
>  work, given it's current status of being slowly move to the pathology
>  department.
>  
>  Just to make clear: Content-wise, i definitely prefer the solution
>  proposed in draft-malas-enum-trunk-sip. I'm just not entirely happy
>  with
>  the sloppy process.
>  
>  Alex
>  
>  _______________________________________________
>  enum mailing list
>  enum@ietf.org
>  https://www.ietf.org/mailman/listinfo/enum