CSR-T Volume 6 #6, September 1995

COMMUNICATIONS STANDARDS REVIEW TELECOMMUNICATIONS

Volume 6, Number 6 September 1995

IN THIS ISSUE The following reports of recent standards meetings represent the view of the reporter and are not official, authorized minutes of the meetings.

TR-41.6.1, North American Wireless Customer Premises Equipment (NA/WCPE) Working Group Meeting May 9 – 11, 1995, Murray Hill, NJ...... 2 TR-41.6.2 PCI...... 4 TR-41.6.1 Partial Meeting Roster, May 9 – 11, 1995, Murray Hill, NJ...... 4 TR-41, User Premises Telecom Requirements, June 12 – 16, 1995, Kansas City, MO...... 5 TR-41.1 Multi-Line Telecommunication Systems...... 5 TR-41.1.1 Multi-Line Telecommunication Systems (MLTS) / Transmission...... 6 TR-41.1.9 Multi-Line Telecommunication Systems Support of Enhanced 911 Service...... 7 TR-41.2 Conformity Assessment...... 8 TR-41.3 Telephones and Acoustic Terminals...... 9 TR-41.5 Premises Distribution for Multimedia...... 10 TR-41.6 Wireless User Premises Equipment (WUPE)...... 12 TR-41.7 Safety and Environmental Considerations...... 12 TR-41.7.1 North American Telecommunication Equipment Safety...... 15 TR-41.7.3 Electromagnetic Compatibility Considerations...... 15 TR-41.8 Commercial and Residential Premises Wiring...... 16 TR-41.8.1 Commercial Premises Wiring...... 16 TR-41.8.2 Residential Wiring/Cabling...... 21 TR-41.8.3 TIA-569-A Telecommunications Pathways and Spaces...... 21 TR-41.8.4, Customer-Owned Outside Plant...... 21 TR-41.9 Regulatory Considerations...... 22 TR-41 Partial Meeting Roster, June 12 – 16, 1995, Kansas City, MO...... 26 Second Meeting of the JCG on AVMMS (Audiovisual/Multimedia Services), July 3 – 5, 1995, Geneva...... 27 JCG on AVMMS Meeting Roster, July 3 – 5, 1995, Geneva...... 32 TR-29, Facsimile Systems and Equipment, July 31 – August 3, 1995, Quebec City, Quebec...... 33 TR-29.1 Facsimile and File Transfer Protocols...... 35 TR-29.2 Facsimile Programmable Interfaces...... 37 TR-29.3 and Q10/8, Audiographic Conferencing...... 40 TR-29.4 Secure Facsimile...... 42 TR-29 Partial Meeting Roster, July 31 - August 3, 1995, Quebec City, Quebec, Canada...... 43 SG 14 Rapporteurs Meetings, August 7 – 12, 1995, Hood River, OR...... 44 Q1/14, V.savd...... 44 Q1/14, V.8bis...... 46 Q7/14, DTE-DCE Interfaces...... 50 SG 14 Meeting Roster, August 7 – 12, 1995, Hood River, OR...... 54 Acronym Glossary...... 55 1995 Meeting Schedules as of August 31. 1995...... 57 1996 Calendar...... 57

September1995 Vol. 6.6 Copyright © CSR 1995 1 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS REPORT OF TR-41.6.1, NORTH AMERICAN WIRELESS CUSTOMER PREMISES EQUIPMENT (NA/WCPE) WORKING GROUP MEETING MAY 9 – 11, 1995, MURRAY HILL, NJ

TR-41.6.1/95-05-011 is the working draft (first V&V version) of Wireless Customer Premises Equipment Interoperability Standard (PN-3400) dated April 13, 1995. It is derived from ETS 300 175 (DECT). At this meeting the working draft was reviewed in detail as summarized below. PART 1, OVERVIEW

Part 1, Overview, was reviewed and cross referenced with the discrepancy report (DR) contained in TR-41.6.1/95- 05-41. There was also a discussion on methods of defining conformance as found in Section 9. PART 2, PHYSICAL LAYER

TR-41.6.1/95-05-54 (G.J. Wimpenny, Symbionics) presents the results of analyses and simulations showing the relationship between Differential Vector Error Measurement (DVEM) and system implementation loss, and it proposes a maximum limit for DVEM over any burst of less than 12.5%. The paper argues that DVEM rather than EVM (Error Vector Measurement) is the better means of assessing the modulation accuracy of WCPE transmitters. The limit values were discussed and adopted. TR-41.6.1/95-05-57 (D. Akerberg, Ericsson) proposes modifications to Annex C, Synchronization Port. Part 2, Physical Layer, was reviewed and revised; the V&V DRs were discussed. AT&T, Ericsson, Motorola, Nokia, Symbionics, and Northern Telecom were represented in the V&V team. TR-41.6.1/95-05-56 (D. Akerberg, Ericsson) proposes modifications to Section 5.5, Unwanted RF Power Radiation. During discussion, changes were made to meet the intent of this contribution. PART 3, MEDIUM ACCESS CONTROL LAYER

Part 3, Medium Access Control Layer, was reviewed and revised; the V&V DRs were discussed. Nokia, Motorola, Northern Telecom, and Ericsson were represented at the V&V meetings. PART 4, DATA LINK CONTROL LAYER

Part 4, Data Link Control Layer, was reviewed; the V&V DRs were discussed. V&V team representatives were from Mitel, Ericsson, Northern Telecom, and Nokia. PART 5, NETWORK LAYER

The DR was reviewed. A new V&V meeting will be set up to go over the new Part 5, Network Layer, for quality. PART 6, IDENTITIES AND ADDRESSING

TR-41.6.1/95.05.46 (N. King, Siemens) is the DR for Part 6, Identities and Addressing. Rolm, Ericsson, Siemens, Motorola, and Northern Telecom were represented at the V&V session. TR-41.6.1/95.05.06D© (N. King, Siemens) is Version D of Part 6, Identities and Addressing. The document was discussed in reference to the DR. It was noted that while International Portable User Identity type R (IPUI R) is public/GSM (Groupe Speciale Mobile), it is actually a Global Mobile Number and thus applies to all public wireless services. It was decided that IPUI R should either include non-GSM billing or a new IPUI should be defined for the more universal case. PART 7, SECURITY FEATURES

TR-41.6.1/95.05.07C© (N. King, Siemens) is Version C of Part 7, Security Features. TR-41.6.1/95.05.047 (N. King, Siemens) is the DR for Part 7. Northern Telecom, Ericsson, Motorola, Siemens, and Rolm were represented at the V&V meeting.

PART 8, SPEECH CODING AND TRANSMISSION

The DR for Part 8 was reviewed. AT&T, Mitel, Ericsson, and NTI were represented on the V&V team. Part 8, Speech Coding and Transmission, was revised per the DR. PART 9, CUSTOMER PREMISES ACCESS PROFILE

The DR was discussed; four items were identified as being outside of the scope of the V&V group. These items were sent to the TR-41.6.1 Working Group for resolution. V&V team representatives were from Symbionics, Northern, Nokia, Motorola, and AT&T. During review of Part 9, Customer Premises Access Profile, a question was raised on how to handle Crypted->clear failure. This will be coordinated with ETSI RES3. SYNCHRONOUS DATA (STU-III)

TR-41.6.1/95-04-1060 (J. Ferranto, NTIA/ITS) proposes the addition of synchronous data services option to CPAP (Customer Premises Access Profile) using LU5/LU6 (Logical Unit) services on the DLC (Dynamic Load Control). TR-41.6.1/95-04-1059 (J. Ferranto, NTIA/ITS) proposes the addition of synchronous data services (STU-III) option to CPAP using LU1 service only. There was discussion around the issue of whether these contributions, 1) define an architecture that is non-compatible with WCPE, and 2) create a necessary and sufficient set of changes to WCPE. There was a range of opinion, and it was decided to set up a synchronous data meeting on May 24. TR-41.6.1/95-05-58 (D. Akerberg, Ericsson) discusses open issues associated with transmission of synchronous data. TR-41.6/95-05-273 is the Interface Control Document for the STU-III Black Digital Interface. TR-41.6/95-05-272 is entitled “Future Secure Voice System: Signaling Plan - Interoperable Modes.” PART 10, CONFORMANCE TEST

Part 10 (not included in current draft), Conformance Test, will be discussed in the June meeting with the intention of kicking it off with Test Houses and Test Equipment Manufacturers at the September meeting. PART 12, CORDLESS RADIO FIXED PARTS

Part 12, Cordless Radio Fixed Parts, was reviewed. BALLOTING PROCESS

Version control was discussed. The editors will create Rev. F with revision bars showing the agreements as of May 11, 1995, and it will be shown to ETSI for coordination purposes. Rev. G will be the same as Rev. F with all revisions incorporated. TR-41.6.1/95-05-1062 is a template for WCPE normative references. It defines final formatting, left revision bars, etc. A JTC TAG 6 liaison report included work on using the WCPE document as the basis of the DCT-U(Digital Cordless Telephone-U.S., WCPE for the licensed band). This document will be a “delta” document on the DCT-U. GENERAL

TR-46/95-05-276 is the May 5, 1995 draft ANSI Standard for Methods of Measurement of the Electromagnetic and Operational Compatibility of Unlicensed Personal Communications Services U-PCS)Devices. ANSI C63 SC 7 is responsible for the development of this work. This project was started in November 1993, when the FCC invited ANSI C63 to develop procedures to support the provisions to Part 15 for U-PCS. WINForum and FWUF (Federal Wireless Users Forum) are jointly conducting the WINWork 95 conference during the week of May 15, 1995. TIA, ETSI, IEEE, ANSI, and UTAM, Inc. (Unlicensed Transition and Management) will be participating. The WINSpectrum meeting will have a press release on 5.2 GHz on May 15. The WINAdvocate meeting will be held at the same place on May 16.

During the UTAM liaison report, it was stated that UTAM, Inc. is certified by the FCC. (UTAM purchases unlicensed spectrum from private users to make the bands available.) Formal announcement of this will be in May after the WINForum/FWUF workshop. The UTAM, Inc. test suite is under evaluation. The test house, CCLabs, is requesting submissions for Beta test of the test procedures. Manufacturers who submit equipment for beta test and pass the test (assuming the test proves to be adequate) will get immediate UTAM certification without further testing. TR-41.6/95-05-274 (P. Weismantel, NEC America) presents a model and definition of terms for the formulation of a Mobility Management standard. This contribution along with TR-41.6/95-05-275 will be the basis for a discussion regarding the mobility management proposed project at the June meeting. TR-41.6.2 PCI TR-41.6.2 PCI draft 0.4 from G. Boudreau (Northern Telecom), dated May 12, 1995, is on the WWW, ftp://ftp.ti.org/pub/tr41/pci.

TR-41.6.1 PARTIAL MEETING ROSTER, MAY 9 – 11, 1995, MURRAY HILL, NJ Peter Bligh, Mitel Chair TR-41.6 Anritsu Mike Barrick AT&T Ed Polansky AT&T Terry Sterkel Ericsson Dag Akerberg Ericsson Peter Murray Mitel Peter Bligh Motorola Rick Sagers NEC Paul Weismantel Nokia Peter Harrison Northern Telecom Gary Boudreau Northern Telecom Shila Heeralall Northern Telecom Stewart Kuan NTIA Jim Hoffmeyer NTIA/ITS Liz Pol Panasonic Sam McConoughey Panasonic Naoya Morita Philips Semi Stefan Drude Siemens Bob Pau Siemens Rolm Neal King Spectralink Tom Ohlsson Stanford Telecom Herman A. Bustamante Symbionics Graham Norgett

4 Vol. 6.6 Copyright © CSR 1995 September 1995 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS REPORT OF TR-41, USER PREMISES TELECOM REQUIREMENTS JUNE 12 – 16, 1995, KANSAS CITY, MO TR-41.1 MULTI-LINE TELECOMMUNICATION SYSTEMS

T1E1 LIAISON

T1E1.1 is considering introducing balanced ringing on loop-start lines and requests input from TIA (see additional discussion below). The following recent T1E1 activities have impact on future potential work of TR-41.1: • Consideration is being given to adding DS3 wander requirements to the DS3 jitter requirements in standard T1.404 (Customer-Network DS3 Interface). • The pulse mask in standard T1.404 needs correcting to be compatible with that in standard T1.102 (Network- Network DS3 Interface). • T1E1.4 has approval for a study on spectrum compatibility (e.g., what types of circuits can go into the same binder group). Spectrum compatibility impacts impairments; however, the current scope of the study excludes CPE (Customer Premise Equipment) and CI (Call Indicator) wiring. UPDATE/RESTRUCTURE OF TIA-464 P RIVATE AUTOMATIC PBX

Letter Ballot Action The letter ballot period for the update and revision of standard TIA-464-A (PBX) was sent out in early April 1995 and closed on June 13, 1995 (one day prior to the meeting). The balloting resulted in: • 11 Favorable votes with no comments • 5 Favorable votes with comments • 3 Unfavorable votes (with comments) Letter Ballot Comment Resolution This meeting was almost entirely devoted to the review of and response to the letter ballot comments on the update of TIA-464-A. All comments were resolved. The three companies casting unfavorable ballots were represented at the meeting and agreed that the resolution adequately addressed their objections. It was determined by the group that the resulting technical changes warranted the generation of a default ballot but were not extensive enough to justify a full re-balloting. All ballot comments (favorable and unfavorable) are contained in TR-41.1/95-06-022 (J. Schick, Nortel). Comments that resulted in technical changes reflected in the default ballot are noted below: • AT&T objected to a requirement relating to digital (A&B bit) address signaling that implies that 911-CAMA (Centralized Automatic Message Accounting) trunks with MF (Multitone Frequency) must be supported by the PBX (Private Branch Exchange). This was resolved by deleting references to inband signaling in the requirement. • Bell Atlantic was concerned about the PSTN (Public Switched Telephone Network) loss treatment for access lines and the need for the inclusion of 911-CAMA trunk requirements. The definitions for access lines were updated to reflect current practice. A definition for the 911-CAMA trunk was added to the section on analog access lines with reference to the recently issued standard T1.411 for requirements. • Bellcore’s unfavorable vote addressed several differences between the current text and the recently revised standard T1.403 (DS1 Metallic Interface), as well as the concern raised at the previous meeting on PBX call blockage on calls to the network (see CSR-T 6.4). Technical changes to align with T1.403 were approved and will be reflected in the default ballot. The PBX blockage issue was resolved via addition of a desirable requirement that the PBX provide a means to provide internal call blockage user notification. The wording reflects the recommendation in TR-41.1/95-06-021 (R. Frank, Siemens) that the requirement does not specifically call for a recorded announcement to advise users of internal call blockage. • Revised wording in the scope clarifies an issue raised by the Canadian Standards Association (CSA) regarding whether the updated standard applies to all digital PBXs or specifically to Integrated Services PBXs (ISPBXs). The standard anticipates that the majority of digital PBXs manufactured and sold in North America will have ISDN (Integrated Services Digital Network) functionality and compatibility. For digital PBXs that do not have this functionality, all of the requirements in the standard apply except for those that are specific to the ISDN functionality. • In response to the unfavorable vote from Siemens Rolm Communications, a full rewrite of the section on ISDN Private Network Interface Requirements was submitted and adopted in TR-41.1/95-06-026 (Mitel). The rewrite

clarifies that PSS1 (Private network Signaling System 1, defined by ISO) addresses signaling and is not synonymous with overall private network requirements and that the requirements in this standard address only PRI (Primary Rate Interface), not BRI (Basic Rate Interface). Furthermore, throughout the rewrite, the term “Q-SIG” is replaced with “PSS1” in recognition that PSS1 is the international designation for ISDN private network signaling, while Q-SIG is a term used mainly by ECMA (European Computer Manufacturer’s Association). GLOBAL STANDARDS HARMONIZATION

The PBX Transmission Requirements Comparison was updated to the latest draft issue (January 1995) of the ETSI (European Telecommunication Standards Institute) PBX Transmission Standard, BTC-02048 (not provided as a contribution). Major changes in this issue of BTC-02048 are: • Specific half-connection loss or levels are no longer presented as requirements. Half-connection levels, as well as the port-to-port loss plan, shall have a value stated by the supplier. (However, many administrations may still require that PBX ports adhere to the currently defined input and output levels; thus, an annex of the standard contains country-specific port levels as currently required by the administrations.) • Specific requirements or guidelines for one-way delay have been deleted. The transmission delay between ports shall have a value stated by the supplier. • Requirements, as well as test methods, for impedance unbalance about earth (i.e., longitudinal balance requirements) are no longer in the standard. A detailed cross-reference between BTC-02048 and TIA-464B was submitted (TR-41.1/95-06-023, T. Tung, Siemens). Ordered by the clauses and subclauses of BTC-02048, the corresponding section or paragraph of TIA-464 or other existing TIA standard is shown. In addition, the cross-reference gives the correspondence between the terms used by ETSI (global) and those used by TIA (North American). Of note is the fact that a number of ETSI requirements do not have a directly corresponding requirement in TIA standard, particularly issues covered in normative and informative annexes (e.g., test procedures and equipment). J. Horrocks (ETSI BTC2 Chair) expressed his feeling (TR-41.1/95-03-019) that the joint meeting in March was constructive and useful and issued a formal invitation (TR-41.1/95-03-020) to TIA for a second joint meeting in conjunction with the regular fall meeting of BTC2 in Mainz, Germany, on October 23-26, 1995. LOOP REVERSE BATTERY SUPERVISION

At the March meeting, TR-41.1 reacted to a T1E1 proposal for eliminating requirements for “immediate dial” and “delay dial” from ANSI standard T1.405, asserting that, as long as certain COs (Central Offices) required these methods of supervision, they should be covered by a T1E1 standard (see CSR-T 6.4). This position was communicated to T1E1 (TR-41.1/95-03-017). T1E1 responded (TR-41.1/95-06-025) by stating that these requirements will be retained in an annex to T1.405 and, further, that the focus of T1.405 will be re-oriented to make it specific to DID (Direct Inward Dialing) service. T1.405 currently addresses a general-purpose loop reverse-battery interface. Several recent draft changes have been made to the document. Although these changes may need to be reflected in a future version of TIA-464, the current TIA-464-A update, discussed above, will not be further modified since the T1.405 update, in contrast to T1.403, is still in draft form. BALANCED RINGING ON LOOP-START ACCESS LINES

T1E1.1 is proposing a change to ANSI standard T1.401 to allow for the application of balanced ringing by network equipment to access lines. Historically (and currently) loop ringing is based upon applying the ringing voltage to the ring conductor and ground (with or without dc offset) to the tip conductor. Semiconductor technology makes it possible to apply ringing signals balanced between the tip and ring conductor which could be attractive for systems such as fiber-loops that do not have inherent ground connections. T1E1 solicited comments from TR-41 (TR- 41.1/95-06-024) regarding any potential compatibility problems of using balanced ringing on loop-start lines. TR-41.1.1 MULTI-LINE TELECOMMUNICATION SYSTEMS (MLTS) / TRANSMISSION

TRANSMISSION CONSIDERATIONS FOR WIRELESS USER PREMISES EQUIPMENT

WCPE (Wireless Customer Premise Equipment) Loss Plan TR-41.1.1/95-06-009 (J. Schick, Nortel) presents two alternative scenarios for implementing a loss plan for wireless stations. The basis of both scenarios is that, for connections to any other PBX line or trunk port, a call terminating to a wireless station port (digital) will have loudness characteristics equivalent to those of a call terminating to an ICS (ISDN-Compatible Station) port. Loudness values for the wireless stations are assumed to be the long-term

ITU-defined ISDN values that, based upon the work described in TR-41.1.1/95-03-004 (S. Whitesell, AT&T), translate to TOLR = -49 dB, ROLR = +53 dB. One scenario describes a loss plan that inserts electrical loss in any wireless port-to-other port path, such that, the loudness characteristics will be equal to those of an ICS-to-other port path. In general, this scenario requires unique loss values that are not currently defined in the ISPBX (Integrated Services PBX) loss plan. The other scenario uses the ICS port loss electrical values and presents the deviations in loudness characteristics. In general, the deviations are such that the nominal levels from the wireless port to other ports is about 3 dB louder than that of an ICS connection while the levels towards the wireless port are about 2 dB softer. An advantage to this scenario is that ISDN connections are bit-transparent. It was noted that complaints had been received from some network users that connections from an ISDN terminal sound “loud.” Nevertheless, the group recommended the second scenario on the basis that it is should not be the responsibility of the PBX to make special adjustments for wireless sets when such sets have ISDN loudness characteristics that are different than those of ICS. A liaison to that effect will be sent to TR-41.6. This liaison will point out the deviations in loudness levels noted above. WCPE Echo Control TR-41.1.1/95-06-010 (C. Sacco, Bellcore) discusses consideration for private network echo planning and implications of tandeming echo cancelers. Tandeming or cascading of echo cancelers could occur in WCPE where the wireless station connection embodies significant delay so that, by public/private network allocation guidelines (e.g., ANSI standard T1.508), the WCPE is required to insert echo control for terminal-generated echoes. The conclusion presented in TR-41.1.1/95-06-010 is that cascading of echo cancelers is unlikely to cause degradation with “well-designed” echo cancelers (i.e., with margin for the maximum tail end delay expected, non-linear processors that will not operate at inappropriate times during double-talk). However, it is important that the echo path is linear, that the tail end delay does not exceed the echo canceler specification, and that the return loss is greater that the double-talk detection threshold. Non-linearities in the echo path could arise, for example, from ADPCM (Adaptive Differential Pulse Code Modulation), digital loss or gain pads, and PCM overload distortion. These findings will also be provided to TR-41.6. DPBX APPLICATION GUIDE

The editor reported that work had started on revising the diagrams and the text of TIA TSB-32 (Digital PBX Application Guide) in accordance with previous contributions. However, it was not clear as to how various loss treatments would be applied by the network under new guidelines. Thus, no draft was available for review at this meeting. In cooperation with Bell Atlantic, the editor intends to generate a new set of diagrams and a draft for the next meeting. It was suggested that echo control application guidelines also be included in the Application Guide. NEW WORK ITEMS

Future work items for the group were discussed. Two items were of particular interest: • Jitter and Wander • Delay in CPE and delay allocations between CPE and the network The Chair requested contributions on these topics for the next meeting. TR-41.1.9 MULTI-LINE TELECOMMUNICATION SYSTEMS SUPPORT OF ENHANCED 911 SERVICE

FCC NOTICE OF PROPOSED RULE MAKING (NPRM 8143) ON ENHANCED 911

The Chair reported on meetings with the FCC on NPRM 8143. A main focus was to separate Enhanced 911 wireline regulations from those for wireless. The Chair’s impression was that there remains a significant amount of confusion and misunderstanding as to how Enhanced 911 for MLTS currently is implemented. Because of the many remaining unresolved issues, it will be at least a year before meaningful rulemaking. However, the Chair also warned that if TIA puts too much emphasis on the CAMA trunk solution (currently, the only viable solution as described in TIA TSB-103), this method may become adopted as law. The Chair, therefore, urged that TIA should start to prepare for ISDN (e.g., reserving a slot in the D-channel for 911 calling services).

TIA STANDARD FOR MLTS SUPPORT OF ENHANCED 911 CALLING SERVICE

A draft outline of a proposed standard for PBX and KTS (Key Telephone System) Enhanced 911 Calling Service Support is presented in TR-41.1.9/95-06-005 (A.G. Caggiano, AT&T). The intent of the document is to supplement the TIA PBX standard (TIA-464-B) with requirements associated with this service (e.g., addressing 911 dialing, 911 call routing, and 911 caller location database issues). Both current (i.e., 911-CAMA trunk) and future (i.e., ISDN) network interfaces for Enhanced 911 calling will be covered. Text contributions for the proposed standard are to be provided at the next meeting. It is hoped that a complete draft of the standard can be made available by December 1995. John Schick, Northern Telecom

TR-41.2 CONFORMITY ASSESSMENT

MUTUAL RECOGNITION UPDATE

C. Berestecky (AT&T) reported that the US-Europe MRA (Mutual Recognition Agreement) meeting took place on April 1, 1995. The topics discussed at the meeting were safety, EMC (Electromagnetic Compatibility), telecom, and some conformity assessment issues. The US (OSHA) proposed a safety MRA. In Europe, however, safety is already covered by the manufacturer’s declaration. The added value of a safety MRA was unclear at this time. This will be discussed again at the next MRA meeting. The possibility of obtaining a separate MRA for EMC is unlikely. In the event that a multi-sector MRA is reached, the EMC aspects of the MRA should include all non-telecom RF (Radio Frequency) transmitters. The EMC Directive also includes RF transmitters that are not telecom equipment, such as televisions, etc. Europe would also like an MRA for cellular and PCS (Personal Communication Services) equipment. The US and Canada would like an MRA to include analog telecom equipment. While the Telecom Directive has been in effect for some time now and may soon be revised, the Directive’s analog CTRs (Common Technical Requirements) are non-existent to date. Progress on the analog CTRs is occurring slowly. The current CTR for analog data modems covers DTMF (Dual Tone Multi Frequency) and certain disconnect features only. In addition, the laws of countries such as France, Germany, and the US may require modification if the MRA effort is to achieve much success in the future. C. Berestecky (AT&T) also announced that a European market access workshop will be held in Brussels on July 6 and 7. The objective is to describe what it takes, currently, to move a product to market in terms of safety, EMC and telecom requirements. A request has been made to have the European private sector represented at the workshop for added insight. C. Berestecky will report on the workshop at the next TR-41.2 meeting. CCT/NAFTA (CONSULTATIVE COMMITTEE - TELECOMMUNICATIONS/NORTH AMERICAN FREE TRADE AGREEMENT)

