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

John Bradley <ve7jtb@ve7jtb.com> Thu, 11 August 2016 22:43 UTC

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 B4DC512D84D for <oauth@ietfa.amsl.com>; Thu, 11 Aug 2016 15:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ve7jtb-com.20150623.gappssmtp.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 LRZ4iVVe4O5O for <oauth@ietfa.amsl.com>; Thu, 11 Aug 2016 15:43:24 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 D9FC012D0AA for <oauth@ietf.org>; Thu, 11 Aug 2016 15:43:23 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id p186so10322763qkd.1 for <oauth@ietf.org>; Thu, 11 Aug 2016 15:43:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CUUJQwV8kjoBMdSLkFDEvSKjtTM16+yi6juMEdxJqwA=; b=UhnFJe0+hdQ3SUYdjjUYlnaZzxWTn2DJsHrDIuUZ8MQnCtDb0fN7BkGMJiCpcEjkZc m4Avoc2eJ4AHqb5xI8WlNmX35e8PA6AS7BKanmFeyijy1ljiSCclMYw2QD7jT00VIlfU lpjVPIO/uqoHYooE7Zm79RCeddrn2Z2kaSFeBMpiTWG3hlQMsGj/ixUt2DEXcW6Boedk vjc+/3U0TpuNZi9eOKiT7/Wxb7VNcXh0jI/d15deqsnzyKeEv6jsJk3kA2oEH2/+STyq auQkbeSQVJiWCx/9wSY+/qu2PzMx/pu8nUXy1cceP5jyanEc4GKAybMpl5NmNmWMelEi fPCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CUUJQwV8kjoBMdSLkFDEvSKjtTM16+yi6juMEdxJqwA=; b=AAyrjchCO2pS/jkQ5dWR8fPsrwimcOEtsRaIqIBXWyinY5hYXMDaJEbElelJiLqqxT BaGNINaetFza78Ium6yJquh1zSE/XmkMgQmJrgsLiLFTQs8sKPSoXFvRE4IlZjNv3PDe oDYRw7Qcqhmtlb3Eg3NlRpxFzfLaM1HKimuxbBIMJNgeQAn250oEW4lP22CaxEyiZeyr M3AKTYPou4EfQ1I8bYYi7jezw0uxePNYY0n3WgWSSVZx3z5u3bhxIh8Eb+HWM6092QaM eY4ipTdJklkwEQO1fGTlKoOIiwrCYwaZG6fdSgg7A1cX8+OhkjY+f85DbPuS7XNozvCO jdEA==
X-Gm-Message-State: AEkoouu+y9fD03Q9RjL1q+oOc/FajmgiwoyXPRQwoFH7j49qS2zrSwG52HOX4JzHJy/fAqzr
X-Received: by 10.55.102.75 with SMTP id a72mr13907187qkc.20.1470955402843; Thu, 11 Aug 2016 15:43:22 -0700 (PDT)
Received: from [192.168.8.100] ([181.201.74.47]) by smtp.gmail.com with ESMTPSA id r29sm2736564qte.48.2016.08.11.15.43.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 11 Aug 2016 15:43:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <231ad20a-e508-c763-4972-375fefd65fb0@gmail.com>
Date: Thu, 11 Aug 2016 18:43:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <515C7B67-345D-43EA-836D-099FFD9EADCF@ve7jtb.com>
References: <231ad20a-e508-c763-4972-375fefd65fb0@gmail.com>
To: Sergey Beryozkin <sberyozkin@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/7nEM_c53a-FhqyxOaHxcU9oII10>
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: Thu, 11 Aug 2016 22:43:26 -0000

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)

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.

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