different methods for delivering this configuration data to a
client, both in-band and out-of-band which is detailed below.
In order to set up an initial state for the client application the
-configuration MUST be inlined in the session setup informations.
+configuration MUST be conveyed via the signalling channel used to setup
+the session. One example of such signalling is
+<xref target="rfc4566">SDP</xref> with the
+<xref target="rfc3264">Offer/Answer Model</xref>.
Changes to the configuration MAY be communicated via a re-invite,
conveying new SDP, or sent in-band in the RTP channel.
Implementations MUST support in-band delivery of updated codebooks,
<t>
The port value is specified by the server application bound to the address
-specified in the c= line. The sample rate and channel count value specified
-in the rtpmap attribute SHOULD match the current Vorbis stream or considered
-the maximum number of channels to be expected and the least common multiple
-sample rate for the session. The Configuration payload delivers the exact
-information, thus the SDP information SHOULD be considered as a hint.
-An example is found below.
+specified in the c= line. The channel count value specified in the rtpmap
+attribute SHOULD match the current Vorbis stream or considered the maximum
+number of channels to be expected. The timestamp clock rate MUST be a multiple
+of the sample rate, different payload number MUST be used if the clock rate
+changes. The Configuration payload delivers the exact information, thus the
+SDP information SHOULD be considered as a hint.
+An example is found below.
</t>
<section anchor="SDP Example" title="SDP Example">