ITU - Telecommunication Standardization Sector Temporary Document 3030/Rev.2

STUDY GROUP 17

Geneva, 27 February – 8 March 2002

Question(s): 11/17; 12/17

SOURCE: ITU-T SG 17 (Geneva, 27 January-8 March 2002)

TITLE: Liaison statement to UPU on the illegal use of the {joint-iso-itu-t(2) upu(40)} arc in the registration tree of object identifiers

_____________

LIAISON STATEMENT

TO: UPU (Universal Postal Union)

APPROVAL: Agreed to at Study Group 17 meeting

FOR: Action

DEADLINE: October 2002

CONTACT: Mr. Olivier Dubuisson Tel: +33 2 96 05 38 50

France Télécom R&D Fax: +33 2 96 05 39 45

DTL/TAL E-mail: Olivier.Dubuisson@francetelecom.com

22307 Lannion Cédex

France

Q.12/17 is responsible for the X.660-series of ITU-T Recommendations that deal with registration of object identifiers. This is a joint work with the ISO/IEC JTC 1/SC 6 (ISO/IEC 9834 series of standards).

According to information we have received, it appears that some years ago you started using the arc {joint-iso-itu-t(2) upu(40)}.

We have no record of a registration for that arc in conformance with the registration rules standardized in ITU-T Rec. X.662 | ISO/IEC 9834-3.

We note that according to clause 5 of ITU-T Rec. X.662 | ISO/IEC 9834-3 arcs under {joint‑iso‑itu-t(2)} can only be assigned for joint work between ITU-T and ISO/IEC. Moreover each such arc has to be defined in a joint ITU-T Recommendation | ISO/IEC Standard as shown by this extract of ITU-T Rec. X.662 | ISO/IEC 9834-3, clause 6:

<< The elements of information of a register entry shall be:

a) […]

b) an area of joint ISO-ITU-T work in which the value is to be applied, specified by the ISO work item number and number of the International Standard in which the RH-name component value is specified, and the ITU-T Study Group, Study Period, and Question, and the number of the CCITT and ITU-T Recommendation in which the RH-name component value is specified, and a brief title; >>

If it is at all possible, we would suggest that your organization consider registering under {itu‑t(0) identified-organization(4)} in conformance with the registration procedures given in ITU-T Rec. X.669, just as ETSI did, for example (see http://asn1.elibel.tm.fr/en/oid/root/itu-t/identified-organization/etsi/). You will note that ETSI is in no way related to or dependant from the ITU-T, i.e., your registering under this arc would have no meaning with respect to organizational structure or hierarchy.

Please be assured that we are prepared to take all possible measure to help solve this problem. Thus, if the upu(40) arc is already in wide use by the UPU, it seems to us that the best solution would be to create a Recommendation | International Standard that specifies the procedures for registration under {joint-iso-itu-t(2) upu(40)}.

This would ensure conformity with the approved Recommendations and International Standards, while allowing UPU to avoid modifying any existing applications that use the arc in question. If you wish to pursue this option, we would need to receive from you, in the first instance, some text that specifies what use you are making of the {joint-iso-itu-t(2) upu(40)} arc.

We would appreciate your letting us know your opinions concerning the best way to proceed.

____________________