Re: [apps-discuss] Aggregated service discovery

"Paul E. Jones" <paulej@packetizer.com> Mon, 18 June 2012 23:43 UTC

Return-Path: <paulej@packetizer.com>
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 59A9311E80F7 for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 16:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 u9Cy5tsXgjIo for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 16:43:00 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 6648821F847F for <apps-discuss@ietf.org>; Mon, 18 Jun 2012 16:42:58 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id q5INgtCj012134 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 18 Jun 2012 19:42:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1340062976; bh=yWXAedYlXERdNmKyjW7gRXsSIscbtuVxwYry7l8v8jo=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=JxzJ072HuNgriSvLWW4MmbkfT+b1aCyU2Y0JyrFiVXXaySSEyBbPnYNuHwhBlIZVF cAqagLcfi62V8rPDmVz1e1b1Jq9zkcytMWbAyyW+ka7Gm5aqh8CLdJih4SHIfls4+n u1Os9+xMj7M7CkxQqWBZ6izIcRsIV9G6Rt/ox6HI=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Cyrus Daboo' <cyrus@daboo.name>, 'William Mills' <wmills@yahoo-inc.com>, 'Peter Saint-Andre' <stpeter@stpeter.im>
References: <64C6DF43A866F40437AF4CC3@cyrus.local> <059c01cd39c8$f3d027c0$db707740$@packetizer.com> <1339625839.48148.YahooMailNeo@web31816.mail.mud.yahoo.com> <4FD917ED.2050805@stpeter.im> <1339628098.85328.YahooMailNeo@web31812.mail.mud.yahoo.com> <4FD91AF7.5050107@stpeter.im> <1339630300.21499.YahooMailNeo@web31812.mail.mud.yahoo.com> <012401cd4cf4$6a465da0$3ed318e0$@packetizer.com> <1340040987.3036.YahooMailNeo@web31812.mail.mud.yahoo.com> <022801cd4d7f$644c4dc0$2ce4e940$@packetizer.com> <1340046923.34140.YahooMailNeo@web31806.mail.mud.yahoo.com> <027001cd4d8f$48e260f0$daa722d0$@packetizer.com> <1340053004.56116.YahooMailNeo@web31805.mail.mud.yahoo.com> <02bd01cd4d9b$6f651ea0$4e2f5be0$@packetizer.com> <9D8ACECA51A33EADF323F71B@caldav.corp.apple.com>
In-Reply-To: <9D8ACECA51A33EADF323F71B@caldav.corp.apple.com>
Date: Mon, 18 Jun 2012 19:42:59 -0400
Message-ID: <02d301cd4dac$18878260$49968720$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNYFRdarpUA3Z9l4mSBSKHTly568wGsYWTHAiB/MPYCgTB6NAGRuS9TAZsphI0CgPvwiQHAzgIyAdRbPCoCdcjfHwDj9hFfAcntoUICMTf0ewHVZ8SWASo++uKTG/zIgA==
Content-Language: en-us
Cc: 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: Mon, 18 Jun 2012 23:43:01 -0000

Cyrus,

> > So, I think any service that would be specified would have:
> >
> >    Hostname
> >
> >    Port
> >
> >    Transport
> >
> >    Transport-Security  (Perhaps the transport and transport security
> > could be combined?)
> >
> >    Protocol specific parameters (IMAP root folder path, SMTP login
> > requirements)
> >
> >
> 
> Andrew and I are working on a draft that has pretty much that set of
> attributes per service. We did include details on authentication - (e.g.
> mechanism, user id to use etc). Some other features are needed, such as
> priority (e.g., whether IMAP is preferred over POP). Our draft will start
> out with an XML schema and its own .well-known resource - that was pretty
> much our original design before we started the wider discussions here -
> but obviously that is all open to change (i.e. JSON, host-meta or
> whatever).

WebFinger is about discovering resources, and you are defining the resource.  What you are apparently already working on is in line with the approach I suggested at the outset: use WebFinger with an address like mailto:paulej@packetizer.com to discover a link relation of type "config-email" (or whatever) that points to this XML document you're defining.  That XML document can contain all of the information necessary to provision a mail client.

I look forward to seeing it and would be happy to lend a hand.

Paul