Draft of the roadmap to OpenSERv1.1.0
-------------------------------------

OpenSER core:

- generic communication interface which must offer an abstract layer between
  core/modules and transports (e.g., fifo, unix sockets)
- move the code of the implemented trasports as module
- NAPTR lookup
- TLS multi-domain support
- TLS configuration values to be set via a module, to keep core less exposed
  to often changes
- better error reporting and handling
- pseudo-variables to be introduced in different modules
- security checks of destination addess (white/black lists)
- memory defragmentation
- tcp enhancements
- OpenSER command line interface (terminal)

OpenSER modules:

[acc]
- possibility to disable values from db_fmt

[avpops]
- more coherent format of the parameters (=>to be used the one
  from pseudo-variables)
- ability to take the name of the AVP to be loaded from the value
  of another AVP
- global avps - avps to be stored during run time, shared between processes
- local avps - avps to be stored locally, specific per script, not per
  transaction

[cpl-c]
- possibility to configure table and columns' names
- import registrar paramters insted of redefine

[dbtext]
- replace support
- reload support

[dispatcher]
- serial forking when selected destination fails
- database support

[enum]
[-] - parallel/serial forking based on order and preference fields

[postgres]
- connection pool
- shift to memory manager used by openser

[tm]
- unification of t_relay_to_*() in a form of t_relay_to("proto:host:port")

[uac]
- qop authentication support
- proper CSeq value after authentication challenge

[usrloc]
- better handling of the natted contacts, to uniquely identify a contact
- cacheless usrloc
- path support for registrations
- sip instance support
- possibility to attach to a contact a set of values (similar to log_extra
  in acc)