Re: [apps-discuss] Aggregated service discovery

Cyrus Daboo <cyrus@daboo.name> Mon, 18 June 2012 22:08 UTC

Return-Path: <cyrus@daboo.name>
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 C1BAD11E80F6 for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 15:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level:
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 wBd8niRowjf1 for <apps-discuss@ietfa.amsl.com>; Mon, 18 Jun 2012 15:08:06 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4023211E80C1 for <apps-discuss@ietf.org>; Mon, 18 Jun 2012 15:08:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 61DC529A26DB; Mon, 18 Jun 2012 18:08:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbz4l9zJQxHa; Mon, 18 Jun 2012 18:08:04 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 7EDD629A26C8; Mon, 18 Jun 2012 18:08:03 -0400 (EDT)
Date: Mon, 18 Jun 2012 18:08:00 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: "Paul E. Jones" <paulej@packetizer.com>, 'William Mills' <wmills@yahoo-inc.com>, 'Peter Saint-Andre' <stpeter@stpeter.im>
Message-ID: <9D8ACECA51A33EADF323F71B@caldav.corp.apple.com>
In-Reply-To: <02bd01cd4d9b$6f651ea0$4e2f5be0$@packetizer.com>
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>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size="934"
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 22:08:07 -0000

Hi Paul,

--On June 18, 2012 5:43:43 PM -0400 "Paul E. Jones" <paulej@packetizer.com> 
wrote:

> 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).

-- 
Cyrus Daboo