Return-Path: <ve7jtb@ve7jtb.com>
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 053EF21F8566 for <oauth@ietfa.amsl.com>;
 Thu, 23 Aug 2012 07:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.494
X-Spam-Level: 
X-Spam-Status: No, score=-3.494 tagged_above=-999 required=5 tests=[AWL=0.105,
 BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwMfcBgXw5W7 for
 <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 07:51:52 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com
 [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 37DA821F84F3 for
 <oauth@ietf.org>; Thu, 23 Aug 2012 07:51:52 -0700 (PDT)
Received: by yhq56 with SMTP id 56so194286yhq.31 for <oauth@ietf.org>;
 Thu, 23 Aug 2012 07:51:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
 s=20120113;
 h=subject:mime-version:content-type:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to:x-mailer
 :x-gm-message-state; bh=hS6jSBS4ART9M8Bht1gbCAl7QKf0i1r2fv6Bw+nYo8E=;
 b=mwpWPdZfNiSxv+GGhrfOO3pY0AvQPfs8ceNxSN84wAdAbmodXCqJl8f3ncZg1xAaja
 xWiJMzGLjrbsJOHWZTOKqImdJpMjTFr+54pYeecuxUOEPZGQ//Nb0EaBnTtZFoUfhnMg
 1UrdomLQ3cHjowJwgL9arSdV9rHEVow0IhMnMilZJCzpGgK8impt9gn8Fzn7mlcn8Tn4
 n2rseDfcl6xEBY3N76wpES78dun9xlFy9NyO8U0SJXD2P3GB84z38/wlDEujg0bWsXVa
 IHg0XxUdz977f/3WYc2ih7jq3/ugTcCURu0vlBiWJQE1OHpByScCEZ+bh7JqxgC2mBDc Soxg==
Received: by 10.236.173.137 with SMTP id v9mr1508393yhl.0.1345733511665;
 Thu, 23 Aug 2012 07:51:51 -0700 (PDT)
Received: from [192.168.1.35] (190-20-49-249.baf.movistar.cl. [190.20.49.249])
 by mx.google.com with ESMTPS id e24sm13762428yhh.4.2012.08.23.07.51.30
 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Aug 2012 07:51:34 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=us-ascii
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <50364056.4000400@mitre.org>
Date: Thu, 23 Aug 2012 10:51:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5FD7EB9-BFC5-44F7-9FFF-0165477C79F7@ve7jtb.com>
References: <50364056.4000400@mitre.org>
To: Justin Richer <jricher@mitre.org>
X-Mailer: Apple Mail (2.1280)
X-Gm-Message-State: ALoCoQmjZc65JY45cLIfJr8bpOIYupjFxGgE9IBPkj3zuLG0irz3fDJ2vWr7FYQCurC22fe3MVme
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Implementation Support and Community
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: Thu, 23 Aug 2012 14:51:53 -0000

The openID foundation is in a position of promoting OAuth 2 now as a =
significant dependency of openID Connect and other work.

I can ask the board if there is a interest in hosting something specific =
for OAuth 2.  =20

I agree with Justin, now that the core spec is done there needs to be =
some consideration put to marketing and support by someone.=20
This WG has new work items to progress so we probably don't want to get =
bogged down with that in this group.

I will wait to see the discussion on this here before asking OIDF or =
anyone else if they want to set something up.

John B.
On 2012-08-23, at 10:38 AM, Justin Richer wrote:

> With the core specs basically out the door and seeing wider adoption =
and publicity, the OAuth community is going to start to get more =
questions about "how do I do X?", and many of these are questions that =
have been answered before or seem "obvious" to those of us who have been =
up to our ears in the spec for the past few years. Nevertheless, these =
are important questions to support for the wellbeing of the protocol =
community, but where should they be asked?
>=20
> When the OAuth community lived on a simple Google Group, these kinds =
of questions make sense. But I'd argue that the IETF list is not really =
the right place for them. This list, and the IETF in general, seems to =
be best suited for *building* the protocol, not for the *use* and =
*support* of said protocol once it's built.
>=20
> The problem is that, as of right now, we don't have anywhere to point =
people where they could get a "real" answer.
>=20
> This opens a larger question of who might "sponsor" or "host" such a =
community. Anything like that needs moderators, and more importantly, =
needs experts willing to answer the questions. Some options I can think =
of:
>=20
> - Revive the google groups list for these kinds of =
questions/discussions
> - Start a new list/forum, linked to oauth.net
> - Point everyone to StackOverflow with an "oauth" tag
>=20
>=20
> -- Justin (who is not volunteering himself to host or moderate the =
group)
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

