IETF Logo Mail Archive

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

"Paul E. Jones" <paulej@packetizer.com> Wed, 27 June 2012 22:02 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 4E5A121F861C for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jun 2012 15:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 Jwew4gOMgjsR for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jun 2012 15:02:19 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id F399521F8617 for <apps-discuss@ietf.org>; Wed, 27 Jun 2012 15:02:18 -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 q5RM2HP8018482 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Jun 2012 18:02:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1340834538; bh=fWxYFW1+jdmnDrhwF1E9g5iZxOSifBNgHndliSHakAw=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=Dk0xTdEwkiplb0szzAfDAiwr86QKDdzvuft7IcBU5boh7Roevw7zV1gTfnAXQnhht EyDsP+wL95Y7dhWgCLupg1o1OkwfygtU3I9rLCIIrw0JlXZ6HsTb/ik1+X1hHStCRp zOEUqBTdB4mqYNtcM077vLbp6jaB6qtpNpA9Dntc=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Mike Jones' <Michael.Jones@microsoft.com>, 'William Mills' <wmills@yahoo-inc.com>, 'Graham Klyne' <GK@ninebynine.org>, 'SM' <sm@resistor.net>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <CAKaEYhKpeayOw4sN4=NYaoXKJQ2e5P+pP8SqJqnt-=Barb=WqA@mail.gmail.com> <4FEA6677.3020705@it.aoyama.ac.jp> <6.2.5.6.2.20120626224534.0a8b4298@resistor.net> <4FEB3060.1040805@ninebynine.org> <1340818030.8183.YahooMailNeo@web31806.mail.mud.yahoo.com> <047501cd54ae$c6848a30$538d9e90$@packetizer.com> <4E1F6AAD24975D4BA5B16804296739436656BCF0@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436656BCF0@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 27 Jun 2012 18:02:25 -0400
Message-ID: <049e01cd54b0$89925ba0$9cb712e0$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_049F_01CD548F.0281A600"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHACExhZgXedi2je/bJAOmWfz8jRwJIaUzKAmC+4owBc2Np4gGLJqkJAYQI6cwCpl4PgAEjO00olsGleBA=
Content-Language: en-us
Cc: 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: Wed, 27 Jun 2012 22:02:21 -0000

Who in the IESG might raise a concern?  We should talk.

 

So far, it seems like folks are happy in broad terms, but only concerned
about the unknown.  Worrying does not help us.  Let's get whomever we need
involved right now.

 

Paul

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Wednesday, June 27, 2012 5:54 PM
To: Paul E. Jones; 'William Mills'; 'Graham Klyne'; 'SM'
Cc: apps-discuss@ietf.org
Subject: RE: [apps-discuss] The acct: scheme question

 

At least based upon my experience with the OAuth Core and OAuth Bearer
specs, until IESG/IETF last call, a lot of the IESG members don't raise
issues, and then they're often raised as DISCUSS issues, which block
publication until resolved.  Sometimes these DISCUSS issues also call for
cross-organizational review with the W3C.

 

Until the acct: URI is actually in a spec in IESG/IETF last call, my
experience says that we really won't know where we stand.  Hence me wanting
to get us there as soon after Vancouver as possible.

 

                                                                -- Mike

 

From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org]
On Behalf Of Paul E. Jones
Sent: Wednesday, June 27, 2012 2:50 PM
To: 'William Mills'; 'Graham Klyne'; 'SM'
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] The acct: scheme question

 

Bill,

 

I'd say there is a division right down the middle.  It's not clear if there
are more in favor of keeping it there or moving it to a separate document.
However, there is not an overwhelming number on one side.

 

Moving it to a separate document should not be necessary.  We can publish
the WF RFC with the "acct" URI scheme and work to get URI reviewer approval
in parallel.  Is URI reviewer approval required first?  I don't think so.
Graham suggested that having it agreed in a standards-track RFC carries a
lot of weight.

 

It seems that those who want to separate it are mostly concerned that it
will delay the RFC publication.  That does not appear to be an issue at all.

 

Paul

 

From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org]
On Behalf Of William Mills
Sent: Wednesday, June 27, 2012 1:27 PM
To: Graham Klyne; SM
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] The acct: scheme question

 

Based on the comments to date is there consensus for a path forward?  Will
we leave acct: in the WF draft or split it out?  

If we're splitting it do we have someone stepping up to author the new
draft?

Thanks,

-bill

v2.23.0 | Report a Bug | By Email