Re: [Enum] Comments on draft-ietf-enum-infrastructure-enum-reqs
Dale.Worley@comcast.net Thu, 23 November 2006 16:06 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnH5O-00029b-Me; Thu, 23 Nov 2006 11:06:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnH5N-00029B-Fh for enum@ietf.org; Thu, 23 Nov 2006 11:06:01 -0500
Received: from sccrmhc12.comcast.net ([204.127.200.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnH5M-0005Lz-9n for enum@ietf.org; Thu, 23 Nov 2006 11:06:01 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc12) with ESMTP id <2006112316055901200oraore>; Thu, 23 Nov 2006 16:05:59 +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 kANG5x5K005938 for <enum@ietf.org>; Thu, 23 Nov 2006 11:05:59 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id kANG5xbG005934; Thu, 23 Nov 2006 11:05:59 -0500
Date: Thu, 23 Nov 2006 11:05:59 -0500
Message-Id: <200611231605.kANG5xbG005934@dragon.ariadne.com>
To: enum@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <34DA635B184A644DA4588E260EC0A25A0E28DF4E@ACCLUST02EVS1.ugd.att.com> (ppfautz@att.com)
Subject: Re: [Enum] Comments on draft-ietf-enum-infrastructure-enum-reqs
References: <34DA635B184A644DA4588E260EC0A25A0E28DF4E@ACCLUST02EVS1.ugd.att.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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: "Pfautz, Penn L, GBLAM" <ppfautz@att.com> The requirement you propose is actually much different and, while the initial (e.g., Tier 1) response may not be origin-sensitive, further processing is likely to be since A carrier may have different POIs for different interconnection partners. Hmmm... If that's so, you might want to add some explication of that in the requirements. The current definition suggests to the naive that the mapping from E.164 number to URI is offered to all comers . Indeed, from a technological point of view, it's a fairly complex feature to allow different mappings to be delivered to requests made on behalf of different originating parties. Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] Comments on draft-ietf-enum-infrastructure… Dale.Worley
- RE: [Enum] Comments on draft-ietf-enum-infrastruc… Pfautz, Penn L, GBLAM
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Dale.Worley
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Dale.Worley
- RE: [Enum] Comments on draft-ietf-enum-infrastruc… Stastny Richard
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Otmar Lendl
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Tony Rutkowski
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… lconroy
- RE: [Enum] Comments on draft-ietf-enum-infrastruc… Pfautz, Penn L, GBLAM
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Dale.Worley
- RE: [Enum] Comments on draft-ietf-enum-infrastruc… Stastny Richard
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… lconroy
- Re: [Enum] Comments on draft-ietf-enum-infrastruc… Dale.Worley