[xiph-rtp] Updated drafts please review

[Luca Barbato]

We have about a 3 days window, I tried to polish them a bit (removing
double spaces and some typos) and to address the issues found in the ref
code.

the rc rfc are available in the usual[1] places[2] as well as the ref
code[3].

Please have a look and report back withing the 23rd

lu

[1]http://svn.xiph.org/trunk/theora/doc/draft-barbato-avt-rtp-theora-01.{txt,xml}
[2]http://svn.xiph.org/trunk/vorbis/doc/draft-ietf-avt-rtp-vorbis-01.{txt,xml}
[3]http://svn.xiph.org/trunk/xiph-rtp/

[Tor-Einar Jarnbjo]

Post by Luca Barbato
[2]http://svn.xiph.org/trunk/vorbis/doc/draft-ietf-avt-rtp-vorbis-01.{txt,xml}

A few things:

3.1.1. Last sentence: It is up to the ...

6.1.1 What is "http://another/path/to/resource/aggregate.bz2!sha1hash"
suppose to mean?

There seem to be a generally high number of punctuation mistakes in the
text and I am not able to follow the logic behind the capitalization of
specific words ...

Tor

[Luca Barbato]

Post by Tor-Einar Jarnbjo

Post by Luca Barbato
[2]http://svn.xiph.org/trunk/vorbis/doc/draft-ietf-avt-rtp-vorbis-01.{txt,xml}

3.1.1. Last sentence: It is up to the ...

Explain the problem

Post by Tor-Einar Jarnbjo
6.1.1 What is "http://another/path/to/resource/aggregate.bz2!sha1hash"
suppose to mean?

This way looks better?

+<t hangText="configuration-uri:"> the URI of the configuration headers
in case
of out of band transmission. In the form of
"protocol://path/to/resource/". Depending on the specific method, a
single configuration packet could be retrived by its number, or multiple
packets could be aggregated in a single stream. Such aggregates MAY be
compressed using either <xref target="BZ2">bzip2</xref> or <xref
target="rfc1952">gzip</xref>. A <xref target="FIPS180">sha1</xref>
checksum MAY be provided for aggregates. In this latter case the URI
will end with the aggregate name, followed by its compressed extension
if applies, a "!" and the hexadecimal representation of the sha1hash of
the above mentioned compressed aggregatedas in:
"protocol://path/to/resource/aggregated.bz2!sha1hash".</t>

+<t>a=fmtp:98 delivery-method=in_band; configuration=base16string1;
delivery-method=out_band/rtsp;
configuration-uri=rtsp://path/to/the/resource;
delivery-method=out_band/http;
configuration-uri=http://another/path/to/resource/aggregate.bz2!8b6237eb5154a0ea12811a94e8e2697b3312bc6c;</t>

Post by Tor-Einar Jarnbjo
There seem to be a generally high number of punctuation mistakes in the
text and I am not able to follow the logic behind the capitalization of
specific words ...

Please point the cases and I'll try to fix them.

lu

[Tor-Einar Jarnbjo]

Post by Luca Barbato

Post by Tor-Einar Jarnbjo
3.1.1. Last sentence: It is up to the ...

Explain the problem

The current sentence reads: "Is up to the client provide a minimal size
comment header to the decoder if required by the implementation." A few
words are missing. It should obviously be: "It is up to the client to
provide ...".

Another one in 2.1: "and shown in Figure Figure 1."

Post by Luca Barbato
This way looks better?

Sort of, at least I understood what is ment. I missed the discussion (if
there has been any) on supporting compressed (bzip or gzip) headers. Is
it really necessary to add such complexity to the clients? Is the
compression used being defined through the URL ending or should it be
specified in e.g. the content type header if using HTTP retrieval?

Post by Luca Barbato

Post by Tor-Einar Jarnbjo
There seem to be a generally high number of punctuation mistakes in the
text and I am not able to follow the logic behind the capitalization of
specific words ...

Please point the cases and I'll try to fix them.

I'm not a native speaker, so this may be completely wrong. They are not
the only mistakes I think are included, but I really have no time spell
checking the entire text:

1.

Vorbis is a general purpose perceptual audio codec ... A comma is
missing between purpose and perceptual.

3.

Unlike other mainstream audio codecs Vorbis has no statically ... Comma
between codecs and Vorbis
... of a comment header packet which gives ... Comma between packet and
which

Through sections 3.x, several expressions are written capitalized
without obvious meaning (this may of course be some odd RFC guideline
though): "Vorbis Packed Configuration", "Configuration", "Packed
Configuration", "Vorbis Packed Configuration Packets", "Ident", "Packed
Configuration Payload", "Fragment", "Packed configuration" (here capital
P, minuscule c) and so on.

Tor

[Luca Barbato]

http://wiki.hydrogenaudio.org/index.php?title=Listening_Tests
Also I would remove the reference to the reference encoder.

Better dump that part or extend it?

Fabio