Related to #13

Should parse fail when content-disposition header contains a parameter which field is not decodable ?
Today it fails. Shouldn't it only ignore the parameter and move on ?

• what specifically would be considered a recoverable parse failure vs an unrecoverable failure ?
• what should be returned when various different recoverable failures occur ?
• how can we keep intact a strict mode for any users who would want a complete failure ?
• what, if any, guidance does the RFC have on this ?