Re: [AVTCORE] Question
worley@ariadne.com (Dale R. Worley) Mon, 29 December 2014 00:30 UTC
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670761AC3D5 for <avt@ietfa.amsl.com>; Sun, 28 Dec 2014 16:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level:
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=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 9bFMODrc_yni for <avt@ietfa.amsl.com>; Sun, 28 Dec 2014 16:30:28 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E59A01AC3C0 for <avt@ietf.org>; Sun, 28 Dec 2014 16:30:27 -0800 (PST)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-01v.sys.comcast.net with comcast id ZCWG1p0022Qkjl901CWTzt; Mon, 29 Dec 2014 00:30:27 +0000
Received: from hobgoblin.ariadne.com ([173.75.213.57]) by resomta-ch2-15v.sys.comcast.net with comcast id ZCTw1p00N1Es2At01CU2b7; Mon, 29 Dec 2014 00:28:22 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id sBT0SJ3O026123; Sun, 28 Dec 2014 19:28:19 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sBT0SII8026120; Sun, 28 Dec 2014 19:28:18 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHWZdjmYYNu5DQnr53mzwjekU8wxwh+3yGRSTdgvN0Sm=w@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com
Date: Sun, 28 Dec 2014 19:28:18 -0500
Message-ID: <874msfcna5.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419813027; bh=6ayPN+7fABe5J/tnd92g3UQxDYojIiQuLNTuU58cSEo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=QouXrt9sN6YbrBjcxfVPupq6vR0+quoPOZdJcA2oNfidAeVw/yo+JAzAwHzYI+uBz yXMa94WlwT0RWtryBmSfNtl+MzGXVDma3ufaXiDb8FKq64kDaSFp1Pxbhzt67F4eRv J5JQ2nuO0OlyeGdvUHbrHq4r8uDb0jw0ic9ffAkZYJpkKo2Fot9C4yjdeJWtlMSoyv Sm05VxK6S0JKd/0pfsHJ7urUwL8Th6ttYL96pboOPOFVCNnGAHxuOK5Dp+Dy7WdO4c ZmoBsJChXhdMmN1OWFVAeO57zvB2f+R9IRxjxJwkTVex7yOijlmjwWwnIw9Z+es8D0 0eKVyVsoIB+ng==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/vewyVmsnldX6nZdWHz1a5nSHdoY
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Question
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 00:30:29 -0000
Julius Friedman <juliusfriedman@gmail.com> writes: > Rfc 2326 explicitly states that seeking can be disabled by not including > the end information in the range header. > > What if I want to have the end but I don't want to allow seeking? > > E.g. my clip is 10 minutes and I have already been playing for 3 and there > are 7 remaining; why can't I convey that and not allow seeking? I'm no expert in RTSP, but reading the RFC, it appears that the server indicates if seeking is allowed by the inclusion of the end-time: D.2.1 Basic Playback Client implementations may use the presence of length information to determine if the clip is seekable, and visibly disable seeking features for clips for which the length information is unavailable. Exactly why the server cannot indicate the total media length without implicitly stating the media is seekable, I don't know. Perhaps it's because any such media is theoretically seekable, since it must already be instantiated as a stored data object. Or perhaps it is because if seeking is not implemented, the user interface is expected to not display the "slider bar", and so there is no way to tell the user how much time remains in the media: Client implementations may use the presence of length information to determine if the clip is seekable, and visibly disable seeking features for clips for which the length information is unavailable. A common use of the presentation length is to implement a "slider bar" which serves as both a progress indicator and a timeline positioning tool. Perhaps referring to the mailing list discussion for this RFC would reveal the answer. In any case, why would we want to prevent seeking on a stored media object? I can see why if the media is an un-stored media stream, but in that case, the software likely doesn't know the total length that the media will have. Dale
- [AVT] Question Haythem Rashad
- [AVT] Re: Question fenner
- [AVTCORE] Question Julius Friedman
- Re: [AVTCORE] Question Dale R. Worley
- Re: [AVTCORE] Question Julius Friedman
- Re: [AVTCORE] Question Dale R. Worley
- Re: [AVTCORE] Question Julius Friedman
- Re: [AVTCORE] Question Dale R. Worley
- [AVTCORE] Erratum 4097 on RFC 2435 Dale R. Worley
- Re: [AVTCORE] [MMUSIC] Question Julius Friedman
- Re: [AVTCORE] [MMUSIC] Question - Erratum 4097 Dale R. Worley
- Re: [AVTCORE] [MMUSIC] Question - Erratum 4097 Julius Friedman
- Re: [AVTCORE] Erratum 4097 on RFC 2435 Magnus Westerlund
- Re: [AVTCORE] [MMUSIC] Question - Erratum 4097 Dale R. Worley
- Re: [AVTCORE] [MMUSIC] Question - Erratum 4097 Frederick, Ron