May 1998 - sg16-avd - lists.packetizer.com

Gatekeeper MIB update
by Michael Thatcher 13 May '98

13 May '98

As a result the audio conference regarding the mib developement for gatekeeper and ras, I am forwarding 2 files. One contains textual conventions which should be used by the ras, gatekeeper and potentially other mib efforts. The second is the a revised gatekeeper mib which removes those tables which are considered duplicates of those in the ras mib. These are ASCII text files. Mike

1 1

Notice of the Q.12-14/16 Cannes meeting
by Sakae OKUBO 12 May '98

12 May '98

To Experts of ITU-T SG16 Q.12/16, Q.13/16 and Q.14/16 Cc Mr. P-A. Probst, Chairman of SG16 Mr. G. Helder, Vice-Chairman of SG16 Mr. F. Tosco, Chairman of WP2/16 Mr. F. Bigi, ITU-TSB Mr. T. Geary, Rapporteur for Q.11/16 De Sakae OKUBO Rapporteur for Q.12/16 in ITU-T SG16 TAO Waseda Research Center 5th Floor, Nishi-Waseda Bldg. 4-36-19 Yoyogi 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 E-mail: okubo(a)giti.or.jp Dale SKRAN Rapporteur for Q.13/16 in ITU-T SG16 Ascend Communications, Inc. 621 Shrewsbury Avenue Shrewsbury, NJ 07702 USA Tel: +1 908 450 1635 Fax: +1 908 450 1611 E-mail: Dale.Skran(a)ascend.com Gary Thom Rapporteur for Q.14/16 in ITU-T SG16 Delta Information Systems Inc. Horsham Business Center Bldg. 3 300 Welsh Road, Horsham, PA 19044 Tel: +1 215 657 5270 ex 23 Fax: +1 215 657 5273 E-mail: gthom(a)delta-info.com ------------------------------------------------ Subject: Notice of Q.12-14/16 Rapporteur Meeting Date: 13 May 1998 ------------------------------------------------ Dear SG16 Colleagues, The subject meeting of ITU-T SG16 experts will be held in Cannes, France at the kind invitation of France Telecom/CNET. Please note that Q.11 will meet concurrently at the same place and have joint sessions with Q.12-14/16. 1. Date ^^^^^^^ 8 (Monday) - 11 (Thursday) June 1998 starting at 9:00 on the first day 2. Venue ^^^^^^^^ Noga Hilton Cannes 50, La Croisette F-06414 Cannes Cedex Tel: + 33 4 93 99 70 00 Fax: + 33 4 92 99 70 17 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group meetings 2) Q.12/16 B-ISDN multimedia systems and terminals - Progress in security, VBR, interworking and other technical aspects - Future direction of ATM based broadband systems 3) Q.13/16 Packet switched multimedia systems and terminals - Decision/Determination as in Section 5.8/APC-1372 - Final liaison to June SG8 decision meeting for T.38 - MIB work with Q14 - Other technical work 4) Q.14/16 Common protocols, MCUs and protocols for interworking with H.300-series terminals - H.235 V2 issues - H.245 V5 for Determination (9/98) - H.246 Annex B for Determination (9/98) - Other H.246 annexes and issues - H.MediaMIB for Determination (9/98) - Other H.MediaMIB issues - H.RDC for Determination (9/98) - Other technical issues 5) Any other Q.12-14/16 related matters - Interaction with other groups 6) Future work 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 29 May /// /// Distribution of the document: by 1 June /// /// Use the ftp site or e-mail reflector for distribution. /// 1) When you are going to submit a document, please notify S. Okubo as soon as possible, by 29 May (Friday) at the latest. Document number (APC-1nnn) will be allocated. Early indication of your submission plan is welcome. Note - Prefix "APC" comes from Atm (Q.12/16), Packet based (Q.13/16) and Common protocols (Q.14/16) based on coordination with Q.1 ("Q1City"), Q.3 ("T120"), Q.11 ("Q11"), Q.15 ("Q15") groups. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document APC-{1nnn}| | Study Group 16 {Version m if relevant}| | Q.12-14/16 Rapporteur Meeting {Date}| | Cannes, 8-11 June 1998 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ 3) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (by 1 June) by posting them at either of the following: - PictureTel ftp site (please advise S. Okubo of your posting) Site: standard.pictel.com/avc-site Login name: anonymous Directory: Incoming - Q.12-14/16 experts reflector e-mail address: itu-sg16(a)mailbag.jf.intel.com Please avoid the use of reflector when your document is voluminous. Use of Word for Windows 2.0 or 6 or pure text is recommended. 4) Input documents can be retrieved from 9806_Can directory of the ftp site. 5) Please bring 60 copies of your document to Cannes. Your cooperation is needed to start the meeting with all the documents at hand; please note that the copying capacity at the meeting site is limited. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ Please see the invitation which has been provided by the meeting host (/9806_Can/invitation.zip at the ftp site). 6. Registration ^^^^^^^^^^^^^^^ Please notify Mr. Azdine TADRIST (e-mail: azdine.tadrist(a)cnet.francetelecom.fr) with copy to Rapporteurs (e-mail: okubo(a)giti.or.jp, Dale.Skran(a)ascend.com, gthom(a)delta-info.com) as soon as possible if you plan to attend the Cannes meeting. 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ Please directly contact the following hotel using the form contained in the invitation. Noga Hilton Cannes 50, La Croisette F-06414 Cannes Cedex Tel: + 33 4 93 99 70 00 Fax: + 33 4 92 99 70 17 Citadines Carnot Aparthotel 1, rue Le Poussin (at the corner of Boulevard Carnot) 06400 Cannes, France Tel: + 33 4 92 98 34 34 Fax: + 33 4 93 38 84 09 We are looking forward to meeting with you in Cannes. Sincerely yours, Sakae OKUBO Dale SKRAN Gary THOM

