IETF Logo Mail Archive

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

Dale.Worley@comcast.net Tue, 28 November 2006 18:56 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp88G-0004bT-Ju; Tue, 28 Nov 2006 13:56:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp88D-0004ZH-Jw for enum@ietf.org; Tue, 28 Nov 2006 13:56:37 -0500
Received: from rwcrmhc14.comcast.net ([204.127.192.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gp88C-0003lb-C2 for enum@ietf.org; Tue, 28 Nov 2006 13:56:37 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (rwcrmhc14) with ESMTP id <20061128185622m14001jnide>; Tue, 28 Nov 2006 18:56:32 +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 kASIuL69012284 for <enum@ietf.org>; Tue, 28 Nov 2006 13:56:21 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id kASIuLZG012280; Tue, 28 Nov 2006 13:56:21 -0500
Date: Tue, 28 Nov 2006 13:56:21 -0500
Message-Id: <200611281856.kASIuLZG012280@dragon.ariadne.com>
To: enum@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <1B8CAE46-706F-45FA-8FA3-E05C8DA1B416@insensate.co.uk> (lconroy@insensate.co.uk)
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> <200611272004.kARK4ckR009032@dragon.ariadne.com> <1B8CAE46-706F-45FA-8FA3-E05C8DA1B416@insensate.co.uk>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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: lconroy <lconroy@insensate.co.uk>

     i-ENUM does not stand alone.
   Source specific routing may well be a requirement of the overall
   architecture, within which i-ENUM plays a part.

   Please explain why it is a requirement of i-ENUM itself (rather than
   other elements specific to the particular communications services  
   offered)?

I would say that it's a requirement that how we design I-ENUM *doesn't
prevent* source-specific routing.  Whether I-ENUM implements
source-specific routing itself is a question to be decided later.

Dale

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

v2.23.0 | Report a Bug | By Email