Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • ietf.org/archive/id/draft-iab-protocol-maintenance-05.html Commented Jul 13, 2024 at 10:40
  • 3
    Unfortunately, we can't relax validation rules in public interface, so we have to reject even small discrepancies. The reason is simple - relaxed requirements is a feature(even if it is not documented), users rely on features. Removal of such feature is backward incompatible. Making irreversible changes like that should be done only when all other options are exhausted. Initial version of your program HAS TO contain the strictest validation possible, relax it only after user feedback and careful consideration. Commented Jul 13, 2024 at 15:26
  • rfc-editor.org/rfc/rfc9413 Commented Jul 13, 2024 at 16:32
  • 2
    @greenoldman in this context FF protects you from specification "bugs". If specification is ill-defined, parser failures will help discovering this. Commented Jul 15, 2024 at 10:26
  • 1
    @greenoldman: ok, I reworded my answer a little bit, maybe it is clearer now. Just search this site about "Fail fast", you will surely find lots of Q&As which associate this principle with bugs in code. Commented Jul 15, 2024 at 14:14