1 0

Three SG16 white contributions from Q.12/16
by Sakae OKUBO 11 May '98

11 May '98

/// To Q.12-14 experts, the three zipped files have also been /// /// placed at ftp://standard.pictel.com/avc-site/Incoming/ /// Dear Mr. Bigi, I have placed the following three zipped files at the SG16 dropbox: 19455 May 11 16:53 H222_AM5.zip 553899 May 11 16:54 H310V2_D.zip 69739 May 11 16:54 Hbmp_dec.zip They are Q.12/16 white contributions for decision at the September meeting of SG16. 1) H222_AM5.zip contains H222_AM5.doc (Mac Word 6) for Draft H.222.0 Amendment 5. 2) H310V2_D.zip contains the following three files: Version2_clean_97.doc Version2_delta_97.doc Version2_wcm_97.doc They are for Draft H.310 Version 2 and produced with Windows Word 97. The first is for white contribution. The remaining two are for TSB use; delta document and document with change marks, both against H.310 (11/96) + COM16-55 as you requested. Please ignore the Temporary Document heading of Version2_delta_97.doc. 3) Hbmp_dec.zip is for Draft H.bmultipoint produced with Windows Word 7. Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

Re: H.323 Implementers Guide
by Kaynam Hedayat 11 May '98

11 May '98

Hi Jim, The version of the implementers guide which you sent does not include the changes that were proposed by APC-1339. These changes to H.323 Annex C and H.245 were approved at the Yokosuka meeting. Thank you. Kaynam jim.toga(a)INTEL.COM 05/05/98 04:23 PM Please respond to ITU-SG16(a)MAILBAG.INTEL.COM To: ITU-SG16(a)MAILBAG.INTEL.COM cc: (bcc: Kaynam Hedayat/PicTel) Subject: H.323 Implementers Guide Greetings, Attached is the latest version of the H.323 implementers Guide (the 'official' ITU errata). This was the text that was generated out of the experts meeting in Yokuska. Please review and send any comments back to me for further updating. Note that there are some ASN.1 fixes for v2 implementations! I have also placed this file in the 'incoming' directory of the PicTel AVC site. Best Regards, jimt. ****************************************************** *** +1-503-264-8816(voice) Intel - Hillsboro, OR. *** *** mailto:jim.toga@intel.com mailto:james.toga@itu.ch *** *** PGP keyID 36 07 86 49 7D 74 DF 57 50 CB BA 32 08 9C 7C 41 *** ******************************************************