Mexico has provided a matrix of market access requirements. Canada and the US are expected to provide similar matrices soon. CONFORMITY ASSESSMENT WHITE PAPER DISCUSSION

Several white papers on conformity assessment (with supporting documents) were presented at the meeting. A brief description of each paper is given below. Work will continue on each paper for the September meeting. At that time, a discussion will begin on how to combine the papers on conformity assessment. Lab Accreditation TR-41.2/95-06-20 is a draft TIA position paper prepared by T. Tung (Rolm), S. Whitesell (AT&T), and A. Wride (Communication Certification Labs). The TIA recognizes the value of accreditation systems; however, the cost and effort associated with multiple accreditation schemes are unacceptable. This is where mutual recognition of test results is beneficial. Mutual recognition of test results could account for slight differences in test procedures and end-point requirements. The acceptance of test results should be uniform for both manufacturers and independent test laboratories. The ISO Guide 25 provides the appropriate methodology for laboratories to obtain accreditation.

TR-41.2/95-06-24 contains the draft minutes of the Industry Working Group on Laboratory Accreditation held at Ford Motor Company Dearborn Michigan, dated April 19, 1995. The discussions covered broad lab accreditation issues facing US industries of all kinds. Supplier’s Declaration TR-41.2/95-06-21 (P. Adornato, Northern Telecom, S. Crosby, AT&T, and A. Daughtry, Bellcore) covers suppliers’ declaration experience for EMC and safety in North America (FCC is in the process of implementing SDC (Supplier’s Declaration of Conformity) via NPRM 95-19) and discusses progress in this area in Europe (ISO/IEC JTC1/SWG-CA Guide on Supplier’s Declaration will eventually replace ISO Guide 22). Future work on this paper will include supplier accountability, the use of accrediting bodies, marking and labeling, and related MRAs. TR-41.2/95-06-26 (C. Zvonkovich, Information Technology Industry Council) provides a draft letter from ITIC opposing OSHA’s announced intent to consider implementing a program to require use of a unique mark for products certified by NRTLs (National Registered Test Labs). Marks and Labels TR-41.2/95-06-22 (S. Crosby, AT&T and A. Daughtry, Bellcore) covers marking and labeling experience for EMC and safety in North America and in the European territories. Progress in multinational marking and labeling applications were also discussed. In Europe, the CE Marketing is the result of years of cooperative negotiations. In North America, the FCC is currently entertaining suggestions regarding the use of a single marking that transcends any Canadian, Mexican or US language barrier in FCC’s NPRM 95-19. Future work on this topic will include minimizing the number and size of marks and labels, issues relevant to supplier’s declaration and MRAs, and an investigation into what international mechanisms exist to facilitate the use of a universal set of markings and labels. Third Party Accreditation TR-41.2/95-06-23 (J. Christiano, Inchcape, with input from D. Dulmage, Certelecom, and D. Haataja, UL) is a draft paper on third party testing and certifications. Third party accreditation experience was discussed for the North American and international markets. The emphasis here was toward developing an industry position establishing the value of third party accreditation. The draft will be reworked based on discussions. NIST Standards in Trade Program S. Crosby (AT&T) discussed the NIST (National Institute of Standards and Technology) Standards in Trade program and initiatives (TR-41.2/95-06-28). Discussion included: • Support for ISO/IEC and other international standards committees and subcommittees • Implementation of NAFTA: Trilateral Committee and standards information • Overcoming technical trade barriers in the EU (European Union) and Big Emerging Markets (BEM) • Training and informational database implementation The Chair, P. Adornato, asked that the white paper authors continue to develop the white papers on 1) Lab Accreditation, 2) Suppliers Declaration, 3) Marks and Labeling, and 4) Third Party Accreditation. Updates on the white paper authoring progress will be given at the September meeting.

TR-41.3 TELEPHONES AND ACOUSTIC TERMINALS TR-41.3/95-06-021 is a letter from D. Rittenhouse (Chair, TR-41.3) to G. Tennyson, BellSouth Communications, dated June 16, 1995. The letter explains the correlation between the voltage-versus-current characteristics of the T1E1.1 (T1.401-1993) and TR-41.3 related standards (EIA-470A and CSA T.510). TR-41.3 is working on revisions to make their related standards consistent with T1.401-1993 (Figures 5, 6, 11 and 12). TR-41.3/95-06-017 (R. Breden, TIA) is a copy of SSA 410 Basic Requirements for Telephone Sets (Pulse and DTMF), from Saudi Arabia. R. Breden requests comments on this standard be sent to NIST by July 7, 1995. TR-41.3/95-06-018 is a copy of a T1E1.1/95-029, which discusses the possible use of balanced ringing by network equipment. Currently the ring voltage is applied to the Ring conductor and ground is applied to the tip conductor. With balanced ringing, V/2 is applied to each conductor in such a way as to present V across the tip and ring conductors. Balanced ringing will be especially attractive to designers of Fiber-In-The-Loop and Hybrid-Fiber- Coax systems. T1E1 has requested TR-41.3’s input on the potential for network-to-Customer Installation equipment compatibility problems if balanced ringing is used by network equipment.

TR-41.3/95-06-027 is a letter from D Rittenhouse (Chair, TR-41.3) to G. Tennyson (Chair, T1E1.1), dated June 16, 1995. It notes that the initial reaction of TR-41.3 is that balanced ringing should work properly for single party service (not party line) when bridged ring detection circuitry is used. The letter also requests additional information from T1E1 on the specifications proposed and the possibility of non sine wave ringing signals (see TR-41.3/95-06- 026 below). TR-41.3/95-06-019© is a copy of Canadian Standards Association T.510, Performance and Compatibility Requirements for Telephone Sets with Loop Signaling, Third Draft, May 1995. TR-41.3/95-06-020, Addition to Recommendations to TR-41.6 Concerning WUPE Transmission Performance Parameters (R. Britt, Nortel), clarifies a paragraph of text in Appendix A of PN-3446, Personal Communications Interface – Interoperability Standard, regarding possible differences between the idealized conversion factors and actual handsets. TR-41.3/95-06-022 is a draft of the ANSI Specification of Hearing Aid Characteristics, from the Acoustical Society of America. This standard describes air-conduction hearing aid measurement methods that are particularly suitable for specification and tolerance purposes. TR-41.3/95-06-023© is draft 6 of IEEE P1329, Standard Method for Measuring Transmission Performance of Hands- Free Telephone Sets, dated June 1995. TR-41.3/95-06-024 (D. Rittenhouse, U of Waterloo) is draft 4 of PN-3399, Requirements for Handset Telephones Intended for Use by the Hard of Hearing (to become TIA/EIA-504-A and CSA-T515-95). It was distributed for critical review and comment. It defines magnetic field requirements for all handset telephones intended to couple magnetically with hearing aids. It also covers requirements for receive-amplified handset telephone intended for use by the hard of hearing. At the March 1995 TR-41.3 meeting in San Francisco, S. Whitesell (AT&T) agreed to write a note to be included in PN-3399, to grandfather the U-type receiver in light of the tightening of the magnetic field frequency response template. TR-41.3/95-06-025 provides the text for that note. TR-41.3/95-06-026 (S. Whitesell, AT&T) delineates some issues concerning ringing signals. The ringing signals to which telephones should respond are specified in PN-2892 in terms of sine waves, whereas real world ringing signals frequently are not sine waves. ANSI T1.401 acknowledges this fact, and a note pointing to the T1.401 discussion on this point has been included in PN-2892, Revision of EIA-470-A, Telephone Instrument with Loop Signaling for Voiceband Applications. However, a better definition of the ringing signals to which telephone equipment should respond is required by manufacturers using software algorithms and digital signal processors for ring detection in their products. TR-41.3/95-06-028 is a fax from Multi-Coil Concepts dated April 12, 1995. Multi-Coil Concepts has applied for patent on an hearing aid compatibility probe that contains 5 coils inside a transparent non-metallic enclosure to allow more accurate alignment. The company would like the FCC and other interested parties to consider using the coil for HAC measurements. This document was also presented to TR-41.9. TR-41.3/95-06-029 is a presentation describing the Standard Setting Process at TIA.

TR-41.5 PREMISES DISTRIBUTION FOR MULTIMEDIA

MEETING HIGHLIGHTS:

• Preparation of a strategy document on Premises Distribution requirements for release at the September TR-41 meeting. • Liaison to other organizations impacted by premises distribution requirements, informing them of TR-41’s responsibilities and the standards activities underway in TR-41 related to those responsibilities. JOINT TR-41.5 MEETING WITH TR-41.5.1 AND TR-41.5.2

TR-41.5.1, Residential Premises Telecom Systems Protocol (dealing communication among internal residential systems and external service providers), and TR-41.5.2, Uninterrupted Powering for Residential Premises Telecom Network (dealing with continuity of operation for residential equipment and services in the event of commercial power

failures), both met jointly with TR-41.5. Such joint meetings will likely continue until the premises distribution strategy document has been completed. LIAISONS

Reports on the activities in various standards writing organizations, such as DAVIC, ATM Forum, IEEE-802, SCTE (Society of Cable Television Engineers), and T1E1, confirm that many of these groups are actively pursuing premises distribution related specifications that clearly fall under the charter of TIA TR-41. One key area of standards work conflict was identified to be in the current version of the T1E1 project proposal for very high speed ADSL (VADSL). TR-41.5/95-06-010 is the Standards Committee T1 - Telecommunications Project Proposal for network-to- customer interfaces associated with twisted-pair transmission systems capable of operating at speeds in excess of 10 Mbit/s (VADSL). TR-41.5/95-06-07 (M. Reece and S. Godo, Northern Telecom) is a liaison report from IEEE-802.14 indicating that their CATV (Cable TV) access protocol and the preliminary system reference model from ATM-Forum Residential BroadBand (RBB) group will impact the premises distribution. IEEE 802.14 has expressed interest in cooperating with TR-41.5 on the development of standards for the in-home section of their hybrid-fiber coax CATV architecture. TR- 41.5/95-06-08 contains inputs by Canada into ISO/IEC JTC-1/SC 25/WG 1 (Home Electronic Systems), addressing the need for an industry-wide collaboration on premises distribution and associated interfaces with standards development schedules that are consistent with work underway in various bodies that include TR-41. The discussion that followed the liaisons prompted the group to the following approach: • Develop a premises distribution strategy document that would address the requirements on the architecture and the migration from today’s needs to the home distribution needs of the future (e.g., ATM-based consumer devices). • Liaison to all key bodies that are impacted by premises distribution work, stating TR-41’s charter and the premises work underway and inviting their contributions and their active participation in TR-41.5. TR-41.5 S TRATEGY DOCUMENT The strategy document will be built on a proposed transition plan from the fragmented distribution solutions that exist today (i.e., separate non-interoperable solutions over various media and no multiplexing). That transition will move toward using CEBus (EIA IS-60), various media, and FDM (Frequency Division Multiplexing). Longer-term solutions may use ATM, various media, and TDM (Time Division Multiplexing). Homework assignments were accepted for various sections of the document: • Introduction (including vision, assumption, and migration strategy) • Requirements on Architecture • Environment of Architecture • Physical Architecture • Standards and Regulations • Performance • Design Considerations • Schedule and Timeline An interim meeting was approved to be held on July 18 in Alexandria Bay, NY, to develop the document. A draft document was expected to be available for general review subsequent to that meeting. The final document is expected to be completed at the September 18-22 meeting in Vancouver, BC. PRESENTATION ON SMARTHOUSE W. Washington (SHLP) was invited by the Chair to give an overview of the current status of SmartHouse, a proprietary home automation system. Key points of the overview include: SmartHouse system is being upgraded to work with existing wiring with an emphasis on twisted pairs. They are moving away from being a system integrator to become a provider of controllers and components. INPUTS ON CEBUS B. Markwalter (EIA), member of CEBus Council, stated that CEBus (EIA-IS-60) is now going through ANSI ballot. A number of vendors are already building devices and tools, and companies are already making commitments to deploy CEBus on a large scale basis (e.g., Hydro Quebec). Intellon is one of the aggressive vendors, and Nortel is teaming up with them and Cox CATV on a CATV-to-CEBus gateway for demand-side power applications for hydro utility companies.

One of the key advantages with CEBus is that its PHY layer is readily adaptable to all current and future premises media. Some believe that its Data and Network layer needs to be re-developed to fit the premises architectures for emerging services. The upper layers (from Transport to Application) are believed to be readily re-usable. However, a Common Application Language (CAL) needs to be developed for telecom. The existing CAL is basically applicable for heat, ventilation, and security type services. It is believed that the CAL developed by ECMA in their CSTA Version 2 application protocol could be adopted by CEBus. It contains telephony and data functionalities (inclujding voice mail and e-mail) required for premises telecommunications applications. It was stated that this API (Application Programming Interface) is also popular with ATM proponents too. They would like to see CSTA used as an open standard at the upper part of the API layer (i.e., software) and for vendors to continue to use their proprietary solutions (e.g., ASAI, SESA) at the lower part of the API layer (i.e., middleware). Severin Godo, Northern Telecom

TR-41.6 WIRELESS USER PREMISES EQUIPMENT (WUPE)

WCPE: WIRELESS CUSTOMER PREMISES EQUIPMENT

