Re: [OAUTH-WG] oauth - New Meeting Session Request for IETF 106

Brian Campbell <bcampbell@pingidentity.com> Fri, 04 October 2019 21:12 UTC

Return-Path: <bcampbell@pingidentity.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 1F4D7120088 for <oauth@ietfa.amsl.com>; Fri, 4 Oct 2019 14:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 FMn3Rm2UhBlL for <oauth@ietfa.amsl.com>; Fri, 4 Oct 2019 14:12:44 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 CB1FB120025 for <oauth@ietf.org>; Fri, 4 Oct 2019 14:12:44 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id b136so16557873iof.3 for <oauth@ietf.org>; Fri, 04 Oct 2019 14:12:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WpA+1rJxzTwPjm5v8w3gpkm7BHFJkRhIPt+5hrd1X9U=; b=LyLf/X0PQiUGNZU9UY2GuAtk/3kOyfzeLYd+6cK2gMu/nrImPKo7m4mTfRQ5DBjDi4 TGqRx3taw6OfFw/nCqwVF8gpDziN/Ydazwlaf5nJYrzh60scoEQ2vTxKhkQTr1LEZUlm EBorLsoW0bQVs33lwleOPfdnLlRQ4AiLaLL6I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WpA+1rJxzTwPjm5v8w3gpkm7BHFJkRhIPt+5hrd1X9U=; b=OOAP1IyXoWWYYvquQ1CHsOBDTJm2aMvZkRUW5psFOnl9TxlH7XBqt+rl8J8L59tRYI jOUBRm+eZUOPXdJYsgq9yacypi5M8C1PqtQ9lZjbFnHNJvcslUhERXaDDGlNAPqOJAWy FjLfiKRmP+rvrLzC9/Wf3SUaMVizEnCfGJ9ubYYdcjd9/DSn/qTd0n0t10khElKBkZf6 ebYDsSBazcNWwatnd71BwhfrX+m4lYZZ44jvMTALnEn9aDhyzsiiCj/RDoQA3jNc1B9O XQiRMADh1tGhAntnffRp02/ibTYdSkny2kvA3jK9mHVBsVxSpOI0qbwilypxr/fFTldi d96g==
X-Gm-Message-State: APjAAAXr8+3Q42eVv0KOWAgLkMM0AyIMBssOnoaSZ/zuHve7GAEXC2ou hL5esm7UywFSci8r8Afghcv4P0sWjuVKNrAz5q91HkjuuWcmw5ivkDLr+9m1sShR44+7hkJ5ZSw al4d9E0uNyk+Ozw==
X-Google-Smtp-Source: APXvYqwe2Hhy2/tsolBibUGrBMcXDwMb433KR+8LtzAcy5BEPZ+DjH+onP5AdTRZGyZAtuel6qu7OsIzgZka1Gpih5A=
X-Received: by 2002:a6b:cd81:: with SMTP id d123mr15943835iog.78.1570223563951; Fri, 04 Oct 2019 14:12:43 -0700 (PDT)
MIME-Version: 1.0
References: <157021248387.1396.8889788139399592188.idtracker@ietfa.amsl.com> <E85574E6-EE77-41B6-97A5-7CE6056E41ED@lodderstedt.net>
In-Reply-To: <E85574E6-EE77-41B6-97A5-7CE6056E41ED@lodderstedt.net>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Fri, 4 Oct 2019 15:12:17 -0600
Message-ID: <CA+k3eCTqHfX4_aqH1UC+7ZOoonmk5iez5k=gGDo7uMs9Pb3z1A@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth-chairs@ietf.org, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bf74d905941c2918"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ck2JPPPdxyGMM8ebj32dbVn4TS4>
Subject: Re: [OAUTH-WG] oauth - New Meeting Session Request for IETF 106
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2019 21:12:47 -0000

Hello chairs,

I'd like to request some agenda time to present on:
https://tools.ietf.org/html/draft-fett-oauth-dpop

Thank you,
Brian

On Fri, Oct 4, 2019 at 3:09 PM Torsten Lodderstedt <torsten@lodderstedt.net>;
wrote:

> Hi chairs,
>
> I would like to request the following slots:
> - https://tools.ietf.org/html/draft-lodderstedt-oauth-rar
> <https://tools.ietf.org/html/draft-lodderstedt-oauth-rar-00>
> - https://tools.ietf.org/html/draft-lodderstedt-oauth-par
> <https://tools.ietf.org/html/draft-lodderstedt-oauth-par-00>
> - Security BCP
>
> kind regards,
> Torsten..
>
> Am 04.10.2019 um 11:08 schrieb IETF Meeting Session Request Tool <
> session-request@ietf.org>;:
>
> 
>
> A new meeting session request has just been submitted by Hannes
> Tschofenig, a Chair of the oauth working group.
>
>
> ---------------------------------------------------------
> Working Group Name: Web Authorization Protocol
> Area Name: Security Area
> Session Requester: Hannes Tschofenig
>
> Number of Sessions: 2
> Length of Session(s):  1.5 Hours, 1.5 Hours
> Number of Attendees: 50
> Conflicts to Avoid:
> Chair Conflict: acme tls rats sipcore anima
> Technology Overlap: ace secevent teep suit core tokbind saag
>
>
>
> People who must be present:
>  Roman Danyliw
>  Hannes Tschofenig
>  Rifaat Shekh-Yusef
>
> Resources Requested:
>
> Special Requests:
>
> ---------------------------------------------------------
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._