[TLS] Agenda for TLS at IETF 96 Posted

Joseph Salowey <joe@salowey.net> Fri, 08 July 2016 21:18 UTC

Return-Path: <joe@salowey.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5668412D595 for <tls@ietfa.amsl.com>; Fri, 8 Jul 2016 14:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=salowey-net.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 Xh5EBaQxNtmp for <tls@ietfa.amsl.com>; Fri, 8 Jul 2016 14:18:46 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 80ADF12D51D for <tls@ietf.org>; Fri, 8 Jul 2016 14:18:45 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id k35so2279754qtc.3 for <tls@ietf.org>; Fri, 08 Jul 2016 14:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=0AcGL9K/XROGWBW6cBi2YRe05wMYr1HjIPCEn4Pe3r8=; b=X/uVg4uCwnB5aztB5aUnUikEriMiHTngOj51xvQhsNHD+9ICKfhTket4Maaia3yabY arIZqDXqPtkVwASD8/kmfmp658OUNfmcxkKkAlsmHiKIRfXE2dPaC4bWwH6Icugu2kot tCOP/DWjVaP7q+XZu0PuSpsF9ihyFrEfPVaZVsVWXasclzw4qXiOO2UQSt0fS8LYfsER fxXeNy57ndgU9tyxOfdv8hOEcujKpyRQGzE51pAWPYT5EUt/suQrgn5pcsm5hcWXriC7 0iIxLv5mDWM0OHd2an1c9Jzwj/rTn+JZqCTM7d5vneSDr+1YTdR2owmAj7+OfWYPrsla Vg2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0AcGL9K/XROGWBW6cBi2YRe05wMYr1HjIPCEn4Pe3r8=; b=AiVwNkauLPa0BAKs0M8XbBfIbEz9bKTql86snrp2c4halPWr0DIvJC0U14pigI6orE 598H3mM8FRUt0atUMwEkej4pQfw3qLd8uF7J1x+V3MCp0i3KkSbxUxFTggzc/y9fGF/T CF+31eng/OT+rOOvUpcK2A9GpunU1qL8y0eCHaPa8oXTPapUKVrOiLylt8KReaLynMvK EQGFYiS7TajPdF34MChZPmHIXsUIh+GkQbM5KVSv+ZQkAtS7ovgWtCqY4RgQzfWfMpAE ACbVImfvU5RDjnOx0335djRQesgUWb+3dGHVTeAij6sw2zsJKTykisOOwfJQZLYcFSmI +Xcw==
X-Gm-Message-State: ALyK8tI6Q9h1ZswyoSX9CRGf1f+fDjUkBEAi9US7J8hWwoVEKOqvJY4Fn3vQwfgF2u5EaTTQ0Jfkp9tar+EAdw==
X-Received: by 10.200.51.34 with SMTP id t31mr5043240qta.61.1468012724559; Fri, 08 Jul 2016 14:18:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.181.134 with HTTP; Fri, 8 Jul 2016 14:18:25 -0700 (PDT)
From: Joseph Salowey <joe@salowey.net>
Date: Fri, 08 Jul 2016 14:18:25 -0700
Message-ID: <CAOgPGoDr7v=sevyZ61FGhLzJuUBT3V+TB5CY=GR2vjxHgq265Q@mail.gmail.com>
To: "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="001a1135729ef936040537265827"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/xMKX9btXhbDVOj3ryfHElt8_xbo>
Subject: [TLS] Agenda for TLS at IETF 96 Posted
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 21:18:48 -0000

I just posted an agenda for the Berlin meeting (
https://www.ietf.org/proceedings/96/agenda/agenda-96-tls)

Our main focus for the meeting will be TLS 1.3, but I am hopeful that we
will have time for some other topics.  The specific details of the 1.3
topics will likely change as we get closer to the meeting.

Cheers,

Joe