Re: [AVT] draft-ietf-avt-rtp-vorbis: configuration-uri

[Luca Barbato <lu_zero at gentoo.org>]

Peter Saint-Andre wrote:
> As long as the text is changed to say that the format you describe is
> recommmended, I'm fine (because we would specify the XMPP URI format in
> a different spec anyway).

This is the proposed clarification, I'm tempted to ditch the
delivery_method since:

* every implementation MUST handle in_band delivery.
* inline delivery is defined by "configuration"
* out_band delivery is defined by "configuration-uri"

That would make the fmtp smaller.

-      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
+      configuration-uri:  the URI [4] 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 bzip2
-         [15] or gzip [13].  A sha1 [9] checksum MAY be provided for
-         aggregates.  In this latter case the URI will end with the
+         Ident number, or multiple packets could be aggregated in a
+         single stream.  Such aggregates MAY be compressed using either
+         bzip2 [16] or gzip [14].  A sha1 [10] 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 base64 [8] representation of the
+         applies, a "!" and the base64 [9] representation of the
          sha1hash of the above mentioned compressed aggregated as in:
          "protocol://path/to/resource/aggregated.bz2!sha1hash".  The
-         trailing '/' discriminates which of two methods are in use.  It
-         MUST follow the associated delivery method parameter (either
-         "in_band" or "out_band").
+         trailing '/' discriminates which of two methods are in use.
+         The configuration-uri MUST follow the associated delivery
+         method parameter ("out_band").  Non hierarchical protocols and
+         protocols using for special purposes the '!' separator MAY
+         point just to a resource aggregate using their specific syntax.

I hope it addresses the xmpp issue.

-- 

Luca Barbato

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


_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt