Re: ACTION 192 and 195

Dear Davy,

> you can find it in Section 6.2.5. I put it there, next to the other
> error cases.

OK, but wrote this in present time. I added a MUST. The sentence now reads:

"When there is a mismatch between the SMPTE time code used by the UA and
the encoding settings of the requested media resource (e.g., use of
smpte-25 time code when the media resource is encoded at 30fps), the
server MUST ignore the RANGE header and returns the whole resource
(i.e., a 200)"
We can close ACTION-192.

> Hmm, maybe we should remove then this paragraph from section 7.1,
> extend it with your above remarks and put it into the intro of
> Section 5? I can't see the difference between action-195 and
> action-197 ...

Indeed, this is what I have just done. The new paragraph in Section 5 is:

"The User Agent MAY also implement a so-called optimistic processing of 
URI fragments in particular cases. If a URL fragment occurs within a 
particular context such as the value of the @src attribute of a media 
element (audio, video or source) and if the time dimension is requested 
in the media fragment URI, it is recommended that the User Agent follows 
the scenario specified in section 5.1.2 Server mapped byte ranges and 
issues directly a range request using custom units assuming that the 
resource requested is likely to be a media resource. If the MIME-type of 
this resource turns out to be a media type, the server SHOULD interpret 
the RANGE request as specified in section 5.1.2 Server mapped byte 
ranges. Otherwise it SHOULD just ignore the RANGE header."

We can close ACTION-195 and ACTION-197.

   Raphaël

-- 
Raphaël Troncy
EURECOM, Multimedia Communications Department
2229, route des Crêtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/

Received on Wednesday, 1 December 2010 09:35:23 UTC