At 08.25 -0800 97-11-25, Alex Hopmann wrote:
> The Content-Location header MUST be unique within its enclosing
> multipart/related structure.

Do you mean to say that the following is *not* allowed:

   Content-Base: http://www.ietf.cnri.reston.va.us/
   Content-Type: multipart/related; boundary="boundary-example";
                 type="text/html"

   --boundary-example
      Content-Type: text/html; charset=ISO-8859-1
      Content-Transfer-Encoding: QUOTED-PRINTABLE

      ... text of the HTML document, which might contain URIs
      referencing resources in other body parts, for example through
      statements such as:

      <IMG SRC="/images1/ietflogo.gif" ALT="IETF logo1">
      <IMG SRC="/images2/ietflogo.gif" ALT="IETF logo2">
      <IMG SRC="/images3/ietflogo.gif" ALT="IETF logo3">

      Example of a copyright sign encoded with Quoted-Printable: =A9
      Example of a copyright sign mapped onto HTML markup: &#168;

      --boundary-example
      Content-Base: http://www.ietf.cnri.reston.va.us/images1/
      Content-Location: ietflogo.gif

      --boundary-example
      Content-Base: http://www.ietf.cnri.reston.va.us/images2/
      Content-Location: ietflogo.gif

      --boundary-example
      Content-Base: http://www.ietf.cnri.reston.va.us/images3/
      Content-Location: ietflogo.gif

      --boundary-example--

Have we agreed on this? It is not logical, but will probably make
some implementers happy! Other implementors may not be happy!

------------------------------------------------------------------------
Jacob Palme <[log in to unmask]> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/~jpalme