1200 pages of PN-3400, Wireless Customer Premises Equipment (WCPE) – Interoperability Standard, were reviewed at this meeting; PN-3400 was approved for industry ballot. Revision J is the official ballot version. Revision J was placed on the internet node (ftp://ftp.ti.org/pub/ tr41/wcpe). Sections 6 and 7.3 in WCPE Part 1 may have to be updated to agree with possible changes to 1910-1920 band channelization. This also affects Part 3, Medium Access Control Layer, Section 7.2.3.2.8. In Part 2, Physical Layer, revisions to the 1910-1920 band were made in accordance with group consensus. Conformance Testing “Part 10” has been reserved for conformance testing. An ad hoc meeting on conformance testing will be held August 2 - 3 in Boulder CO. Synchronous Data Services TR-41.6.1/95-06-59 (J. Ferranto) is a CPAP-based approach to the addition of synchronous data services. TR- 41.6.1/95-06-60, A High Level Guide to the DECT Standardization, discusses the potential conflict between STU-III signaling and Group 3 fax. An ad hoc meeting will be sponsored by NTIA/ITS in Boulder, CO July 31-August 1 to expedite the completion of the STU-III extension of CPAP (Customer Premises Access Profile). PN-3446, PCI Interoperability PN-3446, Personal Communications Interface – Interoperability Standard, was reviewed and approved for industry ballot. Ed. Note: At the interim meeting on July 31-August 1, the NSA noted that it will submit comments requesting changes to WCPE regarding security. OCDMA: ORTHOGONAL CDMA

The air interface in PN-3522, OCDMA (Orthogonal CDMA) Wireless User Premises Equipment – Interoperability Standard (TR-41.6.4/95-06-001© version .01 June, 15 1995), was updated. There are still a number of areas that have not yet been addressed. It is expected that this standard will go to ballot by the end of 1995.

TR-41.7 SAFETY AND ENVIRONMENTAL CONSIDERATIONS

T1E1.5 LIAISON

TR-41.7/95-06-04 (L. Baker, Reliance Comm/Tec) contains the proposed TR-41.7 response to the T1E1.5 liaison (TR-41.7/94-12-21) on their voltage standard, T1.315 (Voltage Levels for DC Powered Equipment Used in the Telecommunications Environment), and their 40 volt study. The liaison notes that TR-41.7 agrees to maintain consistency with T1.315. However, the infrequent lowering of voltages, at equipment 48V battery inputs, to 40 V is not an issue which TR-41.7 can address. TR-41.7 forwarded the response to the plenary for action. This liaison will be combined with those from TR-41.1 and TR-41.3 and sent to T1E1 from the Chair of TR-41.

T1E1.7 LIAISON

The Electrical Protection for Network Operator-Type Equipment Positions Standard is in final editing with ANSI. T1 Standard T1.308, ESD (Electrostatic Discharge), is now five years old and must be reviewed, revised, and reaffirmed or dropped. TR-41.7/95-06-12 (T1E1.7) is the revised T1.308 (Central Office Equipment -ESD Requirements) that T1E1 approved for ballot at the June meeting. The revision included the recommendations from the International Stan- dard, IEC 801-2, Second Edition, 1991-04. This contribution provides suggested revisions to T1.308 to include the “contact” method of system-level ESD immunity testing and to reference IEC 801-2, for the test methodology. The Protection of Telecommunications Links from Physical Stress Standard review was completed, the letter ballot comments were resolved, and it was approved for default letter ballot. IEEE-1100 LIAISON

TR-41.7/95-06-05 (W. Bush, IEEE Standard 1100 Working Group Liaison) is a liaison report from IEEE-1100 working group (Emerald Book on powering and grounding sensitive electronic equipment) to T1E1. TR-41.7/95- 06-05 includes an early draft of Chapter 10, Telecommunications Practices for review and comment to W. Bush (Teleputer Reliability Services). Copies of the existing Std. 1100 are available from IEEE. IEC-TC-74 LIAISON

The status of IEC-TC-74 Working Group 7 (WG 7) and WG 8 drafts from the last meetings was provided verbally. Copies of the drafts will be made available at the next meeting. BNTG (BI-NATIONAL TASK GROUP)

UL (Underwriters Laboratories) is going to issue an impact statement on listing UL 1459 listed equipment to UL 1950 third edition (the Bi-National Standard). The BNTG is writing that impact statement. It will be included with the TR- 41.7 minutes when they come out from TIA. UL-MULTIMEDIA EQUIPMENT LIAISON

UL is getting requests for listing multimedia equipment that is mounted on the side of the house and provides video and telephone services. A category separate from telecommunications, and others have been created to avoid conflicts. A guide page describing Communications Service Equipment UL-related issues, was handed out as TR-41.7/95-06- 11. R. Ivans (UL) also had copies made of a General Test Program for Communications Test Equipment. This was an informal document, not a contribution. CSA (CANADIAN STANDARDS ASSOCIATION) C22.2 NO. 225 LIAISON

The last meeting dealt primarily with the Bi-National Standard, CSA-950, third edition. Earthing and grounding wording was resolved with some added definitions. They intend to publish CSA-950, third edition, this quarter. It was also reported that the 225 committee was absorbed by the CSA-950 committee. SP-3210-A, I MMUNITY STANDARD

SP-3210-A closed on June 13 with one “NO” vote with comments. The comments had to do with ground planes and other minor technical issues associated with testing procedures. The WG had consensus that some the comments were technically flawed and should not be accepted. TIA policy requires that we go to default ballot if the “NO” vote is not withdrawn. Because of the WG and TR-41.7 consensus, if the “NO” vote is withdrawn, SP-3210-A can be published as ANSI/TIA/EIA-631. There was discussion about SP-3210-A and the FCC promotion of, and positions on, the standard. FCC staff will be meeting the week of June 19 at TIA headquarters with TIA staff to discuss the promotion of the standard. The WG Chair was invited to attend. PN-3283, ESD The ESD proposal is in TR-41.7/95-06-10 (C. Tenorio, AT&T). There was discussion on the numbering of IEC- 1000-4-2 (formerly IEC 801-2, second edition) sections and issue numbers. A question on the air pressure in section 4.2.7.4 was raised: should the 86 kPa be 68 kPa? The following items were agreed upon: • Section 4.2.7.2’s title was changed to “Installation, Maintenance, and Repair.”

• D. Smith (AT&T) will rewrite footnote 2 on page 3 to include a more complete discussion of the ESD Association 14.0 draft and the high frequency characteristics of the waveform. • The word “charging” was deleted from footnote 3 on page 3 as unnecessary. • G. Wong (Northern Telecom) will check on the air pressure lower limit in section 4.2.7.4 and the CENELEC (Commission Européenne de Normalisation Electronique) required ESD voltage levels. • Wrist strap jacks was added to the list of possible test points on page 4, and the sentence below the list was modified to add “with the door open or removed” after the word “tested.” • In section 4.2.7.4, “(1)” (if appropriate) was removed requiring the type 2 ESD surge to be applied to all equipment. • In section 4.2.7.4, item (3) on page 5 will be changed to require 10 discharges of each polarity. This eliminates the need for “(5)” and footnote 5 at the bottom of the page. • D. Smith will write a short appendix giving examples of different types of failure modes for several equipment types, such as cordless phones and PBX equipment. TR-41.7/95-06-012 is the T1E1 Central office ESD standard which is going out for ballot. There was a discussion pointing out that the requirements in this T1E1 Standard are more severe than those being proposed for TIA-571 (Environmental Considerations for Telephone Terminals). The members were asked to discuss this disparity with their companies. TR-41.7/95-06-08 (C. Tenorio, AT&T) proposes changing the title of section 4.3 to “Touch Currents for Perception.” The previous title, Touch Currents, is generally understood to be safety related while those in TIA-571 are not. TR-41.7/95-06-07 (C. Tenorio, AT&T) addresses section 4.2.6.1.1, EMI (Electromagnetic Interference). It proposes using the requirements from ANSI/TIA/EIA-631 (SP-3210-A). C. Tenorio will rewrite this section for the next meeting using this philosophy. TR-41.7/95-06-09 (C. Tenorio, AT&T) addresses section 4.2.5.1, Surge Requirements. It proposes harmonizing the power line surges with IEC 1000-4-5 (same as the CCITT surge). The proposal for a new Type-G1 ground surge was withdrawn and replaced with an L2 extreme 2500 volt, 500 amp per lead, 1.2x50 microsecond surge based on using the power surge generator with a pair of 3 ohm resistors added to provide simultaneous connection to both leads and current limiting. The G2 surge in Table 2, described as abnormal, is changed to G1 extreme. C. Tenorio (AT&T) led a discussion of TR-41.7/95-06-09 covering a brief history of surges, including Bell System studies from the 70’s and the present FCC and CCITT surges. R. Baker (Reliance Comm/TEC) brought up the subject of surge philosophy. Should TIA-571 detail the environment that the protector sees or just what the equipment sees? C. Tenorio thought that TR-41.7 should deal with just what the equipment sees. R. Baker said that TR-41.7 should put a preface in the standard that specifically states that it deals with the surges that the equipment normally sees. Changes proposed to section 4.2.5.1.1 “(2)” were withdrawn. C. Tenorio discussed the difference between normal and abnormal surges in previous standards. He stated there is no such thing as an “abnormal” surge. An abnormal event would be a power line cross. TR-41.7/95-06-09 talks about normal surges and extreme surges. There was discussion on where and how to apply longitudinal surges to a telephone instrument that has no connections to the electronics other than tip and ring but has external floating conductive surfaces. C. Tenorio, R. Ivans (UL), J. Brunssen (Bellcore), and R. Baker (Reliance Comm/Tec) were the main contributors to this discussion. For now, reference to “green wire ground” will be changed to “external ground.” J. Brunssen suggested that the P2 surge, 5000V, should be 6000V to agree with 1089. C. Tenorio thought we should leave it at 5000V. J. Brunssen will investigate the voltage levels for the P1 and P2 surges. C. Tenorio had trouble generating the L1 surge with commercial generators. Before presenting TR-41.7/95-06-06 (C. Tenorio, AT&T), Appendix B - Overvoltage Rationale, C. Tenorio provided some history. Originally, the telecommunication industry thought that the equipment should protect the building wiring. The overvoltage requirements in UL-1459, edition 2, reflect this position. The computer industry disagreed, saying that the building protector should perform this function. Due to lack of evidence to the contrary, UL- 1950, edition 3 (the Bi-National Standard), does not require the equipment to protect the building wiring, only the

14 Vol. 6.6 Copyright © CSR 1995 September 1995 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS wiring from the wall jack to the equipment. For this reason, the rationale for the overvoltage test needs to be changed. There were 6 changes proposed in this contribution. There was a distinction between a four wire phone (e.g., digital access circuits) and a two line phone. In the past, people got confused and applied the four wire test to a two line phone. TR-41.7/95-06-06 spells out clearly which test gets applied to which phone. There was discussion about requiring a 600V on-hook dielectric test between pairs of tip/rings on equipment. This should be added to UL tests as well as this Appendix in TIA-571. PTCs and fusible resistors were added as examples of current limiting devices in B8 on page 5 since they are so common. C. Tenorio (AT&T) agreed to be the editor for the TIA-571 revision. MAINS HARMONIC CURRENT

E. Eckert (Northern Telecom) will provide an update on international mains harmonic standardization. TR-41.7 is looking for volunteers to be the bulletin board system operator for this subcommittee. E. Eckert tentatively agreed to do this if approved by his management. R. Baker (Reliance Comm/Tec) will do it in the interim. TR-41.7.1 NORTH AMERICAN TELECOMMUNICATION EQUIPMENT SAFETY R. Ivans (UL) was approved by his company to serve as the TR-41.7.1 Chair. BNTG (BI-NATIONAL TASK GROUP)

TR-41.7.1/95-06-07 is the latest revision of the impact bulletin describing the impact on telephone equipment of the third edition of UL-1950 and CSA-950. Comments from members will be obtained by R. Ivans, and a new draft will be generated. UL will issue the bulletin when finalized by TR-41.7.1. A copy will be provided to CSA-950 for their use as they see appropriate. The next, and probably the last, revision will be included with the TR-41.7 minutes when they are issued by TIA. Listed/Certified equipment complying with UL-1459/CSA-#225 may remain in manufacture unchanged until the year 2005, when those standards become obsolete. US-TAG/TC 74/WG 7 AND WG 8

C. Tenorio (AT&T) provided a verbal report of both working group meetings. A number of issues were approved to move forward, including: • Wall mounted equipment mounting strength tests, • Leakage current summation for equipment on a bus, • Allowing HB materials (a type of plastic used on telephones) in conjunction with 15 VA limiting, • Enclosure bottom exemption for RAL [Restricted Access Locations]. There were other items, such as acoustic limits and electric strength testing, which continue to be worked. A few items were put on hold, including TNV (Telephone Network Voltage) high voltage current limits and coaxial cable connections. C. Tenorio agreed to provide copies of the Committee drafts and information on how to provide comments to the US-TAG. The draft for Committee review of the fourth amendment should be available shortly. The US-TAG will meet the end of August. CONSULTATIVE COMMITTEE ON TELECOMMUNICATIONS (CCT)

There have been no CCT meetings since TR-41.7’s last meeting. R. Ivans (UL) will provide a copy of the Mexican deviations to IEC-950 at the next meeting. The next CCT Product Safety Group meeting is scheduled for June 20. TR-41.7.3 E LECTROMAGNETIC COMPATIBILITY CONSIDERATIONS

SP-3210-A T ELECOMMUNICATIONS TELEPHONE TERMINAL EQUIPMENT: RADIO FREQUENCY IMMUNITY REQUIREMENTS FOR EQUIPMENT HAVING AN ACOUSTIC OUTPUT

The SP-3210-A ballot closed June 13, the day before this meeting. TR-41.7.3/95-06-07 contains comments from AT&T and provided most of the changes made to SP-3210-A. While all the changes were editorial, those resulting in the most change follow: • In section 5.4.1 and section 5.4.2 the word demodulated is added for clarity.

• The first paragraph of section 5.4.1 was changed to read, “The demodulated acoustic output from the handset of the EUT shall not exceed 55 dBSPL...” • The word demodulated is also added in front of “acoustic Output” in the third line of that paragraph and in the second paragraph of section 5.4.2. • The first paragraph of 5.4.2 is changed to read “...the demodulated signal output measured...from 500 kHz to 2 MHz where the demodulated signal shall not exceed...” TR-41.7.3/95-06-05 (R. Marshall, Marstech) contains comments from Marstech and requests the addition of G- Strip cells to perform the radiated immunity measurements. TR-41.7.3/95-06-06 (H. Mertel) also contains comments, and requests shielded rooms to perform the radiated immunity measurements. To accommodate these comments, the title of section 6.1.1 was changed to “Test Facilities,” and the first paragraph was changed to “...(TEM) cell, Gigahertz Transverse Electromagnetic (GTEM) cell, or other test facilities which illuminates the EUT(Equipment Under Test) with the specified field strength.” TR-41.7.3 agreed that while these facilities may well be usable, they could not be added to the standard without adding detailed testing procedures for their use over the frequency range as was done for the TEM and GTEM cells. The addition of such procedures would delay the release of the standard by several quarters. TR-41.7.3/95-06-06 raises valid questions about the characteristics of the FCC/ANSI LISN (Line Impedance Stabilization Network). To resolve this issue, unnecessary and possibly wrong information about the LISN was removed, including Figure 1 and the note and second sentence of section 6.3.1.1. The 10 kHz in the first sentence of section 6.3.1.1 was changed to 150 kHz to match the lower frequency in the requirements. TR-41.7.3 agreed that no needed information was lost by these changes. TR-41.7.3 disagreed with the claim in TR-41.7.3/95-06-06 that conducted tests should be made without a ground plane. This was based on TR-41.7.3s understanding of the IEC and CISPR (International Special Committee on Radio Interference) procedures for such measurements. This issue and the desire to use a shielded room for radiated immunity testing prevented all the issues raised by this “NO” vote to be resolved. The submitter will be contacted and requested to withdraw his “NO” vote based on the TR-41.7.3 reasons for lack of resolution. If the “NO” vote is withdrawn, the standard can be published based upon the consensus and TR-41.7’s approval of the these recommendations. Otherwise, the Standard will go out for a default ballot. TR-41.7.3/95-06-09 (D.N. Heirman, SC-5 Immunity Chair, Standards Committee on Electromagnetic Compatibility) contains comments from members of various ANSI ASC C63 Subcommittees on behalf of Subcommittee 5 (SC-5) which deals with the immunity of TV and VCRs as well as such home entertainment electronics as telephones. TR-41.7.3/95-06-11 (Bellcore) contains comments from Bellcore’s “YES” ballot. INTERNATIONAL ACCEPTANCE OF TIA-631 (SP-3210-A)

TR-41.7.3/95-06-010 (G. Wong, Northern Telecom) is a request from the Editor of SP-3210-A to have TIA request the international community to adopt this standard. These standards bodies include IEC, CISPR and CENELEC. LeRoy Baker, Reliance Comm/Tec

TR-41.8 COMMERCIAL AND RESIDENTIAL PREMISES WIRING

TR-41.8.1 C OMMERCIAL PREMISES WIRING

TIA/EIA-568-A S TATUS REPORT

The TIA-568-A (SP-2840-A-1, Commercial Building Telecommunications Cabling Standard) default Ballot was returned May 13 with no negative comments. There was one editorial item not related to the default ballot. The default ballot items will be incorporated and then sent to ANSI for approval. TR-41.8.1/95-06-S is a letter from D. Ballast (BICSI, and UT Austin) requesting an explicit disallow of tip/ring reversal (split pair) in TIA-568-A. It will be considered by the Connector Task Group. TIA-568-A will not be published until September. Global Engineering is selling the “ballot copy” (SP-2840-A) with 50% credit toward the final copy. Global’s full standards catalog is available free of charge (800-854-7179).

LINK PERFORMANCE TASK GROUP TR-41.8.1/95-06-C is Draft 11 of TSB-67, Link Performance Transmission Specification for Field Testing of Unshielded Twisted Pair Cabling Systems. Bay Networks requested that TR-41.8.1/95-06-R, Additional wire map error example, be included as an example in TSB-67. However, it was decided not to include it because the mapping error given would be picked up by the testers as a split pair. Ballot Resolution The summary report of ballot responses was presented. It accommodated all technical comments and resolved negative ballots. No new contributions or technical issues have been raised which need to be addressed. All technical issues were resolved satisfactorily. AMP’s comments were considered technical, but not major. Resolution was satisfactory to all. Fluke requested removal of accuracy numbers from the parameter tables, including calculation of level I and level II accuracies for both basic link and channel. Several manufacturers objected to the new accuracy table, in particular the new level II channel specifications. Discussion proposed four possible compromises: 1. Add note to accuracy table stating these are not requirements. 2. Revert to draft 11’s treatment of accuracy. 3. Delete channel accuracy for Level II and basic link accuracy for Level I. 4. Remove the accuracy numbers entirely. Proposal #4 offered the least objections, since no consensus was obtained on the other options. However, the majority expressed disappointment in deleting these accuracy values. A possible compromise solution was proposed to add the following to replace page 15, line 34 through page 16, line 10: “For example, using the equations in A.3, the measurement accuracy for the basic link, Accuracy Level II, is calculated to be ± 1.6 dB for NEXT measurements and ± 1.0 dB for attenuation measurements. Other combinations of accuracy level and link configurations can also be determined by using the equations in A.3.” It was finally agreed to accept this compromise solution. New Editorial Issues Pass/Fail Limits and Reporting: All the variations for limits and pass/marginal pass/fail reporting in draft 12 were discussed. A proposal was made to change 6.1 (general reporting) by replacing paragraph 6.1 lines 5-12 with the following: “A Pass or Fail condition for each parameter shall be determined by the allowable limits for that parameter. The test result of a parameter shall be marked with an asterisk (*) when the result is closer to the test limit than the accuracy of the tester. The test instrument manufacturer shall provide documentation as an aid to interpret results marked with asterisks. “An overall Pass or Fail shall be determined by the outcomes of the required individual tests. Any Fail or Fail* shall result in an overall Fail. In order to achieve an overall Pass result, all individual results shall be Pass or Pass.*” This proposal was accepted. Correct Notes under Tables 5-3/5-4 • “worst-case values are limited to 60 dB” • Page 16, lines 17,18: Change “above” to “from” • Page 15, notes 1 and 2: After note 2 add “, limited by 60 dB” • Page 14, line 20: “Link Performance of” changed to “Performance of a link with” • Page 11, 6.1: Do a global scan of “test instruments” with “field testers” Title Change “technical” to “telecommunications”.

Global “TIA-568-A” to “TIA/EIA-568-A”. Recommendations on Publication/Re-ballot of TSB-67 Because of the large number of technical changes in draft 12, it was decided to send draft 13 for 30 day ballot. (Ed. note: the third committee letter ballot of PN-3287, TSB-67, closed July 28, 1995.) CONNECTOR TASK GROUP

Proposed TSB on Patch Cord Testing (Wiremold) TR-41.8.1/95-06-E, the Draft TSB on UTP patch cord testing (PN-2948, Additional Connector Specifications for Unshielded Twisted Pair Cable Networks for Unshielded Twisted Pair Cables: Non-Destructive Performance Characteristics), was presented. Patch cable preparation follows TSB-40-A (Additional Transmission Specification for Unshielded Twisted-Pair Connecting Hardware). It was decided to move the data to an informative annex. The NEXT (Near End Cross Talk) specifications are shown as TBD (To be Determined) for CAT 3, 4, and 5. The NEXT measurement test setup shows Baluns and common mode terminators at each of the four near-end pairs. There was much discussion about alternative equivalent methods. It was agreed to add far-end detail to the figure, and to expand on the paragraph allowing alternative methods. There was disagreement over the use of CMTs (Common Mode Termination). It was agreed to change 50 to 75 Q. There was an argument to leave CMTs out and then use performance in the link as a referee to determine satisfactory patch cord performance. No consensus was obtained, so the document will show that the issue is for future study. It was accepted that both differential and CMT cases should be looked at for continued test data. Another comment is to add Balun requirements. The test method measures the (near/far) terminated plug NEXT, and the (near/far) mated and terminated NEXT. Subtraction of these figures result in values for the (near/far) modular jack. Then the patch cord is connected between the modular jacks and the total NEXT is measured. Finally, the contribution due to the (near/far) jacks is subtracted from the total, leaving the patch cord’s NEXT. This has nulls, so the 20 dB line is used to extrapolate its 100 MHz NEXT intercept, which will be compared to the Table values (TBD). TR-41.8.1/95-06-F (NorTel) is a model for patch cord testing. Formulas developed in this contribution accurately support the empirical results obtained in TR-41.8.1/95-06-E (Wiremold). The NorTel formula predicts a 20 dB NEXT slope modulated by a delay function which gives the resonance “nulls” pattern associated with the length of the patch cord. The formulas were adjusted to give the same 29 dB value of extrapolated 100 MHz NEXT as the empirical data. The contribution concludes that a line with a 20 dB/dec slope can be drawn connecting the peaks in the measured NEXT of a patch cord to isolate the first part of the equation from the second and to determine intercepts. The effect of cable NEXT contribution (added to connector model) is a dampening of the modulating function as the cable length increases, which is essentially fully damped out beyond 15 m. The 20 dB slope comes from the connectors; as the cable gets longer, the slope changes to 15 dB. TR-41.8.1/95-06-G, Length relationship when testing patch cords (Wiremold), was discussed at length, however a handout was not available. The proposal from IEC JTC1 on patch cord testing (TR-41.8.1/95-06-H) was reviewed. It is essentially the same as the Wiremold contribution (TR-41.8.1/95-06-E), except the modular jack “de-embedding” process is not done. Instead it sets limits according to this formulas for the connectors and the cable, allowing for an additional 2 dB. Some members of the group favored this method, but the majority of the contributors doing patch cord studies favored the “de-embedding” method. One solution is to use the previous method for patch cord measurement, and this method as the referee using the link. The Task Group will consider the proposal as part of the overall picture on links. TR-41.8.1/95-06-I, Resonance behavior of short links (AT&T), are results of a study which placed a worst-case jack at both ends (near and far) of the same link. It shows that only one poor connector is needed to demonstrate the resonance phenomena. Balance/Short Links (Round Robin) TR-41.8.1/95-06-J (DEC) is a summary report from the short link round robin. It includes:

• Results at 1.5, 3, 10 and 15 m • Multiple manufacturer’s components • Far end terminated differentially • Near end results with differential Balun loads, and compared to Baluns with CMT. Only one of seven connector manufacturers had a pair close to the link NEXT limit at 15 m. This worsened to approximately 10 dB over limit at 1.5 m. Bidirectional NEXT variability was worse in the worst case connectors. In a well-behaved connector, the NEXT and return loss do not have resonant anomalies and they are out of phase. In a worst-case connector, there are anomalies at the 1/2 wavelength peaks, and the normal out-of-phase relationship of return loss to NEXT is missing. The wording on this issue in draft 12 of TSB-67 is sufficient at this time, and its publication should not be held up. The Connector Task Group expects to finalize these results and have details for the next meeting in Sept. They will provide a proposal for two test methods (in addition to the connector requirements under study): 1. De-embedding test method for patch cords. 2. Jack qualification procedure using CAT 5 links <15 meters, using previously qualified patch cords (using step 1). The two tests should be included together in a TSB, studying both differential and common mode terminations. The round robin results and the JTC document will be used for step 2. CABLE TASK GROUP

NEMA reviewed future work items for TIA-568-A (TR-41.8.1/95-06-K). They would like to select a number of these items regarding wire and cable for their own work. Non-NEMA members of TIA should contact NEMA to be included in this work. TIA will provide and the NEMA Committee will accept input from TIA TR-41.8.1 on what is needed. Part of this work is harmonization of cable standards between NEMA, ANSI, ISO/IEC and TIA-568-A. The resulting Standard will be published as ANSI document. B. Tuthill (UL) will act as liaison between NEMA and TIA. The Cable Task Group assigned one proposal/study to the NEMA task list in TR-41.8.1/95-06-K. TR-41.8.1/95-06-L is Hitachi’s proposal to add FEXT (Far End Cross Talk) requirements for multi-pair cables. In multi-pair cables, there can be multiple systems transmitting in both directions, and any receiver can see the effects of both NEXT and FEXT. For example, a 25 pair cable system could be typified by a receiver with the power sum of 12 NEXT disturbers and 11 FEXT disturbers. FIBER OPTIC TASK GROUP

Draft 8 of PN-3523, Centralized Optical Fiber Cabling Guide, was approved by TR-41.8.1 but rejected by the TR-41 plenary because the cover page stated that this was a “working document” and subject to change. TR-41.8.1/95-06-N is Draft 9 of PN-3523, Centralized Optical Fiber Cabling Guide, which will become a TSB when published. The additions/differences between draft 8 and draft 9 include an update of the cover page and editorial changes in section 4 (including the definition of pull-through cable). It was agreed to send Draft 9 of PN-3523 for letter ballot with the above corrections. (Ed. note: the Committee letter ballot closed July 26, 1995.) It was agreed to ask TR-41 for permission to hold a meeting in August in Washington, if necessary, to resolve any comments returned from the letter ballot. OPEN OFFICE CABLING TSB

TR-41.8.1/95-06-O is Draft 10 of PN-3398, Additional Horizontal Cabling Practices for Open Offices (to become a TSB). It was approved for committee letter ballot (Ed. note: the committee letter ballot closed August 12, 1995). Annex A of Draft 10 PN-3398 has been included in TIA-569-A, Commercial Building Wiring Standard for Telecommunications Pathways & Spaces. The issue of bend radius has not changed and is still an open issue in TIA- 569-A. SCTP (SCREENED TWISTED PAIR) TASK GROUP

TR-41-8.1.95.06.Q (AMP, Inc.) is Draft 7 of the TSB-xxx ScTP (Screened Twisted Pair). It was agreed to edit paragraphs 4.2.3, and 6.2.4 and delete 4.3.1. Paragraph 6.2.4 describes connector shield effectiveness in terms of overall shielding degradation by emissions measurement using a reverberation chamber. The task group is looking for alternative test methods. It was agreed to change “D.C. path” to “direct connection” in several places to clarify the intent and avoid confusion with dc (direct current).

POWER SEPARATION TASK GROUP REPORT

A report was given on the proposed changes to TIA-569: plan A is to work on creating a new table/list and informative annex by September, plan B is to minimally modify paragraph 10.3. The Task Group has not finalized their position. LIAISON REPORTS

• International Meeting SC-25 Working Group: TR-41.8.1/95-06-M (SC-25) is a Liaison letter to SC-46 on CAT 6 cable. The international committee sees no justification for Category 6 cable, especially considering that the cable is a part of the link with other components. The performance of the link is determined by the worst component. This subject was discussed and the Chair responded to questions. TR-41.8.1/95-06-D is an ISO/TEC JTC1 SC-25 / WG3 Liaison Statement on Link Definitions. • IEEE Liaison: IEEE specified a new work item which differentiates between “alien crosstalk”, which is external/ambient noise coupling, rather than “self-crosstalk”, which is coherently coupled from transmitter to receiver (such as the NEXT measurement defined in TIA-568-A and TSB-67). Both rms (ambient) and transient noise should eventually be a test tool measurement requirement in TSB-67. • ISO/IEC JTC1 SC25 draft standard DIS 11801 Generic Cabling for Customer Premise: The release was flawed. It has been withdrawn and reprinted and will be released again, JTC1 will approve and publish in approximately 2 weeks. New documents, planning and installation guide, an administration document, and a low voltage cable shielding practices, are being started. OTHER MEETING HIGHLIGHTS

S. Hoyler (TIA) reported on administrative items: There is concern over controlling the size of the meeting, number of distributions from TIA, voting vs. non-voting membership, and payment of dues. There are additional concerns with copyright violations of TIA documents. S. Hoyler passed out a document defining copyright permission. A copyright statement will be required on the inside front cover of all draft copies. It prohibits distribution of draft documents via Internet and to the press. Additionally, draft documents will no longer carry the final document number. TIA has a BBS Service. Although there is a dial-in modem, TIA member companies should use e-mail to get meeting notices, etc. Proposal for Contribution Deadline A proposal was made to have a TR-41.8.1 contribution deadline of one week before meeting. Contributors must submit a title and synopsis to the meeting chairman (P. Kish, 514 855-4111), who would then assign a document number to the contribution. This procedure would allow for a prepared list of contributions prior to the meeting, as well as enabling contributions to be properly identified prior to copying. 70 copies should be brought to the start of the TR-41.8.1 meeting, plus 30 more if the contribution will also be provided to TR-41. General agreement to these procedures was obtained; details will be worked out by the chairman. It was noted that this could be handled more easily using the TIA BBS service. Harmonization of Terminology on Cabling Runs Harmonization of terminology on cabling runs was requested by ISO/LEC SC25 WG3. New information was presented from ISO; it was discussed and rejected. • Basic link: International documents show the same basic link as TSB-67, except the test equipment cables are excluded. • Horizontal Link Model is the same as a channel in TSB-67, with equipment and work area cables excluded. The models were not well received by TR-41.8.1 as they differ from the TSB-67 models by not including the equipment cables. • Horizontal Channel Model is the same as the channel in TSB-67. Structure of New TIA-568-B Document One suggestion is to break the new TIA-568-B document into sections for separate updating, balloting. Two additional sections would be created: first and “General”, which would be followed by lettered sections. The General section would include chapters 1-9 plus content/revision of each of the attachments. A suggestion was made to use the EIA- 455 series as a model. (Ed. note: the EIA-455 series are Fiber Optic Test Procedures [FOTPs], from TIA’s Fiber Optic committees. The series includes many individual test procedures, identified as EIA-455-001 through TIA/EIA- 455-190. TSB-63 is a reference guide to assist with the identification of the appropriate FOTP.)

TR-41.8.2 RESIDENTIAL WIRING/CABLING TR-41.8.2 is working on enhancements to TIA-570-A, Residential and Light Commercial Telecommunications Wiring Standard. They plan to incorporate coax cable requirements from SCTE (Society of Telecom Engineers). An IEC draft, Home and Building Electronic Systems - Guidelines relating to safety, was distributed. TR-41.8.3 TIA-569-A T ELECOMMUNICATIONS PATHWAYS AND SPACES Draft 13 of PN-3287, Link Performance Transmission Specification for Field Testing of Unshielded Twisted Pair Cabling Systems, was approved for a 30 day committee letter ballot (Ed. note: The ballot comment period closed July 28, 1995). PN-3523, Centralized Optical Fiber Cabling Guide, was approved for a 30 committee letter ballot (Ed. note: The ballot comment period closed July 26, 1995). PN-3398, Additional Horizontal Cabling Practices for Open Offices, was approved for a 30 day committee letter ballot (Ed. note: The ballot comment period closes August 12, 1995). PN-2950, COMMERCIAL BUILDING WIRING STANDARD FOR TELECOMMUNICATIONS PATHWAYS & SPACES

TR-41.8.3/95-06-001 (R. Aekins, Hubbell Inc.) is comments on PN-2950, Draft 3 (dated May 20, 1995). The firestopping section was briefly discussed. J. O’Brien (Nelson Firestops) submitted a list of editorial changes. No technical changes were discussed. It was decided to move the open office pathway/ space section from the annex into section 6. J. Nienhuis (Herman Miller Inc.) submitted a list of proposed editorial changes (TR-41.8.3/95-06-002). Because of insufficient time and resources, the pathway separation group did not reach any definitive conclusions regarding recommendations that could be made based upon the data collected to date. It was agreed in previous meetings that the June meeting would be the target completion date for this work in order to have PN-2950 out for ballot after the September meeting. As this target was not met, it was decided to change the pathway separation portion of chapter 10 to correct the known problems with it. This decision leaves two opportunities for further changes: at the September meeting, and through the ballot responses. It was reaffirmed that the 10X pathway bend radius for fiber requirement of TIA-569 would be eliminated. It was also reaffirmed that all references to conduit size would be changed to trade size notation, not English/metric units. The subject of NEC conduit fill requirements was raised again. It was reaffirmed that TR-41.8.3 would work closely with NFPA (National Fire Protection Agency) panel 16 regarding interpretation of fill for communications cable. It was reaffirmed that the goal for the September meeting is to approve PN-2950 for ballot, assuming that all technical issues are resolved.

Ed. note: TR-41.8.3/95-08-CSR-1 is PN-2950 Draft 4, dated August 17, 1995. TR-41.8.4, CUSTOMER-OWNED OUTSIDE PLANT The TR-41.8.4 Working Group discussed the architecture of customer-owned campus outside plant. The outside plant facility was determined to be comprised of two components: the pathway and the cable. TR-41.8.4 agreed that cabling extending from the first interior building termination to the exterior of a building (the campus) is a part of outside plant cabling. The pathway demarcation between outside plant pathways and inside building pathways was agreed to be the building’s first pathway emergence from the exterior of the building. Connecting (terminating) hardware will be used to interface various categories of cable that extend to nearby buildings such as a guard post. Based on this information, TR-41.8.4 agreed that campus outside plant connecting hardware shall be categorized. This categorized connecting hardware will include protector hardware and “through” type connecting hardware. The protection information within the standard will likely reference documents such as the NESC, NEC, and ANSI/T1E1 standards.

TR-41.8.4 distributed the IBM/ROLM outside plant document at the meeting and marked sections that they believe should be in the draft standard. D. Lockard (TelCon Associates) and B. Jensen (RCDD) will compile the information into a draft document for review prior to the next meeting (September). B. Jensen provided a contribution about right-of-way. TR-41.8.4 furthered discussion of right-of-way by attempting to define “campus.” TR-41.8.4 constructed additional information for the “campus” definition and will forward it to TR- 41.8.5 (Definitions) for consideration. PN-3339, Customer-owned outside plant facilities standard, will affect the BICSI Customer-Owned Outside Plant Specialty. It was noted at the meeting that BICSI is developing their specialty in conjunction with the standard effort. Close attention to the development of the standard should be maintained by BICSI.

TR-41.9 REGULATORY CONSIDERATIONS A. Wride (Communications Certification Laboratory) is the new Chair of TR-41.9. In her introduction, A. Wride requested everyone’s commitment to the work ahead. LIAISON REPORT TAPAC (Terminal Attachment Program Advisory Committee) has not met since the TIA March meeting. During that period, the TAPAC Technical Task Force has finalized two drafts of CS-03: Draft A, which consists of marked-up requirements and rationale, and Draft B, which contains a clean text of requirements and test methods. These have been sent out for comments; a TAPAC letter ballot is expected to go out in July 1995. TR-41.7 and TR-41.9 met on March 8, 1995, in San Francisco. Equipment failure due to power surges between the power input and the telecommunications network was discussed at length. Complaints to the FCC and a Bellcore survey indicate that registered equipment is suffering surge damage. The group concluded that the present Part 68 surge is not adequate, and they discussed ways to improve it. C. Tenorio (AT&T) was asked to submit contributions proposing an alternative surge. TR-41.9/95-06-032 (C. Tenorio, AT&T) proposes a change to the present definition of surge in the petitioned 68.302(d)(l). This surge proposal is brand new and is based on surges being applied between ac power lines and telephone connections (termed transverse surge). There were concerns about new surges being introduced into Part 68. TR-41.9/95-06-034 (C. Tenorio, AT&T) also proposes changing the present definition in the proposed 68.302(d)(l) with respect to power line surge. The present FCC Part 68 definition for the power line surge is obsolete. This paper proposes using the IEC 1000-4-5 1995 surges for ac power inputs. The IEC surges have about twice the energy of the FCC surge for the same voltage level. There was a concern at this meeting about any adoption of non-standard surge wave shapes that would create difficulties in test equipment acquisition for companies approved under ISO 9000. Other concerns on network harm, equipment damage, and network access were also expressed. It was agreed that the members will study the proposals for discussion at the next meeting. FCC/IC ACTIONS

TR-41.9/95-06-018 (B. G. Almond, Executive Director - Federal Regulatory) is an ex parte (late filing) presentation from BellSouth to the FCC on the problem of substandard telephony wiring in homes. Crosstalk is noted as a significant problem. It proposes that the FCC adopt new standards to mitigate substandard wiring problems in homes. It is part of the proceeding docket 88-57 and was sent to TR-41.9 for information only. TR-41.9/95-06-019 (D. Bart, TIA VP Standards and Technology) is a letter from TIA updating the industry on the activities of the FCC Hearing Aid Compatibility Negotiated Rulemaking (FCC HAC NRC) committee. S. Whitesell (AT&T) reported that TIA sent out a questionnaire trying to establish the industry preference on HAC labeling. Of the 16 respondents, only one third indicated that they presently have some kind of labeling on their products, and only one fifth thought it should be mandatory. Concerning the use of date codes, opinion was evenly divided on whether date coding would solve the field identification problem. No company reported working on alternative coupling methods for hearing aids. The negotiated rulemaking has taken a change of direction in that retrofitting would not be required. In exchange for this compromise, the hard of hearing community would like to see all business sets required to provide amplification in the receive path. A further complication is that the present 12 dB amplification is not considered adequate, and the preferred 25 dB amplification introduces other problems (e.g., need for external power, singing, clipping).

H. Mar (Industry Canada) reported that a petition from B.C. Tel to transfer ownership of inside residential wiring to the subscriber has been granted by the CRTC (Canadian Radio and Television Commission). This will be done on a contract basis (i.e., the subscriber can refuse to take ownership of the wiring). PART 68 HARMONIZED PETITION/CS-03 S TATUS The Part 68 Petition to the FCC has gone through the comment and reply cycles. There were only six comments and all were in favor. TR-41.9/95-06-026 contains these comments along with TIA reply comments. In its reply, TIA suggested that, since industry support is unanimous, the FCC should proceed directly to a Final Order and skip the usual NPRM (Notice of Proposed Rulemaking) procedure. C. Berestecky (AT&T) and some TIA members will meet with L. DuBroof (FCC) on July 18 to encourage the FCC to move this case forward. TR-41.9/95-06-027 is a list of comments on the Petition prepared by C. Chamney (Sprint Ltd.) for consideration by TR-41.9. These comments were reviewed, and B. Corey (Industry Canada) was asked to make corrections on pages 34 and 35 of Appendix B of the Petition to add the tariffed data rate of 38.4 kbit/s and any appropriate secondary channels. This and all other changes suggested in the contribution were editorial and will be addressed by the editorial group. C. Chamney requested that items 1, 3, and 4 under the Substantive Errors heading of the contribution be deleted. TSB-31-B PROJECT PROPOSAL

TR-41.9/95-06-028 is a Project Request and Authorization form for revision of TSB-31-A (Part 68 Rational and Measurement Guidelines) to align the test procedures with the harmonized Part 68 Rule. It must be submitted from TR-41.9 to TR-41. The group approved the form with the following changes: • The project title was changed to TSB-31-B • The completion date was changed to December 31, 1995 • Typographical revisions were made to the contact address Thus, the group was committed to have a tentative final draft of TSB-31-B by year end. G. Slingerland (Mitel), who had accepted the Chief Editor responsibilities at the last meeting, will not be able to work on this project. D. Hayes (AT&T) agreed to take over this responsibility. The working teams are: • Team 1 - Sections 5, 6, and 7 -- J. Christiano, T. Russell, D. Dulmage, D. Moon • Team 2 - Sections 8, 9 and Appendix C, D, E -- J. Bipes, A. Daughtry, S. Crosby • Team 3 - Sections 10, 11, and 14 -- D. Hayes, E. Guevara, D. Dulmage • Team 4 - Section 13 and Appendix F -- B. Corey, P. Adornato, A. Wride The current software version of TSB-31-A will be used as the starting point. A. Wride will make copies available to each team contact (i.e., J. Christiano, J. Bipes, D. Hayes and B. Corey). TR-41.9 CHARTER

TR-41.9 has been requested by TR-41 to review and resubmit the TR-41.9 charter. TR-41.9/95-06-029 contains the current TR-41.9 charter. TR-41.9/95-06-030 proposes five elements to be included in the charter. TR-41.9 had the following comments: • Regulatory Matters is too broad a title, future direction should be considered • Combine items 1 and 2 since TSB-31 has already been produced • Items 3, 4, and 5 may be left as is • Add a new item: Monitor the activities of CCT (Consultative Committee - Telecommunications [Trilateral]) and similar groups as they relate to Part 68 and CS-03, and provide technical input as requested The following members volunteered to prepare the new charter for presentation to TR-41.9 at the next meeting: S. Crosby, P. Adornato, and D. McChesney. TIA SEMINAR AGENDA

In anticipation of FCC approval of the Part 68 Petition, TIA is planning a seminar for February 28-29, 1996, followed by an Industry Meeting on March 1 in Fort Myers, Florida. TR-41.9 was asked to produce and support an agenda for this event. TR-41.9/95-06-031 contains a TIA Seminar agenda from the March 4-5, 1992, meeting. The following ideas were offered: • A suggested seminar title was Global/International Market Access and Harmonized Standards • Presentations on changes to Part 68, TSB-31-A, Form 730, CS-03, and CP-01 • A guide to TSB-31; do not assume that everyone is familiar with TSB-31 • Presentation on harmonization experiences

• Presentation on immunity standards (RFI) • Update on HAC • Direction and philosophy of regulation • Update on inside wiring with emphasis on the crosstalk problem • Presentation on cable TV/telephony convergence: the crossbreeding of cable and telephony wiring • Update on ISDN rules and other pending issues (e.g., stutter dial tone, bell tap) • Update on telephone and power line voltage surges • EU (European Union) MRA update • CCT NAFTA (North American Free Trade Agreement) update • Conformity assessment update • Mexican certification requirements (Mexican speaker) • History of Part 68 • TR-41.1/ETSI progress on PBX standards. It was noted that FCC action on the petition is needed before we can have a seminar based on harmonization. The following members volunteered to prepare a draft agenda for the seminar: R. Corey, P. Adornato, A. Daughtry, S. Crosby and A. Wride. The group was requested to complete this task by October to allow a five month lead time. EU MRA There was a meeting on April 10 in Washington. The main issues discussed were format, aim, and scope of the agreement. The US position on MRA is that mutual acceptance should be by test results. Canada, the US, and the European Commission will meet on July 6-7 in Brussels, Belgium, to provide a workshop on mutual requirements of EMC (Electromagnetic Compatibility), Telecom, and Safety issues. They will try to iron out obstacles. NAFTA CCT TR-41.9 received from Mexico a list of requirements based on parameters rather than products. This change in direction occurred at US and Canada insistence, and it will be the main subject of discussion for the forthcoming CCT meetings in Denver the week of June 19. There are still some issues concerning the interpretation of Article 1304 of NAFTA. TSB-31-B W ORK PROGRAM

Team 1 J. Christiano (Inchcape Testing Services) asked the group for advice on modifying the flowchart on the order of the tests of Section 5 (Reference TSB-31-A, page 26). A discussion followed on the order of the tests relative to the two required surges and the testing. It was decided that TSB-31-A be retained. Team 2 No report. Team 3 TR-41.9/95-06-037 (D. Dulmage, Certelecom, E. Guevara, Stentor, and D. Hayes, AT&T) proposes changes to Section 10 of TSB-31-A to reflect TR-41.9 proposed rule changes. D. Hayes pointed out that the main changes in this contribution are on the DC resistance test and the calculation of REN (Ringer Equivalence Number). TR-41.9/95-06-038 (D. Dulmage, Certelecom, E. Guevara, Stentor, and D. Hayes, AT&T) proposes changes to Section 14 of TSB-31-A to reflect TR-41.9 proposed rule changes. Tests for the automatic redialing requirements are missing and will be developed for the next meeting. Team 4 TR-41.9/95-06-033 (P. Adornato, Northern Telecom, R. Corey, Industry Canada, and A. Wride, CCL) proposes revisions to Section 13 of TSB-31-A. It proposes minor changes on subrate and DS1 (1.544 Mbit/s T1 Interface) test methods. Tests for Reverse Battery Answer Supervision on DS0 channels will be developed for the next meeting. TR-41.9/95-06-035 (R. Corey, Industry Canada) proposes revisions to the subrate text as well as both the subrate and DS1 pulse templates. B. Corey mentioned that the subrate templates for every rate were developed and templates for 38.4 kbit/s and secondary channels will be added. The DSI (Digital Speech Interpolation) templates for Options B

and C were derived by passing the maximum and minimum curves through the required transfer functions. It was suggested that Figure F2-1 be deleted because the Option A pulse is now part of the Rules. SPECTRUM PROPOSAL FOR SUBRATES

TR-41.9/95-06-036 (R. Corey, Industry Canada) is a proposal of a spectrum-based requirement/test method as a substitute for existing subrate DDS pulse template rules. It was submitted for information and further study. L. Baker (Reliance Comm/Tec) suggested that some Bellcore or other documents may already have used a spectrum-based approach. FCC REQUESTS

TR-41.9/95-06-020 (W. H. von Alven, FCC) is a fax from the FCC requesting recommendations for the proper setting of synthesized voice levels associated with PC modems when the PC operator has the ability to set levels. TR- 41.9 agreed that in the worst case of maximum volume settings, the card must still meet the applicable signal power requirements. TR-41.9/95-06-021 (W. H. von Alven, FCC) is a fax inviting TR-41 to revisit the policy with respect to stand- alone surge protectors with C.O. connections. TR-41.9 agreed that these devices are not electrically transparent; therefore, they must be registered due to their possible effects on compliance with longitudinal balance, leakage, on hook, and in band and out of band noise due to possible ground connections. TR-41.9/95-06-022 (W. H. von Alven, FCC) is a fax with questions regarding leakage and components rating. TR-41.9 agreed to the following: • Components which are relied upon for dielectric barriers should continue to be rated at 1000 Vrms. • Leakage current should not be reduced. TR-41.9/95-06-023 (W. H. von Alven, FCC) is a fax asking TR-41 for comments with regard to transferability of registration. It was held for further study and consideration at the next meeting. One suggestion was to look into the component registration proposal pending at the FCC Administrative Committee. TR-41.9/95-06-024© (Multi-Coil Concepts) is a fax regarding an HAC probe coil from Multi-Coil Concepts. TR- 41.9 decided that they were the wrong forum for this proposal. It was decided that it should be studied by TR-41.3. A. Daughtry (Bellcore) will submit the proposal to TR-41.3. TR-41.9/95-06-025 (D. Joffe, Integrated Network Corp.) addresses the inherent problems with the time domain approach for subrate DDS pulse shape testing. L. Baker (Reliance Comm/Tec) commented that this contribution appears to be similar to the TR-41.9/95-06-036 proposal from R. Corey (Industry Canada); however, it seems to suggest the use of less readily available equipment. It was decided that the proposal be considered by the group as a long-term work item.

THE CSR LIBRARY Copies of documents shown in boldface type can be ordered from Communications Standards Review, where not controlled. We have a large library of standards work in process and can help you locate other information you may need.

TR-41 PARTIAL MEETING ROSTER, JUNE 12 – 16, 1995, KANSAS CITY, MO Chuck Berestecky, AT&T Chair, TR-41 Richard Frank, Siemens Rolm Chair, TR-41.1 Pierre Adornato, Northern Telecom Chair, TR-41.2 Dennis Rittenhouse, U. of Waterloo Chair, TR-41.3 Jim Romlein, MIS Labs Chair, TR-41.5 Peter Bligh, Mitel Chair, TR-41.6 Leroy Baker, Reliance Comm/Tec Chair, TR-41.7 George Lawrence, AMP, Inc. Chair, TR-41.8 Anh Wride, Communication Certification Labs Chair, TR-41.9 3M Donald Coy Industry Canada Henry Mar ALCS Div. of WILTEC Jack Wilson Iwatsu America Bob Chrostowski AMP Inc. Ned Sigmon Kreager Associates, Inc. Paul Kreager AT&T Tony Caggiano KRUNE Jamie Zartman AT&T Steve Crosby Leviton Mfg. Pete Newman AT&T C. David Hays Leviton Mfg. Doug Sandberg AT&T Ed Polansky MIS Labs Peter Martin AT&T Masood Shariff Mitel Robert Hamilton AT&T Doug Smith Mitel John Needham AT&T Chuck Tenorio Mobile Engineering John Bipes AT&T Steve Whitesell Motorola ISG Don McChesney Bell Atlantic Trone Bishop NEC (Japan) Shigeo Fujii Bellcore John Balinski NEC Paul Weismantel Bellcore Jim Brunssen Nelson Firestops Joe O’Brien Bellcore Art Daughtry Nise West Hawaii Stephen Kuba Bellcore Charlie Sacco Northern Telecom Roger Britt Berk-Tek Dave Hess Northern Telecom Ed Eckert BICSI/UT Austin Donna Ballast Northern Telecom Alan Mears Business Comm. Svcs Marilyn Michelson Northern Telecom John Schick Canadian Stds Assoc. Sue Wellspring Northern Telecom Gary Wong Certelecom David Dulmage Ortronics Vickie Trippe Comdial Corp. John Green Panduit Randy Mortensen Consultant R.L. Pritchard Panduit Trevor N. Olsen Ericsson Dan Eckert Panduit George Rodriguez Ericsson Tony Wong RGP Consultants, Inc. Ron Provost FCC Catherine Deaton Siemens Rolm G. V. Baldwin GTE William McCoy Siemens Rolm Tailey Tung GTE Harry Van Zandt Sprint Cliff Chamney GTE Tel. Operations Richard Panko Sprint Local Tele. Div Cliff Chamney Haworth, Inc, Bryan Lundgren Steelcase Inc. George Weller Herman Miller Jim Nienhuis Stentor Efrain Guevara Hewlett Packard Salvador Plasencia Telcon Associates Dorothy Lockard Hitachi Telecom Ashok Kumar Telident Martin Moody Hubbell Robert Aekins The Siemon Company Valerie Smith IBM John Gage Thomson Consumer Elec. Tom Russell IBM Tom Toher TIA Shazia Azhar ICC Mike Lin UL Dave Haataja ICC David Roe UL Randy Ivans Inchcape Testing Services/DS&G Jon Christiano VA Plastics Co. Clay Hodges Industry Canada Bob Corey

26 Vol. 6.6 Copyright © CSR 1995 September 1995 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS REPORT OF THE SECOND MEETING OF THE JCG ON AVMMS (AUDIOVISUAL/MULTIMEDIA SERVICES), JULY 3 – 5, 1995, GENEVA The Joint Coordination Group (JCG) on AVMMS (Audiovisual/Multimedia Services), convened by TSB collective- letter 6/15 of 5 April 1995, held its second meeting in Geneva on July 3 – 5, 1995, under the chairmanship of M. Yamashita (NTT Japan, Vice-chairman of Study Group 15). It was noted that ITU-T SG 14 has become member of the JCG. After one year since its first meeting, the main objectives of this meeting were to: • Review the current status of studies on AVMMS carried out in relevant Study Groups • Review developments outside ITU and discuss relationships with Forums/Consortia • Discuss framework for multimedia Recommendations • Coordinate work plans and Questions in the relevant Study Groups and propose recommendations to the relevant SGs TD-3 (J.M. Fanjul, Vice Chair WP 2/TSAG) summarizes the outcome of the discussions held by WP 2/TSAG (Work Program) on various issues related to the work program of ITU-T (a database that coordinates the ITU standards work). This report also lists the following ITU e-mail servers:

Study Area Server address Video on Demand [email protected] Corporate Networks [email protected] Open Networking [email protected] Access Networks [email protected] Intelligent Networks [email protected] Transmission Networks (SDH) [email protected] Satellite Personal Communications Networks [email protected] Information Infrastructure [email protected]

To subscribe to any of the above, send e-mail to [email protected] with subscribe in text. REVIEW OF THE WORK IN RELEVANT STUDY GROUPS

SG 1 reported that due to early information exchange between SGs 1 and 13, the clarification of multimedia services from the user point of view, as discussed in the context of draft Recommendation F.700 in SG 1, is already reflected in SG 13’s draft Recommendation I.375 on network capabilities to support multimedia services. This is considered to be a good example of information exchange between SGs at an early stage of development of Recommendations. In reference to the agreements made at the first meeting of the JCG, SG 8 reported that they have done their homework on IMS (Interactive Multimedia Services), and have drafted and approved a “Multimedia Information Services” work plan (see JCG Report Annex 1, same as TD-21, Appendix 1); SG 8 called for stronger support by other SGs and ITU- T members. ITU-T SG 11 reported on its activities including discussions on signaling requirements to support VOD. It was noted that information exchange between SG 11 and DAVIC is ongoing. REVIEW OF DEVELOPMENTS OUTSIDE THE ITU AND COMMUNICATIONS WITH FORUMS/CONSORTIA

Mr. Rausch (Deutsche Telekom), the liaison from DAVIC to JCG/AVMMS, reported on the activities of DAVIC by making use of their press release. This opened discussions on the exchange of information between ITU and Fo- rums/Consortia, in particular with DAVIC (TD-23 provides additional information on DAVIC work and schedules). The discussions are briefly summarized below: Suitability of Establishment of Communication Process DAVIC is intending to start works on conversational services in the next phase of their work. This news was received by the delegates as generating an increasing risk of duplication of work between ITU and DAVIC.

Implementation of Information Exchange It was pointed out that “formal” communication between ITU and Forums/Consortia should not end in some “contact person” bringing papers from one group to another. Some of the discussions were: • Exchange of information is only a means to progress the work; its “ends” should be considered. • The fact that consensus is reached in Forums/Consortia would hopefully mean that the same proposal could get a similar amount of support in ITU, and thus it is nearer for adoption in the ITU as international standards. ITU member organizations are encouraged to submit consensus-reached-proposals, as appropriate, to the relevant SGs of the ITU. • The above does not mean that the ITU is going to give unconditional rubber stamps to these inputs. In some cases the experiences in the SGs and Forums/Consortia are different and the SGs may need to re-examine the technical implications of the proposed standards. Speed of Standardization Works Discussions led to some observations as to the speed of standardization in ITU and Forums/Consortia. One observation was that the ITU can be as speedy as Forums/Consortia if it could succeed to generate the momentum, attract the right experts/editors, and exploit the ITU procedures. Some good examples of this are the PSTN videotelephony standardization in SG 15; V.61 and V.8bis in SG 14; and T.85 in SG 8. However, there are many obstacles in reality. One example is the requirements for translation and the long interval between SG meetings. Correspondence to DAVIC It was agreed to authorize the Chairman of ITU-T SG 15, the lead SG of the JCG, to send correspondence to DAVIC, which is contained in JCG Report Annex 2. This describes the scope of the work in the ITU (TD-15rev) and supports an on-going working relationship. FRAMEWORK FOR THE NEW QUESTIONS AND THE SG STRUCTURES

Within the present framework of Resolution No. 1 (Section 7), Questions are of an ongoing nature, and are not necessarily subject to updating or creation every four years. Furthermore, according to the guideline in Res. 1, Questions should be drafted in a target oriented fashion, indicating the deliverables and the target dates. This would make it easier to identify any overlap between the works conducted under each Question. In the absence of information about the works in the SGs concerning creation/revision of Questions, it was not possible for the JCG to open discussion on possible harmonization of Questions. For the future it is strongly requested that the SG representatives distribute the information to the JCG members when new Questions or revisions are made in the Study Group, so that harmonization of Questions can be achieved. JCG Report Annex 3 contains the list of relevant Questions currently studied in the various groups. Some preliminary discussions took place on the possible restructuring of SGs from AVMMS’ point of view. The JCG/AVMMS recognizes the following (present) centers of MM-competence: • SG 1 MM-Services, applications, user needs, human factors, quality of MM-service • SG 2 MM-Traffic engineering • SG 3 MM-Tariffing • SG 7 MM-Security Framework, MM-Messages, MM-infrastructure over data networks • SG 8 MM-Components on still image coding, Interactive MM-Retrieval (Terminals, Protocols, in case needed within the ITU-T APIs between Communication and Application Components), MM-Teleconferencing, MM- Document Handling • SG 9 MM-Broadcasting over Broadband/ Cable Networks • SG 11 Network Signaling needs of MM-Services and Applications • SG 12 MM-testing evaluation • SG 13 MM-Network architecture and infrastructures • SG 14 MM-modems, MM-Start-up (PSTN, Other Networks), low complexity Voice/Data centric PSTN MM- Platforms, Interfaces between MM-System-Component-Boxes (MM-DCE/DTE, Dataports [e.g., PC linked to MM- capable communication terminal]),

• SG 15 Conversational MM (e.g., Videophone) over all type of networks, Speech/Audio and Video Coding, Transmission Systems aspects of MM • ITU-R SG 10 MM-Broadcasting • ITU-R SG 11 Television Study Groups are strongly encouraged to take into account the above distribution of competence in their MM-related work. Nobody would claim that the present structure is perfect and that there is no room for improving it. In case we are to consider restructuring, there may be several options, starting from “minor peripheral corrections” to drastically changing to form one “MM Study Group.” However, in any case, it was felt necessary to make a bottom-up approach by identifying the problems we currently face in terms of coordination among SGs. RECOMMENDATIONS FOR COORDINATION AMONG SGS TD-16 (N. Kenyon BT) and TD-21(I. Sebestyen, Siemens) provide considerable information on issues requiring coordination by the JCG. The work plan in TD-21 proposes to develop a MM model, general architecture, define service elements, protocol elements, coding and interrelation between APIs. The goal is to reach SG approval on these issues by February 1997. This JCG work plan was accepted.

As result of the discussions during the meeting, the JCG on AVMMS has adopted a number of recommendations. The SGs are requested to take necessary steps to implement the requirements put forward in the recommendations. Adoption of More Than One Method for the Same or Common Requirement There are several cases where there is a danger of adopting more than one method for the same or common requirements. In such a case, it is the role of JCG to insist on the principle that only one solution be recommended for one job. However, for those cases where the works have progressed too far or where some manufacturers are already prepared for implementation, it may not be so simple to insist on the principle. Even in such cases, it was felt that a minimum condition needs to be demanded, namely to provide a common fall-back mode or a mechanism to select one of the methods. The above guideline was agreed to, and the following recommendations are made to SGs 8, 14 and 15. Recommendation 1 It is strongly recommended that different solutions should only be adopted if the requirements themselves are sufficiently different. In this regard, complexity does not normally constitute sufficient cause because it becomes insignificant within a year or two. In cases where SGs, having identified different requirements, are producing different solutions, they are urged to produce jointly a further single Recommendation including: 1. Identification of the alternatives; 2. Explanation of their differing requirements/ applications and any other considerations which enable a choice to be made between them; 3. A technical procedure specified such that where two connected endpoints do not have a common system, the mandatory signaling is such that this can be made clear to the users; where they have one system in common this is automatically selected; where they have more than one system in common, then an appropriate choice can be initiated without intervention by the user(s); 4. Where the two or more alternative incompatible solutions are at the “system” or higher layer (application-level?), then a common fallback should be identified. In the case that no agreement can be reached between the groups concerning point (4), the Recommendation should explicitly declare that each practical implementation should embody all the methods that are likely to be encountered in its own sector of the marketplace, as well as the automatic selection process. The JCG/AVMMS has identified the following specific cases, and asks the SGs identified to provide a first draft of the above additional Recommendation before approving the incompatible Recommendations concerned.

• System-level Recs. H.324 ,V.DSVD, and V.ASVD ( V.61); and multiplexing schemes, H.223, V.gmux (SG 15, SG 14); in this case the additional Recommendation should set out, or reference the complete dynamic process of initialization to reach the chosen application, and the matter of common fallback should be addressed. • Two or more audio coding schemes for use with digital schemes via V.34 (SG 15) • Two protocols for multipoint conferencing (SG 8, T.120 series, T.195); in this case, the JCG seeks more information, questioning whether there is overlap, as might appear from the work plan. Recommendation 2 The JCG/AVMMS endorses the existence of the following multimedia (MM) platforms with the following functionality targets: • ASVD (defined in SG 14) as a PSTN analog coded Voice/data centric MM-Platform with low complexity, low end- to-end voice delay, low data speed. • DSVD (defined in SG 14) as a PSTN digital coded Voice/data centric MM-Platform with moderate complexity, moderate end-to end voice delay high data speed, not targeted for audio-visual information. • H.324 (defined in SG 15) as a PSTN digital coded Audio-visual centric MM-Platform with higher complexity, longer end-to-end voice delay, high data speed, tailored for audio-visual information. • H.32M (defined in SG 15) as a Mobile digital coded Audio-visual centric MM-Platform with higher complexity, high data speed (delay characteristics similar to H.324), tailored for radio transmission systems. The JCG/AVMMS recommends that the scope of the above MM-Platforms should not be extended in the future in such a way that would result in an increased overlapping of functionalities between the platforms. As a case in point, the JCG/AVMMS discourages the functionality extension (and complexity increase) of the simple LAP-based multiplexing of the draft DSVD platform to carry audio-visual information. The JCG/AVMMS strongly recommends that each MM-platform shall be composed from the same components (audio, multiplex, video, control) wherever possible. A case in point is the H.32M platform which should use as much as possible the same components as H.324; DSVD should also use the same or a subset of the H.245 control, the audio coder shall be one of the SG 15 approved low speed coders. The JCG/AVMMS encourages SG 14 to look into matter of a more general MM capability exchange and selection between MM-platforms, ideally crosscutting different network types. Relationship of V.8 and V.8bis It was noted that in Appendix 1 of V.8bis an overview of the Recommendation is given, and that a separate requirement capture document was generated by SG 14 during the development of draft Recommendation. The requirement capture document itself did not have a chance of receiving comments by the users of V.8bis, notably SGs 8 and 15. The JCG requests that SG 14 takes due note of all liaison from SG 8 and SG 15 on their requirements before completing the Recommendation. Proposed Multimedia Protocol Study Related To Network-Based Services Discussion at the February 1995 meeting of SG 15 WP2 pointed to a possible case for a multimedia protocol study related to network-based services which might be offered by the telecom operators. Although the study is still in its initial stage, the work is likely to be of wide interest and should be owned by the multimedia community as a whole. Thus it is suggested that the initial considerations in SG 15 be forwarded to all relevant SGs and WPs for their examination. Potential Conflicts between ISO/IEC DSM-CC and ITU-T Protocols As the distinction between conversational and non-conversational application becomes blurred, there is a risk that protocols initially intended for each application have overlap problems. The JCG/AVMMS recognizes the following potential conflicts and requests collaboration of those concerned to achieve harmonized solutions: • T.120: Remote control and related functions (Q10/8) • T.170 Series of draft Recommendations (AVIS, Q.11/8) • T.190 Series of draft Recommendations (Corporate Document Handling - XAPI, Q.15/8) • Q.2931: Call-control matters (in SG 11) It is noted that liaisons between SG 8 and ISO/IEC DSM-CC are already underway.

MPEG-4 and the ITU-T work The JCG/AVMMS recognizes the following: • Due to the promising results of the short term (1995) solution of H.324 (PSTN Videophone), the JCG/AVMMS recommends that SG 15 put the “long term” (1998) solution on hold until a significant technical breakthrough justifies the introduction of a second generation PSTN Videophone system. • The original target of both ITU-T and MPEG was to have MPEG-4 (specifically the video part) as the long term solution (1998) for the PSTN Videophone. This goal was not achieved, MPEG-4 having changed its focus from long-term conversational to a low bitrate MM-toolbox with more store and retrieval focus (more the center of competence to SG 8). Suitable components taken from the MPEG-4 MM-toolbox (e.g., a significantly better video coder compared to H.263) might be introduced to PSTN Videophone when they become available. Joint Text MM Recommendations with ISO/IEC Based on experience of SG 8 and SG 15 in the joint standardization of multimedia related matters, the JCG/AVMMS recognizes and recommends the following: • Joint text recommendations should be avoided; it is always possible to make normative references in other ITU-T Recommendations to ISO/IEC standards and vice versa. Another option (less preferred) is – if needed – to have separate but technically aligned standards. • In reaching the above conclusion the following points were made. Joint text recommendations take longer and require that the standardization rules as described in A.23 are very strictly followed. (The procedures on cooperation with ISO/IEC are well defined in a document “Guide for ITU-T and ISO/IEC cooperation” which is attached to WTSC Rec. A.23.) If there is not sufficient discipline or knowledge of procedure on either side, then it is better not enter in joint text projects. Coordination of text, translation, updating and maintenance are very painful, time- consuming and expensive, thus they must be avoided. • Joint text recommendations to be worked out by Collaborative Interchange (one specified way of cooperation) are particularly inappropriate if the ITU-T part is only the junior partner in the undertaking (i.e., ITU has little to say, on the other hand it has to incorporate too many ISO/IEC-dictated standards requirements and constrains). FRAMEWORK FOR RECOMMENDATIONS

SG 15 representative (Dr. N.D. Kenyon, Rapporteur for Q3/15) presented TD-16 which contains the updated version of the framework for AVMMS Recommendations. TDs 9, 10, 14 and 24 contain corrections and proposals for further enhancement of the framework. Dr. Kenyon agreed to update the framework taking into account these inputs (revised version is JCG meeting report Annex 4). It was pointed out that the present work of SG 7 on security matters, as contained in TD-26 (WP5/7 Chairman), apparently does not contain items specific to multimedia, although no doubt many of those listed are applicable in a general way. It was felt that there is a need to identify any specific requirements for security (including authentication, etc.) in the provision of multimedia services such as video on demand, home shopping, etc. A tentative entry was made in the position of AV.151 of the Framework for Multimedia Recommendations, with the title “Requirements for Security Facilities in Multimedia Systems”, and SG 7 is asked, together with other relevant SGs (e.g., SGs 1 and 8) to consider formulating appropriate text for such requirements capture. Since the list of Recommendations is getting longer and longer, there was a discussion about the principles as to which Recommendations should be included and which need not. Some suggestions were made to group the Recommendations in terms of platforms used, to adopt layering method, or to separate Recommendations into core and peripheral. FUTURE WORK

It was agreed that there would be justification to hold another meeting sometime during the spring of 1996, where a major objective would be to review the whole set of multimedia Study Questions. This would most likely be either after the SG 14 meeting in March or before the SG 15 meeting in May.

JCG ON AVMMS MEETING ROSTER, JULY 3 – 5, 1995, GENEVA M. Yamashita, NTT Japan Chairman The list of participants appears in TD-24. Denmark Tele Danmark A/S H. Nielsen France France Telecom Y. Robin Champigneul Germany Deutsche Telekom AG K. Kern Deutsche Telekom AG S. Rausch Deutsche Telekom AG G. Zedler Siemens I. Sebestyen Japan Japan Y. Tawara NTT M. Yamashita Switzerland Telecom PTT M. Pralong Syria Syria N. Kisrawi UK AT&T Network Systems J. Magill BT N. Kenyon BT B. Moore BT R. Nicol USA AT&T N. Mitra International Organization UER/EBU L. Cheveau ITU TSB F. Bigi TSB J. Katona Kiss

Communications Standards Review regularly covers the following committee meetings:

CSR-R CSR-T TIA TR-41.6 TIA TR-29 TR-45 TR-30 TR-46 TR-41 ITU T: SG 8 (CCITT) SG 14 (Formerly SGXVII) SG 15 / 1 and 15 / 2

LIAISON REPORTS

G. Griffith (Rockwell) and J. Decuir (Microsoft) reported on TR-30 and Study Group 14. The US, France, and the UK voted “No” on V.8bis. TR-30 agreed to use the V.8bis Rapporteur’s current document as a basis for restarting the work. The status of the DSVD (Digital Simultaneous Voice Data) voice coding in SG 15 is that there are five candidates that have been submitted for testing. A method will be selected in September. The complexity requirement is 10 MIPS (Million Instructions Per Second) with a data rate of 8 to 9 kbit/s. The key question is quality, which needs to be equivalent to 32 bit ADPCM (Adaptive Differential Pulse Code Modulation). S. Urban (Delta Information Systems) reported on a recent ISO/IEC JTC1 SC29/WG 1 meeting in France. New algorithms for JPEG (Joint Photographics Experts Group) and JBIG (Joint Binary Image Group) are being investigated. The committee is looking at new candidates for lossless JPEG, for which nine proposals have been made. The technical goal for the JPEG lossless method is to offer 25 percent better compression than the current lossless version of JPEG. In new JBIG work, a near lossless and lossless bi-level algorithm were proposed. There are two current proposals. It was decided that the best parts of these will be merged. H. Silbiger (AT&T) reported that AIIM (Association for Information and Image Management) has not finished updates to the MS-53 bi-level image format due to the resignation of the editor. EIA-536, 537 US G ROUP 4 FACSIMILE

It has been proposed that EIA-536 and EIA-537 be rescinded. The two standards are US versions of Group 4 facsimile and are now obsolete. The ballot action on the proposed rescissions is underway. There had been no action on EIA- 538, which is functionally equivalent to T.6. S. Urban (Delta Information Systems) plans to update the document to agree with the current technical content of ITU-T T.6. The updated document will then be sent out for ballot prior to the next meeting. PN-3394, HIGH FREQUENCY RADIO FACSIMILE

TR-29/94-11-68R1 is the updated draft of PN-3394, High Frequency Radio Facsimile, dated July 18, 1995. It was changed to reflect committee letter ballot comments There were “No” votes from Lanier and Hayes. It was agreed to send the revised draft for industry ballot. PN-3194, FAX TESTING

M. Moldovan (Genoa Technology, editor of PN-3194, Fax Testing), reviewed the results of the committee ballot. Up until the meeting, the count of ballots was three ballots with “Yes” or “Yes” with comments and one “No” ballot. Additional ballots were received at the meeting. TR-29/95-02-05R2 is an updated version of PN-3194, based on the ballot comments. TR-29/95-08-42 (G. Griffith, Rockwell) is a “No” ballot on PN-3194. The paper proposes that the specification would be better positioned as a Technical Service Bulletin (TSB), rather than a standard. Rockwell’s key argument is that any test standard implicitly tightens up the standard, giving heretofore compliant devices the appearance of non- compliance. TR-29 agreed to reposition PN-3194 as a TSB. There were also the following technical comments: • The TCF (Training Check) receive test included is only one way of testing. • The application of the document for Class 1 and Class 2 devices could be misleading. It was noted during discussion that the specification will permit tests of Class 1 and Class 2 devices for T.30 protocol compliance. It was felt that text should be added to spell out the potential configurations that can be used for testing, such as the combination of a Class 1 fax device with a particular type of PC-fax software. An ad hoc group will make adjustments to the text, to address the philosophical issues, and to make specific technical improvements. The document will not be sent to the Q5/8 Rapporteurs meeting unless agreement is reached within the ad hoc group.

COLOR FAX

D. Lee (Hewlett Packard) reviewed TR-29/95-08-32 (NTT Printec, HP Labs, and Fuji-Xerox), the draft of a proposal on soft copy and palette-color extensions for Color Facsimile Standards. The main proposal, is to continue to use CIELAB as the color space for soft copy and palette-color applications, primarily because CIELAB has the flexibility to work effectively in different types of color situations. CIELAB is the color space supported in the November 1994 versions of ITU-T T.4 and T.30 Recommendations. In personal computers, color data is most commonly stored as device dependent RGB in one of many data formats. The current feeling is that it is more practical for personal computers to change color space than for hard copy fax machines. A second area of discussion notes the difference between the gamut range in the Recommendations based on hard copy devices and soft-copy devices. When data to be transmitted originates from or is intended to be output to hard-copy, the current default gamut is quite adequate. In the case where the image is synthetic or taken from a soft copy original, and intended for reproduction on a soft-copy device using the somewhat different gamut available on such a device, the default gamut range will not be adequate. The specification of a default set of gamut range and white point specifically for soft-copy facsimile is currently under study in the ITU. For the time being, use of the custom gamut range option already in G3 Recommendations is suggested. There is a second proposal to consider the use of JBIG color fax for palette applications, but this is not yet addressed in the current draft. A question was raised about the best way to handle color compound documents. The new lossless version of JPEG is intended to meet a design goal of performing well for various categories of documents, including compound text + color documents, as well as to run effectively on high speed (i.e., Pentium) PCs. TIA-465-A AND TIA-466-A

TIA-465-A, the US standard equivalent to T.4, has been released. TIA-466-A is being edited for corrections by S. Urban (Delta Information Systems). TR-29 agreed to publish a version with final editorial corrections as soon as possible and then open up a new project to create a totally up-to-date version. US POSITION ON MANDATORY ECM FOR V.34

TR-29 agreed that the US position will support ECM (Error Correction Mode) as mandatory for V.34 fax. OTHER HIGHLIGHTS

There was a request for a NSF (Non-Standard Facilities) provider code from the Salutation Consortium. It was agreed that they will be given a code to use if they are a US organization. Reference will also be provided to them about the ongoing work on extended fax negotiations. TR-29/95-08-43 (H. Silbiger, AT&T) describes a lossless and lossy compression of text images using "soft pattern matching" that was submitted to the JPEG committee (WG 1). It describes a way of making use of the information in previously encountered characters without risking the introduction of character substitution errors. Lossless compression about 20% better than that of JBIG can be obtained. AT&T has applied for patents on this technology. No action was taken. It was provided for information. TR-29/95-08-31, Enhancements to T.434 Application Reference (H. Silbiger, AT&T, same as TR-29.1/95-08- 31R2), was originally developed by J. Rafferty (Human Communications) and contains edits from H. Silbiger (AT&T). It proposes that the definition of the Application Reference tag of T.434 be modified to support use of an optional Object ID. This direction is technically consistent with X.400 messaging approaches. The paper was approved as a proposed SG 8 white contribution and will also be submitted as a TR-29 contribution to an upcoming Q8/8 (Document Transfer And Manipulation) Rapporteurs meeting scheduled in Tokyo in September. TR-29/95-08-35 (R. Lutz, IS-650 Editor, Cognisys) contains the proposed cover sheet for the MFPI (Multi- Function Peripheral Interface) material to be submitted to the Q5 Rapporteurs meeting. The decision was made that the combined document (MFPI with cover) should be sent to the Rapporteurs meeting and proposed as the basis for a recommendation. It will also later be submitted to US Study Group D as a proposed white contribution after the October TR-29 meeting. TR-29 agreed to submit TR-29/95-08-36, Add V.34 half-duplex to proposed Synchronous Modes extension to V.25ter (J. Decuir, Microsoft), as a liaison statement to TR-30. A paper on fax extensions to the Common Mail Calls (CMC) software messaging API (Application Programming Interface) was also reviewed in TR-29.2. An informal response will be sent by H. Silbiger to the author. It will be

noted that if this material is submitted later to Study Group D as a potential US position, TR-29 will need to review it again. B. DeGrasse (BJ Communications) recommended that TR-29 adopt a policy of requiring soft copy submissions wherever possible. There was general agreement. The meeting hosts will need to provide a PC. The default format will be WinWord 2.0. TR-29.1 FACSIMILE AND FILE TRANSFER PROTOCOLS There were four major work areas in TR-29.1: • New Group 3 Negotiations Method • Binary File Transfer • V.34 • Fax Routing. Several papers were proposed for submission as TR-29 contributions to the Question 5/8 Rapporteurs meeting in September. LIAISON REPORTS

H. Silbiger (AT&T) reported on the SG 1 meeting. The issue of mandatory Group 3 Error Correction Mode (ECM) was discussed. It was agreed that ECM should be mandatory for V.34, but could be overridden by the user. This will be in a liaison statement to SG 8. He also noted that Class 2 and Class 3 of Group 4 fax are officially deleted, since Teletex is now no longer supported. The related Group 4 fax recommendations will be revised. Downloading of recommendations for the ITU through the TIES (Telecom Information Exchange Services) system is now available only by subscription or by Study Group members. BINARY FILE TRANSFER

TR-29.1/95-08-31 (J. Rafferty, Human Communications) proposes that the T.434 recommendation be modified so that the Application Reference attribute may be specified either as an Object ID or a graphic string. This approach is consistent with use of the OID (Object Identifier) that is being used for X.400 messaging. It was proposed as a contribution to the September Q8/8 Rapporteurs meeting in Tokyo. During discussion, D. Duehren (Brooktrout) noted that the paper is consistent with TR-29.1’s previous direction in support of using Object IDs within T.434 Binary File Transfer, but that an additional amendment should be added to indicate the version of T.434 that is being used. H. Silbiger (AT&T) suggested that an edited version be submitted as a white contribution to SG 8, since it includes proposals for new text in the T.434 recommendation. TR-29.1 agreed to send the edited version to TR-29 for approval as a TR-29 contribution to the Q8/8 Rapporteurs meeting and as a proposed white contribution to the Study Group 8 meeting next February. TR-29.1 also reviewed plans for the disposition of TIA-614, the US version of T.434 Binary File Transfer. This document had already been approved via industry ballot pending resolution of “Yes” with comment votes. TR-29.1 decided to add the text of diagnostic messages to TIA-614 using the technical content already agreed upon for use in T.434. The diagnostic messages had previously been agreed to during earlier TR-29 committee ballots but had been inadvertently omitted from an earlier draft. The updated version will be released to TIA for publication. EXTENDED NEGOTIATIONS

J. Rafferty (Human Communications) presented TR-29.1/95-08-29 on New Fax Negotiations as a proposed TR-29 contribution to the September Q5/8 Rapporteurs meeting. The paper addresses: (1) a summary of current agreements on this topic within Question 5, and (2) proposals on open issues. The basis of the work on new negotiations is the concepts outlined in paper BET-28 from the Bethesda Rapporteur's meeting November 1994. These concepts include the addition of four new T.30 signals and the addition of code points in V.8 (and V.8bis when completed) to enter directly into the new negotiation method. During discussion, L. McIntyre (Xerox) recommended that the portion of the paper containing proposals be split out as a separate paper and include a clear set of reasons supporting the proposals. TR-29.1 agreed. The revised version of this paper (TR-29.1/95-08-29R1)was approved for submission to TR-29 as a proposed contribution to the Rapporteurs meeting. TR-29.1/95-08-33, New Coding Methods for Facsimile Information Fields (D. Duehren, Brooktrout), proposes a bit-efficient but extensible coding method for a new Fax Negotiations method. The document was not yet complete ; D. Duehren requested input from TR-29.1. The paper contains an outline for the coding of fax capabilities in groups and “supergroups.” The basic approach is to use 4 bit tags with one standard 4 bit tag reserved as a supergroup de-

September 1995 Vol. 6.6 Copyright © CSR 1995 35 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS limiter. A bit extend technique was proposed to represent current fax capabilities. A length indicator of a single octet could be used for future capabilities with an option to support field lengths that would need more octets than 256. TR- 29 authorized an ad hoc group to complete the paper and then submit it to the Question 5 Rapporteurs meeting. The final version will be placed on the TR-29 reflector. V. Cancio presented TR-29.1/95-08-40 (R. Lutz, Cognisys, representing the Multi-Function Peripheral Association, MFPA) on Advanced Facsimile Negotiation Requirements for MFPs and Dial-Up Job Submission. R. Lutz was not certain that the Job Submission approach can be accommodated within T.30, even using the proposed new negotiation scheme. It was noted that Extended Group 3 Fax Negotiations are intended to address many new requirements for fax, not just those of MFP applications. The Chair noted that the new negotiations protocol could probably be extended to support an escape into high speed mode if needed. However, for V.34 duplex fax, large amounts of data could be accommodated in the 2.55 sec frame time, whereas the protocol requirements would be different for half duplex. The Chair requested that R. Lutz submit the requirements for the MFP application, so that TR-29.1 can study whether the new negotiations method should be extended to meet these requirements or whether another approach is needed for this application. It was later noted that TR-29.2/95-08-35 from TR-29.2 addressed some of these requirements. TR-29.1/95-08-41 (J. Rafferty, Human Communications) contains a proposal on the services to be included in the new negotiations method. It proposes that all new Group 3 Facsimile Services be supported using the proposed new Fax Negotiations method, but that vendors may choose either the existing or new method for current fax capabilities. It is an expanded version of the proposal in TR-29.1/95-08-29R1. The new content summarizes the reasons in support of the proposal. TR-29approved the paper as a TR-29 contribution to the Q5 Rapporteurs meeting. V.34 FACSIMILE

TR-29.1/95-8-34 (S. Palm, Rockwell, Japan) was presented by G. Griffith (Rockwell). It reviews different possible scenarios for half duplex V.34 fax where the primary channel or control channel may need retraining. There are two ways of changing the data rate: 1) Sender can send an MPh (Half Duplex Modulation Parameters) signal to request a revised rate (changes the constellation), or 2) Full primary channel retrain. The contribution favors restricting the use of primary channel retrains to a limited set of circumstances. It was presented for information. In April, SG 14 determined modifications requested by SG 8 in March. Since then, the need for additional revisions has been noticed and will be submitted to a SG 14 Working Party meeting in October. The Chair requested that the relevant white papers (planned changes to T.30 and T.4) be submitted to TR-29 for information in October. Major issues to be resolved include: • Primary Channel Retrain - When or shall it be used? • Will V.8 be used or V.8bis? This issue is probably moot, since V.8bis is not stable now and will not be approved prior to February 1995. • Minor V.34 related issues (e.g., higher data rates and error recovery mechanisms) Per the proposal, the recipient can request a data rate change between every change (which will cause the modem constellation to be modified), but the symbol rate does not change unless a primary channel retrain is done. G. Griffith (Rockwell) noted that two connecting V.34 modems specify a range and that the highest common rate will be used. H. Silbiger (AT&T) presented TR-29.1/95-08-35 on changes to Recommendation T.90 Annex F to support V.34 full duplex. While reviewing the latest text of T.90, H. Silbiger confirmed the exact set of changes that are needed within T.90 to permit the use of T.30 Annex C for V.34 fax. This contribution is primarily directed to Q13/8, but will be sent to Q5/8 (Group 3 Fax) for information. TR-29.1 agreed to also send it to TR-29 as a proposed US contribution to SG 8. FAX ROUTING

