IETF Logo Mail Archive

Re: [apps-discuss] The acct: scheme question

Mike Jones <Michael.Jones@microsoft.com> Tue, 26 June 2012 15:18 UTC

Return-Path: <Michael.Jones@microsoft.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 4017821F85DF for <apps-discuss@ietfa.amsl.com>; Tue, 26 Jun 2012 08:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.827
X-Spam-Level:
X-Spam-Status: No, score=-3.827 tagged_above=-999 required=5 tests=[AWL=-0.229, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Ve3o7Tu2Xn7T for <apps-discuss@ietfa.amsl.com>; Tue, 26 Jun 2012 08:18:02 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id A39B921F85AF for <apps-discuss@ietf.org>; Tue, 26 Jun 2012 08:18:01 -0700 (PDT)
Received: from mail112-db3-R.bigfish.com (10.3.81.253) by DB3EHSOBE001.bigfish.com (10.3.84.21) with Microsoft SMTP Server id 14.1.225.23; Tue, 26 Jun 2012 15:16:19 +0000
Received: from mail112-db3 (localhost [127.0.0.1]) by mail112-db3-R.bigfish.com (Postfix) with ESMTP id 80F73C03DB; Tue, 26 Jun 2012 15:16:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC101.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VS-22(zz98dI9371Ic89bhc857hzz1202hzz1033IL8275bh8275dhz2fh2a8h668h839hd25hf0ah)
Received-SPF: pass (mail112-db3: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Michael.Jones@microsoft.com; helo=TK5EX14MLTC101.redmond.corp.microsoft.com ; icrosoft.com ;
Received: from mail112-db3 (localhost.localdomain [127.0.0.1]) by mail112-db3 (MessageSwitch) id 1340723776853679_6057; Tue, 26 Jun 2012 15:16:16 +0000 (UTC)
Received: from DB3EHSMHS011.bigfish.com (unknown [10.3.81.235]) by mail112-db3.bigfish.com (Postfix) with ESMTP id CDAF71A0048; Tue, 26 Jun 2012 15:16:16 +0000 (UTC)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (131.107.125.8) by DB3EHSMHS011.bigfish.com (10.3.87.111) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 26 Jun 2012 15:16:15 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.53]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi id 14.02.0298.005; Tue, 26 Jun 2012 15:17:35 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: William Mills <wmills@yahoo-inc.com>, Melvin Carvalho <melvincarvalho@gmail.com>, "Murray S. Kucherawy" <msk@cloudmark.com>
Thread-Topic: [apps-discuss] The acct: scheme question
Thread-Index: Ac0367W7uVNJxgK+Tf6qpowkmE64wgbqGMQAAAKM2jAAA8N6gAAAR9EQ
Date: Tue, 26 Jun 2012 15:17:34 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394366568FF8@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <CAKaEYhKpeayOw4sN4=NYaoXKJQ2e5P+pP8SqJqnt-=Barb=WqA@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394366568E4F@TK5EX14MBXC283.redmond.corp.microsoft.com> <1340723227.60315.YahooMailNeo@web31801.mail.mud.yahoo.com>
In-Reply-To: <1340723227.60315.YahooMailNeo@web31801.mail.mud.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.32]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394366568FF8TK5EX14MBXC283r_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] The acct: scheme question
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: Tue, 26 Jun 2012 15:18:03 -0000

Yes, there’s a significant advantage.  It allows the acct: scheme to be approved (or rejected) quickly so that we will know whether it is safe for WebFinger and other specifications to use it.  That approval/rejection can then happen in parallel with refining the discovery specification.

Otherwise, we could be in a position where we think we have a final discovery specification, only to learn that it can’t go forward because of objections to the acct: scheme from the W3C and possibly others.  It would be much better for us to know whether that is the case up front.

                                                            -- Mike

From: William Mills [mailto:wmills@yahoo-inc.com]
Sent: Tuesday, June 26, 2012 8:07 AM
To: Mike Jones; Melvin Carvalho; Murray S. Kucherawy
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] The acct: scheme question

Is there any advantage to breaking it out?  The WF draft depends on it and so can't finalize until acct: does, right?

Will one get done more quickly than the other?

________________________________
From: Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.com>>
To: Melvin Carvalho <melvincarvalho@gmail.com<mailto:melvincarvalho@gmail.com>>; Murray S. Kucherawy <msk@cloudmark.com<mailto:msk@cloudmark.com>>
Cc: "apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>" <apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>>
Sent: Tuesday, June 26, 2012 6:20 AM
Subject: Re: [apps-discuss] The acct: scheme question

Yes, I believe that the acct: scheme should be considered separately from discovery, in its own document.

                                                            -- Mike

From: apps-discuss-bounces@ietf.org<mailto:apps-discuss-bounces@ietf.org> [mailto:apps-discuss-bounces@ietf.org]<mailto:[mailto:apps-discuss-bounces@ietf.org]> On Behalf Of Melvin Carvalho
Sent: Tuesday, June 26, 2012 5:06 AM
To: Murray S. Kucherawy
Cc: apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
Subject: Re: [apps-discuss] The acct: scheme question


On 22 May 2012 09:22, Murray S. Kucherawy <msk@cloudmark.com<mailto:msk@cloudmark.com>> wrote:
As we prepare to bring webfinger into appsawg, it looks a lot like there’s substantial discussion just on the point of the proposed “acct:” scheme.

So, a question for those tracking the discussion:  Is this a big enough topic that it should be split into its own document?  This would be a useful thing to decide as we figure out how to handle the work once it enters working group mode.

(This by itself has me wondering if we should revisit the conversation about whether webfinger needs its own working group, but I’ll leave it to Barry and Pete to make that call.)

There has been some discussion of this here and on other lists, and the consensus I think is for people to follow the process at :

<uri-review@ietf.org<mailto:uri-review@ietf.org>>.

I think the current state of play is that webfinger can be used with any URI type e.g. mailto: http: acct: etc. acct: is recommended in the RFC.

-MSK

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/apps-discuss


_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email