Re: [Enum] New Draft: Trunk Group Use in ENUM

Lawrence Conroy <lconroy@insensate.co.uk> Thu, 05 March 2009 10:00 UTC

Return-Path: <lconroy@insensate.co.uk>
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 391F028C37E for <enum@core3.amsl.com>; Thu, 5 Mar 2009 02:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 x-O05PMIaTJa for <enum@core3.amsl.com>; Thu, 5 Mar 2009 02:00:56 -0800 (PST)
Received: from insensate.co.uk (norman.insensate.co.uk [213.152.49.123]) by core3.amsl.com (Postfix) with ESMTP id 0FCD228C37B for <enum@ietf.org>; Thu, 5 Mar 2009 02:00:55 -0800 (PST)
Received: from [IPv6???1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 8EA31FDCAD; Thu, 5 Mar 2009 10:01:21 +0000 (GMT)
Message-Id: <95CBE4B6-A8B4-4348-A545-F02F658A4D9E@insensate.co.uk>
From: Lawrence Conroy <lconroy@insensate.co.uk>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
In-Reply-To: <alpine.DEB.2.00.0903050947050.30758@softronics.hoeneisen.ch>
Content-Type: text/plain; charset="WINDOWS-1252"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 05 Mar 2009 10:01:22 +0000
References: <C5D459CC.270A%d.malas@cablelabs.com> <046f01c99d29$5f228e90$1d67abb0$@us> <alpine.DEB.2.00.0903050947050.30758@softronics.hoeneisen.ch>
X-Mailer: Apple Mail (2.930.3)
Cc: IETF ENUM list <enum@ietf.org>, 'Daryl Malas' <d.malas@cablelabs.com>, 'Tom Creighton' <Tom_Creighton@cable.comcast.com>
Subject: Re: [Enum] New Draft: Trunk Group Use in ENUM
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, 05 Mar 2009 10:00:57 -0000

Hi Bernie, folks,
  Agreed.
If there is a crucial reason to force this through the IETF on the old  
track, then let's discuss this at the ENUM WG meeting :).
all the best,
   Lawrence


On 5 Mar 2009, at 08:47, Bernie Hoeneisen wrote:

> Hi Rich
>
> Why don't we use the new process as decribed in
>
>  http://tools.ietf.org/html/draft-ietf-enum-enumservices-guide
>
> for Trunk Group? So, the document does not need to be WG item.
> I believe it is not worth doing anything according to the old  
> process at
> this point in time.
>
> cheers,
> Bernie
>
>
> On Wed, 4 Mar 2009, Richard Shockey wrote:
>
>> To the list ..
>>
>> FYI this draft essentially supersedes the previous draft that Tom  
>> Creighton
>> and I co authored earlier.
>>
>> As far as I’m personally concerned this is still a legitimate WG  
>> item as it
>> describes, in another way , work we had already approved. It does  
>> have
>> significant applicability in the market today.
>>
>> I have no issues with this proceeding as a ENUM WG document unless  
>> there are
>> objections.  We are close to closure but fast tracking this to WGLC  
>> could be
>> of help to operators looking at this type of function.
>>
>> Comments? Any objections to a fast track?
>>
>> From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On  
>> Behalf Of
>> Daryl Malas
>> Sent: Wednesday, March 04, 2009 6:16 PM
>> To: enum@ietf.org
>> Cc: Tom Creighton
>> Subject: [Enum] New Draft: Trunk Group Use in ENUM
>>
>> All,
>> We have submitted a new draft describing another method for  
>> incorporating
>> trunk group information in an ENUM response.
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>     Title           : Trunk Group Use in ENUM
>>     Author(s)       : D. Malas, T. Creighton
>>     Filename        : draft-malas-enum-trunk-sip-00.txt
>>     Pages           : 7
>>     Date            : 2009-03-04
>> This document concludes that incorporating trunk group parameters
>> into an Electronic Number (ENUM) response for the Session Initiation
>> Protocol (SIP) [RFC3261] service URI is a more effective approach
>> compared to defining a new ENUM service type for a 'trunk'.  Upon
>> further review of the existing ENUM trunk group draft
>> [I-D.ietf-enum-trunkgroup] and practical operator experience, this
>> draft recommends the use of the current trunk group contexts as
>> defined in [RFC4904] as additional parameters in the E2U+SIP
>> enumservice NAPTR record [RFC3403] URI.
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-malas-enum-trunk-sip-00.txt
>> Regards,
>> Daryl
>> -----------------
>> Daryl Malas
>> CableLabs
>> (o) +1 303 661 3302
>> (f) +1 303 661 9199
>> mailto:d.malas@cablelabs.com
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www.ietf.org/mailman/listinfo/enum