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

To clarify: I do believe infrastructure ENUM will deliver a single AoR
to all- and it will be in subsequent processing that differentiation
takes place. I just didn't want to imply that the ultimate PoI derived
would be the same for all.
My apologies for any confusion.

Penn 

-----Original Message-----
From: Otmar Lendl [mailto:lendl@nic.at] 
Sent: Thursday, November 23, 2006 11:57 AM
To: enum@ietf.org
Subject: Re: [Enum] Comments on draft-ietf-enum-infrastructure-enum-reqs

On 2006/11/23 17:11, Dale.Worley@comcast.net wrote:
>    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.

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.

/ol
-- 
< Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer >

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

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