IETF 107 RTGWG Presentation Slot Requests

Yingzhen Qu <yingzhen.ietf@gmail.com> Fri, 28 February 2020 19:59 UTC

Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C565F3A1D0C; Fri, 28 Feb 2020 11:59:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 5giNYmlYtn8H; Fri, 28 Feb 2020 11:59:30 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 409683A1D10; Fri, 28 Feb 2020 11:59:30 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id d15so4798482iog.3; Fri, 28 Feb 2020 11:59:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0mm7AGQ76wBMN/QBC1a7O8rd5nPB/dJwv6ESJyQP8Y0=; b=SvBJvvc29jCSi2uUkP3Qgqs9WK5SUOximhdvq0lMb6IjtArqYIRZzZgYZEgQG1KO3T X8YIvFCLa5RJIC++lufaIdgQOQpfNIVG0SnUVakilFjIcDeTR9oFhCmysN2tbYGyuUsT H3+6KG4AKx7r34ItqDbPZ9FmfWbZqhikjuy/zFyk6QuBxWssb65Xr4VyRKSsNq/kf6O9 J3AVxUETZ8uynS39aQF+/JvKFTFsbzBNt0quvcPZ9DKog1wDucyMM9ZE7KwSPRnp8pft CzF90j50Oq/ODWHljswpGnPOV0V11+jMEwzuzH2XejlKL8398/BbgS2kJ0qqh/mu0caO 4pFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0mm7AGQ76wBMN/QBC1a7O8rd5nPB/dJwv6ESJyQP8Y0=; b=uoWcDYMdGQhLxsm8HgbFSvEvwks4vkEvsb0Xf/EsN0ezvcNmC2ITPNoFgVJ1XNgNUp KkhOtCPuWjevQ8xxrZsq7lH+TfBJ+taOg7gyMgAKZWH0/9+pdOq59VthYIhPwEwUihh/ TEojYkgnTcNLuigCwcyzMMW9xBal6gCOUUgu/5g9inte6vmKvXEt8058ctGGAiTcIaWY J4BzfOMS46MGInfQvz935ZUKLE+Ir08vVndVWnDyuVXA1lWKXwtfirSFbAqz4a5BOZm2 RzWzv+JJFYxPTHnHjsVPkfhfNYAHoNcD+T29pfm9InzR6bMJAKrt4hmTwSHswlBUgInz frtQ==
X-Gm-Message-State: APjAAAV+lpS26blbY4/5RR3+cIeMG0PHUGALNW/LB5UdYuKcfKhS/5Ip YZCM8G5j5rXa7ycwdvOB5MUHf4G+sbHJmfVLHtBzpPx+zg==
X-Google-Smtp-Source: APXvYqzHagQz7XKjX3OYpAdj9Jlhotdrd8/DKEBtxh/FJqGeBD75oj73BAxWP3qv+yL4a8lhrmSxFeGthBopc2YcCP0=
X-Received: by 2002:a02:cdd9:: with SMTP id m25mr4608362jap.123.1582919969235; Fri, 28 Feb 2020 11:59:29 -0800 (PST)
MIME-Version: 1.0
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Fri, 28 Feb 2020 11:59:18 -0800
Message-ID: <CABY-gOPBLJtA0=yd+WHbNd09CkXOA3zQxS0vAP3kEcPkyLqJAQ@mail.gmail.com>
Subject: IETF 107 RTGWG Presentation Slot Requests
To: rtgwg-chairs <rtgwg-chairs@ietf.org>, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000796560059fa84677"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/20RaKHl3O4hVkdTyFBoYjjSqaNA>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 19:59:32 -0000

Hi,

We're now accepting agenda request for the RTGWG Working Grouping meeting
IETF 107. Please send your requests to rtgwg-chairs@ietf.org, indicating
draft name, speaker, and desired duration (covering presentation and
discussion).

If you plan to present remotely, please let us know so we can make the
arrangements with the Meetecho team.

Thanks,
Yingzhen