Re: [Enum] requesting reviewers for draft-ietf-enum-xmpp..

Alexander Mayrhofer wrote:

> thanks for the feedback. Actually, i thought about that, too, especially
> considering that a recent registration proposal for "im" has progressed
> (similar to the "pres" service). (draft-ietf-enum-im-service-01.txt)
> 
> However, XMPP is pretty generic, and not limited to those services (similar
> to SIP), so i think it has deserved its own ENUM service. There are a lot of
> proposals to use XMPP for other purposes than im and presence..

I think you are over engineering things, basically if someone lists an
IM address, regardless if it is MSN, YMGSR, XMPP, or whatever,
everything else will need to be negotiated at the client level due to a
number of reasons including privacy and security.

IMHO, it is much better to make things simpler then to require users to
add 50 different types to specify the capabilities in DNS which is
merely a duplication of what is available from the information within
the client.

> Regarding the experimental Enumservice: I have a bit of a problem with "x-"
> services as long as anybody can use any of them for any purpose. it would be
>  perfectly legal to use an "x-im:xmpp" enumservice for a different protocol
> (eg. HTTP, email, or even SIP) - "x-" services are only to be used
> privately, and interopability must not be expected.

Perhaps I shouldn't have suggested x-im so easily, but instead use
E2U+IMSGR instead, or anything really, the point is clients are capable
to send information more securly on their capabilities, rather then
specify all aspects that it can support which no one will ever use.

> So, to conclude, a new "XMPP" Enumservice seemed to be the most logical
> thing to do, considerung the flexibility of XMPP itself..
> 
> And, it's always the same story about "too much flexibility in the NAPTR -
> where to put the protocol, where to put the application"...

I disagree, people already find each other and the software tells them
what the person they are conversing with is capable of already without
the help of NAPTR, they do this using the XMPP address, or ICQ number,
or email address registered with passport or any of the other
established mechanisms.

However what would be nice for things like GAIM and other clients that
support multiple protocols is an easier way to filter for all IM
services available.

>From there the application can display to the end user not only the
services that match what the user is signed up and/or currently
registered against, but so the user can pick and choose which they
actually want added.

-- 

Best regards,
 Duane

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