The new project number for Fax Routing is PN-3599. Editor, J. Rafferty (Human Communications) noted that the interim standard IS-141 on Fax Routing Utilizing the Subaddress will need reaffirmation in October. TR-29.1/95-08-30 (J. Rafferty, Human Communications) proposes the addition of the Subaddress for Polling applications. Currently, the SUB (subaddress) signal may be used for fax transmit applications, but it is not available for use in Polling. This proposal would permit SUB to be used in conjunction with other signals such as the Selective Polling (SEP) and the Password (PWD). TR-29.1 agreed with the proposal, and it was submitted to TR-29 as a proposed contribution to the Question 5 Rapporteurs meeting.

TR-29.1/95-08-32, Proposed Revision to T.30 Subaddress FIF (Facsimile Information Field) Definition (J. Rafferty, Human Communications), proposes that the Subaddress signal within T.30 be extended to permit the optional use of a variable length Facsimile Information Field. Currently, only a fixed length, 20 character field is permitted. TR-29.1 agreed with the contribution in concept. An edited version, TR-29.1/95-08-32R1, was forwarded to TR-29 as a potential TR-29 contribution to the Q5 Rapporteurs meeting. OTHER HIGHLIGHTS

J. Decuir presented TR-29.1/95-08-37 (AT&T, Intel, Microsoft, Motorola ISG, Radish), as a liaison from TR-30. It suggests that there is a need to have a transition approach between the various potential applications which may run over V.34 modulations (fax, DSVD, H.324, T.120). This contribution was previously discussed at TR-30.1 and SG 15 last month. It reviews the areas of agreement which have been established within Question 5/8. It discusses the number of different types of applications which are emerging using V.34 modulation and envisions situations where it would be useful to move between different services in a single phone call while using a common modulation. The contribution suggests that a faster transition between services would be useful. For H.324 video terminals, codepoints for duplex fax, DSVD and other modes have been proposed. When this contribution was presented in TR-29.3, TR- 29.3 members suggested that a V.8 idle mode be established as a potential exit path, rather than adding additional codepoints to each service. TR-29.1 supported the TR-29.3 approach in principle, subject to review of a planned TR- 29.3 liaison on the topic. This paper was later approved as a TR-29 contribution. TR-29.1/95-08-35 (H. Silbiger, AT&T) proposes extensions to T.35 to add an additional octet for codes that identify countries. This will be submitted to TR-29 as a proposed contribution to the Q5 Rapporteurs meeting and as a white paper. In the TR-29 meeting, it was agreed that TR-29.1/95-08-35 be sent to Study Group D for approval as a US white contribution. H. Silbiger also presented TR-29.1/95-08-38 (G. Bremer, AT&T) and TR-29.1/95-08-39 (G. Bremer, AT&T). These papers propose an approach called V.34Q which could be used to support simultaneous fax and voice. The V.34Q approach uses the same Framed QADM (Quadrature Audio Data Modulation) technology that has already been determined as draft V.61 by SG 14. TR-29.1/95-08-38, V.34Q: High Performance, Low Complexity Simultaneous Voice plus Data, proposes that a V.34Q draft recommendation be developed. The basic concept is that V.34Q will permit audio of all kinds (voice, music, other background sounds) to be sent without distortion; the remaining portion of bandwidth can be used for data applications. Alternatively, information may be transmitted in a data-only mode. The contribution was later approved as a TR-29 contribution. TR-29.1/95-08-39, V.34Q Performance Analysis, presents information intended to substantiate the performance claims of the previous paper. It proposes that an option be added to the SUB signal to permit use of a variable length Facsimile Information Field (FIF). Performance characteristics include very minor delay times (approximately 60 msec end-to-end) and low in- cremental complexity (+15%) as compared to normal V.34. H. Silbiger indicated plans to write a paper for the Q5 Rapporteurs meeting on how V.34Q could be supported via existing facilities such as Group 3 Annex C. This paper was approved as a TR-29 contribution, with minor edits. TR-29.1/95-08-36, Proposed revision of Recommendation T.35 (H. Silbiger, AT&T), addresses a proposal to extend the country codes within T.35. The white contribution from H. Hertlein of Germany (COM 8-104) was also reviewed. The extension mechanism in the German contribution is somewhat different. It was agreed that H. Silbiger will edit the paper for consistency with COM 8-104, particularly in the extension mechanism. TR-29.1 approved the submission to the Study Group (the escape to Annex C/T.35). The paper will also be sent to the Q5 Rapporteurs meeting as a TR-29 contribution. James Rafferty, Human Communications

