Interpreting "+" in query component of https:// scheme URIs.

[Matt Randall <[e-mail]>]

Hopefully this is a quick question with a straightforward answer.  The https URI scheme (RFC7230) denotes that it simply follows the definition of the query component from the base URI RFC (RFC3986).  Query seems to allow for all reserved and unreserved characters (with some caveats around "?" and "/") in the value, and reserves none of the reserved characters as delimiters.

From purely a specifications perspective, my assumption (absent de-facto legacy behaviors of certain clients and www-form-urlencoded query string behaviors) would be to treat the plus sign literally, just as if I would in the path component.  Would this be a correct interpretation given the following statement in section 2.2?:
If a reserved character is found in a URI component and
no delimiting role is known for that character, then it must be
interpreted as representing the data octet corresponding to that
character's encoding in US-ASCII.

I couldn't find anything in the current specifications that would indicate that "+" has a 
defined delimiting role for the https:// URI scheme.

Thank you in advance,

Matt Randall