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

Dale, folks,
  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)?

all the best,
   Lawrence

On 27 Nov 2006, at 20:04, Dale.Worley@comcast.net wrote:
>    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