[Din] Fwd: [103all] IETF 103 - Remote Participation Information

Melinda Shore <melinda.shore@nomountain.net> Thu, 01 November 2018 06:35 UTC

Return-Path: <melinda.shore@nomountain.net>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296F812008A for <din@ietfa.amsl.com>; Wed, 31 Oct 2018 23:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-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 jsFvvx1ToRb0 for <din@ietfa.amsl.com>; Wed, 31 Oct 2018 23:35:02 -0700 (PDT)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 7B7051277CC for <din@irtf.org>; Wed, 31 Oct 2018 23:35:02 -0700 (PDT)
Received: by mail-vs1-xe32.google.com with SMTP id w194so11582960vsc.11 for <din@irtf.org>; Wed, 31 Oct 2018 23:35:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=jYFVKE2xqKkIl4+1Twcd3OYf61EfELFXlFszOrR83wo=; b=bFvYdekAOgu/Sp0B1kgUU5Ej3Ad5ZUyLrmyzGDBSBn77GGEZj+ouKW/qAysxUFlSjg oeHl+TbFtnxKUCLcVaCyWOn5HNEXYMTe9FQZ9a6+4RVHqn0OAL4KiT9J+rcV6Da6P9pe FyAvd5EMdbUJx/c+NR2aYAqwNXvW7L4JAVgHGjPVJ7tB4GRSx27D2yC3z3DMKSakJWyb U6D7EhCA8b5KbnXAi3hCS2/n80Pap0kZrwMZ3CFY4RZQ35/NFCW3ttlu7EBtnCiBIC1U 0K/ACnSkHw5v5d5DwbhDpNpoV/Oxy8Ptrv9JbQa+xYTWjl/jnQJbLV8eE0OrA8cAtrf7 iWDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=jYFVKE2xqKkIl4+1Twcd3OYf61EfELFXlFszOrR83wo=; b=eBxPniEU1CkAVOACHP6mawSLbtdgKWtuHKGZCOy+I6t69/AD90mTKbRsttN1cfTnpY +0Ihb6REa8QVGpNkbH9SqjL31Qu+SBHuwycmVkxYFTaXRJLrkPwKbIG8eBG1C7omdxQv GatkzZClUyzXnJ63ZKaK5BUj6naoBexFV5JRy3N2LNwMEATzQ7iMkQp1/P8S4UVLzr5S RysB0+/PtZQbqQ95YLecoVoZLwJH9lvoYrdSYjhz4YCW6Vpf3+ZvQO6Q46X9UPXUTkha 0/iYdLR2O+S57ArrkQlbqqbIjpEgODVehNZEZyac8bK8/jsSOI1GBs33Go03T/HrHV1y oFRw==
X-Gm-Message-State: AGRZ1gKJecNVCjfCQiZU1T1um2PjVtwrcyhmpswUDLphGxKvyXGcJUjv HrqIiyIFcCCVz9LjqMLjkQblk8LsoTK3gnjS/keM8tQ=
X-Google-Smtp-Source: AJdET5eSVtttwG74ISI7rpCe4CQv9dr8yF4dz13kvQoCgJFCCrmGMMa6BzeXOE56s3yUzs+Xf/DLEcJFaCEesSi+AoU=
X-Received: by 2002:a67:e15e:: with SMTP id o30mr2807643vsl.66.1541054101222; Wed, 31 Oct 2018 23:35:01 -0700 (PDT)
MIME-Version: 1.0
References: <154104529553.5322.10827541457430264088.idtracker@ietfa.amsl.com>
In-Reply-To: <154104529553.5322.10827541457430264088.idtracker@ietfa.amsl.com>
From: Melinda Shore <melinda.shore@nomountain.net>
Date: Wed, 31 Oct 2018 22:34:49 -0800
Message-ID: <CAO+QQRE_oWmqmiE7Qd4uo+2AfOCk+2xQGA4rQ62ieUgYxs1Jsw@mail.gmail.com>
To: din@irtf.org
Content-Type: multipart/alternative; boundary="000000000000488b5e0579949ef0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/R1tbOKi1QMr4hXRGFo0YtFfM60I>
Subject: [Din] Fwd: [103all] IETF 103 - Remote Participation Information
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2018 06:35:06 -0000

If you haven't seen this (and even if you have), here's how to participate
in the upcoming meeting if you're unable to attend in person.

Melinda

---------- Forwarded message ---------
From: IETF Secretariat <ietf-secretariat@ietf.org>
Date: Wed, Oct 31, 2018, 21:08
Subject: [103all] IETF 103 - Remote Participation Information
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: <wgchairs@ietf.org>rg>, <103all@ietf.org>


Can't make it to Bangkok? 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/ietf103/remotereg.py>

General remote participation information can be found here:
<https://ietf.org/how/meetings/103/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://ietf103.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/103/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/103/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 103attendees@ietf.org is for general discussion of things happening
at the meeting; join the list if you want to hear about Bangkok
restaurants and other topics of interest to those who are physically
present at the meeting. Subscribe to 103attendees here:
<https://www.ietf.org/mailman/listinfo/103attendees>.

The 103all@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 103all is essential if you want to hear
about changes to meeting agenda or other important announcements.
Subscribe to 103all here:
<https://www.ietf.org/mailman/listinfo/103all>.

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!

Only 2 days until the Bangkok IETF!

-- 
103all mailing list
103all@ietf.org
https://www.ietf.org/mailman/listinfo/103all