Update README.md

Author: oroulet

README.md

@@ -13,7 +13,7 @@ OPC UA binary protocol implementation is quasi complete and has been tested agai
 
 Most low level code is autogenerated from xml specification, thus adding missing functionnality to client or server is often trivial.
 
-Using Python > 3.4 the dependencies are cryptography and dateutil. If using python 2.7 or pypy < 3 you also need to install enum34, trollius(asyncio), and futures(concurrent.futures), with pip for example.
+Using Python > 3.4 the dependencies are cryptography, dateutil and pytz. If using python 2.7 or pypy < 3 you also need to install enum34, trollius(asyncio), and futures(concurrent.futures), with pip for example.
 
 coveryage.py reports a test coverage of over 90% of code, most of non-tested code is autogenerate code that is not used yet.
 
@@ -60,8 +60,8 @@ Tested servers: freeopcua C++, freeopcua Python, prosys, kepware, beckoff, winCC
 
 Client: what is not implemented yet
 * localized text feature
-* adding some missing modify methods
 * XML protocol
+* maybe automatic reconnection...
 
 
 Server: what works:
@@ -82,12 +82,13 @@ Server: what works:
 Tested clients: freeopcua C++, freeopcua Python, uaexpert, prosys, quickopc
 
 Server: what is not implemented
+* session restore
 * alarms
 * XML protocol
 * views
 * localized text features
 * better securty model with users and password
-* adding some missing modify methods
+
 
 Server: Running on a Raspberry Pi