From nobody Sat Jul 31 07:32:04 2021 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AF63A2848 for ; Sat, 31 Jul 2021 07:32:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RTbQH14qVDQw for ; Sat, 31 Jul 2021 07:31:57 -0700 (PDT) Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (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 816CC3A2843 for ; Sat, 31 Jul 2021 07:31:57 -0700 (PDT) Received: by mail-vk1-xa2c.google.com with SMTP id f4so2657054vkb.10 for ; Sat, 31 Jul 2021 07:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=by8NFpYgTfx4l0fbZnp8CQP9Qv9m7DZtBrZXd6l0okE=; b=TQSSrOtqF/0kyd3kBCf44UC0+2zR9pnvi+5U9M5gXn11+JihKTeBwbSsP4XAy50lY1 pg5e5tqxxn1hlkfqNXrZazsVYu7QLN/Zzu+j+eTQ6RhJJpUNgUHptfwuZkEUXTrmYniI HZBpiR5kH/VL2BYmel02JBiLqPM7v9uW3s8WyZj1AK4kxFAi9eNFGz9/683f5w6uT4tO QQ+j5EJ3KvxRSEM2PwO/Gk4eOtfxDlc6JdVPK3mhRhKBwHYrwJKgzC0CYDJhTi+4W4Eo eAFp2MM/MgdRhwnv0DGqd9nFjdYrvB8N7BnOTrceC9GQrQrIumtUwEVVuvGwVFEuFCdP oRdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=by8NFpYgTfx4l0fbZnp8CQP9Qv9m7DZtBrZXd6l0okE=; b=N5l7ZMxYv+dt0PdXMDQ3F483GVJYFgJacjxxGQL9VKh9rjPfWSx1tNej84ue2lhnJA KbZfOgz1+ckRtktkzCTEIGWzF8N1jro3S6/b0envXm+q5LazUqrxlKcHynMpyYpH36rc 1vwt9+MUJ808+ktEAyAWraE8PTjJMHnNpeOpvwRFd7b8Hf0lhUEPq8GJwiC2y+PtGFtV SdXKKR8HyUQO32EasMaOe1fEKRH5HjaXdXwpnQwVOrG63XxQVDV0PDDtGS3hCkhfRabw P22cHInkxsubiEphqigJpFNF14Wmme0XQC3fFFUfVmNCvfruyWkBBlRgEoWAUqU9ayZh JBuA== X-Gm-Message-State: AOAM531GbaokXciF/uEyUJPGHSHY+3MmaUEFTTAUdpwAXCzoVc2Ehxtd dFHpilea81FJbg6z8FnbsGldLl6MEsU9BboBngHnlXH08wI= X-Google-Smtp-Source: ABdhPJxYkXdaMF92WFeE6RynTAQXXXRkRFpBbIPcoAoyl1aVqtWZej+z0mQje39OgyN1jLG+7Qvm3TMUx50VEmhS50M= X-Received: by 2002:ac5:c7cb:: with SMTP id e11mr5025685vkn.14.1627741915264; Sat, 31 Jul 2021 07:31:55 -0700 (PDT) MIME-Version: 1.0 From: Spencer Dawkins at IETF Date: Sat, 31 Jul 2021 09:31:28 -0500 Message-ID: Subject: Making YouTube videos work better for IETF/IRTF participants To: WG Chairs , "irsg@irtf.org Steering Group" Content-Type: multipart/alternative; boundary="000000000000a5395c05c86c323d" Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jul 2021 14:32:02 -0000 --000000000000a5395c05c86c323d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I hope everyone had a lovely IETF 111, and rested up at least a little before starting to read IETF e-mail. So, full disclosure,I REALLY miss having MeetEcho posting archival videos that synchronized the chat with the speakers and slides, etc. but we're where we are now, so I'm going with that, and want to make a positive suggestion. Making our session videos available on YouTube is in many ways a good thing for making them accessible to the world, but my recent experience poking around at IETF videos on YouTube has been that searching for a specific video from a specific IETF meeting doesn't work super well. Feel free to try this, for past meetings of your own groups, and see what else pops up along the way. Rather than hoping that situation changes, I'm wondering if it's worth putting links to IETF meeting session YouTube videos in the datatracker for various groups under "Meetings", so I can "view all the past session videos for QUIC, in order" without having to wander through spurious matches with other videos, trying to remember if the group actually met at IETF 108, not knowing whether a video has been uploaded from a session earlier in the week, and stuff like that. Specifically, I'm thinking about requesting that we either add a "Meeting VIdeos" selection to pages like https://datatracker.ietf.org/wg/quic/meetings/, or just include them as part of the "Meeting Materials" for each meeting, perhaps appearing with the agenda, minutes, and blue sheets at the top of pages like https://datatracker.ietf.org/meeting/111/session/quic. Obviously, working group/research group co-chairs could add that to the minutes, if they remember to do that, and are in a part of the world where YouTube isn't blocked, but it would be better if that happened automagically(*) when the YouTube video is uploaded, so we could pretty much count on them being available. So, if I'm going to ask someone else to do work, I should start with the goal in mind. Would your working group/research group participants find making your YouTube videos helpful? Please share your thoughts, when you have a moment. Best, Spencer (*) I mean "automagically from the working group/research group chair perspective". I've had too many conversations with secretariat folk, Greg Woods, and tools team members to think that ANYTHING around here happens by accident =F0=9F=98=80 --000000000000a5395c05c86c323d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I hope everyone had a lovely IETF 111, and rested up at le= ast a little before starting to read IETF e-mail.=C2=A0

= So, full disclosure,I REALLY miss having MeetEcho posting archival videos t= hat synchronized the chat with the speakers and slides, etc. but we're = where we are now, so I'm going with that, and want to make a positive s= uggestion.=C2=A0

Making our session videos available on = YouTube is in many ways a good thing for making them accessible to the worl= d, but my recent experience poking around at IETF videos on YouTube has bee= n that searching for a specific video from a specific IETF meeting doesn= 9;t work super well. Feel free=C2=A0to try this, for past meetings of your = own groups, and see what else pops up along=C2=A0the way.=C2=A0
<= br>
Rather than hoping that situation changes, I'm wondering = if it's worth putting links to IETF meeting session YouTube videos in t= he datatracker for various groups under "Meetings", so I can &quo= t;view all the past session videos for QUIC, in order" without having = to wander through spurious matches with other videos, trying to remember if= the group actually met at IETF 108, not knowing whether a video has been u= ploaded from a session earlier in the week, and stuff like that.=C2=A0

Specifically, I'm thinking about requesting that w= e either add a "Meeting VIdeos" selection to pages like https://datatracker.iet= f.org/wg/quic/meetings/, or just include them as part of the "Meet= ing Materials" for each meeting, perhaps appearing with the agenda, mi= nutes, and blue sheets at the top of pages like https://datatracker.ietf.org/meeting= /111/session/quic.

Obviously, working group/re= search group co-chairs could add that to the minutes, if they remember to d= o that, and are in a part of the world where YouTube isn't blocked, but= it would be better if that happened automagically(*) when the YouTube vide= o is uploaded, so we could pretty much count on them being available. So, i= f I'm going to ask someone else to do work, I should start with the goa= l in mind.=C2=A0

Would your working group/research= group participants find making your=C2=A0YouTube videos helpful?
=

Please share your thoughts, when you have a moment.

Best,

Spencer

=
(*) I mean "automagically from the working group/research g= roup chair perspective". I've had too many conversations with secr= etariat folk, Greg Woods, and tools team members to think that ANYTHING aro= und here happens by accident=C2=A0=F0=9F=98=80
--000000000000a5395c05c86c323d--