IETF Logo Mail Archive

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

Alexander Mayrhofer <alexander.mayrhofer@enum.at> Wed, 29 November 2006 16:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpSXI-0001YP-Eh; Wed, 29 Nov 2006 11:43:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpSXH-0001X2-2B for enum@ietf.org; Wed, 29 Nov 2006 11:43:51 -0500
Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpSXF-0006Aa-PI for enum@ietf.org; Wed, 29 Nov 2006 11:43:51 -0500
Received: from [10.10.0.218] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Wed, 29 Nov 2006 17:43:46 +0100 id 0000001E.456DB8C2.0000399C
Message-ID: <456DB8A8.5000200@enum.at>
Date: Wed, 29 Nov 2006 17:43:20 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Duane <duane@e164.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>
In-Reply-To: <456CD852.1010303@e164.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: enum@ietf.org, Otmar Lendl <lendl@nic.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

Duane wrote:
> Otmar Lendl wrote:
> 
>> XMPP isn't just for IM. Google Talk uses XMPP for VoIP.
> 
> The same can be said for most if not all IM protocols.
> 

I think we will always have to deal with (at least) two "types" or
registrations in ENUM.

- The "application" type registration (like, in that case "im" pointing to
an IM URI, which in turn resolves to an XMPP server). Examples: "im",
"pres", "voice", "web", "ft"

- The "protocol" registration (like "xmpp" in that case). Examples "sip",
"h323", etc...

I haven't yet found out which of the two the "holy grail" is - we also try
to work on this issue in draft-ietf-enumservices-guide. contributions are
very welcome for that document...

cheers

Alex

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

v2.23.0 | Report a Bug | By Email