This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The form submission algorithm references RFC2045 for the definition of base64. The newest refrence for base64 is RFC4648. Please update the reference.
Please note that RFC 4648 defines several Base 64 encodings, so please make sure the reference is precise enough. Proposal: "A base-64 encoded representation of data. (See "Base 64 Encoding", Section 4 of [RFC4648])"
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. RFC4648 says to refer to the encoding as "base64", so that's what I did. That seems unambiguous given the definitions in RFC4648.
Checked in as WHATWG revision r5536. Check-in comment: Update references to base64 http://html5.org/tools/web-apps-tracker?from=5535&to=5536