[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Enum] IETF, ENUM and NGN



> I think you've missed the point. If an operator has a private tree
> which they use for the operation of their network, it won't ever be
> visible to their end customers. No matter what that domain name is.

Jim,

  even if the overlay is running on some secret server used just for the
internal telco operations, there's at least one big problem left - 
the private tree overlays the public ENUM tree making it inaccessible
and unusable. However, if the intrastructure ENUM is sitting in
some other domain, both are accessible and it's a matter of local policy
in which order they get consulted. 


>     Marian> I'd be quite interested what will be your reaction, if
>     Marian> someone makes a "private" tree overlaying the .UK TLD with
>     Marian> any sort of (possibly invalid) data.
> 
> People do this already. Some people even do this on the internet for
> the root zone. Provided these silly things don't interfere with the
> operation of real internet...

Well, but The question is whether IETF should recommend/advice/support
such silly implementations.


	With kind regards,

		M.


--------------------------------------------------------------------------
----                                                                  ----
----   Marian Durkovic                       network  manager         ----
----                                                                  ----
----   Slovak Technical University           Tel: +421 2 524 51 301   ----
----   Computer Centre, Nam. Slobody 17      Fax: +421 2 524 94 351   ----
----   812 43 Bratislava, Slovak Republic    E-mail/sip: md at bts.sk    ----
----                                                                  ----
--------------------------------------------------------------------------

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