1 0

Re: PictureTel Proposal for H.323 Remote Device Control
by Roni Even 10 May '98

10 May '98

Hi, I am sorry I did not attend the conference, I thought it will be Q3 only solution. I have one comment. In H.323 we have different conferences models, centralised or distributed, unlike the centralised model of the H.320. I think that in the goals and proposal we should define how FECC works in distributed conferences. Roni Even Accord email: roni_e(a)accord.co.il ______________________________ Reply Separator _________________________________ Subject: PictureTel Proposal for H.323 Remote Device Control Author: <ITU-SG16(a)MAILBAG.INTEL.COM> at internet Date: 5/8/98 2:50 PM This is a summary of the PictureTel proposal for Remote Device Control for H.323, which we discussed in the Q3/Q14 audio conference held on May 7. The Goals: 1) Provide FECC for H.323 conferences. 2) Interoperate with H.320 and H.324 systems with H.281 through gateways. 3) Simple to implement for basic FECC model using H.281 compatible messages. Additional features should be optional. 4) Use a common protocol for point-to-point and multipoint conferences. 5) Add optional support for new camera control mechanisms and for control of other types of devices, such as in T.RDC. 6) Make it extensible for new standard and non-standard features. The Proposal: 1) Start by encapsulating the whole H.224/H.281 stack within UDP, in an H.245 logical channel. 2) Add timestamps to real-time (start/continue/stop) messages, somehow (RTP or other). Receivers can use this to compensate for jitter in the network. Receivers free to ignore these. 3) Add functions from T.RDC into H.281 as optional extensions. Probably we will want to modify these a little, for instance to support positioning units based on field of view. One possibility is to define a new H.281 command code which indicates the rest of the PDU is an ASN.1 coded message, and use the ASN.1 taken from T.RDC. 4) For non-real-time commands (all except start/continue/stop), add a simple retransmission mechanism (just numbered messages and numbered ACKs) to supply reliable (if inefficient) transport on top of UDP. We can crib this from existing standards, such as NSRP from Annex A/H.324. 5) Define the functions of an H.224 router to reside in an MC or MCU. This would mostly be to manage flow control (or not) as does the H.320 LSD channel, rebroadcast info, route info, etc. This might also include caching capsets. 6) Make sure addressing and scope issues are synchronized with H.245 (use M/T addressing probably). 7) Break out the capability exchange function of H.224 into a new H.245 (and therefore TCP) generic cap exchange function that doesn't require the H.245 engine to recognize the contents of the caps, but merely to pass them along (as does H.224 capex). These "non collapsing capabilities" will map 1:1 at the gateway to the existing H.224 cap exchange. 8) In future, add T.124-like capability collapsing (AND, OR, etc.) to H.245. Details need work, but we'd like to support multicast and large conferences. This is not immediately useful for RDC, but would supply a generic extended H.224 stack that would provide for future simple control protocols without requiring upgrades to deployed infrastructure equipment such as MCs, MCUs, and gateways. Mark Duckworth PictureTel duckworthm(a)pictel.com

1 0

H.bmultipoint draft for decision uploaded to ftp site
by Hidenobu Harasaki 09 May '98

09 May '98

Dear Mr. Okubo and Q.12 experts: I have uploaded draft Recommendation H.bmultipoint for decision (hbmuldec.zip) to ftp://standard.pictel.com/avc-site/Incoming/. This will be submitted to the ITU-T by May 11 as a white paper for decision in September. Best regards Hidenobu Harasaki harasaki(a)ccm.CL.nec.co.jp Principal Researcher C&C Media Research Labs., NEC Corporation Phone: +81 44 856 8083 Fax: +81 44 856 2232

1 0

H.323 Annex D White Paper
by Kumar, Vineet 09 May '98

09 May '98

H.323 Colleagues, I have updated the H.323 Annex D (Real-time IP Fax using H.323) white paper with RTP DTMF as decided at the Yokosuka meeting. This file (h323annexDwhite.doc) has been uploaded in the Incoming directory. Comments are welcome. vineet ----------------------------------------------------------- Vineet Kumar Intel Corporation, JF3-212 2111 NE 25th Avenue Hillsboro, OR 97124-5961 (+1) 503-264-3439 (phone) (+1) 503-264-3375 (fax)

