Spec seems to contradict itself with respect to requiring Unix Domain Sockets

[KallynGowdy]

In the "Connectivity" section of the Protocol the spec states:

Only UNIX Domain Sockets MAY be used as endpoints. This will likely change in a future version of this specification to support non-UNIX platforms.

This appears to be a contradictory statement since RCF2119 says this about the term "MAY":

MAY - This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

However, the word "Only" seems to indicate that the feature is required. Which is it?

If Unix sockets are required, then I suggest we change the wording to:

UNIX Domain Sockets MUST be used as endpoints. This will likely change in a future version of this specification to support non-UNIX platforms.

And if they're not required:

UNIX Domain Sockets MAY be used as endpoints. This will likely change in a future version of this specification to support non-UNIX platforms.