All,
A clash of overlapping OIDs values has been detected in H.235Version 2.
OIDs "K", "L" and "M" in the Appendix I currently have the same value assigned as OIDs "A", "B" and "R" of Annex E. However, of course each of the mentioned OIDs shall have a unique value in order to unambiguously identify its purpose. Implementations deploying OIDs from Annex E and Appendix I might thus currently run into interoperability problems.
It is proposed to re-allocate the OIDs in Appendix I with new and distinct values (see below).
Object Identifier Reference Object Identifier Value Description "K" {itu-t (0) recommendation (0) h (8) 235 version (0) 2 31} indicates a RADIUS challenge in the ClearToken "L" {itu-t (0) recommendation (0) h (8) 235 version (0) 2 32} indicates a RADIUS response (conveyed in the challenge field) in the ClearToken "M" {itu-t (0) recommendation (0) h (8) 235 version (0) 2 33} indicates BES default mode with a protected password in the ClearToken Table I.1/H.235: Object Identifiers used by Appendix I.4.6
Please, let me hear your opinion on whether the proposal appears acceptable, or suggest your alternative otherwise.
With kind regards
Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Phone: +49 89 722 55790 | Martin Euchner Fax : +49 89 722 47713 | Siemens AG | ICN M SR 3 mailto:Martin.Euchner@icn.siemens.de mailto:Martin.Euchner@icn.siemens.de | mailto:martin.euchner@ties.itu.int mailto:martin.euchner@ties.itu.int | Hofmannstr. 51 Intranet: http://intranet.icn.siemens.de/marketing/sr/pages/122/122_euchner.htm http://intranet.icn.siemens.de/marketing/sr/pages/122/122_euchner.htm | D-81359 Muenchen Internet: http://www.siemens.de/ http://www.siemens.de/ | __________________ | Germany -----------------------------------------------------------------------