Re: Downloadable recordings of meeting sessions...

Alexa Morris <amorris@amsl.com> Mon, 24 October 2016 18:09 UTC

Return-Path: <amorris@amsl.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 51B7712997C for <ietf@ietfa.amsl.com>; Mon, 24 Oct 2016 11:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.032
X-Spam-Level:
X-Spam-Status: No, score=-3.032 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 vP5q1awsduWj for <ietf@ietfa.amsl.com>; Mon, 24 Oct 2016 11:09:25 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 397A1129962 for <ietf@ietf.org>; Mon, 24 Oct 2016 11:09:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 18E091E55BC; Mon, 24 Oct 2016 11:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRKQgnR4uOID; Mon, 24 Oct 2016 11:08:42 -0700 (PDT)
Received: from [IPv6:2601:647:4281:8ab2:3861:af64:ff96:3eb2] (unknown [IPv6:2601:647:4281:8ab2:3861:af64:ff96:3eb2]) by c8a.amsl.com (Postfix) with ESMTPA id DE5E51E55BD; Mon, 24 Oct 2016 11:08:42 -0700 (PDT)
Subject: Re: Downloadable recordings of meeting sessions...
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="windows-1252"
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <534FFCDA-3B1A-4B2C-AFCD-F91C9B388A81@nominum.com>
Date: Mon, 24 Oct 2016 11:09:22 -0700
Content-Transfer-Encoding: quoted-printable
Sendlaterdate: Mon, 24 Oct 2016 11:09:22 -0700
Message-Id: <B3F126D4-3981-48B2-BB36-57F1AEF9E859@amsl.com>
References: <534FFCDA-3B1A-4B2C-AFCD-F91C9B388A81@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X3PbMQArA46OGgzU9q9Z0RQmlHw>
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:09:26 -0000

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