TR-29.2 FACSIMILE PROGRAMMABLE INTERFACES During the last meeting, the Chair, J. Decuir (Microsoft), announced that he would soon resign and solicited a volunteer to serve as Chair. Since that time, two members expressed interest in serving as Chair: R. Lutz (Cognisys) and V. Cancio (Xerox). Since R. Lutz was absent, it was agreed to postpone the election until the October meeting. LIAISON REPORTS

TR-30.4, DTE-DCE Protocols J. Decuir reported on the July meeting of TR-30.4. PN-3131 (Asynchronous Voice DCE Control) will be divided into call control and voice media control components and proposed for ITU V.60-series (SAVD) recommendations. Draft

Annex A/V.25ter for V.8 DCE control, TR-29.2/95-08-32 (J. Decuir, V.25ter Editor), will be balloted as part of PN-2989 (Extensions to Asynchronous Serial Automatic Dialing and Control) and forwarded to ITU Working Party 1/14. A proposal for Synchronous Access, TR-29.2/95-08-31 (B. O’Mahony, PN-3319 Editor), is being developed for support of several V.34-based protocols. ITU SG 14 Q7, DTE-DCE Control No meetings have been held. There will be a Study Group 14 Question 1 (Q1/14) and Q7/14 Rapporteur’s meeting held the week following this meeting in Hood River, Oregon (see report this issue of CSR-T). Work will focus on DTE-DCE interfaces for SAVD (Simultaneous or Alternating Voice Data) and H.324 operation. AMENDMENTS TO ITU T.31 (T.CLASS 1) FOR V.34

