It seems to me that most common concepts of “default” apply instead to configuration methods. And these are generally not bound by the version / firmware.
Example:
In general, only the most necessary protocols and ports associated with the firewall are opened. If you need more ports/protocols, the user will have to enable them by himself.
Then the firmware / version used does not matter. This is the “default” off.
There are similarities with the concepts of strategy and tactics. Then configuration belongs to strategy, while firmware/versions belong to tactics. Simply put: strategy is the plan, and tactics is the implementation of that plan.
I think when most Tweakers talk about “standard” they’re talking about configuration capabilities in general, not how those possibilities are implemented in firmware/release.
Either I don’t fully understand your question, or your question made you think.
In any case, AFP is an outdated network communications standard that does not apply to the vast majority of users who have purchased a piece of equipment. The manufacturer builds the connection as standard, because there are users, but by definition disables them.
Whatever the user needs, they should be able to enable it themselves. Not that it shouldn’t solve the problem for active users of this connectivity standard, but mostly it doesn’t matter because it’s already disabled by definition.
