From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4856C3CB35; Sat, 23 Mar 2019 06:09:38 -0400 (EDT) Received: by mail-qk1-x742.google.com with SMTP id c189so2694568qke.6; Sat, 23 Mar 2019 03:09:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=7WUQXYjBcRisfuTilon3KBY7duw7VfM2xxOvAhDEHl0=; b=f6hVakEqNQzN0f3aBba07DM+qAJg7b6uuNL8S84CGRWT2fF399TyZHCIsLyaDDZBCP wsNpxs1Zsvyh8r3QczlNQDp2biZz600uIZeEUS0bLsMv7mzvCTsfFb/99L2xjPaj2Enx Eben6pPkSeD9ov0uEQ98/p2bNKl+EGqrUossqjlldlAWLzRSFt3vIo5qprB/77R5+odr OOdHYasMNMLwBVI0LYpZkzwya+WDMd8OG8PDsQjA+eT6eea9ebz5UsTo/9KGWST68n/r wX1ISYbwfIlNmpXfJwewNk/yDtNK868KtbI52A7w/72VZCJpJWlcTC0FXWhAB6ELGljN cnCw== 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:content-transfer-encoding; bh=7WUQXYjBcRisfuTilon3KBY7duw7VfM2xxOvAhDEHl0=; b=uQ/X4Wg/U0mz+cXzF7I5HWe+55yfQp5BvJAwUNnKfLt8nnoq7Q8TLUhn4tsX3eWG2g 1Eu+TV9c9VEagXO7XdBlPdr3o0Ysf8ac8cAC64zt0i5ExJQSK9HhJa0ULjF8/kyteBK7 S6sLDN0VdXxQBgQgDfmcFEKN7aSpabU4Scb5120n6ahxI3k0fkEBqCzVNbchW37lEt08 Q5JQUMuj/otQv1gaq5CEGA6C1oVAvkpN0y9rfW935GKWkijBgkp0KHvHaDZG/cmiG39u ffMO9FlKx/44XP4w1+nFGK9BB+6ZwTY1fhSMAv2htU1w9yvFzSXh8eg6UTjDNGlbbx1h WJ4Q== X-Gm-Message-State: APjAAAXPfEdj71gIX5Kes0ZiBH2HGSfgZmLyxP7F5SqAvNLeBzIZy4Se ite/L/0oFEinUN99Emj7oVXgcwRyKw+k0lDWJoqY6SYSPeiPEQ== X-Google-Smtp-Source: APXvYqw+9tf+Myf5ZRbW3/4eyTNugr0NtofJF1npc2SrqNOSmSjr3/7kjBJ9iI6FiPWgrN8a8guy0bafPwzK4bMAb2U= X-Received: by 2002:a37:4dd0:: with SMTP id a199mr11088466qkb.164.1553335777356; Sat, 23 Mar 2019 03:09:37 -0700 (PDT) MIME-Version: 1.0 References: <155333490041.15676.4839223297944303393.idtracker@ietfa.amsl.com> In-Reply-To: <155333490041.15676.4839223297944303393.idtracker@ietfa.amsl.com> From: Dave Taht Date: Sat, 23 Mar 2019 11:09:25 +0100 Message-ID: To: bloat , Cake List , Make-Wifi-fast , codel@lists.bufferbloat.net, ecn-sane@lists.bufferbloat.net, cerowrt-devel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: [Codel] Fwd: [104all] IETF 104 Remote Participation Information X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Mar 2019 10:09:38 -0000 I would really like more folk to remotely attend the tsvwg wg meeting, which is this monday: 16:10-18:10Monday Afternoon session II Prague time. which is where we will hopefully get a chance to present SCE, and get an update on the L4S/tcpprague/dualpi worker, also. The schedule is here: https://datatracker.ietf.org/meeting/104/agenda/ There are as usual a plethora of work in other working groups worth paying attention to. In particular, the babel protocol working group is going to finalize the babel-hmac security extension, and maybe even dtls, and is considering adoption of the rtt-metric stuff. Homenet is still active (see the homenet mailing list for the discussions there in recent weeks! Hoo, boy), there's some stuff in the various tcp and iccrg working groups about BBR, and so on, and I haven't paid attention to rmcat and webrtc much in recent years. ---------- Forwarded message --------- From: IETF Secretariat Date: Sat, Mar 23, 2019 at 10:55 AM Subject: [104all] IETF 104 Remote Participation Information To: IETF Announcement List Cc: , <104all@ietf.org> 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: General remote participation information can be found here: . 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: . 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: . 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: . 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: . 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: . 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: . 5) Live video of several sessions, including the IETF Plenary and the IRTF Open Meeting, will be streamed live on YouTube. See 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=E2=80= =99d love to hear from you! And don=E2=80=99t forget to follow @ietf on Twitter! -- 104all mailing list 104all@ietf.org https://www.ietf.org/mailman/listinfo/104all --=20 Dave T=C3=A4ht CTO, TekLibre, LLC http://www.teklibre.com Tel: 1-831-205-9740