Re: [apps-discuss] Aggregated service discovery

William Mills <wmills@yahoo-inc.com> Thu, 14 June 2012 01:51 UTC

Return-Path: <wmills@yahoo-inc.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 1EBBA21F843A for <apps-discuss@ietfa.amsl.com>; Wed, 13 Jun 2012 18:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level:
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15]
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 n95mHidlMzLU for <apps-discuss@ietfa.amsl.com>; Wed, 13 Jun 2012 18:51:35 -0700 (PDT)
Received: from nm18.bullet.mail.bf1.yahoo.com (nm18.bullet.mail.bf1.yahoo.com [98.139.212.177]) by ietfa.amsl.com (Postfix) with SMTP id A7E8411E80EB for <apps-discuss@ietf.org>; Wed, 13 Jun 2012 18:51:34 -0700 (PDT)
Received: from [98.139.214.32] by nm18.bullet.mail.bf1.yahoo.com with NNFMP; 14 Jun 2012 01:51:33 -0000
Received: from [98.139.212.199] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 14 Jun 2012 01:51:33 -0000
Received: from [127.0.0.1] by omp1008.mail.bf1.yahoo.com with NNFMP; 14 Jun 2012 01:51:33 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 673863.15957.bm@omp1008.mail.bf1.yahoo.com
Received: (qmail 59860 invoked by uid 60001); 14 Jun 2012 01:51:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1339638692; bh=asSt0hvEZY/CuyTolGPR88ODB9Hq2J9O2HriGNqu4EA=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=OA/HSeiz1VniMJIQfOfZuzmDWHfFkJPFGRDwTDMXtYTNbBQJtvHTal9NPVh4ScWaooQCjxA5FaXue1X20cRDBEyfnz5t7uAEcWY7bbVzNR/tiM6VkhISE2k3yorfqIz/nzHL8Nm9HNzEWDTXXZnNceIFnTR10egaTt2AjKU94qY=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=lrW7yA/pXw2JrKrfEQoI/L7SnHmY9EOimVibkiFP2rnMeky5dDERluHSOIJMxAEteKM1zoishED9oAP0kVzNY/fTtZJz632fBxtPLq32jialquP0V46bXt7za2Rhj+4x7d+Bl6RwaAU3TOjrQ+kMeUBuXybeFJSzg4vYwAeWdm0=;
X-YMail-OSG: tfq9VBwVM1mvnStBSD2euK8QPsl07EYt5.tEmaqwwPwZfA. wh.44HgcOB7mFXMX30PtU86MKgGFEF8NQ7HC9xjzWrBnrJMRoqcTf9WBRkeh WpuUzOgJMBZrR1seO3mTTcpg3OkT77ljnEz4GzqNzaDWpyijiy7_NA3Wl4cf VWsvhqK9l1GfRUQS3Em0n0JfzaosfH6gAaIhI5ccaItDLjAjr_roSFJi_D74 Xqk.5HE5heTVxkTAmf2DGMKtMPHa0wBzdw9tUcZFVAB7iZur6ysPUIoq_lTK ptepGBaQr0wvQ2CqFx3pSMPDJQKNGC8e3rTJMCvzWBe7uhpSxbIkfCD8Fupu _VD_ysJ7mwJwJXi8ApuJHBkSCLibzEiXUS.Omdj46FU3n3eUQYETOF1xXN32 rxqzlsVNAzfP6Jo8FoJjbHOaM3PK2yTfcIhJvj1aTONf8PsTezhsHwcxEqM3 6oAacZD0B_3qFL7D0FyglBg--
Received: from [99.31.212.42] by web31816.mail.mud.yahoo.com via HTTP; Wed, 13 Jun 2012 18:51:32 PDT
X-RocketYMMF: william_john_mills
X-Mailer: YahooMailWebService/0.8.120.356233
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> <3A4C798C-D5E2-4D2C-9E1E-A7D40FB73431@ve7jtb.com>
Message-ID: <1339638692.53675.YahooMailNeo@web31816.mail.mud.yahoo.com>
Date: Wed, 13 Jun 2012 18:51:32 -0700
From: William Mills <wmills@yahoo-inc.com>
To: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <3A4C798C-D5E2-4D2C-9E1E-A7D40FB73431@ve7jtb.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1238014912-427776571-1339638692=:53675"
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
Reply-To: William Mills <wmills@yahoo-inc.com>
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: Thu, 14 Jun 2012 01:51:36 -0000

An important distinction.

In the end though the same question applies.




>________________________________
> From: John Bradley <ve7jtb@ve7jtb.com>
>To: William Mills <wmills@yahoo-inc.com> 
>Cc: Peter Saint-Andre <stpeter@stpeter.im>; "apps-discuss@ietf.org" <apps-discuss@ietf.org> 
>Sent: Wednesday, June 13, 2012 5:14 PM
>Subject: Re: [apps-discuss] Aggregated service discovery
> 
>
>It is probably worth remembering that WF is about discovering services for users.
>hostmeta is about discovering services for domains.
>
>
>One question is if Bob@foo.com and Jane@foo.com can have diffrent OAuth Authorization servers for there Imap and SMTP services.
>
>
>If not then hostmeta and not WF would be the more appropriate way to find the OAuth Authorization service required to get a access grant.
>
>
>For Connect we are also pondering the problem of users with hosted domains that don't have a web server running on the host for the primary domain, or at-least not one that is likely to provide a WF service.
>
>
>There is not a perfect answer to that question at the moment.
>
>
>John B.
>On 2012-06-14, at 12:31 AM, William Mills wrote:
>
>In my use case it's a service/server.
>>
>>
>>Not a terribly happy answer to say "DNS SRV records won't work for you, and there is no other solution.".  By the same token I could ask "Why do we need Webfinger and host meta at all if we have DNS SRV records?".
>>
>>
>>If XMPP uses SRV records for discovery, that's fine.  IMAP and outbound SMTP services both lack a defined discovery method other than the ubiquitous "service documentation".  Is there a compelling reason to pick DNS over WF for this?  From the app developer point of view I don't want to have N ways to discover M services.
>>
>>
>>-bill
>>
>>
>>
>>
>>
>>
>>>________________________________
>>> From: Peter Saint-Andre <stpeter@stpeter.im>
>>>To: William Mills <wmills@yahoo-inc.com> 
>>>Cc: Paul E. Jones <paulej@packetizer.com>; 'Cyrus Daboo' <cyrus@daboo.name>; "apps-discuss@ietf.org" <apps-discuss@ietf.org> 
>>>Sent: Wednesday, June 13, 2012 3:57 PM
>>>Subject: Re: [apps-discuss] Aggregated service discovery
>>> 
>>>On 6/13/12 4:54 PM, William Mills wrote:
>>>> As I said, I'm interested specifically in IMAP, SMTP and OAuth endpoints. 
>>>
>>>What exactly is an "endpoint"? A client? An account? A server?
>>>
>>>> As a data point, DNS SRV records are not controllable in many hosted
>>>> domain models.
>>>
>>>At the last XMPP Summit a few months ago, we learned that DNS SRV
>>>records are unavailable in whole countries (e.g., Japan). That doesn't
>>>mean we should define a replacement for DNS over HTTP. :)
>>>
>>>Peter
>>>
>>>-- 
>>>Peter Saint-Andre
>>>https://stpeter.im/
>>>
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>apps-discuss mailing list
>>apps-discuss@ietf.org
>>https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>
>
>