This draft agenda can be found at URL:
Revised versions might become available as draft-agenda-2, 3, etc.
The issues in this draft agenda are more fully described in the issues list. The issues in this draft agenda are the same as in the issues list and listed in the same order, except that I have moved the three most controversial to the top of the agenda, to be discussed first.
|Agenda Item No.||Issue No. in Issue List||Time||Description|
Require exact match of links and Content-Location headers
Linked body parts SHOULD or MUST be inside multipart/related
Multipart/related versus Content-Disposition
LWSP in URL-s in e-mail headers
Encoding of 8-bit characters in URL-s in e-mail headers
Relation to HTTP 1.1 specification of Content-Base and Content-Location
Resolving relative URLs
Support for fast rendering
Allow File URLs
Allow non-IETF URIs
Encoding of non-ascii characters in HTML bodies; allow all combinations
Recommend any encoding as better than another?
Line breaks must be CRLF, but only before QP/Base64 decoding.
Base64 should of course also be allowed.
Multipart/related become a proposed or draft standard?
An informational RFC?
Recipients who cannot handle multipart/related
Recipients without full Internet connectivity
Default ACTION in forms
Keep Alex Hopmann as editor?
Reports on implementation status for various implementations
Future work plan
|ZB||21||5||Any other issues|