[xiph-rtp] vorbis-rtp update (almost candidate)

[Luca Barbato]

Thanks to Federico and Michael for reviewing it early.

Changes:

- Comment header disallowed completely
- The Vorbis identification and setup headers are packed together
- Added more references.

Yet to be done:

- Double check for formal errors (wording, diagrams, grammar and typos)
- Update credits sections and the release and expire dates (target 15
October)

I hope that the ideas in the rfc are ok for everybody even if the form
could be refined.

lu

gzipped xml sources and produced text attached.
--
Luca Barbato

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-ietf-avt-vorbis-rtp-00.xml.gz
Type: application/gzip
Size: 10270 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/xiph-rtp/attachments/20051007/edb86b78/draft-ietf-avt-vorbis-rtp-00.xml-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-ietf-avt-vorbis-rtp-00.txt.gz
Type: application/gzip
Size: 11498 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/xiph-rtp/attachments/20051007/edb86b78/draft-ietf-avt-vorbis-rtp-00.txt-0001.bin

[David Barrett]

Looks really good. My only two questions/concerns:

- While I don't use the comment header, it seems like a key feature to
Vorbis overall, and I'm not sure why we're dropping it entirely. The
comment packet seems useful both in obvious ways (updating what's
displayed to users mid-stream) and non-obvious ways
(application-specific metadata delivered inline via RTP). I entirely
see why it shouldn't be included with the packed setup/codebook headers,
but I don't see why it should be suppressed altogether.

o The optional parameter "configuration-uri", when present, MUST be
included in the SDP "a=fmpt" attribute.
If the stream comprises chained Vorbis files the configuration and
codebook headers for each file SHOULD be packaged together and passed
to the client using the configuration attribute if all the files to
be played are known in advance. {FIXME: define the configuration
package}
The Vorbis configuration specified in the configuration-uri attribute
MUST pointto a location where all of the Configuration Packets needed
for the life of the session reside.

1) By "the configuration and codebook headers" do you actually mean "the
setup and codebook headers"?

2) By "using the configuration attribute" are you referring to the
"configuration-uri" attribute, or some other "configuration" attribute?
Do you mean a base16-encoded (for example) insertion of the packed
setup/codebook headers, or a link to where these can be downloaded?

3) Typo in the third paragraph: "pointto". Here it says I can download
using a URI. So does this mean there are actually three delivery
vectors: inline, embeddded in the SDP, and via a URI?

Other than these minor confusions, I think it looks great.

-david

Thanks to Federico and Michael for reviewing it early.
- Comment header disallowed completely
- The Vorbis identification and setup headers are packed together
- Added more references.
- Double check for formal errors (wording, diagrams, grammar and typos)
- Update credits sections and the release and expire dates (target 15
October)
I hope that the ideas in the rfc are ok for everybody even if the form
could be refined.
lu
gzipped xml sources and produced text attached.
------------------------------------------------------------------------
_______________________________________________
xiph-rtp mailing list
http://lists.xiph.org/mailman/listinfo/xiph-rtp

[Luca Barbato]

Post by David Barrett
- While I don't use the comment header, it seems like a key feature to
Vorbis overall, and I'm not sure why we're dropping it entirely. The
comment packet seems useful both in obvious ways (updating what's
displayed to users mid-stream) and non-obvious ways
(application-specific metadata delivered inline via RTP). I entirely
see why it shouldn't be included with the packed setup/codebook headers,
but I don't see why it should be suppressed altogether.

Metadata should be part of the container infrastructure, not the codec
one. The comment feature in ogg/vorbis is quite abused already and the
decision was to avoid the same issue for vorbis-rtp.
[snip]

Post by David Barrett
1) By "the configuration and codebook headers" do you actually mean "the
setup and codebook headers"?

I mean Configuration Packet, looks like that one slipped the first cross
read, thank you =)

Post by David Barrett
2) By "using the configuration attribute" are you referring to the
"configuration-uri" attribute, or some other "configuration" attribute?
Do you mean a base16-encoded (for example) insertion of the packed
setup/codebook headers, or a link to where these can be downloaded?

The "configuration" attribute (if someone could come up with a better
name I'll change it immediately) is the parameter in which put the
base16 encoded Configuration Packets. I guess I should change the SDP
inline rule to use the same format used in the out of band delivery for
consistency.

Post by David Barrett
3) Typo in the third paragraph: "pointto". Here it says I can download
using a URI. So does this mean there are actually three delivery
vectors: inline, embeddded in the SDP, and via a URI?

2 defined vectors: inline and embedded SDP
Many user defined vectors: rtsp based, http based, xmpp based... The
only constraint is that the medium is reliable.

lu

[Luca Barbato]

Fixed the latest 2 issues. I there aren't any other problems, I'll
update the credits and resend it before consider it ready for submission
(maybe another 2 full rereads are due)

lu
--
Luca Barbato

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-ietf-avt-vorbis-rtp-00.txt.gz
Type: application/gzip
Size: 11452 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/xiph-rtp/attachments/20051008/f90d94bb/draft-ietf-avt-vorbis-rtp-00.txt-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-ietf-avt-vorbis-rtp-00.xml.gz
Type: application/gzip
Size: 10240 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/xiph-rtp/attachments/20051008/f90d94bb/draft-ietf-avt-vorbis-rtp-00.xml-0001.bin