[rtcweb] rtcweb - New Meeting Session Request for IETF 96

"\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org> Fri, 06 May 2016 16:41 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: session-request@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160506164126.26301.71310.idtracker@ietfa.amsl.com>
Date: Fri, 06 May 2016 09:41:26 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/-MPRNO3Lz9omC2pj-iNYgFycgtI>
Cc: rtcweb@ietf.org, rtcweb-chairs@ietf.org
Subject: [rtcweb] rtcweb - New Meeting Session Request for IETF 96


A new meeting session request has just been submitted by Ted Hardie, a Chair of the rtcweb working group.


---------------------------------------------------------
Working Group Name: Real-Time Communication in WEB-browsers
Area Name: Applications and Real-Time Area
Session Requester: Ted Hardie

Number of Sessions: 2
Length of Session(s):  2 Hours, 1 Hour
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: tls rmcat aqm avtcore avtext clue dispatch httpbis stir acme mmusic payload sipcore perc 
 Second Priority: dprive tcpinc straw tsvwg tsvarea ace uta netvc capport
 Third Priority: insipid irtfopen ianaplan dane opsawg


Special Requests:
  There are two possible BoFs that we need to add as First priority conflicts:  SPUD and QUIC (if approved).

thanks,

Ted
---------------------------------------------------------

[rtcweb] rtcweb - New Meeting Session Request for… "IETF Meeting Session Request Tool"