
This is a request for review application/lost+xml, which is described in http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-06.txt . Comments to the authors or the working group mailing list (ecrit@ietf.org) would be welcome; cc'ing any comments to the AD (Jon Peterson, jon.peterson@neustar.biz) would also be welcome since this is currently also in his review queue. thanks, Ted

* Ted Hardie wrote:
This is a request for review application/lost+xml, which is described in http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-06.txt . Comments to the authors or the working group mailing list (ecrit@ietf.org) would be welcome; cc'ing any comments to the AD (Jon Peterson, jon.peterson@neustar.biz) would also be welcome since this is currently also in his review queue.
For the charset parameter, instead of "Indicates the character encoding of enclosed XML." it should have a pointer to RFC 3023's application/xml charset parameter. The "Encoding considerations" should simply use one of the values defined in RFC 4288 (7bit, 8bit, binary, framed). It would be useful if "Security considerations" had a pointer to the security considerations discussed elsewhere in the draft. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
participants (2)
-
Bjoern Hoehrmann
-
Ted Hardie