Datasets:
Add 1,166 missing ITU-T recommendations (series A,D,I,N,O,R,S,U,Z + newer revs) parsed via Datalab Marker (accurate); update manifest + STATUS
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- .gitattributes +822 -0
- STATUS.md +2 -2
- manifest.jsonl +0 -0
- marked/A/T-REC-A.1-201909-I_PDF-E/2efe0a28a1013bcb779bd16fb83b2bde_img.jpg +3 -0
- marked/A/T-REC-A.1-201909-I_PDF-E/9c85bca234696b6b31056e12bd8def01_img.jpg +3 -0
- marked/A/T-REC-A.1-201909-I_PDF-E/raw.md +664 -0
- marked/A/T-REC-A.11-201211-I_PDF-E/62e1187eade1baedc296526bd9896580_img.jpg +3 -0
- marked/A/T-REC-A.11-201211-I_PDF-E/raw.md +221 -0
- marked/A/T-REC-A.12-201611-I_PDF-E/3b014ddc8eee22a3a4386e61414e2067_img.jpg +3 -0
- marked/A/T-REC-A.12-201611-I_PDF-E/raw.md +159 -0
- marked/A/T-REC-A.13-201909-I_PDF-E/daefb8d8ae0a06b249462b662fdab82b_img.jpg +3 -0
- marked/A/T-REC-A.13-201909-I_PDF-E/raw.md +245 -0
- marked/A/T-REC-A.18-202505-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.18-202505-I_PDF-E/49ebc29538f9ca089d77e7463c19b10e_img.jpg +3 -0
- marked/A/T-REC-A.18-202505-I_PDF-E/raw.md +312 -0
- marked/A/T-REC-A.2-201211-I_PDF-E/62e1187eade1baedc296526bd9896580_img.jpg +3 -0
- marked/A/T-REC-A.2-201211-I_PDF-E/raw.md +202 -0
- marked/A/T-REC-A.23-200010-I_PDF-E/c1dcc5d53f398ab2e17c6fe176fdb69c_img.jpg +3 -0
- marked/A/T-REC-A.23-200010-I_PDF-E/raw.md +116 -0
- marked/A/T-REC-A.24-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.24-202408-I_PDF-E/7cbb01986ee6e18967d2c8aa378a0c8a_img.jpg +3 -0
- marked/A/T-REC-A.24-202408-I_PDF-E/raw.md +603 -0
- marked/A/T-REC-A.25-202410-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.25-202410-I_PDF-E/b945a88ff54102a7b3b480f9483dacab_img.jpg +3 -0
- marked/A/T-REC-A.25-202410-I_PDF-E/raw.md +369 -0
- marked/A/T-REC-A.31-200810-I_PDF-E/c96dfc0f0ec4a44dd1d7e72fd0d99948_img.jpg +3 -0
- marked/A/T-REC-A.31-200810-I_PDF-E/raw.md +357 -0
- marked/A/T-REC-A.7-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.7-202408-I_PDF-E/raw.md +392 -0
- marked/A/T-REC-A.8-202401-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.8-202401-I_PDF-E/8eda6e54bb820fa3f0e0b4a96f35504d_img.jpg +3 -0
- marked/A/T-REC-A.8-202401-I_PDF-E/raw.md +354 -0
- marked/A/T-REC-A.Sup2-202212-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.Sup2-202212-I_PDF-E/raw.md +139 -0
- marked/A/T-REC-A.Sup3-201207-I_PDF-E/750009de35904633a4b5a89996010b7a_img.jpg +3 -0
- marked/A/T-REC-A.Sup3-201207-I_PDF-E/raw.md +362 -0
- marked/A/T-REC-A.Sup4-202601-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.Sup4-202601-I_PDF-E/raw.md +293 -0
- marked/A/T-REC-A.Sup6-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.Sup6-202408-I_PDF-E/raw.md +218 -0
- marked/A/T-REC-A.Sup7-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg +3 -0
- marked/A/T-REC-A.Sup7-202408-I_PDF-E/raw.md +273 -0
- marked/D/T-REC-D.000-201005-I_PDF-E/f80fa557938e5520d93e844924a94f76_img.jpg +3 -0
- marked/D/T-REC-D.000-201005-I_PDF-E/raw.md +392 -0
- marked/D/T-REC-D.1-199107-I_PDF-E/553900e5cb3b1da13d48f54237cf0e50_img.jpg +3 -0
- marked/D/T-REC-D.1-199107-I_PDF-E/edf4fa59aa5565f6d9a0e80d23537961_img.jpg +3 -0
- marked/D/T-REC-D.1-199107-I_PDF-E/raw.md +289 -0
- marked/D/T-REC-D.10-199107-I_PDF-E/8e273781c276cb5fc030cc0acb12ad61_img.jpg +3 -0
- marked/D/T-REC-D.10-199107-I_PDF-E/b0616bc7ab22530cad12687ef443d846_img.jpg +3 -0
- marked/D/T-REC-D.10-199107-I_PDF-E/raw.md +139 -0
.gitattributes
CHANGED
|
@@ -4327,3 +4327,825 @@ original/P/T-REC-P.340-200005-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
|
| 4327 |
original/P/T-REC-P.581-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4328 |
original/P/T-REC-P.501-202504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4329 |
original/P/T-REC-P.1204.1-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 4327 |
original/P/T-REC-P.581-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4328 |
original/P/T-REC-P.501-202504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4329 |
original/P/T-REC-P.1204.1-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4330 |
+
original/A/T-REC-A.1-201909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4331 |
+
original/A/T-REC-A.13-201909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4332 |
+
original/A/T-REC-A.18-202505-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4333 |
+
original/A/T-REC-A.23-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4334 |
+
original/A/T-REC-A.24-202408-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4335 |
+
original/A/T-REC-A.25-202410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4336 |
+
original/A/T-REC-A.31-200810-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4337 |
+
original/A/T-REC-A.7-202408-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4338 |
+
original/A/T-REC-A.8-202401-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4339 |
+
original/A/T-REC-A.Sup3-201207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4340 |
+
original/A/T-REC-A.Sup4-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4341 |
+
original/A/T-REC-A.Sup6-202408-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4342 |
+
original/A/T-REC-A.Sup7-202408-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4343 |
+
original/D/T-REC-D.000-201005-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4344 |
+
original/D/T-REC-D.1040-202008-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4345 |
+
original/D/T-REC-D.1041-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4346 |
+
original/D/T-REC-D.1101-202008-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4347 |
+
original/D/T-REC-D.1102-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4348 |
+
original/D/T-REC-D.1140-202008-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4349 |
+
original/D/T-REC-D.1141-202504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4350 |
+
original/D/T-REC-D.1142-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4351 |
+
original/D/T-REC-D.115-200406-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4352 |
+
original/D/T-REC-D.116-200406-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4353 |
+
original/D/T-REC-D.140-200206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4354 |
+
original/D/T-REC-D.150-199906-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4355 |
+
original/D/T-REC-D.170-201005-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4356 |
+
original/D/T-REC-D.180-200509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4357 |
+
original/D/T-REC-D.190-200206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4358 |
+
original/D/T-REC-D.198-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4359 |
+
original/D/T-REC-D.201-200212-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4360 |
+
original/D/T-REC-D.212-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4361 |
+
original/D/T-REC-D.224-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4362 |
+
original/D/T-REC-D.261-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4363 |
+
original/D/T-REC-D.262-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4364 |
+
original/D/T-REC-D.263-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4365 |
+
original/D/T-REC-D.264-202004-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4366 |
+
original/D/T-REC-D.265-202504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4367 |
+
original/D/T-REC-D.271-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4368 |
+
original/D/T-REC-D.285-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4369 |
+
original/D/T-REC-D.303R-199503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4370 |
+
original/D/T-REC-D.36-199503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4371 |
+
original/D/T-REC-D.4-200509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4372 |
+
original/D/T-REC-D.400R-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4373 |
+
original/D/T-REC-D.41-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4374 |
+
original/D/T-REC-D.50-201104-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4375 |
+
original/D/T-REC-D.502R-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4376 |
+
original/D/T-REC-D.52-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4377 |
+
original/D/T-REC-D.53-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4378 |
+
original/D/T-REC-D.600R-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4379 |
+
original/D/T-REC-D.603R-200212-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4380 |
+
original/D/T-REC-D.604R-200501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4381 |
+
original/D/T-REC-D.607R-202107-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4382 |
+
original/D/T-REC-D.608R-202205-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4383 |
+
original/D/T-REC-D.609R-202502-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4384 |
+
original/D/T-REC-D.7-199201-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4385 |
+
original/D/T-REC-D.700R-202403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4386 |
+
original/D/T-REC-D.90-199503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4387 |
+
original/D/T-REC-D.91-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4388 |
+
original/D/T-REC-D.93-200901-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4389 |
+
original/D/T-REC-D.96-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4390 |
+
original/D/T-REC-D.97-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4391 |
+
original/D/T-REC-D.Sup1-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4392 |
+
original/D/T-REC-D.Sup2-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4393 |
+
original/D/T-REC-D.Sup3-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4394 |
+
original/D/T-REC-D.Sup4-202004-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4395 |
+
original/D/T-REC-D.Sup5-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4396 |
+
original/E/T-REC-E.100SerSup1-201902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4397 |
+
original/E/T-REC-E.118-202509-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4398 |
+
original/E/T-REC-E.164-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4399 |
+
original/E/T-REC-E.164.1-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4400 |
+
original/E/T-REC-E.192-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4401 |
+
original/E/T-REC-E.300SerSup1-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4402 |
+
original/E/T-REC-E.300SerSup3-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4403 |
+
original/E/T-REC-E.300SerSup4-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4404 |
+
original/E/T-REC-E.300SerSup5-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4405 |
+
original/E/T-REC-E.300SerSup7-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4406 |
+
original/E/T-REC-E.371-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4407 |
+
original/E/T-REC-E.800SerSup10-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4408 |
+
original/E/T-REC-E.800SerSup9-202110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4409 |
+
original/E/T-REC-E.Sup11-202006-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4410 |
+
original/E/T-REC-E.Sup8-200911-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4411 |
+
original/F/T-REC-F.740.13-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4412 |
+
original/F/T-REC-F.740.14-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4413 |
+
original/F/T-REC-F.740.15-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4414 |
+
original/F/T-REC-F.743.39-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4415 |
+
original/F/T-REC-F.746.25-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4416 |
+
original/F/T-REC-F.748.54-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4417 |
+
original/F/T-REC-F.748.80-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4418 |
+
original/F/T-REC-F.749.17-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4419 |
+
original/F/T-REC-F.749.20-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4420 |
+
original/F/T-REC-F.749.21-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4421 |
+
original/F/T-REC-F.780.9-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4422 |
+
original/F/T-REC-F.Sup1-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4423 |
+
original/F/T-REC-F.Sup2-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4424 |
+
original/F/T-REC-F.Sup3-201609-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4425 |
+
original/F/T-REC-F.Sup4-202104-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4426 |
+
original/G/T-REC-G.100SerSup29-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4427 |
+
original/G/T-REC-G.100SerSup31-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4428 |
+
original/G/T-REC-G.100SerSup32-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4429 |
+
original/G/T-REC-G.671-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4430 |
+
original/G/T-REC-G.7716-202511-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4431 |
+
original/G/T-REC-G.781-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4432 |
+
original/G/T-REC-G.798-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4433 |
+
original/G/T-REC-G.798.2-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4434 |
+
original/G/T-REC-G.798.3-202602-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4435 |
+
original/G/T-REC-G.8264-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4436 |
+
original/G/T-REC-G.8274-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4437 |
+
original/G/T-REC-G.8275-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4438 |
+
original/G/T-REC-G.8275.2-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4439 |
+
original/G/T-REC-G.874-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4440 |
+
original/G/T-REC-G.976-202511-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4441 |
+
original/G/T-REC-G.9943-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4442 |
+
original/G/T-REC-G.Sup17-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4443 |
+
original/G/T-REC-G.Sup19-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4444 |
+
original/G/T-REC-G.Sup22-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4445 |
+
original/G/T-REC-G.Sup26-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4446 |
+
original/G/T-REC-G.Sup27-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4447 |
+
original/G/T-REC-G.Sup28-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4448 |
+
original/G/T-REC-G.Sup34-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4449 |
+
original/G/T-REC-G.Sup35-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4450 |
+
original/G/T-REC-G.Sup36-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4451 |
+
original/G/T-REC-G.Sup37-199810-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4452 |
+
original/G/T-REC-G.Sup39-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4453 |
+
original/G/T-REC-G.Sup40-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4454 |
+
original/G/T-REC-G.Sup41-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4455 |
+
original/G/T-REC-G.Sup42-201810-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4456 |
+
original/G/T-REC-G.Sup43-201102-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4457 |
+
original/G/T-REC-G.Sup44-200706-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4458 |
+
original/G/T-REC-G.Sup45-202209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4459 |
+
original/G/T-REC-G.Sup46-200905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4460 |
+
original/G/T-REC-G.Sup47-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4461 |
+
original/G/T-REC-G.Sup48-201006-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4462 |
+
original/G/T-REC-G.Sup49-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4463 |
+
original/G/T-REC-G.Sup5-198410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4464 |
+
original/G/T-REC-G.Sup50-201109-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4465 |
+
original/G/T-REC-G.Sup51-201706-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4466 |
+
original/G/T-REC-G.Sup52-201209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4467 |
+
original/G/T-REC-G.Sup53-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4468 |
+
original/G/T-REC-G.Sup54-201507-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4469 |
+
original/G/T-REC-G.Sup55-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4470 |
+
original/G/T-REC-G.Sup56-201602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4471 |
+
original/G/T-REC-G.Sup57-201507-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4472 |
+
original/G/T-REC-G.Sup58-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4473 |
+
original/G/T-REC-G.Sup59-201802-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4474 |
+
original/G/T-REC-G.Sup60-201609-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4475 |
+
original/G/T-REC-G.Sup61-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4476 |
+
original/G/T-REC-G.Sup62-201802-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4477 |
+
original/G/T-REC-G.Sup63-201802-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4478 |
+
original/G/T-REC-G.Sup64-201802-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4479 |
+
original/G/T-REC-G.Sup65-201810-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4480 |
+
original/G/T-REC-G.Sup66-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4481 |
+
original/G/T-REC-G.Sup67-201907-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4482 |
+
original/G/T-REC-G.Sup68-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4483 |
+
original/G/T-REC-G.Sup69-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4484 |
+
original/G/T-REC-G.Sup70-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4485 |
+
original/G/T-REC-G.Sup71-202312-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4486 |
+
original/G/T-REC-G.Sup72-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4487 |
+
original/G/T-REC-G.Sup73-202110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4488 |
+
original/G/T-REC-G.Sup74-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4489 |
+
original/G/T-REC-G.Sup75-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4490 |
+
original/G/T-REC-G.Sup76-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4491 |
+
original/G/T-REC-G.Sup77-202206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4492 |
+
original/G/T-REC-G.Sup78-202209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4493 |
+
original/G/T-REC-G.Sup79-202312-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4494 |
+
original/G/T-REC-G.Sup80-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4495 |
+
original/G/T-REC-G.Sup81-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4496 |
+
original/G/T-REC-G.Sup82-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4497 |
+
original/G/T-REC-G.Sup83-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4498 |
+
original/G/T-REC-G.Sup84-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4499 |
+
original/G/T-REC-G.Sup85-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4500 |
+
original/G/T-REC-G.Sup86-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4501 |
+
original/G/T-REC-G.Sup87-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4502 |
+
original/G/T-REC-G.Sup88-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4503 |
+
original/G/T-REC-G.Sup89-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4504 |
+
original/G/T-REC-G.Sup90-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4505 |
+
original/G/T-REC-G.Sup91-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4506 |
+
original/G/T-REC-G.Sup92-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4507 |
+
original/H/T-REC-H.222.0-202504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4508 |
+
original/H/T-REC-H.262-201202-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4509 |
+
original/H/T-REC-H.274-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4510 |
+
original/H/T-REC-H.430.9-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4511 |
+
original/H/T-REC-H.Sup1-199905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4512 |
+
original/H/T-REC-H.Sup10-200805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4513 |
+
original/H/T-REC-H.Sup11-200902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4514 |
+
original/H/T-REC-H.Sup12-201311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4515 |
+
original/H/T-REC-H.Sup13-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4516 |
+
original/H/T-REC-H.Sup14-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4517 |
+
original/H/T-REC-H.Sup15-201701-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4518 |
+
original/H/T-REC-H.Sup17-201411-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4519 |
+
original/H/T-REC-H.Sup18-201710-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4520 |
+
original/H/T-REC-H.Sup19-202104-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4521 |
+
original/H/T-REC-H.Sup2-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4522 |
+
original/H/T-REC-H.Sup20-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4523 |
+
original/H/T-REC-H.Sup21-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4524 |
+
original/H/T-REC-H.Sup3-200305-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4525 |
+
original/H/T-REC-H.Sup4-201606-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4526 |
+
original/H/T-REC-H.Sup5-200611-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4527 |
+
original/H/T-REC-H.Sup6-200604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4528 |
+
original/H/T-REC-H.Sup7-200805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4529 |
+
original/H/T-REC-H.Sup8-200805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4530 |
+
original/I/T-REC-I.113-199706-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4531 |
+
original/I/T-REC-I.130-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4532 |
+
original/I/T-REC-I.140-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4533 |
+
original/I/T-REC-I.210-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4534 |
+
original/I/T-REC-I.211-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4535 |
+
original/I/T-REC-I.220-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4536 |
+
original/I/T-REC-I.232.3-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4537 |
+
original/I/T-REC-I.233-199110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4538 |
+
original/I/T-REC-I.241.8-199510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4539 |
+
original/I/T-REC-I.251.10-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4540 |
+
original/I/T-REC-I.251.3-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4541 |
+
original/I/T-REC-I.251.7-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4542 |
+
original/I/T-REC-I.251.9-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4543 |
+
original/I/T-REC-I.252.2-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4544 |
+
original/I/T-REC-I.252.4-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4545 |
+
original/I/T-REC-I.253.1-199007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4546 |
+
original/I/T-REC-I.253.2-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4547 |
+
original/I/T-REC-I.253.3-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4548 |
+
original/I/T-REC-I.253.4-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4549 |
+
original/I/T-REC-I.254.1-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4550 |
+
original/I/T-REC-I.254.2-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4551 |
+
original/I/T-REC-I.255.1-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4552 |
+
original/I/T-REC-I.255.3-199007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4553 |
+
original/I/T-REC-I.256.3-199208-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4554 |
+
original/I/T-REC-I.257.1-199510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4555 |
+
original/I/T-REC-I.258.2-199502-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4556 |
+
original/I/T-REC-I.259.1-199607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4557 |
+
original/I/T-REC-I.310-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4558 |
+
original/I/T-REC-I.311-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4559 |
+
original/I/T-REC-I.312-199210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4560 |
+
original/I/T-REC-I.313-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4561 |
+
original/I/T-REC-I.320-199311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4562 |
+
original/I/T-REC-I.322-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4563 |
+
original/I/T-REC-I.324-199110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4564 |
+
original/I/T-REC-I.325-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4565 |
+
original/I/T-REC-I.326-200303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4566 |
+
original/I/T-REC-I.327-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4567 |
+
original/I/T-REC-I.328-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4568 |
+
original/I/T-REC-I.329-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4569 |
+
original/I/T-REC-I.330-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4570 |
+
original/I/T-REC-I.333-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4571 |
+
original/I/T-REC-I.340-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4572 |
+
original/I/T-REC-I.350-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4573 |
+
original/I/T-REC-I.352-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4574 |
+
original/I/T-REC-I.353-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4575 |
+
original/I/T-REC-I.354-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4576 |
+
original/I/T-REC-I.355-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4577 |
+
original/I/T-REC-I.356-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4578 |
+
original/I/T-REC-I.357-200011-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4579 |
+
original/I/T-REC-I.358-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4580 |
+
original/I/T-REC-I.361-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4581 |
+
original/I/T-REC-I.363.1-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4582 |
+
original/I/T-REC-I.363.2-200011-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4583 |
+
original/I/T-REC-I.363.3-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4584 |
+
original/I/T-REC-I.363.5-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4585 |
+
original/I/T-REC-I.364-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4586 |
+
original/I/T-REC-I.365.2-199511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4587 |
+
original/I/T-REC-I.365.3-199511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4588 |
+
original/I/T-REC-I.366.1-199806-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4589 |
+
original/I/T-REC-I.366.2-200011-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4590 |
+
original/I/T-REC-I.370-199110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4591 |
+
original/I/T-REC-I.371-200403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4592 |
+
original/I/T-REC-I.372-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4593 |
+
original/I/T-REC-I.375.2-199806-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4594 |
+
original/I/T-REC-I.375.3-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4595 |
+
original/I/T-REC-I.376-199503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4596 |
+
original/I/T-REC-I.377-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4597 |
+
original/I/T-REC-I.378-200212-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4598 |
+
original/I/T-REC-I.381-200103-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4599 |
+
original/I/T-REC-I.411-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4600 |
+
original/I/T-REC-I.413-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4601 |
+
original/I/T-REC-I.414-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4602 |
+
original/I/T-REC-I.430-199511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4603 |
+
original/I/T-REC-I.431-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4604 |
+
original/I/T-REC-I.432.1-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4605 |
+
original/I/T-REC-I.432.2-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4606 |
+
original/I/T-REC-I.432.3-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4607 |
+
original/I/T-REC-I.432.4-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4608 |
+
original/I/T-REC-I.432.5-199706-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4609 |
+
original/I/T-REC-I.480-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4610 |
+
original/I/T-REC-I.510-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4611 |
+
original/I/T-REC-I.511-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4612 |
+
original/I/T-REC-I.515-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4613 |
+
original/I/T-REC-I.520-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4614 |
+
original/I/T-REC-I.525-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4615 |
+
original/I/T-REC-I.530-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4616 |
+
original/I/T-REC-I.555-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4617 |
+
original/I/T-REC-I.570-201801-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4618 |
+
original/I/T-REC-I.571-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4619 |
+
original/I/T-REC-I.572-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4620 |
+
original/I/T-REC-I.580-199511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4621 |
+
original/I/T-REC-I.581-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4622 |
+
original/I/T-REC-I.601-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4623 |
+
original/I/T-REC-I.610-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4624 |
+
original/I/T-REC-I.630-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4625 |
+
original/I/T-REC-I.731-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4626 |
+
original/I/T-REC-I.732-200010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4627 |
+
original/I/T-REC-I.733-200903-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4628 |
+
original/I/T-REC-I.741-199907-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4629 |
+
original/I/T-REC-I.751-199603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4630 |
+
original/I/T-REC-I.761-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4631 |
+
original/I/T-REC-I.762-200003-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4632 |
+
original/I/T-REC-I.Sup1-199803-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4633 |
+
original/J/T-REC-J.154-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4634 |
+
original/J/T-REC-J.162-200712-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4635 |
+
original/J/T-REC-J.222.3-200711-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4636 |
+
original/J/T-REC-J.Sup10-202409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4637 |
+
original/J/T-REC-J.Sup11-202510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4638 |
+
original/J/T-REC-J.Sup12-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4639 |
+
original/J/T-REC-J.Sup13-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4640 |
+
original/J/T-REC-J.Sup14-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4641 |
+
original/J/T-REC-J.Sup2-199811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4642 |
+
original/J/T-REC-J.Sup3-199811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4643 |
+
original/J/T-REC-J.Sup5-199909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4644 |
+
original/J/T-REC-J.Sup6-201609-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4645 |
+
original/J/T-REC-J.Sup7-202104-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4646 |
+
original/J/T-REC-J.Sup8-202104-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4647 |
+
original/J/T-REC-J.Sup9-202004-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4648 |
+
original/K/T-REC-K.160-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4649 |
+
original/K/T-REC-K.Sup1-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4650 |
+
original/K/T-REC-K.Sup10-201711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4651 |
+
original/K/T-REC-K.Sup11-201809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4652 |
+
original/K/T-REC-K.Sup12-201805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4653 |
+
original/K/T-REC-K.Sup13-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4654 |
+
original/K/T-REC-K.Sup14-201909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4655 |
+
original/K/T-REC-K.Sup15-201809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4656 |
+
original/K/T-REC-K.Sup16-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4657 |
+
original/K/T-REC-K.Sup17-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4658 |
+
original/K/T-REC-K.Sup18-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4659 |
+
original/K/T-REC-K.Sup19-201909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4660 |
+
original/K/T-REC-K.Sup20-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4661 |
+
original/K/T-REC-K.Sup21-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4662 |
+
original/K/T-REC-K.Sup22-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4663 |
+
original/K/T-REC-K.Sup23-202010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4664 |
+
original/K/T-REC-K.Sup24-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4665 |
+
original/K/T-REC-K.Sup25-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4666 |
+
original/K/T-REC-K.Sup26-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4667 |
+
original/K/T-REC-K.Sup27-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4668 |
+
original/K/T-REC-K.Sup28-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4669 |
+
original/K/T-REC-K.Sup29-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4670 |
+
original/K/T-REC-K.Sup3-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4671 |
+
original/K/T-REC-K.Sup30-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4672 |
+
original/K/T-REC-K.Sup31-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4673 |
+
original/K/T-REC-K.Sup32-202406-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4674 |
+
original/K/T-REC-K.Sup4-201809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4675 |
+
original/K/T-REC-K.Sup5-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4676 |
+
original/K/T-REC-K.Sup6-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4677 |
+
original/K/T-REC-K.Sup7-201705-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4678 |
+
original/K/T-REC-K.Sup8-201711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4679 |
+
original/K/T-REC-K.Sup9-201905-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4680 |
+
original/L/T-REC-L.102-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4681 |
+
original/L/T-REC-L.105-202511-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4682 |
+
original/L/T-REC-L.107-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4683 |
+
original/L/T-REC-L.110-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4684 |
+
original/L/T-REC-L.1322-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4685 |
+
original/L/T-REC-L.1421-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4686 |
+
original/L/T-REC-L.1480-202507-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4687 |
+
original/L/T-REC-L.1520-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4688 |
+
original/L/T-REC-L.391-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4689 |
+
original/L/T-REC-L.Sup1-201302-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4690 |
+
original/L/T-REC-L.Sup10-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4691 |
+
original/L/T-REC-L.Sup11-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4692 |
+
original/L/T-REC-L.Sup12-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4693 |
+
original/L/T-REC-L.Sup13-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4694 |
+
original/L/T-REC-L.Sup14-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4695 |
+
original/L/T-REC-L.Sup15-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4696 |
+
original/L/T-REC-L.Sup2-201312-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4697 |
+
original/L/T-REC-L.Sup20-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4698 |
+
original/L/T-REC-L.Sup21-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4699 |
+
original/L/T-REC-L.Sup22-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4700 |
+
original/L/T-REC-L.Sup23-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4701 |
+
original/L/T-REC-L.Sup24-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4702 |
+
original/L/T-REC-L.Sup25-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4703 |
+
original/L/T-REC-L.Sup26-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4704 |
+
original/L/T-REC-L.Sup27-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4705 |
+
original/L/T-REC-L.Sup28-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4706 |
+
original/L/T-REC-L.Sup29-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4707 |
+
original/L/T-REC-L.Sup3-201312-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4708 |
+
original/L/T-REC-L.Sup30-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4709 |
+
original/L/T-REC-L.Sup31-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4710 |
+
original/L/T-REC-L.Sup32-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4711 |
+
original/L/T-REC-L.Sup33-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4712 |
+
original/L/T-REC-L.Sup34-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4713 |
+
original/L/T-REC-L.Sup35-201706-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4714 |
+
original/L/T-REC-L.Sup36-201711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4715 |
+
original/L/T-REC-L.Sup37-202005-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4716 |
+
original/L/T-REC-L.Sup38-202010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4717 |
+
original/L/T-REC-L.Sup39-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4718 |
+
original/L/T-REC-L.Sup4-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4719 |
+
original/L/T-REC-L.Sup41-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4720 |
+
original/L/T-REC-L.Sup42-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4721 |
+
original/L/T-REC-L.Sup43-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4722 |
+
original/L/T-REC-L.Sup44-202406-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4723 |
+
original/L/T-REC-L.Sup45-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4724 |
+
original/L/T-REC-L.Sup46-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4725 |
+
original/L/T-REC-L.Sup47-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4726 |
+
original/L/T-REC-L.Sup48-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4727 |
+
original/L/T-REC-L.Sup49-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4728 |
+
original/L/T-REC-L.Sup5-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4729 |
+
original/L/T-REC-L.Sup50-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4730 |
+
original/L/T-REC-L.Sup51-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4731 |
+
original/L/T-REC-L.Sup52-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4732 |
+
original/L/T-REC-L.Sup53-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4733 |
+
original/L/T-REC-L.Sup54-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4734 |
+
original/L/T-REC-L.Sup55-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4735 |
+
original/L/T-REC-L.Sup56-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4736 |
+
original/L/T-REC-L.Sup57-202306-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4737 |
+
original/L/T-REC-L.Sup58-202312-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4738 |
+
original/L/T-REC-L.Sup59-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4739 |
+
original/L/T-REC-L.Sup6-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4740 |
+
original/L/T-REC-L.Sup60-202406-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4741 |
+
original/L/T-REC-L.Sup61-202506-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4742 |
+
original/L/T-REC-L.Sup7-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4743 |
+
original/L/T-REC-L.Sup8-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4744 |
+
original/L/T-REC-L.Sup9-201412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4745 |
+
original/M/T-REC-M.3020-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4746 |
+
original/M/T-REC-M.3050-200405-I!Sup3!PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4747 |
+
original/M/T-REC-M.3050-200702-I!Sup1!PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4748 |
+
original/M/T-REC-M.3050-200702-I!Sup2!PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4749 |
+
original/M/T-REC-M.3050-200702-I!Sup4!PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4750 |
+
original/M/T-REC-M.3163-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4751 |
+
original/M/T-REC-M.3375-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4752 |
+
original/M/T-REC-M.Sup7-200805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4753 |
+
original/N/T-REC-N.1-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4754 |
+
original/N/T-REC-N.21-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4755 |
+
original/N/T-REC-N.51-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4756 |
+
original/N/T-REC-N.60-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4757 |
+
original/N/T-REC-N.67-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4758 |
+
original/N/T-REC-N.73-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4759 |
+
original/O/T-REC-O.1-200002-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4760 |
+
original/O/T-REC-O.111-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4761 |
+
original/O/T-REC-O.131-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4762 |
+
original/O/T-REC-O.133-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4763 |
+
original/O/T-REC-O.150-199605-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4764 |
+
original/O/T-REC-O.171-199704-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4765 |
+
original/O/T-REC-O.172-200504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4766 |
+
original/O/T-REC-O.173-201202-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4767 |
+
original/O/T-REC-O.174-200911-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4768 |
+
original/O/T-REC-O.175-201210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4769 |
+
original/O/T-REC-O.181-200205-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4770 |
+
original/O/T-REC-O.182-200707-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4771 |
+
original/O/T-REC-O.191-200002-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4772 |
+
original/O/T-REC-O.201-200307-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4773 |
+
original/O/T-REC-O.211-200601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4774 |
+
original/O/T-REC-O.22-199210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4775 |
+
original/O/T-REC-O.220-200703-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4776 |
+
original/O/T-REC-O.3-199210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4777 |
+
original/O/T-REC-O.33-199507-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4778 |
+
original/O/T-REC-O.41-199410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4779 |
+
original/O/T-REC-O.81-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4780 |
+
original/O/T-REC-O.82-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4781 |
+
original/O/T-REC-O.9-199903-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4782 |
+
original/P/T-REC-P.Sup10-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4783 |
+
original/P/T-REC-P.Sup20-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4784 |
+
original/P/T-REC-P.Sup24-200510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4785 |
+
original/P/T-REC-P.Sup25-201101-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4786 |
+
original/P/T-REC-P.Sup26-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4787 |
+
original/P/T-REC-P.Sup27-201701-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4788 |
+
original/P/T-REC-P.Sup28-202009-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4789 |
+
original/P/T-REC-P.Sup29-202301-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4790 |
+
original/P/T-REC-P.Sup30-202309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4791 |
+
original/P/T-REC-P.Sup31-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4792 |
+
original/Q/T-REC-Q.3065-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4793 |
+
original/Q/T-REC-Q.3066-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4794 |
+
original/Q/T-REC-Q.3723-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4795 |
+
original/Q/T-REC-Q.3921-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4796 |
+
original/Q/T-REC-Q.4048-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4797 |
+
original/Q/T-REC-Q.4082-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4798 |
+
original/Q/T-REC-Q.4145-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4799 |
+
original/Q/T-REC-Q.4180-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4800 |
+
original/Q/T-REC-Q.5015-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4801 |
+
original/Q/T-REC-Q.5016-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4802 |
+
original/Q/T-REC-Q.5036-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4803 |
+
original/Q/T-REC-Q.5038-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4804 |
+
original/Q/T-REC-Q.5055-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4805 |
+
original/Q/T-REC-Q.Sup1-199510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4806 |
+
original/Q/T-REC-Q.Sup10-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4807 |
+
original/Q/T-REC-Q.Sup11-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4808 |
+
original/Q/T-REC-Q.Sup12-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4809 |
+
original/Q/T-REC-Q.Sup13-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4810 |
+
original/Q/T-REC-Q.Sup14-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4811 |
+
original/Q/T-REC-Q.Sup15-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4812 |
+
original/Q/T-REC-Q.Sup16-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4813 |
+
original/Q/T-REC-Q.Sup17-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4814 |
+
original/Q/T-REC-Q.Sup18-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4815 |
+
original/Q/T-REC-Q.Sup19-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4816 |
+
original/Q/T-REC-Q.Sup2-199709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4817 |
+
original/Q/T-REC-Q.Sup20-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4818 |
+
original/Q/T-REC-Q.Sup21-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4819 |
+
original/Q/T-REC-Q.Sup22-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4820 |
+
original/Q/T-REC-Q.Sup23-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4821 |
+
original/Q/T-REC-Q.Sup24-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4822 |
+
original/Q/T-REC-Q.Sup25-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4823 |
+
original/Q/T-REC-Q.Sup26-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4824 |
+
original/Q/T-REC-Q.Sup27-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4825 |
+
original/Q/T-REC-Q.Sup28-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4826 |
+
original/Q/T-REC-Q.Sup29-199912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4827 |
+
original/Q/T-REC-Q.Sup3-199805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4828 |
+
original/Q/T-REC-Q.Sup30-200012-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4829 |
+
original/Q/T-REC-Q.Sup31-200012-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4830 |
+
original/Q/T-REC-Q.Sup32-200211-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4831 |
+
original/Q/T-REC-Q.Sup33-200012-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4832 |
+
original/Q/T-REC-Q.Sup35-200012-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4833 |
+
original/Q/T-REC-Q.Sup37-200607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4834 |
+
original/Q/T-REC-Q.Sup38-200105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4835 |
+
original/Q/T-REC-Q.Sup39-200203-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4836 |
+
original/Q/T-REC-Q.Sup4-199805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4837 |
+
original/Q/T-REC-Q.Sup40-200211-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4838 |
+
original/Q/T-REC-Q.Sup41-200211-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4839 |
+
original/Q/T-REC-Q.Sup42-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4840 |
+
original/Q/T-REC-Q.Sup43-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4841 |
+
original/Q/T-REC-Q.Sup44-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4842 |
+
original/Q/T-REC-Q.Sup45-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4843 |
+
original/Q/T-REC-Q.Sup46-200309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4844 |
+
original/Q/T-REC-Q.Sup47-200311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4845 |
+
original/Q/T-REC-Q.Sup48-200403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4846 |
+
original/Q/T-REC-Q.Sup49-201402-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4847 |
+
original/Q/T-REC-Q.Sup5-199903-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4848 |
+
original/Q/T-REC-Q.Sup50-200403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4849 |
+
original/Q/T-REC-Q.Sup51-200412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4850 |
+
original/Q/T-REC-Q.Sup52-200412-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4851 |
+
original/Q/T-REC-Q.Sup53-200509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4852 |
+
original/Q/T-REC-Q.Sup54-200704-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4853 |
+
original/Q/T-REC-Q.Sup55-200704-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4854 |
+
original/Q/T-REC-Q.Sup56-200704-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4855 |
+
original/Q/T-REC-Q.Sup57-200801-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4856 |
+
original/Q/T-REC-Q.Sup58-200801-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4857 |
+
original/Q/T-REC-Q.Sup59-200801-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4858 |
+
original/Q/T-REC-Q.Sup60-201001-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4859 |
+
original/Q/T-REC-Q.Sup61-201004-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4860 |
+
original/Q/T-REC-Q.Sup62-201402-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4861 |
+
original/Q/T-REC-Q.Sup63-201306-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4862 |
+
original/Q/T-REC-Q.Sup64-201402-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4863 |
+
original/Q/T-REC-Q.Sup65-201407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4864 |
+
original/Q/T-REC-Q.Sup66-201407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4865 |
+
original/Q/T-REC-Q.Sup67-201504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4866 |
+
original/Q/T-REC-Q.Sup68-201512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4867 |
+
original/Q/T-REC-Q.Sup69-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4868 |
+
original/Q/T-REC-Q.Sup7-199903-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4869 |
+
original/Q/T-REC-Q.Sup70-201906-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4870 |
+
original/Q/T-REC-Q.Sup71-201910-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4871 |
+
original/Q/T-REC-Q.Sup72-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4872 |
+
original/Q/T-REC-Q.Sup73-202103-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4873 |
+
original/Q/T-REC-Q.Sup74-202103-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4874 |
+
original/Q/T-REC-Q.Sup75-202112-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4875 |
+
original/Q/T-REC-Q.Sup76-202310-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4876 |
+
original/Q/T-REC-Q.Sup77-202402-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4877 |
+
original/Q/T-REC-Q.Sup78-202502-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4878 |
+
original/Q/T-REC-Q.Sup79-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4879 |
+
original/Q/T-REC-Q.Sup8-199903-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4880 |
+
original/Q/T-REC-Q.Sup80-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4881 |
+
original/Q/T-REC-Q.Sup81-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4882 |
+
original/Q/T-REC-Q.Sup82-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4883 |
+
original/Q/T-REC-Q.Sup9-200403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4884 |
+
original/R/T-REC-R.101-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4885 |
+
original/R/T-REC-R.102-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4886 |
+
original/R/T-REC-R.111-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4887 |
+
original/R/T-REC-R.115-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4888 |
+
original/R/T-REC-R.122-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4889 |
+
original/R/T-REC-R.140-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4890 |
+
original/R/T-REC-R.21-199608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4891 |
+
original/R/T-REC-R.79-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4892 |
+
original/S/T-REC-S.13-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4893 |
+
original/S/T-REC-S.16-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4894 |
+
original/S/T-REC-S.18-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4895 |
+
original/S/T-REC-S.Sup1-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4896 |
+
original/T/T-REC-T.800-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4897 |
+
original/T/T-REC-T.801-202308-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4898 |
+
original/T/T-REC-T.802-200501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4899 |
+
original/T/T-REC-T.81-199209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4900 |
+
original/T/T-REC-T.815-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4901 |
+
original/T/T-REC-T.840.1-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4902 |
+
original/T/T-REC-T.840.2-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4903 |
+
original/T/T-REC-T.840.3-202601-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4904 |
+
original/T/T-REC-T.840.5-202601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4905 |
+
original/T/T-REC-T.Sup1-200411-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4906 |
+
original/T/T-REC-T.Sup2-201103-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4907 |
+
original/U/T-REC-U.1-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4908 |
+
original/U/T-REC-U.101-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4909 |
+
original/U/T-REC-U.11-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4910 |
+
original/U/T-REC-U.12-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4911 |
+
original/U/T-REC-U.20-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4912 |
+
original/U/T-REC-U.200-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4913 |
+
original/U/T-REC-U.201-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4914 |
+
original/U/T-REC-U.202-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4915 |
+
original/U/T-REC-U.203-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4916 |
+
original/U/T-REC-U.204-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4917 |
+
original/U/T-REC-U.208-199610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4918 |
+
original/U/T-REC-U.61-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4919 |
+
original/U/T-REC-U.80-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4920 |
+
original/X/T-REC-X.1058-202602-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4921 |
+
original/X/T-REC-X.1060-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4922 |
+
original/X/T-REC-X.1062-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4923 |
+
original/X/T-REC-X.1097-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4924 |
+
original/X/T-REC-X.1238-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4925 |
+
original/X/T-REC-X.1250-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4926 |
+
original/X/T-REC-X.1400-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4927 |
+
original/X/T-REC-X.1457-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4928 |
+
original/X/T-REC-X.1631-202512-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4929 |
+
original/X/T-REC-X.1711-202603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4930 |
+
original/X/T-REC-X.1718-202603-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4931 |
+
original/X/T-REC-X.1901-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4932 |
+
original/X/T-REC-X.508-202410-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4933 |
+
original/X/T-REC-X.510-202310-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4934 |
+
original/X/T-REC-X.603.2-201010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4935 |
+
original/X/T-REC-X.604.2-201010-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4936 |
+
original/X/T-REC-X.Sup10-201401-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4937 |
+
original/X/T-REC-X.Sup11-201109-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4938 |
+
original/X/T-REC-X.Sup12-201203-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4939 |
+
original/X/T-REC-X.Sup13-201809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4940 |
+
original/X/T-REC-X.Sup14-201209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4941 |
+
original/X/T-REC-X.Sup15-201209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4942 |
+
original/X/T-REC-X.Sup16-201209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4943 |
+
original/X/T-REC-X.Sup17-201209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4944 |
+
original/X/T-REC-X.Sup18-201304-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4945 |
+
original/X/T-REC-X.Sup19-201304-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4946 |
+
original/X/T-REC-X.Sup2-200709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4947 |
+
original/X/T-REC-X.Sup20-201304-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4948 |
+
original/X/T-REC-X.Sup21-201401-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4949 |
+
original/X/T-REC-X.Sup22-201401-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4950 |
+
original/X/T-REC-X.Sup23-201409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4951 |
+
original/X/T-REC-X.Sup24-201409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4952 |
+
original/X/T-REC-X.Sup25-201603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4953 |
+
original/X/T-REC-X.Sup26-201603-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4954 |
+
original/X/T-REC-X.Sup27-201609-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4955 |
+
original/X/T-REC-X.Sup28-201609-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4956 |
+
original/X/T-REC-X.Sup29-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4957 |
+
original/X/T-REC-X.Sup3-200804-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4958 |
+
original/X/T-REC-X.Sup30-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4959 |
+
original/X/T-REC-X.Sup31-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4960 |
+
original/X/T-REC-X.Sup32-201803-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4961 |
+
original/X/T-REC-X.Sup33-201809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4962 |
+
original/X/T-REC-X.Sup34-201901-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4963 |
+
original/X/T-REC-X.Sup35-201909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4964 |
+
original/X/T-REC-X.Sup36-202109-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4965 |
+
original/X/T-REC-X.Sup37-202209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4966 |
+
original/X/T-REC-X.Sup38-202209-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4967 |
+
original/X/T-REC-X.Sup39-202309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4968 |
+
original/X/T-REC-X.Sup4-200809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4969 |
+
original/X/T-REC-X.Sup40-202403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4970 |
+
original/X/T-REC-X.Sup41-202409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4971 |
+
original/X/T-REC-X.Sup42-202409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4972 |
+
original/X/T-REC-X.Sup43-202409-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4973 |
+
original/X/T-REC-X.Sup45-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4974 |
+
original/X/T-REC-X.Sup5-200809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4975 |
+
original/X/T-REC-X.Sup6-200909-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4976 |
+
original/X/T-REC-X.Sup8-201012-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4977 |
+
original/X/T-REC-X.Sup9-201109-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4978 |
+
original/Y/T-REC-Y.2352-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4979 |
+
original/Y/T-REC-Y.2504-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4980 |
+
original/Y/T-REC-Y.3190-202512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4981 |
+
original/Y/T-REC-Y.3193-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4982 |
+
original/Y/T-REC-Y.3228-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4983 |
+
original/Y/T-REC-Y.3229-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4984 |
+
original/Y/T-REC-Y.3230-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4985 |
+
original/Y/T-REC-Y.3328-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4986 |
+
original/Y/T-REC-Y.3329-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4987 |
+
original/Y/T-REC-Y.3441-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4988 |
+
original/Y/T-REC-Y.3510-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4989 |
+
original/Y/T-REC-Y.3534-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4990 |
+
original/Y/T-REC-Y.3541-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4991 |
+
original/Y/T-REC-Y.3558-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4992 |
+
original/Y/T-REC-Y.3559-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4993 |
+
original/Y/T-REC-Y.3560-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4994 |
+
original/Y/T-REC-Y.3662-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4995 |
+
original/Y/T-REC-Y.3682-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4996 |
+
original/Y/T-REC-Y.3823-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4997 |
+
original/Y/T-REC-Y.3835-202604-P_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4998 |
+
original/Y/T-REC-Y.Sup1-200607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 4999 |
+
original/Y/T-REC-Y.Sup10-201001-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5000 |
+
original/Y/T-REC-Y.Sup100-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5001 |
+
original/Y/T-REC-Y.Sup101-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5002 |
+
original/Y/T-REC-Y.Sup11-201001-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5003 |
+
original/Y/T-REC-Y.Sup12-201004-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5004 |
+
original/Y/T-REC-Y.Sup13-201101-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5005 |
+
original/Y/T-REC-Y.Sup14-201101-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5006 |
+
original/Y/T-REC-Y.Sup15-201110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5007 |
+
original/Y/T-REC-Y.Sup16-201202-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5008 |
+
original/Y/T-REC-Y.Sup17-201202-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5009 |
+
original/Y/T-REC-Y.Sup18-201206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5010 |
+
original/Y/T-REC-Y.Sup19-201206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5011 |
+
original/Y/T-REC-Y.Sup2-200607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5012 |
+
original/Y/T-REC-Y.Sup20-201206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5013 |
+
original/Y/T-REC-Y.Sup21-201303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5014 |
+
original/Y/T-REC-Y.Sup22-201306-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5015 |
+
original/Y/T-REC-Y.Sup23-201311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5016 |
+
original/Y/T-REC-Y.Sup24-201311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5017 |
+
original/Y/T-REC-Y.Sup25-201505-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5018 |
+
original/Y/T-REC-Y.Sup26-201512-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5019 |
+
original/Y/T-REC-Y.Sup27-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5020 |
+
original/Y/T-REC-Y.Sup28-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5021 |
+
original/Y/T-REC-Y.Sup29-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5022 |
+
original/Y/T-REC-Y.Sup3-200801-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5023 |
+
original/Y/T-REC-Y.Sup30-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5024 |
+
original/Y/T-REC-Y.Sup31-201601-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5025 |
+
original/Y/T-REC-Y.Sup32-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5026 |
+
original/Y/T-REC-Y.Sup33-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5027 |
+
original/Y/T-REC-Y.Sup34-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5028 |
+
original/Y/T-REC-Y.Sup35-201605-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5029 |
+
original/Y/T-REC-Y.Sup36-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5030 |
+
original/Y/T-REC-Y.Sup37-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5031 |
+
original/Y/T-REC-Y.Sup38-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5032 |
+
original/Y/T-REC-Y.Sup39-201510-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5033 |
+
original/Y/T-REC-Y.Sup40-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5034 |
+
original/Y/T-REC-Y.Sup41-201607-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5035 |
+
original/Y/T-REC-Y.Sup42-201608-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5036 |
+
original/Y/T-REC-Y.Sup43-201702-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5037 |
+
original/Y/T-REC-Y.Sup44-201707-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5038 |
+
original/Y/T-REC-Y.Sup45-201709-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5039 |
+
original/Y/T-REC-Y.Sup46-201711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5040 |
+
original/Y/T-REC-Y.Sup47-201804-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5041 |
+
original/Y/T-REC-Y.Sup48-201807-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5042 |
+
original/Y/T-REC-Y.Sup49-201811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5043 |
+
original/Y/T-REC-Y.Sup5-200805-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5044 |
+
original/Y/T-REC-Y.Sup50-201811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5045 |
+
original/Y/T-REC-Y.Sup51-201811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5046 |
+
original/Y/T-REC-Y.Sup52-201812-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5047 |
+
original/Y/T-REC-Y.Sup53-201812-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5048 |
+
original/Y/T-REC-Y.Sup54-201904-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5049 |
+
original/Y/T-REC-Y.Sup55-201910-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5050 |
+
original/Y/T-REC-Y.Sup56-201912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5051 |
+
original/Y/T-REC-Y.Sup57-201912-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5052 |
+
original/Y/T-REC-Y.Sup58-202509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5053 |
+
original/Y/T-REC-Y.Sup59-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5054 |
+
original/Y/T-REC-Y.Sup6-200809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5055 |
+
original/Y/T-REC-Y.Sup60-202206-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5056 |
+
original/Y/T-REC-Y.Sup61-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5057 |
+
original/Y/T-REC-Y.Sup62-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5058 |
+
original/Y/T-REC-Y.Sup63-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5059 |
+
original/Y/T-REC-Y.Sup64-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5060 |
+
original/Y/T-REC-Y.Sup65-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5061 |
+
original/Y/T-REC-Y.Sup66-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5062 |
+
original/Y/T-REC-Y.Sup67-202007-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5063 |
+
original/Y/T-REC-Y.Sup68-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5064 |
+
original/Y/T-REC-Y.Sup69-202105-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5065 |
+
original/Y/T-REC-Y.Sup7-200809-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5066 |
+
original/Y/T-REC-Y.Sup70-202107-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5067 |
+
original/Y/T-REC-Y.Sup71-202207-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5068 |
+
original/Y/T-REC-Y.Sup72-202211-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5069 |
+
original/Y/T-REC-Y.Sup73-202302-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5070 |
+
original/Y/T-REC-Y.Sup74-202303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5071 |
+
original/Y/T-REC-Y.Sup75-202303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5072 |
+
original/Y/T-REC-Y.Sup76-202309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5073 |
+
original/Y/T-REC-Y.Sup77-202309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5074 |
+
original/Y/T-REC-Y.Sup78-202309-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5075 |
+
original/Y/T-REC-Y.Sup79-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5076 |
+
original/Y/T-REC-Y.Sup8-201001-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5077 |
+
original/Y/T-REC-Y.Sup80-202311-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5078 |
+
original/Y/T-REC-Y.Sup81-202403-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5079 |
+
original/Y/T-REC-Y.Sup82-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5080 |
+
original/Y/T-REC-Y.Sup83-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5081 |
+
original/Y/T-REC-Y.Sup84-202407-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5082 |
+
original/Y/T-REC-Y.Sup85-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5083 |
+
original/Y/T-REC-Y.Sup86-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5084 |
+
original/Y/T-REC-Y.Sup87-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5085 |
+
original/Y/T-REC-Y.Sup88-202501-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5086 |
+
original/Y/T-REC-Y.Sup89-202503-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5087 |
+
original/Y/T-REC-Y.Sup9-201001-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5088 |
+
original/Y/T-REC-Y.Sup90-202507-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5089 |
+
original/Y/T-REC-Y.Sup91-202507-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5090 |
+
original/Y/T-REC-Y.Sup92-202509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5091 |
+
original/Y/T-REC-Y.Sup93-202509-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5092 |
+
original/Y/T-REC-Y.Sup94-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5093 |
+
original/Y/T-REC-Y.Sup95-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5094 |
+
original/Y/T-REC-Y.Sup96-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5095 |
+
original/Y/T-REC-Y.Sup97-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5096 |
+
original/Y/T-REC-Y.Sup98-202511-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5097 |
+
original/Y/T-REC-Y.Sup99-202602-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5098 |
+
original/Z/T-REC-Z.100-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5099 |
+
original/Z/T-REC-Z.101-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5100 |
+
original/Z/T-REC-Z.102-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5101 |
+
original/Z/T-REC-Z.103-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5102 |
+
original/Z/T-REC-Z.104-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5103 |
+
original/Z/T-REC-Z.105-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5104 |
+
original/Z/T-REC-Z.106-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5105 |
+
original/Z/T-REC-Z.107-202106-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5106 |
+
original/Z/T-REC-Z.109-201610-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5107 |
+
original/Z/T-REC-Z.111-201604-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5108 |
+
original/Z/T-REC-Z.119-200702-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5109 |
+
original/Z/T-REC-Z.120-201102-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5110 |
+
original/Z/T-REC-Z.121-200302-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5111 |
+
original/Z/T-REC-Z.150-201102-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5112 |
+
original/Z/T-REC-Z.151-201810-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5113 |
+
original/Z/T-REC-Z.161-202310-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5114 |
+
original/Z/T-REC-Z.161.1-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5115 |
+
original/Z/T-REC-Z.161.2-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5116 |
+
original/Z/T-REC-Z.161.3-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5117 |
+
original/Z/T-REC-Z.161.4-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5118 |
+
original/Z/T-REC-Z.161.5-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5119 |
+
original/Z/T-REC-Z.161.6-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5120 |
+
original/Z/T-REC-Z.161.7-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5121 |
+
original/Z/T-REC-Z.162-200711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5122 |
+
original/Z/T-REC-Z.163-200711-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5123 |
+
original/Z/T-REC-Z.164-201710-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5124 |
+
original/Z/T-REC-Z.165-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5125 |
+
original/Z/T-REC-Z.165.1-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5126 |
+
original/Z/T-REC-Z.166-202310-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5127 |
+
original/Z/T-REC-Z.167-202210-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5128 |
+
original/Z/T-REC-Z.168-202110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5129 |
+
original/Z/T-REC-Z.169-202110-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5130 |
+
original/Z/T-REC-Z.170-201710-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5131 |
+
original/Z/T-REC-Z.171-202310-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5132 |
+
original/Z/T-REC-Z.200-199911-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5133 |
+
original/Z/T-REC-Z.314-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5134 |
+
original/Z/T-REC-Z.315-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5135 |
+
original/Z/T-REC-Z.316-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5136 |
+
original/Z/T-REC-Z.317-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5137 |
+
original/Z/T-REC-Z.332-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5138 |
+
original/Z/T-REC-Z.333-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5139 |
+
original/Z/T-REC-Z.334-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5140 |
+
original/Z/T-REC-Z.335-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5141 |
+
original/Z/T-REC-Z.336-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5142 |
+
original/Z/T-REC-Z.337-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5143 |
+
original/Z/T-REC-Z.341-198811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5144 |
+
original/Z/T-REC-Z.352-199303-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5145 |
+
original/Z/T-REC-Z.360-199705-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5146 |
+
original/Z/T-REC-Z.361-199902-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5147 |
+
original/Z/T-REC-Z.371-200504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5148 |
+
original/Z/T-REC-Z.372-200504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5149 |
+
original/Z/T-REC-Z.450-200811-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5150 |
+
original/Z/T-REC-Z.500-199705-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
| 5151 |
+
original/Z/T-REC-Z.Sup1-201504-I_PDF-E.pdf filter=lfs diff=lfs merge=lfs -text
|
STATUS.md
CHANGED
|
@@ -2,6 +2,6 @@
|
|
| 2 |
|
| 3 |
State: complete mirror
|
| 4 |
|
| 5 |
-
- Original files:
|
| 6 |
-
- Marked documents:
|
| 7 |
- Missing marked documents: 0
|
|
|
|
| 2 |
|
| 3 |
State: complete mirror
|
| 4 |
|
| 5 |
+
- Original files: 6,105
|
| 6 |
+
- Marked documents: 6,105
|
| 7 |
- Missing marked documents: 0
|
manifest.jsonl
CHANGED
|
The diff for this file is too large to render.
See raw diff
|
|
|
marked/A/T-REC-A.1-201909-I_PDF-E/2efe0a28a1013bcb779bd16fb83b2bde_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.1-201909-I_PDF-E/9c85bca234696b6b31056e12bd8def01_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.1-201909-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,664 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
# A.1
|
| 12 |
+
|
| 13 |
+
(09/2019)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
---
|
| 18 |
+
|
| 19 |
+
# **Working methods for study groups of the ITU Telecommunication Standardization Sector**
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T A.1
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
# Recommendation ITU-T A.1
|
| 26 |
+
|
| 27 |
+
# Working methods for study groups of the ITU Telecommunication Standardization Sector
|
| 28 |
+
|
| 29 |
+
## Summary
|
| 30 |
+
|
| 31 |
+
Recommendation ITU-T A.1 describes general work methods for ITU-T study groups. It provides guidelines related to work methods, such as the conduct of meetings, preparation of studies, management of study groups, joint coordination groups, the role of rapporteurs and the processing of ITU-T contributions and TDs.
|
| 32 |
+
|
| 33 |
+
## History
|
| 34 |
+
|
| 35 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID* |
|
| 36 |
+
|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
|
| 37 |
+
| 1.0 | ITU-T A.1 | 1996-10-18 | TSAG | <a href="http://handle.itu.int/11.1002/1000/3963">11.1002/1000/3963</a> |
|
| 38 |
+
| 2.0 | ITU-T A.1 | 2000-10-06 | TSAG | <a href="http://handle.itu.int/11.1002/1000/5194">11.1002/1000/5194</a> |
|
| 39 |
+
| 3.0 | ITU-T A.1 | 2004-10-14 | TSAG | <a href="http://handle.itu.int/11.1002/1000/7417">11.1002/1000/7417</a> |
|
| 40 |
+
| 4.0 | ITU-T A.1 | 2006-07-07 | TSAG | <a href="http://handle.itu.int/11.1002/1000/8789">11.1002/1000/8789</a> |
|
| 41 |
+
| 5.0 | ITU-T A.1 | 2008-10-30 | TSAG | <a href="http://handle.itu.int/11.1002/1000/9638">11.1002/1000/9638</a> |
|
| 42 |
+
| 6.0 | ITU-T A.1 | 2012-11-29 | TSAG | <a href="http://handle.itu.int/11.1002/1000/11920">11.1002/1000/11920</a> |
|
| 43 |
+
| 7.0 | ITU-T A.1 | 2016-10-28 | TSAG | <a href="http://handle.itu.int/11.1002/1000/13163">11.1002/1000/13163</a> |
|
| 44 |
+
| 8.0 | ITU-T A.1 | 2019-09-27 | TSAG | <a href="http://handle.itu.int/11.1002/1000/13851">11.1002/1000/13851</a> |
|
| 45 |
+
|
| 46 |
+
## Keywords
|
| 47 |
+
|
| 48 |
+
Contributions, joint coordination, rapporteur, study group management, TD, working methods.
|
| 49 |
+
|
| 50 |
+
---
|
| 51 |
+
|
| 52 |
+
\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
|
| 53 |
+
|
| 54 |
+
## FOREWORD
|
| 55 |
+
|
| 56 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 57 |
+
|
| 58 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 59 |
+
|
| 60 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 61 |
+
|
| 62 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 63 |
+
|
| 64 |
+
## NOTE
|
| 65 |
+
|
| 66 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 67 |
+
|
| 68 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 69 |
+
|
| 70 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 71 |
+
|
| 72 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 73 |
+
|
| 74 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 75 |
+
|
| 76 |
+
© ITU 2019
|
| 77 |
+
|
| 78 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 79 |
+
|
| 80 |
+
## Table of Contents
|
| 81 |
+
|
| 82 |
+
| | <b>Page</b> |
|
| 83 |
+
|-----------------------------------------------------------------------------------------------------------------|-------------|
|
| 84 |
+
| 1 Study groups and their relevant groups ..... | 1 |
|
| 85 |
+
| 1.1 Frequency of meetings ..... | 1 |
|
| 86 |
+
| 1.2 Coordination of work ..... | 1 |
|
| 87 |
+
| 1.3 Preparation of studies and meetings ..... | 1 |
|
| 88 |
+
| 1.4 Conduct of meetings ..... | 2 |
|
| 89 |
+
| 1.5 Liaison statements ..... | 3 |
|
| 90 |
+
| 1.6 Correspondence activities ..... | 4 |
|
| 91 |
+
| 1.7 Preparation of reports of study groups, working parties or joint working parties, and Recommendations ..... | 4 |
|
| 92 |
+
| 1.8 Definitions ..... | 5 |
|
| 93 |
+
| 1.9 References ..... | 6 |
|
| 94 |
+
| 2 Study group management ..... | 7 |
|
| 95 |
+
| 2.1 Study group structure and distribution of work ..... | 7 |
|
| 96 |
+
| 2.2 Joint coordination activities ..... | 7 |
|
| 97 |
+
| 2.3 The roles of rapporteurs ..... | 7 |
|
| 98 |
+
| 3 Submission and processing of contributions ..... | 10 |
|
| 99 |
+
| 3.1 Submission of contributions ..... | 10 |
|
| 100 |
+
| 3.2 Processing of contributions ..... | 11 |
|
| 101 |
+
| 3.3 TDs ..... | 12 |
|
| 102 |
+
| 3.4 Electronic access ..... | 12 |
|
| 103 |
+
| 3.5 Other document types ..... | 12 |
|
| 104 |
+
| 4 Other ITU-T groups ..... | 12 |
|
| 105 |
+
| 4.1 Overview ..... | 12 |
|
| 106 |
+
| 4.2 Focus group (FG) ..... | 12 |
|
| 107 |
+
| 4.3 Intersector Rapporteur Group (IRG) ..... | 13 |
|
| 108 |
+
| 4.4 Joint Coordination Activity (JCA) ..... | 13 |
|
| 109 |
+
| 4.5 Regional Group (RG) ..... | 13 |
|
| 110 |
+
| 4.6 ITU-T group types for collaborating with other SDOs ..... | 13 |
|
| 111 |
+
| 4.7 Additional ITU-T groups ..... | 13 |
|
| 112 |
+
| 5 Joint coordination activities ..... | 13 |
|
| 113 |
+
| Annex A – Template to describe a proposed new Recommendation in the work programme ..... | 17 |
|
| 114 |
+
| Appendix I – Rapporteur progress report format ..... | 18 |
|
| 115 |
+
| Bibliography ..... | 19 |
|
| 116 |
+
|
| 117 |
+
|
| 118 |
+
|
| 119 |
+
# **Recommendation ITU-T A.1**
|
| 120 |
+
|
| 121 |
+
# **Working methods for study groups of the ITU Telecommunication Standardization Sector**
|
| 122 |
+
|
| 123 |
+
## **1 Study groups and their relevant groups**
|
| 124 |
+
|
| 125 |
+
### **1.1 Frequency of meetings**
|
| 126 |
+
|
| 127 |
+
**1.1.1** Study groups meet to facilitate the approval of Recommendations. Such meetings shall only be held with the approval of the Director of the Telecommunication Standardization Bureau (TSB), and with due consideration of the physical and budgetary capabilities of the ITU Telecommunication Standardization Sector (ITU-T). To minimize the number of meetings required, every effort should be made to resolve questions by correspondence (No. 245 of the ITU Convention).
|
| 128 |
+
|
| 129 |
+
**1.1.2** In the establishment of the work programme, the timetable of meetings must take into account the time required for participating bodies (administrations of Member States and other duly authorized entities) to react and prepare contributions. Meetings should not be held more frequently than is necessary to make effective progress and should take into account TSB's capabilities to provide the necessary documentation.
|
| 130 |
+
|
| 131 |
+
**1.1.3** Meetings of study groups having common interests or dealing with problems possessing affinities should, if possible, be arranged so as to enable participating bodies to send one delegate or representative to cover several meetings. As far as possible, the arrangement chosen should enable the study groups meeting during the period to exchange any information they may require without delay. Furthermore, it should enable specialists from all over the world in the same or related subjects to have direct contacts with each other of benefit to their organizations. It should likewise enable the specialists concerned to avoid leaving their home countries too often.
|
| 132 |
+
|
| 133 |
+
**1.1.4** The timetable of meetings shall be prepared and communicated to participating bodies well in advance (one year), to give them time to study problems and submit contributions within the prescribed time-limits and to give TSB time to distribute the contributions. In this way, study group chairmen and delegates will be given the opportunity to consider the contributions in advance, thus helping to make meetings more efficient and reduce their length. A study group chairman, in conjunction with the Director, may schedule short additional study group or working party meetings for the purpose of making the consent, determination or decision, as appropriate, on a draft new or revised Recommendation.
|
| 134 |
+
|
| 135 |
+
**1.1.5** Subject to physical and budgetary limitations and in consultation with the Director, the work of the study groups should be on a continuous basis and dissociated from the interval between world telecommunication standardization assemblies (WTSA).
|
| 136 |
+
|
| 137 |
+
### **1.2 Coordination of work**
|
| 138 |
+
|
| 139 |
+
**1.2.1** A joint coordination activity (JCA) may be formed to coordinate work relating to more than one study group. Its primary role is to harmonize planned work effort in terms of subject matter, time-frames for meetings and publication goals (see clause 5).
|
| 140 |
+
|
| 141 |
+
### **1.3 Preparation of studies and meetings**
|
| 142 |
+
|
| 143 |
+
**1.3.1** At the beginning of each study period, an organization proposal and an action plan for the study period shall be prepared by each study group chairman with the help of TSB. The plan should take into account any priorities and coordination arrangements recommended by the Telecommunication Standardization Advisory Group (TSAG) or decided by WTSA.
|
| 144 |
+
|
| 145 |
+
How the proposed action plan is implemented will depend upon the contributions received from the members of ITU-T and the views expressed by participants in the meetings.
|
| 146 |
+
|
| 147 |
+
**1.3.2** A collective letter with an agenda of the meeting, a draft work plan and a listing of the Questions or proposals under the general areas of responsibility to be examined shall be prepared by TSB with the help of the chairman.
|
| 148 |
+
|
| 149 |
+
The work plan should state which items are to be studied on each day, but it must be regarded as subject to change in the light of the rate at which work proceeds. Chairmen should try to follow it as far as possible.
|
| 150 |
+
|
| 151 |
+
This collective letter should be received by bodies participating in the activities of particular ITU-T study groups, as far as practicable, two months before the beginning of the meeting. The collective letter shall include registration information for these bodies to indicate participation in the meeting. Each Member State administration, Sector Member, Associate, Academia member and regional or international organization should send to TSB a list of its participants at least one month before the start of the meeting. In the event that names cannot be provided, the expected number of participants should be indicated. Such information will facilitate the registration process and the timely preparation of registration materials. Individuals who attend the meeting without pre-registration may experience a delay in receiving their documents.
|
| 152 |
+
|
| 153 |
+
If the meeting in question has not been previously planned and scheduled, a collective letter should be received at least three months before the meeting.
|
| 154 |
+
|
| 155 |
+
**1.3.3** If an insufficient number of contributions or notification of contributions has been submitted, no meeting should be held. The decision whether to cancel a meeting or not shall be taken by the Director, in agreement with the chairman of the study group or working party concerned.
|
| 156 |
+
|
| 157 |
+
### **1.4 Conduct of meetings**
|
| 158 |
+
|
| 159 |
+
**1.4.1** The chairman shall direct the debates during the meeting, with the assistance of TSB.
|
| 160 |
+
|
| 161 |
+
**1.4.2** The chairman is authorized to decide that there shall be no discussion on Questions on which insufficient contributions have been received.
|
| 162 |
+
|
| 163 |
+
**1.4.3** Questions which have not elicited any contributions should not be placed on the final agenda of the meeting, and according to provisions of 7.4.1 of [WTS Res. 1], may be deleted if no contributions have been received for the previous two study group meetings.
|
| 164 |
+
|
| 165 |
+
**1.4.4** Study groups and working parties may set up ad hoc groups (which should be as small as possible and are subject to the normal rules of the study group or working party) during their meetings, to study Questions allocated to those study groups and working parties.
|
| 166 |
+
|
| 167 |
+
**1.4.5** For projects involving more than one study group, baseline documents may be prepared in order to provide the basis for coordinated study among the various study groups. The term "baseline document" refers to a document which contains the elements of common agreement at a given point in time.
|
| 168 |
+
|
| 169 |
+
**1.4.6** Chairmen will ask, during each meeting, whether anyone has knowledge of intellectual property rights issues<sup>1</sup>, including patents, copyright for software or text, marks, the use of which may be required to implement or publish the Recommendation being considered. The fact that the question was asked shall be recorded in the working party or study group meeting report, along with any affirmative responses.
|
| 170 |
+
|
| 171 |
+
**1.4.7** Study groups shall establish and maintain a work programme, which includes target dates for consenting or determining each draft Recommendation. The work programme is available in a
|
| 172 |
+
|
| 173 |
+
---
|
| 174 |
+
|
| 175 |
+
<sup>1</sup> See <https://www.itu.int/ipr>
|
| 176 |
+
|
| 177 |
+
database which is searchable from the study group website. For each work item under development, the database contains the Recommendation number (or provisional mnemonic designation), the title, scope, editor, timing, priority, identification of any liaison relationships, any editor assigned, the location of the most recent text, the approval process and the status for documents in the approval process. The database is updated to reflect progress or completion of work, re-planning of in-progress items, or addition of new work items.
|
| 178 |
+
|
| 179 |
+
The decision to add a new work item to the work programme shall be documented in the report of the meeting using the template in Annex A. Note that this may not be necessary to document the continuation of existing work (e.g., an amendment or revision of an existing Recommendation).
|
| 180 |
+
|
| 181 |
+
A work item may be considered for discontinuation from the work programme if it has not given rise to any contribution in the time interval of the previous two study group meetings.
|
| 182 |
+
|
| 183 |
+
### **1.5 Liaison statements**
|
| 184 |
+
|
| 185 |
+
**1.5.1** The following information shall be included in outgoing liaison statements prepared at study group, working party or rapporteur group meetings. When necessary, between scheduled meetings, the liaison statement may be prepared by an appropriate correspondence process and approved by the study group chairman in consultation with the study group management team.
|
| 186 |
+
|
| 187 |
+
- List the appropriate Question numbers of the originating and destination study groups.
|
| 188 |
+
- Identify the study group, working party or rapporteur group meeting at which the liaison statement was prepared.
|
| 189 |
+
- Include a concise title appropriate to the subject matter. If this is in reply to a liaison statement, make this clear, e.g., "Reply to liaison statement from (*source and date*) concerning ...".
|
| 190 |
+
- Identify the study group(s) and working party(ies) (*if known*) or other standards organizations to which it has been sent. (*A liaison statement can be sent to more than one organization.*)
|
| 191 |
+
- Indicate the level of approval, e.g., study group or working party, or state that the liaison statement has been agreed at a rapporteur group meeting.
|
| 192 |
+
- Indicate if the liaison statement is sent for action *or* comment *or* information. (*If sent to more than one organization, indicate this for each one.*)
|
| 193 |
+
- If action is requested, indicate the date by which a reply is required.
|
| 194 |
+
- Include the name and address of the contact person.
|
| 195 |
+
|
| 196 |
+
The text of the liaison statement should be concise and clear, using a minimum of jargon.
|
| 197 |
+
|
| 198 |
+
An example of the information required in a liaison statement is shown in Figure 1-1.
|
| 199 |
+
|
| 200 |
+
---
|
| 201 |
+
|
| 202 |
+
| | | | |
|
| 203 |
+
|---------------------|---------------------------------------------------------------------------------------------------------------|-----------------------|--------------------------|
|
| 204 |
+
| <b>Question(s):</b> | 4 | <b>Meeting, date:</b> | London, 2-6 October 2017 |
|
| 205 |
+
| <b>Study Group:</b> | 15 | <b>Working Party:</b> | 1 |
|
| 206 |
+
| <b>Source:</b> | ITU-T SG15, Rapporteur group for Q4/15 | | |
|
| 207 |
+
| <b>Title:</b> | LS/o/r on Object identifier registration – Reply to liaison statement from Q11/17 (Geneva, 5-9 February 2017) | | |
|
| 208 |
+
|
| 209 |
+
---
|
| 210 |
+
|
| 211 |
+
#### **LIAISON STATEMENT**
|
| 212 |
+
|
| 213 |
+
| | |
|
| 214 |
+
|----------------------------|---------------------------------------------------------|
|
| 215 |
+
| <b>For action to:</b> | ITU-T Q11/17 |
|
| 216 |
+
| <b>For information to:</b> | ITU-R SG11, ISO/IEC JTC 1/SC 6 |
|
| 217 |
+
| <b>Approval:</b> | Q4/15 rapporteur group meeting (London, 6 October 2017) |
|
| 218 |
+
| <b>Deadline:</b> | 22 January 2018 |
|
| 219 |
+
|
| 220 |
+
---
|
| 221 |
+
|
| 222 |
+
| | | |
|
| 223 |
+
|-----------------|--------------------------------------------------------|----------------------------------------------------------------------|
|
| 224 |
+
| <b>Contact:</b> | John Jones, rapporteur for Q4/15<br>ABC Company<br>USA | Tel: +1 576 980 9987<br>Fax: +1 576 980 9956<br>E-mail: jj@abcco.com |
|
| 225 |
+
|-----------------|--------------------------------------------------------|----------------------------------------------------------------------|
|
| 226 |
+
|
| 227 |
+
**Figure 1-1 – Example of the information required in a liaison statement**
|
| 228 |
+
|
| 229 |
+
**1.5.2** Liaison statements should be forwarded to the appropriate destinations as soon after the meeting as possible. Copies of all liaison statements should also be sent to the chairmen of the study groups and working parties involved for information and to TSB for processing.
|
| 230 |
+
|
| 231 |
+
### **1.6 Correspondence activities**
|
| 232 |
+
|
| 233 |
+
A correspondence activity on a particular topic may be authorized to be conducted via e-mail between meetings. Each correspondence activity should have specified terms of reference. A convener is appointed to moderate the e-mail discussion and prepare a report to a subsequent meeting. A correspondence activity should normally conclude no later than the contribution deadline of the meeting to which it is expected to report (see also clause 2.3.3.5).
|
| 234 |
+
|
| 235 |
+
### **1.7 Preparation of reports of study groups, working parties or joint working parties, and Recommendations**
|
| 236 |
+
|
| 237 |
+
**1.7.1** A report on the work done during a meeting of a study group, working party or joint working party shall be prepared by TSB. Reports of meetings not attended by TSB should be prepared under the responsibility of the chairman of the meeting. This report should set out the results of the meeting and the agreements reached in a condensed form and should identify the points left to the next meeting for further study. The number of annexes to the report should be kept to a strict minimum by means of cross-references to contributions, reports, etc., and references to material in the documentation of a study group or working party. It would be desirable to have a concise summary of contributions (or equivalent) considered by the meeting.
|
| 238 |
+
|
| 239 |
+
The report should concisely present the following: organization of work; references to and possible summary of contributions and/or documents issued during a meeting; main results, including status of new and/or revised Recommendations consented, determined or under development; directive for future work; planned meetings of working parties, sub-working parties and rapporteur groups; and condensed liaison statements endorsed at the study group or working party level. The table showing the status of Recommendations from the report is used to update the work programme database (see clause 1.4.7).
|
| 240 |
+
|
| 241 |
+
**1.7.2** To assist TSB in this task, the study group or working party may arrange for delegates to draft some parts of the report. TSB should coordinate this drafting work. If necessary, the meeting
|
| 242 |
+
|
| 243 |
+
will set up an editorial group to improve the texts of draft Recommendations in the official languages of the Union.
|
| 244 |
+
|
| 245 |
+
**1.7.3** If possible, the report shall be submitted for approval before the end of the meeting; otherwise, it shall be submitted to the chairman of the meeting for approval.
|
| 246 |
+
|
| 247 |
+
**1.7.4** When existing and already translated ITU-T texts have been used for some parts of the report, a copy of the report annotated with references to the original sources should also be sent to TSB. If the report contains ITU-T figures, the ITU-T reference number should not be deleted even if the figure has been modified.
|
| 248 |
+
|
| 249 |
+
**1.7.5** Individual reports of meetings should be accessible online to appropriate users as soon as electronic versions of these documents are available to TSB.
|
| 250 |
+
|
| 251 |
+
**1.7.6** ITU-T participating bodies are authorized to transmit study group or working party reports and documents to any experts they consider it expedient to consult, except where the study group or working party concerned has specifically decided that its report, or a document, is to be treated as confidential.
|
| 252 |
+
|
| 253 |
+
**1.7.7** The report of a study group's first meeting in the study period shall include a list of all the rapporteurs appointed. This list shall be updated, as required, in subsequent reports.
|
| 254 |
+
|
| 255 |
+
### **1.8 Definitions**
|
| 256 |
+
|
| 257 |
+
#### **1.8.1 Terms defined elsewhere**
|
| 258 |
+
|
| 259 |
+
NOTE – [b-ITU-T A.13] describes procedures and defines terms related to non-normative publications in addition to those defined in clause 1.8.2.
|
| 260 |
+
|
| 261 |
+
This Recommendation uses the following term defined elsewhere:
|
| 262 |
+
|
| 263 |
+
**1.8.1.1 Question** ([WTSA Res. 1]): Description of an area of work to be studied, normally leading to the production of one or more new or revised Recommendations.
|
| 264 |
+
|
| 265 |
+
#### **1.8.2 Terms defined in this Recommendation**
|
| 266 |
+
|
| 267 |
+
This Recommendation defines the following terms:
|
| 268 |
+
|
| 269 |
+
**1.8.2.1 amendment:** Changes or additions to an already published ITU-T Recommendation.
|
| 270 |
+
|
| 271 |
+
NOTE – If an amendment forms an integral part of the Recommendation, approval of the amendment follows the same approval procedure as the Recommendation; otherwise (e.g., when all changes are in appendices), it is agreed by the study group.
|
| 272 |
+
|
| 273 |
+
**1.8.2.2 annex:** Material (e.g., technical detail or explanation) that is necessary to the overall completeness and comprehensibility of a Recommendation, and is therefore considered an integral part of the Recommendation.
|
| 274 |
+
|
| 275 |
+
NOTE 1 – As an annex is an integral part of the Recommendation, approval of an annex follows the same approval procedure as the Recommendation.
|
| 276 |
+
|
| 277 |
+
NOTE 2 – In common ITU-T | ISO/IEC texts, this element is called an "integral annex".
|
| 278 |
+
|
| 279 |
+
**1.8.2.3 appendix:** Material that is supplementary to and associated with the subject matter of a Recommendation but is not essential to its completeness or comprehensibility.
|
| 280 |
+
|
| 281 |
+
NOTE 1 – An appendix is not considered to be an integral part of the Recommendation and thus it does not require the same approval procedure as the Recommendation; agreement by the study group is sufficient. See [b-ITU-T A.13] for the case of an appendix agreed separately from its base Recommendation.
|
| 282 |
+
|
| 283 |
+
NOTE 2 – In common ITU-T | ISO/IEC texts, this element is called a "non-integral annex".
|
| 284 |
+
|
| 285 |
+
**1.8.2.4 clause:** Single-digit or multiple-digit numbered text passages.
|
| 286 |
+
|
| 287 |
+
**1.8.2.5 corrigendum:** Corrections to an already published ITU-T Recommendation.
|
| 288 |
+
|
| 289 |
+
NOTE 1 – Approval of a corrigendum follows the same approval procedure as an amendment.
|
| 290 |
+
|
| 291 |
+
NOTE 2 – In common ITU-T | ISO/IEC texts, this element is called a "technical corrigendum".
|
| 292 |
+
|
| 293 |
+
**1.8.2.6 erratum:** Corrections of publication and editorial errors in an already published ITU-T Recommendation. An erratum is published by TSB with the concurrence of the study group Chairman, in consultation with other relevant parties.
|
| 294 |
+
|
| 295 |
+
**1.8.2.7 normative reference:** The whole or parts of another document where the referenced document contains provisions which, through reference to it, constitute provisions to the referring document.
|
| 296 |
+
|
| 297 |
+
**1.8.2.8 text:** The "text" of Recommendations is understood in a broad sense. It may contain printed or coded text and/or data (such as test images, graphics, software, etc.).
|
| 298 |
+
|
| 299 |
+
**1.8.2.9 work item:** An assigned piece of work, which is identifiable with a Question and which has specific or general objectives, which will result in a product, such as a Recommendation, for publication by ITU-T.
|
| 300 |
+
|
| 301 |
+
**1.8.2.10 work programme:** A list of work items that are owned by a study group.
|
| 302 |
+
|
| 303 |
+
### 1.9 References
|
| 304 |
+
|
| 305 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 306 |
+
|
| 307 |
+
- | | |
|
| 308 |
+
|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 309 |
+
| [ITU-T A.2] | Recommendation ITU-T A.2 (2012), <i>Presentation of contributions to the ITU Telecommunication Standardization Sector.</i> |
|
| 310 |
+
| [ITU-T A.5] | Recommendation ITU-T A.5 (2019), <i>Generic procedures for including references to documents of other organizations in ITU-T Recommendations.</i> |
|
| 311 |
+
| [ITU-T A.7] | Recommendation ITU-T A.7 (2016), <i>Focus groups: Establishment and working procedures.</i> |
|
| 312 |
+
| [ITU-T A.11] | Recommendation ITU-T A.11 (2012), <i>Publication of ITU-T Recommendations and World Telecommunication Standardization Assembly proceedings.</i> |
|
| 313 |
+
| [ITU-T A.25] | Recommendation ITU-T A.25 (2019), <i>Generic procedures for incorporating text between ITU-T and other organizations.</i> |
|
| 314 |
+
| [PP Res. 66] | Plenipotentiary Conference Resolution 66 (Rev. Dubai, 2018), <i>Documents and publication of the Union.</i> |
|
| 315 |
+
| [WTSA Res. 1] | WTSA Resolution 1 (Rev. Hammamet, 2016), <i>Rules of procedure of the ITU Telecommunication Standardization Sector.</i> |
|
| 316 |
+
| [WTSA Res. 2] | WTSA Resolution 2 (Rev. Hammamet, 2016), <i>ITU Telecommunication Standardization Sector study group responsibility and mandates.</i> |
|
| 317 |
+
| [WTSA Res. 18] | WTSA Resolution 18 (Rev. Hammamet, 2016), <i>Principles and procedures for the allocation of work to, and strengthening coordination and cooperation among, the ITU Radiocommunication, ITU Telecommunication Standardization and ITU Telecommunication Development Sectors.</i> |
|
| 318 |
+
| [WTSA Res. 22] | WTSA Resolution 22 (Rev. Hammamet, 2016), <i>Authorization for the Telecommunication Standardization Advisory Group to act between world telecommunication standardization assemblies.</i> |
|
| 319 |
+
|
| 320 |
+
[WTSA Res. 45] WTSA Resolution 45 (Rev. Hammamet, 2016), *Effective coordination of standardization work across study groups in the ITU Telecommunication Standardization Sector and the role of the ITU Telecommunication Standardization Advisory Group*.
|
| 321 |
+
|
| 322 |
+
[WTSA Res. 54] WTSA Resolution 54 (Rev. Hammamet, 2016), *Creation of, and assistance to, regional groups*.
|
| 323 |
+
|
| 324 |
+
## **2 Study group management**
|
| 325 |
+
|
| 326 |
+
### **2.1 Study group structure and distribution of work**
|
| 327 |
+
|
| 328 |
+
**2.1.1** Study group chairmen shall be responsible for the establishment of an appropriate structure for the distribution of work and the selection of an appropriate team of working party chairmen and shall take into account the advice provided by the members of the study group as well as the proven competence, both technical and managerial, of the candidates.
|
| 329 |
+
|
| 330 |
+
**2.1.2** A study group may entrust a Question, a group of Questions or the maintenance of some existing Recommendations within its general area of responsibility to a working party.
|
| 331 |
+
|
| 332 |
+
**2.1.3** Where the scope of the work is considerable, a study group may decide to further divide the tasks assigned to a working party to sub-working parties.
|
| 333 |
+
|
| 334 |
+
**2.1.4** Working parties and sub-working parties should be set up only after thorough consideration of the Questions. Proliferation of working parties, sub-working parties or any other subgroups should be avoided.
|
| 335 |
+
|
| 336 |
+
**2.1.5** A study group may exceptionally, by agreement with other relevant study group(s) and taking account of any advice from TSAG and the Director of TSB, entrust a joint working party with Questions or parts of Questions of common interest to the study groups concerned. This study group shall act as the parent study group for the joint working party and shall coordinate and have responsibility for the work concerned. The contributions used as a basis for discussion in the joint working party shall be sent exclusively to those registered in the joint working party. Only the reports shall be sent to all participating bodies of the study groups concerned.
|
| 337 |
+
|
| 338 |
+
NOTE – Two or more study groups may decide to progress work on topics of common interest through joint meetings of their rapporteur groups.
|
| 339 |
+
|
| 340 |
+
**2.1.6** As the promotion of study group activities is an essential element in any ITU-T marketing plan, each study group chairman, supported by other study group leaders and subject matter experts, is encouraged to establish, maintain and participate in a promotion plan, coordinated with TSB, whose emphasis is the dissemination of study group information to the telecommunication community. Such study group information dissemination should cover, but is not limited to, new work initiatives and significant accomplishments regarding technologies and technical solutions.
|
| 341 |
+
|
| 342 |
+
### **2.2 Joint coordination activities**
|
| 343 |
+
|
| 344 |
+
See clause 5.
|
| 345 |
+
|
| 346 |
+
### **2.3 The roles of rapporteurs**
|
| 347 |
+
|
| 348 |
+
**2.3.1** The chairmen of study groups and working parties (including joint working parties) are encouraged to make most effective use of the limited resources available by delegating responsibility to rapporteurs for the detailed study of individual Questions or small groups of related Questions, parts of Questions, terminology, or amendment of existing Recommendations. Responsibility for review and approval of the results resides with the study group or working party.
|
| 349 |
+
|
| 350 |
+
**2.3.2** Liaison between ITU-T study groups or with other organizations can be facilitated by rapporteurs or by the appointment of liaison rapporteurs.
|
| 351 |
+
|
| 352 |
+
**2.3.3** The following guidelines should be used as a basis within each study group or working party to define the roles of rapporteurs, associate rapporteurs and liaison rapporteurs; however, they may be adjusted following careful deliberation of the need for change and with the approval of the relevant study group or working party.
|
| 353 |
+
|
| 354 |
+
**2.3.3.1** Specific persons should be appointed as rapporteurs to be responsible for progressing the study of those Questions, or specific study topics, that are felt to be likely to benefit from such appointments. The same person may be appointed as rapporteur for more than one Question, or topic, particularly if the Questions, parts of Questions, terminology, or amendment of existing Recommendations concerned are closely related.
|
| 355 |
+
|
| 356 |
+
**2.3.3.2** Rapporteurs may be appointed (and their appointments may be terminated) at any time with the agreement of the competent working party, or of the study group, where the Question(s) are not allocated to a working party. The term of the appointment relates to the work that needs to be done rather than to the interval between WTSAs. If the related Question is modified by WTSA, for continuity purposes, the rapporteur may, at the discretion of the new study group chairman, continue to progress the relevant work until the next meeting of the study group.
|
| 357 |
+
|
| 358 |
+
**2.3.3.3** Where the work so requires, a rapporteur may propose the appointment of one or more associate rapporteurs, liaison rapporteurs or editors, whose appointments should then be endorsed by the relevant working party (or study group). Again, these appointments may be made or terminated at any time in accordance with the work requirements. An associate rapporteur assists the rapporteur, either in general or to deal with a particular point or area of study in a Question. A liaison rapporteur assists the rapporteur by ensuring there is effective liaison with other groups, by attending meetings of other designated groups to advise and assist in an official capacity, by correspondence with such groups or by any other means considered appropriate by the rapporteur. In the event that a liaison rapporteur is not appointed, the responsibility to ensure effective liaison resides with the rapporteur. The editor assists the rapporteur in the preparation of the text of draft Recommendations or other publications.
|
| 359 |
+
|
| 360 |
+
**2.3.3.4** Rapporteurs, and their associate and liaison rapporteurs as well as the editors, play an indispensable role in coordinating increasingly detailed and often highly technical study. Consequently, their appointment should be primarily based on their expertise in the subject to be studied.
|
| 361 |
+
|
| 362 |
+
**2.3.3.5** As a general principle, work by correspondence (including electronic messaging and telephone communications) is preferred (see also clause 1.6) and the number of meetings should be kept to a strict minimum, consistent with the scale and milestones agreed by the parent group. Where possible, meetings in related areas of study or within a work area covered by a JCA should be coordinated. In any case, this work should proceed in a continuous fashion between meetings of the parent group.
|
| 363 |
+
|
| 364 |
+
**2.3.3.6** The rapporteur's responsibilities are:
|
| 365 |
+
|
| 366 |
+
- a. to coordinate the detailed study in accordance with guidelines established at working party (or study group) level;
|
| 367 |
+
- b. to the extent authorized by the study group, to act as a contact point and source of expertise for the allocated study topic with other ITU-T, ITU Radiocommunication Sector (ITU-R) and ITU Telecommunication Development Sector (ITU-D) study groups, other rapporteurs, other international organizations and other standards organizations (where appropriate) and TSB;
|
| 368 |
+
- c. to adopt methods of work (correspondence, including the use of the TSB EDH system, meetings of experts, etc.) as considered appropriate for the task;
|
| 369 |
+
- d. in consultation with the collaborators for the study topic, to review and update the work programme, which should be approved and reviewed periodically by the parent group (see clause 1.4.7);
|
| 370 |
+
|
| 371 |
+
- e. to ensure that the parent working party (or study group) is kept well informed of the progress of the study, particularly of work proceeding by correspondence or otherwise outside of the normal study group and working party meetings;
|
| 372 |
+
- f. in particular, to submit a progress report (e.g., of a rapporteur's meeting or editor's work) to each of the parent group's meetings (see suggested format in Appendix I), in the form of a TD to be submitted as soon as possible (see clause 3.3.3);
|
| 373 |
+
- g. to submit, where possible, as separate TDs each draft new or revised Recommendation planned for consent or determination (or draft document planned for agreement), at least six weeks prior to the parent group's meeting;
|
| 374 |
+
- h. to give the parent working party or study group and TSB adequate advance notice of the intention to hold any meetings of experts (see clause 2.3.3.10), particularly where such meetings are not included in the original programme of work;
|
| 375 |
+
- i. to establish a group of active "collaborators" from the working party (or study group) where appropriate, with an updated list of those collaborators being given to TSB at each working party meeting;
|
| 376 |
+
- j. to delegate the relevant functions from the list above to associate rapporteurs and/or liaison rapporteurs, as necessary.
|
| 377 |
+
|
| 378 |
+
**2.3.3.7** The basic goal of each rapporteur is to assist the study group or working party in developing new and revised Recommendations to meet changing requirements in telecommunication techniques and services. However, it must be clearly understood that rapporteurs should not feel under any obligation to produce such texts unless a thorough study of the Question reveals a clear need for them. If it turns out that this is not the case, the work should be concluded with a simple report to the parent group establishing that fact.
|
| 379 |
+
|
| 380 |
+
**2.3.3.8** Rapporteurs are responsible for the quality of their texts, submitted by the study group for publication. They shall be involved in the final review of that text prior to it being submitted to the publication process. This responsibility extends only to text in the original language and should take into account applicable time constraints. (See [ITU-T A.11] on the publication of ITU-T Recommendations.)
|
| 381 |
+
|
| 382 |
+
**2.3.3.9** Rapporteurs should normally base any draft new or substantially revised Recommendations on written contribution(s) from ITU-T members (see also clause 1.4.7).
|
| 383 |
+
|
| 384 |
+
**2.3.3.10** In conjunction with their work planning, rapporteurs must give advance notice of any meetings they arrange, not only to the collaborators on their Question or project, but also to the study group and working party (see clause 2.3.3.11) and to TSB. TSB is not required to circulate collective letters for meetings below working party level. The intention to hold rapporteur group meetings, along with details of the issues to be studied, should be agreed in principle and publicized with as much notice as possible (normally at least two months) at study group or working party meetings (for inclusion in their reports) and via the study group webpage, for example.
|
| 385 |
+
|
| 386 |
+
**2.3.3.11** TSB will post a convening letter for rapporteur group meetings (using a TSB-defined template), normally at least two months prior to the meeting, on the study group webpage, as provided by the study group. Visa support should be provided by the meeting host.
|
| 387 |
+
|
| 388 |
+
**2.3.3.12** Rapporteurs should prepare a meeting report for each rapporteur group meeting held and submit it as a TD to the next study group or working party meeting. See clause 3.3 for submission and processing of TDs, and in particular clause 3.3.3.
|
| 389 |
+
|
| 390 |
+
This report should include the date, venue and chairman, an attendance list with affiliations, the agenda of the meeting, a summary of technical inputs, a summary of results and the liaison statements sent to other organizations.
|
| 391 |
+
|
| 392 |
+
Rapporteurs will ask, during each meeting, whether anyone has knowledge of intellectual property rights issues, including patents, copyright for software or text, marks, the use of which may be required to implement or publish the Recommendation being considered. The fact that the question was asked shall be recorded in the meeting report, along with any affirmative responses.
|
| 393 |
+
|
| 394 |
+
**2.3.3.13** Rapporteur group meetings, as such, should not be held during working party or study group meetings. However, rapporteurs may be called upon to chair those portions of working party or study group meetings that deal with their particular area of expertise. In these cases, rapporteurs must recognize that the rules of the working party and study group meetings then apply and the more relaxed rules described above, particularly those that relate to document approvals and submission deadlines, would not apply.
|
| 395 |
+
|
| 396 |
+
**2.3.3.14** The parent working party (or study group) must define clear terms of reference for each rapporteur. The general direction to be followed in the study should be discussed, reviewed as necessary and agreed periodically by the parent group.
|
| 397 |
+
|
| 398 |
+
**2.3.3.15** When meetings are arranged to be held outside ITU premises, participants should not be charged for meeting facilities, unless agreed in advance by the study group. Meeting charges should be an exceptional case and only done if, for example, the study group is of the opinion that a meeting charge is necessary for the work to proceed properly. However, no participant should be excluded from participation if he or she is unwilling to pay the charge. Additional services offered by the host shall be voluntary, and there shall be no obligation on any of the participants resulting from these additional services.
|
| 399 |
+
|
| 400 |
+
## **3 Submission and processing of contributions**
|
| 401 |
+
|
| 402 |
+
### **3.1 Submission of contributions**
|
| 403 |
+
|
| 404 |
+
**3.1.1** Member States and other duly authorized entities registered with a study group or its relevant group should submit their contributions to current studies via electronic means, in accordance with guidance from the Director of TSB (see clause 3.2.6).
|
| 405 |
+
|
| 406 |
+
**3.1.2** *(clause intentionally left blank)*
|
| 407 |
+
|
| 408 |
+
**3.1.3** These contributions shall contain comments or results of experiments and proposals designed to further the studies to which they relate.
|
| 409 |
+
|
| 410 |
+
**3.1.4** Contributors are reminded, when submitting contributions, that early disclosure of patent information is desired, as contained in the statement on Common Patent Policy for ITU-T/ITU-R/ISO/IEC (available at the ITU-T website). Patent declarations are to be made using the "Patent Statement and Licensing Declaration Form for ITU-T/ITU-R Recommendation | ISO/IEC Deliverable" available at the ITU-T website. See also clause 3.1.5.
|
| 411 |
+
|
| 412 |
+
**3.1.5** A general patent statement and licensing declaration may be submitted using the form available at the ITU-T website. The purpose of this form is to give patent holders the voluntary option of making a general licensing declaration relative to patented material contained in any of their contributions. Specifically, the submitter of the licensing declaration declares its willingness to license, in case part(s) or all of any proposals contained in contributions submitted by the organization are included in ITU-T Recommendation(s) and the included part(s) contain items that have been patented or for which patent applications have been filed and whose use would be required to implement ITU-T Recommendation(s).
|
| 413 |
+
|
| 414 |
+
The general patent statement and licensing declaration is not a replacement for the individual (per Recommendation) patent statement and licensing declaration but is expected to improve responsiveness and early disclosure of the patent holder's compliance with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC.
|
| 415 |
+
|
| 416 |
+
**3.1.6** By making a contribution, contributors acknowledge, to the best of their knowledge, that material such as text, diagrams, etc., submitted as their contribution to the work of ITU-T has no restriction<sup>2</sup> in order to permit the normal distribution of this material for discussions within the appropriate ITU-T study groups and other groups and possible use, in whole or in part, with or without modification, in any resulting ITU-T Recommendations that are published (see [PP Res. 66]).
|
| 417 |
+
|
| 418 |
+
**3.1.7** If a contribution proposes to make normative reference to, or to incorporate text, diagrams, etc. from a document from a source qualified according to [ITU-T A.5], the source document should be clearly identified in the contribution, allowing [ITU-T A.5] or [ITU-T A.25] to be followed in the case the study group reaches consensus on such a proposal.
|
| 419 |
+
|
| 420 |
+
**3.1.8** A contributor submitting copyrighted software for incorporation in the draft Recommendation is required to submit a software copyright statement and licensing declaration form available at the ITU-T website. The form must be provided to TSB at the same time that the contributor submits the copyrighted software<sup>3</sup>.
|
| 421 |
+
|
| 422 |
+
**3.1.9** The full text of contributions that are to be considered at a study group or working party meeting shall reach TSB at least 12 calendar days before the meeting.
|
| 423 |
+
|
| 424 |
+
### **3.2 Processing of contributions**
|
| 425 |
+
|
| 426 |
+
**3.2.1** Contributions received at least two months before a meeting may be translated (see clause 3.2.2) and will be posted in the original and, if applicable, in translated languages, on the web as soon as practicable after they are received. They will be printed and distributed at the beginning of the meeting only to the participants present who request paper copies.
|
| 427 |
+
|
| 428 |
+
**3.2.2** If a chairman, in agreement with the participants of his or her study group (or working party), states that the study group (or working party) is willing to use documents in the original language, no translations will be made.
|
| 429 |
+
|
| 430 |
+
**3.2.3** Contributions received by the Director less than two months but not less than 12 calendar days before the date set for the opening of a meeting cannot be translated.
|
| 431 |
+
|
| 432 |
+
**3.2.4** Contributions should be posted on the web no more than three working days after they are received by the secretariat.
|
| 433 |
+
|
| 434 |
+
**3.2.5** Contributions received by the Director less than 12 calendar days before the meeting will not appear on the agenda of the meeting, will not be distributed and will be held for the next meeting. Contributions judged to be of extreme importance may be admitted by the Director at shorter notice. The final decision as to their consideration by the meeting shall be taken by the study group (or working party).
|
| 435 |
+
|
| 436 |
+
**3.2.6** The Director should insist that contributors follow the rules established for the presentation and form of documents set out in clause 2 of [ITU-T A.2], and the timing given in clause 3.1.9. A reminder should be sent out by the Director whenever appropriate.
|
| 437 |
+
|
| 438 |
+
**3.2.7** The Director, with the agreement of the study group chairman, may return to the contributor any document that does not comply with the general directives set out in [ITU-T A.2], so that it may be brought into line with those directives.
|
| 439 |
+
|
| 440 |
+
**3.2.8** Contributions shall not be included in reports as annexes, but should be referenced as needed.
|
| 441 |
+
|
| 442 |
+
**3.2.9** Contributions should, as far as possible, be submitted to a single study group. If, however, a member submits a contribution that it believes is of interest to several study groups, it should identify the study group primarily concerned; a single sheet giving the title of the contribution, its
|
| 443 |
+
|
| 444 |
+
---
|
| 445 |
+
|
| 446 |
+
<sup>2</sup> Restrictions include, but are not limited to, copyright ownership by other entities.
|
| 447 |
+
|
| 448 |
+
<sup>3</sup> See <https://www.itu.int/ipr>
|
| 449 |
+
|
| 450 |
+
source and a summary of its contents will be issued to the other study groups by the member. This single sheet will be numbered in the series of contributions of each study group to which it is issued.
|
| 451 |
+
|
| 452 |
+
### **3.3 TDs**
|
| 453 |
+
|
| 454 |
+
**3.3.1** TDs should be provided to TSB in electronic format. TSB shall post electronically those TDs submitted as electronic files as soon as they become available; those submitted as paper copies will be posted as soon as practicable. Printed copies may be provided upon request to persons with disabilities and specific needs.
|
| 455 |
+
|
| 456 |
+
**3.3.2** Extracts from reports of other study group meetings or from reports of chairmen, rapporteurs or drafting groups shall be published as TDs.
|
| 457 |
+
|
| 458 |
+
**3.3.3** TDs input before the start of the study group or working party meeting, including documents from the ITU secretariat, should be posted on the relevant page of the website not later than three working days from the date on which they are received by the secretariat, to ensure their availability not later than seven calendar days before the start of the meeting. This deadline shall not extend to administrative documents or reports on events that have taken place less than 21 calendar days before the start of the meeting, nor to proposals from chairmen and convenors of ad hoc groups, compilations of proposals prepared by chairmen or the secretariat, or documents specifically requested by the meeting. Reports on events that have taken place less than 21 calendar days before the start of the meeting should normally be posted on the relevant page of the website not later than two calendar days before the beginning of the discussion of the item in question at the meeting, unless otherwise agreed by the meeting.
|
| 459 |
+
|
| 460 |
+
**3.3.4** TDs can be produced during the meeting.
|
| 461 |
+
|
| 462 |
+
**3.3.5** Chairmen and vice-chairmen of study groups and working parties may at any time submit inputs as TDs to their study group or working party, including, in particular, proposals likely to accelerate the debates.
|
| 463 |
+
|
| 464 |
+
### **3.4 Electronic access**
|
| 465 |
+
|
| 466 |
+
**3.4.1** TSB will post electronically all documents (e.g., contributions, TDs (including liaison statements)) as soon as electronic versions of these documents are available. Appropriate search facilities for posted documents should be provided (see also clause 3.3.3).
|
| 467 |
+
|
| 468 |
+
### **3.5 Other document types**
|
| 469 |
+
|
| 470 |
+
As the work of the ITU-T and its groups progresses, various types of output materials might result, in addition to Recommendations and other texts previously described. This clause addresses the types of texts that are in use within ITU-T, other than those defined in [WTSA Res. 1] or clause 1.8.2 of this Recommendation. Other types of ITU-T documents include non-WTSA proceedings (e.g., Kaleidoscope), tutorials, e-learning and web-based guides. These document types do not require agreement by a study group and do not have working methods described by an A-series Recommendation.
|
| 471 |
+
|
| 472 |
+
## **4 Other ITU-T groups**
|
| 473 |
+
|
| 474 |
+
### **4.1 Overview**
|
| 475 |
+
|
| 476 |
+
In addition to study groups, other groups operate to carry forward the mission of the ITU-T. This clause documents the types of groups other than study groups that exist within ITU-T.
|
| 477 |
+
|
| 478 |
+
### **4.2 Focus group (FG)**
|
| 479 |
+
|
| 480 |
+
The objective of focus groups is to help advance the work of the ITU Telecommunication Standardization Sector (ITU-T) study groups and to encourage the participation of members of other
|
| 481 |
+
|
| 482 |
+
standards organizations, including experts and individuals who may not be members of ITU. Focus group activities may include an analysis of gaps between current Recommendations and expected Recommendations, and provide material for consideration in the development of Recommendations. Their working methods are documented in [ITU-T A.7].
|
| 483 |
+
|
| 484 |
+
### **4.3 Intersector Rapporteur Group (IRG)**
|
| 485 |
+
|
| 486 |
+
Intersector Rapporteur Groups (IRGs) are established to coordinate the progress of specific topics of mutual interest between sectors of the ITU. For a given topic, IRGs encourage the collaboration between ITU-T study groups and groups from other ITU sectors on work items unique to each study group. See [WTSA Res. 18] for more details.
|
| 487 |
+
|
| 488 |
+
### **4.4 Joint Coordination Activity (JCA)**
|
| 489 |
+
|
| 490 |
+
A Joint Coordination Activity (JCA) is formed to coordinate activities on topics of relevance across ITU-T Study Groups. They report their progress either to TSAG or to a particular study group. Where FGs are typically formed to study forward-looking topics, report results, and dissolve, JCAs are envisioned as tools for coordination between study groups. Like FGs, JCAs do not write Recommendations. Their working methods are documented in clause 5.
|
| 491 |
+
|
| 492 |
+
### **4.5 Regional Group (RG)**
|
| 493 |
+
|
| 494 |
+
For information on regional groups see [WTSA Res. 54].
|
| 495 |
+
|
| 496 |
+
### **4.6 ITU-T group types for collaborating with other SDOs**
|
| 497 |
+
|
| 498 |
+
Several groups within ITU-T have been formed to support joint efforts between ITU-T and other standards development organizations (SDOs) on the development of common or aligned specifications or standards. The working methods of these groups vary, as does the documentation regarding how new instances of such groups are formed. In some cases, such groups seek to align the timing by which standards development progresses through two processes, such as ITU-T and another SDO. In other cases, participation in the collaborative effort is not limited to a specific SDO. See [b-ITU-T A.sup5] for more information.
|
| 499 |
+
|
| 500 |
+
### **4.7 Additional ITU-T groups**
|
| 501 |
+
|
| 502 |
+
In addition to the group types documented above, additional groups exist that operate with working methods distinct from those documented above. [WTSA Res. 22] *resolves 1 e)* provides more information. TSAG and study groups should terminate inactive groups.
|
| 503 |
+
|
| 504 |
+
## **5 Joint coordination activities**
|
| 505 |
+
|
| 506 |
+
**5.1** A joint coordination activity (JCA) is a tool for management of the work programme of ITU-T when there is a need to address a broad subject covering the area of competence of more than one study group (see also [WTSA Res. 45]). A JCA may help to coordinate the planned work effort in terms of subject matter, time-frames for meetings, colocated meetings where necessary and publication goals including, where appropriate, release planning of the resulting Recommendations.
|
| 507 |
+
|
| 508 |
+
The establishment of a JCA aims mainly at improving coordination and planning. The work itself will continue to be conducted by the relevant study groups and the results are subject to the normal approval processes within each study group. A JCA may identify technical and strategic issues within the scope of its coordination role, but will not perform technical studies nor write Recommendations. A JCA may also address coordination of activities with recognized standards development organizations (SDOs) and forums, including periodic discussion of work plans and schedules of deliverables. The study groups take JCA suggestions into consideration as they carry out their work.
|
| 509 |
+
|
| 510 |
+
**5.2** Any group (study group or TSAG) may propose that a JCA be established. The proposal to establish a JCA should first be discussed within the proposing group's management team, then among the relevant study group chairmen and the TSAG chairman. Discussions may be held with external SDOs and forum leaders.
|
| 511 |
+
|
| 512 |
+
If the study group proposing the establishment of the JCA has been designated as the lead study group by WTSA or TSAG according to Section 2 of [WTSA Res. 1], and if the subject is under their responsibility and mandate as described in [WTSA Res. 2], then the study group may establish a JCA on its own authority. If a study group meeting is pending within the next two months, then an electronic notification<sup>4</sup> proposing the JCA, including the terms of reference (including scope, objectives and anticipated lifetime) and the chairman, is published four weeks prior to the study group meeting, giving opportunity for the membership to give their position at the meeting. If this is done at least four weeks prior to the study group meeting, following the resolution of any comments, the JCA may be established by the study group by consensus at its meeting. If a study group meeting is not pending within the next two months, then an electronic notification as above is sent for the membership to give their position by electronic response. If the notification is sent less than four weeks before the study group meeting, no decision is taken at the study group meeting; the decision may be taken four weeks after the notification, excluding the meeting time. If necessary, the proposal is adjusted taking into consideration comments received and made available to the study group electronically for decision with a further four-week interval. If there are no substantive comments, the JCA is considered approved. TSAG will be informed for review, possible comment, and endorsement. TSAG may consider the terms of reference of the JCA in the context of the overall work programme of ITU-T and may provide comments to modify the terms of reference.
|
| 513 |
+
|
| 514 |
+
Where the lead study group has not yet been designated by WTSA or TSAG for the subject, or where the subject for the JCA is a broad subject potentially falling under the responsibility and mandate of a number of study groups as described in [WTSA Res. 2], then the proposal has to be made available to the membership for consideration. If a TSAG meeting is pending within the next two months, then an electronic notification<sup>5</sup> proposing the JCA, including the terms of reference (including scope, objectives and anticipated lifetime) and the chairman, is published four weeks prior to the TSAG meeting, giving opportunity for the membership to give their position at the meeting. If this is done at least four weeks prior to the TSAG meeting, following the resolution of any comments, the JCA may be established by TSAG by consensus at its meeting. If a TSAG meeting is not pending within the next two months, then an electronic notification as above is sent for the membership to give their position by electronic response. If the notification is sent less than four weeks before the TSAG meeting, no decision is taken at the TSAG meeting; the decision may be taken four weeks after the notification, excluding the meeting time. If necessary, the proposal is adjusted taking into consideration comments received and made available to the membership electronically for decision with a further four-week interval. If there are no substantive comments, the JCA is considered approved. The decision includes the designation of the group responsible (a study group or TSAG), the terms of reference (including scope, objectives and anticipated lifetime) and the chairman.
|
| 515 |
+
|
| 516 |
+
Figure 5-1 provides a schematic of the alternatives in proposing and approving the creation of a JCA.
|
| 517 |
+
|
| 518 |
+
---
|
| 519 |
+
|
| 520 |
+
<sup>4</sup> This electronic notification should be sent to the general e-mail reflector for the proposing study group and should also be a TD to the next meeting of the study group.
|
| 521 |
+
|
| 522 |
+
<sup>5</sup> This electronic notification should be sent to the general e-mail reflector for the potentially involved study groups and TSAG, and should also be a TD to the next meeting of TSAG.
|
| 523 |
+
|
| 524 |
+
|
| 525 |
+
|
| 526 |
+
```
|
| 527 |
+
|
| 528 |
+
graph TD
|
| 529 |
+
Start([JCA proposal initiated]) --> D1{Lead SG and within Res. 2 mandate?}
|
| 530 |
+
D1 -- No --> E1[Electronic notification to TSAG and SG reflectors]
|
| 531 |
+
D1 -- Yes --> E2[Electronic notification to SG reflector]
|
| 532 |
+
E1 --> D2{Time to next TSAG meeting?}
|
| 533 |
+
E2 --> D3{Time to next SG meeting?}
|
| 534 |
+
D2 -- "> 4 weeks, < 8 weeks*" --> C1[Comments from TSAG, and SG membership]
|
| 535 |
+
D2 -- "< 4 weeks" --> C2[Comments from TSAG, and SG membership]
|
| 536 |
+
D2 -- "> 8 weeks*" --> C3[Comments from TSAG, and SG membership]
|
| 537 |
+
D3 -- "> 4 weeks, < 8 weeks*" --> C4[Comments from SG membership]
|
| 538 |
+
D3 -- "< 4 weeks" --> C5[Comments from SG membership]
|
| 539 |
+
D3 -- "> 8 weeks*" --> C6[Comments from SG membership]
|
| 540 |
+
C1 --> R1[Resolve comments, approve at TSAG meeting]
|
| 541 |
+
C2 --> R2[Resolve comments, approve** electronically]
|
| 542 |
+
C3 --> R3[Discuss at TSAG meeting but no decision yet]
|
| 543 |
+
C4 --> R4[Resolve comments, approve at SG meeting]
|
| 544 |
+
C5 --> R5[Resolve comments, approve** electronically]
|
| 545 |
+
C6 --> R6[Discuss at SG meeting but no decision yet]
|
| 546 |
+
R3 --> R7[Resolve comments, approve** electronically]
|
| 547 |
+
R6 --> R8[Resolve comments, approve** electronically]
|
| 548 |
+
R1 --> End([JCA-initiated])
|
| 549 |
+
R2 --> End
|
| 550 |
+
R4 --> End
|
| 551 |
+
R5 --> End
|
| 552 |
+
R7 --> End
|
| 553 |
+
R8 --> End
|
| 554 |
+
|
| 555 |
+
```
|
| 556 |
+
|
| 557 |
+
Flowchart titled 'Alternatives in proposing and approving the creation of a JCA'. The process starts with 'JCA proposal initiated'. A decision diamond asks 'Lead SG and within Res. 2 mandate?'. If 'No', it goes to 'Electronic notification to TSAG and SG reflectors'. If 'Yes', it goes to 'Electronic notification to SG reflector'. Both paths lead to a decision diamond about the time to the next meeting. For the 'Yes' path, the decision is 'Time to next SG meeting?'. For the 'No' path, it is 'Time to next TSAG meeting?'. Each path has three time-based branches: '> 4 weeks, < 8 weeks\*', '< 4 weeks', and '> 8 weeks\*'. These lead to boxes for 'Comments from SG membership' or 'Comments from TSAG, and SG membership'. These are followed by boxes for 'Resolve comments, approve at SG meeting', 'Resolve comments, approve\*\* electronically', or 'Discuss at SG/TSAG meeting but no decision yet'. Some paths have a final 'Resolve comments, approve\*\* electronically' box. All paths converge at 'JCA-initiated'.
|
| 558 |
+
|
| 559 |
+
A.1(19)\_F5-1
|
| 560 |
+
|
| 561 |
+
\* Nominal time period.
|
| 562 |
+
|
| 563 |
+
\*\* If there are no substantive comments, the JCA is considered approved. If the JCA proposal is modified per comments received, it is again circulated for a four-week review. If there are no substantive comments, the JCA is considered approved.
|
| 564 |
+
|
| 565 |
+
**Figure 5-1 – Alternatives in proposing and approving the creation of a JCA**
|
| 566 |
+
|
| 567 |
+
**5.3** JCAs are open, but (to restrict their size) should primarily be limited to official representatives from the relevant study groups that are responsible for work covered by the scope of the JCA. A JCA may also include invited experts and invited representatives of other SDOs and forums, as appropriate. All participants should confine inputs to a JCA to the purpose of the JCA.
|
| 568 |
+
|
| 569 |
+
**5.4** The establishment of a JCA is to be announced in a TSB circular, which should include the terms of reference of the JCA, the chairman of the JCA, and the study group responsible for the JCA.
|
| 570 |
+
|
| 571 |
+
**5.5** JCAs should work primarily by correspondence and electronic meetings. Any physical meeting considered necessary should be convened by the chairman of the JCA. Physical meetings should be supported by conferencing capabilities where possible, and both physical and electronic meetings should be scheduled as far as practicable at times that will provide maximum opportunity for broad participation. It is anticipated that physical meetings will be in conjunction with the involved study group meetings (in which case it is reflected in the collective letter for that study group) as far as practicable, but if a separate meeting is to be held, it is to be announced at least four weeks in advance by an (electronic) collective invitation letter.
|
| 572 |
+
|
| 573 |
+
**5.6** Inputs to the work of a JCA should be sent to the JCA chairman and to the concerned TSB counsellor, and the latter will make these available to the members of the JCA.
|
| 574 |
+
|
| 575 |
+
**5.7** JCAs may submit proposals to the relevant study groups to achieve alignment in the development of related Recommendations and other deliverables by the respective study groups. A JCA may also issue liaison statements.
|
| 576 |
+
|
| 577 |
+
**5.8** JCA input and output documents and reports are made available to the ITU-T membership. Reports are issued after each JCA meeting. TSAG may monitor JCA activities through these reports.
|
| 578 |
+
|
| 579 |
+
**5.9** TSB will provide support for a JCA, within available resource limits.
|
| 580 |
+
|
| 581 |
+
**5.10** A JCA may be terminated at any time if the involved study groups agree that the JCA is no longer required. A proposal to do so, including justification, may be submitted by any study group involved or by TSAG, and examined for decision by the study group responsible for the JCA, after consulting the involved study groups and TSAG (via electronic means, if a TSAG meeting is not pending in the near future). A JCA will be reviewed at the first TSAG meeting following the WTSA. A specific decision must be taken on the continuation of the JCA, potentially with adjusted terms of reference.
|
| 582 |
+
|
| 583 |
+
## Annex A
|
| 584 |
+
|
| 585 |
+
## Template to describe a proposed new Recommendation in the work programme
|
| 586 |
+
|
| 587 |
+
(This annex forms an integral part of this Recommendation.)
|
| 588 |
+
|
| 589 |
+
| | | | |
|
| 590 |
+
|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------|---------------------------------------|
|
| 591 |
+
| <b>Question:</b> | / | <b>Proposed new ITU-T Recommendation</b> | <b><Meeting date></b> |
|
| 592 |
+
| <b>Reference and title:</b> | Recommendation ITU-T <X.xxx> "Title" | | |
|
| 593 |
+
| <b>Base text:</b> | <C nnn> or <TD nnnn> | | <b>Timing:</b> <Month-Year> |
|
| 594 |
+
| <b>Editor(s):</b> | <Name, membership, e-mail address> | | <b>Approval process:</b> <AAP or TAP> |
|
| 595 |
+
| <b>Scope</b> (defines the intent or object of the Recommendation and the aspects covered, thereby indicating the limits of its applicability): | | | |
|
| 596 |
+
| <b>Summary</b> (provides a brief overview of the purpose and contents of the Recommendation, thus permitting readers to judge its usefulness for their work): | | | |
|
| 597 |
+
| <b>Relations to ITU-T Recommendations or to other standards</b> (approved or under development): | | | |
|
| 598 |
+
| <b>Liaisons with other study groups or with other standards bodies:</b> | | | |
|
| 599 |
+
| <b>Supporting members that are committing to contributing actively to the work item:</b><br><Member States, Sector Members, Associates, Academia> | | | |
|
| 600 |
+
|
| 601 |
+
## Appendix I
|
| 602 |
+
|
| 603 |
+
### Rapporteur progress report format
|
| 604 |
+
|
| 605 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 606 |
+
|
| 607 |
+
The following format is recommended for the progress reports of rapporteurs to enable a maximum transfer of information to all concerned:
|
| 608 |
+
|
| 609 |
+
- a)* brief summary of contents of report;
|
| 610 |
+
- b)* conclusions or Recommendations sought to be endorsed;
|
| 611 |
+
- c)* *status of work with reference to work plan, including baseline document if available;*
|
| 612 |
+
- d)* draft new or draft revised Recommendations;
|
| 613 |
+
- e)* draft liaison in response to or requesting action by other study groups or organizations;
|
| 614 |
+
- f)* reference to contributions considered part of assigned study and summary of contributions considered at rapporteur group meetings (see Note);
|
| 615 |
+
- g)* reference to liaison statements from other organizations;
|
| 616 |
+
- h)* *major issues remaining for resolution and draft agenda of future approved meeting, if any;*
|
| 617 |
+
- i)* response to question on knowledge of intellectual property rights issues, including patents, copyright for software or text, marks;
|
| 618 |
+
- j)* list of attendees at all meetings held since last progress report.
|
| 619 |
+
|
| 620 |
+
A meeting report shall clearly indicate in its title the Question number, meeting venue and meeting date. In general, the title shall be of the form "Rapporteur Report Qx/x".
|
| 621 |
+
|
| 622 |
+
Any draft Recommendations produced shall be presented as separate TDs (one document per Recommendation). The title of the TD shall be of the form "Draft new Recommendation ITU-T X.x: abc", where "abc" stands for the title of the draft Recommendation, or "Draft revised Recommendation ITU-T X.x: abc", or "Draft Amendment 1 to Recommendation ITU-T X.x: abc", etc.
|
| 623 |
+
|
| 624 |
+
A progress report shall not be used as a vehicle to violate the rules concerning the submission of contributions that are inappropriate to the assigned study task.
|
| 625 |
+
|
| 626 |
+
NOTE – The progress report may make reference to the meeting reports (see clause 2.3.3.12) in order to avoid duplication of information.
|
| 627 |
+
|
| 628 |
+
## **Bibliography**
|
| 629 |
+
|
| 630 |
+
- [b-ITU-T A.13] Recommendation ITU-T A.13 (2019), *Non-normative ITU-T publications, including Supplements to ITU-T Recommendations*.
|
| 631 |
+
- [b-ITU-T A.sup5] ITU-T A-series Recommendations – Supplement 5 (2016), *Guidelines for collaboration and exchange of information with other organizations*.
|
| 632 |
+
|
| 633 |
+
|
| 634 |
+
|
| 635 |
+
|
| 636 |
+
|
| 637 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 638 |
+
|
| 639 |
+
### **Series A Organization of the work of ITU-T**
|
| 640 |
+
|
| 641 |
+
| | |
|
| 642 |
+
|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 643 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 644 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 645 |
+
| Series F | Non-telephone telecommunication services |
|
| 646 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 647 |
+
| Series H | Audiovisual and multimedia systems |
|
| 648 |
+
| Series I | Integrated services digital network |
|
| 649 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 650 |
+
| Series K | Protection against interference |
|
| 651 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 652 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 653 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 654 |
+
| Series O | Specifications of measuring equipment |
|
| 655 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 656 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 657 |
+
| Series R | Telegraph transmission |
|
| 658 |
+
| Series S | Telegraph services terminal equipment |
|
| 659 |
+
| Series T | Terminals for telematic services |
|
| 660 |
+
| Series U | Telegraph switching |
|
| 661 |
+
| Series V | Data communication over the telephone network |
|
| 662 |
+
| Series X | Data networks, open system communications and security |
|
| 663 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 664 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.11-201211-I_PDF-E/62e1187eade1baedc296526bd9896580_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.11-201211-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,221 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
# A.11
|
| 12 |
+
|
| 13 |
+
(11/2012)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
# --- Publication of ITU-T Recommendations and World Telecommunication Standardization Assembly proceedings
|
| 18 |
+
|
| 19 |
+
Recommendation ITU-T A.11
|
| 20 |
+
|
| 21 |
+
|
| 22 |
+
|
| 23 |
+
ITU logo: a globe with a red lightning bolt and the text 'ITU International Telecommunication Union'
|
| 24 |
+
|
| 25 |
+
|
| 26 |
+
|
| 27 |
+
# **Recommendation ITU-T A.11**
|
| 28 |
+
|
| 29 |
+
# **Publication of ITU-T Recommendations and World Telecommunication Standardization Assembly proceedings**
|
| 30 |
+
|
| 31 |
+
# **Summary**
|
| 32 |
+
|
| 33 |
+
This Recommendation provides information on the procedures to be followed for publication of ITU-T Recommendations and the results of WTSAs.
|
| 34 |
+
|
| 35 |
+
## **History**
|
| 36 |
+
|
| 37 |
+
| Edition | Recommendation | Approval | Study Group |
|
| 38 |
+
|---------|----------------|------------|-------------|
|
| 39 |
+
| 1.0 | ITU-T A.11 | 2000-10-06 | Assembly |
|
| 40 |
+
| 2.0 | ITU-T A.11 | 2004-10-14 | Assembly |
|
| 41 |
+
| 3.0 | ITU-T A.11 | 2008-10-30 | Assembly |
|
| 42 |
+
| 4.0 | ITU-T A.11 | 2012-11-30 | Assembly |
|
| 43 |
+
|
| 44 |
+
# FOREWORD
|
| 45 |
+
|
| 46 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 47 |
+
|
| 48 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 49 |
+
|
| 50 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 51 |
+
|
| 52 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 53 |
+
|
| 54 |
+
## NOTE
|
| 55 |
+
|
| 56 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 57 |
+
|
| 58 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 59 |
+
|
| 60 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 61 |
+
|
| 62 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 63 |
+
|
| 64 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 65 |
+
|
| 66 |
+
© ITU 2013
|
| 67 |
+
|
| 68 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 69 |
+
|
| 70 |
+
## Table of Contents
|
| 71 |
+
|
| 72 |
+
| | <b>Page</b> |
|
| 73 |
+
|--------------------------------------------------------------------|-------------|
|
| 74 |
+
| 1 Introduction ..... | 1 |
|
| 75 |
+
| 2 Publication of Recommendations ..... | 1 |
|
| 76 |
+
| 3 Publication of WTSA proceedings ..... | 1 |
|
| 77 |
+
| 4 Associated activities ..... | 2 |
|
| 78 |
+
| 5 Relation with the Council ..... | 2 |
|
| 79 |
+
| Annex A – Guidelines on publication of ITU-T Recommendations ..... | 3 |
|
| 80 |
+
|
| 81 |
+
|
| 82 |
+
|
| 83 |
+
## **Recommendation ITU-T A.11**
|
| 84 |
+
|
| 85 |
+
## **Publication of ITU-T Recommendations and World Telecommunication Standardization Assembly proceedings**
|
| 86 |
+
|
| 87 |
+
*(2000; 2004; 2008; 2012)*
|
| 88 |
+
|
| 89 |
+
# **1 Introduction**
|
| 90 |
+
|
| 91 |
+
Under No. 98 of the ITU Convention, the Secretary-General is charged with the task of publishing Recommendations, and Recommendation ITU-T A.12 of the ITU Telecommunication Standardization Sector (ITU-T) sets out the identification and layout of ITU-T Recommendations. In addition to the publication of ITU-T Recommendations, the procedures for publishing the proceedings of the World Telecommunication Standardization Assembly (WTSA) are specified below.
|
| 92 |
+
|
| 93 |
+
It should be noted that although the designation "CCITT" has not been applied to new publications for some time, references to CCITT and ITU-T Recommendations are contained in numerous legal documents throughout the world.
|
| 94 |
+
|
| 95 |
+
# **2 Publication of Recommendations**
|
| 96 |
+
|
| 97 |
+
**2.1** Each new and revised Recommendation should be made available to the public as soon as practicable after it has been approved, and in each language as soon as it is available (see Annex A).
|
| 98 |
+
|
| 99 |
+
**2.2** Each new and revised Recommendation should be added to a directly accessible database of ITU-T Recommendations.
|
| 100 |
+
|
| 101 |
+
**2.3** The collection of approved Recommendations should also be published on an appropriate distribution medium.
|
| 102 |
+
|
| 103 |
+
**2.4** Adequate indexing should be provided on all media.
|
| 104 |
+
|
| 105 |
+
**2.5** The current status of each Recommendation in the complete range of Recommendations, including those approved by CCITT prior to 1993, should be accessible online.
|
| 106 |
+
|
| 107 |
+
# **3 Publication of WTSA proceedings**
|
| 108 |
+
|
| 109 |
+
**3.1** To provide a record of the proceedings of each assembly, an ITU-T Book should be published with the contents restricted to the following in principle:
|
| 110 |
+
|
| 111 |
+
- Resolutions and Opinions adopted by the assembly;
|
| 112 |
+
- Recommendations on the organization of the work of ITU-T (A-series);
|
| 113 |
+
- a list of the study groups, the advisory group and any other groups established or maintained by the assembly, with their titles and general areas of work;
|
| 114 |
+
- titles of the Questions (continuing or newly approved for study) and their allocation;
|
| 115 |
+
- reports of the committees of the assembly.
|
| 116 |
+
|
| 117 |
+
NOTE – The list of participants and list of documents of the assembly may be provided in the book, or pointers may be provided as to where the online list of participants and the online list of documents of the assembly may be found.
|
| 118 |
+
|
| 119 |
+
**3.2** Resolutions and ITU-T A-series Recommendations should also be published individually in electronic form.
|
| 120 |
+
|
| 121 |
+
**3.3** The colour of the cover of the ITU-T Book recording the results of WTSA will rotate successively through the colours of previous books in their chronological order, i.e. white, green, orange, yellow, red and blue.
|
| 122 |
+
|
| 123 |
+
# **4 Associated activities**
|
| 124 |
+
|
| 125 |
+
**4.1** The Director of the Telecommunication Standardization Bureau (TSB) should observe the annexed guidelines (see Annex A) when managing the continuing process of publishing Recommendations during the upcoming study period.
|
| 126 |
+
|
| 127 |
+
**4.2** The Director of TSB should report to the next WTSA and to the intervening meetings of TSAG on any difficulties encountered in the timely publication of texts, with proposals for remedial action.
|
| 128 |
+
|
| 129 |
+
# **5 Relation with the Council**
|
| 130 |
+
|
| 131 |
+
The Director of TSB should invite the Council to consider what adjustments, if any, may be needed to the ITU policy on publication, pricing, etc., in order to facilitate the rapid, wide and effective dissemination of ITU-T Recommendations.
|
| 132 |
+
|
| 133 |
+
# **Annex A**
|
| 134 |
+
|
| 135 |
+
## **Guidelines on publication of ITU-T Recommendations**
|
| 136 |
+
|
| 137 |
+
(This annex forms an integral part of this Recommendation.)
|
| 138 |
+
|
| 139 |
+
**A.1** The following guidelines have been drawn up to assist in the timely publication of the approved ITU-T Recommendations. These guidelines should apply to those ITU services involved in the publication and distribution of Recommendations, and (to the extent relevant) to other organizations permitted by ITU to publish and distribute Recommendations under conditions and arrangements established with ITU.
|
| 140 |
+
|
| 141 |
+
**A.2** From the users' viewpoint, the main principles that need to be applied are:
|
| 142 |
+
|
| 143 |
+
- a)* the maximum feasible use of electronic publishing of Recommendations through direct online access to databases that are updated as soon as possible after approval of the Recommendations and by periodic publication on an appropriate distribution medium;
|
| 144 |
+
- b)* unambiguous labelling of Recommendations to identify successive versions (see Recommendation ITU-T A.12);
|
| 145 |
+
- c)* convenient (e.g. online or on a distribution medium) access to appropriate guidance and definitive information on prices, availability and current status of Recommendations;
|
| 146 |
+
- d)* simple-to-use indexes and search facilities to locate specific subjects without necessarily knowing the titles or understanding the general structure and letter series used to designate ITU-T Recommendations.
|
| 147 |
+
|
| 148 |
+
**A.3** Immediately after the conditions for its approval have been met, a new or revised Recommendation should be made available to the public, in accordance with the conditions established by ITU.
|
| 149 |
+
|
| 150 |
+
Recommendations should be made available<sup>1</sup> in appropriate formats, such as:
|
| 151 |
+
|
| 152 |
+
- online access – as soon as practicable;
|
| 153 |
+
- DVD – periodically (e.g. quarterly).
|
| 154 |
+
|
| 155 |
+
Minor modifications may be covered by publishing amendments or corrigenda rather than reissuing the complete Recommendation.
|
| 156 |
+
|
| 157 |
+
**A.4** The current status of the complete range of Recommendations must be accessible on a database at any time.
|
| 158 |
+
|
| 159 |
+
**A.5** Adequate indexing and search facilities should be provided.
|
| 160 |
+
|
| 161 |
+
**A.6** For research and reference purposes, ITU should maintain permanently in an archive an official copy of all Recommendations that are or have been valid.
|
| 162 |
+
|
| 163 |
+
**A.7** The generally accessible online database of Recommendations should contain versions of Recommendations currently in force and versions previously in force since the 1988 Blue Book.
|
| 164 |
+
|
| 165 |
+
**A.8** ITU copyright should be strictly enforced on all formats of ITU-T Recommendations.
|
| 166 |
+
|
| 167 |
+
---
|
| 168 |
+
|
| 169 |
+
<sup>1</sup> Paper copies should be made available as quickly as possible at the request of a Member State, Sector Member or Associate not possessing electronic facilities, by which they can access publications of the Union
|
| 170 |
+
|
| 171 |
+
|
| 172 |
+
|
| 173 |
+
|
| 174 |
+
|
| 175 |
+
### **SERIES OF ITU-T RECOMMENDATIONS**
|
| 176 |
+
|
| 177 |
+
#### **Series A Organization of the work of ITU-T**
|
| 178 |
+
|
| 179 |
+
Series D General tariff principles
|
| 180 |
+
|
| 181 |
+
Series E Overall network operation, telephone service, service operation and human factors
|
| 182 |
+
|
| 183 |
+
Series F Non-telephone telecommunication services
|
| 184 |
+
|
| 185 |
+
Series G Transmission systems and media, digital systems and networks
|
| 186 |
+
|
| 187 |
+
Series H Audiovisual and multimedia systems
|
| 188 |
+
|
| 189 |
+
Series I Integrated services digital network
|
| 190 |
+
|
| 191 |
+
Series J Cable networks and transmission of television, sound programme and other multimedia signals
|
| 192 |
+
|
| 193 |
+
Series K Protection against interference
|
| 194 |
+
|
| 195 |
+
Series L Construction, installation and protection of cables and other elements of outside plant
|
| 196 |
+
|
| 197 |
+
Series M Telecommunication management, including TMN and network maintenance
|
| 198 |
+
|
| 199 |
+
Series N Maintenance: international sound programme and television transmission circuits
|
| 200 |
+
|
| 201 |
+
Series O Specifications of measuring equipment
|
| 202 |
+
|
| 203 |
+
Series P Terminals and subjective and objective assessment methods
|
| 204 |
+
|
| 205 |
+
Series Q Switching and signalling
|
| 206 |
+
|
| 207 |
+
Series R Telegraph transmission
|
| 208 |
+
|
| 209 |
+
Series S Telegraph services terminal equipment
|
| 210 |
+
|
| 211 |
+
Series T Terminals for telematic services
|
| 212 |
+
|
| 213 |
+
Series U Telegraph switching
|
| 214 |
+
|
| 215 |
+
Series V Data communication over the telephone network
|
| 216 |
+
|
| 217 |
+
Series X Data networks, open system communications and security
|
| 218 |
+
|
| 219 |
+
Series Y Global information infrastructure, Internet protocol aspects and next-generation networks
|
| 220 |
+
|
| 221 |
+
Series Z Languages and general software aspects for telecommunication systems
|
marked/A/T-REC-A.12-201611-I_PDF-E/3b014ddc8eee22a3a4386e61414e2067_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.12-201611-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,159 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
## A.12
|
| 12 |
+
|
| 13 |
+
(11/2016)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
---
|
| 18 |
+
|
| 19 |
+
# Identification and layout of ITU-T Recommendations
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T A.12
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
## Recommendation ITU-T A.12
|
| 26 |
+
|
| 27 |
+
# Identification and layout of ITU-T Recommendations
|
| 28 |
+
|
| 29 |
+
## Summary
|
| 30 |
+
|
| 31 |
+
Recommendation ITU-T A.12 provides information on the means on assigning the letter series designations for ITU-T Recommendations.
|
| 32 |
+
|
| 33 |
+
## History
|
| 34 |
+
|
| 35 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID* |
|
| 36 |
+
|---------|-------------------------|------------|-------------|---------------------------------------------------------------------------|
|
| 37 |
+
| 1.0 | ITU-T A.12 | 2000-10-06 | TSAG | <a href="http://handle.itu.int/11.1002/1000/5279">11.1002/1000/5279</a> |
|
| 38 |
+
| 2.0 | ITU-T A.12 | 2004-10-14 | TSAG | <a href="http://handle.itu.int/11.1002/1000/7422">11.1002/1000/7422</a> |
|
| 39 |
+
| 3.0 | ITU-T A.12 | 2008-10-30 | TSAG | <a href="http://handle.itu.int/11.1002/1000/9643">11.1002/1000/9643</a> |
|
| 40 |
+
| 3.1 | ITU-T A.12 (2008) Cor.1 | 2015-06-05 | TSAG | <a href="http://handle.itu.int/11.1002/1000/12526">11.1002/1000/12526</a> |
|
| 41 |
+
| 3.2 | ITU-T A.12 (2008) Cor.2 | 2016-02-05 | TSAG | <a href="http://handle.itu.int/11.1002/1000/12786">11.1002/1000/12786</a> |
|
| 42 |
+
| 4.0 | ITU-T A.12 | 2016-11-02 | TSAG | <a href="http://handle.itu.int/11.1002/1000/13164">11.1002/1000/13164</a> |
|
| 43 |
+
|
| 44 |
+
## Keywords
|
| 45 |
+
|
| 46 |
+
Identification, layout, letter series designation.
|
| 47 |
+
|
| 48 |
+
---
|
| 49 |
+
|
| 50 |
+
\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
|
| 51 |
+
|
| 52 |
+
## FOREWORD
|
| 53 |
+
|
| 54 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 55 |
+
|
| 56 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 57 |
+
|
| 58 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 59 |
+
|
| 60 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 61 |
+
|
| 62 |
+
## NOTE
|
| 63 |
+
|
| 64 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 65 |
+
|
| 66 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 67 |
+
|
| 68 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 69 |
+
|
| 70 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 71 |
+
|
| 72 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 73 |
+
|
| 74 |
+
© ITU 2017
|
| 75 |
+
|
| 76 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 77 |
+
|
| 78 |
+
## Recommendation ITU-T A.12
|
| 79 |
+
|
| 80 |
+
# Identification and layout of ITU-T Recommendations
|
| 81 |
+
|
| 82 |
+
## 1 Scope
|
| 83 |
+
|
| 84 |
+
The Telecommunication Standardization Advisory Group (TSAG) periodically reviews the methods of identifying and laying out Recommendations as well as the Author's Guide for drafting ITU-T Recommendations, prepared and updated by the Telecommunication Standardization Bureau (TSB), providing thus detailed guidelines on format and style. This Recommendation provides principles that are applied in identifying and laying out Recommendations.
|
| 85 |
+
|
| 86 |
+
## 2 Identification and layout of Recommendations
|
| 87 |
+
|
| 88 |
+
**2.1** All Recommendations of the ITU Telecommunication Standardization Sector (ITU-T) shall be numbered. The number of each Recommendation shall have a letter prefix referring to the series as well as a number identifying the particular subject in that series. The numbering shall be done in a manner that permits clear, unequivocal identification and facilitates electronic storage of information concerning the Recommendation. The Recommendation number shall be associated on the cover with the date of approval in the format YYYY. The month may be added if required for uniqueness.
|
| 89 |
+
|
| 90 |
+
**2.2** The scope of the series identified by the letter shall be as follows:
|
| 91 |
+
|
| 92 |
+
- A Organization of the work of ITU-T
|
| 93 |
+
- B *Not allocated*
|
| 94 |
+
- C *Not allocated*
|
| 95 |
+
- D Tariff and accounting principles and international telecommunication/ICT economic and policy issues
|
| 96 |
+
- E Overall network operation, telephone service, service operation and human factors
|
| 97 |
+
- F Non-telephone telecommunication services
|
| 98 |
+
- G Transmission systems and media, digital systems and networks
|
| 99 |
+
- H Audiovisual and multimedia systems
|
| 100 |
+
- I Integrated services digital network
|
| 101 |
+
- J Cable networks and transmission of television, sound programme and other multimedia signals
|
| 102 |
+
- K Protection against interference
|
| 103 |
+
- L Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant
|
| 104 |
+
- M Telecommunication management, including TMN and network maintenance
|
| 105 |
+
- N Maintenance: international sound-programme and television-transmission circuits
|
| 106 |
+
- O Specifications of measuring equipment
|
| 107 |
+
- P Telephone transmission quality, telephone installations, local line networks
|
| 108 |
+
- Q Switching and signalling, and associated measurements and tests
|
| 109 |
+
- R Telegraph transmission
|
| 110 |
+
- S Telegraph services terminal equipment
|
| 111 |
+
- T Terminals for telematic services
|
| 112 |
+
- U Telegraph switching
|
| 113 |
+
|
| 114 |
+
- V Data communication over the telephone network
|
| 115 |
+
- W *Not allocated*
|
| 116 |
+
- X Data networks, open system communications and security
|
| 117 |
+
- Y Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities
|
| 118 |
+
- Z Languages and general software aspects for telecommunication systems
|
| 119 |
+
|
| 120 |
+
**2.3** Recommendations in each series shall be classified in sections, according to subject.
|
| 121 |
+
|
| 122 |
+
**2.4** The title of each Recommendation should be concise (preferably no more than one line) but unique, meaningful and unambiguous. The details identifying the precise intent and coverage should be contained in the text where possible (e.g., under "Scope" clause).
|
| 123 |
+
|
| 124 |
+
**2.5** The date of formal approval of the Recommendation, the study group(s) responsible for its approval and a record of revisions shall be clearly indicated, together with the approval process applied. In accordance with the ITU Convention, the status of Recommendations approved is the same for both the alternative approval process (AAP) and traditional approval process (TAP) methods of approval.
|
| 125 |
+
|
| 126 |
+
**2.6** The author of a new or revised Recommendation shall provide, in front of the main body of the Recommendation, a summary and a set of keywords as outlined in the "Author's Guide for drafting ITU-T Recommendations". The author may also provide other up-front elements, such as background information, as provided for in the Author's Guide.
|
| 127 |
+
|
| 128 |
+
**2.7** The "Author's Guide for drafting ITU-T Recommendations" should be applied in drafting new Recommendations and, wherever practicable, in revising existing Recommendations.
|
| 129 |
+
|
| 130 |
+
|
| 131 |
+
|
| 132 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 133 |
+
|
| 134 |
+
## **Series A Organization of the work of ITU-T**
|
| 135 |
+
|
| 136 |
+
| | |
|
| 137 |
+
|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 138 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 139 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 140 |
+
| Series F | Non-telephone telecommunication services |
|
| 141 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 142 |
+
| Series H | Audiovisual and multimedia systems |
|
| 143 |
+
| Series I | Integrated services digital network |
|
| 144 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 145 |
+
| Series K | Protection against interference |
|
| 146 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 147 |
+
| Series M | Telecommunication management, including telecommunication network management and network maintenance |
|
| 148 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 149 |
+
| Series O | Specifications of measuring equipment |
|
| 150 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 151 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 152 |
+
| Series R | Telegraph transmission |
|
| 153 |
+
| Series S | Telegraph services terminal equipment |
|
| 154 |
+
| Series T | Terminals for telematic services |
|
| 155 |
+
| Series U | Telegraph switching |
|
| 156 |
+
| Series V | Data communication over the telephone network |
|
| 157 |
+
| Series X | Data networks, open system communications and security |
|
| 158 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 159 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.13-201909-I_PDF-E/daefb8d8ae0a06b249462b662fdab82b_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.13-201909-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,245 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
# A.13
|
| 12 |
+
|
| 13 |
+
(09/2019)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
---
|
| 18 |
+
|
| 19 |
+
# **Non-normative ITU-T publications, including Supplements to ITU-T Recommendations**
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T A.13
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
# Recommendation ITU-T A.13
|
| 26 |
+
|
| 27 |
+
# Non-normative ITU-T publications, including Supplements to ITU-T Recommendations
|
| 28 |
+
|
| 29 |
+
## Summary
|
| 30 |
+
|
| 31 |
+
Recommendation ITU-T A.13 describes the process used by ITU-T study groups and the Telecommunication Standardization Advisory Group (TSAG) to develop and agree to publication of informative (non-Recommendation) texts published by ITU-T. The documents using this process include Supplements to ITU-T Recommendations.
|
| 32 |
+
|
| 33 |
+
## History
|
| 34 |
+
|
| 35 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID* |
|
| 36 |
+
|---------|--------------------------|------------|-------------|---------------------------------------------------------------------------|
|
| 37 |
+
| 1.0 | ITU-T A.13 | 2000-10-06 | TSAG | <a href="http://handle.itu.int/11.1002/1000/5280">11.1002/1000/5280</a> |
|
| 38 |
+
| 1.1 | ITU-T A.13 (2000) Amd. 1 | 2007-12-07 | TSAG | <a href="http://handle.itu.int/11.1002/1000/9148">11.1002/1000/9148</a> |
|
| 39 |
+
| 2.0 | ITU-T A.13 | 2019-09-27 | TSAG | <a href="http://handle.itu.int/11.1002/1000/13853">11.1002/1000/13853</a> |
|
| 40 |
+
|
| 41 |
+
---
|
| 42 |
+
|
| 43 |
+
\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
|
| 44 |
+
|
| 45 |
+
## FOREWORD
|
| 46 |
+
|
| 47 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 48 |
+
|
| 49 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 50 |
+
|
| 51 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 52 |
+
|
| 53 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 54 |
+
|
| 55 |
+
## NOTE
|
| 56 |
+
|
| 57 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 58 |
+
|
| 59 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 60 |
+
|
| 61 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 62 |
+
|
| 63 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 64 |
+
|
| 65 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 66 |
+
|
| 67 |
+
© ITU 2019
|
| 68 |
+
|
| 69 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 70 |
+
|
| 71 |
+
## Table of Contents
|
| 72 |
+
|
| 73 |
+
| | <b>Page</b> |
|
| 74 |
+
|----------------------------------------------------------------------------------------------------|-------------|
|
| 75 |
+
| 1 Introduction..... | 1 |
|
| 76 |
+
| 2 References..... | 1 |
|
| 77 |
+
| 3 Definitions ..... | 1 |
|
| 78 |
+
| 4 Abbreviations and acronyms ..... | 2 |
|
| 79 |
+
| 5 Conventions ..... | 2 |
|
| 80 |
+
| 6 Non-normative texts ..... | 2 |
|
| 81 |
+
| 7 Additional considerations specific to Supplements..... | 3 |
|
| 82 |
+
| 8 Work programme..... | 3 |
|
| 83 |
+
| Annex A – Template to describe a proposed new non-normative document in the work<br>programme..... | 4 |
|
| 84 |
+
| Bibliography..... | 5 |
|
| 85 |
+
|
| 86 |
+
|
| 87 |
+
|
| 88 |
+
# Recommendation ITU-T A.13
|
| 89 |
+
|
| 90 |
+
## Non-normative ITU-T publications, including Supplements to ITU-T Recommendations
|
| 91 |
+
|
| 92 |
+
# 1 Introduction
|
| 93 |
+
|
| 94 |
+
In the course of its studies, each study group deals with contributions and reports, which are distributed to those organizations that have registered for participation in the study group's work, and Recommendations resulting from those studies reach a much wider audience. Normally, any information that is considered as merely illustrative or supplementary to a Recommendation should be included as a (non-integral) appendix to that Recommendation, where it is useful to the wider audience. However, there are instances where separate publication of such information is warranted. This information is not part of demonstrating voluntary compliance to any ITU-T Recommendation. Such information can be published in the form of Supplements to the Recommendations or other document types published by ITU-T.
|
| 95 |
+
|
| 96 |
+
# 2 References
|
| 97 |
+
|
| 98 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 99 |
+
|
| 100 |
+
None.
|
| 101 |
+
|
| 102 |
+
# 3 Definitions
|
| 103 |
+
|
| 104 |
+
## 3.1 Terms defined elsewhere
|
| 105 |
+
|
| 106 |
+
This Recommendation uses the following terms defined elsewhere:
|
| 107 |
+
|
| 108 |
+
**3.1.1 handbook:** [b-WTSA Res. 1]: A text which provides a statement of the current knowledge, the present position of studies or good operating or technical practice, in certain aspects of telecommunications, which should be addressed to a telecommunication engineer, system planner or operating official who plans, designs or uses telecommunication services or systems, paying particular attention to the requirements of developing countries.
|
| 109 |
+
|
| 110 |
+
NOTE – It should be self-contained, and require no familiarity with other ITU-T texts or procedures.
|
| 111 |
+
|
| 112 |
+
**3.1.2 work item:** [b-ITU-T A.1]: An assigned piece of work, which is identifiable with a Question and which has specific or general objectives, which will result in a product, usually a Recommendation, for publication by ITU-T.
|
| 113 |
+
|
| 114 |
+
**3.1.3 work programme:** [b-ITU-T A.1]: A list of work items that are owned by a study group.
|
| 115 |
+
|
| 116 |
+
## 3.2 Terms defined in this Recommendation
|
| 117 |
+
|
| 118 |
+
This Recommendation defines the following terms:
|
| 119 |
+
|
| 120 |
+
**3.2.1 implementer's guide:** An informative (non-normative) document which records all identified defects (e.g., typographical errors, editorial errors, ambiguities, omissions or inconsistencies, and technical errors) associated with a Recommendation or a set of Recommendations and their status of correction, from their identification to final resolution.
|
| 121 |
+
|
| 122 |
+
NOTE – An implementer's guide is issued by ITU-T following agreement by a study group, or following agreement by a working party with the concurrence of the study group chairman. Typically, defect corrections are first collected in an implementer's guide and, at a time deemed appropriate by the study group, they are used to produce a corrigendum or are included as revisions to a Recommendation.
|
| 123 |
+
|
| 124 |
+
**3.2.2 Supplement:** An informative (non-normative) document which contains material which is supplementary to and associated with the subject matter of one or more Recommendations but which is not essential to their completeness or understanding and implementation.
|
| 125 |
+
|
| 126 |
+
**3.2.3 technical paper or technical report:** An informative (non-normative) publication containing technical information, prepared by a study group on a given subject within its mandate.
|
| 127 |
+
|
| 128 |
+
# 4 Abbreviations and acronyms
|
| 129 |
+
|
| 130 |
+
This Recommendation uses the following abbreviations and acronyms:
|
| 131 |
+
|
| 132 |
+
TSAG Telecommunication Standardization Advisory Group
|
| 133 |
+
|
| 134 |
+
WTSA World Telecommunication Standardization Assembly
|
| 135 |
+
|
| 136 |
+
# 5 Conventions
|
| 137 |
+
|
| 138 |
+
None.
|
| 139 |
+
|
| 140 |
+
# 6 Non-normative texts
|
| 141 |
+
|
| 142 |
+
The following general principles shall be applied by study groups for the development, approval and revision of non-normative ITU-T publications. These include implementer's guides, technical papers, technical reports, handbooks, Supplements to ITU-T Recommendations and appendices to Recommendations agreed separately from the base text of the Recommendation.
|
| 143 |
+
|
| 144 |
+
NOTE – Text of an appendix approved together with its base Recommendation will follow the approval process (TAP according to section 9 of [b-WTSA Res. 1], or AAP according to [b-ITU-T A.8]) of the base Recommendation.
|
| 145 |
+
|
| 146 |
+
Texts other than Recommendations (often referred to as "non-normative ITU-T publications") are informative or supplementary materials in an area of study relevant to an ITU-T study group.
|
| 147 |
+
|
| 148 |
+
**6.1** Before proposing any new or revised text as a non-normative publication, a study group or TSAG should ensure, in consultation with the Director, that:
|
| 149 |
+
|
| 150 |
+
- i) the subject matter is within its mandate;
|
| 151 |
+
- ii) there is a sufficient need for the information on a long-term basis;
|
| 152 |
+
- iii) the text cannot be reasonably adapted for inclusion in an existing or new Recommendation (e.g., as an appendix);
|
| 153 |
+
- iv) the text contains material which is not essential to the completeness or understanding and implementation of any ITU-T Recommendation;
|
| 154 |
+
- v) the text is sufficiently mature and it follows, as far as possible, the format of [b-Author's Guide] but with language adjusted due to the informative rather than normative nature of the publication.
|
| 155 |
+
|
| 156 |
+
**6.2** Non-normative documents require agreement by the study group or TSAG (in the case of a document developed by TSAG), but they do not require approval according to [b-WTSA Res. 1] or [b-ITU-T A.8] procedures.
|
| 157 |
+
|
| 158 |
+
**6.3** Non-normative publications are only informative and are therefore not considered to be an integral part of any Recommendation(s). The following note shall be added after the foreword of non-normative publications: "NOTE – This is an informative ITU-T publication. Mandatory provisions,
|
| 159 |
+
|
| 160 |
+
such as those found in ITU-T Recommendations, are outside the scope of this publication. This publication should only be referenced bibliographically in ITU-T Recommendations".
|
| 161 |
+
|
| 162 |
+
**6.4** Since non-normative publications are informative material, no onus is implied on the issuing study group to update or to reissue them. However, should (bibliographic) reference to a non-normative publication be made in a Recommendation, the study group should review the applicability both of that reference and the non-normative publication at least once every four years, and take any necessary action.
|
| 163 |
+
|
| 164 |
+
**6.5** Non-normative publications (other than Supplements and implementer's guides) are not included in databases along with ITU-T Recommendations but are published on the web site of the concerned Study Group or TSAG.
|
| 165 |
+
|
| 166 |
+
**6.6** Non normative publications may be deleted after consultation with the concerned study group if not reviewed or updated after a period of eight years.
|
| 167 |
+
|
| 168 |
+
**6.7** Non-normative publications (other than Supplements) are not edited by TSB before publication. They are available for free in electronic format and are not printed in paper format.
|
| 169 |
+
|
| 170 |
+
# **7 Additional considerations specific to Supplements**
|
| 171 |
+
|
| 172 |
+
In addition to the general principles given in clause 6, which apply to all non-normative publications, the following additional principles shall be applied by study groups for the development, agreement, identification and revision of Supplements:
|
| 173 |
+
|
| 174 |
+
**7.1** A working party may agree to a Supplement if the study group that set up the working party has previously identified this Supplement and has authorized the working party to do so at the previous study group meeting provided that such Supplement is not related or linked to any Recommendation having policy or regulatory implications in accordance with Nos. 246D to 246H of the ITU Convention.
|
| 175 |
+
|
| 176 |
+
**7.2** Each Supplement should be unambiguously identified by the series letter to which it is associated followed by a sequential number unique within that series. Supplements may apply to a series of Recommendations; they need not be attached to a particular single Recommendation.
|
| 177 |
+
|
| 178 |
+
**7.3** Supplements should be included in databases along with ITU-T Recommendations.
|
| 179 |
+
|
| 180 |
+
**7.4** To the extent practicable, Supplements will be published in a similar fashion to Recommendations, but with a lower priority, and taking into account market needs.
|
| 181 |
+
|
| 182 |
+
# **8 Work programme**
|
| 183 |
+
|
| 184 |
+
**8.1** The decision to add a new work item for a non-normative ITU-T publication (see clause 6) to the work programme of a study group (or TSAG) should be documented in the report of the meeting using the template in Annex A. Note that this may not be necessary to document the continuation of existing work (e.g., a revision of an existing non-normative document).
|
| 185 |
+
|
| 186 |
+
**8.2** The target date should normally be less than two years after the study group meeting when the new work item is added to the work programme. A work item may be considered for discontinuation from the work programme if it has not given rise to any contribution in the time interval of the previous two study group meetings.
|
| 187 |
+
|
| 188 |
+
## Annex A
|
| 189 |
+
|
| 190 |
+
## Template to describe a proposed new non-normative document in the work programme
|
| 191 |
+
|
| 192 |
+
(This annex forms an integral part of this Recommendation.)
|
| 193 |
+
|
| 194 |
+
| | | | | |
|
| 195 |
+
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------|
|
| 196 |
+
| <b>Question:</b> | / | <b>Proposed new ITU-T:</b><br><input type="checkbox"/> Supplement<br><input type="checkbox"/> Implementer's guide<br><input type="checkbox"/> Technical paper<br><input type="checkbox"/> Technical report<br><input type="checkbox"/> Handbook<br><input type="checkbox"/> Other: _____ | <Meeting date> | |
|
| 197 |
+
| <b>Reference and title:</b> | <X.xxx> "Title" | | | |
|
| 198 |
+
| <b>Base text:</b> | <C nnn> or <TD nnnn> | | <b>Target date:</b> | <Month-Year> |
|
| 199 |
+
| <b>Editor(s):</b> | <Name, membership, e-mail address> | | <b>Approval process:</b> | Agreement |
|
| 200 |
+
| <b>Purpose and scope</b> (defines what issue this non-normative document will address, thus permitting readers to judge its usefulness for their work; also defines the intent or objective of the non-normative document and the aspects covered, thereby indicating the limits of its applicability): | | | | |
|
| 201 |
+
| <b>Summary</b> (provides a brief overview of the proposal): | | | | |
|
| 202 |
+
| <b>Relations to ITU-T Recommendations or other documents</b> (approved or under development): | | | | |
|
| 203 |
+
| <b>Liaisons with other study groups or with other standards bodies:</b> | | | | |
|
| 204 |
+
| <b>Supporting members that are committing to contributing actively to the work item:</b><br><Member States, Sector Members, Associates, Academia> | | | | |
|
| 205 |
+
|
| 206 |
+
# Bibliography
|
| 207 |
+
|
| 208 |
+
- [b-ITU-T A.1] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector*.
|
| 209 |
+
- [b-ITU-T A.8] Recommendation ITU-T A.8 (2008), *Alternative approval process for new and revised ITU-T Recommendations*.
|
| 210 |
+
- [b-WTSA Res. 1] WTSA Resolution 1 (rev. Hammamet, 2016), *Rules of procedure of the ITU Telecommunication Standardization Sector*.
|
| 211 |
+
- [b-Author's guide] ITU-T editing guidelines (2016) – *Author's guide for drafting ITU-T Recommendations*.
|
| 212 |
+
<<https://www.itu.int/oth/T0A0F000004>>
|
| 213 |
+
|
| 214 |
+
|
| 215 |
+
|
| 216 |
+
|
| 217 |
+
|
| 218 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 219 |
+
|
| 220 |
+
### **Series A Organization of the work of ITU-T**
|
| 221 |
+
|
| 222 |
+
| | |
|
| 223 |
+
|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 224 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 225 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 226 |
+
| Series F | Non-telephone telecommunication services |
|
| 227 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 228 |
+
| Series H | Audiovisual and multimedia systems |
|
| 229 |
+
| Series I | Integrated services digital network |
|
| 230 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 231 |
+
| Series K | Protection against interference |
|
| 232 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 233 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 234 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 235 |
+
| Series O | Specifications of measuring equipment |
|
| 236 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 237 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 238 |
+
| Series R | Telegraph transmission |
|
| 239 |
+
| Series S | Telegraph services terminal equipment |
|
| 240 |
+
| Series T | Terminals for telematic services |
|
| 241 |
+
| Series U | Telegraph switching |
|
| 242 |
+
| Series V | Data communication over the telephone network |
|
| 243 |
+
| Series X | Data networks, open system communications and security |
|
| 244 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 245 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.18-202505-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.18-202505-I_PDF-E/49ebc29538f9ca089d77e7463c19b10e_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.18-202505-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,312 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Recommendation **ITU-T A.18 (05/2025)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
## **Joint coordination activities: Establishment and working procedures**
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
# Recommendation ITU-T A.18
|
| 14 |
+
|
| 15 |
+
## Joint coordination activities: Establishment and working procedures
|
| 16 |
+
|
| 17 |
+
## Summary
|
| 18 |
+
|
| 19 |
+
A Joint Coordination Activity (JCA) is formed to coordinate activities on topics of relevance across ITU-T study groups. They report their progress either to the Telecommunication Standardization Advisory Group (TSAG) or to a particular study group. JCAs do not write Recommendations. Their working methods are documented in this Recommendation.
|
| 20 |
+
|
| 21 |
+
Edition 2 adds Appendix I, which contains guiding principles and key performance indicators (KPIs) that should be monitored regularly and provided in particular when a review of JCA activities is submitted to its parent group and/or TSAG.
|
| 22 |
+
|
| 23 |
+
JCAs, including the KPIs, should be reviewed regularly.
|
| 24 |
+
|
| 25 |
+
## History \*
|
| 26 |
+
|
| 27 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 28 |
+
|---------|----------------|------------|-------------|--------------------|
|
| 29 |
+
| 1.0 | ITU-T A.18 | 2024-07-29 | 0 | 11.1002/1000/15862 |
|
| 30 |
+
| 2.0 | ITU-T A.18 | 2025-05-30 | 0 | 11.1002/1000/16405 |
|
| 31 |
+
|
| 32 |
+
## Keywords
|
| 33 |
+
|
| 34 |
+
Joint coordination activities.
|
| 35 |
+
|
| 36 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 37 |
+
|
| 38 |
+
## FOREWORD
|
| 39 |
+
|
| 40 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 41 |
+
|
| 42 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 43 |
+
|
| 44 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 45 |
+
|
| 46 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 47 |
+
|
| 48 |
+
## NOTE
|
| 49 |
+
|
| 50 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 51 |
+
|
| 52 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 53 |
+
|
| 54 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 55 |
+
|
| 56 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 57 |
+
|
| 58 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <https://www.itu.int/ITU-T/ipr/>.
|
| 59 |
+
|
| 60 |
+
© ITU 2025
|
| 61 |
+
|
| 62 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 63 |
+
|
| 64 |
+
## Table of Contents
|
| 65 |
+
|
| 66 |
+
| | <b>Page</b> |
|
| 67 |
+
|-----------------------------------------------------------------------|-------------|
|
| 68 |
+
| 1 Scope ..... | 1 |
|
| 69 |
+
| 2 References..... | 1 |
|
| 70 |
+
| 3 Definitions ..... | 1 |
|
| 71 |
+
| 3.1 Terms defined elsewhere..... | 1 |
|
| 72 |
+
| 3.2 Terms defined in this Recommendation..... | 1 |
|
| 73 |
+
| 4 Abbreviations and acronyms ..... | 2 |
|
| 74 |
+
| 5 Conventions ..... | 2 |
|
| 75 |
+
| 6 Establishment and working procedures ..... | 2 |
|
| 76 |
+
| Appendix I – Guiding principles for the periodic review of JCAs ..... | 5 |
|
| 77 |
+
| Bibliography..... | 6 |
|
| 78 |
+
|
| 79 |
+
|
| 80 |
+
|
| 81 |
+
# Recommendation ITU-T A.18
|
| 82 |
+
|
| 83 |
+
## Joint coordination activities: Establishment and working procedures
|
| 84 |
+
|
| 85 |
+
## 1 Scope
|
| 86 |
+
|
| 87 |
+
A joint coordination activity is a tool for management of the work programme of ITU-T when there is a need to address a broad subject covering the area of competence of more than one study group (see also [b-WTSA Res. 22]). A JCA may help to coordinate the planned work effort in terms of subject matter, time-frames for meetings, collocated meetings where necessary and publication goals including, where appropriate, release planning of the resulting Recommendations.
|
| 88 |
+
|
| 89 |
+
The establishment of a JCA aims mainly at improving coordination and planning. The work itself will continue to be conducted by the relevant study groups and the results are subject to the normal approval processes within each study group. A JCA may identify technical and strategic issues within the scope of its coordination role, but will not perform technical studies nor write Recommendations. A JCA may also address coordination of activities with recognized standards development organizations (SDOs) and forums, including periodic discussion of work plans and schedules of deliverables. The study groups take JCA suggestions into consideration as they carry out their work.
|
| 90 |
+
|
| 91 |
+
## 2 References
|
| 92 |
+
|
| 93 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 94 |
+
|
| 95 |
+
- | | |
|
| 96 |
+
|---------------|---------------------------------------------------------------------------------------------------------------------------------------|
|
| 97 |
+
| [WTSA Res. 1] | WTSA Resolution 1 (Rev. Geneva, 2022), <i>Rules of procedure of the ITU Telecommunication Standardization Sector</i> . |
|
| 98 |
+
| [WTSA Res. 2] | WTSA Resolution 2 (Rev. New Delhi, 2024), <i>Scope and mandate of the ITU Telecommunication Standardization Sector study groups</i> . |
|
| 99 |
+
|
| 100 |
+
## 3 Definitions
|
| 101 |
+
|
| 102 |
+
### 3.1 Terms defined elsewhere
|
| 103 |
+
|
| 104 |
+
This Recommendation uses the following terms defined elsewhere:
|
| 105 |
+
|
| 106 |
+
**3.1.1 question** [WTSA Res. 1]: Description of an area of work to be studied, normally leading to the production of one or more new or revised Recommendations and/or new or revised non-normative documents as defined in Recommendation ITU-T A.13.
|
| 107 |
+
|
| 108 |
+
**3.1.2 work item** [b-ITU-T A.1]: An assigned piece of work, which is identifiable with a Question and which has specific or general objectives, which will result in a product, usually a Recommendation, for publication by ITU-T.
|
| 109 |
+
|
| 110 |
+
**3.1.3 work programme** [b-ITU-T A.1]: A list of work items that are owned by a study group.
|
| 111 |
+
|
| 112 |
+
### 3.2 Terms defined in this Recommendation
|
| 113 |
+
|
| 114 |
+
None.
|
| 115 |
+
|
| 116 |
+
## 4 Abbreviations and acronyms
|
| 117 |
+
|
| 118 |
+
This Recommendation uses the following abbreviations and acronyms:
|
| 119 |
+
|
| 120 |
+
JCA Joint Coordination Activity
|
| 121 |
+
|
| 122 |
+
TSAG Telecommunication Standardization Advisory Group
|
| 123 |
+
|
| 124 |
+
## 5 Conventions
|
| 125 |
+
|
| 126 |
+
None.
|
| 127 |
+
|
| 128 |
+
# 6 Establishment and working procedures
|
| 129 |
+
|
| 130 |
+
**6.1** Any group (study group or TSAG) may propose that a JCA be established. The proposal to establish a JCA should first be discussed within the proposing group's management team, then among the relevant study group chairmen/chairs and the TSAG chair. Discussions may be held with external SDOs and forum leaders. Figure 6-1 provides a schematic of the alternatives in proposing and approving the creation of a JCA.
|
| 131 |
+
|
| 132 |
+
**6.1.1** If the study group proposing the establishment of the JCA has been designated as the lead study group by WTSA or TSAG according to Section 2 of [WTSA Res. 1], and if the subject is under their responsibility and mandate as described in [WTSA Res. 2], then the study group may establish a JCA on its own authority. If a study group meeting is pending within the next two months, then an electronic notification<sup>1</sup> proposing the JCA, including the terms of reference (including scope, objectives and anticipated lifetime) and the chair, is published four weeks prior to the study group meeting, giving opportunity for the membership to give their position at the meeting. If this is done at least four weeks prior to the study group meeting, following the resolution of any comments, the JCA may be established by the study group by consensus at its meeting. If a study group meeting is not pending within the next two months, then an electronic notification as above is sent for the membership to give their position by electronic response. If the notification is sent less than four weeks before the study group meeting, no decision is taken at the study group meeting; the decision may be taken four weeks after the notification, excluding the meeting time. If necessary, the proposal is adjusted taking into consideration comments received and made available to the study group electronically for decision with a further four-week interval. If there are no substantive comments, the JCA is considered approved. TSAG will be informed for review, possible comment, and endorsement. TSAG may consider the terms of reference of the JCA in the context of the overall work programme of ITU-T and may provide comments to modify the terms of reference.
|
| 133 |
+
|
| 134 |
+
**6.1.2** Where the lead study group has not yet been designated by WTSA or TSAG for the subject, or where the subject for the JCA is a broad subject potentially falling under the responsibility and mandate of a number of study groups as described in [WTSA Res. 2], then the proposal has to be made available to the membership for consideration.
|
| 135 |
+
|
| 136 |
+
- a) If a TSAG meeting is pending within the next two months, then an electronic notification<sup>2</sup> proposing the JCA, including the terms of reference (with scope, objectives and anticipated lifetime) and the chair, is published at least four weeks prior to the TSAG meeting, giving opportunity for the membership to give their position at the meeting. Following the resolution of any comments, the JCA may be established by TSAG by consensus at its meeting.
|
| 137 |
+
- b) If a TSAG meeting is not pending within the next two months, then an electronic notification as above is sent for the membership to give their position by electronic response.
|
| 138 |
+
|
| 139 |
+
---
|
| 140 |
+
|
| 141 |
+
<sup>1</sup> This electronic notification should be sent to the general e-mail reflector for the proposing study group and should also be a TD to the next meeting of the study group.
|
| 142 |
+
|
| 143 |
+
<sup>2</sup> This electronic notification should be sent to the general e-mail reflector for the potentially involved study groups and TSAG, and should also be a TD to the next meeting of TSAG.
|
| 144 |
+
|
| 145 |
+
- c) If the notification is sent less than four weeks before the TSAG meeting, no decision is taken at the TSAG meeting; the decision may be taken four weeks after the notification, excluding the meeting time. If necessary, the proposal is adjusted taking into consideration comments received and made available to the membership electronically for decision with a further four-week interval. If there are no substantive comments, the JCA is considered approved.
|
| 146 |
+
|
| 147 |
+
The decision includes the designation of the group responsible (a study group or TSAG), the terms of reference (with scope, objectives and anticipated lifetime) and the chair.
|
| 148 |
+
|
| 149 |
+
|
| 150 |
+
|
| 151 |
+
```
|
| 152 |
+
|
| 153 |
+
graph TD
|
| 154 |
+
Start([JCA proposal initiated
|
| 155 |
+
(Clause 6.1)]) --> SGComments[/Comments from
|
| 156 |
+
SG (or TSAG )
|
| 157 |
+
management team/]
|
| 158 |
+
SGComments --> OtherComments[/Comments from
|
| 159 |
+
other SDO or forum
|
| 160 |
+
leaders (if appropriate)/]
|
| 161 |
+
OtherComments --> LeadSG{Lead SG
|
| 162 |
+
and within Res. 2
|
| 163 |
+
mandate?}
|
| 164 |
+
LeadSG -- Yes
|
| 165 |
+
(Clause 6.1.1) --> SGReflector[/Electronic
|
| 166 |
+
notification to
|
| 167 |
+
SG reflector/]
|
| 168 |
+
LeadSG -- No
|
| 169 |
+
(Clause 6.1.2) --> TSAGReflector[/Electronic
|
| 170 |
+
notification to
|
| 171 |
+
TSAG and
|
| 172 |
+
SG reflectors/]
|
| 173 |
+
SGReflector --> SGTime{Time to next
|
| 174 |
+
SG meeting?}
|
| 175 |
+
TSAGReflector --> TSAGTime{Time to next
|
| 176 |
+
TSAG meeting?}
|
| 177 |
+
SGTime -- "> 8 weeks*" --> SGMem1[/Comments from
|
| 178 |
+
membership/]
|
| 179 |
+
SGTime -- "< 4 weeks" --> SGMem2[/Comments from
|
| 180 |
+
membership/]
|
| 181 |
+
SGTime -- "> 4 weeks,
|
| 182 |
+
< 8 weeks*" --> SGMem3[/Comments from
|
| 183 |
+
membership/]
|
| 184 |
+
TSAGTime -- "> 8 weeks*" --> TSAGMem1[/Comments from
|
| 185 |
+
membership/]
|
| 186 |
+
TSAGTime -- "< 4 weeks" --> TSAGMem2[/Comments from
|
| 187 |
+
membership/]
|
| 188 |
+
TSAGTime -- "> 4 weeks,
|
| 189 |
+
< 8 weeks*" --> TSAGMem3[/Comments from
|
| 190 |
+
membership/]
|
| 191 |
+
SGMem1 --> SGRes1[Resolve
|
| 192 |
+
comments,
|
| 193 |
+
approve**
|
| 194 |
+
electronically]
|
| 195 |
+
SGMem2 --> SGRes2[Resolve
|
| 196 |
+
comments,
|
| 197 |
+
approve at SG
|
| 198 |
+
meeting]
|
| 199 |
+
SGMem3 --> SGRes3[Discuss at SG
|
| 200 |
+
meeting but no
|
| 201 |
+
decision yet]
|
| 202 |
+
TSAGMem1 --> TSAGRes1[Resolve
|
| 203 |
+
comments,
|
| 204 |
+
approve**
|
| 205 |
+
electronically]
|
| 206 |
+
TSAGMem2 --> TSAGRes2[Discuss at TSAG
|
| 207 |
+
meeting but no
|
| 208 |
+
decision yet]
|
| 209 |
+
TSAGMem3 --> TSAGRes3[Resolve
|
| 210 |
+
comments,
|
| 211 |
+
approve at
|
| 212 |
+
TSAG meeting]
|
| 213 |
+
SGRes1 --> End([JCA-initiated])
|
| 214 |
+
SGRes2 --> End
|
| 215 |
+
SGRes3 --> SGRes4[Resolve
|
| 216 |
+
comments,
|
| 217 |
+
approve**
|
| 218 |
+
electronically]
|
| 219 |
+
TSAGRes1 --> End
|
| 220 |
+
TSAGRes2 --> TSAGRes5[Resolve
|
| 221 |
+
comments,
|
| 222 |
+
approve**
|
| 223 |
+
electronically]
|
| 224 |
+
TSAGRes3 --> End
|
| 225 |
+
SGRes4 --> End
|
| 226 |
+
TSAGRes5 --> End
|
| 227 |
+
|
| 228 |
+
```
|
| 229 |
+
|
| 230 |
+
Flowchart illustrating the process for proposing and approving the creation of a JCA. The process starts with 'JCA proposal initiated (Clause 6.1)', followed by 'Comments from SG (or TSAG) management team' and 'Comments from other SDO or forum leaders (if appropriate)'. A decision point asks 'Lead SG and within Res. 2 mandate?'. If 'Yes (Clause 6.1.1)', it leads to 'Electronic notification to SG reflector'. If 'No (Clause 6.1.2)', it leads to 'Electronic notification to TSAG and SG reflectors'. Both paths lead to a decision on 'Time to next meeting?'. For the SG path, if '> 8 weeks\*', it leads to 'Comments from membership' and 'Resolve comments, approve\*\* electronically'. If '< 4 weeks', it leads to 'Comments from membership' and 'Discuss at SG meeting but no decision yet', which then leads to 'Resolve comments, approve\*\* electronically'. If '> 4 weeks, < 8 weeks\*', it leads to 'Comments from membership' and 'Resolve comments, approve at SG meeting'. For the TSAG path, if '> 8 weeks\*', it leads to 'Comments from membership' and 'Resolve comments, approve\*\* electronically'. If '< 4 weeks', it leads to 'Comments from membership' and 'Discuss at TSAG meeting but no decision yet', which then leads to 'Resolve comments, approve\*\* electronically'. If '> 4 weeks, < 8 weeks\*', it leads to 'Comments from membership' and 'Resolve comments, approve at TSAG meeting'. All paths converge to 'JCA-initiated'.
|
| 231 |
+
|
| 232 |
+
\* Nominal time period.
|
| 233 |
+
|
| 234 |
+
\*\* If there are no substantive comments, the JCA is considered approved. If the JCA proposal is modified per comments received, it is again circulated for a four-week review. If there are no substantive comments, the JCA is considered approved.
|
| 235 |
+
|
| 236 |
+
A.18(24)\_F6-1
|
| 237 |
+
|
| 238 |
+
**Figure 6-1 – Alternatives in proposing and approving the creation of a JCA**
|
| 239 |
+
|
| 240 |
+
**6.2** JCAs are open, but (to restrict their size) should primarily be limited to official representatives from the relevant study groups that are responsible for work covered by the scope of the JCA. A JCA may also include invited experts and invited representatives of other SDOs and forums, as appropriate. All participants should confine inputs to a JCA to the purpose of the JCA.
|
| 241 |
+
|
| 242 |
+
**6.3** The establishment of a JCA is to be announced in a TSB circular, which should include the terms of reference of the JCA, the chair of the JCA, and the study group responsible for the JCA.
|
| 243 |
+
|
| 244 |
+
**6.4** JCAs should work primarily by correspondence and electronic meetings. Any physical meeting considered necessary should be convened by the chair of the JCA. Physical meetings should be supported by conferencing capabilities where possible, and both physical and electronic meetings should be scheduled as far as practicable at times that will provide maximum opportunity for broad participation. It is anticipated that physical meetings will be in conjunction with the involved study group meetings (in which case it is reflected in the collective letter for that study group) as far as practicable, but if a separate meeting is to be held, it is to be announced at least four weeks in advance by an (electronic) collective invitation letter.
|
| 245 |
+
|
| 246 |
+
**6.5** Inputs to the work of a JCA should be sent to the JCA chair and to the concerned TSB counsellor, and the latter will make these available to the members of the JCA.
|
| 247 |
+
|
| 248 |
+
**6.6** JCAs may submit proposals to the relevant study groups to achieve alignment in the development of related Recommendations and other deliverables by the respective study groups. A JCA may also issue liaison statements.
|
| 249 |
+
|
| 250 |
+
**6.7** JCA input and output documents (see clause 1), and reports are made available to the ITU-T membership. Reports are issued after each JCA meeting. TSAG may monitor JCA activities through these reports.
|
| 251 |
+
|
| 252 |
+
**6.8** TSB will provide support for a JCA, within available resource limits.
|
| 253 |
+
|
| 254 |
+
**6.9** A JCA may be terminated at any time if the involved study groups agree that the JCA is no longer required. A proposal to do so, including justification, may be submitted by any study group involved or by TSAG, and examined for decision by the study group responsible for the JCA, after consulting the involved study groups and TSAG (via electronic means, if a TSAG meeting is not pending in the near future). A JCA will be reviewed at the first TSAG meeting following the WTSA. A specific decision must be taken on the continuation of the JCA, potentially with adjusted terms of reference.
|
| 255 |
+
|
| 256 |
+
## **Appendix I**
|
| 257 |
+
|
| 258 |
+
### **Guiding principles for the periodic review of JCAs**
|
| 259 |
+
|
| 260 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 261 |
+
|
| 262 |
+
Technology and market requirements evolve rapidly. Consequently, the needs for coordination also evolve and call for a periodic review of JCAs to determine whether they remain fit-for-purpose.
|
| 263 |
+
|
| 264 |
+
This appendix contains guiding principles and key performance indicators (KPIs) that should be monitored regularly and provided in particular when a review of JCA activities is submitted to its parent group and/or TSAG. JCAs, including KPIs, should be reviewed regularly, e.g., at least once a year.
|
| 265 |
+
|
| 266 |
+
The guiding principles and KPIs are the following:
|
| 267 |
+
|
| 268 |
+
- The impact of the JCA and whether its objectives could be achieved by other leaner and existing structures within the study groups or TSAG.
|
| 269 |
+
- The lifetime of the JCA should not exceed two years, renewable once.
|
| 270 |
+
- The need to continue, update the terms of reference, or terminate the JCA.
|
| 271 |
+
- Coordination issues addressed by the JCA during the reporting period, or on a yearly basis (as applicable).
|
| 272 |
+
- Number of meetings held, and the concrete outcomes achieved at each meeting.
|
| 273 |
+
- Deliverables developed and maintained under the JCA (e.g., roadmaps, gap analyses).
|
| 274 |
+
- Number of participants and different entities represented at JCA meetings.
|
| 275 |
+
- Number of input documents submitted to JCA meetings.
|
| 276 |
+
- Number of active liaison relationships maintained with external bodies and ITU Study Groups.
|
| 277 |
+
|
| 278 |
+
## Bibliography
|
| 279 |
+
|
| 280 |
+
- [[b-ITU-T A.1](#)] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector*.
|
| 281 |
+
- [[b-ITU-T A.13](#)] Recommendation ITU-T A.13 (2019), *Non-normative ITU-T publications, including Supplements to ITU-T Recommendations*.
|
| 282 |
+
- [[b-WTSA Res. 22](#)] WTSA Resolution 22 (Rev. New Delhi, 2024), *Authorization for the Telecommunication Standardization Advisory Group to act between world telecommunication standardization assemblies*.
|
| 283 |
+
|
| 284 |
+
|
| 285 |
+
|
| 286 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 287 |
+
|
| 288 |
+
| | |
|
| 289 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 290 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 291 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 292 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 293 |
+
| Series F | Non-telephone telecommunication services |
|
| 294 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 295 |
+
| Series H | Audiovisual and multimedia systems |
|
| 296 |
+
| Series I | Integrated services digital network |
|
| 297 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 298 |
+
| Series K | Protection against interference |
|
| 299 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 300 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 301 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 302 |
+
| Series O | Specifications of measuring equipment |
|
| 303 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 304 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 305 |
+
| Series R | Telegraph transmission |
|
| 306 |
+
| Series S | Telegraph services terminal equipment |
|
| 307 |
+
| Series T | Terminals for telematic services |
|
| 308 |
+
| Series U | Telegraph switching |
|
| 309 |
+
| Series V | Data communication over the telephone network |
|
| 310 |
+
| Series X | Data networks, open system communications and security |
|
| 311 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 312 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.2-201211-I_PDF-E/62e1187eade1baedc296526bd9896580_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.2-201211-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
# A.2
|
| 12 |
+
|
| 13 |
+
(11/2012)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
---
|
| 18 |
+
|
| 19 |
+
# **Presentation of contributions to the ITU Telecommunication Standardization Sector**
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T A.2
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with two red lightning bolts striking it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, the words "International Telecommunication Union" are written in a smaller, blue font.
|
| 26 |
+
|
| 27 |
+
ITU logo: A blue globe with red lightning bolts and the text 'ITU International Telecommunication Union'.
|
| 28 |
+
|
| 29 |
+
|
| 30 |
+
|
| 31 |
+
## **Recommendation ITU-T A.2**
|
| 32 |
+
|
| 33 |
+
# **Presentation of contributions to the ITU Telecommunication Standardization Sector**
|
| 34 |
+
|
| 35 |
+
# **Summary**
|
| 36 |
+
|
| 37 |
+
This Recommendation gives directives on how draft, present and submit contributions to ITU-T study groups.
|
| 38 |
+
|
| 39 |
+
# **History**
|
| 40 |
+
|
| 41 |
+
| Edition | Recommendation | Approval | Study Group |
|
| 42 |
+
|---------|-------------------------|------------|-------------|
|
| 43 |
+
| 1.0 | ITU-T A.1 | 1984-10-19 | Assembly |
|
| 44 |
+
| 2.0 | ITU-T A.1 | 1988-11-25 | Assembly |
|
| 45 |
+
| 3.0 | ITU-T A.1 | 1993-03-12 | TSAG |
|
| 46 |
+
| 4.0 | ITU-T A.2 | 1996-10-18 | Assembly |
|
| 47 |
+
| 5.0 | ITU-T A.2 | 2000-10-06 | Assembly |
|
| 48 |
+
| 6.0 | ITU-T A.2 | 2004-10-14 | Assembly |
|
| 49 |
+
| 6.1 | ITU-T A.2 (2004) Amd. 1 | 2006-07-07 | TSAG |
|
| 50 |
+
| 7.0 | ITU-T A.2 | 2008-10-30 | Assembly |
|
| 51 |
+
| 8.0 | ITU-T A.2 | 2012-11-30 | Assembly |
|
| 52 |
+
|
| 53 |
+
# FOREWORD
|
| 54 |
+
|
| 55 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 56 |
+
|
| 57 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 58 |
+
|
| 59 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 60 |
+
|
| 61 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 62 |
+
|
| 63 |
+
## NOTE
|
| 64 |
+
|
| 65 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 66 |
+
|
| 67 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 68 |
+
|
| 69 |
+
# INTELLECTUAL PROPERTY RIGHTS
|
| 70 |
+
|
| 71 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 72 |
+
|
| 73 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 74 |
+
|
| 75 |
+
© ITU 2013
|
| 76 |
+
|
| 77 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 78 |
+
|
| 79 |
+
## Table of Contents
|
| 80 |
+
|
| 81 |
+
| | Page |
|
| 82 |
+
|----------------------------------------------------------------------------------------------------------------------|------|
|
| 83 |
+
| Appendix I – Detailed guidelines for the preparation of contributions relative to the study of ITU-T Questions ..... | 3 |
|
| 84 |
+
| I.1 Contents of contribution ..... | 3 |
|
| 85 |
+
| I.2 Mechanics and presentation ..... | 4 |
|
| 86 |
+
|
| 87 |
+
|
| 88 |
+
|
| 89 |
+
## Recommendation ITU-T A.2
|
| 90 |
+
|
| 91 |
+
# **Presentation of contributions to the ITU Telecommunication Standardization Sector**
|
| 92 |
+
|
| 93 |
+
*(1984; 1988; 1993; 1996; 2000; 2004; 2008; 2012)*
|
| 94 |
+
|
| 95 |
+
**1** With regard to the presentation of contributions to the study of Questions assigned to the ITU Telecommunication Standardization Sector (ITU-T), the following general directives should be applied:
|
| 96 |
+
|
| 97 |
+
- a) Contributions should be concisely drafted, avoiding unnecessary details, tables or statistics that make no direct contribution to the study of a Question. They should be clearly written with a view to being universally understood, i.e. they should be as codified as possible, use international terminology and avoid the technical jargon peculiar to the author's country. Contributors should use the units, letter symbols and graphical symbols of the international system of units (SI) as supported by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). In addition, Coordinated Universal Time (UTC) should be used to designate time.
|
| 98 |
+
- b) A contribution should not, as a rule, exceed about 2500 words (requiring no more than five printed pages to be distributed), nor should it include more than three pages of figures (making eight pages in all). It should be accompanied by an abstract that is no more than 150-200 words, and which summarizes the aim of the contribution and its technical content. Whenever possible, a section with the heading Rationale (or Discussion) should be used for the main text, which sets forth the essential information required for justifying the proposals or conclusions of the contribution. The contribution should end with a Proposal or, if not feasible, a Conclusion (both if required). For self-explanatory proposals, the rationale section may be omitted. These directives do not apply to draft Recommendations.
|
| 99 |
+
- c) Documents of purely theoretical interest that are not directly related to the Questions under study should not be submitted.
|
| 100 |
+
- d) Articles that have been or are to be published in the technical press should not be submitted to ITU-T, unless they relate directly to Questions under study.
|
| 101 |
+
- e) Passages of an unduly commercial nature included in a contribution may be deleted by the Director of the Telecommunication Standardization Bureau (TSB) in agreement with the chairman; the author of the contribution shall be advised of any such deletions.
|
| 102 |
+
|
| 103 |
+
Detailed guidelines recommended for the preparation of contributions are provided in Appendix I. Details on the presentation of ITU-T texts can be found in the "Author's Guide for drafting ITU-T Recommendations" (referred to as "Guide" in the following).
|
| 104 |
+
|
| 105 |
+
**2** With regard to the submission of contributions and TDs (including liaison statements), all documents to ITU-T should, as far as possible, be sent using electronic means; if no such facilities are available to the contributor, submission of paper only copies is acceptable.
|
| 106 |
+
|
| 107 |
+
Electronic submission facilities include e-mail and the ITU web-based interface. Detailed information and instructions for these methods are maintained by TSB on the ITU-T website and disseminated periodically via TSB circular.
|
| 108 |
+
|
| 109 |
+
If contributions are submitted as paper documents, they shall be addressed to TSB and copied to the study group chairmen and vice-chairmen, working party chairmen and concerned rapporteur(s).
|
| 110 |
+
|
| 111 |
+
**3** Contributions should be printable in A4 format, as far as possible. The first page must have the standard layout of ITU-T contributions. Drafts must be in one or more of the official and working languages of the Union. When existing ITU-T texts already translated have been used in some parts of a contribution, a copy of the contribution with a precise reference to the original
|
| 112 |
+
|
| 113 |
+
sources also should be sent to TSB. If ITU-T figures are used in the contributions, the ITU-T number must not be deleted, but if the figure has been modified, the abbreviation "mod" should be added after the number. If not required by further development of the text, use of colours in the text of contributions or other submitted documents should be avoided.
|
| 114 |
+
|
| 115 |
+
**4** If a contribution contains electronic material (software, test data, etc., referred to herein as "software"), it should be attached to the text sent to TSB.
|
| 116 |
+
|
| 117 |
+
Contributors are encouraged to submit formal language descriptions as electronic attachments.
|
| 118 |
+
|
| 119 |
+
# Appendix I
|
| 120 |
+
|
| 121 |
+
## Detailed guidelines for the preparation of contributions relative to the study of ITU-T Questions
|
| 122 |
+
|
| 123 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 124 |
+
|
| 125 |
+
NOTE – These guidelines will be updated by TSB as necessary. The updated version will be maintained on the ITU-T website and issued in a TSB circular.
|
| 126 |
+
|
| 127 |
+
The guidelines in this appendix supplement the general directives set out in Recommendation ITU-T A.2. For ease of reference, they are organized under relevant headings in two categories: one deals with the contents of the contribution and the other with the mechanics of its presentation.
|
| 128 |
+
|
| 129 |
+
### I.1 Contents of contribution
|
| 130 |
+
|
| 131 |
+
A contribution should be clear, concise and comprehensive in itself. It should start with the Heading and the Abstract, which are independent sections. The main text of the contribution should contain two sections: Rationale (or Discussion) and Proposal (or Conclusion). Supplementary sections such as annexes, if necessary, should follow the main text. The guidelines for the structure of the main text do not apply to draft Recommendations or to submission by rapporteurs.
|
| 132 |
+
|
| 133 |
+
**I.1.1** *Heading* – The heading of a contribution submitted to TSB should provide:
|
| 134 |
+
|
| 135 |
+
- study group Question number(s) that the contribution is addressing;
|
| 136 |
+
- place and date of the meeting to which the contribution is directed;
|
| 137 |
+
- study group and working party to which the contribution should be submitted;
|
| 138 |
+
- source of the contribution: originating country and/or organization;
|
| 139 |
+
- title of the contribution;
|
| 140 |
+
- contact information for the contribution originator and/or representative: name, organization, country, telephone, fax and e-mail address.
|
| 141 |
+
|
| 142 |
+
A template that defines the recommended heading format is available (under "Guides, Tools, and Templates") on the ITU-T study group and TSAG websites.
|
| 143 |
+
|
| 144 |
+
**I.1.2** *Abstract* – The abstract should outline clearly and concisely the aim (for example, proposal for a new Recommendation) and the content (proposals and/or conclusions of the contribution). In addition, it should enable prospective readers to determine quickly whether the contribution contains information in their area of interest and, often, which working party(ies) should review the contribution. This is a very important part of the document and would normally be prepared after the other sections are written. An abstract should not exceed 150-200 words. It should be understandable by other study groups and not just the intended readers of the contribution.
|
| 145 |
+
|
| 146 |
+
**I.1.3** *Rationale (Discussion)* – This section should provide discussion, reasons and justification for the proposals or conclusions. It develops the theme, describing the methods used and the observations or findings, and comments on their significance.
|
| 147 |
+
|
| 148 |
+
**I.1.4** *Proposal (Conclusion)* – The main text should end with a conclusion that, whenever possible, should be in the form of a concrete proposal indicating the intended disposition of the contribution. It would be useful to make the following distinction between Proposal and Conclusion, so that a standard approach to their application may be adopted. The heading Proposal should be used when the section offers suggestions for acceptance (such as solutions, plans and changes the contributor expects to be implemented) and when decisions or actions are requested. The heading Conclusion should be used when it is merely informational, such as summarizing observations and no decision about a course of action is expected. If both appear in a contribution, the proposals should follow the conclusions.
|
| 149 |
+
|
| 150 |
+
**I.1.5** *Supplementary Sections* – Supporting or more detailed information that might interrupt the flow of ideas in the main text should be placed in the sections containing annexes, appendices, references and attachments. A solid line can be used to separate such sections from the main text. "The Guide" describes the distinction between the uses of Annex and Appendix.
|
| 151 |
+
|
| 152 |
+
### **I.2 Mechanics and presentation**
|
| 153 |
+
|
| 154 |
+
**I.2.1** *Clause numbering* – The contribution should be structured logically and, whenever clarity and flow demand, hierarchically, with discrete clauses and subclauses for presenting different levels of detail. Different clauses and subclauses in the main text should be designated with decimal numbers, adhering as much as possible to the hierarchical numbering system recommended for ITU-T texts (see "Guide"); for example, 1.1, 1.2.3. Examples for numbering the supplementary sections are A.1.1 of Annex A and VI.3.4 of Appendix VI.
|
| 155 |
+
|
| 156 |
+
**I.2.2** *Page numbering* – The title page should be left unnumbered. All the following pages should be numbered consecutively from page 2, including tables, annexes, appendices or attachments. Page numbers should normally be centred at the top of the page. Each page should include the document number (if available) immediately below the page number. It is useful to show the total number of pages with the page number, e.g. 2 of 10.
|
| 157 |
+
|
| 158 |
+
**I.2.3** *Figures and diagrams* – Figures and diagrams must be clear and legible when printed in A4 format.
|
| 159 |
+
|
| 160 |
+
**I.2.4** *Formulae* – Mathematical formulae should only be presented for explaining texts. Details of how they are derived should be avoided.
|
| 161 |
+
|
| 162 |
+
**I.2.5** *Quotations* – Simple reference to the document number or paragraph number of an existing text or key phrase should be used instead of lengthy quotes. Material available elsewhere in ITU-T should not be reproduced or quoted at length. Excerpts or brief summaries may be included in the contribution when it is known that the members of the ITU-T study group do not have ready access to such material.
|
| 163 |
+
|
| 164 |
+
**I.2.6** *References* – Reference to other ITU-T contributions or Recommendations should be made by using the official document number, e.g. COM 14-10. If the referenced contribution belongs to a previous study period, this fact should be noted as well.
|
| 165 |
+
|
| 166 |
+
References to standards other than ITU or ISO/IEC publications or standards should conform to the requirements of Recommendation ITU-T A.5. Other publications not covered by Recommendation ITU-T A.5 may be referenced in a Bibliography.
|
| 167 |
+
|
| 168 |
+
(See "Guide" for more information on references and bibliographies.)
|
| 169 |
+
|
| 170 |
+
**I.2.7** *Revision to existing text* – If a contribution proposes modifications to an existing text, e.g. draft Recommendation, the portions of the text to be modified should be clearly shown with revision marks. Adequate indications shall also be given to identify any changes proposed with regard to the previous version of the same text.
|
| 171 |
+
|
| 172 |
+
Such change indications could be made, for example, by strikethrough, underlining and by vertical revision bars (|) appearing at the margin of the page.
|
| 173 |
+
|
| 174 |
+
|
| 175 |
+
|
| 176 |
+
# **SERIES OF ITU-T RECOMMENDATIONS**
|
| 177 |
+
|
| 178 |
+
| | |
|
| 179 |
+
|-----------------|---------------------------------------------------------------------------------------------|
|
| 180 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 181 |
+
| Series D | General tariff principles |
|
| 182 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 183 |
+
| Series F | Non-telephone telecommunication services |
|
| 184 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 185 |
+
| Series H | Audiovisual and multimedia systems |
|
| 186 |
+
| Series I | Integrated services digital network |
|
| 187 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 188 |
+
| Series K | Protection against interference |
|
| 189 |
+
| Series L | Construction, installation and protection of cables and other elements of outside plant |
|
| 190 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 191 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 192 |
+
| Series O | Specifications of measuring equipment |
|
| 193 |
+
| Series P | Terminals and subjective and objective assessment methods |
|
| 194 |
+
| Series Q | Switching and signalling |
|
| 195 |
+
| Series R | Telegraph transmission |
|
| 196 |
+
| Series S | Telegraph services terminal equipment |
|
| 197 |
+
| Series T | Terminals for telematic services |
|
| 198 |
+
| Series U | Telegraph switching |
|
| 199 |
+
| Series V | Data communication over the telephone network |
|
| 200 |
+
| Series X | Data networks, open system communications and security |
|
| 201 |
+
| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
|
| 202 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.23-200010-I_PDF-E/c1dcc5d53f398ab2e17c6fe176fdb69c_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.23-200010-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,116 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
|
| 4 |
+
|
| 5 |
+
ITU logo: a globe with the letters ITU and a lightning bolt.
|
| 6 |
+
|
| 7 |
+
INTERNATIONAL TELECOMMUNICATION UNION
|
| 8 |
+
|
| 9 |
+
# ITU-T
|
| 10 |
+
|
| 11 |
+
TELECOMMUNICATION
|
| 12 |
+
STANDARDIZATION SECTOR
|
| 13 |
+
OF ITU
|
| 14 |
+
|
| 15 |
+
## A.23
|
| 16 |
+
|
| 17 |
+
(10/2000)
|
| 18 |
+
|
| 19 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 20 |
+
|
| 21 |
+
---
|
| 22 |
+
|
| 23 |
+
## **Collaboration with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on information technology**
|
| 24 |
+
|
| 25 |
+
ITU-T Recommendation A.23
|
| 26 |
+
|
| 27 |
+
(Formerly CCITT Recommendation)
|
| 28 |
+
|
| 29 |
+
---
|
| 30 |
+
|
| 31 |
+
|
| 32 |
+
|
| 33 |
+
# **ITU-T Recommendation A.23**
|
| 34 |
+
|
| 35 |
+
###### **Collaboration with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on information technology**
|
| 36 |
+
|
| 37 |
+
###### **Source**
|
| 38 |
+
|
| 39 |
+
ITU-T Recommendation A.23 was prepared by TSAG (1997-2000) and approved by WTSA (27 September – 6 October 2000).
|
| 40 |
+
|
| 41 |
+
## FOREWORD
|
| 42 |
+
|
| 43 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 44 |
+
|
| 45 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 46 |
+
|
| 47 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 48 |
+
|
| 49 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 50 |
+
|
| 51 |
+
## NOTE
|
| 52 |
+
|
| 53 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 54 |
+
|
| 55 |
+
© ITU 2001
|
| 56 |
+
|
| 57 |
+
All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.
|
| 58 |
+
|
| 59 |
+
###### Recommendation A.23
|
| 60 |
+
|
| 61 |
+
###### **Collaboration with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on information technology**
|
| 62 |
+
|
| 63 |
+
*(Helsinki, 1993 amended at Geneva 1996, Montreal, 2000)*
|
| 64 |
+
|
| 65 |
+
The WTSA,
|
| 66 |
+
|
| 67 |
+
*considering*
|
| 68 |
+
|
| 69 |
+
- a) the purposes of the International Telecommunication Union set forth in Article 1 of its Constitution (Geneva, 1992) relating to the harmonization of telecommunication facilities;
|
| 70 |
+
- b) the duties of the Telecommunication Standardization Sector (Chapter III of the Constitution, Geneva, 1992) of the International Telecommunication Union;
|
| 71 |
+
- c) Resolution 7 (Geneva, 1996) recognizes common interests with ISO and IEC concerning telecommunication and information technologies as well as some other topics and cooperation with them by appropriate means,
|
| 72 |
+
|
| 73 |
+
*decides*
|
| 74 |
+
|
| 75 |
+
- 1 that in accordance with Resolution 7, every effort should be made in establishing respective study programmes to identify overlapping studies with a view to avoiding duplication of work;
|
| 76 |
+
- 2 that for those subjects in the fields of information technology including data transmission, multimedia, open system communications and telematic services, etc., where there is a common interest and where it is agreed that coordination is desirable, then text should be drawn up mutually and kept aligned;
|
| 77 |
+
- 3 that in carrying on the respective studies, collaborative meetings at appropriate levels should be scheduled, where necessary. In drafting aligned text, it is necessary to take into account the respective timing for approvals and publication, particularly with the ISO/IEC Joint Technical Committee 1 (JTC 1) on Information Technology.
|
| 78 |
+
|
| 79 |
+
A Guide for ITU-T and ISO/IEC JTC 1 Cooperation is given in Annex A, which contains a set of procedures for cooperation between the two sides. These procedures, which have also been adopted by ISO/IEC JTC 1, should be used, with flexibility, according to need. The "Rules for presentation of ITU-T | ISO/IEC common text"<sup>1</sup> in Annex A should be respected in the drafting of common texts.
|
| 80 |
+
|
| 81 |
+
---
|
| 82 |
+
|
| 83 |
+
<sup>1</sup> The Guide is published as a separate booklet and is available from TSB.
|
| 84 |
+
|
| 85 |
+
|
| 86 |
+
|
| 87 |
+
|
| 88 |
+
|
| 89 |
+
# **SERIES OF ITU-T RECOMMENDATIONS**
|
| 90 |
+
|
| 91 |
+
### **Series A Organization of the work of ITU-T**
|
| 92 |
+
|
| 93 |
+
- Series B Means of expression: definitions, symbols, classification
|
| 94 |
+
- Series C General telecommunication statistics
|
| 95 |
+
- Series D General tariff principles
|
| 96 |
+
- Series E Overall network operation, telephone service, service operation and human factors
|
| 97 |
+
- Series F Non-telephone telecommunication services
|
| 98 |
+
- Series G Transmission systems and media, digital systems and networks
|
| 99 |
+
- Series H Audiovisual and multimedia systems
|
| 100 |
+
- Series I Integrated services digital network
|
| 101 |
+
- Series J Cable networks and transmission of television, sound programme and other multimedia signals
|
| 102 |
+
- Series K Protection against interference
|
| 103 |
+
- Series L Construction, installation and protection of cables and other elements of outside plant
|
| 104 |
+
- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits
|
| 105 |
+
- Series N Maintenance: international sound programme and television transmission circuits
|
| 106 |
+
- Series O Specifications of measuring equipment
|
| 107 |
+
- Series P Telephone transmission quality, telephone installations, local line networks
|
| 108 |
+
- Series Q Switching and signalling
|
| 109 |
+
- Series R Telegraph transmission
|
| 110 |
+
- Series S Telegraph services terminal equipment
|
| 111 |
+
- Series T Terminals for telematic services
|
| 112 |
+
- Series U Telegraph switching
|
| 113 |
+
- Series V Data communication over the telephone network
|
| 114 |
+
- Series X Data networks and open system communications
|
| 115 |
+
- Series Y Global information infrastructure and Internet protocol aspects
|
| 116 |
+
- Series Z Languages and general software aspects for telecommunication systems
|
marked/A/T-REC-A.24-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.24-202408-I_PDF-E/7cbb01986ee6e18967d2c8aa378a0c8a_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.24-202408-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,603 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Recommendation **ITU-T A.24 (08/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
## **Collaboration and exchange of information with other organizations**
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
# Recommendation ITU-T A.24
|
| 14 |
+
|
| 15 |
+
# Collaboration and exchange of information with other organizations
|
| 16 |
+
|
| 17 |
+
## Summary
|
| 18 |
+
|
| 19 |
+
Recommendation ITU-T A.24 addresses different processes for collaboration and exchange of information between ITU-T and qualified organizations, including a generic process for developing an ITU-T document (Recommendation, Supplement, etc.) in collaboration with other organizations, with the aim of producing documents that are identical (or technically-aligned).
|
| 20 |
+
|
| 21 |
+
## History \*
|
| 22 |
+
|
| 23 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 24 |
+
|---------|----------------|------------|-------------|--------------------|
|
| 25 |
+
| 1.0 | ITU-T A.24 | 2024-08-02 | TSAG | 11.1002/1000/15863 |
|
| 26 |
+
|
| 27 |
+
## Keywords
|
| 28 |
+
|
| 29 |
+
Collaboration, collaborative work, common document, common team, formal communication process, multilateral collaboration.
|
| 30 |
+
|
| 31 |
+
---
|
| 32 |
+
|
| 33 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 34 |
+
|
| 35 |
+
## FOREWORD
|
| 36 |
+
|
| 37 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 38 |
+
|
| 39 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 40 |
+
|
| 41 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 42 |
+
|
| 43 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 44 |
+
|
| 45 |
+
### NOTE
|
| 46 |
+
|
| 47 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 48 |
+
|
| 49 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 50 |
+
|
| 51 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 52 |
+
|
| 53 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 54 |
+
|
| 55 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 56 |
+
|
| 57 |
+
© ITU 2024
|
| 58 |
+
|
| 59 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 60 |
+
|
| 61 |
+
## Table of Contents
|
| 62 |
+
|
| 63 |
+
| | | Page |
|
| 64 |
+
|----|--------------------------------------------------------------|------|
|
| 65 |
+
| 1 | Scope..... | 1 |
|
| 66 |
+
| 2 | References..... | 1 |
|
| 67 |
+
| 3 | Definitions ..... | 2 |
|
| 68 |
+
| | 3.1 Terms defined elsewhere..... | 2 |
|
| 69 |
+
| | 3.2 Terms defined in this Recommendation..... | 2 |
|
| 70 |
+
| 4 | Abbreviations and acronyms ..... | 2 |
|
| 71 |
+
| 5 | Conventions ..... | 3 |
|
| 72 |
+
| 6 | Qualification of an organization ..... | 3 |
|
| 73 |
+
| 7 | Determining the mode of collaboration..... | 3 |
|
| 74 |
+
| 8 | Agreeing the mode of collaboration ..... | 5 |
|
| 75 |
+
| 9 | Publication of documents ..... | 6 |
|
| 76 |
+
| 10 | Maintenance of documents ..... | 6 |
|
| 77 |
+
| 11 | Patent policy and copyright arrangements..... | 7 |
|
| 78 |
+
| | Annex A – Collaboration using the liaison mode..... | 8 |
|
| 79 |
+
| | Annex B – Collaboration using collaborative work..... | 10 |
|
| 80 |
+
| | B.1 Establishing a collaborative work ..... | 10 |
|
| 81 |
+
| | B.2 Participation in meetings of the other organization..... | 10 |
|
| 82 |
+
| | B.3 Contributions ..... | 10 |
|
| 83 |
+
| | B.4 Editors for a common document ..... | 10 |
|
| 84 |
+
| | B.5 Achieving consensus ..... | 11 |
|
| 85 |
+
| | B.6 Progress reporting..... | 11 |
|
| 86 |
+
| | Annex C – Collaboration using a common team ..... | 12 |
|
| 87 |
+
| | C.1 Establishing a common team..... | 12 |
|
| 88 |
+
| | C.2 Meetings ..... | 12 |
|
| 89 |
+
| | C.3 Contributions ..... | 13 |
|
| 90 |
+
| | C.4 Editor in case of a common document ..... | 13 |
|
| 91 |
+
| | C.5 Achieving consensus ..... | 13 |
|
| 92 |
+
| | C.6 Progress reporting..... | 14 |
|
| 93 |
+
| | Annex D – Synchronization of approval processes ..... | 15 |
|
| 94 |
+
| | Annex E – Multilateral collaboration..... | 18 |
|
| 95 |
+
| | Bibliography..... | 19 |
|
| 96 |
+
|
| 97 |
+
|
| 98 |
+
|
| 99 |
+
# Recommendation ITU-T A.24
|
| 100 |
+
|
| 101 |
+
## Collaboration and exchange of information with other organizations
|
| 102 |
+
|
| 103 |
+
# 1 Scope
|
| 104 |
+
|
| 105 |
+
ITU-T maintains cooperative relationships with many other organizations. The technologies for which ITU-T and these other organizations are responsible continue to converge, which has resulted in an increase of interdependency between ITU-T's work programme and the programmes of other organizations. This Recommendation describes a process for authoritative document exchange with another organization, which is to be agreed upon with that organization. It also introduces generic procedures for developing an ITU-T document (Recommendation, Supplement, etc.) in collaboration with one or more other organization(s). Such generic procedures are to be considered as guidelines for negotiating a process or mode of collaboration with other qualified organization(s).
|
| 106 |
+
|
| 107 |
+
On a case-by-case basis, ITU-T study groups may use processes or modes of collaboration other than those described in this Recommendation. In particular, exchange of information (by way of liaison statements) can occur at any time with another organization without applying the processes described in this Recommendation.
|
| 108 |
+
|
| 109 |
+
NOTE 1 – This Recommendation does not apply to ITU-T Recommendations developed in collaboration with ISO/IEC JTC 1 because the long-standing procedures of [b-ITU-T A.23], which have proven very successful, remain unchanged.
|
| 110 |
+
|
| 111 |
+
NOTE 2 – Regarding collaboration with the Internet Engineering Task Force (IETF), clause 2.5.3 of [b-ITU-T A-Suppl.3] states that "common or joint text is discouraged because of the current differences in procedures for document approval and revision."
|
| 112 |
+
|
| 113 |
+
The case of normatively referencing the documents of other organizations in ITU-T Recommendations is addressed in [ITU-T A.5].
|
| 114 |
+
|
| 115 |
+
The case of ITU-T incorporating texts (in part or in whole, with or without modifications) from another organization is addressed in [b-ITU-T A.25].
|
| 116 |
+
|
| 117 |
+
## 2 References
|
| 118 |
+
|
| 119 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 120 |
+
|
| 121 |
+
- | | |
|
| 122 |
+
|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 123 |
+
| [ITU-T A.5] | Recommendation ITU-T A.5 (2022), <i>Generic procedures for including references to documents of other organizations in ITU-T Recommendations</i> . |
|
| 124 |
+
| [ITU-T A.8] | Recommendation ITU-T A.8 (2024), <i>Alternative approval process for new and revised ITU-T Recommendations</i> . |
|
| 125 |
+
| [WTSA Res. 1] | World Telecommunication Standardization Assembly Resolution 1 (Rev. Geneva, 2022), <i>Rules of procedure of the ITU Telecommunication Standardization Sector</i> .<br>< <a href="http://www.itu.int/pub/T-RES-T.1-2022">http://www.itu.int/pub/T-RES-T.1-2022</a> > |
|
| 126 |
+
|
| 127 |
+
## 3 Definitions
|
| 128 |
+
|
| 129 |
+
### 3.1 Terms defined elsewhere
|
| 130 |
+
|
| 131 |
+
This Recommendation uses the following terms defined elsewhere:
|
| 132 |
+
|
| 133 |
+
**3.1.1 amendment** [b-ITU-T A.1]: Changes or additions to an already published ITU-T Recommendation.
|
| 134 |
+
|
| 135 |
+
NOTE – If an amendment forms an integral part of the Recommendation, approval of the amendment follows the same approval procedures as the Recommendation; otherwise (e.g., when all changes are in appendices), it is agreed by the study group.
|
| 136 |
+
|
| 137 |
+
**3.1.2 Question** [WTSA Res. 1]: Description of an area of work to be studied, normally leading to the production of one or more new or revised Recommendations and/or new or revised non-normative documents as defined in [b-ITU-T A.13].
|
| 138 |
+
|
| 139 |
+
**3.1.3 Supplement** [b-ITU-T A.13]: An informative (non-normative) document which contains material which is supplementary to and associated with the subject matter of one or more Recommendations but which is not essential to their completeness or understanding and implementation.
|
| 140 |
+
|
| 141 |
+
### 3.2 Terms defined in this Recommendation
|
| 142 |
+
|
| 143 |
+
This Recommendation defines the following terms:
|
| 144 |
+
|
| 145 |
+
**3.2.1 collaborative work**: A mode of collaboration between an ITU-T Question and a group in an organization (or groups in multiple organizations) aimed at producing one or more common (or technically-aligned) documents through close liaison, and in the case of common documents, through a synchronized approval (see Annex B).
|
| 146 |
+
|
| 147 |
+
**3.2.2 common document**: A document which is developed jointly by an ITU-T Question and a group in an organization (or groups in multiple organizations).
|
| 148 |
+
|
| 149 |
+
NOTE – A unique document is developed jointly by an ITU-T Question and one (or more) organizations, but it may be published with different cover pages, headers and footers, based on the publication rules of each organization (see clause 9).
|
| 150 |
+
|
| 151 |
+
**3.2.3 common team**: A working group composed of individuals working on an ITU-T Question and from a group in an organization (or groups in multiple organizations) aimed at producing one or more common (or technically-aligned) documents through common meetings, and in the case of common documents, through a synchronized approval (see Annex C).
|
| 152 |
+
|
| 153 |
+
**3.2.4 technically-aligned documents**: A pair (or set) of documents which are developed in close collaboration between an ITU-T Question and a group in an organization (or groups in multiple organizations), and whose texts are technically aligned (but not identical).
|
| 154 |
+
|
| 155 |
+
NOTE 1 – Implementation of one technically-aligned document may not hamper interoperability with the implementation of the other technically-aligned document(s).
|
| 156 |
+
|
| 157 |
+
NOTE 2 – The document developed by the ITU-T Question follows the ITU-T publication rules (such as [b-Author's Guide]). The other document may follow the publication rules of the (external) organization(s).
|
| 158 |
+
|
| 159 |
+
## 4 Abbreviations and acronyms
|
| 160 |
+
|
| 161 |
+
This Recommendation uses the following abbreviations and acronyms:
|
| 162 |
+
|
| 163 |
+
| | |
|
| 164 |
+
|-----|------------------------------------------|
|
| 165 |
+
| AAP | Alternative Approval Process |
|
| 166 |
+
| TAP | Traditional Approval Process |
|
| 167 |
+
| TSB | Telecommunication Standardization Bureau |
|
| 168 |
+
|
| 169 |
+
## **5 Conventions**
|
| 170 |
+
|
| 171 |
+
In expressions such as "each organization", "one organization", "the other organization", the term "organization" (singular) designates an ITU-T study group or an (external) organization. In case of bilateral collaboration, the expression "the organization" always designates the (external) organization with which an ITU-T study group has established a mode of collaboration. In case of multilateral collaboration, the expression "the organization" designates the (external) organizations with which one (or more) ITU-T study group(s) has established a mode of collaboration.
|
| 172 |
+
|
| 173 |
+
In case of bilateral collaboration, the term "organizations" (plural) designates an ITU-T study group and an (external) organization which have a common interest in an area of work. In case of multilateral collaboration, the term "organizations" designates one (or more) ITU-T study groups and (external) organizations which have a common interest in an area of work.
|
| 174 |
+
|
| 175 |
+
The terms "ballot" and "balloting" are to be understood with respect to the rules and approval process of the organization (ITU-T or the external organization). For ITU-T, this is the last call in the case of the alternative approval process (AAP), and it is the consultation of Member States in the case of the traditional approval process (TAP).
|
| 176 |
+
|
| 177 |
+
## **6 Qualification of an organization**
|
| 178 |
+
|
| 179 |
+
**6.1** the ITU-T study group (or working party) shall consider the organization according to the criteria set out in clauses 6.1.1 to 6.1.3 (except for ISO and IEC).
|
| 180 |
+
|
| 181 |
+
**6.1.1** Qualification of the organization according to the criteria of Annex B of [ITU-T A.5] shall be conducted before considering establishing one of the modes of collaboration listed in clause 7.2.
|
| 182 |
+
|
| 183 |
+
**6.1.2** In addition, the organization is expected to have a process by which its output documents are published and regularly maintained (i.e., reaffirmed, revised, withdrawn, etc.).
|
| 184 |
+
|
| 185 |
+
**6.1.3** The organization is also expected to have a document change control process, including a clear, unambiguous document numbering scheme. In particular, a feature to look for is that updated versions of a given document be distinguishable from the earlier versions.
|
| 186 |
+
|
| 187 |
+
**6.2** Qualification of the organization according to the criteria of Annex B of [ITU-T A.5] is reviewed on a regular basis by study groups that need to establish a mode of collaboration with that organization. In particular, if the patent policy of that organization has changed, it is important to check that the new patent policy is consistent with the common patent policy for ITU-T/ITU-R/ISO/IEC and the guidelines for the implementation of the common patent policy for ITU-T/ITU-R/ISO/IEC (see clause 11).
|
| 188 |
+
|
| 189 |
+
## **7 Determining the mode of collaboration**
|
| 190 |
+
|
| 191 |
+
**7.1** To maximize the effectiveness of resources and to minimize conflict between standards, the ITU-T study group and the relevant group in the organization are encouraged to identify areas for collaborative work as early as possible in the development process. Normally as part of the development of a new Recommendation in ITU-T (see Annex A of [b-ITU-T A.1]), consideration is given to the need for interactions with other organizations. If enough information is available at this stage, then, if appropriate, one of the following modes of collaboration can be proposed and agreement sought from the other organization (see clause 8).
|
| 192 |
+
|
| 193 |
+
|
| 194 |
+
|
| 195 |
+
```
|
| 196 |
+
|
| 197 |
+
graph TD
|
| 198 |
+
D1{An ITU-T study group and one or more organizations have a common interest in an area of work}
|
| 199 |
+
D2{The prime responsibility falls to one of the organizations}
|
| 200 |
+
D3{The work to be carried out is non-controversial, and there is sufficient common participation in meetings of the organizations}
|
| 201 |
+
A1([No collaboration needed])
|
| 202 |
+
A2[Liaison approach
|
| 203 |
+
(see clause 7.3 and Annex A)]
|
| 204 |
+
A3[Collaborative work
|
| 205 |
+
(see clause 7.4 and Annex B)]
|
| 206 |
+
A4[Common team
|
| 207 |
+
(see clause 7.5 and Annex C)]
|
| 208 |
+
A5[Document published by one organization and referenced by the other org.]
|
| 209 |
+
A6[Technically-aligned documents]
|
| 210 |
+
A7[Common document]
|
| 211 |
+
|
| 212 |
+
D1 -- No --> A1
|
| 213 |
+
D1 -- Yes --> D2
|
| 214 |
+
D2 -- No --> D3
|
| 215 |
+
D2 -- Yes --> A2
|
| 216 |
+
A2 --> A5
|
| 217 |
+
D3 -- No --> A4
|
| 218 |
+
D3 -- Yes --> A3
|
| 219 |
+
A4 --> A6
|
| 220 |
+
A4 --> A7
|
| 221 |
+
A3 --> A6
|
| 222 |
+
A3 --> A7
|
| 223 |
+
|
| 224 |
+
```
|
| 225 |
+
|
| 226 |
+
Flowchart illustrating the possible modes of collaboration between ITU-T and one or more organizations. The process starts with a decision: 'An ITU-T study group and one or more organizations have a common interest in an area of work'. If 'No', it leads to 'No collaboration needed'. If 'Yes', it leads to another decision: 'The prime responsibility falls to one of the organizations'. If 'No', it leads to a third decision: 'The work to be carried out is non-controversial, and there is sufficient common participation in meetings of the organizations'. If 'No' to this third decision, it leads to a 'Common team' box, which then branches into 'Technically-aligned documents' and 'Common document'. If 'Yes' to the third decision, it leads to 'Collaborative work', which also branches into 'Technically-aligned documents' and 'Common document'. If 'Yes' to the second decision, it leads to a 'Liaison approach' box, which then leads to 'Document published by one organization and referenced by the other org.'.
|
| 227 |
+
|
| 228 |
+
A.24(24)\_F01
|
| 229 |
+
|
| 230 |
+
**Figure 1 – Possible modes of collaboration between ITU-T and one or more organizations**
|
| 231 |
+
|
| 232 |
+
**7.2** Collaboration (as specified in this Recommendation) can be carried out in one of three ways: by means of a liaison, by means of collaborative work or by means of a common team. Figure 1 provides some criteria for choosing the mode of collaboration, but those criteria are not exhaustive, and it is recommended that the study group and the organization carefully evaluate the terms of reference of the collaboration (see clause 8.2).
|
| 233 |
+
|
| 234 |
+
NOTE – These three modes of collaboration can be generalized to a multilateral collaboration as explained in Annex E.
|
| 235 |
+
|
| 236 |
+
**7.3** A formal communication process can be established to provide authoritative information of one organization's dependencies on the other's work (see Annex A). In addition, where an ITU-T study group and an organization have a common interest in an area of work and have agreed that the prime responsibility falls to one of the two organizations, the liaison approach (see Annex A) is well suited. In this situation, the work is carried out in one organization and the other organization participates, as appropriate, using its liaison status. The result is published by one organization and is referenced, as needed, by the other organization (see [ITU-T A.5]).
|
| 237 |
+
|
| 238 |
+
**7.4** Collaboration by means of collaborative work is suited for situations where the work to be carried out is straight-forward and relatively non-controversial, and where there is sufficient common participation in the meetings of the two organizations to make the interchange highly effective. The work on resolving issues and developing one or more common documents is continually progressed in the successive meetings of the two groups. The normal approval processes of both ITU-T and the organization are synchronized until the eventual publication of common or technically-aligned texts (see clause 9). Annex B details generic procedures when collaborative work is performed.
|
| 239 |
+
|
| 240 |
+
**7.5** Collaboration by means of a common team is well suited for situations where extended dialog is necessary to develop solutions and reach consensus. In this situation, all interested parties participate in a common team to mutually progress the work, resolve issues, and develop one or more
|
| 241 |
+
|
| 242 |
+
common (or technically-aligned) documents. The normal approval processes of both ITU-T and the organization are synchronized until the eventual publication of common or technically-aligned texts (see clause 9). Annex C details generic procedures when a common team is established.
|
| 243 |
+
|
| 244 |
+
**7.6** It is possible for the mode of collaboration to change as the work progresses.
|
| 245 |
+
|
| 246 |
+
NOTE – For example, work could be initiated in one organization and, as a result of a liaison statement, it could become recognized as integrally important to the other organization. At this point, agreement could be reached to advance all future work in another mode of collaboration (see clause 7.2).
|
| 247 |
+
|
| 248 |
+
## **8 Agreeing the mode of collaboration**
|
| 249 |
+
|
| 250 |
+
**8.1** Agreement for collaboration needs to be mutually recognized to be successful. Therefore, operation in one of the three modes of collaboration for a given area of work is an agreed decision of both organizations. This agreement (based on the terms of reference presented in clause 8.2) is to be confirmed at the ITU-T study group level and at the appropriate decision-making level of the organization.
|
| 251 |
+
|
| 252 |
+
**8.2** The mutually agreed terms of reference for a given mode of collaboration shall include:
|
| 253 |
+
|
| 254 |
+
- 1) the relevant ITU-T Question and its parent study group;
|
| 255 |
+
- 2) the relevant group in the organization and, if applicable, its parent body;
|
| 256 |
+
- 3) the mode of collaboration (see clause 7);
|
| 257 |
+
- 4) the scope of the effort as it relates to each organization's work programme;
|
| 258 |
+
- 5) where possible, identification (type, title and reference) of the document(s) that is (are) to be developed collaboratively and their type (technically-aligned documents or common document).
|
| 259 |
+
|
| 260 |
+
NOTE 1 – It is recommended to use the template in Annex A of [b-ITU-T A.1];
|
| 261 |
+
|
| 262 |
+
- 6) detailed explanations on how to synchronize the ITU-T approval process (AAP according to [ITU-T A.8] or TAP according to section 9 of [WTSA Res. 1] or agreement at the study group level) with the approval process in the organization so that comments coming from one organization during the approval process can be taken into account by the other organization (see Annex D);
|
| 263 |
+
- 7) any start-up provisions to accommodate work in progress in each organization.
|
| 264 |
+
NOTE 2 – If the draft ITU-T Recommendation has been consented for AAP Last Call (or determined for TAP consultation), the window to establish a collaboration is considered to be closed;
|
| 265 |
+
- 8) any reporting or tracking provisions beyond those specified in clause B.6 or C.6;
|
| 266 |
+
- 9) explanations on how the document(s) would be cooperatively maintained by both organizations (see clause 10);
|
| 267 |
+
- 10) statement that the organization's patent policy is consistent with the common patent policy for ITU-T/ITU-R/ISO/IEC (see clause 11).
|
| 268 |
+
|
| 269 |
+
**8.3** A collaborative relationship for a given area of work continues as long as both organizations feel collaboration is beneficial. In the unusual event that either organization feels that collaboration for a given area of work may be terminated, it is recommended to discuss this situation immediately with the other organization. If satisfactory resolution cannot be obtained, then collaboration for the given area of work can be terminated at any time by either the ITU-T study group or the appropriate body in the organization. If termination occurs, both organizations can make use of the prior collaborative work.
|
| 270 |
+
|
| 271 |
+
## **9 Publication of documents**
|
| 272 |
+
|
| 273 |
+
**9.1** In the case of a common document, the final editing is done by ITU's Telecommunication Standardization Bureau (TSB) according to [b-Author's Guide]. TSB then sends the final document as soon as possible to the organization for publication according to its own rules.
|
| 274 |
+
|
| 275 |
+
NOTE – A unique document is developed jointly by ITU-T and an organization, but it may be published with different cover pages, headers and footers, based on the publication rules of each organization. Consequently, cover pages, header and footers do not contain any normative statement.
|
| 276 |
+
|
| 277 |
+
**9.2** In the case of technically-aligned documents, each organization publishes its own document according to its own publication rules. However, it is recommended that the organization waits for TSB to produce the final document for ITU-T in case some editorial changes would also apply to its own document.
|
| 278 |
+
|
| 279 |
+
**9.3** The document is published as a Recommendation in ITU-T and as a standard (or any other type of normative document) in the organization (or as a Supplement or any other type of informative document in ITU-T, and as an informative document in the organization).
|
| 280 |
+
|
| 281 |
+
**9.4** It is valuable that users perceive the collaboration between ITU-T and the organization. This may be enforced by the following means:
|
| 282 |
+
|
| 283 |
+
- a) Include a footnote from the title of the ITU-T document that notes the collaborative nature of the work; in the case of technically-aligned document, the footnote gives the title of the document of the organization, and states the degree of technical alignment.
|
| 284 |
+
- b) Include a footnote from the title of the document of the organization that notes the collaborative nature of the work; in the case of technically-aligned documents, the footnote gives the title of the ITU-T document, and states the degree of technical alignment.
|
| 285 |
+
- c) If an ITU-T document makes a reference to another ITU-T document that is a common document (or has a technically-aligned document in an organization), then include a footnote from the reference as in item a); if there are technical differences between both documents, then include an appendix or annex that summarizes the differences.
|
| 286 |
+
- d) If a document from the organization makes a reference to another document that is a common document (or has a technically-aligned document in ITU-T), then include a footnote from the reference as in item b); if there are technical differences between both documents, then include an appendix or annex that summarizes the differences.
|
| 287 |
+
|
| 288 |
+
**9.5** If any unusual circumstances arise to indicate that publication of a common document is no longer desired (e.g., because of substantial differences in content), this situation is immediately discussed with the other organization. If after the consultation either organization determines that common document publication is not appropriate, then each organization can publish separately using its own publication format.
|
| 289 |
+
|
| 290 |
+
## **10 Maintenance of documents**
|
| 291 |
+
|
| 292 |
+
**10.1** The work is not necessarily completed at the stage of publication. While every effort has been taken to produce a quality document, experience has shown that defects may be found as the document is being applied to implementations. Therefore, there is need for an ongoing shared responsibility for maintaining the document.
|
| 293 |
+
|
| 294 |
+
**10.2** It is critical that rapid correction of possible errors, omissions, inconsistencies, or ambiguities be performed cooperatively. It is recommended that the procedures for this important effort are outlined in the terms of reference of the chosen mode of collaboration (see clause 8.2).
|
| 295 |
+
|
| 296 |
+
**10.3** Further work is often identified as a result of the development process and as a result of changing technology and new operational requirements. Accordingly, there is an important need for amendments that provide expansions, enhancements and updates to the basic provisions of the published common (or technically-aligned) documents.
|
| 297 |
+
|
| 298 |
+
**10.4** The processing of amendments may follow the same procedures as the original development. These may be considered as extensions to the original work by the same collaborative work or common team, or may be considered as separate new work that requires the formation of a new collaborative work or a common team (see clause 8.2).
|
| 299 |
+
|
| 300 |
+
## **11 Patent policy and copyright arrangements**
|
| 301 |
+
|
| 302 |
+
For common (or technically-aligned) documents, organizations shall have a patent policy which is consistent with the common patent policy for ITU-T/ITU-R/ISO/IEC, and submit patent statements, as appropriate, to ITU-T and to the organization.
|
| 303 |
+
|
| 304 |
+
NOTE – Information pertaining to the common patent policy is available at <https://itu.int/en/ITU-T/ipr>.
|
| 305 |
+
|
| 306 |
+
## **Annex A**
|
| 307 |
+
|
| 308 |
+
### **Collaboration using the liaison mode**
|
| 309 |
+
|
| 310 |
+
(This annex forms an integral part of this Recommendation.)
|
| 311 |
+
|
| 312 |
+
Establishing a communication process provides a framework for ongoing communications to:
|
| 313 |
+
|
| 314 |
+
- prevent inadvertent duplication of effort, while allowing each organization to pursue its own mandate;
|
| 315 |
+
- provide authoritative information of one organization's dependencies on the other's work;
|
| 316 |
+
- exchange information on topics of mutual interest.
|
| 317 |
+
|
| 318 |
+
This annex applies to the communication process once the liaison mode of collaboration has been determined in accordance with clause 7.
|
| 319 |
+
|
| 320 |
+
**A.1** In some situations of common interest, it may be appropriate to reach an agreement that would allocate the standardization of a particular area of work to one organization. The basic concept of collaboration using the liaison mode is to allow the other organization to participate in the work, as appropriate, using its liaison status. The result is published by one organization and is referenced, as needed, by the other organization (see [ITU-T A.5]). If such an agreement cannot be reached, it is recommended that each organization does not produce a document whose implementation hampers interoperability with the implementation of a document of the other organization.
|
| 321 |
+
|
| 322 |
+
NOTE – Liaison statements can be exchanged with any external organization as necessary to progress the work (see clause 1.5 of [b-ITU-T A.1]). Qualification of the organization under Annex B of [ITU-T A.5] is not required.
|
| 323 |
+
|
| 324 |
+
**A.2** In some situations, authoritative document exchange between an ITU-T study group and an organization helps to strengthen the information flow between ITU-T and this organization. Such a framework for ongoing communications is particularly needed to provide authoritative information of one organization's dependencies on the other's work.
|
| 325 |
+
|
| 326 |
+
**A.3** All interactions between an ITU-T study group and the relevant group in the organization are conducted using the liaison procedures. In particular, this applies to participation in each other's meetings and to the submission of input documents.
|
| 327 |
+
|
| 328 |
+
NOTE – For example, for an individual to represent the relevant group of the organization in an ITU-T study group meeting, a letter (or liaison statement) from that organization is recommended authorizing such representation. Likewise, for an individual to represent an ITU-T Question in the meeting of an organization, a liaison statement from the ITU-T study group to that organization is recommended authorizing such representation.
|
| 329 |
+
|
| 330 |
+
**A.4** The decision to send a liaison statement is made by the study group. When necessary, between scheduled meetings, the liaison statement may be prepared by an appropriate correspondence process and approved by the study group chair in consultation with the study group management. The liaison statement is sent by TSB (on behalf of the study group) to the organization.
|
| 331 |
+
|
| 332 |
+
**A.5** The exchange of documents is to be done in electronic format. Questions of electronic links to enable document exchange are to be agreed upon by the secretariats of the organization concerned.
|
| 333 |
+
|
| 334 |
+
**A.6** Documents submitted to the ITU-T study group by the organization shall conform to the following criteria:
|
| 335 |
+
|
| 336 |
+
- a) contain no confidential information (i.e., no distribution restriction);
|
| 337 |
+
- b) indicate the source within the organization (e.g., committee, subcommittee, etc.);
|
| 338 |
+
- c) differentiate between normative references and non-normative references.
|
| 339 |
+
|
| 340 |
+
**A.7** Documents submitted to the ITU-T study group are not issued as contributions but as a TD at a study group or working party meeting, or as a document at a rapporteur meeting. As soon as they arrive, they are made available, with the agreement of the study group chair, for advance consideration by the relevant group. Moreover, they are issued with a reference to the originating organization.
|
| 341 |
+
|
| 342 |
+
## **Annex B**
|
| 343 |
+
|
| 344 |
+
### **Collaboration using collaborative work**
|
| 345 |
+
|
| 346 |
+
(This annex forms an integral part of this Recommendation.)
|
| 347 |
+
|
| 348 |
+
The basic concept of collaboration using collaborative work is to closely couple the development, consensus building, and ballot/comment resolution efforts of an ITU-T Question and of the relevant group in an organization in an efficient and effective manner to produce mutually agreed common (or technically-aligned) documents.
|
| 349 |
+
|
| 350 |
+
This annex applies when the collaborative mode of work is selected as per clause 7.
|
| 351 |
+
|
| 352 |
+
### **B.1 Establishing a collaborative work**
|
| 353 |
+
|
| 354 |
+
**B.1.1** Upon agreement by the ITU-T study group and the relevant group in the organization that a specific area of work is to be developed collaboratively, a collaborative work is established between the respective ITU-T Question and group in the organization (see clause 8.2).
|
| 355 |
+
|
| 356 |
+
**B.1.2** The ITU-T Question and the relevant group in the organization function using the procedures of their respective organization, but with certain additional procedures, as described below, to facilitate closer collaboration in building consensus and synchronization of approvals leading to the publication of common (or technically-aligned) documents (see Annex D).
|
| 357 |
+
|
| 358 |
+
**B.1.3** During the time of development of a common (or technically-aligned) document, it is important that communication is consistently maintained between organizations by exchanging the different versions of the draft document as it evolves (see also clause B.4).
|
| 359 |
+
|
| 360 |
+
**B.1.4** The terms of reference (see clause 8.2), including the mode of collaboration, can be changed at any time by mutual agreement of the ITU-T study group and of the relevant group in the organization. It is recommended that collaboration also continues for the ongoing maintenance phase (see clause 10). Procedures for terminating a collaborative work are covered in clause 8.4.
|
| 361 |
+
|
| 362 |
+
### **B.2 Participation in meetings of the other organization**
|
| 363 |
+
|
| 364 |
+
**B.2.1** The collaborative work is facilitated if there is some significant degree of common participation by individuals in the meetings of both organizations.
|
| 365 |
+
|
| 366 |
+
**B.2.2** Representation of one organization in a meeting of the other organization is achieved by means of liaison officers (see clause A.3). It is recommended that individuals attending meetings in a liaison capacity are familiar with the procedures of the organization holding the meeting.
|
| 367 |
+
|
| 368 |
+
NOTE – The fact that a liaison officer officially represents one organization in a meeting of the other organization does not preclude experts from that organization from participating in the meeting of the other organization as explained in clause B.2.1. In that case, each expert participates according to his/her membership in the relevant organization.
|
| 369 |
+
|
| 370 |
+
### **B.3 Contributions**
|
| 371 |
+
|
| 372 |
+
Contributions are handled by each organization according to its normal procedures (e.g., clause 3 of [b-ITU-T A.1] for ITU-T). In addition, it is important that the results of analysis of contributions be passed promptly to the other organization.
|
| 373 |
+
|
| 374 |
+
### **B.4 Editors for a common document**
|
| 375 |
+
|
| 376 |
+
NOTE – In the case of technically-aligned documents, each organization nominates one or more Editor(s) for its own document.
|
| 377 |
+
|
| 378 |
+
**B.4.1** It is strongly recommended that the ITU-T Question and the relevant group in the organization agree on a single Editor who will produce and maintain the single master common document, normally in accordance with the [b-Author's Guide].
|
| 379 |
+
|
| 380 |
+
**B.4.2** The draft master common document will be updated only when agreement to the specific text has been made by both organizations. Each iteration of the draft common document is dated. Changes from the previous draft are highlighted by change marks.
|
| 381 |
+
|
| 382 |
+
**B.4.3** The appointed Editor is responsible for the common document through draft iterations and final submission to the secretariats for publication (see clause 9). The individual selected for this task commits to following the work through to completion so that continuity can be maintained.
|
| 383 |
+
|
| 384 |
+
### **B.5 Achieving consensus**
|
| 385 |
+
|
| 386 |
+
**B.5.1** Close liaison is maintained during the development of draft documents, and resolution of ballots and comments to ensure that the views of all concerned are taken into account in building consensus.
|
| 387 |
+
|
| 388 |
+
**B.5.2** In general, the intent is that the degree of consensus and the stability of the agreements will increase at each step of the collaborative process.
|
| 389 |
+
|
| 390 |
+
**B.5.3** In rare cases, it may become apparent during the development of a common document that one or more specific technical differences are necessary in order to take into account the needs of ITU-T and of the organization. All proposed differences are carefully examined to ensure there is a legitimate need for these. In such a case, the common document is to include the full technical material needed by each organization with wording that specifically identifies any text that is applicable only to one organization. If consensus cannot be reached, the collaboration may cease as specified in clause 8.3.
|
| 391 |
+
|
| 392 |
+
### **B.6 Progress reporting**
|
| 393 |
+
|
| 394 |
+
**B.6.1** The ITU-T Question is responsible for providing written reports of its meetings to its parent study group. Similarly, the group in the organization is responsible for reporting the results of its meetings to its parent group following normal procedures. These reports summarize the results of the meeting including agreements reached, areas identified for further study, the status of collaborative progress, and projected upcoming milestones (see Annex D).
|
| 395 |
+
|
| 396 |
+
**B.6.2** These reports, or appropriate extracts, are conveyed to the other group using the normal liaison procedure (see Annex A). Meeting reports contain sufficient information to enable the collaborative work to mutually progress in both organizations as effectively as possible.
|
| 397 |
+
|
| 398 |
+
## **Annex C**
|
| 399 |
+
|
| 400 |
+
### **Collaboration using a common team**
|
| 401 |
+
|
| 402 |
+
(This annex forms an integral part of this Recommendation.)
|
| 403 |
+
|
| 404 |
+
The basic concept of collaboration using a common team is that all development, consensus building, and ballot/comment resolution efforts are performed in common meetings to produce mutually agreed common (or technically-aligned) documents.
|
| 405 |
+
|
| 406 |
+
This annex applies when the common team collaboration mode is selected as per clause 7.
|
| 407 |
+
|
| 408 |
+
### **C.1 Establishing a common team**
|
| 409 |
+
|
| 410 |
+
**C.1.1** Upon agreement by the ITU-T study group and the relevant group in the organization that a specific area of work is to be developed collaboratively in common meetings, a common team is established with participants from both organizations (see clause 8.2).
|
| 411 |
+
|
| 412 |
+
**C.1.2** The common team has either a single convenor agreed upon by the ITU-T study group and the relevant group in the organization, or co-convenors, one appointed by each organization. In the case of co-convenors, the chairing of meetings can be on a rotational basis or as otherwise agreed by the common team.
|
| 413 |
+
|
| 414 |
+
**C.1.3** Eligibility for attendance at a common team meeting is determined by the requirements of each organization.
|
| 415 |
+
|
| 416 |
+
**C.1.4** The common team uses the procedures described below to build consensus and to achieve synchronization of approvals with the aim of publishing common (or technically-aligned) documents (see Annex D).
|
| 417 |
+
|
| 418 |
+
**C.1.5** The terms of reference (see clause 8.2) or mode of collaboration can be changed at any time by mutual agreement of the ITU-T study group and of the relevant group in the organization. It is recommended that collaboration also continues for the ongoing maintenance phase (see clause 10). Procedures for terminating a collaborative work are covered in clause 8.3.
|
| 419 |
+
|
| 420 |
+
### **C.2 Meetings**
|
| 421 |
+
|
| 422 |
+
**C.2.1** Each common team meeting is properly scheduled in advance. The common team is responsible for making its own meeting arrangements and schedule, subject to agreement by the ITU-T study group and by the organization. In ITU-T, a meeting of the common team is considered as a rapporteur meeting of the relevant Question (see clauses 2.3.3.10 to 2.3.3.15 of [b-ITU-T A.1]).
|
| 423 |
+
|
| 424 |
+
**C.2.2** Generally, hosts for common team meetings alternate between ITU-T and the organization, but they may also be cooperatively hosted with appropriate agreement. It is recommended that common team meetings be scheduled at the same location and time as the respective ITU-T study group or relevant group in the organization, although meetings may also be scheduled at other times and locations.
|
| 425 |
+
|
| 426 |
+
**C.2.3** It is recommended that the convenor(s) of the common team maintain a mailing list of all individuals who wish to be informed of the meetings of the common team.
|
| 427 |
+
|
| 428 |
+
**C.2.4** Meeting notices and the agenda respect the deadlines of both ITU-T (e.g., a convening letter for rapporteur meetings is posted, normally at least two months prior to the meeting, on the study group webpage) and the organization. It is recommended that the meeting notice identifies the meeting as one of both ITU-T and the organization, and that the meeting notice and agenda are sent for posting to the ITU-T study group secretariat and to the secretariat of the organization. Each agenda provides a list of documents to be considered, including previous meeting reports and input contributions (see clause C3).
|
| 429 |
+
|
| 430 |
+
**C.2.5** Communication between an ITU-T Question (or rapporteur group) and a common team is also done through liaison statements. It is expected that the relevant group in the organization also communicates with a common team by way of liaison statements.
|
| 431 |
+
|
| 432 |
+
### **C.3 Contributions**
|
| 433 |
+
|
| 434 |
+
**C.3.1** Contributions to the work of the common team may be provided by ITU-T members or by members of the organization. Each contribution indicates its source.
|
| 435 |
+
|
| 436 |
+
**C.3.2** Contributions to be considered at a common team meeting are normally in the hands of the common team convenor(s) at least twelve calendar days before the start of the meeting. Late contributions will only be considered upon agreement by the meeting participants, in particular to accommodate particular deadlines or meeting dates of the organization.
|
| 437 |
+
|
| 438 |
+
**C.3.3** All contributions to the common team, regardless of their means of submission, will be identified and maintained by the common team in a document register.
|
| 439 |
+
|
| 440 |
+
**C.3.4** It is recommended that the convenor(s) maintain a mailing list of the common team participants and ensure timely distribution of contributions and meeting output documents to eligible participants.
|
| 441 |
+
|
| 442 |
+
### **C.4 Editor in case of a common document**
|
| 443 |
+
|
| 444 |
+
NOTE – In the case of technically-aligned documents, each organization nominates one or more Editor(s) for its own document.
|
| 445 |
+
|
| 446 |
+
**C.4.1** It is strongly recommended that the common team appoints a single Editor to produce and maintain the single master common document, normally in accordance with [b-Author's Guide].
|
| 447 |
+
|
| 448 |
+
**C.4.2** The draft master common document will be updated only when agreement to the specific text has been made by the common team. Each iteration of the draft common document are dated. Changes from the previous draft are highlighted by change marks.
|
| 449 |
+
|
| 450 |
+
**C.4.3** The appointed Editor is responsible for the common document through draft iterations and final submission to the secretariats for publication (see clause 9). The individual selected for this task commits to following the work until publication so that continuity can be maintained throughout the effort.
|
| 451 |
+
|
| 452 |
+
### **C.5 Achieving consensus**
|
| 453 |
+
|
| 454 |
+
**C.5.1** The functions of the common team meetings are three-fold: the development and editing of draft documents, and resolution of ballots and comments. The common team meetings are only authorized to deal with the specific collaborative projects identified in the terms of reference (see clause 8.2).
|
| 455 |
+
|
| 456 |
+
**C.5.2** In responding to the requirements of the designated collaborative projects, the development of draft documents is a consensus building process.
|
| 457 |
+
|
| 458 |
+
**C.5.3** Balloting, or voting, by the common team during the development of draft documents is considered inappropriate in reaching a consensus and could be counter-productive. The common team consensus is built through discussion, acceptance, compromise, and, if necessary, informal polling of delegates to sample the state of agreement. It would also be appropriate to record in meeting reports points of consensus, as well as any specific reservations that meeting delegates have on particular issues.
|
| 459 |
+
|
| 460 |
+
**C.5.4** Topics of concern to only the ITU-T or to only the organization may be addressed by sub-group meetings held within the framework of the common team meeting.
|
| 461 |
+
|
| 462 |
+
**C.5.5** In rare cases, it may become apparent during the development of a common document that one or more specific technical differences are necessary in order to take into account the needs of ITU-T and of the organization. All proposed differences are carefully examined to ensure there is a legitimate need for these. In such a case, the common document is to include the full technical material needed by each organization with wording that specifically identifies any text that is applicable only to one organization.
|
| 463 |
+
|
| 464 |
+
**C.5.6** The approval processes will be conducted according to the established procedures of each organization with the adaptation and synchronization described in Annex D. It is recommended to convene a ballot resolution meeting as soon as practical after the close of a ballot/comment period to review and resolve the results. The group is normally chaired by the common team convenor(s) or the editor of the draft document.
|
| 465 |
+
|
| 466 |
+
**C.5.7** The purpose of a ballot resolution meeting is to resolve as many of the negative comments as possible without invalidating any affirmative positions. The goal is to achieve agreements resulting in the greatest possible consensus. This can be done provided that all affected representatives are satisfied with the handling of the comments.
|
| 467 |
+
|
| 468 |
+
### **C.6 Progress reporting**
|
| 469 |
+
|
| 470 |
+
**C.6.1** The common team is responsible for providing written reports of each meeting to the ITU-T study group and to the relevant group in the organization. These reports summarize the results of the meeting including agreements reached, areas identified for further study, the status of collaborative progress, and projected upcoming milestones (see Annex D).
|
| 471 |
+
|
| 472 |
+
**C.6.2** Comments and/or instructions may be provided back to the common team from the ITU-T study group and from the relevant group in the organization.
|
| 473 |
+
|
| 474 |
+
## Annex D
|
| 475 |
+
|
| 476 |
+
### Synchronization of approval processes
|
| 477 |
+
|
| 478 |
+
(This annex forms an integral part of this Recommendation.)
|
| 479 |
+
|
| 480 |
+
To facilitate closer collaboration in building consensus, this appendix explains how to synchronize approvals between the ITU-T study group and the organization in order to lead to the publication of common (or technically-aligned) documents.
|
| 481 |
+
|
| 482 |
+
**D.1** Each organization retains its individual procedures for approving the result of the collaboration work. The following clauses describe how these procedures are synchronized for the different stages of approval.
|
| 483 |
+
|
| 484 |
+
NOTE – In the case of the development of technically-aligned documents, the approval processes do not require exact timing synchronization as explained below. In the case of the development of non-normative documents (i.e., Supplements or other types of non-normative documents in ITU-T), the following process needs to be adapted.
|
| 485 |
+
|
| 486 |
+
**D.2** As outlined in clause B.6 (in the case of collaborative work), each group keeps its parent body informed of the progress of the collaborative work. As outlined in clause C.6 (in the case of a common team), the common team keeps the ITU-T Question and the relevant group in the organization informed of the progress of the collaborative work. When the work has progressed to a point where a schedule for synchronized approval can be established with a degree of confidence, it is important for the two groups (in the case of collaborative work) or the common team to jointly plan the specific steps, taking into account scheduled dates of meetings of the ITU-T study group and of the relevant group in the organization.
|
| 487 |
+
|
| 488 |
+
**D.3** When the groups (in case of collaborative work) or the common team decide that the draft has reached a point of maturity and that the synchronized approval process may commence, each organization is advised of the decision.
|
| 489 |
+
|
| 490 |
+
**D.4** The following subclauses only apply if the organization has one or more intermediate levels of balloting (before final balloting for approval).
|
| 491 |
+
|
| 492 |
+
**D.4.1** The organization distributes the draft document for comment to its members.
|
| 493 |
+
|
| 494 |
+
**D.4.2** At the same time, the draft document is distributed to the ITU-T study group members for review and comment. ITU-T member comments are provided by means of contributions within the same time period. The organization considers all responses together.
|
| 495 |
+
|
| 496 |
+
**D.4.3** In the case of collaborative work, both sets of responses are made available to the ITU-T Question as well as to the relevant group in the organization. Both groups coordinate their efforts in resolving all received comments and producing the revised draft document.
|
| 497 |
+
|
| 498 |
+
**D.4.4** In the case of a common team, both sets of responses are made available to the common team which resolves all received comments and produces the revised draft document (see clauses C.5.6 and C.5.7).
|
| 499 |
+
|
| 500 |
+
**D.4.5** If the changes are substantive and if another intermediate level of balloting (before final balloting for approval) is available in the organization, clause D.4 is recursively applied.
|
| 501 |
+
|
| 502 |
+
**D.5** When all issues have been resolved to the satisfaction of both organizations, the organization conducts the final balloting for approval according to the following subclauses.
|
| 503 |
+
|
| 504 |
+
NOTE – If a problem is indicated on the side of the organization which would delay approval, this is immediately conveyed to the ITU-T study group so that appropriate action can be taken and, if necessary, a new synchronized plan established.
|
| 505 |
+
|
| 506 |
+
**D.5.1** At the same time, the draft document is distributed to the ITU-T study group members for review and comment. ITU-T member comments are provided by means of contributions within the same time period. The organization considers all responses together.
|
| 507 |
+
|
| 508 |
+
**D.5.2** Also during this time period, TSB will review the document and submit comments, if any.
|
| 509 |
+
|
| 510 |
+
**D.5.3** In the case of collaborative work, both sets of responses are made available to the ITU-T Question as well as to the relevant group in the organization. Both groups coordinate their efforts in resolving all received comments and producing the revised draft document.
|
| 511 |
+
|
| 512 |
+
**D.5.4** In the case of a common team, both sets of responses are made available to the common team which resolves all received comments and produces the revised draft document (see clauses C.5.6 and C.5.7).
|
| 513 |
+
|
| 514 |
+
**D.5.5** It is at this point where synchronization is critical. The first controlling factor is the date of the ITU-T study group (or working party) meeting where determination (TAP) or consent (AAP) or agreement (non-normative documents) is to be obtained. At this meeting, the balloting has normally concluded in the organization and a revised draft document is published as a TD in time for the ITU-T study group (or working party) meeting. However, the ITU-T study group (or working party) meeting may accept to consent (for AAP) or determine (for TAP) a draft document pending further adjustments based on the result of the balloting in the organization.
|
| 515 |
+
|
| 516 |
+
NOTE – It is understood that the stable draft document would always be available for comments to ITU members for the AAP Last Call or TAP consultation (see clause D.5.6).
|
| 517 |
+
|
| 518 |
+
**D.5.6** The second controlling factor is that the balloting has concluded in the organization and a revised draft document is produced for ITU-T approval:
|
| 519 |
+
|
| 520 |
+
- a) for TAP: by 4 months before the ITU-T study group (or working party) meeting where approval is to be obtained so that the Director of TSB can issue a letter announcing the intent to approve the Recommendation at the upcoming study group (or working party) meeting;
|
| 521 |
+
- b) for AAP: normally by 2 months after the ITU-T study group (or working party) meeting where consent was obtained so that the Director of TSB can announce the Last Call for approval of the Recommendation;
|
| 522 |
+
- c) for agreement (in case of non-normative documents): at least seven calendar days before the ITU-T study group (or working party) meeting (see clause 3.3.3 of [b-ITU-T A.1]).
|
| 523 |
+
|
| 524 |
+
**D.6** If no negative votes and no technical comments are submitted during the AAP Last Call or the TAP consultation, or discussion at the study group (or working party) meeting in case of agreement, and if, in the case of TAP, the following ITU-T study group (or working party) meeting approves the document, the organization is informed and the document is published according to clause 9.
|
| 525 |
+
|
| 526 |
+
**D.7** If negative votes and/or technical comments are submitted during the AAP Last Call or the TAP consultation, or if comments are made at the study group (or working party) meeting in the case of agreement, the comments are resolved according to the following subclauses.
|
| 527 |
+
|
| 528 |
+
NOTE – If an ITU-T Member State indicates a problem which would prevent approval, this is immediately conveyed to the organization so that appropriate action can be taken and, if necessary, a new synchronized plan established.
|
| 529 |
+
|
| 530 |
+
**D.7.1** In the case of collaborative work, the ITU-T Question resolves all received comments and produces the revised draft document. Comments and the revised draft document are also made available to the organization.
|
| 531 |
+
|
| 532 |
+
**D.7.2** In the case of a common team, the team resolves comments and produces the revised draft document (see clauses C.5.6 and C.5.7).
|
| 533 |
+
|
| 534 |
+
**D.7.3** If the changes are substantive, this is immediately conveyed to the organization to find an appropriate solution:
|
| 535 |
+
|
| 536 |
+
- a) In case of technically-aligned documents, the organization considers whether some or all of the changes can be applied to its own document or if the documents are published separately.
|
| 537 |
+
- b) In case of a common document, if the organization can conduct another final balloting for approval, clause D.5 is applied once again (for an additional review in ITU-T in the case of AAP) and the approval in ITU-T is delayed.
|
| 538 |
+
- c) Otherwise, the ITU-T study group and the organization may decide to publish the document as either technically-aligned documents or separately.
|
| 539 |
+
|
| 540 |
+
## **Annex E**
|
| 541 |
+
|
| 542 |
+
### **Multilateral collaboration**
|
| 543 |
+
|
| 544 |
+
(This annex forms an integral part of this Recommendation.)
|
| 545 |
+
|
| 546 |
+
This annex explains how the processes described in previous annexes can be generalized to a multilateral collaboration (including the development of multiple documents) between ITU-T and more than one organization in a given area of work, while avoiding the approval of multiple bilateral agreements.
|
| 547 |
+
|
| 548 |
+
NOTE – The rest of this Recommendation covers bilateral collaboration as this is the most common case. In case of multilateral collaboration as introduced in this annex, some parts of the text (e.g., "the other organization", "two", "both") should be understood to apply to multiple organizations according to the conventions given in clause 5.
|
| 549 |
+
|
| 550 |
+
**E.1** When it is recognized that other organizations are working on the same area as an ITU-T study group and that coordination with them is complicated, the study group may consider establishing a multilateral collaboration to avoid incompatibility between standards and for a more efficient use of resources.
|
| 551 |
+
|
| 552 |
+
NOTE 1 – Before establishing multilateral collaboration as outlined in this annex, the study group is expected to investigate whether a focus group (see [b-ITU-T A.7]) is feasible.
|
| 553 |
+
|
| 554 |
+
NOTE 2 – This annex does not apply when the multilateral collaboration only involves ITU-T and ITU-R study groups because an intersector coordination group or an intersector rapporteur group can then be established (see Annexes B and C of [b-WTSA Res. 18]). The Inter-Sector Coordination Team could also consider the matter.
|
| 555 |
+
|
| 556 |
+
**E.2** Each of the organizations involved in multilateral collaboration needs to be qualified (see clause 6).
|
| 557 |
+
|
| 558 |
+
**E.3** The terms of reference for the multilateral collaboration are established as explained in clause 8.2. Different instances of the three modes of collaboration (see clause 7) may be described, depending on the subset of organizations involved in the development of particular common (or technically-aligned) documents. The terms of reference are mutually agreed by all organizations involved in the multilateral collaboration.
|
| 559 |
+
|
| 560 |
+
## Bibliography
|
| 561 |
+
|
| 562 |
+
- [b-ITU-T A.1] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector (ITU-T)*.
|
| 563 |
+
- [b-ITU-T A.7] Recommendation ITU-T A.7 (2024), *Focus groups: Establishment and working procedures*.
|
| 564 |
+
- [b-ITU-T A.13] Recommendation ITU-T A.13 (2019), *Non-normative ITU-T publications, including Supplements to ITU-T Recommendations*.
|
| 565 |
+
- [b-ITU-T A.23] Recommendation ITU-T A.23 (2000), *Collaboration with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on information technology*.
|
| 566 |
+
- [b-ITU-T A.25] Recommendation ITU-T A.25 (2022), *Generic procedures for incorporating texts between ITU-T and other organizations*.
|
| 567 |
+
- [b-ITU-T A-Suppl.3] ITU-T A-series Recommendations – Supplement 3 (2012), *IETF and ITU-T collaboration guidelines*.
|
| 568 |
+
- [b-Author's Guide] *Author's Guide for drafting ITU-T Recommendations*.
|
| 569 |
+
<<https://www.itu.int/ITU-T/go/authors-guide/>>
|
| 570 |
+
- [b-WTSA Res. 18] World Telecommunication Standardization Assembly Resolution 18 (Rev. Geneva, 2022), *Principles and procedures for the allocation of work to, and strengthening coordination and cooperation among, the ITU Radiocommunication, ITU Telecommunication Standardization and ITU Telecommunication Development Sectors*.
|
| 571 |
+
<<https://www.itu.int/pub/T-RES-T.18-2022>>
|
| 572 |
+
|
| 573 |
+
|
| 574 |
+
|
| 575 |
+
|
| 576 |
+
|
| 577 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 578 |
+
|
| 579 |
+
| | |
|
| 580 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 581 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 582 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 583 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 584 |
+
| Series F | Non-telephone telecommunication services |
|
| 585 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 586 |
+
| Series H | Audiovisual and multimedia systems |
|
| 587 |
+
| Series I | Integrated services digital network |
|
| 588 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 589 |
+
| Series K | Protection against interference |
|
| 590 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 591 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 592 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 593 |
+
| Series O | Specifications of measuring equipment |
|
| 594 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 595 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 596 |
+
| Series R | Telegraph transmission |
|
| 597 |
+
| Series S | Telegraph services terminal equipment |
|
| 598 |
+
| Series T | Terminals for telematic services |
|
| 599 |
+
| Series U | Telegraph switching |
|
| 600 |
+
| Series V | Data communication over the telephone network |
|
| 601 |
+
| Series X | Data networks, open system communications and security |
|
| 602 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 603 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.25-202410-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.25-202410-I_PDF-E/b945a88ff54102a7b3b480f9483dacab_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.25-202410-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,369 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Recommendation **ITU-T A.25 (10/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
## **Generic procedures for incorporating text between ITU-T and other organizations**
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
# Recommendation ITU-T A.25
|
| 14 |
+
|
| 15 |
+
## Generic procedures for incorporating text between ITU-T and other organizations
|
| 16 |
+
|
| 17 |
+
## Summary
|
| 18 |
+
|
| 19 |
+
Recommendation ITU-T A.25 addresses the process of incorporating text (in whole or in part, with or without modification) of documents from another organization into an ITU-T Recommendation (or another ITU-T document). Similarly, guidance is provided for other organizations incorporating text (in whole or in part, with or without modification) from ITU-T Recommendations (or other ITU-T documents) in their documents.
|
| 20 |
+
|
| 21 |
+
## History\*
|
| 22 |
+
|
| 23 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 24 |
+
|---------|----------------|------------|-------------|--------------------|
|
| 25 |
+
| 1.0 | ITU-T A.25 | 2016-02-05 | TSAG | 11.1002/1000/12573 |
|
| 26 |
+
| 2.0 | ITU-T A.25 | 2019-09-27 | TSAG | 11.1002/1000/13854 |
|
| 27 |
+
| 3.0 | ITU-T A.25 | 2022-03-09 | WTSA | 11.1002/1000/14987 |
|
| 28 |
+
| 4.0 | ITU-T A.25 | 2024-10-23 | WTSA | 11.1002/1000/16200 |
|
| 29 |
+
|
| 30 |
+
## Keywords
|
| 31 |
+
|
| 32 |
+
Copying text, incorporating text, qualification, references.
|
| 33 |
+
|
| 34 |
+
---
|
| 35 |
+
|
| 36 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 37 |
+
|
| 38 |
+
## FOREWORD
|
| 39 |
+
|
| 40 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 41 |
+
|
| 42 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 43 |
+
|
| 44 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 45 |
+
|
| 46 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 47 |
+
|
| 48 |
+
## NOTE
|
| 49 |
+
|
| 50 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 51 |
+
|
| 52 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 53 |
+
|
| 54 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 55 |
+
|
| 56 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 57 |
+
|
| 58 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 59 |
+
|
| 60 |
+
© ITU 2024
|
| 61 |
+
|
| 62 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 63 |
+
|
| 64 |
+
## Table of Contents
|
| 65 |
+
|
| 66 |
+
| | | Page |
|
| 67 |
+
|---|---------------------------------------------------------------------------------------------------------------------------------------------------------|------|
|
| 68 |
+
| 1 | Scope..... | 1 |
|
| 69 |
+
| 2 | References..... | 1 |
|
| 70 |
+
| 3 | Definitions ..... | 1 |
|
| 71 |
+
| | 3.1 Terms defined elsewhere..... | 1 |
|
| 72 |
+
| | 3.2 Terms defined in this Recommendation..... | 1 |
|
| 73 |
+
| 4 | Abbreviations and acronyms ..... | 2 |
|
| 74 |
+
| 5 | Conventions ..... | 2 |
|
| 75 |
+
| 6 | Generic procedures for incorporating text of other organizations in ITU-T documents..... | 2 |
|
| 76 |
+
| | 6.1 Process for incorporation..... | 2 |
|
| 77 |
+
| | 6.2 Permission arrangements..... | 4 |
|
| 78 |
+
| | 6.3 Copyright arrangements ..... | 4 |
|
| 79 |
+
| 7 | Generic procedures for incorporating text of ITU-T documents in the documents of other organizations..... | 4 |
|
| 80 |
+
| | 7.1 Documents sent to other organizations..... | 4 |
|
| 81 |
+
| | 7.2 Permission arrangements..... | 5 |
|
| 82 |
+
| | 7.3 Copyright arrangements ..... | 5 |
|
| 83 |
+
| | Appendix I – Workflow for incorporating text of another organization..... | 6 |
|
| 84 |
+
| | Appendix II – Format for documenting a study group or working party decision..... | 7 |
|
| 85 |
+
| | II.1 Description of the referenced document (incl. full copy)..... | 7 |
|
| 86 |
+
| | II.2 Status of approval ..... | 7 |
|
| 87 |
+
| | II.3 Justification for the specific incorporation ..... | 7 |
|
| 88 |
+
| | II.4 Intellectual property rights (patents, copyrights for software or text, marks) issues, if any, related to the proposed text for incorporation..... | 7 |
|
| 89 |
+
| | II.5 Proper names and trademarks of specific companies/organizations, products or services ..... | 7 |
|
| 90 |
+
| | II.6 Other information ..... | 7 |
|
| 91 |
+
| | II.7 Stability or maturity of the document..... | 7 |
|
| 92 |
+
| | II.8 Relationship with other existing or emerging documents ..... | 8 |
|
| 93 |
+
| | II.9 List of normative references within the incorporated document..... | 8 |
|
| 94 |
+
| | II.10 Qualification of the organization (per Annex B of [ITU-T A.5]) ..... | 8 |
|
| 95 |
+
| | II.11 Document maintenance process ..... | 8 |
|
| 96 |
+
| | Bibliography..... | 9 |
|
| 97 |
+
|
| 98 |
+
|
| 99 |
+
|
| 100 |
+
# Recommendation ITU-T A.25
|
| 101 |
+
|
| 102 |
+
## Generic procedures for incorporating text between ITU-T and other organizations
|
| 103 |
+
|
| 104 |
+
## 1 Scope
|
| 105 |
+
|
| 106 |
+
This Recommendation provides generic procedures for incorporating (in whole or in part, with or without modification) the documents of other organizations (including consortia, forums, and national and regional standards development organizations) in ITU-T Recommendations (or other ITU-T documents) and provides guidance for other organizations on how to incorporate ITU-T Recommendations (or other ITU-T documents), in whole or in part, in their documents. These procedures are applied each time a proposal for incorporation is made.
|
| 107 |
+
|
| 108 |
+
The case of normatively referencing the documents of other organizations in ITU-T Recommendations is addressed in [ITU-T A.5].
|
| 109 |
+
|
| 110 |
+
## 2 References
|
| 111 |
+
|
| 112 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 113 |
+
|
| 114 |
+
- [ITU-T A.5] Recommendation ITU-T A.5 (2022), *Generic procedures for including references to documents of other organizations in ITU-T Recommendations*.
|
| 115 |
+
- [PP Res. 66] Plenipotentiary Conference Resolution 66 (Rev. Bucharest, 2022), *Documents and publication of the Union*.
|
| 116 |
+
|
| 117 |
+
## 3 Definitions
|
| 118 |
+
|
| 119 |
+
### 3.1 Terms defined elsewhere
|
| 120 |
+
|
| 121 |
+
This Recommendation uses the following terms defined elsewhere:
|
| 122 |
+
|
| 123 |
+
- 3.1.1 approved document** [ITU-T A.5]: An official output (such as a standard, a specification, an implementation agreement, etc.) which has been formally approved by an organization.
|
| 124 |
+
- 3.1.2 non-normative reference** [ITU-T A.5]: The whole or parts of a document where the referenced document has been used as supplementary information in the preparation of the Recommendation or to assist the understanding or use of the Recommendation, and to which conformance is not necessary.
|
| 125 |
+
- 3.1.3 normative reference** [b-ITU-T A.1]: The whole or parts of another document where the referenced document contains provisions which, through reference to it, constitute provisions to the referring document.
|
| 126 |
+
|
| 127 |
+
### 3.2 Terms defined in this Recommendation
|
| 128 |
+
|
| 129 |
+
This Recommendation defines the following term:
|
| 130 |
+
|
| 131 |
+
- 3.2.1 draft document:** An output from an organization, which is still in draft form.
|
| 132 |
+
|
| 133 |
+
## **4 Abbreviations and acronyms**
|
| 134 |
+
|
| 135 |
+
This Recommendation uses the following abbreviations and acronyms:
|
| 136 |
+
|
| 137 |
+
TSB Telecommunication Standardization Bureau
|
| 138 |
+
|
| 139 |
+
## **5 Conventions**
|
| 140 |
+
|
| 141 |
+
None.
|
| 142 |
+
|
| 143 |
+
## **6 Generic procedures for incorporating text of other organizations in ITU-T documents**
|
| 144 |
+
|
| 145 |
+
This clause addresses the process of incorporating text (in whole or in part) from another organization into an ITU-T document (see the diagram in Appendix I). This process is expected to be rarely used because ITU-T study groups are encouraged to rather use the normative reference process explained in [ITU-T A.5].
|
| 146 |
+
|
| 147 |
+
### **6.1 Process for incorporation**
|
| 148 |
+
|
| 149 |
+
**6.1.1** An ITU-T study group or ITU-T members may identify the need to specifically incorporate text (in whole or in part, with or without modification) from a draft or approved document from another organization within a draft ITU-T Recommendation (or another draft ITU-T document). The need to incorporate text may also be identified by the organization itself. ITU-T study groups are strongly encouraged to incorporate approved text rather than draft text from other organizations and, whenever possible, to incorporate text without modification.
|
| 150 |
+
|
| 151 |
+
**6.1.2** Information to explain why incorporation was chosen over a normative reference should be provided in a TD (or a contribution), as outlined in clauses 6.1.2.1 to 6.1.2.10 (see also Appendix II).
|
| 152 |
+
|
| 153 |
+
**6.1.2.1** Description of the referenced document (incl. full copy): A clear description of the document considered for incorporation (type of document, title, number, version, date, etc.). (See also clause 6.2.2.)
|
| 154 |
+
|
| 155 |
+
**6.1.2.2** Status of approval: Incorporating text that has not yet been approved by the organization can lead to confusion; thus, incorporating is usually limited to approved documents. If absolutely necessary, incorporation of text from a draft document can be made where cooperative work requiring cross-incorporation is being approved by ITU-T and another organization in approximately the same time frame.
|
| 156 |
+
|
| 157 |
+
**6.1.2.3** Justification for the specific incorporation, including why it is inappropriate to reference the text in the draft ITU-T Recommendation (or other draft ITU-T document).
|
| 158 |
+
|
| 159 |
+
**6.1.2.4** Intellectual property rights<sup>1</sup> (patents, copyrights for software or texts, marks) issues, if any, related and specific to the proposed text for incorporation: See clauses 6.2 and 6.3. Relevant documents should be attached.
|
| 160 |
+
|
| 161 |
+
**6.1.2.5** Other information that might be useful in describing the "quality" of the document (e.g., whether products have been implemented using it, whether conformance requirements are clear, whether the specification is readily and widely available).
|
| 162 |
+
|
| 163 |
+
**6.1.2.6** Degree of stability or maturity of the document (e.g., length of time it has existed).
|
| 164 |
+
|
| 165 |
+
**6.1.2.7** Relationship with other existing or emerging documents.
|
| 166 |
+
|
| 167 |
+
**6.1.2.8** List of normative references within the incorporated document: All normative references within the incorporated document should be listed (see also clause 6.2.2 c).
|
| 168 |
+
|
| 169 |
+
---
|
| 170 |
+
|
| 171 |
+
<sup>1</sup> See: <https://www.itu.int/ipr>.
|
| 172 |
+
|
| 173 |
+
**6.1.2.9** Qualification of the organization (per Annex B of [ITU-T A.5]): This needs to be done only the first time a document from the organization is being considered for incorporation, and only if such qualification information has not been already documented. Qualification of an organization is reviewed on a regular basis (any study group willing to incorporate a document from the organization may perform the review). In particular, if the patent policy of that organization has changed, it is important to check that the new patent policy is consistent with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC and the Guidelines for the Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC.
|
| 174 |
+
|
| 175 |
+
NOTE – In case of a partnership project that is not a legal entity, qualification (per Annex B of [ITU-T A.5]) is required for each organization in the partnership project.
|
| 176 |
+
|
| 177 |
+
**6.1.2.10** Document maintenance process: Approved Recommendations need to be reviewed and maintained over time. This may require collaborative effort with the other organization. Depending on new agreements reached between the ITU-T study group and the other organization, new versions of the incorporated text can be produced by the ITU-T study group or by the other organization. Therefore, it shall be clarified if maintenance of the text is a shared responsibility between the ITU-T study group and the organization (see [b-ITU-T A.24], in particular clause 10), or if the organization is responsible of producing new versions of the incorporated text.
|
| 178 |
+
|
| 179 |
+
**6.1.3** As soon as the documents to be incorporated are received (see clause 6.2.2), they are made available, with the agreement of the study group chairman, and subject to the permission arrangements set out in clause 6.2 and to the copyright arrangements set out in clause 6.3, for advance consideration by the relevant group. They are issued, together with information about them (see clause 6.1.2), as a TD at a study group or working party meeting, normally at least one month before the start of the meeting at which the ITU-T Recommendation (or other ITU-T document) is planned for determination for TAP consultation, or consent for AAP last call (or agreement). When the other organization is responsible of producing new versions of the text (see clause 6.1.2.10), the draft resulting ITU-T Recommendation is notified by a circular at least three months before the start of the meeting at which the Recommendation is planned for determination for TAP consultation or consent for AAP last call.
|
| 180 |
+
|
| 181 |
+
**6.1.4** The study group (or working party) evaluates this information (see clause 6.1.2) and decides whether to make the incorporation. The format for documenting the study group or working party decision is given in Appendix II.
|
| 182 |
+
|
| 183 |
+
**6.1.5** When an ITU-T study group decides to incorporate text (in whole or in part, with or without modification) from another organization in its own document, it notifies the organization about the actions taken concerning this text. The use, acceptance or reproduction of such text by the ITU-T study group is subject to the permission arrangements set out in clause 6.2 and to the copyright arrangements set out in clause 6.3.
|
| 184 |
+
|
| 185 |
+
**6.1.6** The resulting ITU-T Recommendation (or ITU-T document) shall identify the incorporated text, and shall provide a bibliographic reference to the document of the organization and to its particular version. In case the text of another organization is incorporated in whole and without modification, the bibliographic reference in the ITU-T Recommendation is followed by a note indicating that the referenced text is technically equivalent to the ITU-T Recommendation.
|
| 186 |
+
|
| 187 |
+
**6.1.7** The cover sheet of the resulting ITU-T Recommendation will draw the attention of implementers to potential notices of intellectual property received by the other organization as they may also apply to the ITU-T Recommendation.
|
| 188 |
+
|
| 189 |
+
### **6.2 Permission arrangements**
|
| 190 |
+
|
| 191 |
+
**6.2.1** At the earliest possible moment (see clause 6.1.3), upon the request of the study group or working party, the Telecommunication Standardization Bureau (TSB) will ensure that the organization (or designated contact point for a joint collaboration arrangement – see clause 7.3 of [ITU-T A.5]) has provided a written statement in which it agrees to:
|
| 192 |
+
|
| 193 |
+
- the distribution of the material for discussions within the appropriate groups, and
|
| 194 |
+
- its possible use (in whole or in part, with or without modification) in any resulting ITU-T Recommendations (or other ITU-T documents) that are published (see [PP Res. 66]).
|
| 195 |
+
|
| 196 |
+
**6.2.2** TSB will also get from the organization a full copy of the existing document, preferably in electronic format (see clause 6.1.3). No reformatting is necessary. The objective is to have referenced documents available via the web at no cost, so that the study group (or working party) may proceed with its evaluation. Accordingly, if a document to be incorporated in whole or in part is available in this manner, it is sufficient to provide its exact location on the web. The document should conform to the following criteria:
|
| 197 |
+
|
| 198 |
+
- a) should contain no confidential information;
|
| 199 |
+
- b) should indicate the source within the organization (e.g. committee, subcommittee, etc.);
|
| 200 |
+
- c) should differentiate between normative references and non-normative references.
|
| 201 |
+
|
| 202 |
+
**6.2.3** Should the organization decline to provide such statement or fail to do so, the incorporation shall not be made. In this case, the decision to incorporate the reference (according to [ITU-T A.5]) instead of the text shall be made by consensus.
|
| 203 |
+
|
| 204 |
+
### **6.3 Copyright arrangements**
|
| 205 |
+
|
| 206 |
+
The subject of modifications to texts and arrangements for royalty-free copyright licences, including the right to sub-license, for texts accepted by ITU-T, is a matter to be agreed upon between TSB and the particular organization. However, the originating organization retains the copyright and change control for its texts, unless explicitly relinquished. (See also clauses 6.1.2.10, 6.1.6 and 6.2.1.)
|
| 207 |
+
|
| 208 |
+
## **7 Generic procedures for incorporating text of ITU-T documents in the documents of other organizations**
|
| 209 |
+
|
| 210 |
+
Organizations are strongly encouraged to reference approved ITU-T documents as appropriate to progress their work. This clause addresses the process of incorporating text (in whole or in part, with or without modification) from an ITU-T document in a document of another organization. This process is expected to be rarely used.
|
| 211 |
+
|
| 212 |
+
### **7.1 Documents sent to other organizations**
|
| 213 |
+
|
| 214 |
+
**7.1.1** An organization may incorporate text (in whole or in part, with or without modification) from a draft or approved ITU-T Recommendation (or of other documents produced by ITU-T), as all or part of the text of its draft document. Organizations are strongly encouraged to incorporate approved text rather than draft text from ITU-T and, whenever possible, to incorporate text without modification.
|
| 215 |
+
|
| 216 |
+
**7.1.2** When an organization decides to accept ITU-T text, it notifies TSB about the actions taken concerning this text. The use, acceptance or reproduction of such text by the qualified organization is subject to the permission arrangements set out in clause 7.2 and to the copyright arrangements set out in clause 7.3.
|
| 217 |
+
|
| 218 |
+
### **7.2 Permission arrangements**
|
| 219 |
+
|
| 220 |
+
**7.2.1** At the earliest possible moment, the organization will ensure that the TSB has provided a written statement that it agrees to the distribution of the material for discussions within the appropriate groups and possible use (in whole or in part, with or without modification) in any documents of the organization.
|
| 221 |
+
|
| 222 |
+
**7.2.2** Should the ITU decline to provide such statement, or fails to do so, the incorporation shall not be made.
|
| 223 |
+
|
| 224 |
+
### **7.3 Copyright arrangements**
|
| 225 |
+
|
| 226 |
+
The subject of modifications to texts and arrangements for royalty-free copyright licences, including the right to sub-license, for texts accepted by qualified organizations and their publishers and others, is a matter to be agreed upon between TSB and the particular organization. However, the ITU retains the copyright and change control for its texts, unless explicitly relinquished.
|
| 227 |
+
|
| 228 |
+
## Appendix I
|
| 229 |
+
|
| 230 |
+
### Workflow for incorporating text of another organization
|
| 231 |
+
|
| 232 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 233 |
+
|
| 234 |
+
Figure I.1 describes the workflow for incorporating text of another organization.
|
| 235 |
+
|
| 236 |
+
|
| 237 |
+
|
| 238 |
+
```
|
| 239 |
+
graph TD; A[A contribution from a member
|
| 240 |
+
(possibly containing an
|
| 241 |
+
ITU-T A.25 justification)
|
| 242 |
+
proposes to incorporate text] --> D{The study group agrees
|
| 243 |
+
on the proposal}; B[Discussion during a
|
| 244 |
+
meeting identifies the need
|
| 245 |
+
to incorporate text] --> D; C[Another organization
|
| 246 |
+
sends a liaison statement
|
| 247 |
+
(possibly containing an
|
| 248 |
+
ITU-T A.25 justification) with a
|
| 249 |
+
proposal to incorporate its text] --> D; D --> E[The question develops
|
| 250 |
+
a (draft) ITU-T A.25
|
| 251 |
+
justification as a TD]; E -.-> F[Clause 6.1.2]; E --> G[TSB interacts with the
|
| 252 |
+
other organization to check
|
| 253 |
+
the permission and
|
| 254 |
+
copyright arrangements]; G -.-> H[Clause 6.2]; G --> I{The fully-completed ITU-T A.25
|
| 255 |
+
justification is available normally at least one month
|
| 256 |
+
before the start of the meeting at which
|
| 257 |
+
the ITU-T Rec. is planned for determination,
|
| 258 |
+
or consent (or agreement)}; I -.-> J[Clause 6.1.3]; I --> K{The study group approves
|
| 259 |
+
the ITU-T A.25 qualification}; K -.-> L[Clause 6.1.4];
|
| 260 |
+
```
|
| 261 |
+
|
| 262 |
+
The flowchart illustrates the process for incorporating text from another organization. It begins with three parallel paths: a member proposing text, a meeting identifying a need, or an external organization sending a liaison statement. All paths lead to a decision point where the study group agrees on the proposal. This is followed by developing a draft ITU-T A.25 justification as a TD, which is linked to Clause 6.1.2. The next step is TSB interaction with the other organization to check permissions and copyright, linked to Clause 6.2. This leads to a decision on whether the fully-completed justification is available at least one month before the meeting, linked to Clause 6.1.3. Finally, the study group approves the ITU-T A.25 qualification, linked to Clause 6.1.4. The diagram is identified as A.25(19)\_F1.1.
|
| 263 |
+
|
| 264 |
+
Flowchart illustrating the workflow for incorporating text of another organization.
|
| 265 |
+
|
| 266 |
+
Figure I.1 – Workflow for incorporating text of another organization
|
| 267 |
+
|
| 268 |
+
## Appendix II
|
| 269 |
+
|
| 270 |
+
### Format for documenting a study group or working party decision
|
| 271 |
+
|
| 272 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 273 |
+
|
| 274 |
+
### II.1 Description of the referenced document (incl. full copy)
|
| 275 |
+
|
| 276 |
+
*[Insert clear description of the document considered for incorporation, e.g., type of document, title, number, version, date, etc.]*
|
| 277 |
+
|
| 278 |
+
*[Insert number of the TD containing the document or URL to the document on the website of the other organization]*
|
| 279 |
+
|
| 280 |
+
NOTE – No reformatting is necessary. The objective is to have referenced documents available via the web at no cost, so that the study group (or working party) may proceed with its evaluation. Accordingly, if a document to be incorporated in whole or in part is available in this manner, it is sufficient to provide its exact location on the web. On the other hand, if the document is not available in this manner, a full copy must be provided (preferably in electronic format).
|
| 281 |
+
|
| 282 |
+
### II.2 Status of approval
|
| 283 |
+
|
| 284 |
+
NOTE – Incorporating text that has not yet been approved by the organization can lead to confusion; thus, incorporating is usually limited to approved documents. If absolutely necessary, incorporation of text from a draft document can be made where cooperative work requiring cross-incorporation is being approved by ITU-T and another organization in approximately the same time frame.
|
| 285 |
+
|
| 286 |
+
*[Indicate status of approval:*
|
| 287 |
+
|
| 288 |
+
*Draft*
|
| 289 |
+
|
| 290 |
+
*Approved]*
|
| 291 |
+
|
| 292 |
+
### II.3 Justification for the specific incorporation
|
| 293 |
+
|
| 294 |
+
*[Insert justification, including why it is inappropriate to reference the text in the draft ITU-T Recommendation or other draft ITU-T document]*
|
| 295 |
+
|
| 296 |
+
### II.4 Intellectual property rights (patents, copyrights for software or text, marks) issues, if any, related to the proposed text for incorporation
|
| 297 |
+
|
| 298 |
+
*[Insert current information, if any, about patents, copyrights for software or text, marks, etc. Relevant documents should be attached]*
|
| 299 |
+
|
| 300 |
+
### II.5 Proper names and trademarks of specific companies/organizations, products or services
|
| 301 |
+
|
| 302 |
+
*[Insert all proper names and trademarks of specific companies/organizations, products or services contained in the proposed text. This information should be provided on a best effort basis, and no search is required]*
|
| 303 |
+
|
| 304 |
+
### II.6 Other information
|
| 305 |
+
|
| 306 |
+
*[Insert other information that might be useful in describing the "quality" of the document, e.g., whether products have been implemented using it, whether conformance requirements are clear, whether the specification is readily and widely available]*
|
| 307 |
+
|
| 308 |
+
### II.7 Stability or maturity of the document
|
| 309 |
+
|
| 310 |
+
*[Insert degree of stability or maturity, e.g., length of time it has existed]*
|
| 311 |
+
|
| 312 |
+
### **II.8 Relationship with other existing or emerging documents**
|
| 313 |
+
|
| 314 |
+
*[Insert relationship]*
|
| 315 |
+
|
| 316 |
+
### **II.9 List of normative references within the incorporated document**
|
| 317 |
+
|
| 318 |
+
NOTE – When text from a document is to be incorporated in an ITU-T Recommendation, all normative references within the incorporated document should be listed. The document should differentiate between normative references and non-normative references.
|
| 319 |
+
|
| 320 |
+
*[List all normative references]*
|
| 321 |
+
|
| 322 |
+
### **II.10 Qualification of the organization (per Annex B of [ITU-T A.5])**
|
| 323 |
+
|
| 324 |
+
NOTE – This needs to be done only the first time a document from the organization is being considered for incorporation, and only if such qualification information has not been already documented. Qualification of an organization is reviewed on a regular basis (any study group willing to incorporate a document from the organization may perform the review). In particular, if the patent policy of that organization has changed, it is important to check that the new patent policy is consistent with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC and the Guidelines for the Implementation of the Common Patent Policy for ITU-T/ITU-R/ISO/IEC. In case of a partnership project that is not a legal entity, qualification (per Annex B of [ITU-T A.5]) is required for each organization in the partnership project.
|
| 325 |
+
|
| 326 |
+
*[Insert number of the TD containing the A.5 qualification of the organization if it is not yet qualified]*
|
| 327 |
+
|
| 328 |
+
### **II.11 Document maintenance process**
|
| 329 |
+
|
| 330 |
+
NOTE – Approved Recommendations need to be reviewed and maintained over time. This may require collaborative effort with the other organization. Depending on new agreements reached, new versions of the incorporated text can be produced by the ITU-T study group or by the other organization. Therefore, it shall be clarified if maintenance of the text is a shared responsibility between the ITU-T study group and the organization (see [b-ITU-T A.24], in particular clause 10), or if the organization is responsible of producing new versions of the incorporated text.
|
| 331 |
+
|
| 332 |
+
*[Describe the maintenance process]*
|
| 333 |
+
|
| 334 |
+
## Bibliography
|
| 335 |
+
|
| 336 |
+
- [b-ITU-T A.1] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector*.
|
| 337 |
+
- [b-ITU-T A.24] Recommendation ITU-T A.24 (2024), *Collaboration and exchange of information with other organizations*.
|
| 338 |
+
|
| 339 |
+
|
| 340 |
+
|
| 341 |
+
|
| 342 |
+
|
| 343 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 344 |
+
|
| 345 |
+
| | |
|
| 346 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 347 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 348 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 349 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 350 |
+
| Series F | Non-telephone telecommunication services |
|
| 351 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 352 |
+
| Series H | Audiovisual and multimedia systems |
|
| 353 |
+
| Series I | Integrated services digital network |
|
| 354 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 355 |
+
| Series K | Protection against interference |
|
| 356 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 357 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 358 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 359 |
+
| Series O | Specifications of measuring equipment |
|
| 360 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 361 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 362 |
+
| Series R | Telegraph transmission |
|
| 363 |
+
| Series S | Telegraph services terminal equipment |
|
| 364 |
+
| Series T | Terminals for telematic services |
|
| 365 |
+
| Series U | Telegraph switching |
|
| 366 |
+
| Series V | Data communication over the telephone network |
|
| 367 |
+
| Series X | Data networks, open system communications and security |
|
| 368 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 369 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.31-200810-I_PDF-E/c96dfc0f0ec4a44dd1d7e72fd0d99948_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.31-200810-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,357 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
# A.31
|
| 12 |
+
|
| 13 |
+
(10/2008)
|
| 14 |
+
|
| 15 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 16 |
+
|
| 17 |
+
---
|
| 18 |
+
|
| 19 |
+
# **Guidelines and coordination requirements for the organization of ITU-T workshops and seminars**
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T A.31
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with two red arrows pointing towards the letters 'ITU' in a bold, blue font. Below the globe, the words 'International Telecommunication Union' are written in a smaller, blue font.
|
| 26 |
+
|
| 27 |
+
ITU logo: A globe with red arrows pointing to the letters 'ITU' and the text 'International Telecommunication Union'.
|
| 28 |
+
|
| 29 |
+
|
| 30 |
+
|
| 31 |
+
## **Recommendation ITU-T A.31**
|
| 32 |
+
|
| 33 |
+
# **Guidelines and coordination requirements for the organization of ITU-T workshops and seminars**
|
| 34 |
+
|
| 35 |
+
## **Summary**
|
| 36 |
+
|
| 37 |
+
This Recommendation provides guidelines and coordination requirements for the organization of seminars and workshops by the Telecommunication Standardization Sector (ITU-T).
|
| 38 |
+
|
| 39 |
+
## **Source**
|
| 40 |
+
|
| 41 |
+
Recommendation ITU-T A.31 was prepared by TSAG (2005-2008) and approved by the World Telecommunication Standardization Assembly (Johannesburg, 21-30 October 2008).
|
| 42 |
+
|
| 43 |
+
## FOREWORD
|
| 44 |
+
|
| 45 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 46 |
+
|
| 47 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 48 |
+
|
| 49 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 50 |
+
|
| 51 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 52 |
+
|
| 53 |
+
### NOTE
|
| 54 |
+
|
| 55 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 56 |
+
|
| 57 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 58 |
+
|
| 59 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 60 |
+
|
| 61 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 62 |
+
|
| 63 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 64 |
+
|
| 65 |
+
© ITU 2009
|
| 66 |
+
|
| 67 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 68 |
+
|
| 69 |
+
## CONTENTS
|
| 70 |
+
|
| 71 |
+
| | | <b>Page</b> |
|
| 72 |
+
|----|----------------------------------------------------------------------------------------------------------------------|-------------|
|
| 73 |
+
| 1 | Scope ..... | 1 |
|
| 74 |
+
| 2 | References ..... | 1 |
|
| 75 |
+
| 3 | Definitions ..... | 1 |
|
| 76 |
+
| | 3.1 Terms defined elsewhere ..... | 1 |
|
| 77 |
+
| | 3.2 Terms defined in this Recommendation ..... | 1 |
|
| 78 |
+
| 4 | Abbreviations and acronyms ..... | 2 |
|
| 79 |
+
| 5 | Conventions ..... | 2 |
|
| 80 |
+
| 6 | Choice of the proper event format ..... | 2 |
|
| 81 |
+
| 7 | Event format specifics ..... | 2 |
|
| 82 |
+
| | 7.1 Seminars ..... | 2 |
|
| 83 |
+
| | 7.2 Workshops ..... | 2 |
|
| 84 |
+
| 8 | Event coordination ..... | 2 |
|
| 85 |
+
| | 8.1 Study group strategy focused ..... | 3 |
|
| 86 |
+
| | 8.2 Information focused ..... | 3 |
|
| 87 |
+
| | 8.3 Tutorial focused ..... | 3 |
|
| 88 |
+
| | 8.4 Promotion focused ..... | 4 |
|
| 89 |
+
| 9 | Event identification ..... | 4 |
|
| 90 |
+
| 10 | Guidelines and coordination requirements for the organization of ITU-T workshops and seminars ..... | 4 |
|
| 91 |
+
| | 10.1 Guidelines, results and exchange of experience ..... | 4 |
|
| 92 |
+
| | 10.2 Coordination within ITU-T, and between ITU-T and the other two Sectors and the General Secretariat of ITU ..... | 5 |
|
| 93 |
+
| | 10.3 Coordination between ITU-T and relevant SDOs and regional organizations ..... | 5 |
|
| 94 |
+
| | 10.4 Administrative nature ..... | 5 |
|
| 95 |
+
| 11 | Basic requirements for the evaluation and follow-up actions of workshops and seminars ..... | 5 |
|
| 96 |
+
|
| 97 |
+
|
| 98 |
+
|
| 99 |
+
## Recommendation ITU-T A.31
|
| 100 |
+
|
| 101 |
+
# Guidelines and coordination requirements for the organization of ITU-T workshops and seminars
|
| 102 |
+
|
| 103 |
+
(2008)
|
| 104 |
+
|
| 105 |
+
## 1 Scope
|
| 106 |
+
|
| 107 |
+
This Recommendation provides guidelines and coordination requirements for the organization of workshops and seminars by ITU-T. These workshops and seminars aim for discussion and dissemination of the development of standards for worldwide implementation in telecommunications carried out by the study groups (SGs) of ITU-T.
|
| 108 |
+
|
| 109 |
+
## 2 References
|
| 110 |
+
|
| 111 |
+
The following ITU-T Recommendations and other references contain provisions that, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 112 |
+
|
| 113 |
+
[ITU-T A.1] Recommendation ITU-T A.1 (2008), *Work methods for study groups of the ITU Telecommunication Standardization Sector (ITU-T)*.
|
| 114 |
+
|
| 115 |
+
## 3 Definitions
|
| 116 |
+
|
| 117 |
+
### 3.1 Terms defined elsewhere
|
| 118 |
+
|
| 119 |
+
None.
|
| 120 |
+
|
| 121 |
+
### 3.2 Terms defined in this Recommendation
|
| 122 |
+
|
| 123 |
+
This Recommendation defines the following terms:
|
| 124 |
+
|
| 125 |
+
**3.2.1 seminar:** The seminar is a primarily one-way format, focused on the dissemination of information, in what amounts to classroom-style format. Depending on the subject and/or audience, there may be a lesser or greater degree of participant interaction with the experts who are presenting.
|
| 126 |
+
|
| 127 |
+
**3.2.2 workshop:** The workshop environment is fundamentally a meeting of peers, gathered to discuss technical, implementation, industry, or strategic issues. Workshops can span a spectrum of styles, from highly technical events focusing on a single detailed issue, to broader gatherings intended to expose a wide spectrum of input and opinion.
|
| 128 |
+
|
| 129 |
+
## **4 Abbreviations and acronyms**
|
| 130 |
+
|
| 131 |
+
This Recommendation uses the following abbreviations and acronyms:
|
| 132 |
+
|
| 133 |
+
| | |
|
| 134 |
+
|-----|------------------------------------|
|
| 135 |
+
| SC | Steering committee |
|
| 136 |
+
| SDO | Standards development organization |
|
| 137 |
+
| SGs | Study groups |
|
| 138 |
+
|
| 139 |
+
## **5 Conventions**
|
| 140 |
+
|
| 141 |
+
Terminologies and definitions throughout this Recommendation must be considered in accordance with the ITU-T "Author's guide for drafting ITU-T Recommendations".
|
| 142 |
+
|
| 143 |
+
## **6 Choice of the proper event format**
|
| 144 |
+
|
| 145 |
+
**6.1** The format, scope and goals of each planned event must be determined at the start of the event-planning process, as these choices will determine the addressable target audience, and trigger the workshop or seminar notification and promotion process. The awareness of these nuances among different workshop and seminar events is relevant to appropriate event planning and, therefore, to consistent and successful results.
|
| 146 |
+
|
| 147 |
+
**6.2** As a way forward to accomplish organization consistency and reach common understanding on the Sector's needs, and to facilitate cooperation and coordination in the organization of cross-Sector events, the above-mentioned standardized terminology (see clause 3) should be observed in order to cope with different characteristics of events within the Sector.
|
| 148 |
+
|
| 149 |
+
## **7 Event format specifics**
|
| 150 |
+
|
| 151 |
+
### **7.1 Seminars**
|
| 152 |
+
|
| 153 |
+
Seminars are most useful in sharing ITU-T vision and technical knowledge with new participants who have not previously been exposed to the scope, workings, or results of the ITU-T standardization process.
|
| 154 |
+
|
| 155 |
+
### **7.2 Workshops**
|
| 156 |
+
|
| 157 |
+
Workshops are the preferred vehicle for demonstrations, technical issue resolution, and for the creation of specific deliverables (outputs). A workshop should have clear goals and a limited scope, setting and delivering upon well-defined expectations from the participants and workshop leaders.
|
| 158 |
+
|
| 159 |
+
## **8 Event coordination**
|
| 160 |
+
|
| 161 |
+
Aiming at the improvement of the organization of ITU-T workshops and seminars, and coordination with the other two Sectors and the General Secretariat for the preparation, running and evaluation of workshops and seminars, four types of ITU-T workshops and seminars are defined, according to the distinct levels of coordination and the structures, scopes and goals each type requires.<sup>1</sup>
|
| 162 |
+
|
| 163 |
+
---
|
| 164 |
+
|
| 165 |
+
<sup>1</sup> Some of the events defined in this Recommendation may have a mixed nature, such as dissemination of information and promotion.
|
| 166 |
+
|
| 167 |
+
### **8.1 Study group strategy focused**
|
| 168 |
+
|
| 169 |
+
**8.1.1** These events are focused on a specific technical topic or standardization area.
|
| 170 |
+
|
| 171 |
+
**8.1.2** The main objective is to review points of current development of technology, application and service.
|
| 172 |
+
|
| 173 |
+
**8.1.3** In general, they gather information on standardization development in other standardization development organizations (SDOs).
|
| 174 |
+
|
| 175 |
+
**8.1.4** They aim at in-depth discussion on the work programme of the SGs, that is, subsequent standardization projects, improvements in coordination or cooperation methods with other SDOs, etc.
|
| 176 |
+
|
| 177 |
+
**8.1.5** The proposal for this type of workshop or seminar normally comes from the SG management teams and membership. Speakers are usually proposed and invited by internal experts.
|
| 178 |
+
|
| 179 |
+
**8.1.6** Such events are in general collocated with SG meetings and the audience comprises mainly SG delegates and non-ITU-T members.
|
| 180 |
+
|
| 181 |
+
**8.1.7** Some of these events are co-organized with the Telecommunication Development Bureau (BDT) to reply to WTSA Resolution 44 concerning the requirements to bridge the standardization gap.
|
| 182 |
+
|
| 183 |
+
**8.1.8** These events have the following advantages:
|
| 184 |
+
|
| 185 |
+
- a) they ensure that the workshop or seminar topic is closely relevant to SG work;
|
| 186 |
+
- b) they are cost-effective in terms of organization, and avoid extra time/cost to SG delegates;
|
| 187 |
+
- c) they have a guaranteed quantity and quality of participants; thus, a guaranteed quality of discussion.
|
| 188 |
+
|
| 189 |
+
### **8.2 Information focused**
|
| 190 |
+
|
| 191 |
+
**8.2.1** These events are focused on a new technology or emerging study area. By carrying them out, it is possible to review points of current development of technology, applications and services.
|
| 192 |
+
|
| 193 |
+
**8.2.2** They are good opportunities for briefing SGs with information regarding standardization development in other SDOs.
|
| 194 |
+
|
| 195 |
+
**8.2.3** The proposal for this type of workshop or seminar normally comes from the SG management teams and membership or from the technology watch function of TSB. Speakers are usually proposed and invited by internal experts.
|
| 196 |
+
|
| 197 |
+
**8.2.4** Such events are in general collocated with SG meetings and the audience comprises mainly SG delegates.
|
| 198 |
+
|
| 199 |
+
**8.2.5** These events have the following advantages:
|
| 200 |
+
|
| 201 |
+
- a) they ensure that the workshop or seminar topic is closely relevant to SG work;
|
| 202 |
+
- b) they are cost-effective in terms of organization, and avoid extra time/cost to SG delegates;
|
| 203 |
+
- c) they have a guaranteed quantity and quality of participants; thus, a guaranteed quality of discussion;
|
| 204 |
+
- d) they could bring new ideas and work topics to relevant SGs.
|
| 205 |
+
|
| 206 |
+
### **8.3 Tutorial focused**
|
| 207 |
+
|
| 208 |
+
**8.3.1** These events are focused on ITU-T SG ongoing work or published Recommendations. Topics are selected according to local interest.
|
| 209 |
+
|
| 210 |
+
**8.3.2** The main goal is to disseminate ITU-T technical knowledge and to promote the products of the work on standardization.
|
| 211 |
+
|
| 212 |
+
**8.3.3** They are often co-organized with and funded by BDT and targeted at developing countries.
|
| 213 |
+
|
| 214 |
+
**8.3.4** ITU-T membership or BDT normally initiates this type of event and proposes topics of interest. The Telecommunication Standardization Bureau (TSB) informs and relies on the related SG management team to look for and identify qualified speakers.
|
| 215 |
+
|
| 216 |
+
### **8.4 Promotion focused**
|
| 217 |
+
|
| 218 |
+
**8.4.1** These events are closely linked to promotion activities held outside ITU in order to promote ITU-T work and demonstrate the extent to which ITU contributes in a specific technical area.
|
| 219 |
+
|
| 220 |
+
**8.4.2** Though this type of event is mostly suggested by one or more SGs, with specific venue and date, it might not be collocated with the SG meeting but rather associated with a non-ITU industry event related to its study topic.
|
| 221 |
+
|
| 222 |
+
## **9 Event identification**
|
| 223 |
+
|
| 224 |
+
Once the event format and coordination are properly identified, all related information shall be made available to the Steering Committee (SC), who will be responsible for revising and issuing general advice on the strategic coordination, planning, organization, programme, implementation, drawing and follow-up actions. This SC's task shall be taken according to clause 10 below.
|
| 225 |
+
|
| 226 |
+
# **10 Guidelines and coordination requirements for the organization of ITU-T workshops and seminars**
|
| 227 |
+
|
| 228 |
+
An appropriate working party within the Telecommunication Standardization Advisory Group (TSAG) shall undertake the responsibility for all activities and tasks regarding the organization of ITU-T workshops and seminars. The following clauses indicate such duties, followed by those within ITU-T to assist TSAG in this undertaking.
|
| 229 |
+
|
| 230 |
+
### **10.1 Guidelines, results and exchange of experience**
|
| 231 |
+
|
| 232 |
+
**10.1.1** Study and provide conceptual and strategic guidelines for the preparation, running and evaluation of workshops and seminars.
|
| 233 |
+
|
| 234 |
+
Support: TSB.
|
| 235 |
+
|
| 236 |
+
**10.1.2** Review the extent to which it is possible to follow the conceptual and strategic guidelines in the preparation, running and evaluation of each workshop or seminar.
|
| 237 |
+
|
| 238 |
+
Support: TSB.
|
| 239 |
+
|
| 240 |
+
**10.1.3** Review the reports produced by each workshop or seminar that, *inter alia*, cover lessons learned and recommended follow-up actions. These reports should be produced no later than three months following the events. The reports should highlight the needs of developing countries, if any, and be disseminated as widely as possible.
|
| 241 |
+
|
| 242 |
+
Support: Study groups and TSB.
|
| 243 |
+
|
| 244 |
+
**10.1.4** Contribute to the exchange of positive experience in the preparation, running and evaluation of the workshops and seminars.
|
| 245 |
+
|
| 246 |
+
Support: Study groups and TSB.
|
| 247 |
+
|
| 248 |
+
**10.1.5** Encourage and evaluate the evolving implementation of the gender perspective in the programme of ITU-T workshops and seminars.
|
| 249 |
+
|
| 250 |
+
Support: TSB.
|
| 251 |
+
|
| 252 |
+
## **10.2 Coordination within ITU-T, and between ITU-T and the other two Sectors and the General Secretariat of ITU**
|
| 253 |
+
|
| 254 |
+
**10.2.1** Coordinate and assess the development of the ITU-T programme of workshops and seminars, taking into consideration budgetary implications and the needs of developing countries.
|
| 255 |
+
|
| 256 |
+
Support: TSB, in cooperation with BDT (e.g., ITU regional offices and centres of excellence), as applicable.
|
| 257 |
+
|
| 258 |
+
**10.2.2** Coordinate and harmonize the programme of ITU-T workshops and seminars, in close cooperation with the other two Sectors and the General Secretariat of ITU.
|
| 259 |
+
|
| 260 |
+
Support: TSB, in cooperation with BDT, BR and the General Secretariat, as applicable.
|
| 261 |
+
|
| 262 |
+
**10.2.3** Coordinate and harmonize the programme of ITU-T workshops and seminars, in order to optimize the participation of non-ITU-T members involved with technological innovation and technical change (e.g., academia, research organizations, and small and medium enterprises) in as many events as practicable.
|
| 263 |
+
|
| 264 |
+
Support: TSB.
|
| 265 |
+
|
| 266 |
+
**10.2.4** Work in close cooperation with the study groups' management teams and TSB.
|
| 267 |
+
|
| 268 |
+
Support: TSB, in cooperation with BDT, as applicable.
|
| 269 |
+
|
| 270 |
+
**10.2.5** Take into account relevant topics identified by the technology watch function of TSAG, in order to encourage the eventual organization of a workshop or seminar associated with them.
|
| 271 |
+
|
| 272 |
+
Support: TSB.
|
| 273 |
+
|
| 274 |
+
### **10.3 Coordination between ITU-T and relevant SDOs and regional organizations**
|
| 275 |
+
|
| 276 |
+
Coordinate and harmonize the programme of ITU-T workshops and seminars, in close cooperation with relevant regional organizations.
|
| 277 |
+
|
| 278 |
+
Support: TSB.
|
| 279 |
+
|
| 280 |
+
### **10.4 Administrative nature**
|
| 281 |
+
|
| 282 |
+
Provide a report on the activities addressed in clauses 10.1, 10.2 and 10.3, to each meeting of TSAG for consideration and appropriate action.
|
| 283 |
+
|
| 284 |
+
Support: TSB.
|
| 285 |
+
|
| 286 |
+
## **11 Basic requirements for the evaluation and follow-up actions of workshops and seminars**
|
| 287 |
+
|
| 288 |
+
**11.1** Depending consistently upon the use of information technology, ITU-T homepages are identified as a crucial item for improving the organization of workshops and seminars and giving valuable feedback to TSB and TSAG on current status. Therefore, the website is to be maintained by TSB, so that accurate information provided by workshop and seminar organizers and the SC is made public on the Internet to all interested parties.
|
| 289 |
+
|
| 290 |
+
**11.2** The website shall provide a range of functionalities, including immediate access to past, current and forthcoming events. Data on events is to be shown in a standardized format and is to include the following basic requirements for the evaluation and follow-up actions of ITU-T workshops and seminars, as exemplified in Table 1:
|
| 291 |
+
|
| 292 |
+
- Title
|
| 293 |
+
- Place
|
| 294 |
+
- Start date
|
| 295 |
+
- End date
|
| 296 |
+
- Basic information
|
| 297 |
+
- Contact
|
| 298 |
+
- Invitation
|
| 299 |
+
- Programme
|
| 300 |
+
- Steering committee
|
| 301 |
+
- Sponsorship
|
| 302 |
+
- Introduction
|
| 303 |
+
- Objective
|
| 304 |
+
- Type
|
| 305 |
+
- Event format
|
| 306 |
+
- Event coordination
|
| 307 |
+
- Content
|
| 308 |
+
- Abstract
|
| 309 |
+
- Presentations
|
| 310 |
+
- Biography
|
| 311 |
+
- Report
|
| 312 |
+
- List of participants
|
| 313 |
+
|
| 314 |
+
**Table 1 – Format of information for the evaluation and follow-up actions of workshops and seminars**
|
| 315 |
+
|
| 316 |
+
| Item | Title | Place | Start date | End date | Basic information | | | | | | Type | Content | | | Report<br>**** | List of participants | |
|
| 317 |
+
|------|-----------------|----------------------|------------|----------|-------------------|-------------|-----------|------------|-------------|--------------|-----------|----------|---------------|-----------|----------------|----------------------|---|
|
| 318 |
+
| | | | | | Contact | Invitation* | Programme | Steering** | Sponsorship | Introduction | Objective | Abstract | Presentations | Biography | | | |
|
| 319 |
+
| # | <name of event> | <city>,<br><country> | dd/mm/yy | dd/mm/yy | √ | √ | √ | √ | √ | √ | √ | *** | √ | √ | √ | √ | √ |
|
| 320 |
+
|
| 321 |
+
\* The invitation letter contains also information notes so that the wording should be: "Invitation letter and information notes", if not explicitly mentioned in a separated link, "Information notes or practical information".
|
| 322 |
+
|
| 323 |
+
\*\* This column indicates if the steering committee information was available on the webpage of the event.
|
| 324 |
+
|
| 325 |
+
\*\*\* The indication of the "Type" of event implies that both the "event format" (workshop or seminar) and the "event coordination" (study group strategy, information, tutorial or promotion focused) shall be clearly identified (refer to clauses 7 and 8).
|
| 326 |
+
|
| 327 |
+
\*\*\*\* Three months is the expected period for the final report submission.
|
| 328 |
+
|
| 329 |
+
|
| 330 |
+
|
| 331 |
+
## **SERIES OF ITU-T RECOMMENDATIONS**
|
| 332 |
+
|
| 333 |
+
| | |
|
| 334 |
+
|-----------------|---------------------------------------------------------------------------------------------|
|
| 335 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 336 |
+
| Series D | General tariff principles |
|
| 337 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 338 |
+
| Series F | Non-telephone telecommunication services |
|
| 339 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 340 |
+
| Series H | Audiovisual and multimedia systems |
|
| 341 |
+
| Series I | Integrated services digital network |
|
| 342 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 343 |
+
| Series K | Protection against interference |
|
| 344 |
+
| Series L | Construction, installation and protection of cables and other elements of outside plant |
|
| 345 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 346 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 347 |
+
| Series O | Specifications of measuring equipment |
|
| 348 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 349 |
+
| Series Q | Switching and signalling |
|
| 350 |
+
| Series R | Telegraph transmission |
|
| 351 |
+
| Series S | Telegraph services terminal equipment |
|
| 352 |
+
| Series T | Terminals for telematic services |
|
| 353 |
+
| Series U | Telegraph switching |
|
| 354 |
+
| Series V | Data communication over the telephone network |
|
| 355 |
+
| Series X | Data networks, open system communications and security |
|
| 356 |
+
| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
|
| 357 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.7-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.7-202408-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,392 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Recommendation **ITU-T A.7 (08/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
**Focus groups: Establishment and working procedures**
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
# Recommendation ITU-T A.7
|
| 14 |
+
|
| 15 |
+
## Focus groups: Establishment and working procedures
|
| 16 |
+
|
| 17 |
+
## Summary
|
| 18 |
+
|
| 19 |
+
Recommendation ITU-T A.7 describes working methods and procedures of a focus group such as its establishment, terms of reference, leadership, participation, financing, support and deliverables.
|
| 20 |
+
|
| 21 |
+
The creation of focus group working guidelines, including continued coordination with their parent group, could facilitate the swift development of deliverables by the relevant study groups.
|
| 22 |
+
|
| 23 |
+
ITU-T focus groups are a flexible tool for progressing new work. Such flexibility may allow for groups developing a wide range of deliverables. Since there have been many instances in which the membership of a focus group does not have experience in the development of technical specifications, it has been common that focus group deliverables, although useful, needed to be reworked by the relevant study groups.
|
| 24 |
+
|
| 25 |
+
Appendix I provides guidance to study groups and focus groups when implementing ITU-T A.7 focus groups that aim at producing specifications that can be efficiently streamlined from focus group deliverables to ITU-T Recommendations or informative texts.
|
| 26 |
+
|
| 27 |
+
## History \*
|
| 28 |
+
|
| 29 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 30 |
+
|---------|-------------------------|------------|-------------|--------------------|
|
| 31 |
+
| 1.0 | ITU-T A.7 | 2000-06-14 | TSAG | 11.1002/1000/5092 |
|
| 32 |
+
| 2.0 | ITU-T A.7 | 2002-06-21 | TSAG | 11.1002/1000/5711 |
|
| 33 |
+
| 3.0 | ITU-T A.7 | 2004-10-14 | TSAG | 11.1002/1000/7419 |
|
| 34 |
+
| 3.1 | ITU-T A.7 (2004) Amd. 1 | 2006-07-07 | TSAG | 11.1002/1000/8793 |
|
| 35 |
+
| 4.0 | ITU-T A.7 | 2008-10-30 | TSAG | 11.1002/1000/9640 |
|
| 36 |
+
| 5.0 | ITU-T A.7 | 2012-11-30 | TSAG | 11.1002/1000/11922 |
|
| 37 |
+
| 5.1 | ITU-T A.7 (2012) Amd. 1 | 2015-06-05 | TSAG | 11.1002/1000/12527 |
|
| 38 |
+
| 6.0 | ITU-T A.7 | 2016-10-28 | TSAG | 11.1002/1000/13165 |
|
| 39 |
+
| 7.0 | ITU-T A.7 | 2024-08-02 | TSAG | 11.1002/1000/15859 |
|
| 40 |
+
|
| 41 |
+
## Keywords
|
| 42 |
+
|
| 43 |
+
Focus groups.
|
| 44 |
+
|
| 45 |
+
---
|
| 46 |
+
|
| 47 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 48 |
+
|
| 49 |
+
## FOREWORD
|
| 50 |
+
|
| 51 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 52 |
+
|
| 53 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 54 |
+
|
| 55 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 56 |
+
|
| 57 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 58 |
+
|
| 59 |
+
### NOTE
|
| 60 |
+
|
| 61 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 62 |
+
|
| 63 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 64 |
+
|
| 65 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 66 |
+
|
| 67 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 68 |
+
|
| 69 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 70 |
+
|
| 71 |
+
© ITU 2024
|
| 72 |
+
|
| 73 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 74 |
+
|
| 75 |
+
## Table of Contents
|
| 76 |
+
|
| 77 |
+
| | | Page |
|
| 78 |
+
|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------|
|
| 79 |
+
| 1 | Scope..... | 1 |
|
| 80 |
+
| 1bis | References..... | 1 |
|
| 81 |
+
| 2 | Establishment, terms of reference and leadership ..... | 1 |
|
| 82 |
+
| 2.1 | Establishment ..... | 1 |
|
| 83 |
+
| 2.2 | Terms of reference..... | 4 |
|
| 84 |
+
| 2.3 | Leadership ..... | 4 |
|
| 85 |
+
| 3 | Focus group working procedures..... | 5 |
|
| 86 |
+
| 3.1 | Participation..... | 5 |
|
| 87 |
+
| 3.2 | Working language ..... | 5 |
|
| 88 |
+
| 3.3 | Technical contributions ..... | 5 |
|
| 89 |
+
| 3.4 | Working guidelines ..... | 5 |
|
| 90 |
+
| 3.5 | Meeting announcements ..... | 5 |
|
| 91 |
+
| 3.6 | Progress reports ..... | 6 |
|
| 92 |
+
| 4 | Financing of focus groups and their meetings..... | 6 |
|
| 93 |
+
| 5 | Administrative support ..... | 6 |
|
| 94 |
+
| 6 | Meeting logistics..... | 6 |
|
| 95 |
+
| 7 | Intellectual property rights..... | 6 |
|
| 96 |
+
| 8 | Deliverables ..... | 7 |
|
| 97 |
+
| 8.1 | Form of deliverables..... | 7 |
|
| 98 |
+
| 8.2 | Approval of deliverables ..... | 7 |
|
| 99 |
+
| 8.3 | Transfer of focus group deliverables to the parent group..... | 7 |
|
| 100 |
+
| Appendix I – Guidelines for the efficient transfer of focus group deliverables to its parent group..... | | 8 |
|
| 101 |
+
| I.1 | Scope ..... | 8 |
|
| 102 |
+
| I.2 | Streamlining the transfer of deliverables by focus groups and their approval by study groups..... | 8 |
|
| 103 |
+
| Bibliography..... | | 10 |
|
| 104 |
+
|
| 105 |
+
|
| 106 |
+
|
| 107 |
+
# Recommendation ITU-T A.7
|
| 108 |
+
|
| 109 |
+
## Focus groups: Establishment and working procedures
|
| 110 |
+
|
| 111 |
+
# 1 Scope
|
| 112 |
+
|
| 113 |
+
The objective of focus groups is to help advance the work of the ITU Telecommunication Standardization Sector (ITU-T) study groups and to encourage the participation of members of other standards organizations, including experts and individuals who may not be members of ITU.
|
| 114 |
+
|
| 115 |
+
Procedures and working methods are established to facilitate the financing of focus groups, the completion of work on a well-defined topic and the documentation of the results.
|
| 116 |
+
|
| 117 |
+
The process of establishment is described in order to help identify, in a timely and collaborative manner, all study groups concerned by the scope of a potential focus group, and to agree on a study group or the Telecommunication Standardization Advisory Group (TSAG) as the parent group.
|
| 118 |
+
|
| 119 |
+
The management of a focus group is placed under the responsibility of a parent group (study group or TSAG), in association with other involved study groups in the case where the work area of the focus group overlaps with the responsibility and the mandate of those study groups (see clause 2.2).
|
| 120 |
+
|
| 121 |
+
## 1bis References
|
| 122 |
+
|
| 123 |
+
The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
|
| 124 |
+
|
| 125 |
+
[ITU-T A.1] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector (ITU-T)*.
|
| 126 |
+
|
| 127 |
+
[PP Res. 123] Resolution 123 (Rev. Bucharest, 2022) of the ITU Plenipotentiary Conference, *Bridging the standardization gap between developing and developed countries*.
|
| 128 |
+
<<https://www.itu.int/en/council/Documents/basic-texts-2023/RES-123-E.pdf>>
|
| 129 |
+
|
| 130 |
+
[PP Res. 175] Resolution 175 (Rev. Bucharest, 2022) of the ITU Plenipotentiary Conference, *Telecommunication/information and communication technology accessibility for persons with disabilities and persons with specific needs*.
|
| 131 |
+
<<https://www.itu.int/en/council/Documents/basic-texts-2023/RES-175-E.pdf>>
|
| 132 |
+
|
| 133 |
+
# 2 Establishment, terms of reference and leadership
|
| 134 |
+
|
| 135 |
+
Within the ITU-T standardization working structure, the establishment procedures of a focus group should be progressed in a transparent manner.
|
| 136 |
+
|
| 137 |
+
For each step of the establishment process, the compliance of the focus group proposal with all clauses of this Recommendation should be ensured, and all decisions are to be made by consensus.
|
| 138 |
+
|
| 139 |
+
## 2.1 Establishment
|
| 140 |
+
|
| 141 |
+
A focus group is established to address a well-scoped topic that directly advances the work of ITU-T study groups.
|
| 142 |
+
|
| 143 |
+
To justify the establishment of a focus group, the following criteria shall be fulfilled to their full extent:
|
| 144 |
+
|
| 145 |
+
- There is a significant interest in a subject and the need to timely help advance the work of the ITU-T study groups. Because the work of the ITU-T study groups is to prepare Recommendations with a view to standardizing telecommunications on a worldwide basis, the subject should have a broad level of industry interest, market relevance and anticipated interest for international standardization.
|
| 146 |
+
- The subject is not already addressed by work underway in ITU-T study groups or other focus groups, or cannot be currently handled by a study group.
|
| 147 |
+
- There should be at least four entities (i.e., Member States, Sector Members, Associates of the parent group or Academia) from different countries who commit to actively support the new focus group.
|
| 148 |
+
- The subject is not better addressed through another type of appropriate mechanism (e.g., a joint coordination activity, a correspondence group or a new Question).
|
| 149 |
+
|
| 150 |
+
Attention should be paid to distinguishing between the following two situations:
|
| 151 |
+
|
| 152 |
+
#### *a) Topic is within the mandate of one study group*
|
| 153 |
+
|
| 154 |
+
When the terms of reference of the focus group fall within the mandate of a single study group, that study group has the necessary authority to approve the formation of a focus group and become its parent group (see clause 2.1.1), provided that the chair of this study group consults with the chairs of all possibly impacted study groups. If there is any doubt that all the topics fall under the responsibility and mandate of only this study group, the decision of such an establishment should be referred to TSAG.
|
| 155 |
+
|
| 156 |
+
#### *b) Topic is within the mandate of multiple study groups*
|
| 157 |
+
|
| 158 |
+
When the terms of reference of the focus group fall within the mandate of multiple study groups, TSAG has the necessary authority to approve the formation of a focus group (see clause 2.1.2) and to become its parent group or appoint a study group as the parent group. TSAG shall consult the lead study group on the topic, if any (see clause 2.1.5 of [b-WTSA Res. 1]).
|
| 159 |
+
|
| 160 |
+
The study group or TSAG, when receiving the written contribution, should check to see which study group could best address the proposed activity for the focus group. The study group dealing with the proposal for a focus group that contains topics felt as potentially falling under the responsibility and mandate of one or more other study groups remains responsible for the consultation with the other relevant study group chairs, and for informing TSAG and the Director of TSB. The whole procedure for consultation should be kept responsive and fast by using, as often as possible, consultation of relevant parties by e-mail and teleconferencing tools, rather than physical meetings.
|
| 161 |
+
|
| 162 |
+
In all cases, the Director of TSB and the chair of TSAG are to be kept duly advised during the establishment procedure.
|
| 163 |
+
|
| 164 |
+
The establishment of a focus group and its first meeting will be announced according to clause 3.5 by the Director of TSB in cooperation with the parent group.
|
| 165 |
+
|
| 166 |
+
### **2.1.1 Establishment by a study group**
|
| 167 |
+
|
| 168 |
+
##### **2.1.1.1 Establishment at a study group meeting**
|
| 169 |
+
|
| 170 |
+
For establishment at a study group meeting, the submission of a proposal to set up a focus group on a specific topic should take the form of a submitted written contribution (see clause 3.1 of [ITU-T A.1], and in particular clause 3.1.9). The proposal must include well-defined terms of reference (fulfilling all requirements described in clause 2.2), which the study group will assess in line with the criteria in clause 2.1.
|
| 171 |
+
|
| 172 |
+
In the case that all topics fall, without doubt, within the work area of this study group, the establishment will be discussed during this meeting, and may be decided at the same meeting.
|
| 173 |
+
|
| 174 |
+
If views are expressed that the proposed topic overlaps with the mandate of another study group, the chair of the study group to which the proposal is addressed will send the proposal to the chair of TSAG. The chair of TSAG will then proceed as described in clauses 2.1.2.1 or 2.1.2.2.
|
| 175 |
+
|
| 176 |
+
##### **2.1.1.2 Establishment between study group meetings**
|
| 177 |
+
|
| 178 |
+
Exceptionally, in response to urgent marketplace needs, a focus group may be established between study group meetings for the purpose of studying technical issues (i.e., those that have no regulatory or policy implications).
|
| 179 |
+
|
| 180 |
+
The proposal, including terms of reference, to set up a focus group on a specific technical topic (within the mandate of the parent group) may be sent by any member to the chair of an appropriate study group selected by the initiators according to the foreseen work content. The chair coordinates the first review of the proposal with the vice-chairs and the chairs of working parties of the study group. If the proposal to establish the focus group is agreed, the proposal, with completed terms of reference, will be posted on the ITU website and distributed to the study group e-mail distribution list, allowing four weeks for comments.
|
| 181 |
+
|
| 182 |
+
In the absence of unresolved comments, the study group chair may decide the immediate establishment of the focus group. As far as possible, the chair should seek to resolve comments by correspondence; however, if this is not possible, the decision to approve the establishment of the focus group is to be deferred to the next meeting of the study group.
|
| 183 |
+
|
| 184 |
+
If views are expressed that the proposed focus group overlaps with the mandate of another study group, the chair of the study group to which the proposal is addressed will send the proposal to the chair of TSAG. The chair of TSAG will then proceed as described in clauses 2.1.2.1 or 2.1.2.2.
|
| 185 |
+
|
| 186 |
+
### **2.1.2 Establishment by TSAG**
|
| 187 |
+
|
| 188 |
+
##### **2.1.2.1 Establishment at a TSAG meeting**
|
| 189 |
+
|
| 190 |
+
For establishment at a TSAG meeting, the submission of a proposal to set up a focus group on a specific topic should take the form of a written contribution (see clause 3.1 of [ITU-T A.1], and in particular clause 3.1.9). The proposal must include well-defined terms of reference (fulfilling all requirements described in clause 2.2), which TSAG will assess in line with the criteria in clause 2.1.
|
| 191 |
+
|
| 192 |
+
The TSAG plenary can decide to establish the focus group and designate the parent group or be its parent group.
|
| 193 |
+
|
| 194 |
+
This way of proceeding can also be adopted to decide on cases transmitted according to clause 2.1.1.2, when the schedule of the TSAG meeting is compatible with a timely response, whereby the proposal must be available for the members at least twelve calendar days before the meeting.
|
| 195 |
+
|
| 196 |
+
##### **2.1.2.2 Establishment between TSAG meetings**
|
| 197 |
+
|
| 198 |
+
Exceptionally, in response to urgent marketplace needs, a focus group may be established between TSAG meetings for the purpose of studying technical issues (i.e., those that have no regulatory or policy implications).
|
| 199 |
+
|
| 200 |
+
A proposal to set up a focus group on a specific technical topic, including draft terms of reference, may be submitted by any member to the chair of TSAG.
|
| 201 |
+
|
| 202 |
+
The chair of TSAG coordinates the first review of the proposal with the /vice-chairs and working party chairs of TSAG and chairs of all study groups. If the proposal to set up a focus group is agreed, the proposal, with completed terms of reference and the nomination of the parent group, will be posted on the ITU-T website and distributed to the TSAG e-mail distribution list, allowing four weeks for comments.
|
| 203 |
+
|
| 204 |
+
In the absence of unresolved comments, the chair of TSAG may decide the immediate establishment of the focus group. As far as possible, the chair of TSAG should seek to resolve comments by correspondence; however, if this is not possible, the decision to approve establishment of the focus group is deferred to the next meeting of TSAG.
|
| 205 |
+
|
| 206 |
+
This way of proceeding can also be adopted to decide on cases transmitted according to clause 2.1.1.2, when the schedule of the TSAG meetings is not deemed to be compatible with a timely response.
|
| 207 |
+
|
| 208 |
+
## **2.2 Terms of reference**
|
| 209 |
+
|
| 210 |
+
The topic for a particular focus group is to be well defined (prior to approval), and the terms of reference must include the scope of actions, a plan of action, the expected deliverables and the time schedules for completion.
|
| 211 |
+
|
| 212 |
+
The relationship of this work to that of the parent group must be indicated, in addition to relationships with other ITU study groups, standards organizations, forums and consortia, etc., and the degree of urgency of the specific topic. The justification that the intended activity cannot be handled as efficiently by study groups should be given.
|
| 213 |
+
|
| 214 |
+
NOTE – It is suggested to provide (as a separate document) a gap analysis with the work in other ITU study groups, standards organizations, forums, consortia, etc. (see [b-ITU-T A-Suppl.6]).
|
| 215 |
+
|
| 216 |
+
It is expected that a focus group will complete its work in a short period of time, typically 9 to 12 months, in accordance with the plan of action and time schedules defined in the terms of reference. The scope and breadth of work identified in the terms of reference should take this timeline into account. If a focus group requires more time to fulfil its mandate, the extension of its term will be subject to review and approval by the parent group.
|
| 217 |
+
|
| 218 |
+
During the life of the focus group, its terms of reference cannot be modified by the focus group itself. Any proposal to modify the terms of reference is to be submitted as a written contribution to the parent group for its consideration and approval.
|
| 219 |
+
|
| 220 |
+
If more than one study group is involved (i.e., the topic falls under the responsibility and mandate of one or more other study groups), a possible modification of the terms of reference (including scope) should be discussed with the other involved study groups before approval is granted.
|
| 221 |
+
|
| 222 |
+
Extension of the lifetime requires a decision of the parent group (with no reservations by the other involved study groups in the case where a topic falls under the responsibility and mandate of one or more other study groups). The focus group will automatically stop if the parent group does not agree to extend the lifetime of the focus group.
|
| 223 |
+
|
| 224 |
+
## **2.3 Leadership**
|
| 225 |
+
|
| 226 |
+
A chair and vice-chair are initially appointed by the parent group. If needed, after the initial establishment of the focus group, subsequent management appointments will be made by the focus group, and the parent group informed accordingly. If the focus group was established by TSAG with a different parent group, TSAG will also be informed accordingly. Appointment of chair and vice-chair shall be primarily based upon demonstrated competence both in technical content of the parent group and in the management skills required.
|
| 227 |
+
|
| 228 |
+
Member States and ITU-T Sector Members will provide the chairship, but vice-chairships can be open to ITU-T Associates and academia.
|
| 229 |
+
|
| 230 |
+
A focus group chair who is unable to carry out his or her duties is replaced by one of the vice-chairs, who is chosen and appointed by the parent group at its next meeting. If none of the vice-chairs is able to take on the role of chair, the parent group calls for candidates and the chair is appointed at the next meeting of the parent group.
|
| 231 |
+
|
| 232 |
+
# **3 Focus group working procedures**
|
| 233 |
+
|
| 234 |
+
## **3.1 Participation**
|
| 235 |
+
|
| 236 |
+
Any individual from a country that is a member of ITU and who is willing to contribute actively to the work may participate in a focus group. This includes individuals who are also members of international, regional and national organizations.
|
| 237 |
+
|
| 238 |
+
Participation in focus groups shall not be used as an alternative to ITU membership.
|
| 239 |
+
|
| 240 |
+
A list of participants is to be maintained by the focus group for reference purposes and made available to focus group participants. This list will include information for persons with disabilities on how their participation shall be facilitated.
|
| 241 |
+
|
| 242 |
+
Participation in focus groups that have impacts on strategic, structural and/or operational aspects of ITU-T is limited to ITU-T members.
|
| 243 |
+
|
| 244 |
+
To facilitate the efficient transfer of deliverables from a focus group to its parent group, it is suggested that experts leading the work within a focus group have experience in developing ITU-T texts (e.g., ITU-T Recommendations, Supplements or Technical Reports). Additionally, training should be provided to the focus group management and participants on the ITU-T working methods.
|
| 245 |
+
|
| 246 |
+
## **3.2 Working language**
|
| 247 |
+
|
| 248 |
+
The language to be used will be mutually agreed by the focus group participants. However, any communication with the parent group shall preferably be in English or one of the other ITU official languages.
|
| 249 |
+
|
| 250 |
+
## **3.3 Technical contributions**
|
| 251 |
+
|
| 252 |
+
Any participant may submit a technical contribution directly to the focus group, in accordance with the time schedule adopted. A template for contributions can be found on the ITU-T website.
|
| 253 |
+
|
| 254 |
+
## **3.4 Working guidelines**
|
| 255 |
+
|
| 256 |
+
In accordance with its terms of reference (see clause 2.2), it is recommended that the focus group agrees as soon as possible on a working structure (e.g., working groups), a related management team and a working schedule.
|
| 257 |
+
|
| 258 |
+
A focus group may, at its discretion, share working documents via liaison statements (see clause 1.5.1 of [ITU-T A.1]).
|
| 259 |
+
|
| 260 |
+
Focus groups may develop additional internal working guidelines, as required.
|
| 261 |
+
|
| 262 |
+
## **3.5 Meeting announcements**
|
| 263 |
+
|
| 264 |
+
The establishment of a focus group will be announced in cooperation with the parent group via ITU publications and other means, e.g., communication with other organizations and/or experts, technical journals.
|
| 265 |
+
|
| 266 |
+
The first meeting of a focus group will be arranged by the parent group and the initially appointed chair.
|
| 267 |
+
|
| 268 |
+
The schedule of subsequent meetings of a focus group will be decided by the focus group. The process of announcing meetings can be decided by the focus group and the parent group. Meetings will be announced at least six weeks in advance on the ITU website.
|
| 269 |
+
|
| 270 |
+
## **3.6 Progress reports**
|
| 271 |
+
|
| 272 |
+
Focus group progress reports are to be provided at each parent group meeting at least twelve calendar days before the meeting (or as a minimum every six months) and transmitted in copy to all involved study groups. They will be posted in the form of TDs.
|
| 273 |
+
|
| 274 |
+
These progress reports to the parent group should include the following information:
|
| 275 |
+
|
| 276 |
+
- an updated work plan, including a schedule of planned meetings;
|
| 277 |
+
- status of work with reference to the work plan, including a list of outputs and possibly a suggested list study groups for which they are intended;
|
| 278 |
+
- summary of contributions considered by the focus group;
|
| 279 |
+
- list of attendees at all meetings held since the last progress report;
|
| 280 |
+
- details of any financing provided to the focus group. The parent group chair should also keep TSAG advised of the progress of the focus group.
|
| 281 |
+
|
| 282 |
+
# **4 Financing of focus groups and their meetings**
|
| 283 |
+
|
| 284 |
+
Financing of meetings and their preparation is accomplished by volunteer hosting in a similar manner to rapporteur groups, or on the basis of financial arrangements determined by the focus group, provided there is no incremental increase in expenditure and no adverse impact on the normal work of the study groups and TSAG, except for encouraging the participation of persons with disabilities in accordance with [PP Res. 175], and for supporting the participation of representatives of developing countries<sup>1</sup> in accordance with [PP Res. 123].
|
| 285 |
+
|
| 286 |
+
# **5 Administrative support**
|
| 287 |
+
|
| 288 |
+
Focus groups can establish their own method of providing and financing administrative support between meetings. This shall be documented in the progress report (see clause 3.6).
|
| 289 |
+
|
| 290 |
+
Where administrative services are requested from TSB, there shall be no incremental increase in expenditure and no adverse impact on the normal work of the study groups and TSAG, except for encouraging the participation of persons with disabilities in accordance with [PP Res. 175], and for supporting the participation of representatives of developing countries<sup>1</sup> in accordance with [PP Res. 123].
|
| 291 |
+
|
| 292 |
+
All costs must be covered by the focus group. ITU-T will not be expected to offer any distribution services free of charge, except for progress reports submitted according to clause 3.6, or deliverables to study groups.
|
| 293 |
+
|
| 294 |
+
## **6 Meeting logistics**
|
| 295 |
+
|
| 296 |
+
The frequency and location of meetings is decided by each focus group. Participation of persons with disabilities, including the provision of electronic documents in accessible formats, shall be encouraged in accordance with [PP Res. 175].
|
| 297 |
+
|
| 298 |
+
## **7 Intellectual property rights**
|
| 299 |
+
|
| 300 |
+
The Common Patent Policy for ITU-T/ITU-R/ISO/IEC is to be used.
|
| 301 |
+
|
| 302 |
+
The chair of a focus group should announce this during every meeting and record all responses in the meeting report.
|
| 303 |
+
|
| 304 |
+
---
|
| 305 |
+
|
| 306 |
+
<sup>1</sup> These include the least developed countries, small island developing states, landlocked developing countries and countries with economies in transition.
|
| 307 |
+
|
| 308 |
+
The copyright provisions in [ITU-T A.1] are to be followed.
|
| 309 |
+
|
| 310 |
+
# **8 Deliverables**
|
| 311 |
+
|
| 312 |
+
## **8.1 Form of deliverables**
|
| 313 |
+
|
| 314 |
+
Deliverables can be in the form of technical specifications (e.g., terminology, requirements, functional architecture), technical reports on standards gap analysis results (e.g., landscape, use cases, technical maturity assessment), base material for the development of draft ITU-T texts (e.g., ITU-T Recommendations, Supplements or technical reports – see also Appendix I), etc., and are expected to form input to and advance the work of the parent group and other involved study groups.
|
| 315 |
+
|
| 316 |
+
## **8.2 Approval of deliverables**
|
| 317 |
+
|
| 318 |
+
Approval shall be obtained by consensus.
|
| 319 |
+
|
| 320 |
+
## **8.3 Transfer of focus group deliverables to the parent group**
|
| 321 |
+
|
| 322 |
+
The focus group will send all its deliverables to the parent group for further consideration. The deliverables shall be submitted as TDs to the parent group in accordance with [ITU-T A.1], but not later than four calendar weeks before the meeting of the parent group.
|
| 323 |
+
|
| 324 |
+
## Appendix I
|
| 325 |
+
|
| 326 |
+
### **Guidelines for the efficient transfer of focus group deliverables to its parent group**
|
| 327 |
+
|
| 328 |
+
(This appendix does not form an integral part of this Recommendation.)
|
| 329 |
+
|
| 330 |
+
## **I.1 Scope**
|
| 331 |
+
|
| 332 |
+
The guidelines in this appendix are intended to facilitate the efficient transfer of deliverables from focus groups (FGs) aimed at being base material for the development of draft ITU-T Recommendations (see [b-WTSA Res. 1], [ITU-T A.1] and [b-ITU-T A.8]) or informative texts (see [b-ITU-T A.13]).
|
| 333 |
+
|
| 334 |
+
Focus groups are a flexible tool for progressing new work. According to the core text of this Recommendation, focus group deliverables can be in the form of technical specifications, reports on standards gap analysis results or base material for the development of draft Recommendations.
|
| 335 |
+
|
| 336 |
+
Such flexibility may allow focus groups to develop a wide range of deliverables with the involvement of external stakeholders. However, this flexibility can sometimes be a shortcoming, as their deliverables may not be structured or contain material ready to be used as specifications, or their development is not sufficiently coordinated with the relevant study groups to ensure a speedy handling at study groups after completion of the deliverables by focus groups.
|
| 337 |
+
|
| 338 |
+
## **I.2 Streamlining the transfer of deliverables by focus groups and their approval by study groups**
|
| 339 |
+
|
| 340 |
+
The following streamlining guidance is provided:
|
| 341 |
+
|
| 342 |
+
NOTE – It should be noted that not all focus groups aim at producing base material for the development of draft Recommendations or informative texts. In many cases, it is acceptable that a focus group will produce other types of deliverables – such as ex ante standardization studies, roadmaps and gap analyses.
|
| 343 |
+
|
| 344 |
+
- 1) ITU-T focus groups should be created with terms of reference and working guidelines that clearly indicate the expected deliverables to be developed, including, but not limited to, formatted base material for the study group's development and approval of a draft ITU-T Recommendation or of an informative text.
|
| 345 |
+
- 2) Where appropriate, deliverables of a focus group should be prepared and formatted in a manner that facilitates their development and adoption by the appropriate study group(s) into draft Recommendations (e.g., base material formatted in the structure of an ITU-T Recommendation) or informative texts.
|
| 346 |
+
- 3) Where appropriate and necessary, the parent group of the focus group should provide coordination for the timely transfer of focus group deliverable(s) to the appropriate study group(s). This is expected to be required especially in instances where the deliverable(s) of a focus group has an unclear destination study group or multiple destination study groups.
|
| 347 |
+
- 4) Experts leading the work within a focus group should have experience in developing ITU-T Recommendations or informative texts. Additionally, training should be provided to the focus group management and participants on the ITU-T working methods.
|
| 348 |
+
- 5) Focus group deliverables aimed as future ITU-T Recommendations or Supplements should follow the *Author's Guide for drafting ITU-T Recommendations* [b-Author's] and their content must have content that is expected for ITU-T Recommendations or Supplements.
|
| 349 |
+
|
| 350 |
+
- 6) Drafts of focus group deliverables intended to become ITU-T Recommendations or informative texts should be shared with the parent group on a regular basis. When focus group deliverables intended to become ITU-T Recommendations or informative texts would fall under the responsibility of different study groups, the focus group should share their deliverables with the relevant study groups as soon as possible.
|
| 351 |
+
- 7) Once mature, focus group deliverables intended to become ITU-T Recommendations or informative texts are approved by the focus group for transmission to the parent group for appropriate consideration.
|
| 352 |
+
- 8) The parent group is expected to tally the number of ITU-T Recommendations approved by relevant study groups, and the number of agreed informative texts, that were based on its focus group's deliverables.
|
| 353 |
+
|
| 354 |
+
## Bibliography
|
| 355 |
+
|
| 356 |
+
- [b-ITU-T A.8] Recommendation ITU-T A.8 (2024), *Alternative approval process for new and revised ITU-T Recommendations*.
|
| 357 |
+
- [b-ITU-T A.13] Recommendation ITU-T A.13 (2019), *Non-normative ITU-T publications, including Supplements to ITU-T Recommendations*.
|
| 358 |
+
- [b-ITU-T A-Suppl.6] ITU-T A-series Recommendations – Supplement 6 (2024), *Guidelines for the development of a standardization gap analysis*.
|
| 359 |
+
- [b-WTSA Res. 1] WTSA Resolution 1 (Rev. Geneva, 2022), *Rules of procedure of the ITU Telecommunication Standardization Sector*.
|
| 360 |
+
<<https://www.itu.int/pub/T-RES-T.1-2022>>
|
| 361 |
+
- [b-Author's] *Author's Guide for drafting ITU-T Recommendations*.
|
| 362 |
+
<<https://www.itu.int/ITU-T/go/authors-guide/>>
|
| 363 |
+
|
| 364 |
+
|
| 365 |
+
|
| 366 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 367 |
+
|
| 368 |
+
| | |
|
| 369 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 370 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 371 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 372 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 373 |
+
| Series F | Non-telephone telecommunication services |
|
| 374 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 375 |
+
| Series H | Audiovisual and multimedia systems |
|
| 376 |
+
| Series I | Integrated services digital network |
|
| 377 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 378 |
+
| Series K | Protection against interference |
|
| 379 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 380 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 381 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 382 |
+
| Series O | Specifications of measuring equipment |
|
| 383 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 384 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 385 |
+
| Series R | Telegraph transmission |
|
| 386 |
+
| Series S | Telegraph services terminal equipment |
|
| 387 |
+
| Series T | Terminals for telematic services |
|
| 388 |
+
| Series U | Telegraph switching |
|
| 389 |
+
| Series V | Data communication over the telephone network |
|
| 390 |
+
| Series X | Data networks, open system communications and security |
|
| 391 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 392 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.8-202401-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.8-202401-I_PDF-E/8eda6e54bb820fa3f0e0b4a96f35504d_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.8-202401-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,354 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Recommendation **ITU-T A.8 (01/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
---
|
| 8 |
+
|
| 9 |
+
## **Alternative approval process for new and revised ITU-T Recommendations**
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
# Recommendation ITU-T A.8
|
| 14 |
+
|
| 15 |
+
## Alternative approval process for new and revised ITU-T Recommendations
|
| 16 |
+
|
| 17 |
+
## Summary
|
| 18 |
+
|
| 19 |
+
Recommendation ITU-T A.8 provides working methods and procedures for approving draft new and revised ITU-T Recommendations using the alternative approval process.
|
| 20 |
+
|
| 21 |
+
While this edition does not modify the alternative approval process, it:
|
| 22 |
+
|
| 23 |
+
- Adds clarification on copyright clearance;
|
| 24 |
+
- consolidates into ITU-T A.8 text concerning steps following updates to normative references during comment resolution (mirroring text from Recommendation ITU-T A.5);
|
| 25 |
+
- streamlines the deadlines for availability of resolved drafts after comment resolution;
|
| 26 |
+
- reinstates the provisions from Recommendation ITU-T A.8 (2008) which are more accurate concerning the deletion of Recommendations approved under AAP;
|
| 27 |
+
- includes a redrawn Figure 1 to better illustrate the various steps of the AAP, with updates to the respective notes.
|
| 28 |
+
|
| 29 |
+
## History \*
|
| 30 |
+
|
| 31 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 32 |
+
|---------|----------------|------------|-------------|--------------------|
|
| 33 |
+
| 1.0 | ITU-T A.8 | 2000-10-06 | TSAG | 11.1002/1000/5198 |
|
| 34 |
+
| 2.0 | ITU-T A.8 | 2004-10-14 | TSAG | 11.1002/1000/7420 |
|
| 35 |
+
| 3.0 | ITU-T A.8 | 2006-07-07 | TSAG | 11.1002/1000/8794 |
|
| 36 |
+
| 4.0 | ITU-T A.8 | 2008-10-30 | TSAG | 11.1002/1000/9641 |
|
| 37 |
+
| 5.0 | ITU-T A.8 | 2022-03-09 | TSAG | 11.1002/1000/14986 |
|
| 38 |
+
| 6.0 | ITU-T A.8 | 2024-01-26 | TSAG | 11.1002/1000/15578 |
|
| 39 |
+
|
| 40 |
+
## Keywords
|
| 41 |
+
|
| 42 |
+
AAP, approval, procedures, Recommendation, working methods.
|
| 43 |
+
|
| 44 |
+
---
|
| 45 |
+
|
| 46 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 47 |
+
|
| 48 |
+
## FOREWORD
|
| 49 |
+
|
| 50 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 51 |
+
|
| 52 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 53 |
+
|
| 54 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 55 |
+
|
| 56 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 57 |
+
|
| 58 |
+
## NOTE
|
| 59 |
+
|
| 60 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 61 |
+
|
| 62 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 63 |
+
|
| 64 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 65 |
+
|
| 66 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 67 |
+
|
| 68 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 69 |
+
|
| 70 |
+
© ITU 2024
|
| 71 |
+
|
| 72 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 73 |
+
|
| 74 |
+
## Table of Contents
|
| 75 |
+
|
| 76 |
+
| | <b>Page</b> |
|
| 77 |
+
|-----------------------------------------------------|-------------|
|
| 78 |
+
| 1 General..... | 1 |
|
| 79 |
+
| 2 Process ..... | 1 |
|
| 80 |
+
| 3 Prerequisites..... | 1 |
|
| 81 |
+
| 4 Last call and additional review ..... | 2 |
|
| 82 |
+
| 5 Procedure at study group meetings..... | 4 |
|
| 83 |
+
| 6 Notification..... | 5 |
|
| 84 |
+
| 7 Correction of defects..... | 5 |
|
| 85 |
+
| 8 Deletion of Recommendations ..... | 6 |
|
| 86 |
+
| 8.1 Deletion of Recommendations by WTSA..... | 6 |
|
| 87 |
+
| 8.2 Deletion of Recommendations between WTSAs ..... | 6 |
|
| 88 |
+
| Annex A – Table of comments ..... | 10 |
|
| 89 |
+
|
| 90 |
+
|
| 91 |
+
|
| 92 |
+
# **Recommendation ITU-T A.8**
|
| 93 |
+
|
| 94 |
+
## **Alternative approval process for new and revised ITU-T Recommendations**
|
| 95 |
+
|
| 96 |
+
## **1 General**
|
| 97 |
+
|
| 98 |
+
**1.1** Recommendations of the ITU Telecommunication Standardization Sector (ITU-T) will be approved using this alternative approval process (AAP), except Recommendations that have policy or regulatory implications, which will be approved using the traditional approval process (TAP) found in Resolution 1 of the World Telecommunication Standardization Assembly (WTSA).
|
| 99 |
+
|
| 100 |
+
The competent study group may also seek approval at a World Telecommunication Standardization Assembly (WTSA).
|
| 101 |
+
|
| 102 |
+
**1.2** In accordance with the ITU Convention, the status of Recommendations approved is the same for both AAP and TAP methods of approval.
|
| 103 |
+
|
| 104 |
+
## **2 Process**
|
| 105 |
+
|
| 106 |
+
**2.1** Study groups should apply the AAP described in clauses 3 to 6 for seeking the approval of draft new and revised Recommendations as soon as they have been developed to a sufficiently mature state. Figure 1 depicts the sequence of events.
|
| 107 |
+
|
| 108 |
+
NOTE – In case of discrepancy, clauses 3 to 6 prevail over Figure 1.
|
| 109 |
+
|
| 110 |
+
## **3 Prerequisites**
|
| 111 |
+
|
| 112 |
+
**3.1** Upon request of the study group chair, the Director of the Telecommunication Standardization Bureau (TSB) shall announce the intention to apply AAP and to initiate the last call set out in this Recommendation (see clause 4). Such action shall be based upon consent at a study group or working party meeting or, exceptionally, at a WTSA, that a draft Recommendation is sufficiently mature for such action. At this stage, the draft Recommendation is considered to have "CONSENT". The Director shall include a summary of the draft Recommendation in the announcement. Reference shall be provided to the documentation where the text of the draft new or revised Recommendation to be considered may be found. This information shall be made available to all Member States and Sector Members.
|
| 113 |
+
|
| 114 |
+
**3.2** The text of the draft new or revised Recommendation must be available to TSB in a final edited form at the time that the Director makes the announcement of the intended application of the AAP set out in this Recommendation. Any associated electronic material included in the Recommendation (e.g., software, test vectors, etc.) must also be made available to TSB at the same time. Recommendation ITU-T A.5 provides generic procedures for normatively referencing documents of other organizations in ITU-T Recommendations. A summary that reflects the final edited text of the draft Recommendation must also be provided to TSB, in accordance with clause 3.3.
|
| 115 |
+
|
| 116 |
+
**3.3** Such a summary should be prepared in accordance with the Author's Guide for drafting ITU-T Recommendations<sup>1</sup>. This summary is a brief outline of the purpose and content of the new or revised draft Recommendation and, where appropriate, the intent of the revisions. No Recommendation shall be considered as complete and ready for approval without this summary statement.
|
| 117 |
+
|
| 118 |
+
---
|
| 119 |
+
|
| 120 |
+
<sup>1</sup> The Author's guide can be downloaded from: <http://handle.itu.int/11.1002/plink/8306947125>
|
| 121 |
+
|
| 122 |
+
**3.4** Approval may only be sought for a draft new or revised Recommendation within the study group's mandate as defined by the Questions allocated to it, in accordance with No. 192 of the Convention. Alternatively, or additionally, approval may be sought for amendment of an existing Recommendation within the study group's responsibility and mandate.
|
| 123 |
+
|
| 124 |
+
**3.5** Where a draft new or revised Recommendation falls within the mandate of more than one study group, the chair of the study group proposing the approval should consult and take into account the views of any other study group chairs concerned before proceeding with the application of this approval procedure.
|
| 125 |
+
|
| 126 |
+
**3.6** Recommendations are to be elaborated in accordance with the Common Patent Policy for ITU-T/ITU-R/ISO/IEC, the ITU Software Copyright Guidelines and the ITU-T Guidelines related to the inclusion of Marks in ITU-T Recommendations, available at <https://www.itu.int/ipr>, and by taking into consideration possible copyright restrictions for texts or pictures taken from external sources (see also clause 4.2). For example:
|
| 127 |
+
|
| 128 |
+
**3.6.1** Any party participating in the work of ITU-T should, from the outset, draw the attention of the Director of TSB to any known patent or to any known pending patent application, either of their own or of other organizations. The "Patent Statement and Licensing Declaration" form from the ITU-T website is to be used.
|
| 129 |
+
|
| 130 |
+
**3.6.2** ITU-T non-member organizations that hold patent(s) or pending patent application(s), the use of which may be required in order to implement an ITU-T Recommendation, can submit a "Patent Statement and Licensing Declaration" to TSB using the form available at the ITU-T website.
|
| 131 |
+
|
| 132 |
+
**3.7** In the interests of stability, once a new or revised Recommendation has been approved, approval should not normally be sought within a reasonable period of time for any further amendment of that new text or that revised portion, respectively, unless the proposed amendment complements rather than changes the agreement reached in the previous approval process, or a significant error or omission is discovered. As a guideline, in this context "a reasonable period of time" would be at least two years, in most cases.
|
| 133 |
+
|
| 134 |
+
Amendments that correct defects may be approved, in accordance with clause 7.1.
|
| 135 |
+
|
| 136 |
+
## **4 Last call and additional review**
|
| 137 |
+
|
| 138 |
+
**4.1** The last call encompasses the four-week period and procedures beginning with the Director's announcement of the intention to apply the alternative approval process (clause 3.1).
|
| 139 |
+
|
| 140 |
+
**4.2** If TSB has received a statement(s) indicating that the use of intellectual property, protected by one or more copyright(s) or patent(s), issued or pending, may be required in order to implement a draft Recommendation, the Director shall post this information on the ITU-T website.
|
| 141 |
+
|
| 142 |
+
**4.3** The Director of TSB shall advise the Directors of the other two Bureaux that Member States and Sector Members are being asked to comment on the approval of a proposed new or revised Recommendation.
|
| 143 |
+
|
| 144 |
+
**4.4** During the last call, should any Member State or Sector Member be of the opinion that the draft new or revised Recommendation should not be approved, they should advise their reasons for disapproving and indicate the possible changes that would facilitate further consideration and approval of the draft new or revised Recommendation. TSB will make the comments available to the membership of ITU-T.
|
| 145 |
+
|
| 146 |
+
**4.4.1** If no comments, other than those indicating typographical errors (misspelling, syntactical and punctuation mistakes, etc.), are received by the end of the last call, the draft new or revised Recommendation is considered as approved, and the typographical errors are corrected.
|
| 147 |
+
|
| 148 |
+
**4.4.2** If comments, other than those indicating typographical errors, are received by the end of the last call, the study group chair, in consultation with TSB, makes the judgement whether:
|
| 149 |
+
|
| 150 |
+
- a) a planned study group meeting is sufficiently close to consider the draft Recommendation for approval, in which case the procedures in clause 4.6 regarding approval at a study group meeting are applied; or
|
| 151 |
+
- b) to save time and/or because of the nature and maturity of the work, comment resolution should be initiated under the direction of the study group chair. This will be accomplished by appropriate study group experts, via electronic correspondence or at meetings. Revised, edited draft text is prepared, as appropriate, and the procedures beginning in clause 4.4.3 are applied.
|
| 152 |
+
|
| 153 |
+
**4.4.3** If comments, other than those indicating typographical errors, are received at the end of the last call process, the rapporteur, with the assistance of the editor, shall, normally within two weeks of the end of the last call, compile all such comments in a single document, for example in the form of a table (see Annex A), to be used as the basis for completion of the comment resolution process.
|
| 154 |
+
|
| 155 |
+
**4.4.4** After comment resolution is completed, and the revised and edited draft text is made available, the study group chair, in consultation with TSB, makes the judgement whether:
|
| 156 |
+
|
| 157 |
+
- a) a planned study group meeting is sufficiently close to consider the draft Recommendation for approval, in which case the procedures in clause 4.6 are applied; or
|
| 158 |
+
- b) to save time and/or because of the nature and maturity of the work, an additional review should be initiated, in which case the procedures in clause 4.5 are applied; or
|
| 159 |
+
- c) a new normative reference has been added to a referenced organization that is not already qualified according to the criteria in Recommendation ITU-T A.5, Annex B, in which case the procedures in clause 4.6 are applied.
|
| 160 |
+
|
| 161 |
+
**4.5** The additional review encompasses a three-week period and will be announced by the Director. The text (including any revisions as a result of comment resolution) of the draft Recommendation in a final edited form and comments from the last call with their resolution compiled in a single document (for example in the form of a table as suggested in Annex A) must be made available to TSB at the time that the Director makes the announcement of the additional review. Reference shall be provided to the documentation where the text of the draft Recommendation and last call comments to be considered may be found.
|
| 162 |
+
|
| 163 |
+
NOTE – If a new normative reference has been added as a result of comment resolution, a reference to the ITU-T A.5 justification is included in the comment resolution (see Recommendation ITU-T A.5, clause 6.4).
|
| 164 |
+
|
| 165 |
+
**4.5.1** If no comments, other than those indicating typographical errors (misspelling, syntactical and punctuation mistakes, etc.), are received by the end of the additional review, the Recommendation is considered as approved, and the typographical errors are corrected by TSB.
|
| 166 |
+
|
| 167 |
+
**4.5.2** If comments other than those indicating typographical errors, are received by the end of the additional review, then the procedures in clause 4.6 regarding approval at a study group meeting are applied.
|
| 168 |
+
|
| 169 |
+
NOTE – This covers the case where a new normative reference is added as a result of resolution of comments submitted during an AAP additional review, or concerns were expressed about a new normative reference added as a result of resolution of comments submitted during an AAP last call.
|
| 170 |
+
|
| 171 |
+
**4.6** The Director shall explicitly announce the intention to approve the draft Recommendation at least three weeks prior to the study group meeting. The Director shall include the specific intent of the proposal in summarized form. Reference shall be provided to the documentation where the draft text and comments from the last call (and additional review, if relevant) may be found. The text (including any revisions as a result of comment resolution) of the draft Recommendation in a final edited form, and a single document compiling comments from the last call (or additional review) and their resolution (for example in the form of a table as suggested in Annex A) must be made available to TSB at the time that the Director makes the announcement. The edited text of the draft
|
| 172 |
+
|
| 173 |
+
Recommendation from the additional review (or last call if there is no additional review) is submitted for approval by the study group meeting in accordance with clause 5.
|
| 174 |
+
|
| 175 |
+
## **5 Procedure at study group meetings**
|
| 176 |
+
|
| 177 |
+
**5.1** The study group should review the text of the draft new or revised Recommendation and the associated comments in the documentation referred to in clause 4.6. The meeting may then accept any corrections or amendments to the draft new or revised Recommendation. The study group should reassess the summary statement in terms of its completeness.
|
| 178 |
+
|
| 179 |
+
**5.2** Changes may only be made during the meeting as a consequence of written comments as a result of the last call, additional review, contributions, or temporary documents including liaison statements. Where proposals for such revisions are found to be justified but to have a major impact on the intent of the Recommendation or to depart from points of principle agreed at the previous study group or working party meeting, consideration of this approval procedure should not be applied at this meeting. However, in justified circumstances, the approval procedure may still be applied if the chair of the study group, in consultation with TSB, considers:
|
| 180 |
+
|
| 181 |
+
- that the proposed changes are reasonable (in the context of the documentation described in this clause) for those Member States and Sector Members not represented at the meeting, or not represented adequately under the changed circumstances; and
|
| 182 |
+
- that the proposed text is stable.
|
| 183 |
+
|
| 184 |
+
However, if a Member State present declares that this text has policy or regulatory implications or there is a doubt, the approval procedure shall proceed according to WTSA Resolution 1, clause 9.3 or clause 5.8.
|
| 185 |
+
|
| 186 |
+
**5.3** After debate at the study group meeting, the decision of the meeting to approve the Recommendation under this approval procedure must be unopposed (but see clauses 5.5, 5.7 and 5.8). Every effort should be made to reach unopposed agreement.
|
| 187 |
+
|
| 188 |
+
**5.4** If, despite these attempts, unopposed agreement has not been reached, the Recommendation is considered as approved if, following consultation with their Sector Members present, no more than one Member State present in the meeting opposes the decision to approve the Recommendation (but see clauses 5.5, 5.6 and 5.8). Otherwise, the study group may authorize additional work to address the remaining issues.
|
| 189 |
+
|
| 190 |
+
**5.5** In cases where a Member State or Sector Member does not elect to oppose approval of a text but would like to register a degree of concern on one or more aspects, this shall be noted in the report of the meeting. Such concerns shall be mentioned in a concise note appended to the text of the Recommendation concerned.
|
| 191 |
+
|
| 192 |
+
**5.6** A decision must be reached during the meeting on the basis of a text available in its final form to all participants at the meeting. Exceptionally, but only during the meeting, a Member State may request more time to consider its position for clause 5.4. Unless the Director of TSB is advised of their opposition within a period of four weeks from the end of the meeting, the Recommendation is approved, and the Director shall proceed in accordance with clause 6.1.
|
| 193 |
+
|
| 194 |
+
**5.6.1** A Member State that requested more time to consider its position and that then indicates disapproval within the four-week interval specified in clause 5.6 is requested to include its reasons and to indicate the possible changes that would facilitate further consideration, if required, for future approval of the draft new or revised Recommendation.
|
| 195 |
+
|
| 196 |
+
**5.7** A Member State or Sector Member may advise at the meeting that it is abstaining from the application of the procedure. Their presence shall then be ignored for the purposes of clause 5.3. Such an abstention may subsequently be revoked, but only during the course of the meeting.
|
| 197 |
+
|
| 198 |
+
**5.8** If the draft new or revised Recommendation is not approved, the study group chair, after consultation with the parties concerned, may proceed according to clause 3.1, without further CONSENT at a subsequent working party or study group meeting.
|
| 199 |
+
|
| 200 |
+
## **6 Notification**
|
| 201 |
+
|
| 202 |
+
**6.1** The Director of TSB shall promptly notify the membership of the results (indicating approval or non-approval) of the last call and additional review.
|
| 203 |
+
|
| 204 |
+
**6.2** Within two weeks of the closing date of the study group meeting described in clauses 5.3 to 5.5 or, exceptionally, two weeks after the period described in clause 5.6, the Director shall notify by a circular whether the text is approved or not. The Director shall arrange for this information to also be included in the next available ITU Operational Bulletin. Within this same period, the Director shall also ensure that any Recommendation approved is available online, with an indication that the Recommendation may not be in its final publication form.
|
| 205 |
+
|
| 206 |
+
**6.3** Should minor, purely editorial amendments or correction of evident oversights or inconsistencies in the text as presented for approval be necessary, TSB may correct these with the approval of the chair of the study group.
|
| 207 |
+
|
| 208 |
+
**6.4** The Secretary-General shall publish the approved new or revised Recommendations as soon as practicable, indicating, as necessary, a date of entry into effect. However, in accordance with Recommendation ITU-T A.11, minor amendments may be covered by corrigenda rather than a complete reissue. Also, where appropriate, texts may be grouped to suit market needs.
|
| 209 |
+
|
| 210 |
+
**6.5** Text shall be added to the cover sheets of all new and revised Recommendations urging users to consult the ITU-T patent database and the ITU-T software copyright database. Suggested wording is:
|
| 211 |
+
|
| 212 |
+
"ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed intellectual property right. ITU takes no position concerning the evidence, validity or applicability of claimed intellectual property rights, whether asserted by ITU Member States and Sector Members or by others outside of the Recommendation development process."
|
| 213 |
+
|
| 214 |
+
"As of the date of approval of this Recommendation, ITU had/had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available at the ITU-T website."
|
| 215 |
+
|
| 216 |
+
**6.6** See Recommendation ITU-T A.11 concerning the publication of new and revised Recommendations.
|
| 217 |
+
|
| 218 |
+
## **7 Correction of defects**
|
| 219 |
+
|
| 220 |
+
**7.1** When a study group identifies the need for implementers to be made aware of defects (e.g., typographical errors, editorial errors, ambiguities, omissions or inconsistencies and technical errors) in a Recommendation, one mechanism that may be employed is an implementer's guide. This guide is a historical document recording all identified defects and their status of correction, from their identification to final resolution. Implementer's guides shall be agreed by the study group, or agreed by one of its working parties with the concurrence of the study group chair. Implementer's guides shall be made available by posting on the ITU-T website with open access.
|
| 221 |
+
|
| 222 |
+
## **8 Deletion of Recommendations**
|
| 223 |
+
|
| 224 |
+
### **8.1 Deletion of Recommendations by WTSA**
|
| 225 |
+
|
| 226 |
+
Upon the decision of the study group, the chair shall include in the report to WTSA the request to delete a Recommendation. WTSA may approve this request.
|
| 227 |
+
|
| 228 |
+
### **8.2 Deletion of Recommendations between WTSAs**
|
| 229 |
+
|
| 230 |
+
**8.2.1** At a study group meeting it may be agreed to delete a Recommendation, i.e. because it has been superseded by another Recommendation or because it has become obsolete. This agreement by the Member States and Sector Members present at the meeting must be unopposed. If unopposed agreement has not been reached, the same criteria as in clause 5.4 are applied. Information about this agreement, including an explanatory summary about the reasons for the deletion, shall be provided by a circular. If no objection to the deletion is received from a Member State or a Sector Member within three months, the deletion will come into force. In the case of objection, the matter will be referred back to the study group.
|
| 231 |
+
|
| 232 |
+
**8.2.2** Notification of the result will be given in another circular, and TSAG will be informed by a report from the Director of TSB. In addition, the Director shall publish a list of deleted Recommendations whenever appropriate, but at least once by the middle of a study period.
|
| 233 |
+
|
| 234 |
+
|
| 235 |
+
|
| 236 |
+
```
|
| 237 |
+
|
| 238 |
+
graph TD
|
| 239 |
+
Start([1 SG or WP consent]) --> LC[2 Edited text available for LC]
|
| 240 |
+
LC --> AnnLC[3 Director's announcement and posting for LC]
|
| 241 |
+
AnnLC --> WaitLC[LC 4 weeks]
|
| 242 |
+
WaitLC --> JudLC{4 LC judgement}
|
| 243 |
+
|
| 244 |
+
JudLC -- "4a No comment other than typographical errors" --> End([12 Director's notification and publication of the approved Recommendation])
|
| 245 |
+
JudLC -- "4b Comments and a sufficiently close SG meeting" --> AnnSG[5 Director's announcement and posting 3 weeks in advance]
|
| 246 |
+
JudLC -- "4c Comments" --> Res[7 Comment resolution]
|
| 247 |
+
Res --> AR[8 Edited text available for AR]
|
| 248 |
+
AR --> JudAR{9 Next step judgement}
|
| 249 |
+
|
| 250 |
+
JudAR -- "9a Sufficiently close SG meeting" --> AnnSG
|
| 251 |
+
JudAR -- "9b Additional review" --> AnnAR[10 Director's announcement and posting for AR]
|
| 252 |
+
AnnAR --> WaitAR[AR 3 weeks]
|
| 253 |
+
WaitAR --> JudAR2{11 AR judgement}
|
| 254 |
+
|
| 255 |
+
JudAR2 -- "11a No comment other than typographical errors" --> End
|
| 256 |
+
JudAR2 -- "11b Comments" --> AnnSG
|
| 257 |
+
|
| 258 |
+
AnnSG --> DecSG{6 SG meeting decision}
|
| 259 |
+
DecSG -- "6b Approval" --> End
|
| 260 |
+
DecSG -- "6c Non-approval but new attempt" --> LC
|
| 261 |
+
DecSG -- "6a.i Policy or regulatory implications" --> Resol[WTSA Resolution 1]
|
| 262 |
+
DecSG -- "6a.ii Policy or regulatory implications" --> LC
|
| 263 |
+
|
| 264 |
+
```
|
| 265 |
+
|
| 266 |
+
LC: Last call
|
| 267 |
+
AR: Additional review
|
| 268 |
+
|
| 269 |
+
A.8(24)
|
| 270 |
+
|
| 271 |
+
Flowchart of the AAP sequence of events, showing the process from SG/ WP consent to the final Director's notification and publication of the approved Recommendation.
|
| 272 |
+
|
| 273 |
+
**Figure 1 – AAP sequence of events**
|
| 274 |
+
|
| 275 |
+
#### Notes to Figure 1 – AAP sequence of events
|
| 276 |
+
|
| 277 |
+
- 1) *SG or WP consent* – The study group or working party concludes that the work on a draft Recommendation is sufficiently mature to begin the alternative approval process and to initiate the last call (clause 3.1).
|
| 278 |
+
- 2) *Edited text available* – The final, edited, draft text, including summary, is provided to TSB, and the study group chair requests the Director to initiate the last call (clause 3.2). Any associated electronic material included in the Recommendation must also be made available to TSB at the same time.
|
| 279 |
+
- 3) *Director's last call announcement and posting* – The Director announces the beginning of the last call to all Member States, Sector Members and Associates, with reference to the summary and complete text. If the draft Recommendation has not already been electronically posted, it is done at this time (clause 3.1).
|
| 280 |
+
- 4) *Last call judgement* – The study group chair, in consultation with TSB, makes the judgement whether:
|
| 281 |
+
- a) no comments, other than those indicating typographical errors, have been received. In this case, the Recommendation is considered as approved (clause 4.4.1);
|
| 282 |
+
- b) a planned study group meeting is sufficiently close to consider the comments received (clause 4.4.2 a); or
|
| 283 |
+
- c) to save time and/or because of the nature and maturity of the work, comment resolution should be initiated leading to the preparation of edited texts (clause 4.4.2 b).
|
| 284 |
+
- 5) *Director's study group announcement and posting* – The Director announces that the next study group meeting will consider the draft Recommendation for approval and will include reference to either:
|
| 285 |
+
- a) the draft Recommendation (the edited text (LC) version) plus the comments received from the last call (clause 4.6); or
|
| 286 |
+
- b) if comment resolution has been carried out, the revised draft Recommendation text. If the revised draft Recommendation has not already been electronically posted, it is done at this time (clause 4.6).
|
| 287 |
+
- 6) *Study group decision meeting* – The study group meeting reviews and addresses all written comments and either:
|
| 288 |
+
- a) proceeds (i) under WTSA Resolution 1 or (ii) clause 5.8, as appropriate, if there might be policy or regulatory implications (clause 5.2); or
|
| 289 |
+
- b) approves the draft Recommendation (clause 5.3 or 5.4); or
|
| 290 |
+
- c) does not approve the draft Recommendation. If it is concluded that a further attempt at addressing comments received is appropriate, then additional work should be done and the process returns to step 2 (without further CONSENT at a working party or study group meeting) (clause 5.8).
|
| 291 |
+
- 7) *Comment resolution* – The study group chair, with assistance from TSB and experts, via electronic correspondence and rapporteur and working party meetings, where appropriate, addresses the comments and prepares a new edited draft Recommendation text (clause 4.4.3).
|
| 292 |
+
- 8) *Edited text available* – The revised edited text, including summary, is provided to TSB (clause 4.4.3).
|
| 293 |
+
- 9) *Next step judgement* – The study group chair, in consultation with TSB, makes the judgement whether:
|
| 294 |
+
- a) a planned study group meeting is sufficiently close to consider the draft Recommendation for approval (clause 4.4.4 a) or, as a result of comment resolution, a new normative
|
| 295 |
+
|
| 296 |
+
reference is added to a referenced organization that is not already qualified according to the criteria in Recommendation ITU-T A.5 (clause 4.4.4 c); or
|
| 297 |
+
|
| 298 |
+
- b) to save time and/or because of the nature and maturity of the work, an additional review should be initiated (clause 4.4.4 b).
|
| 299 |
+
- 10) *Director's additional review announcement and posting* – The Director announces the beginning of the additional review to all Member States and Sector Members, with reference to the summary and complete text of the revised draft Recommendation, and comments with their resolution compiled in a single document. If the revised draft Recommendation has not already been electronically posted, it is done at this time (clause 4.5).
|
| 300 |
+
- 11) *Additional review judgement* – The study group chair, in consultation with TSB, makes the judgement whether:
|
| 301 |
+
- a) no comments, other than those indicating typographical errors, have been received. In this case, the Recommendation is considered approved (clause 4.5.1); or
|
| 302 |
+
- b) comments, other than those indicating typographical errors, have been received. In this case, the process proceeds to the study group meeting (clause 4.5.2).
|
| 303 |
+
- 12) *Director's notification* – The Director notifies the members that the draft Recommendation has been approved (clause 6.1 or 6.2) (see Recommendation ITU-T A.11).
|
| 304 |
+
|
| 305 |
+
## **Annex A**
|
| 306 |
+
|
| 307 |
+
### **Table of comments**
|
| 308 |
+
|
| 309 |
+
(This annex forms an integral part of this Recommendation.)
|
| 310 |
+
|
| 311 |
+
Source of comments:
|
| 312 |
+
|
| 313 |
+
| | | | | <b>Date:</b> | <b>Document: Reference number and title</b> | |
|
| 314 |
+
|----------------------------------------------------------------------------|----------------------------|------------------------------|-----------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------|------------------------|
|
| 315 |
+
| <b>Comment number<br/>(include reference<br/>to source of<br/>comment)</b> | <b>Comment<br/>made by</b> | <b>Clause/<br/>Subclause</b> | <b>Paragraph/<br/>Figure/<br/>Table</b> | <b>Type of<br/>comment<br/>(Ed = editorial<br/>Te = technical<br/>Ge = general)</b> | <b>Comment</b> | <b>Proposed change</b> |
|
| 316 |
+
| | | | | | | |
|
| 317 |
+
| | | | | | | |
|
| 318 |
+
| | | | | | | |
|
| 319 |
+
| | | | | | | |
|
| 320 |
+
| | | | | | | |
|
| 321 |
+
| | | | | | | |
|
| 322 |
+
| | | | | | | |
|
| 323 |
+
| | | | | | | |
|
| 324 |
+
| | | | | | | |
|
| 325 |
+
|
| 326 |
+
|
| 327 |
+
|
| 328 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 329 |
+
|
| 330 |
+
| | |
|
| 331 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 332 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 333 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 334 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 335 |
+
| Series F | Non-telephone telecommunication services |
|
| 336 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 337 |
+
| Series H | Audiovisual and multimedia systems |
|
| 338 |
+
| Series I | Integrated services digital network |
|
| 339 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 340 |
+
| Series K | Protection against interference |
|
| 341 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 342 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 343 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 344 |
+
| Series O | Specifications of measuring equipment |
|
| 345 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 346 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 347 |
+
| Series R | Telegraph transmission |
|
| 348 |
+
| Series S | Telegraph services terminal equipment |
|
| 349 |
+
| Series T | Terminals for telematic services |
|
| 350 |
+
| Series U | Telegraph switching |
|
| 351 |
+
| Series V | Data communication over the telephone network |
|
| 352 |
+
| Series X | Data networks, open system communications and security |
|
| 353 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 354 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.Sup2-202212-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.Sup2-202212-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,139 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Supplement **ITU-T A Suppl. 2 (12/2022)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
|
| 7 |
+
## **Guidelines on interoperability experiments and proof-of-concept events**
|
| 8 |
+
|
| 9 |
+
|
| 10 |
+
|
| 11 |
+
## Supplement 2 to ITU-T A-series Recommendations
|
| 12 |
+
|
| 13 |
+
## Guidelines on interoperability experiments and proof-of-concept events
|
| 14 |
+
|
| 15 |
+
## Summary
|
| 16 |
+
|
| 17 |
+
These guidelines relate to interoperability experiments and proof-of-concept events to be performed outside of ITU-T. The guidelines have been prepared in order to encourage such experiments and events to be performed, and to facilitate information exchange between ITU-T and parties participating in such experiments.
|
| 18 |
+
|
| 19 |
+
## History
|
| 20 |
+
|
| 21 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID* |
|
| 22 |
+
|---------|------------------|------------|-------------|---------------------------------------------------------------------------|
|
| 23 |
+
| 1.0 | ITU-T A Suppl. 2 | 2000-06-14 | TSAG | <a href="http://handle.itu.int/11.1002/1000/5199">11.1002/1000/5199</a> |
|
| 24 |
+
| 2.0 | ITU-T A Suppl. 2 | 2022-12-16 | TSAG | <a href="http://handle.itu.int/11.1002/1000/15252">11.1002/1000/15252</a> |
|
| 25 |
+
|
| 26 |
+
## Keywords
|
| 27 |
+
|
| 28 |
+
Information exchange, interoperability experiment to be performed outside of ITU-T, proof-of-concept, quality of Recommendations.
|
| 29 |
+
|
| 30 |
+
---
|
| 31 |
+
|
| 32 |
+
\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
|
| 33 |
+
|
| 34 |
+
## FOREWORD
|
| 35 |
+
|
| 36 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 37 |
+
|
| 38 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 39 |
+
|
| 40 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 41 |
+
|
| 42 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 43 |
+
|
| 44 |
+
### NOTE
|
| 45 |
+
|
| 46 |
+
This is an informative ITU-T publication. Mandatory provisions, such as those found in ITU-T Recommendations, are outside the scope of this publication. This publication should only be referenced bibliographically in ITU-T Recommendations.
|
| 47 |
+
|
| 48 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 49 |
+
|
| 50 |
+
ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the publication development process.
|
| 51 |
+
|
| 52 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 53 |
+
|
| 54 |
+
© ITU 2023
|
| 55 |
+
|
| 56 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 57 |
+
|
| 58 |
+
## **Supplement 2 to ITU-T A-series Recommendations**
|
| 59 |
+
|
| 60 |
+
## **Guidelines on interoperability experiments and proof-of-concept events**
|
| 61 |
+
|
| 62 |
+
## **1 Scope**
|
| 63 |
+
|
| 64 |
+
These guidelines relate to interoperability experiments and proof-of-concept events to be performed outside of ITU-T. The guidelines have been prepared to encourage such experiments and events to be performed, and to facilitate information exchange between parties participating in such experiments and events, and ITU-T study groups developing relevant Recommendation(s).
|
| 65 |
+
|
| 66 |
+
## **2 References**
|
| 67 |
+
|
| 68 |
+
None.
|
| 69 |
+
|
| 70 |
+
## **3 Definitions**
|
| 71 |
+
|
| 72 |
+
None.
|
| 73 |
+
|
| 74 |
+
## **4 Abbreviations and acronyms**
|
| 75 |
+
|
| 76 |
+
PoC Proof-of-Concept
|
| 77 |
+
|
| 78 |
+
## **5 Conventions**
|
| 79 |
+
|
| 80 |
+
None.
|
| 81 |
+
|
| 82 |
+
## **6 Background**
|
| 83 |
+
|
| 84 |
+
**6.1** Study groups of ITU-T have been doing their best to ensure interoperability of products made in accordance with ITU-T Recommendations. There is no better way to assess interoperability than to actually interoperate systems and equipment of various manufacturers. ITU-T has occasionally initiated interoperability experiments for specific projects in the past.
|
| 85 |
+
|
| 86 |
+
**6.2** However, when interoperability experiment/testing has not been performed, users may have suffered from the lack of interoperability between products coming from different manufacturers. Moreover, manufacturers are not always members of ITU-T and develop their products only by reading relevant Recommendations.
|
| 87 |
+
|
| 88 |
+
**6.3** In addition, following the rapid development of new technologies, the proof-of-concept (PoC) is used by different standards development organizations as a useful tool to determine the feasibility of the concept, technology or solution, or to verify that it will function as intended and according to the features defined in particular standards that are under development. This approach may significantly help ITU standardization activities to understand whether the concept, technology or solution is viable, and provide useful information in order to advance work items under study or to evolve the standards of interest.
|
| 89 |
+
|
| 90 |
+
## **7 Objective**
|
| 91 |
+
|
| 92 |
+
The objective of these guidelines is to encourage interoperability experiments and PoC events to be performed outside of ITU-T and to facilitate information exchange between parties participating in such experiments and study groups of ITU-T.
|
| 93 |
+
|
| 94 |
+
## **8 Guidelines**
|
| 95 |
+
|
| 96 |
+
**8.1** The interoperability experiments and PoC events are to be performed outside of ITU-T on a voluntary basis, self-governed, self-supporting and incurring no additional cost to ITU-T. Such interoperability experiments and PoC events may therefore involve non ITU-T members as well.
|
| 97 |
+
|
| 98 |
+
**8.2** The self-governance of interoperability experiments and PoC events to be performed outside of ITU-T means that parties participating in such an experiment or event should govern themselves by making rules of their own. ITU-T is in no way involved in such rule making.
|
| 99 |
+
|
| 100 |
+
**8.3** ITU-T would like to ask the kind cooperation of its members participating in such an interoperability experiment or PoC event to submit contributions to study groups based on the results of the interoperability experiment or PoC event in order to advance ongoing work items and improve the quality of Recommendations, e.g., by proposing text changes to remove ambiguities, etc.
|
| 101 |
+
|
| 102 |
+
**8.4** Furthermore, ITU-T would like to ask the kind cooperation of its members participating in such an interoperability experiment or PoC event to share as much information as possible on its experiment or event at study group meetings. Examples of information that would be useful to be shared are as follows:
|
| 103 |
+
|
| 104 |
+
- the results of the experiment or event;
|
| 105 |
+
- how should interoperability experiments or PoC events be performed: description of the experiment or event, testing or PoC methods, test equipment, experiment schedules, coordinator, etc.;
|
| 106 |
+
- where have interoperability experiments or PoC events been conducted or are going to be conducted;
|
| 107 |
+
- how should testing or PoC results be handled in order to submit contributions to ITU-T to advance ongoing work items and improve the quality of ITU-T Recommendations;
|
| 108 |
+
- identification of other activities in the same area and potential cooperation and work-sharing with them.
|
| 109 |
+
|
| 110 |
+
|
| 111 |
+
|
| 112 |
+
## **SERIES OF ITU-T RECOMMENDATIONS**
|
| 113 |
+
|
| 114 |
+
### **Series A Organization of the work of ITU-T**
|
| 115 |
+
|
| 116 |
+
| | |
|
| 117 |
+
|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 118 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 119 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 120 |
+
| Series F | Non-telephone telecommunication services |
|
| 121 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 122 |
+
| Series H | Audiovisual and multimedia systems |
|
| 123 |
+
| Series I | Integrated services digital network |
|
| 124 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 125 |
+
| Series K | Protection against interference |
|
| 126 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 127 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 128 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 129 |
+
| Series O | Specifications of measuring equipment |
|
| 130 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 131 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 132 |
+
| Series R | Telegraph transmission |
|
| 133 |
+
| Series S | Telegraph services terminal equipment |
|
| 134 |
+
| Series T | Terminals for telematic services |
|
| 135 |
+
| Series U | Telegraph switching |
|
| 136 |
+
| Series V | Data communication over the telephone network |
|
| 137 |
+
| Series X | Data networks, open system communications and security |
|
| 138 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 139 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.Sup3-201207-I_PDF-E/750009de35904633a4b5a89996010b7a_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.Sup3-201207-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,362 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
# ITU-T
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
## Series A
|
| 12 |
+
|
| 13 |
+
### Supplement 3
|
| 14 |
+
|
| 15 |
+
(07/2012)
|
| 16 |
+
|
| 17 |
+
SERIES A: ORGANIZATION OF THE WORK OF ITU-T
|
| 18 |
+
|
| 19 |
+
---
|
| 20 |
+
|
| 21 |
+
# **IETF and ITU-T collaboration guidelines**
|
| 22 |
+
|
| 23 |
+
ITU-T A-series Recommendations – Supplement 3
|
| 24 |
+
|
| 25 |
+
|
| 26 |
+
|
| 27 |
+
The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with two red lightning bolts striking it. To the right of the globe, the text "ITU" is written in a large, bold, blue font, and below it, the words "International Telecommunication Union" are written in a smaller, blue font.
|
| 28 |
+
|
| 29 |
+
ITU logo: a blue globe with red lightning bolts and the text 'ITU International Telecommunication Union'
|
| 30 |
+
|
| 31 |
+
|
| 32 |
+
|
| 33 |
+
# **Supplement 3 to ITU-T A-series Recommendations**
|
| 34 |
+
|
| 35 |
+
# **IETF and ITU-T collaboration guidelines**
|
| 36 |
+
|
| 37 |
+
# **Summary**
|
| 38 |
+
|
| 39 |
+
This Supplement provides guidance to aid in the understanding of collaboration on standards development between ITU-T and the Internet Society (ISOC)/Internet Engineering Task Force (IETF).
|
| 40 |
+
|
| 41 |
+
## **History**
|
| 42 |
+
|
| 43 |
+
| Edition | Recommendation | Approval | Study Group |
|
| 44 |
+
|---------|------------------|------------|-------------|
|
| 45 |
+
| 1.0 | ITU-T A Suppl. 3 | 2001-11-30 | TSAG |
|
| 46 |
+
| 2.0 | ITU-T A Suppl. 3 | 2012-07-04 | TSAG |
|
| 47 |
+
|
| 48 |
+
# FOREWORD
|
| 49 |
+
|
| 50 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 51 |
+
|
| 52 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 53 |
+
|
| 54 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 55 |
+
|
| 56 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 57 |
+
|
| 58 |
+
## NOTE
|
| 59 |
+
|
| 60 |
+
In this publication, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 61 |
+
|
| 62 |
+
Compliance with this publication is voluntary. However, the publication may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the publication is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the publication is required of any party.
|
| 63 |
+
|
| 64 |
+
# INTELLECTUAL PROPERTY RIGHTS
|
| 65 |
+
|
| 66 |
+
ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the publication development process.
|
| 67 |
+
|
| 68 |
+
As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this publication. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 69 |
+
|
| 70 |
+
© ITU 2012
|
| 71 |
+
|
| 72 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 73 |
+
|
| 74 |
+
## Table of Contents
|
| 75 |
+
|
| 76 |
+
| | | Page |
|
| 77 |
+
|-----|---------------------------------------------------|------|
|
| 78 |
+
| 1 | Introduction and scope..... | 1 |
|
| 79 |
+
| 2 | Guidance on collaboration..... | 2 |
|
| 80 |
+
| 2.1 | How to interact on ITU-T or IETF work items ..... | 2 |
|
| 81 |
+
| 2.2 | Representation ..... | 3 |
|
| 82 |
+
| 2.3 | Communication outside of meetings ..... | 3 |
|
| 83 |
+
| 2.4 | Mailing lists ..... | 4 |
|
| 84 |
+
| 2.5 | Document sharing..... | 4 |
|
| 85 |
+
| 2.6 | Simple cross referencing ..... | 5 |
|
| 86 |
+
| 2.7 | Preliminary work efforts..... | 5 |
|
| 87 |
+
| 2.8 | Additional items ..... | 5 |
|
| 88 |
+
| 3 | References..... | 7 |
|
| 89 |
+
| 3.1 | Normative references..... | 7 |
|
| 90 |
+
| 3.2 | Informative references..... | 7 |
|
| 91 |
+
|
| 92 |
+
|
| 93 |
+
|
| 94 |
+
# Supplement 3 to ITU-T A-series Recommendations
|
| 95 |
+
|
| 96 |
+
# IETF and ITU-T collaboration guidelines
|
| 97 |
+
|
| 98 |
+
# 1 Introduction and scope
|
| 99 |
+
|
| 100 |
+
This document provides non-normative guidance to aid in the understanding of collaboration on standards development between the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) and the Internet Engineering Task Force (IETF) of the Internet Society (ISOC). Early identification of topics of mutual interest will allow for constructive efforts between the two organizations based on mutual respect.
|
| 101 |
+
|
| 102 |
+
In the IETF, work is done in working groups (WGs), mostly through open, public mailing lists rather than face-to-face meetings. WGs are organized into areas, each area being managed by two co-area directors. Collectively, the area directors comprise the Internet Engineering Steering Group (IESG).
|
| 103 |
+
|
| 104 |
+
In the ITU-T, work is defined by study Questions which are worked on mostly through meetings led by rapporteurs (these are sometimes called "rapporteur's group" meetings). Questions are generally grouped within working parties (WPs) led by a WP chairman. Working parties report to a parent study group (SG) led by an SG chairman. Work may also be conducted in ITU-T focus groups (see clause 2.7).
|
| 105 |
+
|
| 106 |
+
To foster ongoing communication between the ITU-T and IETF, it is important to identify and establish contact points within each organization. Contact points may include:
|
| 107 |
+
|
| 108 |
+
### 1. ITU-T study group chairman and IETF area director
|
| 109 |
+
|
| 110 |
+
An IETF area director is the individual responsible for overseeing a major focus of activity with a scope similar to that of an ITU-T study group chairman. These positions are both relatively long-term (of several years) and offer the stability of contact points between the two organizations for a given topic.
|
| 111 |
+
|
| 112 |
+
### 2. ITU-T rapporteur and IETF working group chair
|
| 113 |
+
|
| 114 |
+
An IETF working group chair is an individual who is assigned to lead the work on a specific task within one particular area with a scope similar to that of an ITU-T rapporteur. These positions are working positions (of a year or more) that typically end when the work on a specific topic ends. Collaboration here is very beneficial to ensure the actual work gets done.
|
| 115 |
+
|
| 116 |
+
### 3. Other contact points
|
| 117 |
+
|
| 118 |
+
It may be beneficial to establish additional contact points for specific topics of mutual interest. These contact points should be established early in the work effort, and in some cases the contact point identified by each organization may be the same individual. ITU-T has an additional level of management, the working party chairman. From time to time, it may be beneficial for this person to exchange views with IETF working group chairs and area directors.
|
| 119 |
+
|
| 120 |
+
NOTE — The current list of IETF area directors and working group chairs can be found in the IETF working group charters. The current ITU-T study group chairmen and rapporteurs are listed on the ITU-T study group web pages.
|
| 121 |
+
|
| 122 |
+
# **2 Guidance on collaboration**
|
| 123 |
+
|
| 124 |
+
This clause describes how the existing processes within the IETF and ITU-T may be utilized to enable collaboration between the organizations.
|
| 125 |
+
|
| 126 |
+
## **2.1 How to interact on ITU-T or IETF work items**
|
| 127 |
+
|
| 128 |
+
Study groups that have identified work topics that are related to the Internet protocol (IP) should evaluate the relationship with topics defined in the IETF. Current IETF working groups and their charters (IETF definition of the scope of work) are listed in the IETF archives (see clause 2.8.1).
|
| 129 |
+
|
| 130 |
+
A study group may decide that development of a Recommendation on a particular topic may benefit from collaboration with the IETF. The study group should identify this collaboration in its work plan (specifically in that of each Question involved), describing the goal of the collaboration and its expected outcome.
|
| 131 |
+
|
| 132 |
+
An IETF working group should also evaluate and identify areas of relationship with the ITU-T and document the collaboration with the ITU-T study group in its charter.
|
| 133 |
+
|
| 134 |
+
The following clauses outline a process that can be used to enable each group to be informed about the other's new work items.
|
| 135 |
+
|
| 136 |
+
#### **2.1.1 How the ITU-T is informed about existing IETF work items**
|
| 137 |
+
|
| 138 |
+
The responsibility is on individual study groups to review the current IETF working groups to determine if there are any topics of mutual interest. Working group charters and active Internet-Drafts can be found on the IETF web site (<http://datatracker.ietf.org/wg/>). If a study group identifies a common area of work, the study group leadership should contact both the IETF working group chair and the area director(s) responsible. This may be accompanied by a formal liaison statement (see clause 2.3).
|
| 139 |
+
|
| 140 |
+
#### **2.1.2 How the IETF is informed about existing ITU-T work items**
|
| 141 |
+
|
| 142 |
+
The IETF through its representatives will review the current work of the various study groups from time to time. Each ITU-T study group's web page on the ITU-T web site contains its current list of Questions as well as its current work programme. When an area or working group identifies a common area of work, the matter is referred to appropriate working group chairs and area directors, where they may consider sending a liaison statement to the appropriate study group.
|
| 143 |
+
|
| 144 |
+
#### **2.1.3 How the ITU-T is informed about proposed new IETF work items**
|
| 145 |
+
|
| 146 |
+
The IETF maintains a mailing list for the distribution of proposed new work items among standards development organizations. Many such items can be identified in proposed birds-of-a-feather (BoF) sessions, as well as draft charters for working groups. The IETF forwards all such draft charters for all new and revised working groups and BoF session announcements to the IETF new-work mailing list. An ITU-T mailing list is subscribed to this list. Leadership of study groups may subscribe to this ITU-T mailing list, which is maintained by the Telecommunication Standardization Bureau (TSB). Members of the SG-specific listname may include the SG chairman, SG vice-chairmen, working party chairmen, concerned rapporteurs, other experts designated by the SG and the SG Counsellor. This will enable the SGs to monitor the new work items for possible overlap or interest to their study group. It is expected that this mailing list will see a few messages per month.
|
| 147 |
+
|
| 148 |
+
Each SG chairman, or designated representative, may provide comments on these charters by responding to the IESG mailing list at [iesg@ietf.org](mailto:iesg@ietf.org) clearly indicating their ITU-T position and the nature of their concern. Plain-text email is preferred on the IESG mailing list.
|
| 149 |
+
|
| 150 |
+
It should be noted that the IETF turnaround time for new working group charters can be as short as two weeks. As a result, the mailing list should be consistently monitored.
|
| 151 |
+
|
| 152 |
+
#### **2.1.4 How the IETF is informed about ITU-T work items**
|
| 153 |
+
|
| 154 |
+
The ITU-T accepts new areas of work through the creation or update of Questions and these can be found on the ITU-T study group web pages. In addition, the ITU-T work programme is documented on each ITU-T study group's web page on the ITU-T web site.
|
| 155 |
+
|
| 156 |
+
Study groups send updates to the IETF new-work mailing list as new Questions are first drafted or created, terms of reference for Questions are first drafted or updated, or otherwise when there is reason to believe that a particular effort might be of interest to the IETF. Area directors or WG chairs should provide comments through liaison statements or direct email to the relevant SG chairman in cases of possible overlap or interest.
|
| 157 |
+
|
| 158 |
+
### **2.2 Representation**
|
| 159 |
+
|
| 160 |
+
ISOC, including its standards body IETF, is a Sector Member of the ITU-T. As a result, ISOC delegates are afforded the same rights as other ITU-T Sector Members (see clause 2.2.1). Conversely, ITU-T delegates may participate in the work of the IETF as representatives of the ITU-T (see clause 2.2.2). To promote collaboration, it is useful to facilitate communication between the organizations as further described below.
|
| 161 |
+
|
| 162 |
+
#### **2.2.1 IETF recognition at ITU-T**
|
| 163 |
+
|
| 164 |
+
Experts and representatives from the IETF that are chosen by IETF leadership normally participate in ITU-T meetings as ISOC delegates. The ISOC focal point will facilitate registration and verification of these people, as appropriate.
|
| 165 |
+
|
| 166 |
+
#### **2.2.2 ITU-T recognition at ISOC/IETF**
|
| 167 |
+
|
| 168 |
+
ITU-T study group chairmen can authorize one or more members to attend an IETF meeting as an official ITU-T delegate speaking authoritatively on behalf of the activities of the study group (or a particular rapporteur group). The study group chairman sends the ITU-T list of delegates by email to the working group chair, with a copy to the area directors, and also to the study group. According to IETF process, opinions expressed by any such delegate are given equal weight with opinions expressed by any other working group participant.
|
| 169 |
+
|
| 170 |
+
### **2.3 Communication outside of meetings**
|
| 171 |
+
|
| 172 |
+
Informal communication between contact points and experts of both organizations is encouraged. However, formal communication from an ITU-T study group, working party or rapporteur group to an associated IETF contact point must be explicitly approved and identified as coming from the study group, working party, or rapporteur group, respectively. Formal liaison statements from the ITU-T to the IETF are transmitted according to the procedures described in RFC 4053 [2]. These liaison statements are placed by the IETF onto a liaison statements web page at <https://datatracker.ietf.org/liaison/>. An individual at the IETF is assigned responsibility for dealing with each liaison statement that is received. The name and contact information of the responsible person and any applicable deadline is listed with the links to the liaison statement on this web page.
|
| 173 |
+
|
| 174 |
+
Formal liaison statements from the Internet Architecture Board (IAB), the IESG, the IETF, an IETF working group or area to the ITU-T are generated, approved, and transmitted according to the procedures described in RFC 4053 [2] and Recommendation ITU-T A.1 [15]. Formal communication is intended to allow the sharing of positions between the IETF and the ITU-T outside of actual documents (as described in clause 2.5.1). This covers such things as comments on documents and requests for input.
|
| 175 |
+
|
| 176 |
+
### **2.4 Mailing lists**
|
| 177 |
+
|
| 178 |
+
All IETF working groups and all ITU-T study group Questions have associated mailing lists.
|
| 179 |
+
|
| 180 |
+
In the IETF, the mailing list is the primary vehicle for discussion and decision-making. It is recommended that the ITU-T experts interested in particular IETF working group topics subscribe to and participate in these lists. IETF WG mailing lists are open to all subscribers. The IETF working group mailing list subscription and archive information are noted in each working group's charter. In the ITU-T, the TSB has set up formal mailing lists for Questions, working parties, and other topics within study groups (more detail can be found on the ITU-T web site). These mailing lists are typically used for ITU-T correspondence, including technical discussion, meeting logistics, reports, etc.
|
| 181 |
+
|
| 182 |
+
NOTE – Individual subscribers to this list must be affiliated with an ITU-T member or associate (at this time, there is no blanket inclusion of all IETF participants as members, however, as a member, the ISOC focal point can facilitate access by IETF technical experts, liaison representatives, or liaison managers).
|
| 183 |
+
|
| 184 |
+
IETF participants may subscribe to ITU-T focus group email lists if they are individuals from a country that is a member of ITU-T.
|
| 185 |
+
|
| 186 |
+
### **2.5 Document sharing**
|
| 187 |
+
|
| 188 |
+
During the course of ITU-T and IETF collaboration, it is important to share working drafts and documents among the technical working groups. Initially proposed concepts and specifications typically can be circulated by email (often just repeating the concept and not including the details of the specification) on both the IETF and ITU-T mailing lists. In addition, working texts (or URLs) of draft Recommendations, Internet-Drafts, or RFCs may also be sent between the organizations as described below.
|
| 189 |
+
|
| 190 |
+
Internet-Drafts are available on the IETF web site. The ITU-T can make selected ITU-T documents at any stage of development available to the IETF by attaching them to a formal liaison statement. Although a communication can point to a URL where a non-ASCII document (e.g., Word) can be downloaded, attachments in proprietary formats to an IETF mailing list are discouraged. It should also be recognized that the official versions of all IETF documents are in ASCII.
|
| 191 |
+
|
| 192 |
+
#### **2.5.1 Contributions and liaison statements from the IETF to ITU-T**
|
| 193 |
+
|
| 194 |
+
IETF documents (e.g., Internet-Drafts) or URLs of those documents are most commonly transmitted to ITU-T study groups as liaison statements (see RFC 4053 [2]), but exceptionally can be submitted to a study group as a contribution from ISOC in accordance with Recommendation ITU-T A.2 [16]. In order to ensure that the IETF has properly authorized this, the IETF working group must agree that the specific drafts are of mutual interest; that there is a benefit in forwarding them to the ITU-T for review, comment and potential use; and that the document status is accurately represented in the cover letter. Once agreed, the appropriate area directors review the working group request and give approval. The rules of the IETF Trust are followed in these circumstances [3]. The contributions are then forwarded (with the noted approval) to the TSB for circulation as a contribution to the appropriate ITU-T study group. Material submitted to the ITU-T as an ISOC contribution is governed by clause 3.1.5 of Recommendation ITU-T A.1 [15]. Any such contribution will be made only after receiving necessary approval of owners of the work in question. In other circumstances, a liaison statement may be appropriate. See RFC 5378 [3] and Recommendation ITU-T A.1 [15] for more information.
|
| 195 |
+
|
| 196 |
+
#### **2.5.2 Contributions and liaison statements from the ITU-T to IETF**
|
| 197 |
+
|
| 198 |
+
An ITU-T study group or working party may send texts of draft new or revised Recommendations, clearly indicating their status, to the IETF as contributions in the form of liaison statements or Internet-Drafts. Internet-Drafts are IETF temporary documents that expire six months after being published. The study group or working party must decide that there is a benefit in forwarding them
|
| 199 |
+
|
| 200 |
+
to the IETF for review, comment, and potential use. Terms of reference for rapporteur group meetings may authorize rapporteur groups to send working documents, in the form of Internet-Drafts, to the IETF.
|
| 201 |
+
|
| 202 |
+
If the study group or working party elects to transmit the text as an Internet-Draft, the document editor would be instructed to prepare the contribution in Internet-Draft format (in ASCII and optionally postscript format as per RFC 2223 [8]) and upload it via <https://datatracker.ietf.org/idst/upload.cgi>. Material submitted as an Internet-Draft or intended for inclusion in an Internet-Draft or RFC is governed by the rules set forth in RFCs 5378 [3], 3979 [4], and 4879 [5]. Alternatively, the study group, working party, or rapporteur group could attach the text to a formal liaison statement.
|
| 203 |
+
|
| 204 |
+
Both the rapporteur and the document editor should be identified as contacts in the contribution. The document should also clearly indicate the state of development in a particular ITU-T study group.
|
| 205 |
+
|
| 206 |
+
NOTE – Liaison statements and their attachments sent to the IETF are made publicly available on the IETF web site.
|
| 207 |
+
|
| 208 |
+
#### **2.5.3 ITU-T and IETF**
|
| 209 |
+
|
| 210 |
+
It is envisaged that the processes of clauses 2.5.1 and 2.5.2 will often be used simultaneously by both an IETF working group and an ITU-T study group to collaborate on a topic of mutual interest.
|
| 211 |
+
|
| 212 |
+
It is also envisaged that the outcome of the collaboration will be the documentation in full by one body and its referencing by the other (see clause 2.6 for details). That is, common or joint text is discouraged because of the current differences in procedures for document approval and revision. Where complementary work is being undertaken in both organizations that will result in Recommendations or RFCs, due allowance should be given to the differing perspectives, working methods, and procedures of the two organizations. That is, each organization should understand the other organization's procedures and strive to respect them in the collaboration.
|
| 213 |
+
|
| 214 |
+
### **2.6 Simple cross referencing**
|
| 215 |
+
|
| 216 |
+
Recommendation ITU-T A.5 [6] describes the process for including references to documents of other organizations in ITU-T Recommendations. Recommendation ITU-T A.5 also addresses the situation where a study group or working party decides to incorporate the text of another organization into the text of a Recommendation, rather than referencing it. Information specific to referencing IETF RFCs is found at <http://itu.int/ITU-T/go/ref-ietf-isoc>.
|
| 217 |
+
|
| 218 |
+
Section 6.1.1 of RFC 2026 [7] describes the process for referencing other open standards (like ITU-T Recommendations) in IETF RFCs.
|
| 219 |
+
|
| 220 |
+
### **2.7 Preliminary work efforts**
|
| 221 |
+
|
| 222 |
+
Both ITU-T and IETF provide mechanisms for early discussion of potential new work areas prior to the official start of work in an ITU-T study group or creation of an IETF working group.
|
| 223 |
+
|
| 224 |
+
Objectives, methods, and procedures for the creation and operation of ITU-T focus groups are defined in Recommendation ITU-T A.7 [17]. Focus groups are frequently created in new work areas where there is a need for deliverables to be produced on a specific topic within a short timeframe. IETF participants who are not members or associates of ITU-T may participate fully in the work of ITU-T focus groups if they are from a country that is a member of ITU-T.
|
| 225 |
+
|
| 226 |
+
In the IETF, guidance for BoF sessions is provided in RFC 5434 [13]. Efforts that have not yet reached the working group stage may be discussed in BOF sessions. These sessions typically gauge interest in pursuing creation of working groups. In some cases, these discussions continue on mailing lists.
|
| 227 |
+
|
| 228 |
+
### 2.8 Additional items
|
| 229 |
+
|
| 230 |
+
#### 2.8.1 IETF information that may be useful to ITU-T participants
|
| 231 |
+
|
| 232 |
+
Information on IETF procedures may be found in the documents in the informative references, and URLs below.
|
| 233 |
+
|
| 234 |
+
NOTE – RFCs do not change after they are published. Rather, they are either obsoleted or updated by other RFCs. Such updates are tracked in the rfc-index.txt file.
|
| 235 |
+
|
| 236 |
+
Current list and status of all IETF RFCs:
|
| 237 |
+
|
| 238 |
+
<ftp://ftp.ietf.org/rfc/rfc-index.txt>
|
| 239 |
+
|
| 240 |
+
Current list and description of all IETF Internet-Drafts:
|
| 241 |
+
|
| 242 |
+
<ftp://ftp.ietf.org/internet-drafts/lid-abstracts.txt>
|
| 243 |
+
|
| 244 |
+
Current list of IETF working groups and their Charters: (includes area directors and chair contacts, mailing list information, etc.)
|
| 245 |
+
|
| 246 |
+
<http://www.ietf.org/dyn/wg/charter.html>
|
| 247 |
+
|
| 248 |
+
Current list of registered BOFs:
|
| 249 |
+
|
| 250 |
+
<http://trac.tools.ietf.org/bof/trac/>
|
| 251 |
+
|
| 252 |
+
RFC Editor pages about publishing RFCs, including available tools and lots of guidance:
|
| 253 |
+
|
| 254 |
+
<http://www.rfc-editor.org/pubprocess.html>
|
| 255 |
+
|
| 256 |
+
Current list of liaison statements:
|
| 257 |
+
|
| 258 |
+
<https://datatracker.ietf.org/liaison/>
|
| 259 |
+
|
| 260 |
+
IETF Intellectual Property Rights Policy and Notices:
|
| 261 |
+
|
| 262 |
+
<http://www.ietf.org/ipr/>
|
| 263 |
+
|
| 264 |
+
*The Tao of the IETF – A Novice's Guide to the Internet Engineering Task Force:*
|
| 265 |
+
|
| 266 |
+
<http://www.ietf.org/tao.html>
|
| 267 |
+
|
| 268 |
+
#### 2.8.2 ITU-T information that may be useful to IETF participants
|
| 269 |
+
|
| 270 |
+
Information about the ITU-T can be found in the informative references and at the URLs below.
|
| 271 |
+
|
| 272 |
+
ITU-T Main page:
|
| 273 |
+
|
| 274 |
+
<http://itu.int/ITU-T>
|
| 275 |
+
|
| 276 |
+
List of all ITU-T Recommendations:
|
| 277 |
+
|
| 278 |
+
<http://itu.int/itu-t/recommendations/>
|
| 279 |
+
|
| 280 |
+
ITU-T study group main page for Study Group NN (where NN is the 2-digit SG number):
|
| 281 |
+
|
| 282 |
+
<http://itu.int/ITU-T/studygroups/comNN/>
|
| 283 |
+
|
| 284 |
+
Intellectual Property policies, forms and databases:
|
| 285 |
+
|
| 286 |
+
<http://itu.int/en/ITU-T/ipr/Pages/default.aspx>
|
| 287 |
+
|
| 288 |
+
Current list of active ITU-T focus Groups
|
| 289 |
+
|
| 290 |
+
<http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx>
|
| 291 |
+
|
| 292 |
+
ITU-T Procedures including:
|
| 293 |
+
|
| 294 |
+
- WTSA Resolution 1, *Rules of procedure of the ITU Telecommunication Standardization Sector (ITU-T)*
|
| 295 |
+
- WTSA Resolution 2, *Study Group responsibility and mandates*
|
| 296 |
+
<http://itu.int/publ/T-RES/en>
|
| 297 |
+
|
| 298 |
+
*Author's Guide for drafting ITU-T Recommendations:*
|
| 299 |
+
|
| 300 |
+
<http://itu.int/ITU-T/go/author-guide>
|
| 301 |
+
|
| 302 |
+
Templates for contributions, ITU-T Recommendations, and liaison statements:
|
| 303 |
+
|
| 304 |
+
<http://itu.int/ITU-T/studygroups/templates/index.html>
|
| 305 |
+
|
| 306 |
+
# 3 References
|
| 307 |
+
|
| 308 |
+
### 3.1 Normative references
|
| 309 |
+
|
| 310 |
+
- [1] Daigle, L., Ed., and Internet Architecture Board, *IAB Processes for Management of IETF Liaison Relationships*, BCP 102, RFC 4052, April 2005.
|
| 311 |
+
- [2] Trowbridge, S., Bradner, S., and F. Baker, *Procedures for Handling Liaison Statements to and from the IETF*, BCP 103, RFC 4053, April 2005.
|
| 312 |
+
- [3] Bradner, S., Ed., and J. Contreras, Ed., *Rights Contributors Provide to the IETF Trust*, BCP 78, RFC 5378, November, 2008.
|
| 313 |
+
- [4] Bradner, S., Ed., *Intellectual Property Rights in IETF Technology*, BCP 79, RFC 3979, March 2005.
|
| 314 |
+
- [5] Narten, T., *Clarification of the Third Party Disclosure Procedure in RFC 3979*, BCP 79, RFC 4879, April 2007.
|
| 315 |
+
- [6] Recommendation ITU-T A.5 (2008), *Generic procedures for including references to documents of other organizations in ITU-T Recommendations*, International Telecommunication Union.
|
| 316 |
+
|
| 317 |
+
## 3.2 Informative references
|
| 318 |
+
|
| 319 |
+
- [7] Bradner, S., *The Internet Standards Process – Revision 3*, BCP 9, RFC 2026, October 1996.
|
| 320 |
+
- [8] Postel, J. and J. Reynolds, *Instructions to RFC Authors*, RFC 2223, October 1997.
|
| 321 |
+
- [9] Brett, R., Bradner, S., and G. Parsons, *Collaboration between ISOC/IETF and ITU-T*, RFC 2436, October 1998.
|
| 322 |
+
- [10] Fishman, G. and S. Bradner, *Internet Engineering Task Force and International Telecommunication Union – Telecommunications Standardization Sector Collaboration Guidelines*, RFC 3356, August 2002.
|
| 323 |
+
- [11] Hovey, R. and S. Bradner, S., *The Organizations Involved in the IETF Standards Process*, BCP 11, RFC 2028, October, 1996.
|
| 324 |
+
- [12] Bradner, S., *IETF Working Group Guidelines and Procedures*, BCP 25, RFC 2418, September 1998.
|
| 325 |
+
- [13] Narten, T., *Considerations for Having a Successful Birds-of-a-Feather (BOF) Session*, RFC 5434, February 2009.
|
| 326 |
+
- [14] Alvestrand, H., *A Mission Statement for the IETF*, BCP 95, RFC 3935, October 2004.
|
| 327 |
+
- [15] Recommendation ITU-T A.1 (2008), *Work methods for study groups of the ITU Telecommunication Standardization Sector (ITU-T)*, International Telecommunication Union.
|
| 328 |
+
- [16] Recommendation ITU-T A.2 (2008), *Presentation of contributions to the ITU-T*, International Telecommunication Union.
|
| 329 |
+
- [17] Recommendation ITU-T A.7 (2008), *Focus groups: Working methods and procedures*, International Telecommunication Union.
|
| 330 |
+
- [18] Recommendation ITU-T A.8 (2008), *Alternative approval process for new and revised ITU-T Recommendations*, International Telecommunication Union.
|
| 331 |
+
|
| 332 |
+
|
| 333 |
+
|
| 334 |
+
|
| 335 |
+
|
| 336 |
+
# **SERIES OF ITU-T RECOMMENDATIONS**
|
| 337 |
+
|
| 338 |
+
| | |
|
| 339 |
+
|-----------------|---------------------------------------------------------------------------------------------|
|
| 340 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 341 |
+
| Series D | General tariff principles |
|
| 342 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 343 |
+
| Series F | Non-telephone telecommunication services |
|
| 344 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 345 |
+
| Series H | Audiovisual and multimedia systems |
|
| 346 |
+
| Series I | Integrated services digital network |
|
| 347 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 348 |
+
| Series K | Protection against interference |
|
| 349 |
+
| Series L | Construction, installation and protection of cables and other elements of outside plant |
|
| 350 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 351 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 352 |
+
| Series O | Specifications of measuring equipment |
|
| 353 |
+
| Series P | Terminals and subjective and objective assessment methods |
|
| 354 |
+
| Series Q | Switching and signalling |
|
| 355 |
+
| Series R | Telegraph transmission |
|
| 356 |
+
| Series S | Telegraph services terminal equipment |
|
| 357 |
+
| Series T | Terminals for telematic services |
|
| 358 |
+
| Series U | Telegraph switching |
|
| 359 |
+
| Series V | Data communication over the telephone network |
|
| 360 |
+
| Series X | Data networks, open system communications and security |
|
| 361 |
+
| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
|
| 362 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.Sup4-202601-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.Sup4-202601-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,293 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Supplement **ITU-T A Suppl. 4 (01/2026)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
Supplements to the Series A Recommendations
|
| 7 |
+
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
# **Guidelines for remote participation**
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
|
| 14 |
+
## Supplement 4 to ITU-T A-series Recommendations
|
| 15 |
+
|
| 16 |
+
# Guidelines for remote participation
|
| 17 |
+
|
| 18 |
+
## Summary
|
| 19 |
+
|
| 20 |
+
Supplement 4 to the A series of ITU-T Recommendations specifies guidelines on the organization and handling of meetings of ITU-T groups with remote participation.
|
| 21 |
+
|
| 22 |
+
## History\*
|
| 23 |
+
|
| 24 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 25 |
+
|---------|------------------|------------|-------------|--------------------|
|
| 26 |
+
| 1.0 | ITU-T A Suppl. 4 | 2015-06-05 | 0 | 11.1002/1000/12580 |
|
| 27 |
+
| 2.0 | ITU-T A Suppl. 4 | 2022-12-16 | 0 | 11.1002/1000/15253 |
|
| 28 |
+
| 3.0 | ITU-T A Suppl. 4 | 2026-01-30 | 0 | 11.1002/1000/16733 |
|
| 29 |
+
|
| 30 |
+
## Keywords
|
| 31 |
+
|
| 32 |
+
e-meeting, fully virtual meeting, remote participation.
|
| 33 |
+
|
| 34 |
+
---
|
| 35 |
+
|
| 36 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 37 |
+
|
| 38 |
+
## FOREWORD
|
| 39 |
+
|
| 40 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 41 |
+
|
| 42 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 43 |
+
|
| 44 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 45 |
+
|
| 46 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 47 |
+
|
| 48 |
+
## NOTE
|
| 49 |
+
|
| 50 |
+
This is an informative ITU-T publication. Mandatory provisions, such as those found in ITU-T Recommendations, are outside the scope of this publication. This publication should only be referenced bibliographically in ITU-T Recommendations.
|
| 51 |
+
|
| 52 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 53 |
+
|
| 54 |
+
ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the standards development process.
|
| 55 |
+
|
| 56 |
+
As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this publication. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <https://www.itu.int/ITU-T/ipr/>.
|
| 57 |
+
|
| 58 |
+
© ITU 2026
|
| 59 |
+
|
| 60 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 61 |
+
|
| 62 |
+
## Table of Contents
|
| 63 |
+
|
| 64 |
+
| | | Page |
|
| 65 |
+
|----|----------------------------------------------------------------------------------------|------|
|
| 66 |
+
| 1 | Scope..... | 1 |
|
| 67 |
+
| 2 | References..... | 1 |
|
| 68 |
+
| 3 | Definitions ..... | 2 |
|
| 69 |
+
| | 3.1 Terms defined elsewhere ..... | 2 |
|
| 70 |
+
| | 3.2 Terms defined in this Supplement ..... | 2 |
|
| 71 |
+
| 4 | Abbreviations and acronyms ..... | 2 |
|
| 72 |
+
| 5 | Conventions ..... | 2 |
|
| 73 |
+
| 6 | Organization of a meeting with remote participation ..... | 2 |
|
| 74 |
+
| 7 | Guidelines for the group chair ..... | 3 |
|
| 75 |
+
| 8 | Technical guidelines for remote participants..... | 4 |
|
| 76 |
+
| 9 | Technical guidelines for in-person participants..... | 5 |
|
| 77 |
+
| 10 | Practical measures for persons with disabilities and persons with specific needs ..... | 5 |
|
| 78 |
+
|
| 79 |
+
|
| 80 |
+
|
| 81 |
+
# Supplement 4 to ITU-T A-series Recommendations
|
| 82 |
+
|
| 83 |
+
## Guidelines for remote participation
|
| 84 |
+
|
| 85 |
+
## 1 Scope
|
| 86 |
+
|
| 87 |
+
Well-documented rules and procedures, including the legal aspects, are useful for electronic meetings of ITU-T groups. ITU-T groups include, but are not limited to, Telecommunication Standardization Advisory Group (TSAG), study groups, working parties, Questions or Rapporteur groups, focus groups, Joint Coordination Activities (JCAs), correspondence groups, ad hoc groups and regional groups.
|
| 88 |
+
|
| 89 |
+
NOTE 1 – The rights of remote participants are not covered in this Supplement.
|
| 90 |
+
|
| 91 |
+
Meetings of ITU-T groups may be conducted in the following formats:
|
| 92 |
+
|
| 93 |
+
- physical meetings (face-to-face);
|
| 94 |
+
- physical meetings with remote observation (i.e., webcast);
|
| 95 |
+
- physical meetings with remote participation;
|
| 96 |
+
- fully virtual meetings, also called e-meetings.
|
| 97 |
+
|
| 98 |
+
NOTE 2 – The first two formats are not covered by this Supplement.
|
| 99 |
+
|
| 100 |
+
NOTE 3 – This Supplement is intended to be aligned with the "Guidelines on the management of fully virtual meetings and physical meetings with remote participation" [Council-2025] established by the 2025 session of the ITU Council.
|
| 101 |
+
|
| 102 |
+
The same format may not apply to all sessions of a given meeting. This Supplement provides guidelines for physical meetings with remote participation and fully virtual meetings. The meeting format (see clause 6.4) to be used for any given meeting or meeting session is beyond the scope of this Supplement.
|
| 103 |
+
|
| 104 |
+
## 2 References
|
| 105 |
+
|
| 106 |
+
- | | |
|
| 107 |
+
|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 108 |
+
| [Council-2025] | ITU Council, Guidelines on the management of fully virtual meetings and physical meetings with remote participation.<br>< <a href="https://www.itu.int/en/general-secretariat/ICT-Services/remoteparticipation">https://www.itu.int/en/general-secretariat/ICT-Services/remoteparticipation</a> > |
|
| 109 |
+
| [FSTP-ACC-RCS] | Overview of remote captioning services (2019).<br>< <a href="https://www.itu.int/pub/T-TUT-FSTP-2019-ACC-RCS">https://www.itu.int/pub/T-TUT-FSTP-2019-ACC-RCS</a> > |
|
| 110 |
+
| [FSTP-ACC-RemPart] | Guidelines for supporting remote participation in meetings for all (2015).<br>< <a href="https://www.itu.int/pub/T-TUT-FSTP-2015-ACC">https://www.itu.int/pub/T-TUT-FSTP-2015-ACC</a> > |
|
| 111 |
+
| [FSTP-AM] | Guidelines for accessible meetings (2015).<br>< <a href="https://www.itu.int/pub/T-TUT-FSTP-2015-AM">https://www.itu.int/pub/T-TUT-FSTP-2015-AM</a> > |
|
| 112 |
+
| [PP GR] | Plenipotentiary Conference, General Rules of conferences, assemblies and meetings of the Union (Rev. Guadalajara, 2010).<br>< <a href="https://www.itu.int/pub/S-CONF-PLEN-2019">https://www.itu.int/pub/S-CONF-PLEN-2019</a> > |
|
| 113 |
+
| [PP Res.167] | Plenipotentiary Conference, Resolution 167 (Rev. Bucharest, 2022), Strengthening and developing ITU capabilities for fully virtual meetings and physical meetings with remote participation, and the electronic means to advance the work of the Union.<br>< <a href="https://www.itu.int/pub/S-CONF-ACTF-2022">https://www.itu.int/pub/S-CONF-ACTF-2022</a> > |
|
| 114 |
+
|
| 115 |
+
## 3 Definitions
|
| 116 |
+
|
| 117 |
+
### 3.1 Terms defined elsewhere
|
| 118 |
+
|
| 119 |
+
None.
|
| 120 |
+
|
| 121 |
+
### 3.2 Terms defined in this Supplement
|
| 122 |
+
|
| 123 |
+
This Supplement defines the following terms:
|
| 124 |
+
|
| 125 |
+
**3.2.1 group:** A study group, Telecommunication Standardization Advisory Group (TSAG), a working party, a Question, a Rapporteur group, a correspondence group, an ad hoc group, a joint coordination activity (JCA), a focus group, a regional group or any other type of group created in ITU-T.
|
| 126 |
+
|
| 127 |
+
NOTE – A workshop or a seminar is not considered a group in the context of this Supplement.
|
| 128 |
+
|
| 129 |
+
**3.2.2 remote participation:** Participation in a meeting from a separate geographical location, using communication technologies.
|
| 130 |
+
|
| 131 |
+
**3.2.3 remote participation moderator:** A person in charge of monitoring the remote participation tool, ensuring that remote participants know what is taking place in the meeting and allowing remote participants chances to contribute (if the meeting is with remote participation).
|
| 132 |
+
|
| 133 |
+
NOTE – A remote participation moderator is not systematically available for each meeting with remote participation.
|
| 134 |
+
|
| 135 |
+
## 4 Abbreviations and acronyms
|
| 136 |
+
|
| 137 |
+
This Supplement uses the following abbreviations and acronyms:
|
| 138 |
+
|
| 139 |
+
JCA Joint Coordination Activity
|
| 140 |
+
|
| 141 |
+
TSAG Telecommunication Standardization Advisory Group
|
| 142 |
+
|
| 143 |
+
UTC Coordinated Universal Time
|
| 144 |
+
|
| 145 |
+
## 5 Conventions
|
| 146 |
+
|
| 147 |
+
None.
|
| 148 |
+
|
| 149 |
+
## 6 Organization of a meeting with remote participation
|
| 150 |
+
|
| 151 |
+
This clause gives guidelines for the group chair and secretariat who are organizing a meeting with remote participation, whether physical or fully virtual.
|
| 152 |
+
|
| 153 |
+
**6.1** When scheduling the time for meetings with remote participation or for fully virtual meetings, consideration should be given to the different time zones of the expected remote participants. Times for the scheduling of meetings are stated in the invitations to such meetings as both Coordinated Universal Time (UTC) and Geneva times. Consideration should also be given to, when practical, scheduling relevant agenda items identified by a remote participant to better accommodate the remote participant's time zone.
|
| 154 |
+
|
| 155 |
+
**6.1.1** In the case of a physical meeting with remote participation, it should be scheduled during the normal working hours of the location where the physical meeting is being held.
|
| 156 |
+
|
| 157 |
+
**6.1.2** In the case of a fully virtual meeting, it is recommended to organize it between 1100 and 1500 hours, Geneva time, and to avoid Fridays whenever possible. If the meeting extends over two weeks, there should be no sessions on Saturdays or Sundays. A fully virtual meeting should normally limit itself to sessions of 1 hour and 15 minutes, interspersed with breaks of a minimum of 10 minutes.
|
| 158 |
+
|
| 159 |
+
**6.1.3** The times of opening and closing of sessions during a meeting should normally be adhered to. Amendments to the timings of meetings and of sessions within meetings are notified to all participants as soon as practically possible after the decision to change the timings has been taken.
|
| 160 |
+
|
| 161 |
+
**6.2** If remote participation is to be arranged for a meeting, TSB should be informed at least twelve calendar days before the meeting, to allow for enough time for logistics arrangements.
|
| 162 |
+
|
| 163 |
+
**6.3** The following are considerations to be followed for meeting chairs.
|
| 164 |
+
|
| 165 |
+
- a) In the case of a fully virtual meeting, the group should identify an acting chair, normally amongst the group vice-chairs, to ensure meeting continuity should the communication with the chair fail.
|
| 166 |
+
- b) In the case of a physical meeting with remote participation, the group chair should be physically present. It would be advisable that vice-chairs also be physically present as a vice-chair may be called to stand in for the chair in case of unavailability of the latter.
|
| 167 |
+
|
| 168 |
+
NOTE – It would additionally be advisable that the relevant working party chairs and rapporteurs be physically present at study group meetings.
|
| 169 |
+
|
| 170 |
+
**6.4** The collective letter, or calling notice, indicates the format in which the meeting will be conducted:
|
| 171 |
+
|
| 172 |
+
- physical (face-to-face);
|
| 173 |
+
- physical with remote observation (i.e., webcast);
|
| 174 |
+
- physical with remote participation (see also clause 7.1): the notification indicates whether, and for which sessions, remote participation can be requested; plenary sessions should support remote participation; it also indicates that the decision-making is with those physically present in the room [PP Res.167];
|
| 175 |
+
- fully virtual meeting, also called virtual meeting (see also clause 7.1): the notification indicates that decision making is by consensus.
|
| 176 |
+
|
| 177 |
+
NOTE – The first two formats are not covered by this Supplement. The meeting format could be based on a variety of criteria, including, but not limited to, the nature of the meeting, whether the meeting is held inside or outside Geneva, and technical capabilities available for the meeting.
|
| 178 |
+
|
| 179 |
+
**6.5** It is recommended that the technologies used for remote participation are those available from the ITU, even for meetings held outside Geneva. Access to remote participation should be available thirty minutes prior to the start of a meeting to allow remote participants to ensure that they can connect.
|
| 180 |
+
|
| 181 |
+
NOTE – It is not a requirement to have ITU staff present in a support capacity during the meeting.
|
| 182 |
+
|
| 183 |
+
**6.6** For meetings held outside Geneva with remote participation, it is recommended that hosts be supplied with guidelines in order to minimize possible technical issues related to remote participation. These guidelines (e.g., in the form of a checklist) should be accessible for the host well in advance before the event and should include all the technical and logistics requirements for providing the remote participation facility.
|
| 184 |
+
|
| 185 |
+
## **7 Guidelines for the group chair**
|
| 186 |
+
|
| 187 |
+
This clause gives guidelines for the group chair to help chairing a meeting with remote participation.
|
| 188 |
+
|
| 189 |
+
**7.1** All remote participants should mute themselves when utilizing a tool to participate remotely. Remote participants only unmute when the chair recognizes them. To prevent interference of background noise, the chair reminds remote participants to mute their microphones until when they wish to contribute (see also clause 7.5).
|
| 190 |
+
|
| 191 |
+
**7.2** In the case of physical meetings with remote participation, the group chair and the remote participation moderator (when available) are encouraged to meet in the room ten minutes before the
|
| 192 |
+
|
| 193 |
+
scheduled start of the meeting to verify that the system is working and that the group chair can display and share documents.
|
| 194 |
+
|
| 195 |
+
NOTE – The remote participation moderator informs the meeting that a remote participant wishes to intervene and the chair includes the remote participant in the queue of meeting participants who want to intervene.
|
| 196 |
+
|
| 197 |
+
**7.3** At the beginning of each meeting with remote participation, the group chair announces that there is a remote facility and states the rules governing remote participation in physical meetings. The group chair also states the following: "When taking the floor, participants shall announce their name and affiliation. They shall be brief and clear in their interventions by speaking slowly so that those for whom English<sup>1</sup> is not their native language can understand. Remote participants shall mute their microphone when they are not speaking".
|
| 198 |
+
|
| 199 |
+
**7.4** The General Rules of conferences, assemblies and meetings of the Union [PP GR] apply to meetings with remote participation, in particular clauses 20.2 (Order of debates), 20.8 (Limitation of speeches) and 20.9 (Closing the list of speakers).
|
| 200 |
+
|
| 201 |
+
**7.5** Where supported by the remote participation tool, the chair or the remote participation moderator is permitted to mute remote participants with bad connections or whose connections introduce too much noise, or may ask them to leave the meeting if the situation cannot be remedied.
|
| 202 |
+
|
| 203 |
+
**7.6** While a remote participation tool may support video, it is recommended that the group chair does not use the share video option and turns off the camera to avoid creating bandwidth problems.
|
| 204 |
+
|
| 205 |
+
## **8 Technical guidelines for remote participants**
|
| 206 |
+
|
| 207 |
+
This clause gives guidelines for remote participants.
|
| 208 |
+
|
| 209 |
+
**8.1** Remote participants are encouraged to use the remote facility through a landline (when available), or to use a headset (and not the microphone and speaker of their machine). Remote participants should make sure that the loudspeaker on their machine is muted when they call from a landline.
|
| 210 |
+
|
| 211 |
+
**8.2** It is recommended that remote participants connect at least five minutes before the start of the meeting to avoid disturbance. This will also allow for the group chair and/or the remote participation moderator to verify sound levels.
|
| 212 |
+
|
| 213 |
+
**8.3** Remote participants are encouraged to announce their name and affiliation clearly before making any intervention (see also clause 7.3).
|
| 214 |
+
|
| 215 |
+
NOTE – This is particularly useful in case of a meeting with interpretation or with participants with disabilities or specific needs (see clause 10).
|
| 216 |
+
|
| 217 |
+
**8.4** Remote participants should speak from a quiet place without background noise. They should speak slowly and clearly to allow the other participants to compensate for any audio problem. They are encouraged to end their remarks with the phrase "This concludes my intervention".
|
| 218 |
+
|
| 219 |
+
NOTE – Clauses 8.3 and 8.4 are particularly useful in the case of a meeting with interpretation, or with participants with disabilities or specific needs (see clause 10).
|
| 220 |
+
|
| 221 |
+
**8.5** Any comments entered in the chat of the remote participation tool do not form part of the official meeting records. Remote participants recognize that, for various reasons, the chair and secretariat may be unable to read messages in the chat of a meeting. However, the chat may be used to provide certain inputs upon request of the chair (for example, a specific proposal made during the debates or a remote intervention when the connexion is poor). It may also be used to highlight technical problems or obtain help from the moderator (see also clause 8.8). It may not be used to ask for the floor.
|
| 222 |
+
|
| 223 |
+
---
|
| 224 |
+
|
| 225 |
+
<sup>1</sup> In case the working language of the meeting is not English, this statement is adapted accordingly.
|
| 226 |
+
|
| 227 |
+
**8.6** During a physical meeting with remote participation, remote participants accept that, in case of technical problems (e.g., lost connection), their participation may be interrupted (see also clause 8.8) while the physical meeting will continue, whereas in case of onsite technical issues (e.g., headphone failure), the chair may decide to suspend the meeting until the problem is solved.
|
| 228 |
+
|
| 229 |
+
NOTE – Remote participants recognize that an important part of any meeting are the informal discussions during coffee and lunch breaks where delegates can informally explain, understand, and forge the compromises needed for the consensus processes to work. Remote participants recognize that they will not have this type of interaction with the other participants.
|
| 230 |
+
|
| 231 |
+
**8.7** During a fully virtual meeting, remote participants accept that in case of technical problems (e.g., lost connection), the chair will assess whether enough participants are still connected and will decide whether to continue the meeting (see also clause 8.8) or to suspend the meeting until the problem is solved.
|
| 232 |
+
|
| 233 |
+
**8.8** Remote participants may report problems to the remote participation moderator (when available) who should determine where the cause lies and should either take direct remedial action or offer advice as appropriate. A remote participant who experiences problems in joining the meeting should preferably discuss with the remote participation moderator in a private chat so that the main chat is reserved for discussions of interest to all participants.
|
| 234 |
+
|
| 235 |
+
**8.9** While a remote participation tool may support video, it is recommended that participants do not use the share video option and turn off their cameras to avoid creating bandwidth problems.
|
| 236 |
+
|
| 237 |
+
## **9 Technical guidelines for in-person participants**
|
| 238 |
+
|
| 239 |
+
This clause gives guidelines for participants physically present in a meeting with remote participation.
|
| 240 |
+
|
| 241 |
+
**9.1** In order to increase voice quality, only one microphone should be on (open) at a given time in the meeting room, and physically present participants are asked to speak close to (and in front of) the microphone.
|
| 242 |
+
|
| 243 |
+
## **10 Practical measures for persons with disabilities and persons with specific needs**
|
| 244 |
+
|
| 245 |
+
This clause presents practical measures to support equitable opportunities for participation.
|
| 246 |
+
|
| 247 |
+
**10.1** For meetings with remote participation (whether physical or fully virtual), captioning can be followed on the web-conference platform.
|
| 248 |
+
|
| 249 |
+
**10.2** Sign language may be made available upon request (subject to the availability of resources – see clause 10.3) in any ITU meeting and may be extended to the web conference platform.
|
| 250 |
+
|
| 251 |
+
**10.3** Persons with disabilities can flag on the registration form that they have specific needs and later inform TSB of the nature of their specific needs (for example, captioning, sign language or web-conference platform features). Provision of specific facilities is done in accordance with budgetary availability (see *resolves* 3 of [PP Res.167]).
|
| 252 |
+
|
| 253 |
+
**10.4** Web-conference platforms selected by ITU include accessibility features (e.g., screen reader support, adjustable colour and font size, keyboard) for persons with disabilities and persons with specific needs.
|
| 254 |
+
|
| 255 |
+
**10.5** At the beginning of a session, participants will be informed of the accessibility features available on the web-conference platform used for the meeting.
|
| 256 |
+
|
| 257 |
+
**10.6** Guidelines for users with hearing or visual impairments are available from the Joint Coordination Activity on Accessibility and Human Factors (JCA-AHF<sup>2</sup>).
|
| 258 |
+
|
| 259 |
+
---
|
| 260 |
+
|
| 261 |
+
<sup>2</sup> <https://itu.int/en/ITU-T/jca/ahf>
|
| 262 |
+
|
| 263 |
+
**10.7** Requirements and good practice for supporting remote participation in meetings for all are contained in [FSTP-ACC-RemPart]. Guidelines for accessible meetings are contained in [FSTP-AM]. An overview of remote captioning services is contained in [FSTP-ACC-RCS].
|
| 264 |
+
|
| 265 |
+
|
| 266 |
+
|
| 267 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 268 |
+
|
| 269 |
+
| | |
|
| 270 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 271 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 272 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 273 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 274 |
+
| Series F | Non-telephone telecommunication services |
|
| 275 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 276 |
+
| Series H | Audiovisual and multimedia systems |
|
| 277 |
+
| Series I | Integrated services digital network |
|
| 278 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 279 |
+
| Series K | Protection against interference |
|
| 280 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 281 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 282 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 283 |
+
| Series O | Specifications of measuring equipment |
|
| 284 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 285 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 286 |
+
| Series R | Telegraph transmission |
|
| 287 |
+
| Series S | Telegraph services terminal equipment |
|
| 288 |
+
| Series T | Terminals for telematic services |
|
| 289 |
+
| Series U | Telegraph switching |
|
| 290 |
+
| Series V | Data communication over the telephone network |
|
| 291 |
+
| Series X | Data networks, open system communications and security |
|
| 292 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 293 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.Sup6-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.Sup6-202408-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,218 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
# Supplement **ITU-T A Suppl. 6 (08/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
Supplements to the Series A Recommendations
|
| 7 |
+
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
# **Guidelines for the development of a standardization gap analysis**
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
|
| 14 |
+
## Supplement 6 to ITU-T A-series Recommendations
|
| 15 |
+
|
| 16 |
+
## Guidelines for the development of a standardization gap analysis
|
| 17 |
+
|
| 18 |
+
## Summary
|
| 19 |
+
|
| 20 |
+
Supplement 6 to the ITU-T A-series Recommendations provides guidelines for ITU-T study groups to develop a standardization gap analysis based on standards developed by other ITU study groups or other standards development organizations. A standardization gap analysis may be beneficial for a study group when considering new areas of work (e.g., establishing a new Question, establishing a focus group, adding a new work item to its work programme). A focus group may also develop a standardization gap analysis.
|
| 21 |
+
|
| 22 |
+
## History \*
|
| 23 |
+
|
| 24 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 25 |
+
|---------|------------------|------------|-------------|--------------------|
|
| 26 |
+
| 1.0 | ITU-T A Suppl. 6 | 2024-08-02 | TSAG | 11.1002/1000/16141 |
|
| 27 |
+
|
| 28 |
+
## Keywords
|
| 29 |
+
|
| 30 |
+
Collaboration, gap analysis, study programme, template.
|
| 31 |
+
|
| 32 |
+
---
|
| 33 |
+
|
| 34 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 35 |
+
|
| 36 |
+
## FOREWORD
|
| 37 |
+
|
| 38 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 39 |
+
|
| 40 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 41 |
+
|
| 42 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 43 |
+
|
| 44 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 45 |
+
|
| 46 |
+
## NOTE
|
| 47 |
+
|
| 48 |
+
This is an informative ITU-T publication. Mandatory provisions, such as those found in ITU-T Recommendations, are outside the scope of this publication. This publication should only be referenced bibliographically in ITU-T Recommendations.
|
| 49 |
+
|
| 50 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 51 |
+
|
| 52 |
+
ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the standards development process.
|
| 53 |
+
|
| 54 |
+
As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this publication. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 55 |
+
|
| 56 |
+
© ITU 2024
|
| 57 |
+
|
| 58 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 59 |
+
|
| 60 |
+
# Supplement 6 to ITU-T A-series Recommendations
|
| 61 |
+
|
| 62 |
+
# Guidelines for the development of a standardization gap analysis
|
| 63 |
+
|
| 64 |
+
## 1 Scope
|
| 65 |
+
|
| 66 |
+
Conducting a standardization gap analysis based on standards developed by other ITU study groups or other international standards development organizations (ISO, IEC and relevant ITU-T A.5-qualified organizations<sup>1</sup>) can foster a common understanding of the work that needs to be done and can help identify potential competitive advantages and strategic standardization opportunities while optimizing the allocation of resources. This approach could be advantageous when a study group plans to:
|
| 67 |
+
|
| 68 |
+
- expand its scope,
|
| 69 |
+
- establish a new Question,
|
| 70 |
+
- form a focus group, or
|
| 71 |
+
- add a new work item to its work programme.
|
| 72 |
+
|
| 73 |
+
Focus groups may also develop a standardization gap analysis.
|
| 74 |
+
|
| 75 |
+
A standardization gap analysis is normally provided in a contribution to a meeting and further refined during the meeting.
|
| 76 |
+
|
| 77 |
+
## 2 References
|
| 78 |
+
|
| 79 |
+
- [ITU-T A.1] Recommendation ITU-T A.1 (2019), *Working methods for study groups of the ITU Telecommunication Standardization Sector (ITU-T)*.
|
| 80 |
+
- [ITU-T A.2] Recommendation ITU-T A.2 (2012), *Presentation of contributions to the ITU Telecommunication Standardization Sector*.
|
| 81 |
+
- [ITU-T A.7] Recommendation ITU-T A.7 (2024), *Focus groups: Establishment and working procedures*.
|
| 82 |
+
- [ITU-T A.13] Recommendation ITU-T A.13 (2019), *Non-normative ITU-T publications, including Supplements to ITU-T Recommendations*.
|
| 83 |
+
- [ITU-T A.23] Recommendation ITU-T A.23 (2000), *Collaboration with the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) on information technology*.
|
| 84 |
+
- [ITU-T A-Suppl.3] Supplement 3 to ITU-T A-series Recommendations (2012), *IETF and ITU-T collaboration guidelines*.
|
| 85 |
+
- [WTSA Res. 1] WTSA Resolution 1 (Rev. Geneva, 2022), *Rules of procedure of the ITU Telecommunication Standardization Sector*.
|
| 86 |
+
- [WTSA Res. 2] WTSA Resolution 2 (Rev. Geneva, 2022), *ITU Telecommunication Standardization Sector study group responsibility and mandates*.
|
| 87 |
+
|
| 88 |
+
## 3 Definitions
|
| 89 |
+
|
| 90 |
+
### 3.1 Terms defined elsewhere
|
| 91 |
+
|
| 92 |
+
None.
|
| 93 |
+
|
| 94 |
+
---
|
| 95 |
+
|
| 96 |
+
<sup>1</sup> See <https://itu.int/go/a5orgs>.
|
| 97 |
+
|
| 98 |
+
### 3.2 Terms defined in this Supplement
|
| 99 |
+
|
| 100 |
+
This Supplement defines the following term:
|
| 101 |
+
|
| 102 |
+
**3.2.1 standardization gap analysis:** Process of identifying discrepancies or deficiencies between current standardization activities in ITU, ISO, IEC and ITU-T A.5-qualified organizations, and desired or optimal standardization activities, aiming to identify the gaps within a specific domain.
|
| 103 |
+
|
| 104 |
+
## 4 Abbreviations and acronyms
|
| 105 |
+
|
| 106 |
+
This Supplement uses the following abbreviations and acronyms:
|
| 107 |
+
|
| 108 |
+
| | |
|
| 109 |
+
|------|------------------------------------------------|
|
| 110 |
+
| IEC | International Electrotechnical Commission |
|
| 111 |
+
| IETF | Internet Engineering Task Force |
|
| 112 |
+
| ISO | International Organization for Standardization |
|
| 113 |
+
| SDO | Standards Development Organizations |
|
| 114 |
+
| SMB | Standardization Management Board |
|
| 115 |
+
| SPCG | Standardization Programme Coordination Group |
|
| 116 |
+
| TMB | Technical Management Board |
|
| 117 |
+
|
| 118 |
+
## 5 Conventions
|
| 119 |
+
|
| 120 |
+
None.
|
| 121 |
+
|
| 122 |
+
## 6 Context of use and benefits
|
| 123 |
+
|
| 124 |
+
**6.1** A standardization gap analysis can be used to consolidate information, which in turns leads to the effective and efficient delineation of the scope of the work. Although the templates specified in clause 7 are not mandatory, it is recommended that they be used to enhance a common understanding of the work that needs to be done.
|
| 125 |
+
|
| 126 |
+
**6.1.1** According to *decides* 1 of [ITU-T A.23], every effort should be made by ITU-T, ISO and IEC in establishing their respective study programmes to identify overlapping studies with a view to avoiding duplication of work. One of the objectives of the IEC SMB/ISO TMB/ITU-T TSAG Standardization Programme Coordination Group (SPCG) is to review existing standardization activities in IEC, ISO and ITU-T, and identify areas where coordination is required and/or could be enhanced.
|
| 127 |
+
|
| 128 |
+
**6.1.2** According to [ITU-T A-Suppl.3], study groups that have identified work topics that are related to the Internet protocol (IP) should evaluate the relationship with topics defined in the IETF.
|
| 129 |
+
|
| 130 |
+
**6.2** Based on discussions at a meeting, a study group (or a focus group) may agree to conduct a standardization gap analysis:
|
| 131 |
+
|
| 132 |
+
- when the study group is considering expanding its scope (see [WTSA Res. 2]);
|
| 133 |
+
- when the study group is considering establishing a new Question (see section 7 of [WTSA Res. 1]);
|
| 134 |
+
- when the focus group is being formed (see [ITU-T A.7]);
|
| 135 |
+
- when the study group is considering adding a new work item to its work programme (see clause 1.4.7 of [ITU-T A.1], and clause 8.1 of [ITU-T A.13]);
|
| 136 |
+
- as a focus group deliverable (see [ITU-T A.7]).
|
| 137 |
+
|
| 138 |
+
**6.3** When drafting a contribution (see [ITU-T A.2]) addressing one of the cases listed in clause 6.2, a member may also find it beneficial to provide a standardization gap analysis. A standardization
|
| 139 |
+
|
| 140 |
+
gap analysis will benefit from the knowledge of all experts attending the meeting where it is discussed. To the extent possible, TSB may assist members to access the references, documentation and/or summary necessary to help the member conducting such an analysis.
|
| 141 |
+
|
| 142 |
+
## **7 Templates**
|
| 143 |
+
|
| 144 |
+
- 7.1** A standardization gap analysis can be organized in two ways:
|
| 145 |
+
- starting from a perceived gap and then considering the standardization activities impacted (see Table 1); and/or
|
| 146 |
+
- starting from the perspective of the study groups and other SDOs in the standardization ecosystem, identifying their standardization activities, and then determining (by comparison) if there is a gap to fill (see Table 2).
|
| 147 |
+
- 7.2** Table 1 and Table 2 are not mutually exclusive. Table 2 is valuable for gaining insight into the ecosystem, and Table 1 is beneficial for quick and convenient referencing of the gaps.
|
| 148 |
+
- 7.3** Table 1 is formatted in a form that will capture each gap, provide a description of the gap and point to the standardization activities that are impacted.
|
| 149 |
+
|
| 150 |
+
**Table 1 – Template to describe standardization gaps**
|
| 151 |
+
|
| 152 |
+
| | |
|
| 153 |
+
|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
| 154 |
+
| <b>Gap:</b> <i><Identifier></i> | <b>Title:</b> <i><Short descriptive title></i> |
|
| 155 |
+
| <b>Gap description:</b> | <i><Description of the gap, including area(s) where the gap exists></i> |
|
| 156 |
+
| <b>Future work:</b> | <i><Description of the future work/study needed to fill the gap (as [ITU-T A.1] or [ITU-T A.13] justifications, when applicable)></i> |
|
| 157 |
+
| <b>Related work:</b> | <i><Existing and draft standards which are relevant to the future work; SDOs impacted></i> |
|
| 158 |
+
|
| 159 |
+
**7.4** Table 2 is formatted so that each organization has multiple rows in the table, providing a way to list all the standardization activities (i.e., approved standards or ongoing work items) that need to be considered as part of the standardization gap analysis.
|
| 160 |
+
|
| 161 |
+
**Table 2 – Template to describe existing standards**
|
| 162 |
+
|
| 163 |
+
| <b>SDO</b> | <b>Standards reference and title</b> | <b>Short description</b> |
|
| 164 |
+
|-------------------------|---------------------------------------------|------------------------------------------------------------------------------------|
|
| 165 |
+
| <i><SDO name></i> | <i><Standards reference: "Title"></i> | <i><Description (in relation with the specific domain being considered)></i> |
|
| 166 |
+
|
| 167 |
+
**7.5** Each table is followed by a paragraph that provides a comparative analysis between the intended standardization activities and the existing ones described in the table.
|
| 168 |
+
|
| 169 |
+
## Appendix I
|
| 170 |
+
|
| 171 |
+
### Examples
|
| 172 |
+
|
| 173 |
+
This appendix provides an example of use of the templates in Table 1 and Table 2, for illustration only.
|
| 174 |
+
|
| 175 |
+
**Table I.1 – Example of a standardization gap described using the template of Table 1**
|
| 176 |
+
|
| 177 |
+
| | |
|
| 178 |
+
|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 179 |
+
| <b>Gap: G1</b> | Title: Media protection modelling is missing for Transport Element Optical Media Management |
|
| 180 |
+
| <b>Gap description:</b> | Optical media protection as described in ITU-T G.807 "Generic functional architecture of the optical media network" is an important capability that is currently missing from the ITU-T Q14/15 management model Recommendations. |
|
| 181 |
+
| <b>Future work:</b> | Enhance the optical media model described in ITU-T G.875 "Optical transport network: Protocol-neutral management information model for the network element view" adding the model for optical media protection. |
|
| 182 |
+
| <b>Related work:</b> | ITU-T G.875, ITU-T G.807, ITU-T G.798, Optical Internetworking Forum (OIF) FlexE IA, IEEE Std 802.3 |
|
| 183 |
+
|
| 184 |
+
**Table I.2 – Example of an existing standard described using the template of Table 2**
|
| 185 |
+
|
| 186 |
+
| <b>SDO</b> | <b>Standards reference and title</b> | <b>Short description</b> |
|
| 187 |
+
|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 188 |
+
| Optical Internetworking Forum (OIF) | FlexE 2.2 Implementation Agreement<br>< <a href="https://www.oiforum.com/wp-content/uploads/OIF-FLEXE-02.2.pdf">https://www.oiforum.com/wp-content/uploads/OIF-FLEXE-02.2.pdf</a> > | The Flex Ethernet (FlexE) Implementation Agreement provides a generic mechanism for supporting a variety of Ethernet MAC rates that may or may not correspond to any existing Ethernet PHY rate. |
|
| 189 |
+
|
| 190 |
+
|
| 191 |
+
|
| 192 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 193 |
+
|
| 194 |
+
| | |
|
| 195 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 196 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 197 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 198 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 199 |
+
| Series F | Non-telephone telecommunication services |
|
| 200 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 201 |
+
| Series H | Audiovisual and multimedia systems |
|
| 202 |
+
| Series I | Integrated services digital network |
|
| 203 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 204 |
+
| Series K | Protection against interference |
|
| 205 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 206 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 207 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 208 |
+
| Series O | Specifications of measuring equipment |
|
| 209 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 210 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 211 |
+
| Series R | Telegraph transmission |
|
| 212 |
+
| Series S | Telegraph services terminal equipment |
|
| 213 |
+
| Series T | Terminals for telematic services |
|
| 214 |
+
| Series U | Telegraph switching |
|
| 215 |
+
| Series V | Data communication over the telephone network |
|
| 216 |
+
| Series X | Data networks, open system communications and security |
|
| 217 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 218 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/A/T-REC-A.Sup7-202408-I_PDF-E/067602530aafbd65e10764142bb75566_img.jpg
ADDED
|
Git LFS Details
|
marked/A/T-REC-A.Sup7-202408-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,273 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
## Supplement **ITU-T A Suppl. 7 (08/2024)**
|
| 4 |
+
|
| 5 |
+
SERIES A: Organization of the work of ITU-T
|
| 6 |
+
Supplements to the Series A Recommendations
|
| 7 |
+
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
# **Guidelines for the preparation of WTSA Resolutions**
|
| 11 |
+
|
| 12 |
+
|
| 13 |
+
|
| 14 |
+
# Supplement 7 to ITU-T A-series Recommendation
|
| 15 |
+
|
| 16 |
+
## Guidelines for the preparation of WTSA Resolutions
|
| 17 |
+
|
| 18 |
+
## Summary
|
| 19 |
+
|
| 20 |
+
Supplement 7 to ITU-T A-series Recommendations provides guidelines for ITU-T members on the principles of streamlining Resolutions, as well as guidance on how to propose new draft Resolutions and revisions to existing World Telecommunication Standardization Assembly (WTSA) Resolutions in the preparation for WTSA.
|
| 21 |
+
|
| 22 |
+
The review process for WTSA Resolutions encompasses editorial updates, identifying overlap, identifying candidates for merging or suppression, simplifying or shortening Resolutions, preparing consolidated draft texts, and actively involving the regional telecommunication organizations (RTOs) in discussions leading up to a WTSA.
|
| 23 |
+
|
| 24 |
+
## History \*
|
| 25 |
+
|
| 26 |
+
| Edition | Recommendation | Approval | Study Group | Unique ID |
|
| 27 |
+
|---------|------------------|------------|-------------|--------------------|
|
| 28 |
+
| 1.0 | ITU-T A Suppl. 7 | 2024-08-02 | TSAG | 11.1002/1000/16142 |
|
| 29 |
+
|
| 30 |
+
## Keywords
|
| 31 |
+
|
| 32 |
+
Guidelines, Resolutions, streamlining, WTSA preparations.
|
| 33 |
+
|
| 34 |
+
---
|
| 35 |
+
|
| 36 |
+
\* To access the Recommendation, type the URL <https://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID.
|
| 37 |
+
|
| 38 |
+
## FOREWORD
|
| 39 |
+
|
| 40 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 41 |
+
|
| 42 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 43 |
+
|
| 44 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 45 |
+
|
| 46 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 47 |
+
|
| 48 |
+
## NOTE
|
| 49 |
+
|
| 50 |
+
This is an informative ITU-T publication. Mandatory provisions, such as those found in ITU-T Recommendations, are outside the scope of this publication. This publication should only be referenced bibliographically in ITU-T Recommendations.
|
| 51 |
+
|
| 52 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 53 |
+
|
| 54 |
+
ITU draws attention to the possibility that the practice or implementation of this publication may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the standards development process.
|
| 55 |
+
|
| 56 |
+
As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this publication. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at <http://www.itu.int/ITU-T/ipr/>.
|
| 57 |
+
|
| 58 |
+
© ITU 2024
|
| 59 |
+
|
| 60 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 61 |
+
|
| 62 |
+
## Table of Contents
|
| 63 |
+
|
| 64 |
+
| | <b>Page</b> |
|
| 65 |
+
|-------------------------------------------------------------------------|-------------|
|
| 66 |
+
| 1 Scope ..... | 1 |
|
| 67 |
+
| 2 References..... | 1 |
|
| 68 |
+
| 3 Definitions ..... | 1 |
|
| 69 |
+
| 3.1 Terms defined elsewhere ..... | 1 |
|
| 70 |
+
| 3.2 Terms defined in this Supplement ..... | 1 |
|
| 71 |
+
| 4 Abbreviations and acronyms ..... | 1 |
|
| 72 |
+
| 5 Conventions ..... | 2 |
|
| 73 |
+
| 6 Guidelines for streamlining resolutions ..... | 2 |
|
| 74 |
+
| 6.1 Mechanisms and reasoning for streamlining Resolutions ..... | 2 |
|
| 75 |
+
| 6.2 Approach for streamlining Resolutions ..... | 2 |
|
| 76 |
+
| 6.3 Guiding principles for streamlining in-force WTSA Resolutions ..... | 3 |
|
| 77 |
+
| 7 Guidelines for drafting WTSA Resolutions ..... | 4 |
|
| 78 |
+
| Bibliography..... | 6 |
|
| 79 |
+
|
| 80 |
+
|
| 81 |
+
|
| 82 |
+
# **Supplement 7 to ITU-T A-series Recommendation**
|
| 83 |
+
|
| 84 |
+
## **Guidelines for the preparation of WTSA Resolutions**
|
| 85 |
+
|
| 86 |
+
## **1 Scope**
|
| 87 |
+
|
| 88 |
+
This Supplement provides guidelines for ITU-T members on the principles of streamlining Resolutions, as well as guidance on how to propose new draft Resolutions and revisions to existing World Telecommunication Standardization Assembly (WTSA) Resolutions in the preparation for WTSA.
|
| 89 |
+
|
| 90 |
+
The review process for WTSA Resolutions encompasses editorial updates, identifying overlap, identifying candidates for merging or suppression, simplifying or shortening Resolutions, preparing consolidated draft texts, and actively involving the regional telecommunication organizations (RTOs) in discussions leading up to a WTSA.
|
| 91 |
+
|
| 92 |
+
## **2 References**
|
| 93 |
+
|
| 94 |
+
None.
|
| 95 |
+
|
| 96 |
+
## **3 Definitions**
|
| 97 |
+
|
| 98 |
+
### **3.1 Terms defined elsewhere**
|
| 99 |
+
|
| 100 |
+
None.
|
| 101 |
+
|
| 102 |
+
### **3.2 Terms defined in this Supplement**
|
| 103 |
+
|
| 104 |
+
None.
|
| 105 |
+
|
| 106 |
+
## **4 Abbreviations and acronyms**
|
| 107 |
+
|
| 108 |
+
This Supplement uses the following abbreviations and acronyms:
|
| 109 |
+
|
| 110 |
+
| | |
|
| 111 |
+
|------|------------------------------------------------|
|
| 112 |
+
| ADD | Addition |
|
| 113 |
+
| ICT | Information and Communication Technology |
|
| 114 |
+
| MOD | Modification |
|
| 115 |
+
| MS | Member State |
|
| 116 |
+
| NOC | No Change |
|
| 117 |
+
| PP | Plenipotentiary Conference |
|
| 118 |
+
| RA | Radiocommunication Assembly |
|
| 119 |
+
| RTO | Regional Telecommunication Organization |
|
| 120 |
+
| SDG | Sustainable Development Goal |
|
| 121 |
+
| SG | Study Group |
|
| 122 |
+
| SM | Sector Member |
|
| 123 |
+
| SUP | Suppression |
|
| 124 |
+
| TSB | Telecommunication Standardization Bureau |
|
| 125 |
+
| WRC | World Radiocommunication Conference |
|
| 126 |
+
| WTDC | World Telecommunication Development Conference |
|
| 127 |
+
|
| 128 |
+
## 5 Conventions
|
| 129 |
+
|
| 130 |
+
None.
|
| 131 |
+
|
| 132 |
+
## 6 Guidelines for streamlining resolutions
|
| 133 |
+
|
| 134 |
+
### 6.1 Mechanisms and reasoning for streamlining Resolutions
|
| 135 |
+
|
| 136 |
+
This clause provides the potential streamlining action of Resolutions for modification (MOD) or suppression (SUP).
|
| 137 |
+
|
| 138 |
+
#### MOD (Modification)
|
| 139 |
+
|
| 140 |
+
**6.1.1 Modified** (to bring Resolutions up-to-date, or for improvement, or for housekeeping); or
|
| 141 |
+
|
| 142 |
+
**6.1.2 Merged** (for Resolutions thematically related to a particular actor entity, or Resolutions of the same category/subject) so as to reduce redundancy or overlap, including '**restructured**' (grouping together scattered information found in various Resolutions into one Resolution); or
|
| 143 |
+
|
| 144 |
+
**6.1.3 Simplified** where possible or reasonable while keeping adequate essential information, making texts more concise, simpler, easier to understand, and requiring less efforts for regular updating and maintenance; or
|
| 145 |
+
|
| 146 |
+
**6.1.4 Aligned** with other Resolutions (for Resolutions on generic subjects e.g., gender perspective, accessibility, etc.) such as Plenipotentiary Conference (PP) and Council Resolutions or Resolutions of other ITU sectors to focus on ITU-T specific actions and avoid duplication or repetition; or
|
| 147 |
+
|
| 148 |
+
#### SUP (Suppression)
|
| 149 |
+
|
| 150 |
+
**6.1.5 Suppressed** (for Resolutions with obsolete timing or milestones, completed with no further action to be taken, or have no action reported.)
|
| 151 |
+
|
| 152 |
+
### 6.2 Approach for streamlining Resolutions
|
| 153 |
+
|
| 154 |
+
This clause provides approaches to prepare Resolutions for streamlining.
|
| 155 |
+
|
| 156 |
+
**6.2.1** Review and examine in-force WTSA Resolutions with a view to streamlining them, considering, as appropriate:
|
| 157 |
+
|
| 158 |
+
- a) the PP Resolutions and Council Resolutions (vertically, where PP Resolutions prevail);
|
| 159 |
+
- b) Resolutions of other Sectors, such as World Telecommunication Development Conference (WTDC), World Radiocommunication Conference (WRC) and Radiocommunication Assembly (RA) (horizontally);
|
| 160 |
+
- c) the detailed report and status of its implementation as reflected in the WTSA Action Plan since it was established (ADDED at a previous WTSA). For reference, see: [[WTSA-12 DOC28](#)], [[WTSA-16 DOC35](#)], [[WTSA-20 DOC34](#)], [[WTSA-24 DOC34](#)].
|
| 161 |
+
|
| 162 |
+
**6.2.2** Examine the WTSA Resolutions with a view to avoid repetitions and duplication with the PP Resolutions.
|
| 163 |
+
|
| 164 |
+
**6.2.3** Prepare towards modification, suppression or addition of Resolutions for WTSA and PP.
|
| 165 |
+
|
| 166 |
+
### 6.3 Guiding principles for streamlining in-force WTSA Resolutions
|
| 167 |
+
|
| 168 |
+
**6.3.1** At WTSA, the in-force WTSA Resolutions should be examined with the objective to modify, merge, simplify, align or suppress completed or obsolete Resolutions and parts thereof based on contributions.
|
| 169 |
+
|
| 170 |
+
**6.3.2** The guiding principles in Table 1 might prove useful in the work on streamlining Resolutions and should be followed to the extent possible to help the ITU membership to draft proposals, so that WTSA Resolutions are concise, ITU-T focused, implementable, effective, and stay abreast of the evolution of information and communication technologies (ICTs) and service the standardization environment, taking into account World Summit on the Information Society (WSIS) Action Lines and UN Sustainable Development Goals (SDGs).
|
| 171 |
+
|
| 172 |
+
**Table 1 – Guiding principles for streamlining in-force WTSA Resolutions**
|
| 173 |
+
|
| 174 |
+
| Principle | Questions | Possible streamlining actions |
|
| 175 |
+
|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|
|
| 176 |
+
| Coherence and consistency | – Is the Resolution consistent with the ITU-T mandate (vs other ITU Sectors) and the WTSA Action Plan? | → MOD |
|
| 177 |
+
| Overlap and duplication | – Is there an overlap or duplication with other in-force WTSA/Council/PP Resolutions that address the same topic or action (in particular, Resolution 2 mandates of all ITU-T Study Groups), or with any action item already covered by the WTSA Action Plan?<br>– Are the goals of Resolutions already reflected in the ITU-T Strategic Plan objectives, outputs and outcomes, study group (SG) Questions or working methods? | → MOD and/or SUP |
|
| 178 |
+
| Necessity | – Is the Resolution indispensable as a stand-alone?<br>– Has the implementation of the Resolution already been completed? Is there any action instructed by the Resolution found unimplementable in the WTSA Action Plan? | → MOD, and/or SUP |
|
| 179 |
+
| Action-orientation and accountability | – Does the Resolution call for a specific action or outcome?<br>– Is there a clear accountability line or responsible actor in the Resolution? | → MOD |
|
| 180 |
+
|
| 181 |
+
**6.3.3** All similar or related subjects should be addressed in one single WTSA Resolution to the extent possible ("stand-alone principle"). In general, streamlining in-force Resolutions is preferable rather than adding a new WTSA Resolution. ITU-T Study Groups should analyse the implementation activities of related WTSA Resolutions during WTSA preparation and send a list of WTSA Resolution streamlining candidates to TSAG via a liaison statement.
|
| 182 |
+
|
| 183 |
+
**6.3.4** When the actions or activities put forward in a Resolution have been implemented or accomplished, the Resolution can be considered fulfilled and can be suppressed.
|
| 184 |
+
|
| 185 |
+
**6.3.5** If no change is to be made to the substance of the WTSA Resolution, no editorial updates (such as date or venue of the conference) will be made to the WTSA Resolution, i.e., it should remain as is, that is, No Change (NOC).
|
| 186 |
+
|
| 187 |
+
**6.3.6** Editorial modifications of adopted Resolutions should be kept to a minimum or to what is strictly necessary for their efficient implementation.
|
| 188 |
+
|
| 189 |
+
**6.3.7** If only editorial updates are required to a WTSA Resolution, the necessary editorial amendments could be entrusted by WTSA to the Telecommunication Standardization Bureau (TSB) for the necessary updates and publication of the Resolution.
|
| 190 |
+
|
| 191 |
+
**6.3.8** All PP and WTSA Resolutions in the same category/subject should be reviewed during the preparation of WTSA in regional preparatory meetings and as much as possible in inter-regional coordination meetings. A list of WTSA Resolution streamlining candidates should be prepared by
|
| 192 |
+
|
| 193 |
+
TSB based on all the SG liaison statements (see clause 6.3.3) for further consideration by ITU-T members.
|
| 194 |
+
|
| 195 |
+
## 7 Guidelines for drafting WTSA Resolutions
|
| 196 |
+
|
| 197 |
+
The following principles are suggested to be followed to help the ITU membership draft proposals on new and modified Resolutions, so that Resolutions of the World Telecommunication Standardization Assembly are concise and ITU-T focused, implementable, effective and stay abreast of the evolution of telecommunication and information technologies and the ICT standardization environment.
|
| 198 |
+
|
| 199 |
+
**7.1** At WTSA, the in-force WTSA Resolutions should be examined with the objective to suppress completed or obsolete ones and parts thereof based on contributions from ITU Member States (MSs) and ITU-T Sector Members (SMs), taking into consideration the detailed report and status of its implementation as reflected in the WTSA Action Plan since it was established (ADDED at a previous WTSA). For reference, see: [[WTSA-12 DOC28](#)], [[WTSA-16 DOC35](#)], [[WTSA-20 DOC34](#)], [[WTSA-24 DOC34](#)].
|
| 200 |
+
|
| 201 |
+
**7.2** If no change is to be made to the substance of a WTSA Resolution, no editorial updates (such as date or venue of the conference) should be proposed to the WTSA Resolution, i.e., it should remain as is (NOC).
|
| 202 |
+
|
| 203 |
+
**7.3** All similar or related subjects should be addressed in one single WTSA Resolution to the extent possible ("stand-alone principle"). Thus, in general, revising an in-force WTSA Resolution is preferable to adding a new WTSA Resolution.
|
| 204 |
+
|
| 205 |
+
**7.4** It is preferable for a WTSA Resolution not to exceed **four** A4-pages (except for Resolutions 1 and 2).
|
| 206 |
+
|
| 207 |
+
**7.5** The "preamble" part of a WTSA Resolution should be as concise as possible, summarizing key rationales for justification. It is undesirable to repeat the "preamble" part of the relevant PP Resolution, it is enough to include a reference to this Resolution. **It is preferable that the "preamble" part does not exceed one A4 page.** While any additional explanation and justification such as a detailed chronicle of events, bibliography, historical activities and achievements could be submitted as background material in a contribution, their inclusion shall be avoided in the adopted final WTSA Resolution text.
|
| 208 |
+
|
| 209 |
+
**7.6** Cross-reference to other ITU Resolutions should be kept to a minimum as necessary ("minimum cross-reference principle"), while striking a balance to avoid inserting material copied from other instruments.
|
| 210 |
+
|
| 211 |
+
**7.7** Once an ITU Resolution on the same or relevant subject is referenced, any identical justification or rational text should be minimized whereas additional ITU-T specific justification or rational could be added to this WTSA Resolution ("no repetition principle").
|
| 212 |
+
|
| 213 |
+
**7.8** Reference to the ITU Constitution, Convention and the General Rules should prevail over a reference to a Resolution of a Plenipotentiary Conference when applicable. Where it is strongly required, such references could co-exist with a duplication of the referred text to make the WTSA Resolution stand on its own (exception to "stand-alone principle").
|
| 214 |
+
|
| 215 |
+
**7.9** When reference to the conclusion or output of an event is deemed necessary, the reference should be meaningful and in substance to specify its relevance, avoiding listing only the event per se ("no chronicle of events principle").
|
| 216 |
+
|
| 217 |
+
**7.10** Any reference to documents should be meaningful and substantive to specify its relevance to the purpose of the Resolution ("no bibliography principle").
|
| 218 |
+
|
| 219 |
+
**7.11** When drafting the "operational" part of a WTSA Resolution, the following should be kept in mind:
|
| 220 |
+
|
| 221 |
+
- a. an instruction given to the ITU membership is non-binding;
|
| 222 |
+
- b. an instruction given to ITU-T SGs or TSAG will serve its purpose only if followed by a contribution to the ITU-T SG to drive the work to progress. SG or TSAG management team may also encourage members to support the implementation of the instruction.
|
| 223 |
+
|
| 224 |
+
**7.12** The "operational" part of a WTSA Resolution should:
|
| 225 |
+
|
| 226 |
+
- a. include instructions and tasks from the relevant PP Resolutions;
|
| 227 |
+
- b. include instructions and tasks assigned by other ITU conferences and assemblies to ITU-T on the relevant thematic;
|
| 228 |
+
- c. use an appropriate verb to specify an implementable action by a respective entity according to its proper mandate ("identified entity and specific action principle");
|
| 229 |
+
- d. specify an expected result (or results) so that the achievement in implementing this action can be measurable as much as possible using objective measurement methodologies ("measurable result principle");
|
| 230 |
+
- e. plan or recommend a course of action with milestones and/or checkpoints as appropriate ("planning principle");
|
| 231 |
+
- f. specify a reporting and expiration mechanism as appropriate ("report/expire principle"); and
|
| 232 |
+
- g. specify concrete instructions for relevant SGs and TSAG for the implementation of the Resolution, if required.
|
| 233 |
+
|
| 234 |
+
## Bibliography
|
| 235 |
+
|
| 236 |
+
- [[WTSA-12 DOC28](#)] World Telecommunication Standardization Assembly 2012, WTSA-12 DOC28, *Action Plan related to the Resolutions and Decision of PP-10 and of WTSA-08*.
|
| 237 |
+
<https://www.itu.int/md/meetingdoc.asp?lang=en&parent=T09-WTSA.12-C-0028>
|
| 238 |
+
- [[WTSA-16 DOC35](#)] World Telecommunication Standardization Assembly 2016, WTSA-16 DOC35, *Action Plan related to the Resolutions and Opinion of WTSA-12*.
|
| 239 |
+
<https://www.itu.int/md/meetingdoc.asp?lang=en&parent=T13-WTSA.16-C-0035>
|
| 240 |
+
- [[WTSA-20 DOC34](#)] World Telecommunication Standardization Assembly 2020, WTSA-20 DOC34, *Action Plan related to the Resolutions and Opinion of WTSA-16, and TSB Director Reports to WTSA-20 on WTSA Resolutions 40, 44, 55, 64, 65, 68, 69, 72, 73, 89, and PP Resolution 102*.
|
| 241 |
+
<https://www.itu.int/md/meetingdoc.asp?lang=en&parent=T17-WTSA.20-C-0034>
|
| 242 |
+
- [[WTSA-24 DOC34](#)] World Telecommunication Standardization Assembly 2024, [WTSA-24 DOC34](#), *Action Plan related to the Resolutions and Opinion of WTSA-20, and TSB Director Reports to WTSA-24 on WTSA Resolutions 40, 44, 55, 64, 65, 68, 69, 72, 73, 89, 99, 100, and PP Resolution 102*.
|
| 243 |
+
<https://www.itu.int/md/meetingdoc.asp?lang=en&parent=T22-WTSA.24-C-0034>
|
| 244 |
+
|
| 245 |
+
|
| 246 |
+
|
| 247 |
+
## SERIES OF ITU-T RECOMMENDATIONS
|
| 248 |
+
|
| 249 |
+
| | |
|
| 250 |
+
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
|
| 251 |
+
| <b>Series A</b> | <b>Organization of the work of ITU-T</b> |
|
| 252 |
+
| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
|
| 253 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 254 |
+
| Series F | Non-telephone telecommunication services |
|
| 255 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 256 |
+
| Series H | Audiovisual and multimedia systems |
|
| 257 |
+
| Series I | Integrated services digital network |
|
| 258 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 259 |
+
| Series K | Protection against interference |
|
| 260 |
+
| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
|
| 261 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 262 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 263 |
+
| Series O | Specifications of measuring equipment |
|
| 264 |
+
| Series P | Telephone transmission quality, telephone installations, local line networks |
|
| 265 |
+
| Series Q | Switching and signalling, and associated measurements and tests |
|
| 266 |
+
| Series R | Telegraph transmission |
|
| 267 |
+
| Series S | Telegraph services terminal equipment |
|
| 268 |
+
| Series T | Terminals for telematic services |
|
| 269 |
+
| Series U | Telegraph switching |
|
| 270 |
+
| Series V | Data communication over the telephone network |
|
| 271 |
+
| Series X | Data networks, open system communications and security |
|
| 272 |
+
| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
|
| 273 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/D/T-REC-D.000-201005-I_PDF-E/f80fa557938e5520d93e844924a94f76_img.jpg
ADDED
|
Git LFS Details
|
marked/D/T-REC-D.000-201005-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,392 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
|
| 4 |
+
|
| 5 |
+
**ITU-T**
|
| 6 |
+
|
| 7 |
+
TELECOMMUNICATION
|
| 8 |
+
STANDARDIZATION SECTOR
|
| 9 |
+
OF ITU
|
| 10 |
+
|
| 11 |
+
**D.000**
|
| 12 |
+
|
| 13 |
+
(05/2010)
|
| 14 |
+
|
| 15 |
+
SERIES D: GENERAL TARIFF PRINCIPLES
|
| 16 |
+
|
| 17 |
+
Terms and definitions
|
| 18 |
+
|
| 19 |
+
# --- **Terms and definitions for the D-series Recommendations**
|
| 20 |
+
|
| 21 |
+
Recommendation ITU-T D.000
|
| 22 |
+
|
| 23 |
+
|
| 24 |
+
|
| 25 |
+
The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking it, and the text "ITU" in blue, with "International Telecommunication Union" in smaller blue text below it.
|
| 26 |
+
|
| 27 |
+
ITU logo
|
| 28 |
+
|
| 29 |
+
# ITU-T D-SERIES RECOMMENDATIONS
|
| 30 |
+
|
| 31 |
+
# GENERAL TARIFF PRINCIPLES
|
| 32 |
+
|
| 33 |
+
| <b>TERMS AND DEFINITIONS</b> | <b>D.0</b> |
|
| 34 |
+
|--------------------------------------------------------------------------------------------------------|-------------|
|
| 35 |
+
| <b>GENERAL TARIFF PRINCIPLES</b> | |
|
| 36 |
+
| Private leased telecommunication facilities | D.1–D.9 |
|
| 37 |
+
| Tariff principles applying to data communication services over dedicated public data networks | D.10–D.39 |
|
| 38 |
+
| Charging and accounting in the international public telegram service | D.40–D.44 |
|
| 39 |
+
| Charging and accounting in the international telex message service | D.45–D.49 |
|
| 40 |
+
| Principles applicable to GII-Internet | D.50–D.59 |
|
| 41 |
+
| Charging and accounting in the international telex service | D.60–D.69 |
|
| 42 |
+
| Charging and accounting in the international facsimile service | D.70–D.75 |
|
| 43 |
+
| Charging and accounting in the international videotex service | D.76–D.79 |
|
| 44 |
+
| Charging and accounting in the international phototelegraph service | D.80–D.89 |
|
| 45 |
+
| Charging and accounting in the mobile services | D.90–D.99 |
|
| 46 |
+
| Charging and accounting in the international telephone service | D.100–D.159 |
|
| 47 |
+
| Drawing up and exchange of international telephone and telex accounts | D.160–D.179 |
|
| 48 |
+
| International sound- and television-programme transmissions | D.180–D.184 |
|
| 49 |
+
| Charging and accounting for international satellite services | D.185–D.189 |
|
| 50 |
+
| Transmission of monthly international accounting information | D.190–D.191 |
|
| 51 |
+
| Service and privilege telecommunications | D.192–D.195 |
|
| 52 |
+
| Settlement of international telecommunication balances of accounts | D.196–D.209 |
|
| 53 |
+
| Charging and accounting principles for international telecommunication services provided over the ISDN | D.210–D.269 |
|
| 54 |
+
| Charging and accounting principles for next generation networks (NGN) | D.270–D.279 |
|
| 55 |
+
| Charging and accounting principles for universal personal telecommunication | D.280–D.284 |
|
| 56 |
+
| Charging and accounting principles for intelligent network supported services | D.285–D.299 |
|
| 57 |
+
| <b>RECOMMENDATIONS FOR REGIONAL APPLICATION</b> | |
|
| 58 |
+
| Recommendations applicable in Europe and the Mediterranean Basin | D.300–D.399 |
|
| 59 |
+
| Recommendations applicable in Latin America | D.400–D.499 |
|
| 60 |
+
| Recommendations applicable in Asia and Oceania | D.500–D.599 |
|
| 61 |
+
| Recommendations applicable to the African Region | D.600–D.699 |
|
| 62 |
+
|
| 63 |
+
*For further details, please refer to the list of ITU-T Recommendations.*
|
| 64 |
+
|
| 65 |
+
# **Recommendation ITU-T D.000**
|
| 66 |
+
|
| 67 |
+
# **Terms and definitions for the D-series Recommendations**
|
| 68 |
+
|
| 69 |
+
## **Summary**
|
| 70 |
+
|
| 71 |
+
Recommendation ITU-T D.000 sets out the general principles for developing and using terms and definitions in the D-series Recommendations. The Recommendation also contains a list of definitions applicable to all D-series Recommendations.
|
| 72 |
+
|
| 73 |
+
## **History**
|
| 74 |
+
|
| 75 |
+
| Edition | Recommendation | Approval | Study Group |
|
| 76 |
+
|---------|-----------------------------|------------|-------------|
|
| 77 |
+
| 1.0 | ITU-T D.000 | 1984-10-19 | |
|
| 78 |
+
| 2.0 | ITU-T D.000 | 1988-11-25 | |
|
| 79 |
+
| 3.0 | ITU-T D.000 | 1993-03-12 | III |
|
| 80 |
+
| 4.0 | ITU-T D.000 | 2000-10-06 | 3 |
|
| 81 |
+
| 5.0 | ITU-T D.000 | 2002-06-14 | 3 |
|
| 82 |
+
| 5.1 | ITU-T D.000 (2002) Amend. 1 | 2007-10-09 | 3 |
|
| 83 |
+
| 6.0 | ITU-T D.000 | 2010-05-21 | 3 |
|
| 84 |
+
|
| 85 |
+
## FOREWORD
|
| 86 |
+
|
| 87 |
+
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 88 |
+
|
| 89 |
+
The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
|
| 90 |
+
|
| 91 |
+
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
|
| 92 |
+
|
| 93 |
+
In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
|
| 94 |
+
|
| 95 |
+
## NOTE
|
| 96 |
+
|
| 97 |
+
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
|
| 98 |
+
|
| 99 |
+
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
|
| 100 |
+
|
| 101 |
+
## INTELLECTUAL PROPERTY RIGHTS
|
| 102 |
+
|
| 103 |
+
ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
|
| 104 |
+
|
| 105 |
+
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
|
| 106 |
+
|
| 107 |
+
© ITU 2010
|
| 108 |
+
|
| 109 |
+
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
|
| 110 |
+
|
| 111 |
+
# CONTENTS
|
| 112 |
+
|
| 113 |
+
| | | <b>Page</b> |
|
| 114 |
+
|---------|-----------------------------------------------------|-------------|
|
| 115 |
+
| 1 | Requirements ..... | 1 |
|
| 116 |
+
| 2 | General principles ..... | 1 |
|
| 117 |
+
| 3 | List of definitions ..... | 1 |
|
| 118 |
+
| Annex A | – Definitions ..... | 2 |
|
| 119 |
+
| A.1 | Accounting rate ..... | 2 |
|
| 120 |
+
| A.2 | Settlement rate ..... | 2 |
|
| 121 |
+
| A.3 | Termination charge ..... | 2 |
|
| 122 |
+
| A.4 | Collection charge ..... | 2 |
|
| 123 |
+
| A.5 | Lease ..... | 2 |
|
| 124 |
+
| A.6 | Rental ..... | 2 |
|
| 125 |
+
| A.7 | Network (service) access component ..... | 2 |
|
| 126 |
+
| A.8 | Network (service) utilization component ..... | 2 |
|
| 127 |
+
| A.9 | Service invocation component ..... | 2 |
|
| 128 |
+
| A.10 | Full refund ..... | 2 |
|
| 129 |
+
| A.11 | Partial refund ..... | 3 |
|
| 130 |
+
| A.12 | Relation ..... | 3 |
|
| 131 |
+
| A.13 | Origin country (or Administration) ..... | 3 |
|
| 132 |
+
| A.14 | Destination country (or Administration) ..... | 3 |
|
| 133 |
+
| A.15 | Terminal country (or Administration) ..... | 3 |
|
| 134 |
+
| A.16 | Transit country (or Administration) ..... | 3 |
|
| 135 |
+
| A.17 | International circuit ..... | 3 |
|
| 136 |
+
| A.18 | National extension ..... | 3 |
|
| 137 |
+
| A.19 | Remuneration for shared use and exclusive use ..... | 4 |
|
| 138 |
+
| A.20 | Flat-rate price per circuit procedure ..... | 4 |
|
| 139 |
+
| A.21 | Traffic-unit price procedure ..... | 4 |
|
| 140 |
+
| A.22 | Accounting revenue division procedure ..... | 4 |
|
| 141 |
+
| A.23 | Accounting rate share ..... | 4 |
|
| 142 |
+
| A.24 | Terminal share ..... | 4 |
|
| 143 |
+
| A.25 | Transit share ..... | 4 |
|
| 144 |
+
| A.26 | Per word tariff system ..... | 5 |
|
| 145 |
+
| A.27 | Binary tariff system ..... | 5 |
|
| 146 |
+
| A.28 | Non-discrimination ..... | 5 |
|
| 147 |
+
| A.29 | Transparency ..... | 5 |
|
| 148 |
+
| A.30 | Cost oriented ..... | 5 |
|
| 149 |
+
| A.31 | Hub ..... | 5 |
|
| 150 |
+
| A.32 | Hubbing ..... | 5 |
|
| 151 |
+
|
| 152 |
+
|
| 153 |
+
|
| 154 |
+
# **Recommendation ITU-T D.000**
|
| 155 |
+
|
| 156 |
+
# **Terms and definitions for the D-series Recommendations**
|
| 157 |
+
|
| 158 |
+
## **1 Requirements**
|
| 159 |
+
|
| 160 |
+
**1.1** There is a need for a structured approach to developing and using terms and definitions in D-series Recommendations. Such an approach will enhance the clarity of Recommendations and the effectiveness of communications related to the development and application of Recommendations.
|
| 161 |
+
|
| 162 |
+
**1.2** There are many existing terms originally defined in technical/operational contexts which are being used with tariff connotations. There is a need for the qualification and/or definition of such terms for tariffication purposes.
|
| 163 |
+
|
| 164 |
+
## **2 General principles**
|
| 165 |
+
|
| 166 |
+
**2.1** It is desirable that, to the greatest extent possible, terms used in D-series Recommendations be applied with the same and unique definition in these Recommendations (see clause 3).
|
| 167 |
+
|
| 168 |
+
**2.2** It is recognized that for certain reasons (e.g., increased precision) in certain cases, the general definition given as per clause 3 might not be appropriate in a specific Recommendation. In such instances the qualification of the term for use in that specific Recommendation should be indicated by a footnote.
|
| 169 |
+
|
| 170 |
+
**2.3** In the absence of a general definition as per clause 3, terms that may give rise to misinterpretation should be defined within the specific Recommendation.
|
| 171 |
+
|
| 172 |
+
**2.4** In cases of non-tariff terms used in D-series Recommendations, their use should generally be consistent with ITU-T Terms and Definitions Database.
|
| 173 |
+
|
| 174 |
+
## **3 List of definitions**
|
| 175 |
+
|
| 176 |
+
A list of terms with definitions applicable to D-series Recommendations is provided in Annex A.
|
| 177 |
+
|
| 178 |
+
## **Annex A**
|
| 179 |
+
|
| 180 |
+
### **Definitions**
|
| 181 |
+
|
| 182 |
+
(This annex forms an integral part of this Recommendation)
|
| 183 |
+
|
| 184 |
+
### **A.1 Accounting rate**
|
| 185 |
+
|
| 186 |
+
The rate agreed between Administrations in a given relation that is used for the establishment of international accounts.<sup>1</sup>
|
| 187 |
+
|
| 188 |
+
### **A.2 Settlement rate**
|
| 189 |
+
|
| 190 |
+
A rate agreed between involved administrations/ROAs for terminating incoming traffic.
|
| 191 |
+
|
| 192 |
+
### **A.3 Termination charge**
|
| 193 |
+
|
| 194 |
+
A charge set by the destination administration/ROA for terminating incoming traffic regardless of origin.
|
| 195 |
+
|
| 196 |
+
### **A.4 Collection charge**
|
| 197 |
+
|
| 198 |
+
The charge established and collected by an Administration from its customers for the use of an international telecommunication service.
|
| 199 |
+
|
| 200 |
+
### **A.5 Lease**
|
| 201 |
+
|
| 202 |
+
An agreement whereby a certain facility is made available by an Administration or Administrations to a customer or customers for his or their exclusive use.
|
| 203 |
+
|
| 204 |
+
### **A.6 Rental**
|
| 205 |
+
|
| 206 |
+
Payment(s) due to Administrations for the provision of certain facilities or access to certain facilities/services for designated periods.
|
| 207 |
+
|
| 208 |
+
### **A.7 Network (service) access component**
|
| 209 |
+
|
| 210 |
+
A tariff component, normally intended to compensate Administrations for the facilities required for a customer to access a service or services, which is independent of service utilization.
|
| 211 |
+
|
| 212 |
+
### **A.8 Network (service) utilization component**
|
| 213 |
+
|
| 214 |
+
A tariff component which is normally intended to cover the costs of a service that are dependent on the customer's use of the network resources and any additional functions.
|
| 215 |
+
|
| 216 |
+
### **A.9 Service invocation component**
|
| 217 |
+
|
| 218 |
+
A tariff component which is normally intended to cover the per event cost of activating a service, already subscribed to.
|
| 219 |
+
|
| 220 |
+
### **A.10 Full refund**
|
| 221 |
+
|
| 222 |
+
Reimbursement to the customer of the total charges paid to the Administration for the service/facility in question.
|
| 223 |
+
|
| 224 |
+
---
|
| 225 |
+
|
| 226 |
+
<sup>1</sup> Definition adopted by the World Administration Telegraph and Telephone Conference, Melbourne, 1988.
|
| 227 |
+
|
| 228 |
+
### **A.11 Partial refund**
|
| 229 |
+
|
| 230 |
+
Reimbursement to the customer of only part of the total charges paid to the Administration for the service/facility in question.
|
| 231 |
+
|
| 232 |
+
### **A.12 Relation**
|
| 233 |
+
|
| 234 |
+
Exchange of traffic between two terminal countries, always referring to a specific service if there is between their Administrations:
|
| 235 |
+
|
| 236 |
+
- a) a means for the exchange of traffic in that specific service either over direct circuits (direct relation), or via a point of transit in a third country (indirect relation), and
|
| 237 |
+
- b) normally, the settlement of accounts.
|
| 238 |
+
|
| 239 |
+
### **A.13 Origin country (or Administration)**
|
| 240 |
+
|
| 241 |
+
The country in which the traffic originates.
|
| 242 |
+
|
| 243 |
+
### **A.14 Destination country (or Administration)**
|
| 244 |
+
|
| 245 |
+
The country in which the traffic terminates.
|
| 246 |
+
|
| 247 |
+
### **A.15 Terminal country (or Administration)**
|
| 248 |
+
|
| 249 |
+
An origin country and a destination country in a given relation.
|
| 250 |
+
|
| 251 |
+
### **A.16 Transit country (or Administration)**
|
| 252 |
+
|
| 253 |
+
A country through which traffic is routed between two terminal countries.
|
| 254 |
+
|
| 255 |
+
#### **A.16.1 Direct-transit country**
|
| 256 |
+
|
| 257 |
+
A transit country through which traffic is routed on direct circuits, i.e., on circuits provided for the exclusive use of other countries.
|
| 258 |
+
|
| 259 |
+
#### **A.16.2 Switched-transit country**
|
| 260 |
+
|
| 261 |
+
A transit country through which traffic is routed by switching in an international transit exchange.
|
| 262 |
+
|
| 263 |
+
### **A.17 International circuit**
|
| 264 |
+
|
| 265 |
+
A circuit between two international exchanges situated in different countries.
|
| 266 |
+
|
| 267 |
+
#### **A.17.1 Continental circuit**
|
| 268 |
+
|
| 269 |
+
An international circuit between two international exchanges situated in two different countries in the same continent.
|
| 270 |
+
|
| 271 |
+
#### **A.17.2 Intercontinental circuit**
|
| 272 |
+
|
| 273 |
+
An international circuit between two international exchanges in different continents.
|
| 274 |
+
|
| 275 |
+
### **A.18 National extension**
|
| 276 |
+
|
| 277 |
+
The part of the connection which extends from the national side of the international exchange to the subscribers.
|
| 278 |
+
|
| 279 |
+
### **A.19 Remuneration for shared use and exclusive use**
|
| 280 |
+
|
| 281 |
+
#### **A.19.1 Remuneration for shared use of circuits and equipment**
|
| 282 |
+
|
| 283 |
+
The expression "remuneration for shared use" refers to the remuneration paid to the Administration of a country **P** which makes its facilities available to a number of Administrations of other countries $L_1, L_2, \dots, L_n$ for the routing of different international traffic streams. It may apply either to circuits or to switching equipment. Under the control of the owner Administration, the use of such facilities may be shared in any appropriate manner with other Administrations (including the Administration which owns them). The latter sets the price for the shared use of its facilities:
|
| 284 |
+
|
| 285 |
+
- a) either according to the number of traffic units;
|
| 286 |
+
- b) or by a fixed amount covering a certain period of time and based on the estimated volume of traffic and its time characteristics.
|
| 287 |
+
|
| 288 |
+
#### **A.19.2 Remuneration for exclusive use of circuits**
|
| 289 |
+
|
| 290 |
+
**A.19.2.1** The *remuneration for exclusive use* is the remuneration paid to the Administration of a country which makes its circuits available for direct transit, each circuit being assigned on an exclusive basis. The volume of traffic, its origin and its fluctuations in time are not the concern of the owner Administration and have no effect on the amount of the remuneration, which is paid circuit by circuit. The owner does not control the traffic routed over the circuit. This is the conventional lease arrangement between Administrations.
|
| 291 |
+
|
| 292 |
+
**A.19.2.2** For further clarification, it should be mentioned that:
|
| 293 |
+
|
| 294 |
+
- a) the general term "*lease*" (in French: *location*) used until now applies only to the case cited in clause A.19.2.1 above where exclusive use is granted;
|
| 295 |
+
- b) the term "*owner*" in these definitions refers to an Administration which receives the remuneration and which grants the rights to another Administration. The owner may have real ownership or the indefeasible right of use of the facilities.
|
| 296 |
+
|
| 297 |
+
### **A.20 Flat-rate price per circuit procedure**
|
| 298 |
+
|
| 299 |
+
The procedure which consists of remunerating an Administration on the basis of a flat-rate price per circuit.
|
| 300 |
+
|
| 301 |
+
### **A.21 Traffic-unit price procedure**
|
| 302 |
+
|
| 303 |
+
The procedure whereby remuneration of an Administration is based on traffic units.
|
| 304 |
+
|
| 305 |
+
### **A.22 Accounting revenue division procedure**
|
| 306 |
+
|
| 307 |
+
The procedure whereby accounting revenue is shared between terminal Administrations, and, as appropriate, between the Administrations of transit countries.
|
| 308 |
+
|
| 309 |
+
### **A.23 Accounting rate share**
|
| 310 |
+
|
| 311 |
+
The part of the accounting rate corresponding to the facilities made available in each country; this share is fixed by agreement among the Administrations.
|
| 312 |
+
|
| 313 |
+
### **A.24 Terminal share**
|
| 314 |
+
|
| 315 |
+
The part of the accounting rate which is due to a terminal Administration.
|
| 316 |
+
|
| 317 |
+
### **A.25 Transit share**
|
| 318 |
+
|
| 319 |
+
The part of the accounting rate which is due to an intermediate Administration whose territory, installations or circuits are used to route traffic between two terminal countries.
|
| 320 |
+
|
| 321 |
+
### **A.26 Per word tariff system**
|
| 322 |
+
|
| 323 |
+
In the per word tariff system, rates are established per word purely and simply, the word-counting provisions of the relevant ITU-T Recommendations being applied. A minimum rate per telegram corresponding to the rate for a certain number of words is applied.
|
| 324 |
+
|
| 325 |
+
In the per word tariff system, the accounting rate is the rate per word purely and simply of an ordinary private telegram without any special system.
|
| 326 |
+
|
| 327 |
+
### **A.27 Binary tariff system**
|
| 328 |
+
|
| 329 |
+
The binary tariff system has two components:
|
| 330 |
+
|
| 331 |
+
- a) a fixed component representing the costs involved in the acceptance and delivery of a telegram (fixed charge); and
|
| 332 |
+
- b) a component proportional to the length of the telegram representing the costs involved in transmitting and receiving the telegram and the cost of using the telegraph network (charge per word).
|
| 333 |
+
|
| 334 |
+
In this binary tariff system, the accounting rate has the two components described in a) and b) above. No minimum rate for a certain number of words is applied.
|
| 335 |
+
|
| 336 |
+
### **A.28 Non-discrimination**
|
| 337 |
+
|
| 338 |
+
The application of no less favourable treatment to any service or service provider than that accorded to other like services or service providers in similar conditions.
|
| 339 |
+
|
| 340 |
+
### **A.29 Transparency**
|
| 341 |
+
|
| 342 |
+
The publication of all administrative measures of general application affecting access to or operation of the telecommunication market, including:
|
| 343 |
+
|
| 344 |
+
- tariffs and other terms and conditions of service;
|
| 345 |
+
- specifications of technical interfaces with such networks and services;
|
| 346 |
+
- information on bodies responsible for the preparation and adoption of standards affecting such access and use;
|
| 347 |
+
- conditions applying to attachment of terminals or other equipment;
|
| 348 |
+
- notifications, registrations or licensing requirements, if any.
|
| 349 |
+
|
| 350 |
+
### **A.30 Cost oriented**
|
| 351 |
+
|
| 352 |
+
Cost oriented corresponds to the use of a cost structure to determine the cost necessary to provide a particular service.
|
| 353 |
+
|
| 354 |
+
### **A.31 Hub**
|
| 355 |
+
|
| 356 |
+
A transit centre (or network operator) that offers to other operators a telecommunication traffic termination service to nominated destinations contained in the offer.
|
| 357 |
+
|
| 358 |
+
### **A.32 Hubbing**
|
| 359 |
+
|
| 360 |
+
The routing of telecommunication traffic in *hubbing* mode consists in the use of *hub* facilities to terminate telecommunication traffic to other destinations, with full payment due to the *hub*.
|
| 361 |
+
|
| 362 |
+
|
| 363 |
+
|
| 364 |
+
|
| 365 |
+
|
| 366 |
+
# SERIES OF ITU-T RECOMMENDATIONS
|
| 367 |
+
|
| 368 |
+
| | |
|
| 369 |
+
|-----------------|---------------------------------------------------------------------------------------------|
|
| 370 |
+
| Series A | Organization of the work of ITU-T |
|
| 371 |
+
| <b>Series D</b> | <b>General tariff principles</b> |
|
| 372 |
+
| Series E | Overall network operation, telephone service, service operation and human factors |
|
| 373 |
+
| Series F | Non-telephone telecommunication services |
|
| 374 |
+
| Series G | Transmission systems and media, digital systems and networks |
|
| 375 |
+
| Series H | Audiovisual and multimedia systems |
|
| 376 |
+
| Series I | Integrated services digital network |
|
| 377 |
+
| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
|
| 378 |
+
| Series K | Protection against interference |
|
| 379 |
+
| Series L | Construction, installation and protection of cables and other elements of outside plant |
|
| 380 |
+
| Series M | Telecommunication management, including TMN and network maintenance |
|
| 381 |
+
| Series N | Maintenance: international sound programme and television transmission circuits |
|
| 382 |
+
| Series O | Specifications of measuring equipment |
|
| 383 |
+
| Series P | Terminals and subjective and objective assessment methods |
|
| 384 |
+
| Series Q | Switching and signalling |
|
| 385 |
+
| Series R | Telegraph transmission |
|
| 386 |
+
| Series S | Telegraph services terminal equipment |
|
| 387 |
+
| Series T | Terminals for telematic services |
|
| 388 |
+
| Series U | Telegraph switching |
|
| 389 |
+
| Series V | Data communication over the telephone network |
|
| 390 |
+
| Series X | Data networks, open system communications and security |
|
| 391 |
+
| Series Y | Global information infrastructure, Internet protocol aspects and next-generation networks |
|
| 392 |
+
| Series Z | Languages and general software aspects for telecommunication systems |
|
marked/D/T-REC-D.1-199107-I_PDF-E/553900e5cb3b1da13d48f54237cf0e50_img.jpg
ADDED
|
Git LFS Details
|
marked/D/T-REC-D.1-199107-I_PDF-E/edf4fa59aa5565f6d9a0e80d23537961_img.jpg
ADDED
|
Git LFS Details
|
marked/D/T-REC-D.1-199107-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,289 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
|
| 4 |
+
|
| 5 |
+
ITU logo: a globe with a lightning bolt and the letters ITU inside.
|
| 6 |
+
|
| 7 |
+
INTERNATIONAL TELECOMMUNICATION UNION
|
| 8 |
+
|
| 9 |
+
# CCITT
|
| 10 |
+
|
| 11 |
+
## D.1
|
| 12 |
+
|
| 13 |
+
THE INTERNATIONAL
|
| 14 |
+
TELEGRAPH AND TELEPHONE
|
| 15 |
+
CONSULTATIVE COMMITTEE
|
| 16 |
+
|
| 17 |
+
# **GENERAL TARIFF PRINCIPLES CHARGING AND ACCOUNTING IN INTERNATIONAL TELECOMMUNICATIONS SERVICES** ---
|
| 18 |
+
|
| 19 |
+
## **GENERAL PRINCIPLES FOR THE LEASE OF INTERNATIONAL (CONTINENTAL AND INTERCONTINENTAL) PRIVATE TELECOMMUNICATION CIRCUITS AND NETWORKS**
|
| 20 |
+
|
| 21 |
+
### **Recommendation D.1** ---
|
| 22 |
+
|
| 23 |
+
Geneva, 1991
|
| 24 |
+
|
| 25 |
+
## FOREWORD
|
| 26 |
+
|
| 27 |
+
The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 28 |
+
|
| 29 |
+
The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
|
| 30 |
+
|
| 31 |
+
Recommendation D.1 was prepared by Study Group III and was approved under the Resolution No. 2 procedure on the 15th of July 1991.
|
| 32 |
+
|
| 33 |
+
## --- CCITT NOTE
|
| 34 |
+
|
| 35 |
+
In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
|
| 36 |
+
|
| 37 |
+
© ITU 1991
|
| 38 |
+
|
| 39 |
+
All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
|
| 40 |
+
|
| 41 |
+
### Recommendation D.1
|
| 42 |
+
|
| 43 |
+
## GENERAL PRINCIPLES FOR THE LEASE OF INTERNATIONAL (CONTINENTAL AND INTERCONTINENTAL) PRIVATE TELECOMMUNICATION CIRCUITS AND NETWORKS
|
| 44 |
+
|
| 45 |
+
*(revised 1991)*
|
| 46 |
+
|
| 47 |
+
### Preamble
|
| 48 |
+
|
| 49 |
+
This Recommendation sets out the general principles and conditions applicable to international (continental and intercontinental) private leased telecommunication circuits and networks, taking into account opportunities available to Administrations, or other organizations or persons to enter into special arrangements, subject to national laws<sup>1)</sup>, for the establishment, operations, and use of international private leased telecommunication circuits. The diagram included as Annex A to this Recommendation, extracted from Recommendation M.1010 [1] relating to the constitution and nomenclature of international private leased telecommunication circuits and supplemented for tariff requirements, indicates what is to be understood by the terms international private leased telecommunication circuits and national extensions.
|
| 50 |
+
|
| 51 |
+
### 1 General principles
|
| 52 |
+
|
| 53 |
+
1.1 The international private leased telecommunication circuit service consists of making dedicated international telecommunication circuits available to a customer<sup>2)</sup> for use on the terms and conditions which may be set out in a lease agreement between the customer and the Administration of the country at each end of the circuit. Customers may also combine a series of such circuits to establish international private leased telecommunication circuit networks.
|
| 54 |
+
|
| 55 |
+
1.2 In providing an international private leased telecommunication circuit service, account should be taken of:
|
| 56 |
+
|
| 57 |
+
- a) national laws;
|
| 58 |
+
- b) the provisions of this Recommendation;
|
| 59 |
+
- c) such other terms and conditions as may be mutually agreed upon between the Administrations participating in the provision of the particular service arrangement;
|
| 60 |
+
- d) the desirability of facilitating the advance of technology and the use of modern methods of operation and management;
|
| 61 |
+
- e) the need to meet the long-term and specific requirements of customers.
|
| 62 |
+
|
| 63 |
+
1.3 When an Administration or one of its subsidiaries provides a telecommunication service that may also be provided by others under its national laws, Members should ensure that the Administration or its subsidiary does not enjoy unfair advantage over other international private leased telecommunication circuit customers offering the same type of service.
|
| 64 |
+
|
| 65 |
+
1.4 When international private leased telecommunication circuits and networks are used to provide telecommunication services to the public, the Member concerned shall, as appropriate, encourage the application of relevant CCITT Recommendations.
|
| 66 |
+
|
| 67 |
+
---
|
| 68 |
+
|
| 69 |
+
<sup>1)</sup> National laws include national regulations.
|
| 70 |
+
|
| 71 |
+
<sup>2)</sup> The customer is the individual or entity who, or which, leases an international private leased telecommunication circuit from an Administration and is responsible for payment of all charges and rentals due.
|
| 72 |
+
|
| 73 |
+
1.5 The international private leased telecommunication circuit service is important in international relations and Administrations should recognize the requirements for international private leased telecommunication circuits in their planning.
|
| 74 |
+
|
| 75 |
+
### **2 Conditions of lease**
|
| 76 |
+
|
| 77 |
+
2.1 The customer using an international private leased telecommunication circuit or establishing an international private leased telecommunication circuit network may be requested by the Administrations concerned to provide technical information as required to prevent technical harm to the public network or to network personnel or information of a kind that will assist the Administration in providing the customer with a more timely and efficient service.
|
| 78 |
+
|
| 79 |
+
2.2 Recognizing the requirements of preventing technical harm to the network and protecting the safety of network personnel, equipment connected to an international private leased telecommunication circuit must meet the technical conditions laid down by each of the Administrations concerned. Administrations should consult with each other whenever consultation would assist in expediting type-approval of such apparatus and equipment.
|
| 80 |
+
|
| 81 |
+
2.3 When an international private leased telecommunication circuit or international private leased telecommunication circuit network has been established, the connection between the terminal stations is set up for the period of the lease in such a way that the international centres at the ends of the international private leased telecommunication circuit or international private leased telecommunication circuit network do not need to intervene. However, arrangements must be such as to enable the appropriate staff at these centres to perform necessary supervision and maintenance.
|
| 82 |
+
|
| 83 |
+
2.4 Administrations are not obliged to accept any responsibility for the end-to-end quality of transmission over connected circuits which comprise an international private leased telecommunication circuit network. Administrations which otherwise accept responsibility for the quality of transmission over connected circuits which comprise an international private leased telecommunication circuit network need not do so for portions of the network which they do not provide or which are not operated within the applicable technical requirements for such connected use.
|
| 84 |
+
|
| 85 |
+
2.5 Administrations may temporarily withdraw an international private leased telecommunication circuit from operation in order to perform such tests, adjustments and routine maintenance as is necessary to ensure that the circuit is kept in proper working condition. Administrations shall endeavour to make such a withdrawal only after consultation with the customer and at a time mutually agreeable to all parties.
|
| 86 |
+
|
| 87 |
+
2.6 Under extraordinary circumstances (for example, because of force majeure or threat of imminent technical harm from the continued operation of the international private leased telecommunication circuit involved), Administrations may temporarily withdraw an international private leased telecommunication circuit if this is required in the public interest. Under such conditions, withdrawal should be made with as much notice as feasible under the circumstances and restored in the shortest practicable time.
|
| 88 |
+
|
| 89 |
+
2.7 Administrations shall take all steps, appropriate in the circumstances, to ensure that the provisions governing the lease of international private leased telecommunication circuits are respected.
|
| 90 |
+
|
| 91 |
+
2.8 In the event of a violation of these provisions, Administrations reserve the right to cancel the lease of the international private leased telecommunication circuit concerned; they must, however, give the customer immediate and adequate notice of their intention to take such action and sufficient opportunity to respond thereto.
|
| 92 |
+
|
| 93 |
+
2.9 In the event that questions arise concerning the applicability or interpretation of the provisions herein, the Administration shall confer with the customer to seek a mutually acceptable solution.
|
| 94 |
+
|
| 95 |
+
### **3 Conditions of use**
|
| 96 |
+
|
| 97 |
+
3.1 Subject to national laws, the customer may:
|
| 98 |
+
|
| 99 |
+
3.1.1 Subdivide an international private leased telecommunication circuit into telecommunication channels. These channels, or some of them, may be extended by means of other circuits leased by the same customer;
|
| 100 |
+
|
| 101 |
+
3.1.2 Sublease;
|
| 102 |
+
|
| 103 |
+
3.1.3 Provide international telecommunication services using an international private leased telecommunication circuit or an international private leased telecommunication circuit network. Members of the ITU reserve the right to designate certain telecommunication services<sup>3)</sup> for special or exclusive provision by specified entities or to submit them to special authorizing conditions.
|
| 104 |
+
|
| 105 |
+
3.2 Customers should notify Administrations if they plan substantial changes in the configuration or technical specifications of their international private leased telecommunication circuit network.
|
| 106 |
+
|
| 107 |
+
3.3 Communications between customers and users<sup>4)</sup> and amongst users via international private leased telecommunication circuits may be allowed by Administrations subject to conditions provided for in national laws applied in the countries concerned.
|
| 108 |
+
|
| 109 |
+
### **4 Access to public networks**
|
| 110 |
+
|
| 111 |
+
4.1 The interconnection of an international private leased telecommunication circuit or international private leased telecommunication circuit networks with public networks at only one end of the circuit or the network should be permitted subject to national laws.
|
| 112 |
+
|
| 113 |
+
The interconnection of an international private leased telecommunication circuit or international private leased telecommunication circuit networks with public networks may be permitted simultaneously at both ends of the circuit or the network if agreed between the Members concerned in conformity with their national laws to be applied regarding the exclusive provision of certain services. Such interconnection should in principle be made on the customer's premises.
|
| 114 |
+
|
| 115 |
+
4.2 Administrations are not obliged to guarantee the quality of the transmission of calls to or from users on the public network over an international private leased telecommunication circuit.
|
| 116 |
+
|
| 117 |
+
### **5 Duration of the lease, charging, cancellation**
|
| 118 |
+
|
| 119 |
+
5.1 Except as provided in § 5.5 below for temporary services, the lease shall last for a minimum of one month.
|
| 120 |
+
|
| 121 |
+
5.2 The lease shall be continued thereafter by tacit agreement until cancelled by either party. Notice of cancellation should normally be given seven days in advance of the effective date of cancellation. However, an Administration and a customer may agree on a different period of notice. The charges for fractional parts of a month beyond the first month should be in accordance with §§ 5.4.1 and 5.4.2 below.
|
| 122 |
+
|
| 123 |
+
---
|
| 124 |
+
|
| 125 |
+
<sup>3)</sup> In particular the public telephone service.
|
| 126 |
+
|
| 127 |
+
<sup>4)</sup> The user is the individual or entity designated by the customer, individually or by class, as having access to the international private leased telecommunication circuit.
|
| 128 |
+
|
| 129 |
+
5.3 The lease should normally be payable one month in advance.
|
| 130 |
+
|
| 131 |
+
5.4 In calculating the duration of the lease, one month shall mean one calendar month. Moreover, the day on which the circuit is made available for service to the customer, shall not be reckoned. The day on which the circuit is withdrawn shall be reckoned as a full day. However, in cases where customer provided equipment is necessary for operation of the circuit and the customer equipment is not ready for use, Administrations should take into consideration particular circumstances in determining the date of start of service. Thus, a period of lease covering one month or more is calculated as follows:
|
| 132 |
+
|
| 133 |
+
- a) count the number of days beginning on the following day on which the circuit was made available until the end of the month;
|
| 134 |
+
- b) thereafter count the number of full calendar months, if any; and
|
| 135 |
+
- c) count the number of service days in the last month, including the day on which the circuit was withdrawn.
|
| 136 |
+
|
| 137 |
+
5.4.1 As regards charging:
|
| 138 |
+
|
| 139 |
+
- full calendar months are subject to the monthly rental;
|
| 140 |
+
- fractions of a month shall be subject to a daily charge equal to 1/30th of the monthly rental.
|
| 141 |
+
|
| 142 |
+
5.4.2 Examples: see Table 1/D.1.
|
| 143 |
+
|
| 144 |
+
TABLE 1/D.1
|
| 145 |
+
|
| 146 |
+
| Life of a lease from<br>the day of availability until<br>the day of withdrawal | Chargeable time | Charge |
|
| 147 |
+
|-------------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------------------------|
|
| 148 |
+
| 30 October-15 December<br>30 October not counted<br>31 October = 1 day<br>November = 1 month<br>1-15 December = 15 days | 1 month 16 days | 1 monthly rental + 16/30th<br>of this rental |
|
| 149 |
+
| 30 November-15 January<br>30 October not counted<br>December = 1 month<br>1-15 January = 15 days | 1 month 15 days | 1 monthly rental + 15/30th<br>of this rental |
|
| 150 |
+
| 4 January-10 February<br>4 January not counted<br>5 January-31 January = 27 days<br>1 February-10 February = 10 days | 37 days | 37/30th of monthly rental |
|
| 151 |
+
|
| 152 |
+
5.5 A temporary lease service may be granted for a period of less than one month.
|
| 153 |
+
|
| 154 |
+
5.5.1 In calculating the life of a temporary lease, one day shall mean a period of 24 consecutive hours.
|
| 155 |
+
|
| 156 |
+
The life of a lease should be calculated in multiples of 24 hours, the period starting from the time at which the circuit is made available until the time at which it is withdrawn. If the number of days thus obtained contains a fraction of 24 hours, it should be rounded up to the next whole number.
|
| 157 |
+
|
| 158 |
+
*Examples:*
|
| 159 |
+
|
| 160 |
+
Circuit made available on 1 June at 09.00 hours, cleared on 5 June at 09.00 hours:
|
| 161 |
+
|
| 162 |
+
$4 \times 24$ hours, i.e. 4 chargeable days.
|
| 163 |
+
|
| 164 |
+
Circuit made available on 1 June at 09.00 hours, cleared on 5 June at 11.00 hours:
|
| 165 |
+
|
| 166 |
+
(4 days + 2/24 days), i.e. 5 chargeable days.
|
| 167 |
+
|
| 168 |
+
5.5.2 In this case (temporary lease), the charges shall be calculated as follows:
|
| 169 |
+
|
| 170 |
+
- a) for the first day of lease: 20% of the monthly rental;
|
| 171 |
+
- b) for each subsequent day from the second day: 3.33% (1/30) of the monthly rental, the total amount per month paid by the customer in no case being more than the monthly rental.
|
| 172 |
+
|
| 173 |
+
5.6 The leases considered in §§ 5.1 and 5.5 above are full-time leases, i.e. for 24 hours per day.
|
| 174 |
+
|
| 175 |
+
However, the Administrations concerned may in some cases permit part-time leases.
|
| 176 |
+
|
| 177 |
+
### **6 Charging principles**
|
| 178 |
+
|
| 179 |
+
6.1 Charges for international private leased telecommunication circuits are recognized as a national matter of the country at each end of the circuit. However, charges levied for international private leased telecommunication circuits should generally be cost-oriented and established on a flat-rate basis.
|
| 180 |
+
|
| 181 |
+
6.2 The charging in the terminal countries for the national extensions of an international private leased telecommunication circuit is subject to any regulations that may be applied by the Administrations of those countries.
|
| 182 |
+
|
| 183 |
+
6.3 When an international private leased telecommunication circuit is connected to public networks, in addition to the private leased circuit charges, the Administration may levy the normal charge for the use of the public network service. If interconnection to public networks by international private leased telecommunication circuits gives rise to additional costs for the Administration concerned, an additional cost-related charge may be levied.
|
| 184 |
+
|
| 185 |
+
6.4 When the international private leased telecommunication circuit does not pass through a transit country, two methods are generally recognized:
|
| 186 |
+
|
| 187 |
+
6.4.1 Each Administration of the two terminal countries collects its own share of the international private leased telecommunication circuit rental from the customer resident in its own country.
|
| 188 |
+
|
| 189 |
+
6.4.2 Subject to mutual agreement by Administrations concerned, either terminal Administration may collect the rental for the international private leased telecommunication circuit; in this case, the collecting Administration credits the other terminal Administration through the international accounts with the share due to it.
|
| 190 |
+
|
| 191 |
+
6.5 An international private leased telecommunication circuit transiting one or more countries shall be charged for as if it were one circuit, if no intermediate station exists in any transit country to which a customer or user may have access. If, however, a customer or user station is connected to the circuit in any transit country, normally the circuit shall be divided into separate sections for charging purposes, each station being charged for as a separate circuit. Exceptionally, Administrations may agree among themselves to apply a different basis of charging taking into account the provisions of § 6.6 below.
|
| 192 |
+
|
| 193 |
+
6.6 If the international private leased telecommunication circuit passes through one or more transit countries, the terminal Administrations shall agree with the transit Administration(s) on the method to be adopted for collecting and international accounting of the charges due to it (them).
|
| 194 |
+
|
| 195 |
+
6.7 When leasing a series of circuits forming an international private leased telecommunication circuit network, the terminal and transit Administrations involved may agree upon an equitable division of revenues for the international private leased telecommunication circuits and should endeavour to grant the best possible charging conditions to the customer.
|
| 196 |
+
|
| 197 |
+
### **7 Additional charge for special routings**
|
| 198 |
+
|
| 199 |
+
If a customer requests the Administrations to provide an international private leased telecommunication circuit by means of a specific routing other than that planned by them, these Administrations may levy an additional charge which takes into consideration the additional costs involved. An additional charge would be applicable where the request was made for diversity or security reasons, but not where an existing international private leased telecommunication circuit fails to meet specifications according to relevant CCITT Recommendations.
|
| 200 |
+
|
| 201 |
+
### **8 Allowances for interruptions**
|
| 202 |
+
|
| 203 |
+
8.1 In the event of an interruption of an international private leased telecommunication circuit for which a customer or user is not responsible, an allowance shall normally be made to the customer if there has been an initial period of interruption of:
|
| 204 |
+
|
| 205 |
+
- a continental circuit for not less than 180 consecutive minutes<sup>5)</sup>, <sup>6)</sup>;
|
| 206 |
+
- an intercontinental circuit for not less than 60 consecutive minutes<sup>6)</sup>.
|
| 207 |
+
- a) Any interruption or operating trouble shall be promptly reported by the customer or user. However, in cases of facility failures known to the Administration such reports may not be required.
|
| 208 |
+
- b) Any requirement that customers specifically request allowances should be in accordance with the practices of each Administration concerned.
|
| 209 |
+
- c) For the calculation of the allowance, the reporting time shall normally be the starting time for the duration of the interruption. If, however, a report is not required because the facility failure is known to the Administration, the time of the failure is taken as starting time for calculating the allowance.
|
| 210 |
+
|
| 211 |
+
8.2 For each hour of the initial period of interruption mentioned in § 8.1 above and for each subsequent consecutive hourly period or fraction of at least 30 minutes, the amount of the allowance should be equivalent to 1/24th of a day's rental for a full-time circuit.
|
| 212 |
+
|
| 213 |
+
In the case of international private leased telecommunication circuits leased on a part-time basis as described in § 5.6 above, the allowance for interruption shall be *pro rata* to the number of hours of the lease per day.
|
| 214 |
+
|
| 215 |
+
---
|
| 216 |
+
|
| 217 |
+
<sup>5)</sup> In cases where the rental charges for continental circuits are roughly at the same level as charges for intercontinental circuits, Administrations may apply the initial time limit of 60 minutes in determining the interruption periods on continental circuits for which an allowance should be made.
|
| 218 |
+
|
| 219 |
+
<sup>6)</sup> As far as digital leased circuits are concerned, the Administrations may apply initial periods of interruption lower than those under § 8 for the determination of the allowances for interruption of such circuit, to be made to the customer.
|
| 220 |
+
|
| 221 |
+
8.3 For the purpose of computing allowances for interruptions, a month is considered to be 30 days. When the lease is for less than one month, the charge for a day's lease shall be calculated by dividing the total rental by the number of days reckoned in the lease.
|
| 222 |
+
|
| 223 |
+
8.4 Administrations need not consider requests for allowances for interruptions resulting from unfavourable propagation conditions on HF radio circuits.
|
| 224 |
+
|
| 225 |
+
8.5 In principle, an allowance should be given for all components of the through international private leased telecommunication circuit between the customers' operating terminals regardless of where the interruption occurs, except as provided for in § 8.7 below. Where the interrupted circuit forms part of an international private leased telecommunication circuit network, the allowances would apply only to the affected circuit.
|
| 226 |
+
|
| 227 |
+
*Note* – It is recognized that some Administrations are in a position to make allowances only in respect of failures in the intercontinental portion of international private leased telecommunication circuits.
|
| 228 |
+
|
| 229 |
+
8.6 Requests for refund of charges for the use of public telecommunication services during the period when the international private leased telecommunication circuit is not available shall not be considered.
|
| 230 |
+
|
| 231 |
+
8.7 No allowance shall be granted when an interruption (regardless of its duration) or non-operation of the international private leased telecommunication circuit, is due to the negligence of the customer or to a fault of equipment provided by the customer or user for which the Administration is not responsible.
|
| 232 |
+
|
| 233 |
+
8.8 Normally, no allowance shall be granted when an international private leased telecommunication circuit is withdrawn in order for Administrations to perform tests, adjustments and routine maintenance as provided in § 2.5 above.
|
| 234 |
+
|
| 235 |
+
8.9 Administrations will not consider requests for interruption allowances for non-operation of an international private leased telecommunication circuit or international private leased telecommunication circuit network resulting from failures in public network facilities to which the international private leased telecommunication circuit has access.
|
| 236 |
+
|
| 237 |
+
## **ANNEX A** **(to Recommendation D.1)**
|
| 238 |
+
|
| 239 |
+
|
| 240 |
+
|
| 241 |
+
International private leased telecommunication circuit network
|
| 242 |
+
|
| 243 |
+
International link
|
| 244 |
+
|
| 245 |
+
National extension
|
| 246 |
+
|
| 247 |
+
Terminal national section
|
| 248 |
+
|
| 249 |
+
National line
|
| 250 |
+
(composed of one or more circuit sections)
|
| 251 |
+
|
| 252 |
+
International line
|
| 253 |
+
(composed of one or more circuit sections)
|
| 254 |
+
|
| 255 |
+
National line
|
| 256 |
+
(composed of one or more circuit sections)
|
| 257 |
+
|
| 258 |
+
Terminal national section
|
| 259 |
+
|
| 260 |
+
Customer's or user's premises
|
| 261 |
+
|
| 262 |
+
Terminal national centre
|
| 263 |
+
|
| 264 |
+
Terminal international centre
|
| 265 |
+
|
| 266 |
+
Terminal international centre
|
| 267 |
+
|
| 268 |
+
Terminal national centre
|
| 269 |
+
|
| 270 |
+
Customer's or user's premises
|
| 271 |
+
|
| 272 |
+
○ Circuit test points
|
| 273 |
+
|
| 274 |
+
Customer's or user's installation
|
| 275 |
+
|
| 276 |
+
● Junction point of the international private leased telecommunication circuit network and the customer's or user's installation
|
| 277 |
+
|
| 278 |
+
T0300890-92
|
| 279 |
+
|
| 280 |
+
Diagram illustrating the constitution of international private telecommunication circuits. The diagram shows a sequence of components: Customer's or user's premises, Terminal national centre, Terminal international centre, and another Terminal national centre, followed by another Customer's or user's premises. The circuit is divided into sections: National extension, National line (composed of one or more circuit sections), International link, and another National extension. The International link is further divided into two National lines. The diagram also includes a legend for circuit test points and junction points, and a reference to T0300890-92.
|
| 281 |
+
|
| 282 |
+
*Note* – Figure taken from Recommendation M.1010 [1], with the addition of the term *national extension* for purposes of charging.
|
| 283 |
+
|
| 284 |
+
FIGURE A-1/D.1
|
| 285 |
+
**Constitution of international private telecommunication circuits**
|
| 286 |
+
|
| 287 |
+
### **Reference**
|
| 288 |
+
|
| 289 |
+
- [1] CCITT Recommendation *Constitution and nomenclature of international leased circuits*, Rec. M.1010.
|
marked/D/T-REC-D.10-199107-I_PDF-E/8e273781c276cb5fc030cc0acb12ad61_img.jpg
ADDED
|
Git LFS Details
|
marked/D/T-REC-D.10-199107-I_PDF-E/b0616bc7ab22530cad12687ef443d846_img.jpg
ADDED
|
Git LFS Details
|
marked/D/T-REC-D.10-199107-I_PDF-E/raw.md
ADDED
|
@@ -0,0 +1,139 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
|
| 2 |
+
|
| 3 |
+
|
| 4 |
+
|
| 5 |
+
ITU logo: a globe with the letters ITU inside.
|
| 6 |
+
|
| 7 |
+
INTERNATIONAL TELECOMMUNICATION UNION
|
| 8 |
+
|
| 9 |
+
# CCITT
|
| 10 |
+
|
| 11 |
+
## D.10
|
| 12 |
+
|
| 13 |
+
THE INTERNATIONAL
|
| 14 |
+
TELEGRAPH AND TELEPHONE
|
| 15 |
+
CONSULTATIVE COMMITTEE
|
| 16 |
+
|
| 17 |
+
# **GENERAL TARIFF PRINCIPLES CHARGING AND ACCOUNTING IN INTERNATIONAL TELECOMMUNICATIONS SERVICES** ---
|
| 18 |
+
|
| 19 |
+
# **GENERAL TARIFF PRINCIPLES FOR INTERNATIONAL PUBLIC DATA COMMUNICATION SERVICES**
|
| 20 |
+
|
| 21 |
+
**Recommendation D.10**
|
| 22 |
+
|
| 23 |
+
---
|
| 24 |
+
|
| 25 |
+
|
| 26 |
+
|
| 27 |
+
CCITT logo: a globe with the letters CCITT inside.
|
| 28 |
+
|
| 29 |
+
Geneva, 1991
|
| 30 |
+
|
| 31 |
+
## FOREWORD
|
| 32 |
+
|
| 33 |
+
The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
|
| 34 |
+
|
| 35 |
+
The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988).
|
| 36 |
+
|
| 37 |
+
Recommendation D.10 was prepared by Study Group III and was approved under the Resolution No. 2 procedure on the 15th of July 1991.
|
| 38 |
+
|
| 39 |
+
## --- CCITT NOTE
|
| 40 |
+
|
| 41 |
+
In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency.
|
| 42 |
+
|
| 43 |
+
## Recommendation D.10
|
| 44 |
+
|
| 45 |
+
© ITU 1991
|
| 46 |
+
|
| 47 |
+
All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
|
| 48 |
+
|
| 49 |
+
# GENERAL TARIFF PRINCIPLES FOR INTERNATIONAL PUBLIC DATA COMMUNICATION SERVICES
|
| 50 |
+
|
| 51 |
+
(revised 1991)
|
| 52 |
+
|
| 53 |
+
## Preamble
|
| 54 |
+
|
| 55 |
+
This Recommendation sets out the general principles and conditions applicable by Administrations to data communication services over international public networks dedicated to this type of communication. It is recognized that this is a rapidly developing field at the present time in terms of the diversity of application and flexibility is therefore essential.
|
| 56 |
+
|
| 57 |
+
The tariff principles contained in this Recommendation do not apply to leased circuits for private use (see Recommendation D.1).
|
| 58 |
+
|
| 59 |
+
## 1 General
|
| 60 |
+
|
| 61 |
+
1.1 A public data communication service is a data communication service established and operated by an Administration by means of a public data network dedicated to this type of communication.
|
| 62 |
+
|
| 63 |
+
## 2 Charging
|
| 64 |
+
|
| 65 |
+
### 2.1 *General principles*
|
| 66 |
+
|
| 67 |
+
2.1.1 Tariffs developed for public data communication service should:
|
| 68 |
+
|
| 69 |
+
- take into account the provisions of Recommendation D.5;
|
| 70 |
+
- take into account tariff relationships with other services provided by the Administrations;
|
| 71 |
+
- be flexible enough to enable new needs to be accommodated as the service develops;
|
| 72 |
+
- be as administratively simple as possible;
|
| 73 |
+
- take into account the geographical configuration of countries;
|
| 74 |
+
- not impart undue advantage or disadvantage to any category of user;
|
| 75 |
+
- encourage customer choice depending upon his needs as to the use of circuit or packet-switched services where the alternative exists;
|
| 76 |
+
- be such as to encourage the use of public data network, meet the needs of as many users as possible, and promote optimum growth and utilization of the network;
|
| 77 |
+
- be easily understood by subscribers;
|
| 78 |
+
- sustain the service on a long-term basis.
|
| 79 |
+
|
| 80 |
+
2.1.2 Each Administration shall, subject to the applicable national law, establish the charges to be collected from its customers. The level of the charges is a national matter; however, in establishing these charges, Administrations should try to avoid too great a dissymmetry between the charges applicable in each direction of the same relation.
|
| 81 |
+
|
| 82 |
+
### 2.2 *Tariff components*
|
| 83 |
+
|
| 84 |
+
2.2.1 The tariff should normally consist of two components: the network access component and the network utilization component.
|
| 85 |
+
|
| 86 |
+
2.2.2 The network access component, normally intended to cover the cost of making the service available, represents the cost of the service which is not dependent on network utilization.
|
| 87 |
+
|
| 88 |
+
2.2.3 The network utilization component normally covers the costs which are dependent on network utilization.
|
| 89 |
+
|
| 90 |
+
2.2.4 Some factors which may be taken into account in developing tariffs include, for example:
|
| 91 |
+
|
| 92 |
+
- user class of service (see Recommendation X.1 [1]);
|
| 93 |
+
- optional user facilities (see Recommendation X.2 [2]);
|
| 94 |
+
- type of switching;
|
| 95 |
+
- volume of data and/or duration of call;
|
| 96 |
+
- distance;
|
| 97 |
+
- time (peak and off-peak periods);
|
| 98 |
+
- route;
|
| 99 |
+
- other functions.
|
| 100 |
+
|
| 101 |
+
While certain of the above factors may be more closely associated with one component or another, some may be associated with both. The particular application of some factors will depend on the type of switching employed.
|
| 102 |
+
|
| 103 |
+
## **3 Accounting**
|
| 104 |
+
|
| 105 |
+
3.1 Administrations should, by agreement, establish the overall accounting rate applicable in a given relation and divide that rate into terminal shares payable to the Administrations of the terminal countries and, where appropriate, into transit shares payable to the transit Administration(s). The same accounting rate should apply in both directions of a given relation. The overall accounting rate between two terminal countries should be the same irrespective of the route used.
|
| 106 |
+
|
| 107 |
+
3.2 Normally only the network utilization component should be considered for international accounts.
|
| 108 |
+
|
| 109 |
+
3.3 The gathering of information required for charging and accounting should normally be the responsibility of the calling Administration. Additionally, if the interconnection of dissimilar networks occurs at the called Administration, then the latter should be responsible for providing the calling Administration with the necessary data for charging and accounting.
|
| 110 |
+
|
| 111 |
+
## **4 Interworking of public data communication services**
|
| 112 |
+
|
| 113 |
+
4.1 Normally, the interconnection of dissimilar data networks (such as packet-to-circuit) should take place at the originating or terminating country Administration. However, conversion at a transit point may be provided if the originating, terminating and transit country Administrations agree.
|
| 114 |
+
|
| 115 |
+
4.2 In the cases where interworking is permitted, it is recommended that preference be given to the interworking alternatives which provide for the use of data circuits between international data communication centres (gateways).
|
| 116 |
+
|
| 117 |
+
4.3 Interconnection of a public data network with a public telephone/telex network in a transit country should be avoided.
|
| 118 |
+
|
| 119 |
+
4.4 Tariff principles in the case of interworking between dissimilar data networks shall be as follows:
|
| 120 |
+
|
| 121 |
+
#### **4.4.1 Collection charges**
|
| 122 |
+
|
| 123 |
+
4.4.1.1 The charge shall be, according to the policy of the origin Administration, either:
|
| 124 |
+
|
| 125 |
+
- a) the international charge applicable to the originating network, or
|
| 126 |
+
- b) the charge for the international network used.
|
| 127 |
+
|
| 128 |
+
4.4.1.2 Where appropriate, charges may also be levied for additional facilities used in the country of origin, e.g. for the access network to, and/or the use of, a network interworking facility.
|
| 129 |
+
|
| 130 |
+
#### 4.4.2 *Accounting*
|
| 131 |
+
|
| 132 |
+
International accounting should be based on the accounting rate for the international network used, irrespective of the collection charges applied.
|
| 133 |
+
|
| 134 |
+
*Note* – The desirability and possibility of adjusting the accounting rates to include the cost of providing interworking facilities used for international data traffic needs further study in consultation with Study Group I and other relevant Study Groups.
|
| 135 |
+
|
| 136 |
+
## **References**
|
| 137 |
+
|
| 138 |
+
- [1] CCITT Recommendation *International user classes of service in public data networks and integrated services digital networks (ISDNs)*, Rec. X.1.
|
| 139 |
+
- [2] CCITT Recommendation *International data transmission services and optional user facilities in public data networks and ISDNs*, Rec. X.2.
|