[TLS] tls - Requested sessions have been scheduled for IETF 100

"\"IETF Secretariat\"" <agenda@ietf.org> Sat, 21 October 2017 00:24 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: sean+ietf@sn3rd.com, tls-chairs@ietf.org
Cc: Kathleen.Moriarty.ietf@gmail.com, tls@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150854546484.20809.12942799502820490500.idtracker@ietfa.amsl.com>
Date: Fri, 20 Oct 2017 17:24:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/FQyVc6viZKcRf1i8NgwCbJSwZbE>
Subject: [TLS] tls - Requested sessions have been scheduled for IETF 100

Dear Sean Turner,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

tls Session 1 (2:30:00)
    Thursday, Morning Session I 0930-1200
    Room Name: Canning size: 250
    ---------------------------------------------
    tls Session 2 (1:00:00)
    Monday, Afternoon Session III 1740-1840
    Room Name: Padang size: 300
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Transport Layer Security
Area Name: Security Area
Session Requester: Sean Turner

Number of Sessions: 2
Length of Session(s):  2.5 Hours, 1 Hour
Number of Attendees: 120
Conflicts to Avoid: 
 First Priority: quic rtcweb stir curdle saag uta acme cfrg httpbis tokbind perc dispatch
 Second Priority: dprive ace
 Third Priority: tcpinc lamps


People who must be present:
  Eric Rescorla
  Sean Turner
  Joseph A. Salowey
  Kathleen Moriarty

Resources Requested:

Special Requests:
  If sec-dispatch ends up being a thing please don&#39;t schedule us against that.  Also please don&#39;t put us up against the TEEP or FUD BOFs.
---------------------------------------------------------

[TLS] tls - Requested sessions have been schedule… "IETF Secretariat"