[xiph-rtp] [vorbis-rtp] Updates

[Luca Barbato]

Ralph Giles wrote:

> Also in section 2.3, a reference is made to an ITU spec for channel
> mapping. Maybe we should give some examples since that spec isn't
> freely available? (and so we can make sure it matches the vorbis
> mapping!) Is there a way to distinguish dolby-style 5.1 from other
> six channel mappings?

We could just point the vorbis mapping since the aiff-c is incompatible 
with vorbis and remove the ITU reference (why did it come in first?)

> We should also explicitly say somewhere that the ident field in the 
> payload header maps a given data packet to a given decoder 
> configuration, and that for out-of-band retrieval methods, that
> mapping is outside the scope of the current document.

The mapping is in the scope of the document since it uses the same tag. 
Given it is explicit the way the numbers are produced is completely free.

> 
> I also think we should mention some of the examples of oob methods we've 
> come up with in this document, e.g. URI in the SDP or equivalent 
> pointing to an HTTP or RTSP url for unicast use, another SDP for a 
> separate multicast channel containing just the headers for a multicast
> session, or even a private fixed mapping for broadcast applications. 
> Also, a hash could be included to allow caching. This helps illustrate 
> what we're thinking even if we don't give any details.

I'll add an example section with some usage scenarios. If someone wants 
something in particular please ask.

In list:

- stream radio.
  - live dj performance (mix of live and stored content)
  - multicast/unicast consideration

- conference (multicast)
  - clients joining and departing at random time
  - rate adaptation
  - latency consideration

lu

-- 

Luca Barbato

Gentoo/linux Developer		Gentoo/PPC Operational Leader
http://dev.gentoo.org/~lu_zero