27039 2014-10-13 23:49:06 +0000 Replace references to RFC 2388 with RFC XXXX based on draft-ietf-appsawg-multipart-form-data-05.txt 2015-06-17 03:34:04 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WONTFIX P3 editorial --- 1 lmm dave.null mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 113060 0 lmm 2014-10-13 23:49:06 +0000 This requires a little more coordination. http://tools.ietf.org/html/draft-ietf-appsawg-multipart-form-data-05 went through Working Group Last Call in the IETF applications area working group without much review. (Only comments were typos, now fixed). It needs IETF last call for final approval. Please review, and then update HTML: I think for the most part you can replace RFC 2388 with RFC XXXX based on draft-ietf-appsawg-multipart-form-data-05.txt http://www.w3.org/TR/html5/forms.html#multipart-form-data and then update the reference once final approval and assignment of RFC number. 113085 1 robin 2014-10-14 09:48:56 +0000 I don't quite understand — it seems to me that we shouldn't update to "RFC XXXX", that's a bit... provisional. We can certainly update the next gen draft when the number is assigned. 121159 2 mike 2015-06-17 03:34:04 +0000 No response to comment 1 so moving to resolved=wontfix for now. I don't think we can get agreement to put a literal "RFC XXX" in the References section, nor do I believe most people would say we should. The right thing to do here would seem to be to wait until we actually have a new RFC that replaces RFC 2388, then open a new bug for that.