1. The problem that in some cases it is not possible to know what is an URL and not an URL in HTML code containing applets, and that thus mhtml maybe will not work in such cases.
2. Has any interoperability tests between working implementations of the mhtml-spec been done yet?
3. Planning of interoperability tests. What should be tested?
(see appendix).
4. Will all or only a subset of the functions (see appendix) be implemented by current implementations?
5a. Will rewriting of URLs be done before sending out HTML messages?
5b. Will rewriting of URLs be done after receipt of HTML messages?
5c. Which of the implementation methods described in chapter 4 of draft-ietf-mhtml-info-05.txt will be used?
6. Use of multipart/alternative, inside or outside of multipart/related (chapter 8 of draft-ietf-mhtml-info-05.txt).
7. Go through draft-ietf-mhtml-info-05.txt chapter by chapter and check which comments there are: Can also the info document be forwarded for publication as an informational document (not a standard)?
|
Function |
Implementation for generation |
Implementation for receipt |
|
Use of multipart/related |
|
|
|
- for HTML with embedded graphics, etc. |
|
|
|
- for sets of related HTML objects |
|
|
|
Reference to embedded body parts |
|
|
|
- using Content-ID-s |
|
|
|
- using absolute Content-Location |
|
|
|
- using relative URLs and no Content-Location |
|
|
|
Use of combinations of multipart/related and
multipart/alternative |
|
|
|
Use of content-disposition header for recipients who do
not handle mhtml |
|
|
|
Use of HTML messages whose URLs for enbedded graphics
must be resolved through HTTP retrieval from the source |
|
|
|
Use of the message/external-body method for sending HTML
in e-mail |
|
|
|
Use of character sets in HTML messages |
|
|
|
- US-ascii |
|
|
|
- ISO 8859-1 |
|
|
|
- Other ISO 8859 variants |
|
|
|
- ISO 10646/Unicode |
|
|
|
- Other character sets |
|
|