Re: [Lager] IETF 96 - Working Group/BOF/IRTF Scheduling

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 26 April 2016 11:04 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: lager@ietfa.amsl.com
Delivered-To: lager@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 918A812D12D for <lager@ietfa.amsl.com>; Tue, 26 Apr 2016 04:04:06 -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=verisign-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 cSG3AV8x4Hed for <lager@ietfa.amsl.com>; Tue, 26 Apr 2016 04:04:04 -0700 (PDT)
Received: from mail-oi0-x263.google.com (mail-oi0-x263.google.com [IPv6:2607:f8b0:4003:c06::263]) (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 2B53112D0F8 for <lager@ietf.org>; Tue, 26 Apr 2016 04:04:04 -0700 (PDT)
Received: by mail-oi0-x263.google.com with SMTP id i2so945749oib.3 for <lager@ietf.org>; Tue, 26 Apr 2016 04:04:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=a59ZjFZ0YjJ0hEBnos1fRSIwWA2ugEwsOQHRwBNHHpg=; b=Rr0t6cbjLwhK+rLj4tXM+WVU28gmfdDtCA5Zo1EOQoCz5r3xzYkHpw/JcwwMBv1UvX 8lIHsLEiGI8c5Ujp6KBKBLwjycrP/V1vl4dL7F7eTO2zgjtf327N6w5r14v/tr/ryxVM NNGk44Pd0yiCz/kffUaLh82GU+ezzk/B0zhCOuG7WF6uaecnzf8/WZTfVYcxfV8iVVEM d25nIVYwVHiFEuS1U7nsCnlyx+CiDzK+60M+5ZQNaDjToxQKUkBPru8scIBf7ORtzE14 /+K5/y+FrEy8vDUxEBsiRBrIHh1hw3SOGSxMEaWTzupHN5clfLmbx8Ay4zTh2agy6MUq Fkdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=a59ZjFZ0YjJ0hEBnos1fRSIwWA2ugEwsOQHRwBNHHpg=; b=g9mKKlFppwlKDg/91PVUSn4xRB12Ra/TP+WLGHfuze0GidluSpvCPcmDZa6BYEJEgg D4jb7HkzXTe4I22SUnF6quKHWSidEm7KPivRlEV18vCITOfw9tdMXSwGsp1s0F3AitDF 45h1qReVY24NXYx2VQ7kRoON0daRehC/0U5a10vfRyPOOnQi7N5qChK9ZJ3Jl9Qo4GT0 BJ+908h2C9CZDC7VI1zA0mNS4hjKxz7K08ED8c5i8foP4MEScEYgztmS49RC/weL1KhN /ECPv9eoObCh7ghwLHfTFRyD3++qME5uxICECsevzWTVu6ZhApEF1Sb6ZtuCE+Jjx0CF gYZQ==
X-Gm-Message-State: AOPr4FUmhwpJrjmnGYxbghh6gE5MH6RwjxPWMSWVBcOA61gQIixjWqPvV/f6+Hx3xeESg3P3ttk06pdRQLHTGQstGhnNGJjp
X-Received: by 10.140.236.20 with SMTP id h20mr1527651qhc.49.1461668643206; Tue, 26 Apr 2016 04:04:03 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id e185sm2842832qkb.6.2016.04.26.04.04.03 for <lager@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 26 Apr 2016 04:04:03 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u3QB42Fb013061 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <lager@ietf.org>; Tue, 26 Apr 2016 07:04:02 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 26 Apr 2016 07:04:00 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "lager WG (lager@ietf.org)" <lager@ietf.org>
Thread-Topic: IETF 96 - Working Group/BOF/IRTF Scheduling
Thread-Index: AQHRnzGjvwix0PxoXkiczXTxZTBHxp+cF+VA
Date: Tue, 26 Apr 2016 11:03:59 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A3CE974@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <20160425203243.30150.68017.idtracker@ietfa.amsl.com>
In-Reply-To: <20160425203243.30150.68017.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lager/pGRjgv1iZ6grod3NDF_LIeHSVAE>
Subject: Re: [Lager] IETF 96 - Working Group/BOF/IRTF Scheduling
X-BeenThere: lager@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Label Generation Rules <lager.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lager>, <mailto:lager-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lager/>
List-Post: <mailto:lager@ietf.org>
List-Help: <mailto:lager-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lager>, <mailto:lager-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2016 11:04:06 -0000

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF
> Agenda
> Sent: Monday, April 25, 2016 4:33 PM
> To: Working Group Chairs
> Subject: IETF 96 - Working Group/BOF/IRTF Scheduling
> 
> Subject: IETF 96 - Working Group/BOF/IRTF Scheduling
> 
> -----------------------------------------------------------------
> IETF 96 – Berlin, Germany
> Meeting Dates: July 17 – 22, 2016
> -----------------------------------------------------------------
> 
> We are accepting scheduling requests for all Working Groups, BOFs, and
> Research Groups starting today.  Please review the IETF 95 attendance
> numbers below for your working group and adjust for IETF 96 as
> necessary. Please also check to ensure your conflict lists are up to
> date.

We're getting close to completing our chartered work item, but there may be more work to do and things to talk about. Should Marc and I request a meeting slot for IETF-96?

Scott