IETF Logo Mail Archive

Re: [OAUTH-WG] How to participate in OAuth2 IETF meetings

Sergey Beryozkin <sberyozkin@gmail.com> Fri, 12 August 2016 08:34 UTC

Return-Path: <sberyozkin@gmail.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 45A1E12B04F for <oauth@ietfa.amsl.com>; Fri, 12 Aug 2016 01:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T867UrIULIpL for <oauth@ietfa.amsl.com>; Fri, 12 Aug 2016 01:34:31 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 559BD128E19 for <oauth@ietf.org>; Fri, 12 Aug 2016 01:34:31 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id o80so17898012wme.1 for <oauth@ietf.org>; Fri, 12 Aug 2016 01:34:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ZUJ8jc/dnXgUPuWGaKVIowXdp+Q996MZcq+o1KsixDo=; b=hK9TSXM5DI5qinp2DqsuEjQG5Xiibo4sGXOoLikUnGKxFR6cddPahlzAfY79v2+wkJ ldD5C5yqh1ahZoncvhlUOUvlHv+L0rR6uGLzMgQkGFPWHGFALWfGSLAc8IEdcdrOWWW6 UA5SMmvebu11+nQwH5KKW4203eTHPUcZhjFmkSnDwuwoSihD5k6KKgaTrGo1rFRTwcG3 Y8qh9LBkTcDgJN64nAfYnKGDl45zM50KvlcOnxA+6E9Qnds8nYV0dGb4TSgsD4dWLs1V 9HVhuU/fnIdhtkDhhDvll+IgBC64Fg98F0vUblmxblgWtCx5eGCxioVaFZqGbFx9maD5 n3zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZUJ8jc/dnXgUPuWGaKVIowXdp+Q996MZcq+o1KsixDo=; b=T0Nn6H2he0yMUNXN6BOhgKytDYiimoF9eR3NOLfzAEGqEpx128oiFE8ywVFNWsNOGF vlpsXf7P0wUry+fVSBcsbHuBeeKGmngizRo+9fSC9rF3EeUrWFfP4977t7o+vwIqMyi7 Z5bmZ+abzTm6NkzLdAQsOLw9er2LMkgIQPL71m+DudKkQXr3KerXM29DSHnWPWY93pU0 t9aReT41lzyRvCqBmmUKj3T1q2a7XDc8kLNgpBe/kVnJCe7Oq04nUZlpV7bc7y8zCpCL Ah2SIyOItL83w9bX5/6YfjvfFkwvtkuYcRMYehMocnisprHPzeiXgK/2oArt8oZEqTXi 9IPw==
X-Gm-Message-State: AEkoous75gBRmrbHo4yO4ZfGMx6+I5m8EkjPLPVaKqUqaDC6rG7Tlkj10rA/Ghfxyq0WTQ==
X-Received: by 10.28.154.208 with SMTP id c199mr1853273wme.102.1470990869635; Fri, 12 Aug 2016 01:34:29 -0700 (PDT)
Received: from [192.168.2.7] ([79.97.121.181]) by smtp.googlemail.com with ESMTPSA id d80sm1461138wmd.14.2016.08.12.01.34.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Aug 2016 01:34:28 -0700 (PDT)
To: John Bradley <ve7jtb@ve7jtb.com>
References: <231ad20a-e508-c763-4972-375fefd65fb0@gmail.com> <515C7B67-345D-43EA-836D-099FFD9EADCF@ve7jtb.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <e142bab4-c576-ccaa-8915-596fab230630@gmail.com>
Date: Fri, 12 Aug 2016 09:34:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <515C7B67-345D-43EA-836D-099FFD9EADCF@ve7jtb.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/uaQ36QgvQE0C-sJ4pEZZzCdd44k>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] How to participate in OAuth2 IETF meetings
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 12 Aug 2016 08:34:33 -0000

Hi John

On 11/08/16 23:43, John Bradley wrote:
> Anyone can attend IETF meetings, and we encourage new people.  We all were new at some point.  (I have always been old but am the exception)

Wait and see a newcomer like myself and you may get surprised :-)

>
> We meet 3 times a year.  The meetings are listed at https://www.ietf.org/meeting/upcoming.html
>
> There are sometimes interim meetings that are announced on the list.  We just had one on Security in Germany.
>
> Often there more informal meetings at IIW http://www.internetidentityworkshop.com/ in California twice a year and at OpenID workshops.
>
We'll keep an eye on the upcoming calendar and the list announcements.

Many thanks, Sergey

> John B.
>
>> On Aug 11, 2016, at 6:35 PM, Sergey Beryozkin <sberyozkin@gmail.com> wrote:
>>
>> Hi All
>>
>> Who can participate in OAuth2 IETF meetings/workshops ?
>> I've checked the meeting archives, apparently the 'Newcomers' can be there but how formal the process is and how OAuth2-'qualified' the newcomers should be ?
>>
>> I'm interested in talking to other OAuth2 implementers f2f and myself and my other colleagues might also provide some input to the standardization effort.
>>
>> Are the rules for OIDC & JOSE workshops different (I can ask on specific lists for more details if yes)
>>
>> We might be able to join sometimes depending on the locality, times, and other constraints.
>>
>>
>>
>> Cheers, Sergey
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email