Subject: Re: [Enum] Now that carrier enum is seperate, will user enum ever be deployed?

From: "Stastny Richard" <[email-masked]>
Date: Thu, 11 Aug 2005 18:57:11 +0200

> It would seem that by seperating the two the pressure is
>off of the carriers to implement the rest of the tree?

This was the basic problem with User ENUM in the first place:
there is no pressure for the carrier to implement User ENUM
at all

User ENUM is regulator and End-User opt-in, the
carreirs have no say whatsoever in User ENUM

Now we have two options and we will see what
will be deployed. It is still the end-user who decides:
Does he use User ENUM or leave it to the carrier to
deploy Carreir ENUM. A smart carrier may offer
their useres to query both.

-richard

________________________________

Von: [email-masked] im Auftrag von Michael Mealling
Gesendet: Do 11.08.2005 14:28
An: [email-masked]
Betreff: [Enum] Now that carrier enum is seperate,will user enum ever be deployed?

Apologies for missing the discussion but after reading
draft-haberler-carrier-enum I'm curious whether the discussion got to
whether or not this would cause user enum to never be deployed in any
useful level? It would seem that by seperating the two the pressure is
off of the carriers to implement the rest of the tree?

-MM

_______________________________________________
enum mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/enum

_______________________________________________
enum mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/enum