RFC 6121 section 8.5.3 defines how a server should process a stanza that is addressed to a full JID. When a matching resource is found, the specification does not distinghuis between an “available” resource and a “connected” resource. Instead, it refers to an “available resource or connected resource” (this is different for processing of stanzas to bare JIDs, in sectino 8.5.2).

Openfire’s implementation of routing stanzas addressed to a full JID of a resource for which a route exist does evaluate the ‘availability’ of the route. This contradicts the RFC, which doesn’t differentiate between ‘available’ and ‘connected’. Openfire should not differentiate either.