IETF Logo Mail Archive

Re: [apps-discuss] Aggregated service discovery

Cyrus Daboo <cyrus@daboo.name> Wed, 23 May 2012 12:55 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 E85AF21F861A for <apps-discuss@ietfa.amsl.com>; Wed, 23 May 2012 05:55:23 -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=[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 y-WJwBOORmXM for <apps-discuss@ietfa.amsl.com>; Wed, 23 May 2012 05:55:23 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9D35921F85D7 for <apps-discuss@ietf.org>; Wed, 23 May 2012 05:55:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id DE19927C743A; Wed, 23 May 2012 08:55:21 -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 qLkeS+WfvOsN; Wed, 23 May 2012 08:55:19 -0400 (EDT)
Received: from [10.0.1.101] (dhcp50-95-124-140.hil-chachdt.atl.wayport.net [50.95.124.140]) by daboo.name (Postfix) with ESMTPSA id 71CD527C742C; Wed, 23 May 2012 08:55:18 -0400 (EDT)
Date: Wed, 23 May 2012 08:55:22 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Mark Nottingham <mnot@mnot.net>
Message-ID: <FF3DD3C9968F397579BC846A@cyrus.local>
In-Reply-To: <22873D37-8462-48AE-ABA0-49445776E4CC@mnot.net>
References: <64C6DF43A866F40437AF4CC3@cyrus.local> <22873D37-8462-48AE-ABA0-49445776E4CC@mnot.net>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="694"
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: Wed, 23 May 2012 12:55:24 -0000

Hi Mark,

--On May 23, 2012 4:29:24 PM +1000 Mark Nottingham <mnot@mnot.net> wrote:

> If they're HTTP -
> <https://datatracker.ietf.org/doc/draft-nottingham-json-home/>

Of course we do want service discovery for non-HTTP protocols, LDAP, IMAP, 
Submission, POP3, XMPP etc. Now I could almost imagine having non-http 
resource URIs in the json-home document for these other protocols, but I 
think that would be over stepping the intent of json-home.

> Not yet convinced that well-known is needed for this yet; it's
> effectively substituting a hostname for a full URL.

Not sure what you mean by that. Obviously it is important to have just one 
jumping off point for this.

-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email