Re: [OAUTH-WG] Meeting slot for the Vancouver IETF meeting requested

Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 25 July 2012 16:19 UTC

Return-Path: <torsten@lodderstedt.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C457221F86E4 for <oauth@ietfa.amsl.com>; Wed, 25 Jul 2012 09:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level:
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 SC+oPH4uoYvf for <oauth@ietfa.amsl.com>; Wed, 25 Jul 2012 09:19:03 -0700 (PDT)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.98]) by ietfa.amsl.com (Postfix) with ESMTP id E79AC21F86D1 for <oauth@ietf.org>; Wed, 25 Jul 2012 09:19:02 -0700 (PDT)
Received: from [79.253.54.1] (helo=[192.168.71.42]) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1Su4Ie-0003EM-AK; Wed, 25 Jul 2012 18:19:00 +0200
Message-ID: <50101C74.6060005@lodderstedt.net>
Date: Wed, 25 Jul 2012 18:19:00 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <09CE58C6-9409-4E28-B4CA-DC76C37B898E@gmx.net> <4E1F6AAD24975D4BA5B16804296739436672BBBE@TK5EX14MBXC285.redmond.corp.microsoft.com> <B26C1EF377CB694EAB6BDDC8E624B6E7554F911D@BL2PRD0310MB362.namprd03.prod.outlook.com> <6DEBD33A-815E-460D-934E-A684AED2BA6B@ve7jtb.com> <FD90CDD8-7BC7-4952-BEF9-F29C282130E8@gmx.net> <5E393DF26B791A428E5F003BB6C5342A108171DC@OC11EXPO24.exchange.mit.edu>
In-Reply-To: <5E393DF26B791A428E5F003BB6C5342A108171DC@OC11EXPO24.exchange.mit.edu>
Content-Type: multipart/alternative; boundary="------------090107050103050407070505"
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Cc: Derek Atkins <derek@ihtfp.com>, "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Meeting slot for the Vancouver IETF meeting requested
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 16:19:05 -0000

Hi Hannes,

I'm unfortunately had to cancel my trip to IETF-84. Phil will cover the 
status of the threat model document. But none of the authors of the 
Revocation Draft will be attending. So I would ask you to postpone the 
presentation of this I-D to the next IETF meeting as well.

best regards,
Torsten.

