Again, for rtsp, you could choose anything as the standard. I'm going to switch here to representing myself and Progressive Networks. Here's the concern that we have. It is only inconsistent if you want to treat the track as a resource, and not as just a retrieval operation on a larger resource. Using extra path information does not suffer from this limitation, but only works when the extra segments are hierarchical in nature.
Containers are hierarchical in nature.
We want the authoring scenarios to be protocol independent. I assume that you mean RTSP would respond with the container's streams and HTTP would respond with the metafile, which the client would read and make separate requests for the individual streams. I'm not sure what the correct character would be here. It would be syntactically ambiguous to append another component to the query. However, that was found not to be true in practice.