Re: [Enum] Comments on draft-ietf-enum-infrastructure-enum-reqs

Dale.Worley@comcast.net Mon, 27 November 2006 20:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gomis-0000Xt-0e; Mon, 27 Nov 2006 15:05:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gomiq-0000Xk-Bp for enum@ietf.org; Mon, 27 Nov 2006 15:05:00 -0500
Received: from sccrmhc13.comcast.net ([63.240.77.83]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gomip-0003ok-0y for enum@ietf.org; Mon, 27 Nov 2006 15:05:00 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc13) with ESMTP id <2006112720043801300arrkke>; Mon, 27 Nov 2006 20:04:58 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id kARK4c69009036 for <enum@ietf.org>; Mon, 27 Nov 2006 15:04:38 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id kARK4ckR009032; Mon, 27 Nov 2006 15:04:38 -0500
Date: Mon, 27 Nov 2006 15:04:38 -0500
Message-Id: <200611272004.kARK4ckR009032@dragon.ariadne.com>
To: enum@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <20061123165645.GA26860@nic.at> (lendl@nic.at)
Subject: Re: [Enum] Comments on draft-ietf-enum-infrastructure-enum-reqs
References: <34DA635B184A644DA4588E260EC0A25A0E28DF4E@ACCLUST02EVS1.ugd.att.com> <200611231605.kANG5xbG005934@dragon.ariadne.com> <20061123165645.GA26860@nic.at>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
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>
Errors-To: enum-bounces@ietf.org

   From: Otmar Lendl <lendl@nic.at>

   I agree with Richard here: I-ENUM should return an AoR which act
   as a "name" and does not contain source specific routing information.

   It may well be that further processing is done on this AoR that leads
   to different ingress points depending on the source network.

   That, though, is out of scope for I-ENUM and thus need not be
   mentioned in this document.

If the carriers who are going to be the ones using I-ENUM need to have
source-specific routing, we need to make sure that the I-ENUM system
permits source-specific routing, in some method or another.  Given its
apparent importance, the requirements should at least mention the
subject and require that we not generate a standard which cannot
support source-specific routing.

Although I agree that it would probably be best not to have
source-specificity in the mapping to the SIP AoR, but rather
downstream in processing from there.

Dale

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