Am 23.07.2012 17:02, schrieb Thomas Hardjono:
> Hannes, Derek,
>
> Would it possible to postpone presentation/discussion of the Dyn-Reg
> draft (Dynamic Client Registration Protocol) to the Atlanta/November
> IETF meeting?
>
> The reason is that none of the proposers will be attending the
> Vancouver IETF in-person.
>
> Thanks.
>
> /thomas/
>
> __________________________________________
>
>
>> -----Original Message-----
>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
> Behalf
>> Of Hannes Tschofenig
>> Sent: Sunday, July 15, 2012 1:58 PM
>> To: John Bradley
>> Cc: oauth@ietf.org WG
>> Subject: Re: [OAUTH-WG] Meeting slot for the Vancouver IETF meeting
>> requested
>>
>> Hi all,
>>
>> I have uploaded an agenda for the meeting.
>>
>> I am assuming that all these items do not require discussion time
>> anymore:
>> * draft-ietf-oauth-assertions
>> * draft-ietf-oauth-saml2-bearer
>> * draft-ietf-oauth-urn-sub-ns
>> * draft-ietf-oauth-v2
>> * draft-ietf-oauth-v2-bearer
>>
>> Hence, we can focus on the new items. As discussed in the mail below
> I
>> put a separate slot for discussion of the holder-of-the-key/MAC
> token
>> security discussion on the agenda. I would suggest that a couple of
> us
>> meeting during the IETF week to work together on a presentation that
>> provides some concrete suggestions for next steps to the rest of the
>> group.
>>
>> I also put the following persons on the spot for the presentations
> of
>> working group items:
>>
>> - OAuth Dynamic Client Registration Protocol (Thomas)
>> - JSON Web Token (JWT) (Mike)
>> - JSON Web Token (JWT) Bearer Token Profiles for OAuth 2.0 (Mike)
>> - Token Revocation (Torsten)
>> - SAML 2.0 Bearer Assertion Profiles for OAuth 2.0 (Brian)
>> - OAuth Use Cases (Zachary)
>>
>> Let me know if you want someone else to give the presentation.
>>
>> As a preparation for the meeting it would be good if you could
>> (a) identify the open issues with your document, and
>> (b) find one or two reviewers to have a look at your document during
>> the next two weeks.
>>
>> Ciao
>> Hannes
>>
>> On Jul 15, 2012, at 5:59 PM, John Bradley wrote:
>>
>>> Yes we need to get clearer on the the threats and use cases.
>>>
>>> I think Phil Hunt has some though there is likely overlap.
>>>
>>> Part of the problem with MAC was people never agreed on the
> threats
>> it was mitigating.
>>> I can present something or coordinate with Tony or Phil.
>>>
>>> John B.
>>>
>>> On 2012-07-14, at 9:36 PM, Anthony Nadalin wrote:
>>>
>>>> How about a few min on proof-of-possession requirements? I can
>> present our use cases and requirements
>>>> -----Original Message-----
>>>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
>> Behalf Of Mike Jones
>>>> Sent: Friday, July 13, 2012 4:42 PM
>>>> To: Hannes Tschofenig; oauth@ietf.org WG
>>>> Subject: Re: [OAUTH-WG] Meeting slot for the Vancouver IETF
> meeting
>> requested
>>>> I'm willing to do 5 minutes on the status of the Core and Bearer
>> documents.
>>>> I'm willing to give an update on JWT and the JWT Bearer -
> probably
>> 15 minutes.  It's probably good that we're a day after the JOSE WG
>> meeting, given the JWT dependency upon the JOSE specs.
>>>> I'm willing to be part of a discussion on the Assertions draft,
> but
>> would appreciate doing this with Brian and/or Chuck - I'm guessing
> 15
>> minutes for that as well.  (I'm not certain this will be needed, but
>> I'd like to review the recent changes before saying that it's not.)
>>>> Looking forward to seeing many of you in Vancouver!
>>>>
>>>> 				-- Mike
>>>>
>>>> -----Original Message-----
>>>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
>> Behalf Of Hannes Tschofenig
>>>> Sent: Saturday, June 02, 2012 12:46 AM
>>>> To: oauth@ietf.org WG
>>>> Subject: [OAUTH-WG] Meeting slot for the Vancouver IETF meeting
>> requested
>>>> Hi all,
>>>>
>>>> I have requested a 2,5 hour slot for the upcoming meeting.
>>>>
>>>> While the next meeting is still a bit away it is nevertheless
> useful
>> to hear
>>>> * whether you plan to attend the next meeting, and
>>>> * whether you want to present something.
>>>>
>>>> I could imagine that these documents will be discussed:
>>>> * draft-ietf-oauth-dyn-reg
>>>> * draft-ietf-oauth-json-web-token
>>>> * draft-ietf-oauth-jwt-bearer
>>>> * draft-ietf-oauth-revocation
>>>> * draft-ietf-oauth-use-cases
>>>>
>>>> To the draft authors of these docuemnts: Please think about the
> open
>> issues and drop a mail to the list so that we make some progress
>> already before the face-to-face meeting.
>>>> I am assume that the following documents do not require any
>> discussion time at the upcoming IETF meeting anymore:
>>>> * draft-ietf-oauth-assertions
>>>> * draft-ietf-oauth-saml2-bearer
>>>> * draft-ietf-oauth-urn-sub-ns
>>>> * draft-ietf-oauth-v2
>>>> * draft-ietf-oauth-v2-bearer
>>>>
>>>> Ciao
>>>> Hannes
>>>>
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
>>>>
>>>>
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth