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

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Wed, 27 September 2017 20:16 UTC

Return-Path: <rifaat.ietf@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 A05CF134314; Wed, 27 Sep 2017 13:16:56 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 GOt4zURa3ZQI; Wed, 27 Sep 2017 13:16:55 -0700 (PDT)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::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 B5E0013247A; Wed, 27 Sep 2017 13:16:54 -0700 (PDT)
Received: by mail-ua0-x235.google.com with SMTP id t36so9221657uah.10; Wed, 27 Sep 2017 13:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u62++XQL9Mmm1Ron4YIBrEVSQ36bHPuWKJiYIuZE8WM=; b=YF28rP7NEF204ySi26Amcaa5fvwLm79SbROrGQ2veHLWDKZmHxBHh6RJNw9UqvwElU dmbTI3StR7/iX0zwuwsVWIRBDSWkR0URT+0500WyFNaBVtwT9tm8wZF5VYfeivDFA+Pm mRIiCVOW7CuHZSz/VgnWW/h9qOiBlgAB/Se5vSsUs4F60a60m0vVwvpQmYc+b1SF6/MF x3d05GRyVHjMd+a3IOQjaxOW3hEJWt7EKKcNWGj7Q3h57W7epcDzeb4W5vWyn54TxUb5 mSa1HTj0QLXJPRKAITzJMUaA+XdGYmO4uGT5eRRqK1EqpVWU3/7LGs6x+gfRLwiRDNI0 auGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u62++XQL9Mmm1Ron4YIBrEVSQ36bHPuWKJiYIuZE8WM=; b=RciH+hSID9EptbrmKGLjvPftTr0FL0sICALlTLYaiAh3g936FXrtE5SbQUJUTtbmTp nFcUNKNC5TBj7FYDd9zaoXWx4hy+pDjwDl5FchUu0Ol/QQMm5Wxnrcx9E97wbS2cKgU5 4cozRjsDcAZHShOYJ05ZzzftNfx5O2SWYdC8GwSRO5ijjc9dzJ3cmuMhUicMJNOxqi8s MokiekHHpwSYwJOR2nsattPDHitzeWBcAf8+TMZxc5gGRc21Oa9NLTq4ruKbchrBSsYl fAJv5L+1l2Kt7Z9k9E9t/CZI1zlgWO2gj39j9dMsnSlCuIvTA13Aeg+QB0OlubV1Jgnq S2Xw==
X-Gm-Message-State: AHPjjUi4ogeDtIfTXP4EhVkCHwp3pFyBW011iJ6+J+DSGsQvIJXkm+Hz IklYR1k058fUvQjSl+a5hAsw0+WS0oh05Znx9Qo=
X-Google-Smtp-Source: AOwi7QAyoQYHQ5/wta8GQMIWbvjhm4WOucacGCdVqiQ5JrjBHb+dHd8nJHAGwBTqSgRU2SZqT+0H6MnHZB6sQTq7T1o=
X-Received: by 10.176.0.172 with SMTP id 41mr1587172uaj.0.1506543413860; Wed, 27 Sep 2017 13:16:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.91.152 with HTTP; Wed, 27 Sep 2017 13:16:53 -0700 (PDT)
In-Reply-To: <CAD9ie-taVBDP+3WaDMh8OBXOXxT+-bxkbRzK1L2983atYh-Liw@mail.gmail.com>
References: <150653315332.25011.10428786780586096514.idtracker@ietfa.amsl.com> <CA+k3eCQqKYFJyTEB_2gWoC=6k0ep7Pw02nSaOeXgeUBY8btwsQ@mail.gmail.com> <CAGL6ep+KfL=kKK0S09yt+OwYuMOOD3m1av1jpVrKuuWT1uyd5Q@mail.gmail.com> <CAD9ie-taVBDP+3WaDMh8OBXOXxT+-bxkbRzK1L2983atYh-Liw@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Wed, 27 Sep 2017 16:16:53 -0400
Message-ID: <CAGL6ep+jUmz7GmXEvUxUD-fQrYyzCGQAUWYp+0pcqbr5EGcQBg@mail.gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Cc: Brian Campbell <bcampbell@pingidentity.com>, IETF Meeting Session Request Tool <session-request@ietf.org>, oauth <oauth@ietf.org>, oauth-chairs@ietf.org
Content-Type: multipart/alternative; boundary="001a113dd5ba05a1c4055a31796c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3D_UovYriNtV1vYT3A6MiDc_edE>
Subject: Re: [OAUTH-WG] oauth - New Meeting Session Request for IETF 100
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 27 Sep 2017 20:16:56 -0000

Sure

On Wed, Sep 27, 2017 at 4:10 PM, Dick Hardt <dick.hardt@gmail.com> wrote:

> And secevent?
>
> On Wed, Sep 27, 2017 at 10:39 AM, Rifaat Shekh-Yusef <
> rifaat.ietf@gmail.com> wrote:
>
>> Sure, I will add that to the list.
>>
>> Regards,
>>  Rifaat
>>
>>
>> On Wed, Sep 27, 2017 at 1:35 PM, Brian Campbell <
>> bcampbell@pingidentity.com> wrote:
>>
>>> Can we possibly also try and avoid conflicts with tokbind?
>>>
>>> On Wed, Sep 27, 2017 at 11:25 AM, IETF Meeting Session Request Tool <
>>> session-request@ietf.org> wrote:
>>>
>>>>
>>>>
>>>> A new meeting session request has just been submitted by Rifaat
>>>> Shekh-Yusef, a Chair of the oauth working group.
>>>>
>>>>
>>>> ---------------------------------------------------------
>>>> Working Group Name: Web Authorization Protocol
>>>> Area Name: Security Area
>>>> Session Requester: Rifaat Shekh-Yusef
>>>>
>>>> Number of Sessions: 2
>>>> Length of Session(s):  1.5 Hours, 1.5 Hours
>>>> Number of Attendees: 50
>>>> Conflicts to Avoid:
>>>>  First Priority: saag core tls ace sipcore acme
>>>>
>>>>
>>>>
>>>>
>>>> People who must be present:
>>>>   Eric Rescorla
>>>>   Hannes Tschofenig
>>>>   Rifaat Shekh-Yusef
>>>>
>>>> Resources Requested:
>>>>
>>>> Special Requests:
>>>>   Please avoid conflict with sec area BoFs. Please avoid Monday.
>>>> ---------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> 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.*
>>
>>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
>
>
> --
> Subscribe to the HARDTWARE <http://hardtware.com/> mail list to learn
> about projects I am working on!
>