J. Decuir presented draft Annex B (Procedure for Service Class 1 support of V.34 modems)/T.31, embedded in TR- 29.2/95-05-24R1 (J. Decuir, T.31 Editor). This reflects changes agreed to at the previous meeting. It was reviewed, and all changes were approved except: • Wording was added to B.7.3 on FCS (Frame Check Sequence) bytes in received data. • The previous suggestion to send final flags in B.8.3 and B.9.3 was rescinded as it was incorrect. The previous open issues of +F34 persistence were not addressed. The result of this discussion was a further revised document, TR-29.2/95-05-24R2. Since this was not copied by the end of the TR-29.2 meeting, it was referred to TR- 29 for approval and forwarding to ITU. J. Decuir also presented the Synchronous Modes proposal, TR-29.2/95-08-31 (B. O’Mahony, PN-3319 Editor) from TR-30. It is based on Annex B/T.31. It deletes half duplex V.34 support, but it adds several features useful for implementing protocols like V.42, DSVD (Digital Simultaneous Voice Data), and H.324 in DTE. It was noted that if the code points needed for V.34 half duplex control were added, Annex B/T.31 could be deleted or simplified. It was agreed to draft a liaison to TR-30 to that effect and forward it through TR-29. AMENDMENTS TO ITU T.32 (T.CLASS 2) FOR V.34

J. Decuir distributed draft Annex C (Procedure for Service Class 2 support of V.34 modems) to T.32, embedded in TR- 29.2/95-05-25R1 (J. Decuir, T.32 Editor). It reflects changes agreed to at the previous meeting. It was reviewed, and all changes were approved. However, it was noted that all other T.32 parameter and subparameter values are in hexadecimal, so the additional BR (bit rate sub parameter) values 10-14 were replaced by hex values A-E. These changes are in Table C.1 and in the sample sessions. The result of this discussion was a further revised document, TR-29.2/95-05-25R2. Since this was not copied by the end of the meeting, it was referred to TR-29 for approval and forwarding to ITU. PN-3130, SERVICE CLASS 4 FAX MODEMS

No papers were submitted. However, L. Staples (DataRace) volunteered to be the editor, if there was interest expressed. He was accepted as editor, based upon previously expressed interest from Delrina, STF, and Faximum Software, all DTE software companies. L. Staples agreed to take the previous document, make previously agreed minor changes, add new material for V.34 support that adapts draft Annex B/T.31, and produce a new draft. If acceptable, it should be balloted in committee after the next meeting. PN-3294, FACSIMILE DCE APPLICATIONS NOTES

There were no new contributions. The editor, H. Silbiger (AT&T), agreed to produce a draft based upon previous contributions on ECM (Error Correction Mode) and on various applications issues using Class 1. PN-2725, SERVICE CLASS 3

The Editor, R. Lutz (Cognisys), sent a report on PN-1906 (Multi-Function Peripheral Interface, MFPI), PN-2725, and related work. This report is contained in TR-29.2/95-08-35 (R. Lutz, Cognisys representing MFPA). No new documents were submitted directly on PN-2725. PN-1906, MFPI, IS-650 TIA has not approved IS-650 for publication because the intellectual property disclosure wording does not match that specified in the TIA Engineering Manual. R. Lutz will work this out with TIA.

It was agreed to forward IS-650 to ITU as a white contribution for the February SG 8 meeting. J. Decuir agreed to draft a cover page for approval by TR-29. FUTURE MFPI

TR-29.2/95-08-35 (R. Lutz, Cognisys representing MFPA) notes the following work items as important to future MFPI work: • Completion of IS-650. Consider harmonization with IEEE 1294.3 transport protocol used in HP OfficeJet. Other items are identified in TR-29.2/95-08-35). • Completion of PN-2725. • Extended negotiations work in TR-29.1 and ITU Q5/8. • Facsimile MIB (Management Information Base); TR-29.2/95-08-33 is a Project Initiation Notification System (PINS) form for a project to develop a US standard for the Configuration Management of facsimile devices. This needs to be coordinated with MIBs for Scanners, Modems, Printers, Copiers, etc. • A possible “Troika” MFP API (Application Programming Interface) based on a previous proposal from R. Lutz. It was noted that there was considerable overlap between the work on MFPI and the work in IEEE 1284.3. R. Lutz has been attending both meetings. TR-29.2/95-08-35 contains a report on the joint meeting between 1284.3 and MFPA that was held in June. R. Lutz indicated that the direction of the work may depend on the development of protocols for use in capabilities query and configuration with remote MFP. This is to be addressed in TR-29.1. It was considered premature to prepare a new project statement until this issue was addressed. V. Cancio (Xerox) presented TR-29.2/95-08-36© (R. Lutz, Cognisys representing MFPA), “Job Submission and Transportable Document Format.” This was considered to be an essential component of MFPI level 4 for networked or remotely located MFP. It was not discussed in detail. Instead, it was tabled until the next meeting when R. Lutz would be in attendance. CONFIGURATION MANAGEMENT FOR FACSIMILE DEVICES

TR-29.2/95-08-33 is a project statement on developing a US standard for Configuration Management of facsimile devices. It was drafted and presented by J. Rafferty (Human Communications), and it was accepted. It was agreed that this should leverage existing printer and scanner work. The TWAIN group will be approached to help locate any scanner MIB. It was also agreed that this could apply to facsimile modems as well as MFP. J. Decuir noted that this is related to PN-3147, the Modem MIF (Management Information File) project in TR-30.4, which is currently out to letter ballot. He agreed to bring the results to the TR-29.2 October meeting. This project statement will not be forwarded to TIA until someone agrees to serve as editor. There were no volunteers, although J. Rafferty will make contributions. FAX API S

J. Rafferty (Human Communications, representing EMA) presented TR-29.2/95-08-34, on extensions of CMC (Common Messaging Calls) 2.0 API for facsimile. This was presented for comment, representing work in the X.400 API Association (XAPIA). It will be reviewed at their meeting during the following week. It was noted that some clarifications are needed on the high resolution descriptions. H. Silbiger (AT&T) will convey these concerns to the source, S. Griesmer (AT&T Bell Labs). REVISION OF TIA-578-A (C LASS 1)

J. Decuir (Microsoft) noted that T.31 plus proposed Annex B contains material not in TIA-578-A, Facsimile Digital Interfaces - Asynchronous Facsimile DCE Control Standard, Class 1. In discussion, it was agreed that a revised TIA- 578-B should be generated based upon the 1996 version of T.31. J. Decuir agreed to draft the project statement and contribute the source files. V. Cancio (Xerox) agreed to serve as editor. REVISION OF TIA-592 (C LASS 2.0) AND REPLACEMENT OF IS-134

Similarly, it was noted that T.32 plus proposed Annex C contains material not included in TIA-592 or IS-134 (Revision to TIA/EIA-592, Asynchronous Facsimile DCE Control Standard, Service Class 2-A). It was agreed that a

September 1995 Vol. 6.6 Copyright © CSR 1995 39 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS revised TIA-592-A should be generated based upon the 1996 version of T.32. This would retire IS-134. J. Decuir (Microsoft) agreed to draft the project statement and contribute the source files. V. Cancio (Xerox) agreed to serve as editor. OTHER BUSINESS

The UK-based company, WordCraft International, has produced a specification entitled, “Computer FAX Protocol.” The subject overlaps IS-650. WordCraft may submit it to ITU SG 8 for consideration. R. Lutz (Cognisys) wrote an MFPA contribution of commentary. It is a technical contribution providing comments on Computer Fax Protocol (CFP). It was distributed as TR-29.2/95-08-37, and it notes items of interest and value and some limitations. M. Lake (WordCraft) wrote a response, and it was distributed as TR-29.2/95-08-38. No decisions were made. Joe Decuir, Microsoft

TR-29.3 AND Q10/8, AUDIOGRAPHIC CONFERENCING This was a joint meeting of ITU-T Q10/8 and TR-29.3. Work proceeds at the highest priority on T.120 and T.121. White documents will be submitted by October 15 to be translated in time for decision in February 1996, as announced at the last Study Group 8 meeting in March 1995. T.123 and T.128 are the next level of priority. It is hoped that both will be mature enough for determination in February 1996 and decision at the first meeting of 1997. T.124 GENERIC CONFERENCE CONTROL (GCC)

Q10/8-95-07-246 (J. Bernstein, PictureTel, Q10/8 Rapporteur) identifies three significant typographical errors in the PDU (Protocol Data Unit) definitions of T.124 in its final draft. It was agreed that this errata should be corrected before publication. The editor will draft a letter to the ITU-TSB specifying details and will post a revised document to the FTP site. T.126 MULTIPOINT STILL IMAGE AND ANNOTATION PROTOCOL

Q10/8-95-07-262 (T. Itoh, Fujitsu, Japan) provides comments on T.126. Q10/8-95-07-263 (J. Johnstone, DataBeam) identifies errata and requests changes in T.126 final draft. Q10/8-95-07-265 (T. Peers, BT Labs, UK) identifies T.126/T.127 application protocol initiation sequence errata and proposes changes to both T.126 and T.127. The errata and proposed changes of these contributions will be collected into a single list of T.126 errata, Q10/8-95- 07-250rev (P. Romano, Polycom). The desire was to correct as many errata as possible before publication. Advice on how to proceed will be sought from the ITU-TSB. T.127 MULTIPOINT BINARY FILE TRANSFER PROTOCOL Q10/8-95-07-261 (G. Kisor, Intel) identifies a problem with T.127 when using private channels and suggests three possible solutions. Discussion concluded that no simple solution is available now. A note should be added before publication to warn implementers about the danger of expelling receivers too quickly. Additional errata were presented in Q10/8-95-07-265 (T. Peers, BT Labs, UK), as described above. A complete single list of errata will be developed for T.127. It was agreed to proceed as with T.126. T.120 DATA PROTOCOLS FOR MULTIMEDIA CONFERENCING Q10/8-95-07-247 (J. Bernstein, PictureTel) proposes to suppress MCS (Multipoint Control Services) negotiation of domain parameters. It was not accepted. An alternative idea was discussed, in that terminals should be required to open negotiation with the broadest range possible between their minimum and maximum values. This will be written up in a form suitable for use in T.120 and will be revisited at the next meeting. The editor shall distribute, before the next meeting, a revised text of T.120 incorporating changes in response to comments made at the March 1995 meeting.

T.121 GENERIC APPLICATION TEMPLATE Q10/8-95-07-240 (T. Peers, BT Labs, UK) is Draft E of T.121, Generic Application Template. It contains new text concerning how a default session, used as a step in creating a new common session, was modified to show the result, typically, as one rather than multiple new sessions. Changes to Figures 9 and 10 were explained. It is necessary to enroll using the full session key before attempting to enter items into the application registry. This impacts T.126 and T.127, which incorporate material from the previous version of T.121 and, hence, use GCC incorrectly. It was agreed to modify the scope of T.121 to say that it is suggested, not mandatory, for the definition of new standardized application protocols. In this view, T.121 offers useful examples that are easy to apply, but it may not cover all possibilities. And, it is not a prescription of what is or is not permitted -- that is specified in T.124. Terms that are already defined in T.124 will not be defined differently in T.121. Q10/8-95-07-154 (T. Peers, BT Labs, UK) is the T.121 change list and issues. It is the editor’s record. T.128 MULTIPOINT REAL TIME STREAM CONTROL SERVICE ARCHITECTURE

There was much discussion on the scope and architectural model described in Q10/8-95-07-241 (T. Peers, BT Labs, UK), Proposed Draft Recommendation T.128.0. To attain agreement on the scope and architectural model of T.128 by working out more details, two series of audio conferences will be scheduled, one on network dependent multiplexer control and the other on throughput control for individual data applications. Details will be broadcast on the t120- [email protected] reflector. The further study of network-dependent interface management functions will be correlated with relevant Study Group 15 recommendations (e.g., H.245). Q10/8-95-07-253 (G. Kisor, Intel) is a QoS/BWC (Quality of Service/Bandwidth Control) Model for T.128.2. It provides a framework for expressing the quality of service of a point-to-point link, so that different values can be conveyed in T.128 PDUs. It is not meant to duplicate or conflict with mechanisms of existing networks. T.RES CONFERENCE RESERVATION PROTOCOLS

Q10/8-95-07-243 (France Telecom) is the current draft of T.RES. It was agreed to expand its scope to cover all three interfaces described in Q10/8-95-07-242 (K. Eckel, MCI Telecommunications), “Reservation System Service Requirements.” The user interface to reservations will be specified to work equally well over T.120 services or over alternative transport. These agreements are detailed in Q10/8-95-07-267 (T.RES Editor). T.123 NETWORK SPECIFIC DATA PROTOCOL STACKS FOR MULTIMEDIA CONFERENCING Q10/8-95-07-244 (T. Lyons, AT&T) proposes changes to T.123. These were reviewed and accepted, except as follows: • Issues A and B (how to guarantee the successful outcome of a point-to-point connection attempt) were recast as new work item T.baseline with written contributions sought for the next meeting. • Issue C (Retain alternative profile for B-ISDN) was closed by deleting section 13.6, “Alternative: B-ISDN based on Q.2110.” This is the alternative profile for B-ISDN that was displayed as a possibility in Appendix III before the revision. The base profile finally adopted for B-ISDN is based on a suggestion from SG 15. It is defined in Section 13.5 using a single VC (Virtual Channel) with audio and video instead of a separate VC for data. • Issue D was closed by retaining section 13.7 (to be renumbered 13.6), “Alternative: LAN based on data unit transfer,” despite the fact that SG 8 cannot reference proprietary LAN protocols. • Issue E (PPP, SLIP, etc., are intentionally omitted) was closed by reducing the number and strength of references to ISO 8802. This is a way to generalize the protocol stack for non-standard LANs and remote access to LANs. • Issue F will be closed by deleting Appendix II, “DTE-DCE Interface Incorporating Audiovisual Control,” if the SG 14 Rapporteurs reply positively to a liaison statement requesting that they take responsibility for defining a data port interface for videotelephones per SG 15 request (Q10/8-95-07-258rev). • Issue G (Requirements of T.CDH [Cooperative Document Handling] in the way of extended profiles) remains open temporarily. However, the sentiment in Q10/8 is against retaining the extended mode profiles, as they seem to offer no advantage compared to basic mode. The Rapporteur will poll other Questions to learn whether they have a continued need for extended mode profiles. If not, they will be deleted. Q10/8-95-07-259 is a proposed liaison to Q2/15 regarding the harmonization of T.123 and H.245 protocol stacks for B-ISDN.

Q10/8-95-07-251 (G. Kisor, Intel) proposes further changes, and these were mostly accepted. The editor agreed to investigate H.244 and consider whether it should be mandated along with H.242 and H.243. The suggestion to update Appendix I on H.320 call control and to add an appendix on H.324 start-up sequencing depends on a volunteer for new text. It will be noted that where a call control stack is shown for clarity in the profile figures, it is not meant to be a normative part of the specification. It will also be noted that by the addition of TPKT, AppleTalk qualifies for inclusion in section 13.7. Q10/8-95-07-245 (T. Lyons, AT&T) provides two AT&T contributions describing the advantages of V.34Q (AT&T VoiceSpan using V.34 technology) from the July TR-30.1 meeting. V.34Q has a total talker-to-listener delay of 60 msec including a 35 msec V.34 “modem” delay. There was considerable interest in Q10/8 to consider this approach. Q10/8-95-07-249 (N. Kenyon, BT Labs) addresses the need to define the dynamic procedures from call establishment to multimedia session. He proposes a document called V. conv to define this, but noted that this work could be part of other SG 15 or SG 14 recommendations. These two contributions were considered evidence of continued ferment in multimedia solutions for PSTN. Things should settle down before the T.123 revision is submitted for decision. Q10/8-95-07-260rev is a liaison statement to Q1/14 and Q7/14 encouraging the study of the application of Framed QADM (Quadrature Audio Data Modulation) techniques to enhance V.34 modem technology (V.34Q). Q10/8-95-07-252 (G. Kisor, Intel) provides the latest draft of revisions to V.25ter (to be submitted at the August meeting of TR-30.4). While this contribution may lead to new ways of composing multimedia endpoints, it was determined that it does not affect T.123 directly. It is a local interface that could be used at one end of a connection but not the other. It is not intended to change what goes across the wire (i.e., that which is specified by T.123). OTHER HIGHLIGHTS

The last point of Q10/8-95-07-249 (N. Kenyon, BT Labs), will be covered on the agenda of the next meeting. It seeks, on behalf of the JCG, information about a possible overlap of T.120 and T.195 (Document Conferencing and remote Presentation, Multi-Point Configuration). Q10/8 95-07-256 from I. Sebestyen, Siemens describes the scope to the Q10 work as agreed in SG 8 and SG 1 and suggests that the title of T.120 “Transmission protocols for multimedia data” be changed to “System Characteristics and Protocols for the Audio Graphics Conferencing Service”, as multimedia is not in the charter of Q10. Q10/8 95-07-266 is a proposal outline from PictureTel to be presented to the TSAG in July for a multimedia study group with 5 working parties. This proposes bringing together the parts of work in SG 14, SG 8 and SG 15. Q10/8-95-07-255 (C. Garthwaite, Microsoft) addresses switching between different services and applications that use a common physical layer (e.g., V.34) without discontinuing that carrier. This stimulated interesting discussion. It led to creating a draft liaison statement to Q1/14 and Q7/14, Q10/8-95-07-264rev, proposing a scope definition for V.dispatch. V.dispatch is proposed to operate after the physical layer is created (using V.8bis to initiate the V.dispatch protocol) to negotiate capabilities for other services and applications. Q10/8 cannot act on Q10/8-95-07-255 because the T.120 series does not yet contain a system-level specification (e.g., H.324 or V.60). Q10/8-95-07-257 (Deutsche Telekom) notes that T.190 (Cooperative Document Handling, Framework and Basic Services, based on OSI stack) defines a set of applications - T.191 (point-to-point document conferencing), T.192 (remote editing), T.193 (document archive and distribution), T.194 (sequential document production) and T.195 - in which one or more users are jointly working on a set of documents. The point raised is to have a common interface for different services, i.e., OSI stack or T.120 protocols. XAPI (eXtended API) is suggested as the common interface. It was distributed in order to alert members to these issues. Time will be allocated at the next meeting for a more complete presentation and discussion. Electronic mail should be sent to all members through the reflector at t120-interest@world .std.com. For instructions on joining this distribution list, send email to t120-interest-request @world.std.com. Anonymous FTP site, ftp.csn.net, subdirectory ConferTech contains document drafts.

TR-29.4 SECURE FACSIMILE The NATO STANAG 5000 document was enhanced per the latest revisions to the MIL-STD-188-161D. Comments from NATO were reviewed by TR-29.4 and resolutions were proposed. J. Hamadani (Ricoh) is looking into expanding the military fax Type 1 for use over faster digital networks. Investigation is also underway regarding the use of Group 3 over digital telephone networks.

TR-29.4 has been in contact with NSA (National Security Agency), which is developing new STU III secure telephone technology. The new port configuration is being defined and ongoing contact is planned. ISDN is beginning to be implemented in the Washington DC area, and they will try to get information on this.

J. Rafferty (Human Communications) briefly summarized the status of secure fax in the ITU. James Rafferty, Human Communications

TR-29 PARTIAL MEETING ROSTER, JULY 31 - AUGUST 3, 1995, QUEBEC CITY, QUEBEC, CANADA Steve Urban, Delta Information Systems Chair, TR-29 David Duehren, Brooktrout Technology Chair, TR-29.1 Joe Decuir, Microsoft Chair, TR-29.2 Bruce DeGrasse, BJ Communications Chair, TR-29.3 Bob Robinson, Ilex Systems Chair, TR-29.4 AT&T Terry Lyons AT&T Herman Silbiger AT&T Rand Sherman AT&T Paradyne Robert Lastinger Bellcore Rich Beckman BJ Communications Bruce DeGrasse British Telecom John Boucher British Telecom Trevor Peers CSTI Greg Pfister DataBeam Jim Johnstone DataBeam Neil Starkey Data Race Les Staples France Telecom Bruno Ceccaldi General DataComm Charles Nahas General DataComm Ghassan Semaan General DataComm Marc St-Hilaire Genoa Technology Mike Moldovon GPT Video Systems Loc-Kin Yuen Hewlett Packard Daniel Lee Hewlett Packard Salvador Plasencia Human Communications James Rafferty Intel Greg Kisor Lanier Worldwide Gary Lucas MCI Telecommunications Ken Eckel Microsoft Joe Decuir NCS Stephen Perschau PictureTel Jeff Bernstein PictureTel Jean-Marc Matteini Polycom Pat Romano Rockwell International Glen Griffith Technische Universität Berlin Jörg Ott Texas Instruments Henry Jacobs VideoServer Chuck Grandgent VTEL Bruce Kravitz Xerox Vivian Cancio Xerox Lloyd McIntyre

