#23 added statement about further plans

README.md

@@ -34,7 +34,7 @@ However, the specification [does not define](https://tools.ietf.org/html/rfc6749
   is _beyond the scope_ of this specification.  The authorization server
   _may be the same server_ as the resource server _or a separate entity_.
 
-The library assumes an existence of external server which implements [API](http://planb.readthedocs.io/en/latest/intro.html#token-info) of [Plan B Token Info service](https://github.com/zalando/planb-tokeninfo) and which is responsible for the validation of access tokens. The Plan B Token Info service API is not compatible with [OAuth 2.0 Token Introspection](https://tools.ietf.org/html/rfc7662), so the library does not cover an interaction with authorization servers which might implement token introspection. However, support of token introspection can be easily added by providing an implementation of `org.zalando.zhewbacca.AuthProvider` interface.
+The library assumes an existence of external server which implements [API](http://planb.readthedocs.io/en/latest/intro.html#token-info) of [Plan B Token Info service](https://github.com/zalando/planb-tokeninfo) and which is responsible for the validation of access tokens. The Plan B Token Info service API is not compatible with [OAuth 2.0 Token Introspection](https://tools.ietf.org/html/rfc7662), so the library does not cover an interaction with authorization servers which might implement token introspection. However, support of token introspection can be easily added by providing an implementation of `org.zalando.zhewbacca.AuthProvider` interface. We want to remove coupling to Plan B before the end of Q3 2017 and provide better way to integrate authorization servers (see [issue-33](https://github.com/zalando-incubator/play-zhewbacca/issues/33)).
 
 **Note: the library does not validate access tokens on its own**.