[OAUTH-WG] How to participate in OAuth2 IETF meetings
Sergey Beryozkin <sberyozkin@gmail.com> Thu, 11 August 2016 22:35 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 6DFE312D0AA for <oauth@ietfa.amsl.com>; Thu, 11 Aug 2016 15:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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=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 dySXFU3DFOyq for <oauth@ietfa.amsl.com>; Thu, 11 Aug 2016 15:35:49 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 AD80012B047 for <oauth@ietf.org>; Thu, 11 Aug 2016 15:35:49 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id q128so2469696wma.1 for <oauth@ietf.org>; Thu, 11 Aug 2016 15:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=WEDImadfhLIs7uGPlCuYW9cyHik9Rw7bA1brB+xvGnE=; b=y3hXyMDTxiG1Uhgm+Ku81+PlOZ9BmsmoUPosw0nhL7wSpSCWDXydH3eyAGYiTsShiq DHsvheeyUQJIIvFnCmBfTa9zYTZZVX8zbEYGsaAocxG1fclOGtAu0OX4G4Fm6VEe/LIf k12fZDu7DV2ghPz+v0j6gWJ5jUST0rxJ4KzdDPiJvG0Vl6JFKhtim/JEEIEDQ0DtW+LS AhdsPRQN1iC49KfT8qkVH/zQPHvHr+prJTF1SxvD65ay2G5CYXqcNlICGW6bSFbfRDJ1 Ibe/9hbZOhs/fgHP2J++27c6Ya/giPoFOxYc7cPucYXBNg+HlPApK0ZrkHfNvP0Gq/e0 lN0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=WEDImadfhLIs7uGPlCuYW9cyHik9Rw7bA1brB+xvGnE=; b=dVqaMWi9txVzKaQuMa0Q15ph20P5DiGIEnONwzwhgNaXhbPhKnJYteciiZ5Hc5u5t4 vY7R/bXselm/Ou5QRA0gRW264XzsB5Wj2uI5NrHaMYwYxPq6EuNU6NSkwSc3ZwP3JQCZ lUJ7ERcJXTf4VBH1cmLTBkhuGvLtrdVP7dXGrVqVqQl52Ru1qaEV3TOZNslNQ5xk09yL Ena3XVWSA+JKpGG0r6BVo4V8fTLEq7LzSJ6RULfu19oTBx0q6cl6gn9vwrvTGFcBgh0X O1FwgpzBpCxdE+W4Gg86ZLtC3yYM0JBB2OcYLKMCqchgevTEOZ+Y9k3BY7nb9W+Uw/Ro 1tZQ==
X-Gm-Message-State: AEkoousSVqWI257YqBYX33taTA9wIqudkvS7KBcbDfAQs7F0igoRvEBEIV4YMFsaAvDIfw==
X-Received: by 10.28.193.10 with SMTP id r10mr12019483wmf.49.1470954947924; Thu, 11 Aug 2016 15:35:47 -0700 (PDT)
Received: from [192.168.2.7] ([79.97.121.181]) by smtp.googlemail.com with ESMTPSA id a184sm1892333wmh.1.2016.08.11.15.35.46 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Aug 2016 15:35:47 -0700 (PDT)
From: Sergey Beryozkin <sberyozkin@gmail.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Message-ID: <231ad20a-e508-c763-4972-375fefd65fb0@gmail.com>
Date: Thu, 11 Aug 2016 23:35:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/owGmlCEw5_mnrvMk1xFEjqr4WoY>
Subject: [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:35:51 -0000
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
- Re: [OAUTH-WG] How to participate in OAuth2 IETF … Sergey Beryozkin
- Re: [OAUTH-WG] How to participate in OAuth2 IETF … John Bradley
- [OAUTH-WG] How to participate in OAuth2 IETF meet… Sergey Beryozkin