RE: [Enum] Triggering ENUM Queries

Richard Stastny wrote:
> 2. put ONE pointer to a Personal User Agent (PUA), which controls your
> complete communication (including screening, filtering, etc.)
> 
> Of course, for the group heading in the second direction, the whole
> discussion on enumservices is somewhat ridiculous, they say 
> (depending in
> the multiservice they prefer), just put in sip, h323, pres, 
> srs, uci, ....
> 
> And here we are again at the point: as long as we do not have these
> multiservices PUAs in operation, we have to live with the 
> multiple NAPTRs,
> different URIs and services.

I think this is the crux of the issue, e.g. ENUM will ultimately be used as a way of resolving an arbitrary E.164 number into associated PUA services, but the bootstrapping of ENUM may depend on more exposure of these services until the interfaces and protocols for PUA services are well defined and widespread.

This is why the schema matters, since the success of the bootstrap depends on the widespread use of a well-defined, well-understood service schema that doesn't have more than a dozen elements. I continue to assert that the basic intent of the inquiry should be the predominating factor in enumservice selection, e.g.:

- I want to talk to the entity behind this E.164 number
- I want to deposit a message for the entity behind this E.164 number
- I want to enter a chat session with the entity behind this E.164 number
- I want to use a share a collaborative application with the entity behind this E.164 number
- I want to go to the web site for the entity behind this E.164 number
- I want to see my options for communication with the entity behind this E.164 number
- I want to validate the identity of the entity behind this E.164 number

and eventually a wildly successful deployment might lead to:

- I want to post a micropayment to the entity behind this E.164 number
- I want to post an invoice to the entity behind this E.164 number
- I want to get location information for the entity behind this E.164 number (as a PSAP, for instance)

and even more interesting concepts where the intent is very different than communications and the transactions happen elsewhere but use the E.164 number as a means of identity resolution for entities human and machine, organized and grouped under a single entity like a corporation or government or just individual devices or an individual role for a single person. The point is that E.164 numbers are used for all of these purposes today but require active human participation to complete these transactions, so these scenarios aren't as far fetched so long as identity and policy systems are available to the participating entities.

Anyway, the point here is a simple request to stick to the definition of vertical that we started with

-or-

draw a different matrix and call the resulting scheme 'vertical scheme from matrix2' or something that clearly distinguishes it from the original vertical.

--Andy

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