The next issue of Communications Standards Review – Telecommunications (Vol. 6 #7) is scheduled for October 1995.

September 1995 Vol. 6.6 Copyright © CSR 1995 43 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS REPORT OF SG 14 RAPPORTEURS MEETINGS AUGUST 7 – 12, 1995, HOOD RIVER, OR Q1/14, V.SAVD The V.savd Rapporteur is J. Magill (Probe Communications, UK). LIAISONS

SAVD-95-082 (J. Magill, Q1/14 Rapporteur) is the report of the last meeting of the Joint Coordination Group (JCG) on Audio Visual Multi-Media Systems (AVMMS) (see report this issue of CSR-T). This report includes a list of all Questions/Study Groups relevant to Audiovisual Multimedia and an updated Framework of Multimedia Standards (see CSR-T 6.2 page 33 for a previous version of the framework). The Rapporteur highlighted the recommendations of the group, some of which were that Study Groups: • Not adopt more than one method to satisfy a common requirement; • Work together to develop joint Recommendations where appropriate; • Not extend the scope of Recommendations in a way that would result in overlap of functionality. In addition, Q1/14 recognized what is referred to Multi-Media platforms and proposed that all platforms consist of the same components (e.g., audio, multiplex, video control, etc.). It was understood that the JCG has no “authority” to require adherence to these recommendations but that their desires should be considered. SAVD-95-111 (N. Kenyon, BT, plc) was introduced by J. Brownlie (BT, plc). It calls for a stop to the study of V.dsvd since it provides the same functionality as that provided by H.324, which BT believes offers a superior solution. VOCODER

In response to a question from the floor, J. Magill reported that the SG 14 proposals for revisions to the terms of reference for the vocoder selection had been accepted by the SG 15 experts. Five candidates are presently being considered. These proposals will be tested in NTT labs, and NTT will also conduct the Japanese listening tests. The English language tests will be performed by Comsat Labs on a contractual basis. The selection will take place at a meeting in Bethesda, MD, on September 14-15. SYSTEM

As there were no papers here on AVD (Alternating Voice Data), the Rapporteur raised the question as to whether it should even be mentioned in the V.dsvd system Recommendation. SAVD-95-083 (J. Magill, Q1/14 Rapporteur) is Revision 0.2 of the proposed Draft Recommendation V.dsvd- system. J. Magill conducted a point-by-point review of this latest version. Much of the discussion was related to what should be included in this Recommendation as opposed to what should be included in other referenced Recommendations (e.g., V.34, V.8bis, V.gmux, etc.). There was some discussion about the use of the word “terminal” as some of the functions could be implemented in either the DCE (Data Circuit Terminating Equipment) or the DTE (Data Terminal Equipment). There was also some discussion on how the control was divided up between V.8bis and the control channel, but this was put off for discussion at a later time in the meeting. It was also noted that this document should address rapid switching between DSVD (Digital Simultaneous Voice Data) and Video Telephony, as had been done in H.245 (video telephone system control) for rapid switching between Video Telephony and DSVD. It was agreed that it would be appropriate to provide a specification for “allowable delay” for both audio and data in Section 9. CONTROL CHANNEL

SAVD-95-077 (C. Hansen, Intel) is the latest version of the proposed Recommendation for a control channel protocol for DSVD. This document is aligned, to the maximum extent possible, with Recommendation V.42. Following this presentation C. Hansen (Intel) also briefly gave an overview of the latest version of draft Recommendation H.245. SAVD-95-095 (C. Garthwaite, Microsoft) proposes a method for quick movement between Videotelephony and DSVD. SAVD-95-112 (B. DeGrasse, BJ Communications), in answer, proposes the development of a new generic

Recommendation called V.dispatch to specify procedures for quick movement between different services and applications that use a common physical layer. It proposes that either V.8bis or H.245 be used as the initiator for V.dispatch. SAVD-95-112 is a liaison statement from SG 8 to Q1/14 and Q7/14 proposing a definition for the scope of V.dispatch. (Also see the discussion of V.dispatch below.) There was considerable discussion about how much time this new protocol might add to the startup (even though it would be done at a higher data rate). There was also discussion about how long the modem should stay in V.8bis (300 bit/s) while negotiating. It was generally agreed that the V.8bis negotiation should be limited to basic functions. Several people also expressed a concern over the creation of one more protocol that appears to be addressing a similar need. SAVD-95-118rev was introduced by C. Hansen (Intel) and reports on the initial meetings of the DSVD-C Ad Hoc group. The Ad Hoc group made the following observations: • It is desirable to have maximum compatibility with H.245. • H.245 relies on an out-of-band architecture. • More information is needed on the encoding and decoding of H.245. • Retention of standardized LAPM (Link Access Protocol Modem) in any merged H.245/DSVD-C Recommendation is highly desirable. V.61, ASVD SAVD-95-081 (R.P. Brandt, Text Telephony [Q8] Rapporteur) addresses the use of Draft Recommendation V.61 (ASVD) in a Text Telephony environment. It attempts to analyze the potential effect of implementing V.18 (Operational and Interworking Requirements for Modems Operating in the Test Telephony Mode) on a Draft Recommendation V.61 modem that also implements V.8bis. It provides specific suggestions for changes to the text of Draft Recommendations V.8bis and V.61 as well as of Recommendation V.18. Considerable discussion followed the introduction of this paper, and a detailed analysis of the scenarios was undertaken. In the end, it was determined that the issue of interest was the case where a V.61/V.8bis/V.18 (Multimode, MM) device was called by an unknown device (either a V.18 or a MM device) that sent the V.18 CI (Call Indicator). The point discussed was whether, upon detection of the CI, the device should attempt to proceed as V.18 or still attempt to establish a V.8bis link. There was general support for leaving this optional depending on the application (e.g., it might be okay to go directly to V.18 in a home environment and subsequently decide to go to AVD. However, it might be desirable to go to the desired mode such as V.61 or V.18, as soon as possible in a 911 call processing center). It was proposed that a general framework Recommendation for Text Telephony be developed to “pull together all related aspects of this work.” The suggestions for changes to the text of V.61 were considered but any decision was deferred until the October meeting. The changes to the text of the other Recommendations were referred to the appropriate Rapporteurs for consideration. In response to the proposal made in SAVD-95-117 (R.P. Brandt, Q8/14 Rapporteur) addressing the use of Draft Recommendation V.8bis in a Text Telephony environment, it was agreed that Circuit 135 (received energy present) should be added to the list of supported circuits in Draft Recommendation V.61 with the note that it only need be implemented if it is intended to support Text Telephony. (See also V.8bis below for more discussion of this contribution.) V.34Q SAVD-95-079 (G. Bremer, AT&T) recommends the initiation of a study of the framed QADM (Quadrature Audio Data Modulation) principles, similar to the V.61 draft Recommendation, to a Recommendation based on the V.34 modem. Introduced by R.K. Smith (AT&T), it highlights some of the potential advantages to such a modem (i.e., low delay [60 msec], high performance 24 kbit/s data concurrent with good quality audio, low complexity, etc.). Unlike the earlier V.61 work, this is being approached as a collaborative effort. Several questions were raised about the relative complexity of this proposal with respect to Recommendation V.61; however, no comparisons or information were available. SAVD-95-080 (G. Bremer, AT&T) provides a more detailed analysis of the requirements/ benefits of a V.34Q modem. Introduced by B. Betts (AT&T), it considers various options including trade-offs in terms of throughput for higher and lower audio quality.

It was clarified that the side channel is used to transmit information on what is being carried in the data channel. I. Sebestyen (Siemens) raised the issue of possibly delaying the approval of Draft Recommendation V.61 pending the completion of the V.34Q work. BT countered with a request not to delay V.61 but to couple the development of V.34 with an effort to shorten the start-up (to voice) in V.34. SAVD-95-113 is a liaison from the Q10/8 Rapporteur encouraging the rapid study of V.34Q. It was agreed that this work be progressed by an e-mail reflector between now and the October Working Party meeting. Later in the meeting, the Rapporteur obtained approval to recommend that, because of the obvious technological impact, V.34Q be studied in the Q1/14 High Speed Modems group (D. Stuart, Rapporteur) with close liaison to the SAVD group to make sure all MM issues are covered. SAVD-95-137 is the liaison to Q1/14 High Speed Modem Rapporteurs requesting that they take up the study of the V.34Q proposals. V.DISPATCH

SAVD-95-116rev (M. Buckley, V.dispatch Ad Hoc Group Chair) reports on the agreements reached in the Ad Hoc group on V.dispatch. The liaison from Q10/8 (SAVD-95-112) draws attention to the difficulty of managing a collection of codepoints, each specific to one member of an ever expanding set of services and applications. SAVD- 905-112 advocates that a single common facility (V.dispatch) be considered. The SAVD committee agreed to the need for this type of protocol (although it was not clear that this would require a separate Recommendation), that the protocol should use V.8bis and LAPM, and that it should be as compatible as possible with H.245. During discussion, it became apparent that the use and possible implications of this type of a protocol was not fully understood and that considerable work is still needed before a common agreement can be reached on even these basic concepts. V.GMUX SAVD-95-107 (F. Burg, Editor, AT&T) is the latest version of Draft Recommendation V.gmux: Generic Multiplexer based on V.42 LAPM, dated 8/95. It has grown in size primarily due to the decision to include the text of Recommendation V.42. SAVD-95-106 (J.H. Derby, IBM) describes suspend/resume as an optional extension to V.gmux for DSVD modems. This proposal had been made several times in the past, including at the interim meeting of Working Party 1/14 in Orlando in December 1994. The proposal attempts to mitigate the multiplexer delay in the audio channel through a scheme which prioritizes audio frames. Considerable discussion followed this presentation. PictureTel and Motorola supported keeping V.gmux simple and using H.223 if higher efficiency is desired. IBM and AT&T supported increasing the efficiency of V.gmux. In the end, no decision was possible. In response to a question, the IBM representative stated that when IBM started working in this area, a patent search was conducted; and in his opinion, there was no applicable IPR associated with this proposal. SAVD-95-115 (J. Magill, Rapporteur) is a proposal for an overall GSTN (General Switched Telephone Network) multimedia framework Recommendation as was requested by the JCG-AVMMS meeting. This proposed outline was described as a “more focused” version of SAVD-95-110 (N. Kenyon BT), Draft Recommendation V.conv (Multimedia Multiplexing Systems for the GSTN). The two SG 15 representatives stated that there may not be a need for this type of Recommendation. It was decided to pass this document to the JCG for comment and to defer any action on this item until the October meeting. SAVD-95-084 (J. Magill, Rapporteur) proposes a numbering sequence for the proposed Recommendations. Under this scheme, V.gmux would be re-numbered to V.64. (Technical editors note: in the SAVD work, only V.61 is a SG 14 approved designation at this time.) Because this is a matter to be decided by the SG Chair, it was decided to have R.P. Brandt, the SG 14 Vice Chair, convey the preferences to K. Kern, SG 14 Chair. OUTGOING LIAISONS

SAVD-95-136 forwards the contributions on V.34Q to appropriate groups in SG 8, 12, and 15 for information. Q1/14, V.8BIS L. Brown (Motorola ISG) is the Associate Rapporteur for V.8bis.

SAVD-95-101 (L. Brown, V.8bis Associate Rapporteur) is a V.8bis status report. It provides a summary of the agreements to date, the latest version of the objectives, comments from the UK and US, and a list of outstanding issues. The comments associated with the US and UK “No” votes on Draft Recommendation V.8bis, as reported in SAVD-95-101, were addressed. It was decided that, for the most part, all of the concerns were addressed in some form. SAVD-95-090 (TR-30) is Version 4 of Draft Recommendation V.8bis, dated May 29, 1995. It also contains a list of the most recent editorial changes, minor inconsistencies, and clarifications. SAVD-95-094 (J. Brownlie, BT plc) proposes a simpler V.8bis compatible with Recommendation V.8. It retains, to the greatest extent possible, the functionality of V.8bis. The dual tone structure, however, is replaced with Recommendation V.21 (V.8-like) signals. Additionally, the process relies on the use of new signals, one with a CI cadence called Capabilities Exchange (CE) and a continuous signal called Answer List (AL) at the beginning of the call. New signals called Facilities Exchange (FE) and Facilities List (FL) are also defined for use during the call. In the event of failure, the system reverts to voice quickly, during the call, in most scenarios relying on the users to negotiate their way out of the failure. A specific scenario is also provided to address the movement between text telephone and other modes of operation. When questioned as to whether two deaf users were considered when developing the “revert to voice” form of error recovery, J. Brownlie said that he relied on the possibility that if the call were being transferred from voice to text telephone mode that the two hearing parties would probably still be present and be able to take over. L. Smith (AT&T) observed that the proposal appeared to be designed for machines only and, therefore, did not seem to have the same goal as V.8bis, which attempts to address (the more likely case) of voice callers. He then asked J. Brownlie if he had considered the case where the caller was human. J. Brownlie said that he would develop a scenario for that. SAVD-95-105 (AT&T, Cray Communications, Hayes, Racal Datacom) suggests ways in which the comments that accompany the UK “No” vote on V.8bis might be resolved. J. Magill presented this multi-UK company paper. It addresses the issues one by one by suggesting to resolve the patent issue, remove all references to T.30 until the issues with SG 8 have been resolved, and test the signals proposed in V.8bis on a continuing basis. It finally suggests that changes to the text of the Draft Recommendation be limited to the correction of inconsistencies and ambiguities. The proposal for the resolution of the UK comments were addressed. It was decided that, for the most part, all of the concerns were addressed in some form. J. Brownlie (BT plc) presented SAVD-95-109 (N. Kenyon, BT Labs) and SAVD-95-110, Draft Recommendation V.conv. SAVD-95-109 states that, as presently written, V.8bis does not provide a clear path to initialize an MM session. SAVD-95-110 provides a “straw man” for an overview document on “Multimedia Multiplexing Systems for the GSTN.” Section 6 of this document addresses the shortcomings referred to in SAVD-95-109. It was not clear what the problems referred to in SAVD-95-109 were or how the figures in Section 6 might address these problems. The Rapporteur requested that BT provide a clearer definition of the problems or the proposed solutions. A discussion followed, initiated by J. Brownlie, in an attempt to question why consideration is now being given to the possible replacement of V.8 with V.8bis. SAVD-95-081 (R.P. Brandt, Text Telephony [Q8] Rapporteur) addresses the use of Draft Recommendation V.61 (ASVD) in a Text Telephony environment. SAVD-95-093 (G. Hellstrom, Sweden) modifies chapter 8, “Information Field Coding Format,” from the V.8bis proposal. It revises Communication Function (CF) and Com- munication Capability (CC) fields in the modem negotiation procedure to enable technology selection. These two contributions were briefly reviewed with reference to the proposals for changing the CC and CF coding for text telephony. Discussion was deferred until the other papers addressing the structure of the CC and CF were presented. SAVD-95-096 (L. Smith, AT&T) proposes a raising of the level of the dual tone signals to -5 dBm (-10 dBm is specified in the present draft) to increase the probability of reliable detection in the presence of speech. An analysis of detection in the presence of various speech files (Bellcore and Corpus) is given to support this proposal. The required signal level to cause a network echo suppresser to get to the double-talk mode (referred to as break-in state in G.164) is also given as further reason for accepting this proposal. There was some discussion about the various proposals for levels that had been made by AT&T in the past, and the Rapporteur clarified that this is the first time where test results were provided. Radish questioned the tests results with reference to the echo suppresser issue on the basis that no dynamic testing of echo suppressers was performed. (It was generally conceded that it would not be practical to run these type of tests.) The Rapporteur pointed out that, even with this change, the specification is still 15-19 dB away from the goal stated in the contribution for detection without requiring an adaptive hybrid. L. Smith responded that with proper circuit design this remaining margin could be

September 1995 Vol. 6.6 Copyright © CSR 1995 47 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS accommodated. It was clarified that AT&T still proposes that the -24 dBm level be retained for the initial tone exchange. SAVD-95-097 (L. Smith, AT&T) presents some new plots of format frequencies of vowel sounds. These plots were derived from two separate sources (one from a 1995 study by Western Michigan University). They indicate that the dual tone frequencies presently specified in V.8bis appear to fall in the clear areas of the plots. SAVD-95-098 (L. Smith, AT&T) proposes investigation of the use of an ES/MS (Escape Signal/Mode Select) exchange in place of the CM/JM (Call Menu/Joint Menu) exchange, specified in V.8, in specific cases, to save time in the start-up. Specifically it is recommended that a liaison be sent to SG 15 to assess its possible impact in the demod/remod function in network CME (Circuit Multiplication Equipment). The discussion was generally driven by J. Brownie’s defense of V.8 and ended with no resolution. The following contributions were presented by A. Heinke (Radish), and all assume the use of an octet oriented structure replacing the existing bit oriented structure. • SAVD-95-086 concludes that the present method of coding for the CF (Communications Functions) field unnecessarily limits the amount of proprietary functions that could be supported. It proposes new modes for the CF field and a means to extend the non-standard modes supported. Discussion related to how non-standard CF fields would be coded. It was clarified that octets would only be required to be sent if they were used. • SAVD-95-087 proposes adding the provision for a non-standard CC (Communications Capabilities) for a standard CF through the use of a non-standard octet in the CC. Considerable discussion followed this presentation. The old question of how much needed to be signaled at the V.8bis level was once more raised, this time triggered by the Table 4 (message type field format) example given in the contribution. It was clarified that Table 4 was only given as an example. • SAVD-95-088 addresses what is referred to as an omission in V.8bis that does not allow for the selection of a non-standard CF with an MS. It proposes the use of bit 1 in the first octet of the MS to indicate whether a request for non-standard information was included in the signal. • SAVD-95-089 (Ameritech, Microsoft, Compaq) compares the present bit-oriented structure of V.8bis with the proposed octet-oriented structure. It concludes that the time required by either is essentially the same only when the more commonly used MS signal is considered. It further concludes that the octet-oriented structure provides a more robust structure. SAVD-95-091 (TR-30) proposes three modifications to Draft Recommendation V.8bis: • Remove references to T.35 Provider Codes in section 8.2.3. • Include H.324 and V.dsvd as Communication Functions in table 7 rather than Communication Capabilities under the duplex data Communication Function. • Combine the Message Type and Function Fields in sections 7.2.7 and 7.2.8 to reduce them to a single octet. SAVD-95-092 (M. Buckley, AT&T) proposes a major revision to the coding format of V.8bis. Specifically, it proposes differentiation by protocol stack (instead of such things as “duplex data”), an indication of support for V.8, inclusion of code points for modulation formats, and an indication of support for ISDN modes of operation. In this proposal, the Communications Function (CF) is replaced by a new field called Communications Protocol (CP), also a new field called Physical Layer (PL) is added between the new CF field and the CC field. SAVD-95-108 (F. Burg, AT&T) is a proposed US contribution to SG 8. It proposes revisions to the text of Recommendation T.35 to extend the number of country codes by using an octet containing 1111 1111 as a field extender indication. When the code 1111 1111 is found in the first octet of the Non-Standard Facilities (NSF) frame, the second octet will contain a country code. It also proposes the removal of the restriction that limits its use to T.series Recommendations. SAVD-95-085 (A. Heinke, Radish) proposes adding the capability for interoperability with V.8 and re-transmission during call establishment. Interoperability is achieved through the addition of a requirement for the transmission of and detection of signals associated with specific applications (e.g., CNG) and then taking appropriate action dependent upon the signal detected. It also provides for re-transmissions in the event of no signal detected (e.g., time-out) in both cases. There was considerable discussion about the need for the definition of error recovery in V.8bis. This issue was raised in SAVD-95-085 with the proposal for retransmissions. There seemed to be little support for the inclusion of specific measures for error recovery (e.g., requiring retransmissions) in the Recommendation. SAVD-95-099 (G. Hellstrom, Sweden) raises the issue of the potential for collision when moving from voice to data. It proposes one way of resolving this problem. Although it was clear that there were problems with this specific

proposal, it was also made clear that this needed to be addressed in some fashion in V.8bis. It was agreed that the point on collision resolution raised in SAVD-95-099 requires further study. The Associate Rapporteur obtained the approval of SAVD-95-090 as the new baseline text of Draft Recommendation V.8bis. He then asked J. Brownlie (BT plc, UK) to re-introduce SAVD-95-094 and to highlight what he thought was “broken” in the new baseline text and the associated fixes in SAVD-95-094. J. Brownlie gave a lengthy presentation on BT’s problems with the present draft of Draft Recommendation V.8bis. His main points were: • Possible conflicts with existing signals; however, BT had no definitive knowledge of any conflicts. • Possible interworking problems with V.8; however, BT could not specify any specific problems. • The discouragement of the use of new tones. R.R. Damm (Deutsche Telekom) expressed support for this concern and expressed support for the use of calling tones. At this point, a discussion of the pros and cons of calling tones ensued. It was pointed out that, as presently drafted, V.8bis did not “discourage” calling tones, it just did not specify them. The Rapporteur finally asked for and received the endorsement of the meeting to proceed with V.8bis as presently constructed. BT’s non-agreement to this decision was noted for the record. J. Brownlie also stated that since SAVD-95-094 had been submitted to Geneva as a delayed document, he proposed to re-introduce it in Munich. CODING

SAVD-95-117 (R.P. Brandt, AT&T, Rapporteur for Text Telephony) examines the implications of the AT&T proposal (SAVD-95-92) for the change in coding of V.8bis and the expansion of the scope of Recommendation V.18 to cover all use of modems in Text Telephony. It concludes that if V.18 were designated as a CP (Communications Protocol) and V.61 were moved to the PL (Physical Layer) category, text telephony could be accommodated by Draft Recommendation V.8bis. It further recommends that the sending of the V.18 CI (Call Indicate) continue to be optional but that the note be strengthened to recommend its use unless the user has a priori knowledge that the called device supports V.8bis. The last point was that Circuit 135 should be added to the list of supported circuits in Draft Recommendation V.61 with the note that it only need be implemented if it is intended to support Text Telephony. Agreement was reached on this latter issue. The other items were deferred to the Associate Rapporteurs for V.8bis for further consideration. On the V.18 issues, it was decided to accept the CC assignments of V.21 and V.61 associated with the V.18 CF. It was also agreed to include the reference to V.18 in the note under 1 in section 10.2.1 in V.8bis. No agreement was reached on the recommendation to change the note as proposed in SAVD-95-117. V.8BIS AD HOC GROUPS SAVD-95-139 (L. Brown, V.8bis Rapporteur) summarizes the open issues related to V.8bis. There was general agreement to the CF coding proposed in this document which had been developed in one of the ad hoc discussions. There was an extended discussion when it came time to address the CC, specifically about what was indicated by setting the V.42bis bit. It was not clear if this meant V.42bis on top of V.42 or V.42bis on top of any data link layer. The group was not able to come to any resolution; the Associate Rapporteur asked for contributions aimed at resolving this point prior to the October WP meeting. Consideration should be given to adding all or some of the items assigned code points under data transmission in H.324 to the list of CCs associated with data in V.8bis. It was agreed that there would be no coupling between the “standard” and “non-standard” CFs and CCs. Bit coding was retained. The proposal was to merge the Message Type and Function Field into a single octet. After some off line discussion, it was decided to use a code point in each of the CC fields to point to the availability of non-standard features. SAVD-95-140 (J. Brownlie, BT plc) addresses a previous point raised about the consideration given to the voice caller in the BT proposal (see discussion after SAVD-95-094 above). This paper proposes adding another scenario to SAVD-95-094 to address the voice caller by the sending of an FL (a brief burst of upper V.21 [H] as defined in SAVD 95-094) preceding the OGM (Out Going Message). During the discussion, it was pointed out that this system could fail if CI were being sent and an echo suppresser was on the connection. J. Brownlie agreed that this could happen, but he stated that he would be willing to live with a failure at this point in the call, which he categorized as not as serious a problem as missing a signal (as in Draft Recommendation V.8bis as presently written). SAVD-95-138 (L. Smith, AT&T) reports on the discussions of the ad hoc group on dual tone signal related issues. It proposes to optionally allow the use of higher tone levels for the signals used during an established call. Another proposal is to allow these optional higher levels to be used during call establishment when a calling tone is detected, in order to prevent blocking of the signal by network echo suppressers. It additionally proposes to change the ratio of DT

September 1995 Vol. 6.6 Copyright © CSR 1995 49 COMMUNICATIONS STANDARDS REVIEW - TELECOMMUNICATIONS to the appended signal in the 400 ms sequence and to allow the optional delaying of the OGM when there is a likelihood that a near end echo suppresser might be present. All of the proposals made in SAVD-95-138 were accepted with the exception of changing the length of the V.21 (H) marking frequency. SAVD-95-144 (A. Heinke, Radish) is the report of the ad hoc group on V.8bis. Since the proposal for an indicator for non-standard facilities was already accepted, the discussion centered around the proposal for the concatenation of the Message Type and Function fields. It was agreed to combine the Message Type and Function fields. As part of the new coding, it was also agreed to assign an extension bit to accommodate additional future messages. LIAISONS

SAVD-95-100 (R. Schaphorst, Q2/15 GSTN Videophone Rapporteur) is a liaison from Q2/15 regarding the use of V.8bis in the GSTN Videophone. The Associate Rapporteur briefly introduced this liaison, and summarized the following points: • SG 15 wants V.8bis as soon as they can get it. • The H.324 designation should be moved from being a CC (Communication Capability) to becoming a CF (Communication Function) at the same time expanding the V.8bis structure to three levels. • The scope of V.8bis should be extended to provide the functionality of V.8 to eliminate the need to run both protocols sequentially. It was decided to defer any decision on this request until D. Lindbergh (PictureTel, SG 15) arrived. C. Garthwaite (Microsoft) accepted the job as editor for a “style guide on how to assign V.8bis code points” to be used as a guide by those groups who have been assigned a CF. SAVD-95-102 is a liaison from the Q19/8 Rapporteurs group. It was introduced by G. Griffith (Rockwell), and it asks the following questions: • Should OGM1 (Out Going Message 1) be made mandatory? • Is the delay of one second plus a round trip delay worth it, just to be voice centric? • When should V.8bis be used as opposed to V.8? Q19/8 feels that a better recovery mechanism is needed for the potential collision between CNG (T.30 Calling Tone) and MR (Mode Request). There was some discussion about what was meant by OGM1. Most people felt that it may have been the “Press 1 for Fax” etc. message. In any case, it was generally agreed that this should be done in SG 8, not SG 14. It was pointed out that a more fair comparison would be to compare the delay for OGM1 to the delay experienced when using the “wait until 5 rings” technique used by many fax/tel switches. SAVD-95-082 (J. Magill, Q1/14 Rapporteur) is the report of the last meeting of the Joint Coordination Group (JCG) on Audio Visual Multi-Media Systems (AVMMS). (See report in this issue of CSR-T.) J. Magill re- introduced section 5.2 of this document. Basically, it once more asks the question about the relationship between V.8bis and V.8. J. Magill expressed the urgency to respond to SG 8 out of this meeting, since SG 14’s lack of adequate response in the past had been partially responsible for the “No” vote from the UK. SAVD-95-104 is a liaison from Q2/8 and Q7/8 requesting the inclusion of Videotext in V.8bis. OUTGOING LIAISONS

SAVD-95-141 is a proposed liaison in response to a SG 8 liaison on the use of V.8bis in facsimile. It was introduced by G. Griffith (Rockwell). It answers each of the questions raised by SG 8. There was considerable discussion. It was decided to send SG 8 a copy of Appendix 1 (V.8bis features) of the latest draft in order to answer the question regarding the relationship between V.8 and V.8bis. SAVD-95-145 is a proposed liaison to SGs 1, 2, 8, and 15 on the proposed coding of the CF and CC for Data Communications. It was introduced by M. Buckley (AT&T). It was accepted with minor editorial corrections. Dick Brandt, dB Consulting

Q7/14, DTE-DCE INTERFACES R.R. Damm (Deutsche Telekom AG, Germany) is the Rapporteur for DTE-DCE (Data Terminal Equipment - Data Circuit Terminating Equipment) Interfaces.

LIAISONS

SAVD-95-123 is a liaison statement from Q10/8 regarding the data port for videotelephones. Q10/8 has been working on using the T.123 protocol stack, but they are suspending their efforts in order to coordinate with SG 14. It requests that if SG 14 accepts the charter, they inform Q10/8 of their efforts. There was agreement to do so, and to send affirmative liaison back to Q10/8. (See SAVD-95-149 below.) SAVD-95-129 (J. Decuir, Microsoft) requests that the Synchronous Access proposal, SAVD-95-127 (B. O’Mahony, Intel), include provisions for support of V.34 half-duplex operation. If done expeditiously, draft Annex B/T.31 could be simplified to use Synchronous Access. This was later agreed. (See SAVD-95-151 below.) SAVD-95-146 is a liaison statement from Q2/15. It contains a collection of three papers addressed to the requirements of DTE/DCE signaling and control for GSTN videophones. They were presented by T. Geary (Rockwell), Chair of the SG 15 ad hoc group on this topic. D. Lindbergh (PictureTel) also explained some details. Figures 1 and 2 in the first paper (LBC-95-238r1) show three different DTE-DCE interfaces: • H.324 videophone to V.34 modem • H.324 videophone with microphone and camera connected to PC with CRT and speaker • H.324 PC with CRT and camera connected to V.34 modem with microphone, voice codec, and H.223 multiplexer It was noted that these requirements had been discussed in the July TR-30 DTE-SAVD DCE Ad Hoc meeting (CSR-T 6.5 page 47 and SAVD-95-125 meeting report), and that several of these requirements were addressed in technical contributions to that meeting. V.25TER-RELATED ITEMS

SAVD-95-148 contains proposed editorial corrections for Draft Recommendation V.25ter. It was originally generated by R.R. Damm after examining the final SG 14 version of V.25ter. There was consensus to fix the four obvious typographical errors and to reserve the extra wording on the ATZ command for later consideration. The editor agreed to forward these to the ITU TSB. SAVD-95-134 (J. Decuir, Microsoft) is a preview of TR-30 work directed to filling the place holder for AT+T test commands in section 6.7 of V.25ter. This is being finalized in TR-30 to provide a contribution to the WP1/14 meeting in Munich October 9-14. No action was taken. MULTIPLEXING ISSUES

SAVD-95-124 (B. O’Mahony, Intel, and editor of TR-30.1’s PN-3359 on DTE-SAVD DCE interfaces) summarizes the requirements for a DTE SAVD DCE multiplexer (listed below). Several delegates expressed support. • Support media source/sinks in either DCE or DTE. • Support voice in compressed or uncompressed form. • Support video in compressed form only. • Low induced latency. • Maintain high DCE-DCE bandwidth efficiency. • Support the maximum (DCE-DCE) line rate. • Support the “realities” of PC port flow control. • Allow In-Band V.25ter commands and indications. • Support switching of multimedia modes. SAVD-95-121 (D. Lindbergh, PictureTel) supports SAVD-95-124 (B. O’Mahony, Intel) and adds three additional requirements: • The interface must allow for more than one channel of each media type, as per H.324 • Limiting induced buffer latency and jitter is of paramount importance • Include a method to detect and report buffer underruns with indication where they occurred There was consensus that these requirements should all be accepted and combined into one document for the Working Party 1/14 meeting. However, some work is needed on the last item. SAVD-95-125 (J. Decuir, Microsoft) is a report of the TR-30 DTE-SAVD DCE Ad Hoc meeting of July 6 and 7, 1995. Many of the papers presented here were also presented there. It contains a summary of the requirements for these interfaces. It also notes that there are three different levels of DTE-DCE interface being considered: • Low level, the DCE does modulation and maybe some bit-processing (Figure 2/H.324, right V.24 interface, or LBC 95-238r1 Figure 1) (This is also the subject of SAVD-95-127). • Mid level, the DCE and DTE both handle some media I/O, the DCE includes the multiplexer (LBC 95-238r1 Figure 2, etc.) (This is also the subject of several contributions at this meeting).

• High level, the DCE provides a data port to the DTE (Figure 2/H.324, left V.24 interface). It was noted that a simple model with the end-to-end multiplexer (e.g., H.223) mapped to async and delivered to the DTE was inadequate. It cannot meet the requirements agreed upon. New proposals for DTE-DCE multiplexers and low level interfaces were generated at this meeting (see below). The need for DTE-DCE error control was addressed, but tabled. This is the subject of SAVD-95-126 (B. O’Mahony, Intel) below. It was noted that work is still needed on a V.8bis control interface and on the SAVD DCE control model (see SAVD- 95-147 below). SAVD-95-133 (J. Decuir, Microsoft) is a proposal for a simple mid-level DTE-DCE multiplexer. It is based on a proposal discussed at the TR-30 Ad Hoc but merged with the Synchronous Access proposal in SAVD-95-127 (see below). It also proposes that the multiplexer be based on extending proposed Draft Recommendation V.ib to 8 bit codes (see SAVD-95-135 below). The question was raised as to when it is appropriate to use distinct escape codes with the suggestion of using for local control multiplexing (e.g., TIA-617 and V.ib) and for media stream control. This was tabled. SAVD-95-126 (B. O’Mahony, Intel) proposes a DTE-DCE Multiplexer that includes simple local error control. An example was developed and evaluated around the use of uncompressed G.711 audio. It does not address media stream identification. No action was taken. SAVD-95-142 (M. Patrick, Motorola) proposes a mechanism for multiplexing multiple streams of data and AT+S commands to select the sources and sinks for each of these streams. It is intended for use in the mid-level model, in which the multiplexer (e.g., H.223) is in the DCE. (Note: SAVD-95-147 below is based on SAVD-95-142.) SAVD-95-127 (B. O’Mahony, Editor, Intel, and Microsoft) is a revised draft of synchronous modes extensions to V.25ter. It is directed at the low level interfaces. It is based on draft Annex B/T.31, but it adds several elements deemed necessary to support SAVD, including: • Modes controls, based upon extending the +ES parameter in V.25ter • Adjustable flow control thresholds, based upon a new +IFT command • Additional in-band commands and indications based upon the character • In-band controls on DCE bit processing (High level Data Link Control framing and Cyclic Redundancy Codes) • In-band controls and indications for the signal converter (retrains and rate renegotiations) It was noted that this is a different approach to the DTE-DCE interface compared to V.14 or V42, but the suggestion to label it “V.14bis” instead of “Annex B of V.25ter” was tabled for SG 14. SAVD-95-122 (D. Lindbergh, PictureTel) contains comments on SAVD-95-127. The comments include: • Using the same escape mechanism as used in ISO/IEC 3309 and T.123 instead of • Using small buffers (~10 octets) for latency minimization • Adding a parameter to Table B-1 for “action transmit underrun when NOT following the flag” • Clarification questions about Table B-2 • Suggesting that means are needed to send V.25ter command and response strings in data state The clarification questions were answered in the meeting. The editor will undertake to clarify the material. It was noted that the last item is covered by SAVD-95-135 (see below). During discussion, it was noted that in T.123 use, V.8bis or other means will be needed to negotiate whether asynchronously framed HDLC or synchronously framed HDLC will be used over the wire. As currently defined, asynchronous framing is the default because common V.25ter modems cannot/do not provide synchronous access in a standard way. SAVD-95-147 (M. Patrick, Motorola ISG) is a detailed mid-level and high level H.324 control proposal. Given its length (15 pages), it was not presented in detail. It builds on SAVD-95-142 (see above), and contains an implied DCE control model. It describes AT+S commands for control of channel multiplexers and for data stream format control, including video, audio, and data capabilities and modes. It also includes a number of based in-band commands for audio and video media stream control. This proposal specifies that the H.223 multiplexer and the H.245 control entity be included in the DCE. M. Patrick raised the question about how the H.245 control entity could be moved to the DTE, but this was tabled. SAVD-95-135 (J. Decuir, Editor, Microsoft) is a proposal to modify proposed Draft Recommendation V.ib so that in-band 8 bit commands could be used. This would then provide the code space to handle the in-band commands cited

in previous contributions (e.g., SAVD-95-133). V.ib itself was offered as a solution to the cited requirement to multiplex V.25ter commands and responses in-band. OTHER BUSINESS

SAVD-95-143 (J. Decuir, Microsoft) is a report on the personal computer industry work to define a Universal Serial Bus (USB). The attachment is a draft Telephony Device Class Definition that proposes how to use the USB resources for connecting telephones, modems, and ISDN devices to a PC. The advantages claimed versus standard serial interfaces include: error control, much higher bandwidth (12 Mbit/s), and naturally multiplexed. The latter feature is considered useful for SAVD DCE. R.R. Damm indicated that Q6/14 would have a strong interest in this work. He requested an official contribution from the companies involved. J. Decuir indicated that he would bring a submission for information to the October WP 1/14 meeting. SAVD-95-128 (TR-30) addresses DTE/DCE signaling and control for GSTN Visual Telephone Terminal Applications and the need for additional functionality in the data port in self-contained videophones. It requests that the SG 15 LBC experts consider extending the functionality of the data port described in section 6.8.1/H.324. DISCUSSION AND DECISIONS

The Rapporteurs group listed a series of questions to decide, settled some of them, and reserved the rest for future discussion. The results are summarized as follows. Q7/14 agreed that the provisional requirements for the DTE-DCE interface, based upon SAVD-95-124 and SAVD- 95-121, include: • Allow async DTEs to generate arbitrary synchronous bit streams on the PSTN • Support level interface - DTE does most of the work. • Low latency and jitter. • Maintain high DTE-DCE efficiency. • Support 28,800. • Support realities of PC UARTS. • Support inband V.25ter commands. • Support protocol switching. • Support V.34 half duplex. • Underrun error recovery in framed sub-mode. • In framed sub-mode, HDLC 0 bits, CRCs, idle flags, NRZ/NRZI bit processing. • For transparent sub-mode, optional hunt for sync sequences. Q7/14 agreed to use SAVD-95-127 as the basis for the low level interface and to include V.34 half duplex commands as requested by TR-29 in SAVD-95-129. For lack of time, the following questions were not decided and reserved for further study: • The inclusion of CRC control codes in sync mode (proposed in SAVD-95-133) • Mid-level mux (SAVD-95-126, SAVD-95-133, SAVD-95-142, SAVD-95-147) • SAVD DCE control model (SAVD-95-147) • V.ib for basis of multiplexing scheme (SAVD-95-133, SAVD-95-135) • How to control V.8bis (issue raised in SAVD-95-125) • Where is sync access as a recommendation (V.25ter annex, V.14bis, etc.) • Escape character policy (SAVD-95-121, SAVD-95-127, SAVD-95-133) In discussion of the last item, B. O’Mahony (Intel) proposed that perhaps the synchronous access proposal in SAVD- 95-127 should be extended to include a third submode for support of ISO-3309 HDLC frame tunneling, as used by T.123/Q.922 and PPP (Point-to-Point Protocol). In this mode, the DCE would convert ISO-3309 octet-stuffed streams to synchronous HDLC. There was support for this idea. OUTGOING LIAISONS

SAVD-95-149 is a liaison statement to Q10/8 confirming that Q7/14 will take on the work of defining DTE-SAVD interfaces and that Q10/8 will receive a status report. It was edited in discussion and approved as SAVD-95-149rev1. SAVD-95-150 is a liaison statement to Q2/15 confirming that Q7/14 will take on the work of defining DTE-SAVD interfaces and that Q2/15 will receive a status report. It was edited in discussion and approved as SAVD-95-150rev1.

SAVD-95-151 is a liaison statement to Q5/8 indicating that Q7/14 has developed a Synchronous Access proposed extension to V.25ter based upon their draft Annex B/T.31. It invites Q5/8 to simplify Annex B/T.31 to reference this Synchronous Access proposal. This was approved. Joe Decuir, Microsoft

SG 14 MEETING ROSTER, AUGUST 7 – 12, 1995, H OOD RIVER, OR Dick Brandt, dB Consulting for AT&T Chair WP 14/1 John Magill, Probe Communications (UK) Rapporteur Q1/14 V.savd Les Brown, Motorola - ISG Associate Rapporteur V.8bis Dick Stuart, Penril Datability Networks Rapporteur Q1/14 High Speed Modems Ralf-Rainer Damm, Deutsche Telekom (Germany) Rapporteur Q6/14 and DTE-DCE Interfaces AT&T Bill Betts AT&T Mike Buckley AT&T Fred Burg AT&T Larry Smith AT&T R.K. Smith Bellcore Wes Henry British Telecom PLC (UK) John Brownlie Cresta Systems Allesandro Gatti IBM Jeff Derby IBM Ali Sadri Intel Chris Hansen Intel Greg Kisor Intel Barry O’Mahony Microsoft Joe Decuir Microsoft Charlie Garthwaite National Semiconductor Mai Yong Nokia (Finland) Lippo Rantanen Penril Datability Networks Aleksander Purkovic PictureTel Dave Lindbergh Racal Datacomm (UK) Chris Firth Radish Mike Winseck Rockwell Glenn Griffith Siemens (Germany) Istvan Sebestyen US Robotics Chester Szozepucha

COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES: Communications Standards Review–Radiocommunications (ISSN 1081-6852), a technical journal that reports on U.S. (TIA) Standards Committee meetings in wireless WAN data communications. CSR-R is published six to eight times per year Communications Standards Summary (ISSN 1075-5721), a quarterly publication reporting on all active projects and recently completed standards of the Telecommunications Industry Association’s (TIA’s) TR-committees. Authorized by TIA. Fiber Optics Standards Summary (ISSN 1081-6844), a quarterly publication reporting on all active projects and recently completed standards of the Telecommunications Industry Association’s (TIA’s) FO- committees. Authorized by TIA. To receive a complimentary issue of any of CSR’s technical journals, please contact Elaine Baskin, tel +1 415 856-9018, fax +1 415 856-6591, e-mail [email protected] or [email protected]

ACRONYM GLOSSARY

ADSI Analog Display Services Interface (Bellcore) ASVD Analog SVD ATM Asynchronous Transfer Mode AVD Alternating Voice Data AVIS Audio Visual Information Systems AVMMS AudioVisual and MultiMedia Services BBS Bulletin Board System CAMA Centralized Automatic Message Accounting CATV Cable Television CC Communication Capability field CCITT Consultative Committee International Telephone and Telegraph CCT Consultative Committee - Telecommunications (Trilateral) CDMA Code Division Multiple Access CEBus Consumer Electronics Bus CENELEC Commission Europeenne de Normalisation Electrotechnique CF Center Frequencies CI Call Indicator (V.8) CISPR International Special Committee on Radio Interference CMT Cellular Messaging Teleservice CNG T.30 Calling Tone CO Central Office CPE Customer Premise Equipment CRC Cyclic Redundancy Code CRT Cathode Ray Tube DAVIC Digital Audio-Visual Council DC Direct Current DCE Data Circuit Terminating Equipment DDS Digital Data Service DSM-CC Digital Storage Media - Command and Control DSVD Digital SVD DT Dual Tone DTC Digital Transmit Command ECMA European Communications Manufacturers Association EIA Electronic Industry Association EMC Electromagnetic Compatibility ESD Electrostatic Discharge FCC Federal Communications Commission (U.S.) FL Facilities List FTP File Transfer Protocol HAC Hearing Aid Compatible HDLC High Level Data Link Control ICS Incoming Call Screening IEC International Electrotechnical Comm. IPR Intellectual Property Rights ISDN Integrated Services Digital Network ISO International Standards Organization ITIC Information Technology Industry Council ITU International Telecommunications Union JBIG Joint Binary Image Group JCG Joint Coordination Group JPEG Joint Photographics Expert Group JTC Joint Technical Committee

LAN Local Area Network LAP Link Access Protocol LAPM Link Access Protocol Modem (V.42) LBC Low Bit rate Coder MFP Multifunction Peripheral MFPI Multifunction Peripheral Interface MIB Management Information Base MLTS Multi-Line Telecommunications Systems MM Multimode MPEG Motion Picture Experts Group MRA Mutual Recognition Agreements MS Mode Select NAFTA North American Free Trade Agreement NEC National Electric Code (US) NPRM Notice of Proposed Rule Making (FCC) OGM Out-Going Message OSHA Occupational Safety and Health Administration OSI Open System Interconnection PBX Private Branch Exchange PCM Pulse Code Modulation PSTN Public Switched Telephone Network QSIG Requirements specified by the ITU Q series recommendations (See PSS1) RFI Radio Frequency Interference RMS Root Mean Square ROLR Receive Objective Loudness Rating SG Study Group (ITU, CCITT) TAG Technical Advisory Group TEM Transvers Electro Magnetic TIA Telecommunications Industry Association TOLR Transmit Objective Loudness Rating TSAG Telecommunication Standardization Advisory Group TSB Telecommunication Systems Bulletin (TIA) TSB Telecommunications Standardization Board (ITU) TWAIN Scanner Interface API (MFPI work) UART Universal Asynchronous Receiver Transmitter UTP Unshielded Twisted Pair VoD Video on Demand WCPE Wireless CPE XAPI eXtensive Application Programming Interface

1995 MEETING SCHEDULES AS OF AUGUST 31. 1995 Subject to Change without Notice TR-45 Sep 4 Denver, CO TR41.1/ETSI Oct 23 26 Mainz, Germany G.dsvd Rapp Sep 11 - 15 Annapolis, MD BTC2 JTC(Air) Sep 11 - 15 --- TR-41.6 Oct 23 - 27 --- TR-30 Sep 11 - 15 Portland, OR TR-45.4 Oct 30-Nov 3 Chicago, IL TR-45.5 Sep 11 - 15 Cape Cod, MA JTC(Air) Nov 6 - 10 --- TR-45.3 Sep 12 - 14 Quebec City, Que T1P1 Nov 6 - 10 --- G.dsvd Rapp Sep 14 - 15 Bethesda, MD ITU-T SG 15 Nov 13 - 24 Geneva SG8 Rapp Sep 18 - 22 Palo Alto, CA T1E1 Nov 13 - 17 Orlando, FL T1S1 Sep 18 - 22 New Jersey area TR-30 Nov 13 - 17 Orlando, FL TR-41 Sep 18 - 22 Vancouver, BC TR-45.2 Nov 13 - 17 CO Springs, CO TR-45.2 Sep 18 - 22 San Antonio, TX TR-45.3 Nov 13 - 17 Orlando, FL SG 15 Rapp Sep 25 - 29 VA, U.S.A. TR-45.5 Nov 13 - 17 CO Springs, CO TR-45.4 Sep 25 - 29 Orlando, FL ITU-R SG 8A Nov 22–Dec 1 Geneva TR-46.3 Sep 25 CO Springs, CO ETSI TE Nov 27 - Dec1 Antwerp, Belgium Q3, 8, 15/8 Rapp Oct --- TR-45 Nov 27 Dallas, TX Q10/8 Oct 2 - 6 Paris, France TR-46 Nov 28-Dec 1 San Antonio, TX TR-46 Oct 2 - 6 Orlando, FL T1S1 Dec 4 - 8 --- TR-45.3 Oct 3 - 5 Richardson, TX TR-41 Dec 4 - 8 Los Angeles, CA WP 14/1 Oct 9 - 14 Munich TR-45.4 Dec 4 - 8 Orlando, FL TR-29 Oct 16 - 19 San Diego, CA TR-45.5 Dec 4 - 8 San Diego, CA TR-45.2 Oct 16 - 20 Tampa, FL T1A1 Dec 11 - 15 San Jose, CA TR-45.3 Oct 16 - 20 Toronto, Ont TR-45.2 Dec 11 - 15 Maui, HI TR-45.5 Oct 16 - 20 Seattle, WA TR-45.3 Dec 11 - 15 Maui, HI SG 15 LBC Oct 17 - 20 Darmstadt, FRG G.dsvd Rapp Oct 23 - 27 Europe 1996 CALENDAR Subject to Change without Notice TR-45.4 Jan 8 - 12 San Diego, CA TR-41 Jun 10 - 14 Ottawa, Ont TR-29 Jan 15 - 19 San Antonio, TX TR-45.4 Jun 24 - 28 Durango, CO SG 15 LBC Jan 23 - 26 --- TR-45.4 Jul 29-Aug 2 Lake Tahoe, NV TR-30 Feb 5 - 9 Hawaii TR-30 Aug 5 - 9 --- SG 8 Feb 6 - 15 Geneva TR-41 Sep 9 - 13 --- TR-45.4 Feb 12 - 16 Houston, TX TR-45.4 Sep 9 - 13 Vancouver, BC TR-45.4 Mar 18 - 22 Phoenix, AZ TR-45.4 Oct 7 - 11 Seattle, WA SG 14 Mar 19 -27 Geneva TR-30 Oct 14 - 18 --- TR-41 Apr 1 - 5 Fort Meyers, FL TR-45.4 Nov 11 - 15 El Paso, TX TR-30 Apr 15 - 19 --- TR-30 Dec 2 - 6 --- TR-45.4 Apr 22 - 26 San Antonio, TX TR-41 Dec 9 - 13 --- TR-29 May 6 - 10 --- TR-45.4 Dec 9 - 13 Tampa, FL TR-45.4 May 20 - 24 Chicago, IL SG 15 May 28 - Jun 7 Geneva TR-30 Jun 3 - 7 ---

Communications Standards Review –Telecommunications (ISSN 1081-4655) is published 6 - 8 times per year, within days after the latest, related standards meetings. Editor: Elaine J. Baskin, Ph.D. Technical Editor: Ken Krechmer. Copyright © 1995, Communications Standards Review. All rights reserved. Copying of individual articles for distribution within an organization is permitted. Subscriptions: $595.00 per year worldwide. Discounts for additional subscriptions are available. Submit articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto, CA 94303-3024 U.S.A. Tel: +1-415-856-9018. Fax: +1-415-856-6591. e-mail: [email protected] or [email protected]. 16906