Re: [OAUTH-WG] Planning for upcoming IETF meeting

Torsten Lodderstedt <torsten@lodderstedt.net> Mon, 14 June 2010 16:24 UTC

Return-Path: <torsten@lodderstedt.net>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E4C83A69E9 for <oauth@core3.amsl.com>; Mon, 14 Jun 2010 09:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.044
X-Spam-Level:
X-Spam-Status: No, score=-0.044 tagged_above=-999 required=5 tests=[AWL=-0.395, BAYES_50=0.001, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVfEy87LlULm for <oauth@core3.amsl.com>; Mon, 14 Jun 2010 09:24:12 -0700 (PDT)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.37]) by core3.amsl.com (Postfix) with ESMTP id B9C0A3A69EB for <oauth@ietf.org>; Mon, 14 Jun 2010 09:24:12 -0700 (PDT)
Received: from p4fff0cbe.dip.t-dialin.net ([79.255.12.190] helo=[127.0.0.1]) by smtprelay03.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OOCSN-0006cs-CD; Mon, 14 Jun 2010 18:24:15 +0200
Message-ID: <4C1657AD.2000000@lodderstedt.net>
Date: Mon, 14 Jun 2010 18:24:13 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
References: <3D3C75174CB95F42AD6BCC56E5555B4502B29B75@FIESEXC015.nsn-intra.net>
In-Reply-To: <3D3C75174CB95F42AD6BCC56E5555B4502B29B75@FIESEXC015.nsn-intra.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: 141509
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Planning for upcoming IETF meeting
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Jun 2010 16:24:13 -0000

+1

Am 14.06.2010 16:13, schrieb Tschofenig, Hannes (NSN - FI/Espoo):
> Hi all,
>
> Those who attended the last IETF meeting noticed that the actual working
> group slots are quite short (around 2 hours). The feedback I got was
> that this does not leave us with enough time to get work done. I
> understand that argument and acknowledge that not everyone wants to
> attend a punch of other working group (even though I believe it would be
> useful todo so) and therefore staying the entire week does not make a
> lot of sense either. Traveling to a remote location for a 2 hour meeting
> then does not sound super efficient.
>
> The plan I had discussed with Blaine is the following: Once the final
> IETF meeting agenda is available we will pick time slots all over the
> week (one every day). I will organize a room and we can get together to
> discuss open issues until we reach a point where we need to dig into the
> details (often requiring text to be written). Writing such text
> contributions will then happen afterwards so that we can continue our
> discussion during the next slot.
>
> This will hopefully help us to get some open issues investigated in
> detail and to have text proposals available. The official working group
> meeting slot would be used to summarize the work on the text proposals
> and to get input from the larger community.
>
> Thoughts?
>
> Ciao
> Hannes&  Blaine
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>