RE: [Enum] Re. 2916bis

--On 2002-02-20 15.38 -0600 "Yu, James" <james.yu@neustar.biz> wrote:

> So any valid TN can appear in the tel URL in the NAPTR RR, I see several
> possible ways of handling that particular tel URL (TN) if the TN will
> cause charging issue (a U.S. TN mapped to a Russian TN)

You might have the same cost issues when you end up being gatewaying from
one protocol (cheap) to another one (expensive).

So, it is always important when doing gatewaying like this that even if the
NAPTR have a priority that the called party can set, the calling party or
someone which act on behalf of the called party _have_to_ apply a policy
for what he accepts.

In the IETF we say quite often that we have during the years developed
quite a large number of guns, but just because I have one in my hand, I
don't have to shoot myself in my left foot.

Yes, misconfiguration of NAPTR for ENUM might create problems.

Text about these things should go into the security consideration section
of relevant documents. I can add something general in the 2916bis, but you
who work with individual other things also have to think about these things.

  paf

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