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

Duane <duane@e164.org> Fri, 29 December 2006 03:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H08ZC-0007Lj-02; Thu, 28 Dec 2006 22:37:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H08ZA-0007Le-SG for enum@ietf.org; Thu, 28 Dec 2006 22:37:56 -0500
Received: from wodka.aus-biz.com ([65.23.153.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H08Z5-0001sy-0a for enum@ietf.org; Thu, 28 Dec 2006 22:37:56 -0500
Received: from [172.17.1.113] (unknown [202.10.81.200]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by wodka.aus-biz.com (Postfix) with ESMTP id 189EA11A575; Thu, 28 Dec 2006 22:37:40 -0500 (EST)
Message-ID: <45948D80.2010309@e164.org>
Date: Fri, 29 Dec 2006 14:37:36 +1100
From: Duane <duane@e164.org>
User-Agent: Thunderbird 2.0b1 (X11/20061206)
MIME-Version: 1.0
To: lconroy <lconroy@insensate.co.uk>, enum@ietf.org
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> <456E7B25.6010701@e164.org>
In-Reply-To: <456E7B25.6010701@e164.org>
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc:
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

Duane wrote:

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

I've had a re-think on this, at least to a limited extent, take for
example jingle/xmpp integration into Asterisk/FreeSwitch etc, asterisk
obviously can't text message (unless you wanted to go into text to
speech/speech to text), and a client like gaim can't handle voice, so I
guess this is where listing type of services available in DNS comes in
so clients don't need to handshake to indicate what they can accept.
Although I guess the down side to not listing is of course lagged
initial setup, but would this be detrimental?

-- 

Best regards,
 Duane

http://www.cacert.org - Free Security Certificates
http://www.nodedb.com - Think globally, network locally
http://www.sydneywireless.com - Telecommunications Freedom
http://e164.org - Because e164.arpa is a tax on VoIP

"In the long run the pessimist may be proved right,
    but the optimist has a better time on the trip."

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