From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sonic303-24.consmr.mail.ne1.yahoo.com (sonic303-24.consmr.mail.ne1.yahoo.com [66.163.188.150]) (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 1A4CB3CB37 for ; Sat, 23 Mar 2019 13:30:59 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s2048; t=1553362258; bh=aGKbAYhymAFOtwDKmm9N5hhjjAWM8qbL69VE26IRvCs=; h=From:Subject:Reply-To:To:References:Date:In-Reply-To:From:Subject; b=le9j485CjANGkB4Y87QjWsrPrfDMlPnGuBOIdJJLzm82nqjIRpkdX0CVGOchsqFEety5dUWbiklfh81UdSooR3oWEzLb1tB7fkK7esjTTAZ9prtPsHnc27G+hh1BY0TpX5kDdu4JBWmVSZsrgE8zb/Kr32DZPsLZO9Nfn5AbuvIpb//VdnYke9Rjy3tjP6upNM6WjN7+ICaa0MVJWqi1qvk7yFvX5wsZqTvFjizYU2VdY1Z3TmP26yWJprjDFJNnIc8o70x+8D6UTvqnmAlrtXyCzxeVzTnEqze4tqq1y1Rrv7SQe2QMEhRDDm/Uc7mbohGVsE1Qo9WHuyowUXgx9w== X-YMail-OSG: _HYmiuEVM1lfxn.4.6PdDyr94r6GgZsIAla32YPU6.IdM.giQ9I9I4BZwCbYCkd Y6sav6E7Diwt7URVYMOVOq1wFTT8V6ZFq9W6yWkeaWHEnBag6pMZS2ok0ZLHqn9zYzuvWIet.yvJ POr9hXBgycd97.imGTOsh77bLnrit0xfwm1NFGswTYvgTtSTETVjRof.YTnqzAkCgs0qtzVU9BWV jF5jtG9RJchnay4nuoRSzHL4ADQNyRcFI_ryUKzpTWwm5cUaRitOIpMJSyKIPYCcRByyjNWUh1AR 62iulTapEDFTLW4u2Z8nMBjwQ2rvUhFHmfd7ePYH6fm_LRwmqcfvrEOh7akIIV1C3TsMr30_YT9M z46GJcgSbULGD8ZCfK3mUCOhG_y4OSE2LhhgQMUGKa6vjC6KSu0U75BAsoTW60KrkiwCfSPrbEL6 gE4w2M2xTKwPsmc_yeVG4IkqLthE0Z20KHigEe76P5MVQQc_3VxtGXLWsi4CdW9BEY0X61m_3JJO itQa6La2jCU5wD21Gep1mPx7d_I52LEhtedQNg3.JmQfKtcPpaj_TUE4MVVfoBrW756tRa1pEduS LkM8D75tDCS0Iblg4Hb2ti79L_8Bhbm133VDg6eLnX7QQ7Yx.h_5LuARhOpuIA_o6MT7kHzxaC44 VVLHvU0SaQJ_7chxohSiZNoSCTyMP39lUhU_w26XbJvYaHagP2LMiw6VSAaRLJKjklD9sfaHDozl eFRajZg_TG6LKHOtdhBZyj1_a6tAHeqIXj8NIRa_KntBLdHbhaOYGQ.6Gq3DpN0s1psbCuoXUykF qzzHYhbWY_3QM_g6Zj0tQZVhw.mk87I7ihLHexOzS893TJZNr3wWlsRw0iinIcr5ws.HAhOOOpI0 aZxO38F3t4iAbkH4naB8VYwtsDWZrG4xcVKXMI1.WCr0atCwgV_NFnsx392a53xIHdD7vCYVneuG uH57pAIb06wRqfnQbtquOCPx62QInWnfQ2ot5PMcJdjMkQwocZv49KbaQGZxbhf6nrUfVMKhiAFF 121PMM715KpYm9.BWT1jeoTTvFe0ZOqyVg1Ptzt613nLvkXraRDvrxFch7igGMJlxpw5wGAJP8E4 ZPXxMxNp41UC_mQ1Zov9KIDLRhffZjP0eJNQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Sat, 23 Mar 2019 17:30:58 +0000 Received: from CPEbc4dfba21363-CMbc4dfba21360.cpe.net.cable.rogers.com (EHLO [192.168.0.10]) ([99.240.251.181]) by smtp413.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 113848d26029e8aa4c886bb4f0ba8da9; Sat, 23 Mar 2019 17:30:58 +0000 (UTC) From: David Collier-Brown Reply-To: davecb@spamcop.net To: "codel@lists.bufferbloat.net" References: <155333490041.15676.4839223297944303393.idtracker@ietfa.amsl.com> Message-ID: Date: Sat, 23 Mar 2019 13:30:56 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------7023C3138C48446B5488AB2B" Content-Language: en-US Subject: Re: [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 17:30:59 -0000 This is a multi-part message in MIME format. --------------7023C3138C48446B5488AB2B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Specifically, in https://datatracker.ietf.org/meeting/104/materials/agenda-104-tsvwg-06 ... they are sessions 3.2 and 4.1 --dave On 2019-03-23 6:09 a.m., Dave Taht wrote: > 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 totickets@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 tomtd@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 > The104attendees@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: > . > > The104all@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’d > love to hear from you! And don’t forget to follow @ietf on Twitter! > > -- > 104all mailing list > 104all@ietf.org > https://www.ietf.org/mailman/listinfo/104all > > -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest davecb@spamcop.net | -- Mark Twain --------------7023C3138C48446B5488AB2B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Specifically, in https://datatracker.ietf.org/meeting/104/materials/agenda-104-tsvwg-06

... they are sessions 3.2 and 4.1

--dave

On 2019-03-23 6:09 a.m., Dave Taht wrote:
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 <ietf-secretariat@ietf.org>
Date: Sat, Mar 23, 2019 at 10:55 AM
Subject: [104all] IETF 104 Remote Participation Information
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: <wgchairs@ietf.org>, <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:
<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!

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



-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain
--------------7023C3138C48446B5488AB2B--