IETF Logo Mail Archive

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

"Richard Shockey" <richard@shockey.us> Thu, 05 March 2009 00:30 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 DDD6E28C361 for <enum@core3.amsl.com>; Wed, 4 Mar 2009 16:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.448
X-Spam-Level:
X-Spam-Status: No, score=-1.448 tagged_above=-999 required=5 tests=[AWL=0.816, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 hotE0zaz+npt for <enum@core3.amsl.com>; Wed, 4 Mar 2009 16:30:55 -0800 (PST)
Received: from outbound-mail-315.bluehost.com (outbound-mail-315.bluehost.com [67.222.54.8]) by core3.amsl.com (Postfix) with SMTP id 3197728C36F for <enum@ietf.org>; Wed, 4 Mar 2009 16:30:51 -0800 (PST)
Received: (qmail 9353 invoked by uid 0); 5 Mar 2009 00:24:03 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by outboundproxy6.bluehost.com with SMTP; 5 Mar 2009 00:24:03 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=F1dKJTBYvcQEMBhPGI+6DS5w+tLg4FRLCfiGB+w2oZZm/2qALxYpO7m367/dUdp/hX9kqUTSz4YZ+zI6FPUV43MZg/a75x5WfCcyxxlsDJI4KbS4pfwXJO0jVIpt+Edh;
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 1Lf1SM-0007Zq-Lr; Wed, 04 Mar 2009 17:28:59 -0700
From: Richard Shockey <richard@shockey.us>
To: 'Daryl Malas' <d.malas@cablelabs.com>, enum@ietf.org
References: <C5D459CC.270A%d.malas@cablelabs.com>
In-Reply-To: <C5D459CC.270A%d.malas@cablelabs.com>
Date: Wed, 04 Mar 2009 19:28:55 -0500
Message-ID: <046f01c99d29$5f228e90$1d67abb0$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0470_01C99CFF.764C8690"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmdHzVExhWudUQAA0iPM4Ov8Nc1iwACTzxQ
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}
Cc: '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 00:31:00 -0000

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

v2.23.0 | Report a Bug | By Email