@@ -911,7 +911,7 @@ Where "specific_name" is the name of the out of band delivery method.
<vspaceblankLines="1"/>
<thangText="configuration:"> the <xreftarget="rfc3548">base16</xref> (hexadecimal) representation of the <xreftarget="Packed Headers">Packed Headers</xref>.
<thangText="configuration:"> the <xreftarget="rfc3548">base64</xref> representation of the <xreftarget="Packed Headers">Packed Headers</xref>.
</t>
</list>
</t>
...
...
@@ -931,9 +931,9 @@ stream. Such aggregates MAY be compressed using either
<xreftarget="BZ2">bzip2</xref> or <xreftarget="rfc1952">gzip</xref>.
A <xreftarget="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". The trailing '/' discriminates which of two methods are in use.</t>
compressed extension if applies, a "!" and the <xreftarget="rfc3548">base64</xref> 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.</t>
</list>
</t>
...
...
@@ -1076,14 +1076,14 @@ below.
configuration packet is inlined in the sdp, other configurations could be
fetched at any time from the first provided uri using or all the known
configuration could be downloaded using the second uri. The inline
<xreftarget="rfc3548">base16</xref> configuration string is omitted because of
<xreftarget="rfc3548">base64</xref> configuration string is omitted because of