Re: [apps-discuss] Aggregated service discovery

Peter Saint-Andre <stpeter@stpeter.im> Wed, 13 June 2012 22:45 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59DC11E80B2 for <apps-discuss@ietfa.amsl.com>; Wed, 13 Jun 2012 15:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6bQfvBJC5Qz for <apps-discuss@ietfa.amsl.com>; Wed, 13 Jun 2012 15:45:04 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 101C011E80B5 for <apps-discuss@ietf.org>; Wed, 13 Jun 2012 15:45:04 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 59DF740081; Wed, 13 Jun 2012 17:02:15 -0600 (MDT)
Message-ID: <4FD917ED.2050805@stpeter.im>
Date: Wed, 13 Jun 2012 16:45:01 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120601 Thunderbird/13.0
MIME-Version: 1.0
To: William Mills <wmills@yahoo-inc.com>
References: <64C6DF43A866F40437AF4CC3@cyrus.local> <059c01cd39c8$f3d027c0$db707740$@packetizer.com> <1339625839.48148.YahooMailNeo@web31816.mail.mud.yahoo.com>
In-Reply-To: <1339625839.48148.YahooMailNeo@web31816.mail.mud.yahoo.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Aggregated service discovery
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 22:45:05 -0000

On 6/13/12 4:17 PM, William Mills wrote:
> I was just thinking about this topic and found the thread in the
> archive.  I'm interested specifically in the use case of a client
> discovering IMAP and SMTP services along with OAuth endpoints.
> 
> XMPP, IMAP and POP all have URI schemes defined, though SMTP does not. 
> With things that already have a dedicated scheme for a service type
> would it make sense to use the "related" link type already defined? 
> Then the client looks for "related" links of the scheme they want to
> discover.
> 
> The "related" link type was registered as part of "Atom"
> http://www.iana.org/go/rfc4287, but it seems to fit.
> 
> We still have to deal with SMTP for what I want.  DNS SRV records
> certainly also work, but I like a one-stop-shop.

Hi Bill,

What exactly are you trying to discover? At least in XMPP, we've been
using DNS SRV records for many years, and they seem to work just fine
for discovering XMPP servers and the means for connecting to them. If
you want to discover the IM or other accounts associated with an email
address, then WebFinger seems more appropriate.

Peter