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

Duane <duane@e164.org> Thu, 30 November 2006 06:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpfU5-0008TB-1N; Thu, 30 Nov 2006 01:33:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpfU3-0008T5-L6 for enum@ietf.org; Thu, 30 Nov 2006 01:33:23 -0500
Received: from wodka.aus-biz.com ([65.23.153.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpfU2-00006Y-4d for enum@ietf.org; Thu, 30 Nov 2006 01:33:23 -0500
Received: from [172.17.1.113] (unknown [202.10.81.200]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by wodka.aus-biz.com (Postfix) with ESMTP id 5991211A677; Thu, 30 Nov 2006 01:33:15 -0500 (EST)
Message-ID: <456E7B25.6010701@e164.org>
Date: Thu, 30 Nov 2006 17:33:09 +1100
From: Duane <duane@e164.org>
User-Agent: Thunderbird 1.5.0.8 (X11/20061115)
MIME-Version: 1.0
To: lconroy <lconroy@insensate.co.uk>
Subject: Re: [Enum] requesting reviewers for draft-ietf-enum-xmpp..
References: <456C52F5.20203@enum.at> <456C9D3C.6040104@e164.org> <20061128225646.GB26860@nic.at> <456CD852.1010303@e164.org> <456DB8A8.5000200@enum.at> <237A2882-907D-4BCA-8FDF-85ACE781FAEF@insensate.co.uk>
In-Reply-To: <237A2882-907D-4BCA-8FDF-85ACE781FAEF@insensate.co.uk>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: enum@ietf.org, Otmar Lendl <lendl@nic.at>, Alexander Mayrhofer <alexander.mayrhofer@enum.at>
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Errors-To: enum-bounces@ietf.org

lconroy wrote:

> However, this does not, in my mind, preclude having another registration
> using that protocol that gives a hint on the kind of interaction that the
> client can expect to start. X-IM:xmpp and Voice:xmpp would help to tell me
> to fire up my Jabber client or to try to find a working Googletalk voice
> program for my Mac (or Linux box, or ...).

As I wrote in a previous email, people won't enter every possible type
of enum service and how they can be contacted.

This isn't how these services are used now, and I don't see it happening
in future for 2 simple reasons, people are lazy, and more importantly
what if I use MSN at work and at home, I use the MS client at work which
supports all the bells and whistles, yet at home I use gaim which
doesn't, yet both instances I use the same login details but I can't be
bothered updating DNS 2 or more times a day just to update what the
current client abilities are.

While it might be possible to get some clients to interact with some
enum roots, I doubt they will interact with all so people may in some
cases be left doing manual updates and this just won't happen, so a
simple I can be contacted by MSN with these details are the best way to
attack this problem due to people being lazy.

So if you make things too complicated people will end up ignoring enum
completely and just falling back to what they already know and use all
the time which makes this whole exercise a complete waste of time.

-- 

Best regards,
 Duane

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