[Secdispatch] secdispatch - Requested session has been scheduled for IETF 103

"\"IETF Secretariat\"" <agenda@ietf.org> Fri, 19 October 2018 18:56 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: rdd@cert.org, secdispatch-chairs@ietf.org
Cc: secdispatch@ietf.org, kaduk@mit.edu
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153997539223.6592.10102644787535181926.idtracker@ietfa.amsl.com>
Date: Fri, 19 Oct 2018 11:56:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/imZ4njYFrfgyuKFJT1oX90mj8xo>
Subject: [Secdispatch] secdispatch - Requested session has been scheduled for IETF 103

Dear Roman Danyliw,

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


    secdispatch Session 1 (2:00 requested)
    Tuesday, 6 November 2018, Afternoon Session II 1610-1810
    Room Name: Meeting 2 size: 150
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/103/sessions/secdispatch.ics

Request Information:


---------------------------------------------------------
Working Group Name: Security Dispatch
Area Name: Security Area
Session Requester: Roman Danyliw

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: dispatch ace dots perc acme mls saag
 Second Priority: tls mile



People who must be present:
  Eric Rescorla
  Roman Danyliw
  Richard Barnes
  Benjamin Kaduk

Resources Requested:

Special Requests:
  Ideally this session wouldn&#39;t conflict with any security area meetings; and would be early in the week. The Monday slot given for IETF 102 worked very well.
---------------------------------------------------------

[Secdispatch] secdispatch - Requested session has… "IETF Secretariat"