Re: Downloadable recordings of meeting sessions...

Ted Lemon <ted.lemon@nominum.com> Mon, 24 October 2016 18:19 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E1B11298CE for <ietf@ietfa.amsl.com>; Mon, 24 Oct 2016 11:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 pOQXRoaX05FN for <ietf@ietfa.amsl.com>; Mon, 24 Oct 2016 11:19:47 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CBB21296EF for <ietf@ietf.org>; Mon, 24 Oct 2016 11:19:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 0E96B740201; Mon, 24 Oct 2016 18:19:47 +0000 (UTC)
Received: from [10.0.20.146] (73.167.64.188) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 24 Oct 2016 11:19:47 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Message-ID: <C907786D-57E8-4146-97B0-286D54642E3B@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E87988F-D5F3-401A-8AC6-853890738ABA"
MIME-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Subject: Re: Downloadable recordings of meeting sessions...
Date: Mon, 24 Oct 2016 14:19:44 -0400
In-Reply-To: <B3F126D4-3981-48B2-BB36-57F1AEF9E859@amsl.com>
To: Alexa Morris <amorris@amsl.com>
References: <534FFCDA-3B1A-4B2C-AFCD-F91C9B388A81@nominum.com> <B3F126D4-3981-48B2-BB36-57F1AEF9E859@amsl.com>
X-Mailer: Apple Mail (2.3226)
X-Originating-IP: [73.167.64.188]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qiPvcXSzEdGtIlheFbMfVGRbKnA>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2016 18:19:48 -0000

Unfortunately this doesn’t seem to have happened for DNSOP, which was the recording I went looking for:

https://www.ietf.org/proceedings/96/dnsop.html <https://www.ietf.org/proceedings/96/dnsop.html>

That said, the process you’ve described and that’s shown on the INTAREA wg page in the proceedings totally addresses the questions I raised.

> On Oct 24, 2016, at 2:09 PM, Alexa Morris <amorris@amsl.com> wrote:
> 
> Ted,
> 
> Meetecho is uploading all recorded sessions to the IETF YouTube channel, usually within 24 hours of recording them. Then, when the Secretariat compiles the meeting proceedings, we insert a link to the video recordings. So if you go to a session page in the IETF 96 meeting proceedings, you should find a link to the YouTube video file in the Recordings section. For example, see https://www.ietf.org/proceedings/96/intarea.html. 
> 
> In addition to uploading them to YouTube,  the IETF also receives a copy of all audio and video files directly from Meetecho and they are stored on an IETF server for safekeeping. 
> 
> Regards,
> Alexa
> 
> On Oct 24, 2016, at 10:30 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
> 
>> For IETF 96, the only recordings available are the meetecho recordings, which are basically a recording of the session in an HTML5 presentation that includes both video and audio alongside the jabber.   This is really neat, but definitely different than previous IETFs.
>> 
>> I was able to make this work, so I don’t have an immediate problem with this.   However, the inability to download the video/audio and follow it offline could be a problem at times, and also I don’t know if the IETF actually has files that can serve as an archive in the event that MeetEcho should someday no longer be able to provide service.
>> 
>> Has this been thought about/discussed?
>> 
> 
> ----------
> Alexa Morris / Executive Director / IETF
> +1.510.492.4001
> Email: amorris@amsl.com
> 
> 
>