[vorbis] Vorbis over RTP

[Monty]

> Congestion in usually bursty

Yes, it is, but 'burst error' means something different.

> but it doesn't really matter. What I meant
> was that it is better to fragment yourself instead of letting the lower
> layers doing it if you can use the partial fragments. If we send a 2000
> byte UDP datagram and one IP/network layer fragment is lost all 2000
> bytes is lost. If we fragment it ourself at 1000 bytes and one is lost,
> we still get 1000 bytes that we can use. This is why most (probably all)
> RTP payloads are smaller than the typical MTU of ~1500 bytes.

Correct.

> What I meant was that as soon as the receiver get the codebook and can
> start decoding we can leave this group since they no longer have any use
> for the data. Similar to getting the codebook out of band, but we do not
> need any TCP connection at all so it is much more scalable (think >
> 100,000 users).

100,000 users, connecting one by one, is still considerably less
traffic than large commercial web servers get.  We'd still be talking
about multicasting new headers when the stream ID changes, so this is
only an initial connection mechanism, and it can also be decentralized.

In any case, there's no one optimal-in-all-situations answer to this
puzzle.  What works well in the low bandwidth case is suboptimal for
installations with large bandwidth and vice versa.

Monty

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.