All interested parties....
I feel as though we are quite far from reaching a solution to the ICV coding problem. There were a number of proposals made some providing solutions that may or may not have been backward compatible.
As I have approximately 72 hours to get this into the white paper of the Implementers guide... we need to come to closure.
An alternative is to 'fix' this in rev3 of H.225.0 (when and/if we include non-repudiation). One argument for this is that if you want ICV/non-repudiation you may run IPSec or some other security 'tunnel' which keeps the complexitites from H.225.0 and ASN.1
Thoughts?.... (clock is ticking) jimt.
***************************************************** *** +1-503-264-8816(voice) Intel - Hillsboro, OR. *** *** mailto:jim.toga@intel.com mailto:james.toga@ties.itu.int *** *** PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41 *** *****************************************************