W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2019

Fwd: IETF 104 Remote Participation Information

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 23 Mar 2019 18:09:01 +0100
Message-Id: <94EE69EB-857C-4B1A-9590-191ED7ACD903@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
FYI.

> Begin forwarded message:
> 
> From: IETF Secretariat <ietf-secretariat@ietf.org>
> Subject: IETF 104 Remote Participation Information
> Date: 23 March 2019 at 10:55:00 am GMT+1
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Cc: wgchairs@ietf.org, 104all@ietf.org
> Reply-To: ietf@ietf.org
> Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yk4i0n5zPfw0LRT8ciOU9lRwwzY>
> 
> Can't make it to Prague? Participate remotely! The IETF offers a number
> of ways for remote attendees to audit or even contribute to IETF
> sessions throughout the meeting week.
> 
> First, register for the meeting. There is no cost to register as a
> remote attendee, and by registering you will insure that you receive
> important updates on agenda changes and other things of interest to
> meeting attendees. Please register here:
> <https://www.ietf.org/registration/ietf104/remotereg.py>
> 
> General remote participation information can be found here:
> <https://ietf.org/how/meetings/104/remote/>. Below is a breakdown of
> some of the main services available.
> 
> 1) Meetecho
> The Meetecho platform provides a synchronized view of the audio/video
> stream from the meeting room, which includes slides being presented and
> the presenter, as well as official IETF Jabber room. Meetecho will be
> supporting all eight of the working session tracks, as well as the
> Sunday tutorials, Host Speaker Series, and IETF Plenary. If you have a
> comment or a question, Meetecho enables you to ask it even if you are
> not in the room. For more information on how to join a Meetecho session,
> or to watch a recording after the session has concluded, see here:
> <http://ietf104.conf.meetecho.com/>. To report issues with Meetecho,
> please send email to tickets@meeting.ietf.org.
> 
> 2) Audio Stream
> If you only want to listen to the sessions, the audio stream is a good
> choice. All working sessions are streamed; links to the streams are
> available from the agenda, here:
> <https://datatracker.ietf.org/meeting/104/agenda>. To report issues with
> audio levels, please send email to mtd@ietf.org.
> 
> 3) Jabber Rooms
> All IETF meeting sessions have a corresponding Jabber room. See here for
> link to the meeting agenda with corresponding Jabber rooms:
> <https://datatracker.ietf.org/meeting/104/agenda >. Whenever possible, an
> in-room volunteer monitors the Jabber room; this volunteer will stand at
> the microphone for remote attendees and relay their questions into the
> meeting room microphone so that people in the room can respond. More
> information on the IETF Jabber service is available here:
> <https://ietf.org/how/meetings/jabber/>.
> 
> 4) Mailing Lists
> The 104attendees@ietf.org is for general discussion of things happening
> at the meeting; join the list if you want to hear about Prague
> restaurants and other topics of interest to those who are physically
> present at the meeting. Subscribe to 104attendees here:
> <https://www.ietf.org/mailman/listinfo/104attendees>.
> 
> The 104all@ietf.org list is for important announcements only and is not
> a discussion list. You automatically subscribed when you register as a
> remote participant. Being on 104all is essential if you want to hear
> about changes to meeting agenda or other important announcements.
> Subscribe to 104all here:
> <https://www.ietf.org/mailman/listinfo/104all>.
> 
> 5) Live video of several sessions, including the IETF Plenary and the
> IRTF Open Meeting, will be streamed live on YouTube. See
> <https://www.ietf.org/live/> for more information.
> 
> After the meeting, we will be sending a survey to all remote participants
> to get feedback on their experience; if you participate remotely, we’d
> love to hear from you! And don’t forget to follow @ietf on Twitter!
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Saturday, 23 March 2019 17:09:30 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 23 March 2019 17:09:32 UTC