1 0

PictureTel Proposal for H.323 Remote Device Control
by Mark Duckworth 08 May '98

08 May '98

This is a summary of the PictureTel proposal for Remote Device Control for H.323, which we discussed in the Q3/Q14 audio conference held on May 7. The Goals: 1) Provide FECC for H.323 conferences. 2) Interoperate with H.320 and H.324 systems with H.281 through gateways. 3) Simple to implement for basic FECC model using H.281 compatible messages. Additional features should be optional. 4) Use a common protocol for point-to-point and multipoint conferences. 5) Add optional support for new camera control mechanisms and for control of other types of devices, such as in T.RDC. 6) Make it extensible for new standard and non-standard features. The Proposal: 1) Start by encapsulating the whole H.224/H.281 stack within UDP, in an H.245 logical channel. 2) Add timestamps to real-time (start/continue/stop) messages, somehow (RTP or other). Receivers can use this to compensate for jitter in the network. Receivers free to ignore these. 3) Add functions from T.RDC into H.281 as optional extensions. Probably we will want to modify these a little, for instance to support positioning units based on field of view. One possibility is to define a new H.281 command code which indicates the rest of the PDU is an ASN.1 coded message, and use the ASN.1 taken from T.RDC. 4) For non-real-time commands (all except start/continue/stop), add a simple retransmission mechanism (just numbered messages and numbered ACKs) to supply reliable (if inefficient) transport on top of UDP. We can crib this from existing standards, such as NSRP from Annex A/H.324. 5) Define the functions of an H.224 router to reside in an MC or MCU. This would mostly be to manage flow control (or not) as does the H.320 LSD channel, rebroadcast info, route info, etc. This might also include caching capsets. 6) Make sure addressing and scope issues are synchronized with H.245 (use M/T addressing probably). 7) Break out the capability exchange function of H.224 into a new H.245 (and therefore TCP) generic cap exchange function that doesn't require the H.245 engine to recognize the contents of the caps, but merely to pass them along (as does H.224 capex). These "non collapsing capabilities" will map 1:1 at the gateway to the existing H.224 cap exchange. 8) In future, add T.124-like capability collapsing (AND, OR, etc.) to H.245. Details need work, but we'd like to support multicast and large conferences. This is not immediately useful for RDC, but would supply a generic extended H.224 stack that would provide for future simple control protocols without requiring upgrades to deployed infrastructure equipment such as MCs, MCUs, and gateways. Mark Duckworth PictureTel duckworthm(a)pictel.com

1 0

H.245 Version 4 Uploaded to ftp site
by Mike Nilsson 08 May '98

08 May '98

I have uploaded draft version 4 of H.245 (H245_f.zip) to the ftp site ( ftp://standard.pictel.com/avc-site/Incoming/ ) This will be submitted to the ITU-T as a white paper for decision in September. Best regards Mike Nilsson *********************************************************************** * Mike Nilsson Tel: +44 1473 645413 * * Video Processing Unit Fax: +44 1473 643791 * * Centre for Human Communications Email: mike.nilsson(a)bt-sys.bt.co.uk * * BT Laboratories [MLB3/11] * * Martlesham Heath * * Ipswich IP5 7RE * * UK * ***********************************************************************

2 1

Re: H.323 Implementers Guide
by Orit Levin 07 May '98

07 May '98

Hello Jim! 1.I have corrected the Fast Connect Procedure "correction". Upon receipt of the SETUP message, the original called endpoint's actions should have been merged with the additional "mediaControlChannel" support instead of replacing the former. (So I restored the original text.) 2. It also seems that the corrections to H.235 Pictures are missing from the Implemetors Guide. See APC-1360 3.1 Chapter 10.2 Diffie-Hellman with optional Authentication - Phase 1. The rest of the document seems OK to me. Best Regards, Orit Levin RADVision Inc., Mahwah, NJ Tel: 201-529-4300 ext. 230 Fax: 201-529-3516 E Mail: orit(a)radvision.com

2 1