communications standards review telecommunications

September-October 1997 Vol. 8.8 Copyright © CSR 1997 1

COMMUNICATIONS STANDARDSREVIEW

TELECOMMUNICATIONS

Volume 8, Number 8 September-October 1997

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-30.3 Data Communications Equipment Evaluation and Network Interfaces, June 9, 1997, Costa Mesa, CA.......3TR-30.3 Meeting Roster, June 9, 1997, Costa Mesa, CA...................................................................4

TR-29, Facsimile Systems and Equipment Engineering, August 4 – 6, 1997, Santa Rosa, CA............................5TR-29.1 Facsimile and File Transfer Protocols...............................................................................6TR-29.2 Facsimile Digital Interfaces...........................................................................................9TR-29 Partial Meeting Roster, August 4 – 7, 1997, Santa Rosa, CA.....................................................10

TR-30, Data Transmission Systems & Equipment, August 11 – 15, 1997, Quebec City, Canada.........................11TR-30.1 Modems...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11TR-30.2 Digital Interfaces Including DTE-DCE Protocols..................................................................12TR-30.3 Data Communications Equipment Evaluation and Network Interfaces.........................................13TR-30 meeting Roster, August 11 - 15, 1997, Quebec City, Quebec, Canada...........................................16

TR-30.1 PCM Modem Ad Hoc Meeting, August 12 – 13, 1997, Quebec City, Canada......................................171998 Standards Committee Meeting Schedules as of September 29, 1997....................................................19TR-41, User Premises Telecom Equipment, August 18 – 22, 1997, Quebec City, Quebec, Canada........................20

TR-41.1, Multi-Line Communication Terminal Systems...................................................................20TR-41.1.1 MLTS Transmission..................................................................................................21TR-41.2 Conformity Assessment................................................................................................22TR-41.3 and CSA T510, Telephones and Acoustic Terminals..............................................................25TR-41.5, Multimedia Building Distribution Systems........................................................................27TR-41.6 Wireless User Premises Equipment (WUPE)........................................................................28TR-41.6.1, Personal Wireless Telecommunications.........................................................................28TR-41.6.3 PACS-WUPE...........................................................................................................29TR-41.7 Environmental and Safety Considerations..........................................................................29TR-41.8 commercial and residential premises wiring........................................................................31TR-41.8.1 Commercial Building Cabling......................................................................................31TR-41.8.2, Residential & Light Commercial Premises Distribution.....................................................33TR-41.8.3, Building Pathways and Spaces for Telecommunications.....................................................33TR-41.8.4, Customer-Owned Outside Plant....................................................................................34TR-41.8.5, Definitions...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Report of TR-41.9 Regulatory Considerations on Terminal Attachment Programs....................................34TR-41.10, Private Integrated Service Network (PISN).......................................................................37TR-41 Partial Meeting Roster, August 18 – 22, 1997, Quebec City, Canada............................................39

Q19/16, Extension to existing ITU-T speech coding standards at bit rates below 16 kbit/sSeptember 2 – 5, 1997, Bethesda, MD....................................................................................40

SG 16 Multimedia, WP1 & 2 and Rapporteur Meetings, September 4 – 12, 1997, Sunriver, OR..........................43Q3/16 , Data Protocols for Multimedia Conferencing.......................................................................43Q4/16, V.8bis.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Question 7/16 Rapporteurs Meeting, DCE/DCE Protocols,................................................................46Q9/16, Accessibility to Multimedia for people with disabilities..........................................................48

COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS

2 Vol. 8.8 Copyright © CSR 1997 September-October 1997

Q11/16 Circuit-Switched NEtwork Muiltimedia Systems and Terminals.................................................50Q12/16, Q13/16 and Q14/16 General Information...........................................................................50Q12/16 B-ISDN Multimedia Systems and Terminals.........................................................................51Q13/16 Packet-Switched Multimedia Systems and Terminals..............................................................54Q14/16 Common Protocols, MCUs and Protocols for Interworking with H.300-Series Terminals................59Q15/16 Advanced Video Coding.................................................................................................62Q23/16 PCM Modems..............................................................................................................62Partial Roster for SG 16 WP1&2 and Rapporteur Meetings, September 4 – 12, 1997, Sunriver, OR...............65

Acronym Glossary..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .671997 Standards Committee Meeting Schedules as of September 29, 1997....................................................69



REPORT OF TR-30.3 DATA COMMUNICATIONS EQUIPMENTEVALUATION AND NETWORK INTERFACES

JUNE 9, 1997, COSTA MESA, CAPN-3459, REVISING TSB-37A (T ELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATINGMODEM PERFORMANCE).

TR-30.3/97-06-042© (J. Douglass, TR-30.3 Chair) is the committee letter ballot for PN-3459 (to be TSB-37-B)“Telephone Network Transmission Model for Evaluating Modem Performance.” TR-30.3/97-06-043 (J. Dou-glass, TR-30.3 Chair) contains 16 ballot responses. TR-30.3/97-06-045 (S. Satchell, Motorola) discussesMotorola’s “No” vote on the current draft of PN-3459, noting that they are only concerned with the significantnumber of corrections required. TAS and Consultronics also voted “no.”

TR-30.3/97-06-046 (R. Perez, Bellcore) contains data from Bellcore’s SR-NWT-002027, Digital Access Survey,February 1993. This data from a DLC loop plant survey in the period 1986-1988 indicates that the addition ofDigital Loop Carriers to TSB-37-B does not require any changes in the test loop configurations and combinations.

TAS’ primary concern was the existence of technical changes between the ballot and the most recent draft beforeballot. Technical changes must be made in the committee in response to submissions. The previous editor (W.Park, USR) acknowledges the presence of those technical changes.

Motorola’s primary concerns were the large number of typographical errors and the lack of rationale for the levels ofnetwork impairments. S. Satchell (Motorola) presented TR-30.3/97-06-045 , his new draft of PN-3459. Changemarks were not included in the draft.

Since there were technical changes in the document without TR-30.3’s approval and there was not a paper trail forthese technical changes, TR-30.3 agreed to withdraw the ballot. A new ballot will be submitted at the next meetingby S. Satchell (Motorola), the new editor of PN-3459.

PN-3508, REVISION OF TSB-38

There were no submissions for the revision of TSB-38, Test Procedures for Evaluation of 2 Wire Duplex Modems.S. Satchell (Motorola) will submit a revised version of TSB-38/V.56ter based on TSB-37-B ballot. S. Satchell andW. Henderson (Henderson Communications Laboratories) will work on Annex F. S. Satchell will put the currentdraft of PN-3508 on the FTP site and continue editing.

PN-3857, TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING PCM MODEMSPERFORMANCE

TR-30.3/97-04-039 (J. Douglass, TR-30.3 Chair) is a liaison to the TR-30.1 Ad Hoc concerning PCMmodems. TR-30.3/97-06-047 (P. Caldera, Siemens) discusses gain and total distortion of linecards. TR-30.3/97-06-048 (R. Hill, Sage Instruments) discusses use of the 23 tone test to qualify circuits for PCMmodems.

After reviewing the contributions, the following comments were made:

• The 23 tone test is for line, loop and trunk testing.• Using the current frequency spacing scheme, there is only room for a 25 tone test. The 23 tone test relies on the

uniform frequency spacing of tones.• The energy distribution of the 23 tones test should be similar to that of a V.34 modem, but was developed to

match a half-duplex V.29 signal.• The IEEE-743 committee has the responsibility of defining line test equipment.• Specification IEEE-743 (Standard Equipment Requirements and Measurement Techniques for Analog

Transmission Parameters for Telecommunications) was intended for lease line testing.• The 23 tone test measures Inter Modulation Distortion (IMD) across the band. Frequency dependency is not

included. 2nd and 3rd order IMD are measured independently. Transformers tend to have more NLD (non-lineardistortion) at lower frequencies (where they saturate) than at the higher frequencies. Frequency dependent non-linearity is important to PCM modems.

• V.34 and probably PCM modems may adjust the bandwidth through the spectral shaping and other parameters.Measurements from the existing 23 tone test may not apply.



• Measurements of the line attenuation from 3300 Hz to 4000 Hz and from 40 Hz to 200 Hz would be veryinteresting to TR-30.3. Measurements at 50 Hz, 75 Hz, 150 Hz, 180 Hz, 3300 Hz, and 4000 Hz are desirable.

• Analysis from 40 Hz to 200 Hz is important.• Testing should be considered down to ring frequency.

Jack Douglass, Oak Technologies

TR-30.3 MEETING ROSTER, JUNE 9, 1997, COSTA MESA, CA

Jack Douglass, Oak Technologies ChairTR-30.3Stephen Satchell, Motorola ISG Acting Chair TR-30.3

AirTouch Cellular David SalernoAnalog Devices Avi Ben-zurAnalog Devices Rao NuthalapatiBay Networks Slobodan JovanovicBay Networks Qingli LuiBellcore Ricardo PerezCeleritas Technologies Mike DolanC-net Kate BarnesCompaq Computers Edward NewmanConsultronics Louis ChenierDiamond Multimedia Daniel MooredB Consult’g (Motorola) Dick BrandtGDC Fred LucasHayes Dave RifeHenderson Labs Warren HendersonHenderson Labs Wayne SchultzHenderson Labs Art WallaceLucent Kent MinaMotorola ISG Les BrownMotorola ISG Stephen SatchellMultitech R.S. GopalanRockwell Mike GauerRockwell Glen GriffithSage Insturments Randy HillSiemens Neal KingSmart Link Leor BrenmanTAS Mike PellegriniTAS Charles SimmonsTexas Instruments Jean-Pierre HoudardUS Robotics Wayne Park



REPORT OF TR-29, FACSIMILE SYSTEMS AND EQUIPMENT ENGINEERING,AUGUST 4 – 6, 1997, SANTA ROSA, CA

INTELLECTUAL PROPERTY

Per current TIA policy, a request was made to ascertain intellectual property rights (IPR) associated with TR-29committee work. The status of IPR was noted as follows:

• SVF - Paradyne may have IPR related to this work.• V.8bis - H. Silbiger (Lucent) was aware that other companies have IPR related to V.8bis.• Mixed Raster Content - Xerox may have IPR related to this work and has submitted an IPR statement, TR-

29/96-11-55 (L. McIntyre, Xerox), which offers the IPR license-free if standardized.

ISO L IAISON

The Joint Photographics Expert Group (JPEG) met recently and is working on JPEG 2000. The Joint Binary ImageGroup (JBIG) committee is scheduled to meet in the second week of August, 1997 in Vancouver.

SG 8 LIAISON

The next ITU-T SG 8 meeting after October 1997 is June 9-18, 1998 in Geneva. L. McIntyre (Xerox) reported thatthe Q5/8 Rapporteur group met to finalize the white contributions for Recommendation T.44, Mixed Raster Content(MRC), and related revisions to the Group 3 fax recommendations. The second topic was to review extensions toMRC in which Japan is interested. The extension would allow for more than three layers, which would providesupport for computer generated images. Another extension would be to make provision for rendering hints, whichwill permit better compression in some circumstances.

TR-29.4 MEETING REPORT

G. Constantinou (DoD) reported on the TR-29.4 fax security meeting. TR-29.4 is continuing to study requirementsfor operations above 16 kbit/s; a draft will be worked on this fall. The MIL-STD-188-161D standard has continuedto progress over the last five years. NATO is still reviewing potential updates to the NATO StandardizationAgreement (STANAG) 5000 standard based on the contents of the US 161D standard. Fort Huachuca has establisheda web site in support of their testing activities. TR-29.4 has not decided when their next meeting will be held.

ONGOING TR-29 PROJECTS

No further progress has been made on TIA-538-A, PN-3553, Facsimile Coding Schemes and Coding ControlFunctions for Group 4 Facsimile, the update to the US equivalent to the ITU-T T.6 recommendation.

No work has been done yet on TIA-466-B, PN-3975, a new item. This project will be a US version of the mostrecent Group 3 fax T.30 enhancements.

HF Radio Fax, SP-3394, is still in the process of being published.

There was an IEEE ballot on a color test chart, the same chart being used by the ITU. The ITU version of the faxtest chart CD-ROM had a problem with one of the images.

PN-3194, TIA 465-A and TIA 466-A, Conformity Test Procedures on Fax Testing, has now been published as TSB-85.

REVIEW OF PROPOSED ITU-T SG 8 CONTRIBUTIONS

TR-29 reviewed a series of proposed US contributions to the October meeting of ITU-T Study Group 8 forsubmission to the U.S. Study Group D meeting on September 23, 1997.

TR-29/97-08-29 (D. Bodson, NCS, same as TR-29.2/97-08-8R1) contains text for a proposed corrigendumto ITU-T T.32 to correctly implement the FCLASS=2.1 designation for T.32. The updated document was supportedby TR-29.

TR-29/97-08-33 (J. Rafferty, Human Communications, same as TR-29.1/97-08-52) is a draft liaison requeston V.8 code points. After small change to the title to indicate the source of the draft liaison, the contribution wasagreed as amended. G. Griffith (Rockwell) agreed to informally bring up the topic of adding V.8 code points for faxat the August 1997 TR-30 meeting (see report this issue).



TR-29/97-08-34 (J. Rafferty, Human Communications, same as TR-29.1/97-08-50) is a proposed action planfor furthering the work on Extended Negotiations within SG 8. It is proposed that the work on the Draft Annex Xto T.30 continue beyond the October 1997 meeting and be targeted for Decision at the June 1998 meeting of SG 8.The contribution was accepted with some minor amendments.

TR-29/97-08-35 (J. Rafferty, Human Communications, same as TR-29.1/97-08-42R1) proposes refinementsto the draft Annex X resulting from review in a TR-29.1 ad-hoc meeting. TR-29 supported the proposedcontribution. J. Rafferty (Human Communications) agreed to do additional editing and circulate it before the StudyGroup D meeting if changes are made.

TR-29/97-08-36 (J. Rafferty, Human Communications, same as TR-29.1/97-08-44) and TR-29/97-08-37(J. Rafferty, Human Communications, same as TR-29.1/97-08-45) contain proposals for Binary File Transfer(BFT) Negotiations within Group 3 facsimile. The contributions, with minor edits, were supported by TR-29.

TR-29/97-08-38 (D. Duehren, Brooktrout, same as TR-29.1/97-08-55) contains proposed procedures for RealTime Group 3 Fax on IP networks. The contribution resulted from an ad-hoc meeting on real-time internet fax andreflects agreements reached by that group. D. Duehren (Brooktrout) noted that the contribution is in process andneeds further editorial work. Further work will be done, and it will be circulated among an ad-hoc group prior tosubmission to Study Group D. TR-29 supported this approach.

TR-29/97-8-39 (J. Rafferty, Human Communications, same as TR-29.1/97-08-53) is a proposal to simplifythe negotiation bits for MRC. This approach resulted from discussion within the TR-29.1 meeting. After extendeddiscussion, TR-29 supported the proposed contribution by a vote of 5 yes, 1 no and 2 abstentions.

TR-29/97-08-30 (J. Rafferty, Human Communications, same as TR-29.1/97-08-54) contains the currentInternet Draft for Tagged Image File Format (TIFF). TR-29 agreed that the latest available version of the TIFF-Fdraft should be submitted to the Study Group D meeting as a proposed contribution to Questions 1 and 4. TR-29/97-08-31 (L. McIntyre, Xerox) contains the latest Internet Draft for the TIFF-FX image file format. TR-29agreed that the latest versions of this document and of TIFF-F, contained in TR-29/97-08-30 , should both besubmitted with a single cover page to identify the attached documents.

TR-29/97-08-32 (S. Urban, Delta Information Systems, same as TR-29.1/97-08-51R1) is a proposedcontribution on considerations on requirements for e-mail facsimile. Some additional minor edits were made to thetext in this meeting. The contribution, as edited, was supported by TR-29. It was also reiterated that the InternetDrafts for TIFF-F and TIFF-FX should be submitted as supporting documents along with this contribution.

TR-29.1 FACSIMILE AND FILE TRANSFER PROTOCOLS

INTELLECTUAL PROPERTY

Per current TIA policy, a request was made to ascertain intellectual property rights (IPR) associated with committeework. The status of IPR was noted as follows:

• Simultaneous Voice and Fax: Paradyne may have IPR• Internet Fax: D. Duehren (Brooktrout) is aware of Intellectual Property associated with dial forwarding.• D. MacTaggart (CyberFax) is aware of potential IPR that may apply for real time fax over the Internet.• Fax Security: There is IPR on the security page from France Telecom and on public key management from RSA.

LIAISON REPORTS

ITU-T Q1/8 Facsimile TerminalsTR-29.1/97-08-49 (J. Rafferty, Human Communications) contains the meeting report of the June 1997 Q1/8Rapporteurs meeting, Facsimile Terminals. It was noted that several issues were raised on the draft annex onextended negotiations. Since the document is not fully stable, it is not likely to be ready for Determination inOctober 1997. The documents on Binary File Transfer (BFT) negotiations submitted by US companies wereaccepted as the basis for further work. There were liaisons on the matter of V.8 and V.8bis codepoints (see the Q1/8report in CSR Vol. 8.7).

ITU-T Q4/8 Document Communication ServicesTR-29.1/97-08-48 (H. Silbiger, Lucent) contains the Q4/8 meeting report (see the report in CSR-T Vol. 8.7).Action was taken in the meeting to work on service requirements for Internet fax. Two papers, CM2-043 (Delta,Lucent, Rockwell) and CM2-009 (RAD, Israel with CyberFax) were submitted on real-time session-based Internetfax. The US proposal included parameters for real time fax. A proposal from Israel on real time Internet fax was



submitted and ten issues were identified (see CSR-T Vol. 8.7 for details). The UK submitted an updated contribution(CM2-018) on a fax format for store and forward. Xerox submitted a proposal (CM2-044) to consider use ofTagged Image File Format-FX (TIFF-FX), but the actual proposal was not submitted, so no action was taken. Anad-hoc group did further work on the UK document and produced first drafts on F.Ifax, a set of service requirementsfor Internet fax, based loosely on F.182 (telefax 3 service). The ad-hoc group also worked on an updated draft(T.ifax1) of a message-based fax specification using the UK contribution as the starting point. The current draftswere accepted as the basis for further work (and are included in TR-29.1/97-08-48). Section 4.4 of the F.Ifaxdocument is a table of standardized options (the T.30 negotiable options) for Internet fax and outlines their potentialuse. A contribution from Japanese manufacturers requesting a simple mode of e-mail based Internet fax was notaccepted.

ITU-T SG 16 Q4, V-8 bisG. Griffith (Rockwell) reported on the Q4/16 Rapporteur’s meeting. Q4/16 will revise the tables in the V.8/V.8bisImplementor’s Guide to reference T.30 and T.66 (previously T.codes). Some duplication with T.66 has been deletedfrom the guide.

IETFJ. Rafferty (Human Communications) reported on the status of the IETF Internet Fax work group. There are newInternet Drafts for the TIFF-F and TIFF-FX fax image file formats and for WIDE, another proposal on how to sup-port fax within Internet e-mail. WIDE (Widely Integrated Distributed Environment) is a Japanese research project,see http://www.wide.ad.jp/ for further information.

PN-3675, EXTENDED NEGOTIATIONS

TR-29.1/97-08-41 (J. Rafferty, Human Communications) contains agreed text of the draft Annex X to T.30 onExtended Negotiations, including the results of the June 1997 Rapporteur meeting. J. Rafferty will check with theRapporteur to see if this update can be submitted as an editor’s contribution. Due to the various open issues, it isnot likely that Annex X can be Decided in October 1997. This status will be noted in the contribution and it will beproposed that the document be kept in a Determined status in October 1997 using the updated text. It was agreedthat an ad-hoc group will review open items related to corrections of the flowcharts. TR-29.1/97-08-42R1 ,refinements to Draft Annex X, is the results of the ad hoc group efforts.

There was also a discussion on the best procedure to request code points for V.8 as needed by extended negotiations.It was agreed that a contribution should be written which proposes text for the liaison to SG 16. It was also sug-gested that the liaison request a set of codepoints within V.8 for use by Group 3 facsimile. An ad-hoc group was setup to prepare a draft liaison.

PN-3799, I NTERNET FAX

TR-29.1/97-08-47 (A. Jain, AT&T) presents AT&T’s position regarding Internet Fax. They have an interest intransport over evolving IP networks, including “unmanaged networks” such as the Internet. They suggest thefollowing goals for Real Time fax:1) Meet expectations of current fax users for valid identification, true confirmation and minimal elongation of the

fax call.2) Provide economical implementation path for Service Providers.3) Provide “good behavior” for Network Backbone Providers (minimize bandwidth and graceful degradation). Their

definition of minimal acceptable elongation is to have the elongation be the lesser of 30 seconds or 5% of totalfax call time.

AT&T has developed an Internet simulation. They offer in TR-29.1/97-08-47 to provide facilities forindependent testing of fax protocols and to share results of the work with the “team.” There was a discussion onwhether there was a way to share the results within the standards process to help evaluate alternatives for real timefax protocols.

TR-29.1/97-08-40 (D. Duehren, Brooktrout) is a Real Time Fax update and reviews progress which has takenplace in related efforts such as the Voice Over Internet Protocol (VoIP) Forum. D. Duehren noted that the protocolproposed for VoIP is the use of the Real Time Protocol (RTP) over a User Datagram Protocol (UDP) transport.VoIP did not choose to use the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol due to itsoverhead. The contribution suggests that if this direction is adopted for fax, Brooktrout feels it is preferable to adaptan existing protocol for use over UDP, rather than create a new one. Several suggestions are made on how toprogress the work. There was also some discussion on the ten points, repeated in this paper, which were raised atthe previous Q4/8 Rapporteur’s meeting related to the RAD, Israel, contribution on real time fax. It is suggested



that the focus of addressing for real time fax be on the telephone number and that the Sub-address (SUB) be deliveredwithin the T.30 protocol itself, not as part of the address.

It is now suggested that the fax protocol should be independent of the underlying transport protocol and supportseveral lower level protocols such as TCP and RTP. It is also suggested that V.34 be left for further study at thistime due to the number of technical issues related to V.34 and V.8 handling. The contribution concludes that theIsraeli contribution and earlier TR-29.1 proposals form a basis for further work.

During discussion, D. Crocker (Brandenburg Consulting) commented that it is highly advantageous to use existingInternet protocols rather than inventing a new one, since the Internet is a shared environment and great pains havebeen taken to create protocols that will work in this shared environment.

TR-29.1/97-08-38 (H. Silbiger, Lucent) presents a real time internet fax proposal in the form of a draft T.Ifax2recommendation. It suggests that the parameters used in evaluating protocols include delay, data loss, bandwidth,implementation flexibility and integration with voice. The proposal is intended as a starting point and is subject toimprovement based on inputs from TR-29.1. The basic concept is to use a demod-remod approach for converting thefax signals and data into a digital form. Another part of the approach is to use signaling that has been defined inH.323; H.323 is the approach which will also be used for transport of real time voice over IP networks. The errorcorrection mode approach is similar to that of Error Correction Mode (ECM), but only uses a negative acknowledg-ment to request a re-transmission of missing packets. The packet correction approach is new and it not based on anexisting Internet protocol.

During discussion, it was noted that a set of state diagrams is missing in the current proposal. B. Boykin (Datarace)commented that there are timing issues which need to be considered in more detail.

TR-29.1/97-08-46 (N. Joffe, Cisco) presents a session-based fax proposal that is under review by the IETF.This approach does not attempt to port the T.30 protocol into the Internet environment, but instead relies on the useof Multipurpose Internet Mail Extension (MIME) for transport of data and uses an extended form of Simple MailTransfer Protocol (SMTP) for the protocol. It provides a mechanism for the recipient to advertise its capabilities andrequires confirmation of receipt during the session.

TR-29.1/97-08-43 (J. Rafferty, Human Communications) is an Electronic Messaging Association (EMA)recommendation for development of a single set of message-based Internet Fax standards. J. Rafferty noted thatJapanese manufacturers have expressed interest in being able have a “primitive” mode for store and forward via e-mailand that it may be feasible to accomplish this via reference to IETF Request for Comments (RFCs). The key requestfrom EMA members was that it is preferable that only a single messaging-based standard be developed.

There was discussion on aspects of the real time fax proposals and how to progress the work. D. Crocker(Brandenburg Consulting) commented that as fax is put into the Internet environment, it will need to handle theimpacts of this different environment. He noted that T.30 tunneling may look attractive now, but inevitably theT.30 protocol will need to be changed in some respects even in this tunneling case. He also noted that transportprotocols are a very difficult area in the Internet and that there are only a limited number of true experts in this area.

H. Silbiger (Lucent) noted the need for a contribution which points back to the ITU service requirements and servesas an alternative to the UK proposal for messaging-based fax.

It was agreed to establish ad-hoc groups to work on:• A real-time fax contribution• A US proposal on message-based fax which uses TIFF-F as a file format.

TR-29.1/97-08-51 (H. Silbiger, Lucent, contact: S. Urban, Chair TR-29) is a proposal on requirements for e-mail facsimile. It proposes that the starting point for e-mail based Internet fax should be a simple mode which usesthe TIFF-F file format which is being standardized in the IETF. It also proposes that the “normal mode” for e-mailbased fax include the capabilities identification and confirmation of receipt features that have previously beensupported in the ITU. There was discussion on which approach to take for capabilities identification. J. Rafferty(Human Communications) proposed that the content should be exchanged as a separate MIME type. Possibleformats for this information could be:

1. Application/vcard - based on IETF vcard proposals in process2. Application/faxcap - based on T.30 capabilities encapsulated using the Facsimile Tag Encoding Syntax from

Annex H (which supports encapsulation of all current T.30 frames capabilities)

It was agreed that an ad-hoc group would make minor edits to the proposal for further review in TR-29. TR-29.1/97-08-51R1 is the edited document.



PN-3364, ENHANCED BINARY FILE TRANSFER

TR-29.1/97-08-44 (J. Rafferty, Human Communications) is an Updated Annex B to T.30. The contributiontakes material that was agreed as the basis for further work at the June 1997 Costa Mesa SG 8 Rapporteur’s meeting,and integrates it with the existing Annex B within T.30. The updated draft annex includes content on BFTnegotiations within Group 3 fax and on diagnostic messages.

TR-29.1/97-08-45 (J. Rafferty, Human Communications) is a companion contribution containing proposedchanges to Rec. T.30 and its annexes required to support BFT negotiations. The main change from the materialpresented at the June 1997 Costa Mesa SG 8 Rapporteur’s meeting is to add a second proposed T.30 DIS/DTC(Digital Identification Signal/ Digital Transmitting Code) bit in support of an extended BFT NegotiationsCapability. TR-29.1 accepted the documents in principle, subject to a final editorial review by the author.

TR-29.1/97-08-39 (D. Duehren, Brooktrout) contains feedback from a BFT user (fax manufacturer, unnamed) inJapan on his needs for some advanced capabilities. The user requested that there be an ability to negotiate in advanceof transfers and he felt that the Application Reference tag in T.434 would be very useful for this purpose. It wasnoted during discussion that the requests seem consistent with the current direction of the work in T.434 and thework in process on adding BFT negotiations into Group 3 fax.

OTHER HIGHLIGHTS

M. Mathews (Hewlett Packard) presented a new HP initiative called JetSend. It provides a way for a number ofdifferent types of “information appliances” to communicate information between themselves on a peer-to-peer basis.The approach is independent of both device and device type. Methods are provided for negotiations in order to enablethe exchange of data formats. The specification can be downloaded without charge from http://www.jetsend. hp.com.M. Mathews also asked for input from fax experts on encodings and other standards related to fax and expressedinterest in working with industry groups to ensure interworking between various different types of devices.

TR-29.2 FACSIMILE DIGITAL INTERFACES

MFPA LIAISON

V. Cancio (Xerox, TR-29.2 Chair) reported on the Multi Function Peripheral Association (MFPA). There are stillopenings for the upcoming Integrated Office Conference (IOC) 97 conference; topics such as Internet fax will bediscussed. The MFPA had a presentation from HP on JetSend, but the representative did not understand technicaldetails on areas such as fax. It was noted that there appears to be considerable overlap with the SalutationConsortium work.

ECTF LIAISON

J. Rafferty (Human Communications) reported on the Enterprise Computer Telephony Forum (ECTF) work. Workis proceeding on a Revision 2 to the S.100 Application Programming Interface (API) for fax and other computertelephony resources. ECTF is also working on a fax Management Information Base (MIB), which will report onvarious conditions for fax sessions. Anyone interested in providing input should contact J. Rafferty.

PN-3626, CLASS 1.0 DIGITAL INTERFACE

TR-29.2/97-08-07 (J. Dahmen, Lanier) is the second draft of PN-3626, Class 1.0 Digital Interface, whichretrofits ITU-T T.31 for incorporation in an updated TIA-578-B. J. Dahmen suggested that it would be best toassemble a document which incorporates portions of other specifications such as V.25ter that are needed toimplement fax. B. Boykin (Datarace) argued that it is still cleanest to use references rather than bolting thedocument together and bringing the relevant specifications into the document. V. Cancio also questioned what willhappen if the underlying references change.

An ad-hoc group led by J. Dahmen reviewed this issue and the relevant specifications. The result of the ad-hoc groupwas an agreement to develop informative annexes on V.8 and V.25ter Annex A as part of TIA-578-B and toincorporate the relevant V.8 and V.25ter Annex A material by reference, rather than including duplicate text fromthese documents within the next new draft of TIA-578-B.



PN-3625, CLASS 2.1 DIGITAL INTERFACE

TR-29.2/97-08-R1 (D. Bodson, NCS) discusses the FCLASS designation change from 2.0 to 2.1 to clearlydistinguish T.32 complaint modems from the previous generation of Class 2 modems. S. Perschau (NCS) reportedon discussions with the ITU-T TSB on the correction to T.32. He believes that a delayed contribution needs to besubmitted. V. Cancio (Xerox) and S. Perschau agreed to develop this contribution for review in TR-29.

The Industry Ballot on PN-3625 to create TIA 592-A, which would retrofit T.32 into TIA 592 and include IS-134(Amendments to TIA 592 to support T.30-1993), closed August 4, 1997. There was a review of the ballotcomments which had been received by the TIA. Datarace submitted a No ballot. There was a motion introduced torescind TIA-592. The vote was 2 in favor and 6 against. There was further discussion about the comments from L.Staples (Datarace) and points were raised against the items in his comment. V. Cancio reported on updated PN-3625ballot results (received from the TIA): 9 Yes, 1 No and 3 abstentions. Resolution efforts will continue.

PN-3130, CLASS 4 DIGITAL INTERFACE

Editor B. Boykin (Datarace) discussed what the best form would be to pursue the new extensions to Class 1 that heis proposing to meet the Class 4 requirements. J. Rafferty (Human Communications) suggested that an InterimStandard may be the best way to pursue this, since this will keep it separate from the current TIA-578-B, revision ofTIA-578-A to support T.31. S. Urban (Chair TR-29, Delta Information Systems) suggested that it is probably bestto retire the old project statement (PN-3130) and then create a project statement which is updated. B. Boykinsuggested that it may be premature to call the specification Class 4 before the work is complete (he recommendedusing Class X for now). B. Boykin volunteered to prepare a project statement with a small ad-hoc group. An ad-hocgroup addressed the issues on the structure of PN-3626 (draft TIA-578-B), and agreed that the Class X work would beindependent of the TIA-578-B work.

PN-3756, MULTI-FUNCTION PERIPHERAL INTERFACE

The intent of PN-3756, Multi-Function Peripheral Interface, has been to develop improvements to the MFP interfaceprovided by interim standard IS-650. There has been no editor for this project for the past two meetings. There isstill some interest from some of the MFPA companies, but active contributors have not stepped forward. At the lastmeeting, it was decided that the project should close unless new contributions were made. However, since there doesseem to be a need for interfaces which will work with new physical layer methods such as USB and IEEE 1394, V.Cancio will make one more request for support from MFPA members.

James Rafferty, Human Communications

TR-29 PARTIAL MEETING ROSTER, AUGUST 4 – 7, 1997, SANTA ROSA, CA

Steve Urban, Delta Information Systems Chair TR-29David Duehren, Brooktrout Chair TR-29.1Vivian Cancio, Xerox Chair TR-29.2

AT&T Ajay JainBrandenburg Consult’g Dave CrockerBrooktrout Technology David DuehrenCryptek Secure Comm. David ShawData Race Robert BoykinDelta Information Sys. Stephen UrbanDialogic Steve ShawDialogic Mike SpannFlorida R&D William JacobsHuman Comm. James RaffertyLanier Worldwide Inc. Jim DahmenLucent Herman SilbigerNational Comm. Sys. Steven PerschauRockwell Glen GriffithThought Comm. Philip BogosianXerox Vivian Cancio



REPORT OF TR-30, DATA TRANSMISSION SYSTEMS & EQUIPMENT AUGUST 11 – 15, 1997, QUEBEC CITY, CANADA

TR-30.1 MODEMS

There were no new additions to the list of Intellectual Property Rights (IPR) holders. L. Brown (Motorola)encouraged all companies that had made statements to submit the appropriate letter to the ITU TelecommunicationsStandardization Board (TSB) prior to September 1997. G. Griffith (Rockwell) identified a Mr. Townshend as apotential patent holder on the V.pcm work. D. Walsh (3Com) noted that 3Com had an agreement with Mr.Townshend. J. Magill (Lucent), Chair of ITU-T WP1/16, indicated that he had spoken to Mr. Townshend. Noaction was taken by TR-30.1.

TR-30.1/97-08-066 (L. Brown, Motorola) is the report of the July, 1997 Q23/16 Rapporteur meeting in Dublin,Ireland. It was presented for information. TR-30.1/97-08-064 (L. Brown, Motorola) is the report of the July,1997 Q23/16 Rapporteur meeting in Dublin, Ireland on startup.

TR-30.1 approved the recommendation contained in the ad hoc report to allow early termination of the digitalimpairment learning segment by the analog modem. It was also agreed to allow for early termination of the Phase 3equalizer training after the analog modem receives an indication that the digital modem has trained its echo canceller.It was further agreed to focus on the structures represented by Figures 1-4 in TR-30.1/97-08-064 (same asFigures 1-4 in CSR-T 8.7, p 51).

TR-30.1/97-08-067 (V. Eyuboglu, Motorola) is the output of a small ad hoc group which studied potentialchanges to Figures 1 and 3 of TR-30.1/97-08-064 . The contribution contains a revision of Figure 3, adding anew “programmable training sequence” which reintroduces the periodic R (bar). TR-30.1 agreed to change the nameof this new sequence to “pprobe” for programmable probe.

TR-30.1/97-08-063 (L. Brown, Motorola) is the latest version of the TR-30.1 List of Agreements. It is anupdate to PCM97-81 reflecting the agreements reached in the PCM modem ad hoc meeting in Quebec City. Sometext was added for clarification. TR-30.1 agreed to accept TR-30.1/97-08-063 with the following changes:

• Only CSS (Convolutional Spectral Shaping) and MSI (Maximum Symbol Inversion) will be considered forspectral shaping and only Biquad and One Running Digital Sum will be considered for the spectral shaping filterfunctions.

• A programmable approach will be used for digital impairment learning.

TR-30.1/97-08-065 (S. Olafsson, Rockwell) proposes a structure for digital impairment probing sequences. Itprovides flexibility for manufacturers in that it allows a wide variety of sequences to be specified.

TR-30.1/97-08-069 (B. Barazesh, Lucent) proposes a “simplified” programmable Phase 4 digital impairmentprobing sequence.

TR-30.1/97-08-070 (B. O’Mahony, Intel) proposes bit assignments for the Phase 2 INFO sequences.

TR-30.1/97-08-071 (L. Brown, Motorola and B. O’Mahony, Intel) is the liaison from Q23/16 to Q4/15 onDigital Subscriber Line devices (xDSL) issues. It was modified to be a liaison from TR-30.1 to T1E1.4 (TR-30.1/97-08-072) by replacing Q23/16 with TR-30.1 and T1E1.4 in the appropriate places, and changing the upperband edge from 3700 Hz to 4000 Hz.

TR-30.1/97-08-062 (L. Brown, Motorola) is the liaison from Q4/15 (xDSL) Rapporteurs Group. It agrees tosupport “to the extent practical the use of V-series modem on voice channels associated with voice services”. Itrequests information on band edge delay, band edge attenuation and return-loss as well as other information asrequired.

V.8

TR-30.1/97-08-059 (K. Krechmer, ACTION Consulting) proposes the Determination in September 1997 of arevision to Rec. V.8, to support voice over Internet connections.

In the presentation (not in the text of the contribution), TR-30 support was sought for the concepts that 1) Ashortened IAT (Internet Access Time) is desirable, 2) Paralleling modem startup and the exchange of security/accounting information is desirable, and 3) Call Indicator (CI) is a desirable vehicle for conveyingsecurity/accounting information.



TR-30.1/97-08-060 (K. Krechmer, ACTION Consulting) provides draft text for a V.8ia Recommendation.

Possible security concerns were raised with the use of CI (V.21) to transmit sensitive information as it is essentiallytransmitting in the clear. It was also pointed out that this may delay answer tone (ANS) transmission and thereforelengthen the startup required to assure accurate reception of CI. No action was taken because a quorum did not existduring discussion.

TR-30.1/97-08-068 (C. Hansen, Intel), the draft of V.8 Issue 2, was briefly reviewed. No TR-30.1 action wastaken because a quorum did not exist.

Dick Brandt, dB Consulting

TR-30.2 D IGITAL INTERFACES INCLUDING DTE-DCE PROTOCOLS

REPORT OF Q7/16, DCE/DCE PROTOCOLS

TR-30.2/97-08-019 (F. Lucas, General DataComm) contains a brief report of the Q7/16 Rapporteurs meeting inDublin, Ireland, July 1997. Following the Dublin meeting, a first draft for the revision of the Supplement toV.25ter, Serial Asynchronous Automatic Dialing and Control, had been generated, TR-30.2/ 97-08-020 (F.Lucas, General DataComm). This draft was distributed to TR-30.2 for consideration before the September 1997Q7/16 Rapporteurs meeting. It includes the addition of the GSM related commands provided at the July 11, 1997Rapporteurs meeting. In addition it includes editorial corrections discussed at that meeting and the approved additionsto V.25ter included in COM-16-15 and TD-18(PLEN) from the March 1997 SG 16 meeting. It was observedthat the commands contained in ITU-T Recommendations V.80, V.25ter Annex A and V.25ter Annex B should alsobe included in the Supplement.

STANDARDS FOR REVIEW

At the June 1997 meeting of TR-30.2, a number of TIA Standards, Bulletins and Interim Standards requiringattention were reviewed. As a result of this review a number of new projects have been opened. The followingANSI Project Initiation Notification System (PINS) forms and TIA Project forms were distributed to the members:

PN-4091, Reaffirmation of ANSI/EIA/TIA-530-A, High Speed 25-Position Interface for DTE and DCE.ANSI PINS: TR-30.2/97-08-022TIA Project form: TR-30.2/97-08-023

PN-4092, Reaffirmation of ANSI/EIA/TIA-561, Simple 8-Position Non-Synchronous Interface between DTE andDCE Employing Serial Binary Data InterchangeANSI PINS: TR-30.2/97-08-024TIA Project form: TR-30.2/97-08-025

PN-4093, Reaffirmation of ANSI/EIA/TIA-562 Electrical Characteristics for an Unbalanced Digital InterfaceANSI PINS: TR-30.2/97-08-026TIA Project form: TR-30.2/97-08-027

PN-4094, Reaffirmation of ANSI/EIA/TIA-574, 9-Position Non-Synchronous Interface between DTE and DCEEmploying Serial Binary Data InterchangeANSI PINS: TR-30.2/97-08-028TIA Project form: TR-30.2/97-08-029

PN-4095, Revision of ANSI/TIA/EIA-602, Serial Asynchronous Automatic Dialing and ControlANSI PINS: TR-30.2/97-08-030TIA Project form: TR-30.2/97-08-031

Additional Standards and Bulletins had been received from TIA, which TR-30.2 reviewed. The following will berescinded as they are long out of date and no longer serve a purpose:• EIA-363 (Standard for Specifying Signal Quality of Transmitting and Receiving Data Processing Terminal

Equipment Using Serial Data Transmission at the Interface with Non-Synchronous DCE)• EIA-410 (Standard for the Electrical Characteristics of Class A Closure Interchange Circuits)• IEB5 (Tutorial Paper on the Signal Quality at the Digital Interface)• IEB12 (Application Notes on the Interconnection Between EIA-449 and EIA 232 Interface Circuits)

Regarding existing TIA Standards, TR-30.2 decided to open a project to revise TIA/EIA-615 (Serial AsynchronousAutomatic Dialing and Control - Extended Command Syntax) to make it a reference document to ITU-T



Recommendation V.25ter. The information contained in TIA/EIA-617 (In-Band DCE Control for AsynchronousDTE-DCE Interfaces) has been included in ITU-T Recommendation V.80. It was decided to also open a project torevise TIA/EIA-617 as a reference to V.80.

PN-3855, H IGH SPEED TYPE 232 I NTERFACE

The industry ballot on this new interface (maximum rate 512 Kbit/s) closed prior to the TR-30.2 meeting with nonegative ballots or comments received. With the approval of the standard, it will proceed to TIA for publicationasTIA/EIA-726.

PN-3498, REVISION OF EIA-485

The revised text for EIA-485, Standard for Electrical Characteristics of Generators and Receivers for use in BalancedDigital Multipoint Systems, has been distributed as an ANSI/Industry ballot with a closing date of September 22,1997. Comments received on this ballot will be considered at the October meeting of TR-30.2.

TSB-54, DTE/DCE INTERFACE SELECTION GUIDE

TR-30.2/97-08-018 (F. Lucas, General DataComm) is the first draft of the revision of TSB-54. Thecontribution was distributed for review. Editorial changes are required, as well as the inclusion of references toTIA/EIA-726. It is expected that a committee ballot of TSB-54-A will be authorized at the October TR-30.2meeting.

TIA/EIA 695, CONTROL OF VOICE FUNCTIONS

TR-30.2/97-08-021 (J. Decuir, Microsoft) is a revision of a Microsoft contribution Q07-97-005 at the DublinQ7/16 Rapporteurs meeting and at the June TR-30.2 meeting. Additions and revisions to the draft ITU-T V.voiceRecommendation were recommended, some of which had been accepted in Dublin; the contribution provides additioninformation for a change to the Stuttered Dial Tone reporting. A second paper (TR-30.2/97-08-033) provides textchanges recommended to V.voice for the inclusion of commands in support of duplex voice operation. Theinformation contained in these papers will be presented to the September Q.7/16 Rapporteurs meeting.

Fred Lucas, General DataComm

TR-30.3 DATA COMMUNICATIONS EQUIPMENT EVALUATION AND NETWORK INTERFACES

TR-30.3 Chair J. Douglass (Oak Technology) asked whether there was knowledge of patents, the use of which maybe essential to the standards being considered. There were no responses. TR-30.3/97-06-044 (J. Douglass, TR-30.3 Chair) discusses the new ANSI Patent Policy.

L. Brown (Motorola) opened up folders on the FTP site for TR-30.3 projects. TR-30 is creating an electronicdocumentation handling policy. Documents should be posted on the FTP site on the Wednesday before the meeting.If documents are not placed on the FTP site, an electronic copy must be brought to the meeting. Hard copies mustalso be brought to the meeting. Documents that are not posted on the FTP site before the meeting must be postedafter the meeting.

TR-30.3/97-08-051 (J. Douglass, TR-30.3 Chair), a list of open projects for TR-30/TR-30.3, was submitted byTIA. After reviewing the project list in detail the following was decided:

Project Project Title StatusPN-1372 Interface Standard for Private Leased Line ClosedPN-3251 Cellular Network Transmission Model for Evaluating Modem Performance OpenPN-3435 Study Affects of ADPCM on Modem Performance ClosedPN-3459 Make TSB-37-A (Telephone Network Transmission Model for Evaluating

Modem Performance) into a standard -- TIA/EIA-37-BOpen

PN-3507 Test Procedures for Evaluation of Cellular Modem OpenPN-3508 General Test Procedures for Modem Evaluation ClosedPN-3509 Make TSB-38 (Test Procedure for Evaluation of 2 Wire 4 kHz Voiceband

Duplex Modems) into a Standard -- TIA/EIA-38-AOpen

PN-3681 Test Procedures for Evaluating Low Bit Rate Multi-Media Modems ClosedPN-3856 Test Procedures for Evaluating PCM Modem Performance Open



PN-3857 Telephone Network Transmission Model for Evaluating PCM ModemPerformance

Open

EIA/TIA-496-A

Interface Between DCE and the PSTN Open new projectto revise

TSB-18-A Mechanical/Functional Characteristics of the Interface Between DCEs andVoiceband Analog Channels

Rescind

R. Perez (Bellcore) will work with TR-41.9 to review EIA/TIA-496-A (Interface Between DCE and the PSTN). S.Hoyler (TIA) will officially send EIA/TIA-496-A to TR-41.9 Chair A. Wride and request their review.

J. Douglass (Oak Technology) reported that he had received a call from Ziff Davis lab requesting statisticalinformation on the impairment combinations given in network model for testing PCM modems, and replied to themas follows:

• The document is only a draft and has not been released. Concern was expressed about Ziff Davis having theunreleased committee document.

• TR-30.3 has only completed the first of a three step process to define the impairment combinations. There weremany significant impairments (i.e., Digital Pad, frequency dependent NLD ) that are not included in the presentmodel. Test results derived from the present model will not accurately reflect actual performance on the real lines,since the document is not complete.

• TR-30.3 and TIA should not be referenced in association with the test results or the published article.

A TIA legal person may send a letter to Ziff Davis expressing the concerns of TR-30.3. However, TR-30.3 wouldprefer to work with Ziff Davis concerning these issues.

PN-3459, REVISING TSB-37A (T ELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATINGMODEM PERFORMANCE)

Some of the work from the previous meeting is duplicated here as the Chairman had not been able to attend the Junemeeting due to illness. TR-30.3/97-06-042© (J. Douglass, TR-30.3 Chair) is the ballot copy of PN-3459 (to beTSB-37-B) “Telephone Network Transmission Model for Evaluating Modem Performance.” TR-30.3/97-06-043(J. Douglass, TR-30.3 Chair) contains the 16 committee letter ballot responses for PN-3459. TR-30.3/97-06-045 (S. Satchell, Motorola ISG) discusses their “No” vote on current draft of PN-3459 noting that they are onlyconcerned with the significant number of corrections required.. TAS and Consultronics also voted no. TR-30.3/97-06-045 includes a new draft of PN-3459 with primarily editorial changes.

TR-30.3/97-06-046 (R. Perez, Bellcore) contains data from Bellcore’s SR-NWT-002027, Digital Access Survey,February 1993. This data from a DLC loop plant survey in the period 1986-1988 indicates that the addition ofDigital Loop Carriers into TSB-37B does not require any changes in the test loop configurations and combinations.TR-30.3/97-08-049 (F. Lucas, GDC) is an e-mail noting to the Chairman the concerns raised in the Junemeeting on the technical changes to PN-3459 without committee agreement. TR-30.3/97-08-050 (L. Smith,recently retired) is an e-mail noting disappointment that PN-3459 (TSB-37-B) was not approved, his concerns aboutTSB-37-A and offering to help complete PN-3459 (TSB-37-B).

TAS’ primary concern was the existence of technical changes between the ballot and the most recent draft beforeballot.

Motorola’s primary concerns were the large number of typographical errors and the lack of rationale for the levels ofnetwork impairments.

H. Hagen (Lucent) said that he is able to get Com 102 (ECI codec implementation) and Com 101 (Mitsubishi codecimplementation) documents. This information should be included in an appendix. These codecs need to be includedin the impairment combinations, because they are very common on international calls. However there is IPRassociated with these documents. S. Hoyler (TIA) will let TR-30.3 know how to handle the IPR situation.

H. Hagen (Lucent), R. Perez (Bellcore), S. Satchell (Motorola ISG) will create a rational for the ImpairmentCombinations in TIA/EIA-37-B. This information will be included in an appendix. H. Hagen (Lucent) will headthis effort.

During the ad hoc meeting, TR-30.3/97-06-045 (S. Satchell, Motorola) was reviewed and revised using the letterballot responses in TR-30.3/97-06-043 . S. Satchell (Motorola ISG) will incorporate these changes into the newballot, and post it on the FTP site. TR-30.3 members should review the ballot and submit comments by email by



August 29, 1997. S. Satchell will incorporate the recommended changes and send the final version to TIA forANSI ballot. Any ballot comments received will be discussed at the October 1997 meeting. The document can bereleased for publication if no negative votes are received between the October 1997 meeting and the close of theballot.

PN-3508, REVISION OF TSB-38

S. Satchell (Motorola) will modify TSB-38 to match balloted TIA/EIA-37-B. S. Satchell (Motorola) and W.Henderson (Henderson Communications Laboratories) will add an Annex F. This document will be released forballot to become TIA/EIA-38-A at the same time as TIA/EIA-37-B is released for ballot.

J.P. Houdard (TI) and M. Pellegrini (TAS) will run tests using the current network model.

PN-3251/PN-3507, C ELLULAR MODEM TESTING

G. Smith (BellSouth Cellular) said that the Cellular ad hoc committee will bring a contribution to the next meeting.W. Henderson (Henderson Labs) will lead this effort.

PN-3857, TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING PCM MODEMSPERFORMANCE

TR-30.3/97-04-039 (J. Douglass, TR-30.3 Chair) is a liaison to TR-30.1 ad hoc concerning PCM modems.TR-30.3/97-06-047 (P. Caldera, Siemens AG) discusses gain and total distortion of line cards. TR-30.3/97-06-048 (R. Hill, Sage Instruments) discusses use of the 23 Tone Test to Qualify Circuits for PCM Modems. TR-30.3/97-08-052 (J. Houdard, Texas Instruments) discusses harmonic distortion generated by the line card in thedownstream direction. In the case of connections between the ISP site and the analog modem, harmonic distortion isgenerated by the line card only. Consequently harmonic distortion is less severe than in cases A and B (severe andtypical channel conditions, with impairment combinations defined in TR-30.3/97-03-023). For this reasonadditional impairment combinations (cases C and D) should be considered in the network model. TR-30.3/97-08-053 (J. Houdard, Texas Instruments) contains network model diagrams and impairment combinations tables forevaluation of PCM modems (European Network Model). It notes that the European network model impairmentcombinations, while similar to those defined for the US, do not incorporate digital loss. T-pads and R-pads whereused in the European network are analog to maintain end-to-end bit integrity.

After reviewing the contributions the following homework assignments and comments were made:

• J. Houdard (Texas Instruments will run PCM modem tests using document TR-30.3/97-08-052 (J. Houdard,Texas Instruments).

• R. Perez (Bellcore) will measure Inter Modulation Distortion (IMD) characteristics.• S. Satchell (Motorola) will add attenuation distortion and the digital pad defined by Hayes to the line impairments

defined in TR-30.3/97-04-039AH (J. Douglass, TR-30.3 Chair).

Jack Douglass, Oak Technologies

Communications Standards Review – Telecommunicationsregularly covers the following committee meetings:

TIA TR-29TR-30TR-41

ITU-T SG 8SG 15 WP1SG 16 (formerly SG 14, with parts of SG 8 and SG15 relating to multimedia)

ETSI ATADTAMTATC SPTC STQTIPHON



TR-30 MEETING ROSTER, AUGUST 11 - 15, 1997, QUEBEC CITY, QUEBEC, CANADA

Dick Brandt, dB Consulting Chair TR-30Les Brown, Motorola ISG Chair TR-30.1Fred Lucas, General DataComm Chair TR-30.2Jack Douglass, Oak Technologies Chair TR-30.3

3Com Vladimir Parizhsky3 Com Wayne Park3Com Jim Renkel3Com Dale Walsh3Com Richard WilliamsACTION Consulting Ken KrechmerAdtran Steven BlackwellAltocom Haixiang LiangAMP Ben BennettAnalog Devices Rao NuthalapatiAscend Sandeep AgarwardBay Networks Dannielle HusingaBay Networks Qingli LiuBellcore Ricardo PerezBellSouth Cellular Gary SmithCirrus Logic Wesley SmithCisco Systems Tom MartinCisco Systems Kevin RileyCompaq Computers Luis LucianiConsultronics Louis ChenierCSR Elaine BaskinDavicom Wen ChenDiamond Multimedia Dan MooreEquator Karl ZhaoESS Technology Ping DongFloreat Earl GibsonGao Research Alan MarionGDC Yuri GoldsteinGDC Fred LucasHayes Bruce AdamsHayes Dave RifeIBM Youssef AbdelilahIBM Ali SadriIntel Barry O’Mahony

Lake Datacomms Michael Mc LaughlinLucent Bahman BarazeshLucent Edward SchulzLucent Horace HagenLucent Kent MinaMediagate Doron HerzlichMicrosoft Joe DecuirMotorola Dick BrandtMotorola Les BrownMotorola Vedat EyubogluMotorola Mickey RushingMotorola Stephen SatchellMultitech R.S. GopalanOak Technologies Jack DouglassPCTel Gary AnwylRed Wing Jin-Nan LiawRockwell Mike GauerRockwell Glen GriffithRockwell Joe HoangRockwell Sverrir OlafssonRockwell Zhou ZhenSamsung John StockmanSiemens Thomas HenkelSiemens Neal KingSmart Link Leor BrenmanTAS Michael PellegriniTelindus Paul AertsTexas Instruments E. AgisTexas Instruments D. SimpsonTexas Instruments Jean-Pierre HoudardTIA Susan HoylerVoCal Technolgies Victor DemjanenkoZyXel Hsieh Chi-Ching

COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:

Communications Standards Summary (ISSN 1075-5721), a quarterly publication reporting on all activeprojects and recently completed standards of the TIA’s (Telecommunications Industry Association’s) TR-committees. Authorized by TIA.

For more details: Visit http://www.csrstds.com. To receive a complimentary issue ofeither of CSR’s technical journals, please contact Elaine Baskin, tel +1 650 856-9018,fax +1 650 856-6591, e-mail: [email protected]



REPORT OF TR-30.1 PCM MODEM AD HOC MEETINGAUGUST 12 – 13, 1997, QUEBEC CITY, CANADA

The primary goal of this meeting was to reach consensus on the data mode aspects of V.pcm - Issue 1. This did notoccur.

The Rapporteur for Q23/16 (L. Brown, Motorola ISG) presented for information PCM97-82 , the draft report of theQ23/16 Rapporteur meeting in Dublin, Ireland, July 7-9, 1997. He then presented for information PCM97-83 , thereport of the one day Q23/16 ad hoc meeting on startup that immediately followed the Rapporteur meeting inDublin.

PCM97-89 , an open letter to the standards committee from an attorney representing VoCAL Technologies, wasdeemed inappropriate for discussion by the ad hoc committee and was therefore not presented. The letter basicallyasks why VoCAL proposals have not received more serious consideration, and suggests that reports from thestandards meeting should document the rationale behind the decisions made. S. Hoyler TIA agreed to take a copy ofthe letter to TIA legal for possible response.

The Chair (B. O’Mahony, Intel) asked if there were any companies who wished to declare Intellectual Property (IP)pertaining to PCM modems, in addition to those who had previously made such a declaration. There were noadditional declarations. However, later in the meeting, Rockwell and 3Com representatives reported that a Mr. B.Townshend, who is neither a member of TIA nor ITU-T, is believed to claim IP pertaining to PCM modems. It wasreported that he has been in communication with the WP1/16 Chair and is expected to submit an IP statement to theITU-T prior to the September WP1/16 meeting. The Rapporteur asked that all of those who have declared they ownIP submit patent statements to the ITU-T before the September 1997 SG 16 WP1 meeting.

INCOMING LIAISON REPORTS

There were no official incoming liaison statements. However, the ad hoc committee did review PCM97-80R1 ,the liaison from Q23/16 to Q4/15 concerning aspects of xDSL Specifications which may affect V-series Modems,and agreed to ask TR-30.1 to send a similar liaison to ANSI T1E1.4.

LIST OF AGREEMENTS AND BASELINE TEXT

The Rapporteur for Q23/16 (L. Brown, Motorola ISG) presented PCM97-81R1 , the latest list of agreements forthe V.pcm Recommendations from the Q23/16 Rapporteur meeting, Dublin, Ireland, July 9-11, 1997. This wasapproved.

R. Williams (V.pcm editor) briefly presented PCM97-84 , the latest baseline text for V.pcm - Issue 1. This wasalso approved.

DATA MODE: SPECTRAL SHAPING

PCM97-93 (V. Eyuboglu, Motorola ISG) is a comparison between the Convolutional Spectral Shaping (CSS) andSequence Determined Redundancy (SDR) spectral shaping techniques. It argues that CSS has important practicaladvantages over SDR.

STARTUP PROCEDURES

PCM97-85 (A. Alvarez, G. Ungerboeck, and E. Hulsmans, presented by Y. Abdelilah, IBM) proposes a top-downapproach for identifying modem functionality. It suggests a possible manner to include improvements.

PCM97-87 (J. Renkel, 3Com) proposes a mechanism for the determination of the communications mode to beused by two V.pcm modems when connected via the PSTN, where each modem may support either the V.pcm -Issue 1 communications mode, the V.pcm all digital communications mode, or both. Specifically, it proposes anew category octet in V.8 for use by PCM modems, and what action to take based on the bits exchanged duringCM/JM.

PCM97-88 (B. Adams, Hayes) proposes that a mechanism be included in the startup procedure of V.pcm to allowthe upstream (V.34) modem to reduce its transmit power after probing if it decides that the downstream data ratecould be increased, even if doing so degrades the upstream data rate. Specifically, it proposes to use bits in INFO0and INFO1 to negotiate this feature.



PCM97-90 (E. Freed, V. Demjanenko and F. Hirzel, VoCAL Technologies) describes a technique for training aPCM modem equalizer for spectrally shaped transmit signals using an arbitrarily shaped training signal. It also dis-cusses a criteria for choosing an optimal transmit spectral shape for a given channel and noise spectra. PCM97-91(V. Demjanenko and F. Hirzel, VoCAL Technologies) describes various Phase 2 and Phase 3 techniques to aid indiscovering the characteristics of the downstream channel, including a proposal to specify Phase 2 signals in thecodeword domain rather than in the analog domain.

PCM97-92 (M. McLaughlin, Lake Datacomms) proposes an extension to the digital impairment learningdescriptor described in PCM97-71 .

PCM97-94 (V. Eyuboglu, Motorola) proposes an alternative descriptor also based on earlier contributions.

DISCUSSION AND AGREEMENTS

There was no consensus on the spectral shaping scheme. A straw poll was taken to gauge the level of support foreach proposal with the following result:

CSS: 8 TIA membersMaximum symbol inversion: 6 TIA membersSDR: 1 non-TIA memberFrame inversion: 2 TIA members

There was no consensus on the spectral shaping filter. A straw poll was taken to gauge the level of support for eachproposal with the following result:

Biquad: 8 TIA membersOne RDS: 7 TIA membersHigh order filter: 1 non-TIA member

During the discussions the following agreements pertaining to V.pcm - Issue 1 were reached:

1. Mapping/framing: agreed that the only mapping schemes that will be considered are those that had beenproposed no later than the July 1997 Rapporteur meeting, specifically the following two: shell mapping andmodulus conversion.

2. Spectral shaping: agreed that the only spectral shaping schemes that will be considered are those that had beenproposed no later than the July 1997 Rapporteur meeting, specifically the following four: ConvolutionalSpectral Shaping (CSS), maximum symbol inversion, Sequence Dependent Redundancy (SDR), and frameinversion.

3. Startup Phase 1: agreed to request a new category octet in V.8 for PCM modem use, with bit 5 = ONE denotingV.pcm - Issue 1 client availability, bit 6 = ONE denoting V.pcm - Issue 1 server availability (However, betterterms than client and server need to be found), with bit 7 being reserved for V.pcm - Issue 2.

4. Startup Phase 1: agreed to request that, in the first extension octet to this new category octet in V.8, bit 0 =ONE denote V.pcm - Issue 1 all-digital availability, once a startup procedure for this functionality has beendefined in V.pcm - Issue 1.

5. Startup Phase 1: agreed to request that the action to take after the exchange of the aforementioned new categorybits be as proposed in the second table in PCM97-87 .

6. Startup Phase 1: agreed to request that bit 5 in modn0 of V.8, previously assigned to indicate V.pcmavailability, be released.

7. Startup Phase 1: agreed that bit 7 in gstn0 of V.8 indicating digital vs. analog access should be kept.8. Startup Phase 2: agreed that the Phase 2 structure and frequencies would be flipped together when required (also

deleted the Rapporteur’s note).9. Startup Phase 2: provisionally agreed to keep probing signals as they are in V.34 (no added frequencies, no added

probing sequences). If there are no papers at the September 1997 Q23/16 Rapporteur meeting that demonstratean improvement in the ability to determine how to proceed into Phase 3, this becomes an agreement (no longerprovisional).

10. Startup Phase 2: Agreed that the analog modem will make the determination on how to proceed into Phase 3(also deleted the Rapporteur’s note).

11. Startup Phase 3: agreed that the analog PCM modem will transmit the same sequence of signals during Phase 3as current V.34 modems, specifically: S, S-bar, MD, S, S-bar, PP, TRN (training), J. The information content



of J will likely differ. The transmission of J is interruptable by the digital modem by the same mechanism asin V.34 (S, S-bar).

12. Startup Phase 3: agreed that the digital modem transmit signals (including silence, if present) will be kept to amultiple of 6 symbols in length to the extent practical.

13. Startup Phase 3: agreed that the Phase 3 equalizer training segment transmitted by the digital modem will useonly a 2-point (single magnitude) constellation.

14. Startup Phase 3: agreed that the Phase 3 equalizer training segment transmitted by the digital modem will nothave spectral shaping applied to it.

The following agreement pertaining to V.pcm - Issue 2 was also reached:

1. Agreed that the support of V.pcm - Issue 2 will be indicated in Phase 1 (V.8).

The Rapporteur prepared PCM97-95 , the latest list of agreements incorporating the above. This was presented atthe TR-30.1 meeting the following day.

Les Brown, Motorola ISG

1998 STANDARDS COMMITTEE MEETING SCHEDULESAS OF SEPTEMBER 29, 1997Subject to change without notice

Committee Date(s) LocationETSI TIPHON Jan 5 - 8 Sophia Antipolis, FranceSG 16 Jan 26 - Feb 6 Geneva, SwitzerlandETSI STQ Jan 28 - 30 ---ETSI TIPHON Feb San Jose, CATR-29 Feb 9 - 12 Newport Beach, CASG 15 Feb 9 - 20 Geneva, SwitzerlandTR-41 Feb 23 - 27 AlbuquerqueETSI MTA Mar 2 - 6 Berlin or Sophia AntipolisTR-30 Mar 9 - 13 Ft. Lauderdale, FLETSI TIPHON Apr Munich, GermanyTR-30 Apr 27 - May 1 ---TR-41 May 11 - 15 Washington DCETSI TIPHON Jun Helsinki, FinlandSG 8 Jun 9 - 18 Geneva, SwitzerlandTR-30 Jun 15 - 19 Dallas or Houston, TXETSI MTA Jun 29 - Jul 3 Munich, GermanyETSI TIPHON Jul ---TR-30 Aug 10 - 14 Quebec City, QueTR-41 Aug 17 - 21 Calgary, AlbertaETSI TIPHON Sep Portland, ORSG 16 Sep 14 - 25 Geneva, SwitzerlandSG 15 Oct 12 - 23 Geneva, SwitzerlandTR-30 Nov 9 - 13 San Antonio, TXTR-41 Nov 16 - 20 Palm Springs, CA



REPORT OF TR-41, USER PREMISES TELECOM EQUIPMENT AUGUST 18 – 22, 1997, QUEBEC CITY, QUEBEC, CANADA

TR-41.1, MULTI-LINE COMMUNICATION TERMINAL SYSTEMS

T1E1 LIAISON

TR-41.1/97-08-026 (C. Sacco, Bellcore) contains the T1E1 May 1997 meeting report. T1E1.1 is working on“Network to Customer Installation Interfaces -- Analog Voicegrade Switched Access Lines with Calling NumberDelivery, Calling Name Delivery, or Visual Message Waiting Indication Features;” a document coveringsupplementary services using network-originated asynchronous data messages.

TIA-464-B, PBX S WITCHING EQUIPMENT

Living List For Future Revis ion

TR-41.1/97-08-021 (R. Frank, Siemens Business Communications Systems) is the living list update for the TIA-464-B, the standard on Private Branch Exchange (PBX). There were no major changes to the living list. TR-41.1/97-08-029 (T. Tung, Siemens Business Communication Systems) notes a typographical error in TIA-464-Bsection 4.1.2.1.2.

Line-Side Interface Requirements

TR-41.1/97-08-028 (P. Melton, Cortelco) is a draft of the Basic Rate Interface (BRI) Terminal CapabilitiesQuestionnaire from the North American ISDN User’s Forum (NIUF) Private Switching Group. This questionnaire,to be directed at manufacturers of BRI terminal equipment, is part of an initiative on connection of BRI terminals toMulti-Line Telecommunications Systems (MLTS i.e., PBX), particularly to ensure PBX interoperability with BRIterminal products. The information from this questionnaire will be made available to PBX suppliers. It is alsoproposed to hold a joint meeting of PBX and BRI terminal suppliers to address these issues.

TR-41.1/97-08-023 (J. Needham, Mitel and P. Weismantel, NEC) proposes the scope and project description fora Technical Service Bulletin (TSB) to define the BRI line side interface of MLTS. The objective is to study thecurrent implementation (Bellcore National ISDN 97) with the possible goal of a standard, so that BRI terminalequipment served by MLTS will operate the same as that on a PSTN or Centrex arrangement. The TR-41.1 chairwill initiate the required project authorization and Project Initiation Notification System (PINS).

TIA/ETSI STANDARDS HARMONIZATION

TR-41.1/97-07-020 is the final ETSI draft on private network transmission planning.

SURVEY ON USER QSIG PERSPECTIVE

TR-41.1/97-08-025 (D. Lockard, TelCon Associates) is an informal survey of eight users’ perspectives onrequirements specified by the ITU Q series recommendations (QSIG) service and features. Although it wasrecognized that the survey does not constitute a statistically valid sampling, the results do reflect certain trends. Oneis that some QSIG services are judged highly important, including direct dialing in, path replacement, identificationservices, and call handling services such as forward, transfer, completion, call waiting. The survey also showed thatthere is a range of the degree of users’ QSIG knowledge and understanding of benefits. The survey was accepted asuseful information to manufacturers for structuring QSIG offerings. (The survey was also presented in TR-41.10.)

E911

TR-41.1.9, the Enhanced 911 (E911) working group, did not meet. However, T1S1 has conducted E911 work onthe ISDN solution for E911. TR-41.1/97-08-022 (R. Frank, Siemens, on behalf of Lucent and Bellcore)discusses ISDN signaling of caller location between a Private Branch Exchange (PBX) or a wireless telephone andthe Public Safety Answering Point (PSAP). The types of information that need to be sent include wireless userlocation information as well as a flashing indication (an equivalent to the analog MF indication sent to a PSAPtoday). TR-41.1/97-08-022 suggests contributing to the ITU-T to define the new protocol needed for thesecapabilities.

TR-41.1/97-08-027 (J. Bond-Harris, Lucent) is proposed text for the supplement to standard T1.607 (DSS1-Layer 3 Signaling Specification) in support of E911 service. TR-41.1/97-08-024 (D. Vander Meiden, Siemens)comments on the T1.607 supplement that revises and enhances DSS1 basic call control to add support forEmergency Service calls. No action was indicated in response to these documents; members were urged to reviewthem in preparation for a re-convening of TR-41.1.9 (MLTS Support for E911 Calling) in November, 1997.



The TIA standard on E911, TIA-689, is now under Technical Standards Subcommittee (TSSC) review; presumably itwill be ready for publication following this review.

TR-41.1.1 MLTS TRANSMISSION

PRIVATE NETWORK TRANSMISSION PLANNING GUIDE (WITH ETSI)

Work proceeded on the Private Network Planning Guide (update of TIA TSB-32) and the harmonization of this guidewith the ETSI update of their document, Overall Transmission Plan Aspects for Telephony in a Private Network.The TR-41.1.1 discussion was preparation for the September 1997 joint TIA TR-41.1/ ETSI CN7 meeting. Thejoint meeting’s main purpose will be agreement on harmonization of private network transmission guidelines, andon the future of TIA/ETSI cooperation as CN7 is disbanded and the work transferred to a new ETSI group on SpeechTransmission Quality (STQ). Representatives from Nortel, Lucent, Siemens, and TelCon Associates will representTIA at the joint meeting.

Regarding the document harmonization issue, two options were discussed jointly by T. Tung (Siemens) and J.Schick (Nortel) as a overhead presentation (not a formal contribution).

• Option A is two separate, parallel but independent documents - which was the original orientation of the project -with common tutorial material, but with network parameters, calculation details, and examples described inregion-specific terms. The ETSI document would be published in its present form (with minor corrections),while the TIA document might give more emphasis to planning details in the body of the document. Theadvantages of this option are that publication dates need not be coordinated, North American specific terminologycould be used, and analog interconnection scenarios would be included.

• Option B envisions a single, global private network transmission document, largely based on the ETSIdocument, but with terminology and parameter descriptions expanded to accommodate North American as well asEuropean aspects. For this option, examples would be presented in region-specific annexes. The advantages ofthis option are a single globally applicable document for planners and designers of multinational privatenetworks, a more comprehensive document, and reduced writing effort.

After considerable discussion, the majority of TR-41.1.1 was in favor of Option B. At the joint meeting, bothoptions will be presented with the TIA recommendation of Option B, should ETSI concur.

TR-41.1.1/97-08-019 (J. Schick, Nortel) contains comments on the ETSI Technical Report (ETR) on telephonyin a private network. Based on the recommendation of Option B (above), which would result in a single globaldocument, the comments will be restructured prior to presentation to ETSI at the joint meeting, particularly toaddress North American concerns.

TR-41.1.1/97-08-021 (J. Schick, K. Cheung and R. Britt, Nortel) describes the application of the ETSITransmission Model (E-model) to a number of selected private network connection scenarios, as specific update ofthe former TSB-32 material. The E-model is a transmission planning tool relating impairments to user perceptionof QoS. This contribution is applicable to either of the above options; if Option B is agreed, it will become anAnnex for North American-specific connections. Because the contribution is quite detailed, TR-41.1.1 deemed itappropriate to allow for a review period until the next meeting before approval. At the joint TIA/ETSI meeting, thework will be introduced as follows: “This document represents a contribution by a member of TIA in response to ahomework assignment to demonstrate a practical application of the E-model to North American connections. It iscurrently under study by the TIA [TR-41.1.1] membership and will be revised after further discussion and analysis.Its intent here is to show the direction of the work.”

With respect to progress in the development of the ETSI E-model tool, TR-41.1.1/97-08-020 (e-mail from S.Moeller, Germany) discusses the availability of the latest version (Version 18) of the E-model reference softwareavailable to ITU-T TIES users.

T1A1.7 UPDATE OF T1.508

TR-41.1.1 met via teleconference on July 23, 1997 to formulate a liaison to Committee T1A1.7 with comments ontheir proposed update of standard T1508, Loss Plan for Evolving Digital Networks. TR-41.1.1/97-08-017 (J.Schick, Nortel) contains the record of that teleconference and the resulting liaison letter from the TR-41.1 chair tothe T1.508 update editor in T1A1.7. Key items addressed in the comments include definition and loss treatment ofdigital access lines serving MLTS, adoption of ITU loudness terms, relaxation of strict delay allocation for Customer



Premise Equipment (CPE) echo control, and a long-term strategy of moving from impairment allocation to completeend-to-end transmission planning.

TR-41.1.1/97-08-018 (A. Crossman, T1A1.7) contains the response of T1A1.7 from their August 1997meeting, in which they indicate that there will be a clarification on digital access line connection and loss treatment.Loudness characteristics will be defined in ITU terms (partly due to T1.508 making reference to TIA-579, thestandard on digital telephones; the update of TIA-579 will adopt ITU loudness terms). However, there was reluctanceexpressed in the relaxation of impairment allocations; e.g., current guidelines for the delay limit beyond whichcustomer equipment should provide echo control will remain. TIA is invited to a T1.508 editing teleconference onSeptember 18, 1997 in which some of these issues may be discussed.

TR-41.1.1/97-08-016 (J. Zebarth, Stentor Resource Center) describes one concern raised in conjunction with theT1.508 update: the increasing occurrence of concatenating digital access lines via a PBX or private network, e.g., forDirect Inward Dialing (DID) call forwarding or for Direct Inward Service Access (DISA). Under some circumstances,such concatenated connections could have too little loss for echo control or, in some cases, exceed the tail end delaycapability of echo cancelers. The T1A1.7 position is that, on such calls, the PBX or private network has theresponsibility for assuring control of the echo impairment; however, no clear solution has been proposed.

John Schick, Nortel

TR-41.2 CONFORMITY ASSESSMENT

FEEDBACK FROM MRA AND TECHNICAL REGULATORY REFORM TASK FORCES

Since the last TR-41.2 meeting, the USA and the EU have signed a Mutual Recognition Agreement (MRA). Theactual implementation is in the early stages. TR-41.2/97-08-14 , Agreed minutes USA and EC delegations, TR-41.2/97-08-15 , Agreed minutes Canadian and EC delegations, and TR-41.2/97-08-16 , EC proposal, representthe basic wording going forward. The MRA will not become official until signed by the Presidents of the USA andthe EU. This will not be done until translation is complete. It is expected by the end of the first quarter of 1998.

The transitional phases will begin with a confidence building period for the mutual recognition of test resultsfollowed by a confidence building period for the mutual recognition of product certification. The agreement will notbecome effective until there are conformity assessment bodies in place. Transition to full certification will not gointo effect until all sectors in the agreement are ready.

The hottest area of discussion is that of Conformity Assessment Bodies.

FCC ET DOCKET 97-74 (S TREAMLINING AUTHORIZATION PROCESS FOR RADIO FREQUENCYEQUIPMENT)

TR-41.2/97-08-18 (P. Adornato, Nortel) contains comments on FCC ET (Engineering & Technology) DocketNo. 97-94 generated during the May 22, 1997 ad-hoc meeting of TR-41.2 and TR-41.9. TR-41.2/97-08-019(FCC) is the TIA Technical Regulatory Reform Task Force (TR2TF) response to FCC ET Docket No. 97-94. Replycomments were due August 18, 1997.

One of TIA’s comments relating to the FCC Notice of Proposed Rule Making (NPRM) involves the elimination ofthe FCC’s equipment authorization process called Notification. For equipment formally subject to Notification butnow subject to the DOC process, test laboratories would be subjected to the FCC’s laboratory accreditationrequirements and costs.

Another TIA concern is that the current NPRM does not include streamlining for equipment subject to Part 68(wireline equipment). In response to this concern the FCC will be releasing a further NPRM on streamlining thatcombines equipment subject to Part 68 with equipment covered in the current NPRM.

EMC LABORATORY ACCREDITATION WORKING GROUP (ELAWG)

TR-41.2/97-08-20 (TR-41.2 Chair), TR-41.2/97-08-21 (TR-41.2 Chair) and TR-41.2/97-08-22 (TR-41.2Chair) discuss the designation of conformity assessment bodies, which is the current issue of most interest inimplementation of the US-EU MRA. A number of organizations have begun to address this issue, including theEMC Laboratories Accreditation Working Group (ELAWG). The ELAWG includes participants from Association ofIndependent Scientific, Engineering and Testing Firms (ACIL), TIA, USCEL (United States Council of EMCLaboratories), U.S. Declaration of Conformity National Voluntary Laboratory Accreditation Program (US DoC



NVLAP) and FCC. Other participants so far have included the U.S. Food and Drug Administration (FDA), Ford andGM (representing the automotive sector), and Department of Defense (DoD) Joint Spectrum Center (representing themilitary).

The primary focus is to research the present accreditation processes and work toward coordinated guidelines forlaboratory accreditation. This group does not have any authority, but is sponsored by ACIL and includesgovernment representatives. ELAWG is working to address issues for which there is a void, with the expectationthat proposals developed will be provided as input to the appropriate organizations (e.g., TIA InternationalCommittee) and authorities.

The consensus of TR-41.2 was that the Chair of TR-41.2 should attend the September 22, 1997 ELAWG meeting toaddress TR-41.2 concerns regarding Conformity Assessment and lab accreditation in general, including consistency ofaccreditation requirements. D. Dulmage (Certelecom Laboratories) volunteered to be available as standby attendee atSeptember 22, 1997 meeting in Arlington, VA, at TIA.

EUROPEAN UNION - U.S. MRA

The parties to the Mutual Recognition Agreements (MRA) have completed negotiations successfully; agreements arecurrently being translated into the languages of the member states for formal signing. There will be a two yeartransitional phase to implement the mutual recognition of test results and the mutual recognition of certification.The parties must now determine how to designate conformity assessment bodies to perform the functions establishedin the MRA. TIA will work with the US government to assist in this task.

C. Berestecky (Lucent) reported that the TIA and the Information Technology Industry Council (ITI) will work aspartners on Conformity Assessment (CA), and will work with various government entities to initiate regulatoryreform. The object of this reform is to include an option for a Declaration of Conformity (DOC) as well as thirdparty certification, and to allow product marking to be moved off of the product surface and on to documentation andor the DOC itself.

ITI will be working MRA CA issues through the ITA-II, Trans-Atlantic Business Dialog and the World TradeOrganization (WTO). The US government’s position on the MRA is provided in TR-41.2/97-08-17 , a summaryof the MRA from the White House.

EUROPEAN UNION - CANADA MRA

This MRA with the EU has a shorter transitional period of eighteen months. Two principle issues being addressedare how to implement the safety and certification provisions. Canada is organizing an information seminar forindustry on the impact of the MRA.

OSHA RELATED ACTIVITIES

Work is continuing to be done in groups such as the TR2TF to develop proposals for changes necessary in OSHAregulations as a result of the EU MRA. OSHA still has the final say on approval of National Registered TechnicalLaboratories (NRTLs) for product safety for products sent from the EU to the US. There is general agreement thatchanges need to be made in OSHA. In negotiating for a DOC option, manufacturers may wish to consider the use ofaccredited laboratories as a means of instilling confidence in OSHA regarding the integrity and efficiency of thisoption.

NAFTA/CCT PROGRESS

The last Consultative Committee - Telecommunications (CCT) meetings, held in Toronto the week of June 9, 1997at Electro-Federation of Canada (EFC) headquarters, were probably the most productive to date. The emergencyMexican National Standards (NOM) on Terminal Attachment was published and Mexico plans on issuing anemergency NOM for ElectroMagnetic Compatibility (EMC) based on International Special Committee on RadioInterference (CISPR) 22 in the near future. Note: An emergency NOM is subject to review and modification priorto adoption as an official NOM.

Changes in Mexican law have allowed for certification and lab accreditation by non-government entities in the area ofproduct safety. Progress has been made towards furthering NAFTA objectives; however, a significant legislativeobstacle exists that needs to be addressed. Mexican metrology laws were discussed in the context of mutualacceptance of test data between the parties’ laboratories. Current Mexican metrology laws limit the ability of theparties to reach an agreement in this area.



Several meetings further to discuss this issue were scheduled for August 1997, including a meeting in Mexico CityAugust 19, 1997 as a preliminary step toward signing of laboratory to laboratory agreements to accept test data forproduct safety. Representatives from ACIL, US State Department, the Mexican government and private US andCanadian laboratories will attend.

The next CCT meetings are planned for the week of October 20, 1997 at TIA in Arlington, VA and may include aplenary session.

APEC AND CITEL ACTIVITIES PROGRESS

An agreement was reached by Asia Pacific Economic Cooperation Forum (APEC) members to have an MRAframework in place by the end 1997. The next meeting of Asian Pacific Nations (APEC) will occur in September1997 in New Zealand. APEC negotiations to date have focused on developing an MRA framework that allows theparties to sign on to the MRA when they are ready to do so. However, a minimum number of key countries mustbe willing to sign the MRA framework initially in order to successfully secure an agreement. Comments werereceived by A. Kwan (Industry Canada) in July 1997, and were generally positive.

The US is pushing very hard for implementation of the framework, a matter that will be discussed at the APECmeeting in New Zealand in September 1997. The US position is that the first phase of implementation of an agree-ment be done with the current requirements and processes of the respective parties where the assessment is beingconducted.

All the essential elements for an MRA have been developed in the framework, but not a complete agreement whichwould be signed by the respective governments. Any MRA that will be signed must be multi-lateral (hopefullyeight to ten parties) to be effective.

There is still controversy as to whether safety should be included in an MRA. It is recognized that OSHA is notnow prepared to change its regulations and time will be needed for regulatory (and possibly legislative) changes.

No Comision Internanericana de Telecomunicaciones (CITEL) MRA activity was reported at this time.

1998 TIA/FCC SEMINAR

The TIA/FCC seminar is to be held February 18 - 19, 1998. A proposed schedule and list of speakers was presented.

CONFORMITY ASSESSMENT MATRIX

TR-41.2/97-08-25 (TR-41.2 Chair), a summary of international conformity assessment issues for TerminalAttachment, Electromagnetic Compatibility and Electrical Product Safety, was revised based on the discussion of theTR-41.2 ad-hoc group teleconference meeting held July 30, 1997. It was further changed at the TR-41.2 meeting.

A list of conformity assessment working groups was drafted as follows:

• TIA: TR-41.2, TR2TF, MRA - APEC• ACIL: ELAWG, NCLAC (Higher level policy)• ITI: Tech. Reg. Committee (TRC)• Medical Sector• Automotive Sector

This list is to be expanded and clarified before the next TR-41.2 meeting.

MARKING AND LABELING ACTION PLAN

The proposal for a single marking concept will be presented at the International Electrotechnical Committee (IEC)plenary in September 1997. The single marking concept has received much favorable interest on an internationallevel. The proposal has been presented to many groups, including electrical and customs inspectors and is endorsedby TIA and ITI. The reaction among CEOs, via the Trans-Atlantic Dialog, has been positive.

INTERIM TR-41.2 MEETING

It was agreed that an interim meeting would be held at TIA headquarters during the week of October 20, 1997 towork on the impact of MRAs and the expanded list of conformity assessment working groups.



TR-41.3 AND CSA T510, TELEPHONES AND ACOUSTIC TERMINALS

IPR QUESTION

The Chair, D. Rittenhouse, asked whether there was a knowledge of patents, the use of which may be essential tothe standards being considered. None were identified.

ANSI S3.48 L IAISON

H. Mar (Industry Canada) reported that he had been unsuccessful in contacting the chairman of ANSI S3.48. D.Dulmage (Certelecom Laboratories) agreed to find out the status of the Hearing Aid Standard.

CSA LIAISON

D. Rittenhouse (Spectrum Sciences Institute) reported that the Canadian Standards Association (CSA) chair of T-510, Performance and Compatibility Requirements for Telephone Sets, has recommended to continue joint TIA/CSAmeetings on that standard. No new standard is being developed. With regard to voice transmit standards, CSA T-531(Acoustic-to-Digital and Digital-to-Acoustic Transmission Requirements for ISDN Terminals) is the equivalent ofTIA-579, Acoustic-to-Digital and Digital-to-Acoustic Transmission Requirements for ISDN Terminals. CSA T-531was issued initially in 1991, and was recently reaffirmed as part of the 5 year cycle. It was recommended that TIA-579 be adopted to replace existing T-531 (Acoustic to Digital and Digital to Acoustic Transmission Requirementsfor ISDN Terminals). In CSA T-515, Requirements for Handset Telephones Intended for Use by the Hard of Hearing, no new standards are anticipated.

IEEE LIAISON

R. Britt (Nortel) reported that the IEEE committee wishes to meet jointly with TR-41.3 at the November 1997 TIAmeetings. IEEE 1329, Standard Method for Measuring Transmission Performance of Hands-Free Telephone Sets,has made substantial progress and the final draft for acoustic echo cancellers should be out at their next meeting (lateAug. or early Sept. 1997). TR-41.3 members are asked to provide any comments for revision to IEEE 269-1992,Standard Method for Measuring Transmission Performance of Analog and Digital Telephone Sets, to the IEEEcommittee Chair J. Bareham (telephone: +1 313 665-4224).

TR-41.3/97-08-021 is from J. Bareham regarding the reaffirmation of IEEE 661-1992. He asks whether TR-41.3 wishes to reaffirm the IEEE 661 loudness rating or does TR-41.3 wish to use ITU-T P.79.

REVIEW ACTION ITEMS FROM LAST MEETING

TR-41.3 members were asked to review the previous proposal on anti-movement base from Wyle Labs (TR-41.3/97-02-005 ) that the handset cord extension should be in a 45° vertical direction as well as the horizontaldirections specified. TR-41.3/97-05-015 (J. Hazeltine, Wyle Labs) provides additional comments. Nortelcurrently implements a 45° test from the side or front of the set in both horizontal and vertical planes. TR-41.3agreed that the handset cord extension should be in a 45° vertical direction as well as the horizontal directionsspecified. It was agreed to include this change on a living list of changes to be incorporated in the next revision ofthe standard (CSA T-510 and EIA-470-B). D. Dulmage (Certelecom Laboratories) has agreed to maintain this list.

SP-2892, TIA-470-B

TIA/EIA-470-B, Performance and Compatibility Requirements for Telephone Sets with Loop Signaling, has gone toANSI for approval and publication.

SP-3399, TIA/EIA-504 AND CSA T-515

TIA/EIA-504-A, Acoustic and Magnetic Output Requirements for Handset Telephones Intended for Use by the Hardof Hearing, should be ready to go to ANSI in the next few weeks for approval and publication.

PN-3724, REVIEW OF A TO D AND D TO A TRANSMISSION REQUIREMENTS FOR ISDN TERMINALS ,EIA/TIA 579 , DRAFT 1.1

TR-41.3/97-08-019 (R. Britt, Nortel) contains Draft 1.1 of PN-3724, Acoustic-to-Digital and Digital-to-Acoustic Transmission Requirements for ISDN Terminals. This draft identifies the changes introduced at the May1997 TR-41.3. meeting. TR-41.3/97-08-020 , Draft 1.2, does not have the editing marks.



TR-41.3/97-08-017 (R. Magnuson, Siemens Business Communications) discusses sidetone requirements,terminal coupling loss and psophometric weighting.

TR-41.3 approved fPN-3724 for committee letter ballot.

PN-3674, ENHANCED CALLING FEATURES(TR-41.3.1)

Approximately fifteen responses were received from the ballot on PN-3764A with a number of Yes votes withcomments and one No vote. TR-41.3 reviewed the comments and, as a result of the No vote, made a technicalchange. TR-41.3 approved a motion to reissue the document with the technical change as PN-3674-B, for defaultballot.

FCC NEGOTIATED RULEMAKING ON HEARING AID COMPATIBILITY VOLUME CONTROL

FCC issued a notice of reconsideration to change the implementation date for the volume control Hearing AidCompatibility (HAC) requirements from November 1, 1998 to January 1, 2000. There is a task group under TR-41.9 looking at the apparent conflict between Parts 68.112 and 68.317 as applied to headsets. Part 68.112 discussesthe FCC’s rationale whether HAC volume control is required; 68.312 contains the technical requirements.Declaration of compliance with 68.317 is required on Form 730 as a condition for registration. This declaration is inconflict with the rationale for HAC requirements for headsets. The use of HAC volume control requirements forheadsets are regulated in the workplace, rather than at registration of telephone equipment

BELL TAP MEASUREMENT

TR-41.3/97-02-006 is a proposed addendum to EIA-470-B, Performance and Compatibility Requirements forTelephone Sets with Loop Signaling, regarding referencing WECO 221 relays. As noted at the previous twomeetings, relays equivalent to the WECO 221 components have been identified as being available from Midcom.W. Becker (Lucent) has agreed to arrange for some tests to be conducted to verify the equivalency of these relays. Itwas noted that the Midcom relays do not provide equivalent characteristics to the WECO 221 components. Testsperformed using the Midcom components have given different results than those performed using the WECO compo-nents. No information has been received from W. Becker.

D. McKinnon (Thomson Consumer Products) reported on correspondence with Midcom on the issue of relaysequivalent to the WECO 221 components. D. McKinnon indicated he would be pursuing this issue further withMidcom and agreed to provide information on any developments to TR-41.3.

A secondary issue of bell tap occurs during network testing due to ringer sensitivity characteristics. Some of theoccurrences may be due to transients that occur during switching from line circuits to the test circuits, etc.

The TR-41.3 Chair agreed to send a formal request prior to the FCC Industry meeting, scheduled September 16,1997, to B. Von Alven, to provide more detailed information on this issue. D. McKinnon has also agreed to contactBellcore to request more information.

CORRECTIONS TO ALERTER SENSITIVITY

TR-41.3/97-08-018 (R. Britt, Nortel) contains corrections to Alerter Sensitivity. TR-41.3 agreed with theproposal to add the following statement at the end of 4.3.1.1.2, Method of Measurement: “Repeat all tests without adc bias, i.e., using 0 Vdc.” This item will be added to the living list changes proposed for the next revision of theEIA/TIA-470, CSA T-510 standard.

TR-41 MANAGEMENT ISSUES RELATING TO TR-41.3

It was reported that TIA is implementing a web site where meeting notices may be downloaded. In addition TIA isimplementing a an ftp site for exchange of information. TIA has asked that each committee chair ask for anelectronic document coordinator (EDC) to upload information. Each EDC would be given a password. Thispassword would be changed from time to time to maintain security.

D. Dulmage (Certelecom Laboratories) has tentatively agreed to be the EDC for TR-41.3.

TR-41.5, MULTIMEDIA BUILDING DISTRIBUTION SYSTEMS

No patent statements were disclosed or discussed at this meeting



RESIDENTIAL GATEWAY PROJECT

A number of contributions with proposed text to the draft standard were reviewed and included in the TR-41.5 livinglist. The text will be folded into the draft standard by the editor.

Bellcore’s Radio Frequency Interface (RFI) on Residential Gateway (RG) is to be used by TR-41.5 as a key sourcedocument to bring focus and consensus to the drafting of the RG standard.

Although there is agreement on drafting an RG standard focusing on a minimum set of requirements only, furtherdiscussion is needed to define such a set, in particular for layers 1-3.

Discussion continues on the level of details that need to be specified in RG, in particular with respect to the RGhardware and associated techniques to interconnect carrier access network with home network (e.g., backplane, busspecifics, etc.).

TR-41.5/97-08-09 (Nortel), defining the standard interfaces for both the access and the customer premises side, wasseen as containing a minimum set of requirements necessary for achieving connectivity to/from an RG. Thecontribution did not reveal endorsement of TR-41.5’s view of full vendor interoperability. There will be furtherdiscussion on this subject.

TR-41.5/97-08-05 (R. Cochran, GTE) contains version 2 of FSAN-GX (Full Service Access Networks)Network Termination - Home Network working group, submitted for information (seehttp://www.labs.bt.com/profsoc/access/ for additional information). The GX is an international initiative by telcosand manufacturers to develop a consensus on the systems required in the local access network, focusing on xDSL ac-cess technologies, to deliver a full set of telecom services, both narrowband and broadband. It aims to enable thelarge-scale introduction of broadband access networks through the definition of a basic set of common requirements.

TR-41.5/97-08-04© (R. Cochran, GTE) contains the latest version of the RG draft (v3.1c) reflecting inputs from theMay meeting. The V.3.2 version, reflecting inputs from this meeting, is expected in a TR-41.5 mail-out withinfour weeks.

TR-41.5/97-08-003 (R. Cochran, GTE) contains a list of scenarios developed by TR-41.5 and sent to VESAHNW group as a preliminary response to a request from HNW group for a listing of items that the RG would expectthe Home Network to provide.

TR-41.5/97-08-006 (R. Cochran, GTE) contains a list from the Video Electronic Standard Association (VESA)of their requirements, as agreed to at their July 1997 Home Network Committee meeting. VESA requests that theTR-41.5 RG satisfy these requirements to interface with the VESA Home Network:1. Support of multiple RGs on a home network2. Support for VESA defined physical layers, e.g., IEEE 1394LD and local peripheral network3. Support TCP/IP stack4. Support for VESA defined network management and control5. Support for VESA defined directory services6. Hot swappable7. Support for lifeline and other emergency services

TR-41.5/97-08-007 (R. Janow, Lucent) provides proposals on operating security requirements, includingauthentication, physical security and data encryption.

TR-41.5/97-08-010 (Lucent) contains requirements for the Home Network Operating System (HNOS) that willsupervise the RG and the appliances that it serves. It offers an HNOS architecture and defines key technicalcharacteristics and discusses principles of operation.

TR-41.5/97-08-08 (K. Kerpez, Bellcore) contains proposed prototypical requirements and guidelines for the RG,including:• Service reliability and availability• Design guidelines, focusing on performance specifications (e.g., electrical protection, environmental

consideration, fault monitoring, back-up powering). This input also includes design guidelines for RG locations,housing types, plug-ins, inherent maintenance requirements, etc.

Bellcore has issued an RG RFI (not distributed at TR-41.5) with response due September 19, 1997. The RFI isclosely aligned with current TR-41.5 RG views, and its questions are in-depth and thought-provoking. Following a



suggestion by Nortel, TR-41.5 decided to use the RFI (background and questions) as an information source and abasis for achieving consensus on outstanding RG issues triggered by the RFI questions. Teleconference meetingswere scheduled October 13-17, 1997 to review responses to Bellcore RFI questions with relevance to TR-41.5.

VESA UPDATE

VESA’s (www.vesa.org) liaison reported that IEEE 1394 (High Performance Serial Bus) proof-of-concept has beenachieved in June, as scheduled. Due to technical difficulties (i.e., bus reset issues), only operation with a 4.5 meterdistance of the 1394LD (long distance) version was accomplished. The proof-of-concept used different equipmentfrom different vendors with a mixture of Category 5 and coax cabling. VESA is scheduled to have a public technicaldemo sometime later this year. VESA’s focus is to use IP over IEEE 1394, consistent with their push in theDigital Audio-Visual Council (DAVIC). The next VESA meeting will be September 3-4, 1997 in Morristown, NJ.The meeting will include detailed reports on IEEE 1394LD version status, discussion on resolution of proof-of-concept ‘bus reset’ issue, etc.

Severin Godo, Nortel

TR-41.6 WIRELESS USER PREMISES EQUIPMENT (WUPE)

The following contributions were submitted to the TR-41.6 meeting:

TR-41.6/97-08-13 is comments on the ballot resolution of SP-3614-1 from P. Adornato (Nortel). Nortelapproved the resolution to their negative ballot comments, and therefore approved SP-3614-1 (Personal WirelessTelecommunications - Enhanced Interoperability Standard for 1.9 GHz Band, PWT-E).

TR-41.6/97-08-14 provides comments on the ballot resolution of SP-3614-1 from W. Cruz (LucentTechnologies). Lucent is concerned about out-of-band emissions of PWT-E devices and the effect of these emissionson neighboring PCM systems and did not approve the ballot resolution and therefore still does not approve SP-3614-1.

WARC-92 identified the bands 1885-2025 MHz and 2110-220 MHz as being available on a worldwide basis for useby the terrestrial component of IMT-2000. ITU-R is considered allocating portions of this spectrum for FrequencyDivision Duplex (FDD) and Time Division Duplex (TDD) implementations. TR-41.6/97-08-15 , Aligning theSpectrum Allocations of IMT-2000 with User (Unlicensed) PCS (W Cruz, Lucent Technologies), proposes that TR-41 send a liaison to ITU-R recommending that ITU-R minimally allocate the frequencies 1910-1930 MHz for TDD,low-powered, and unlicensed premises-based wireless applications. (The term premises is used to refer to the indoorand campus environment simultaneously.) This allocation will align the IMT-2000 TDD frequency allocation withthe TDD designation in the Personal Communication Services (PCS) band plan adopted by the Americas.

TR-41.6/97-08-16 , Review of CITEL’s Coordinated Standards Document and Liaison To CITEL withComments (W. Cruz, Lucent Technologies), reviews standards activity on a global basis related to low powereddevices that operate in the 1910-1930 MHz band with a focus on their “air interface” standards and unlicensedapplications. The organization of American States’ (OAS) Inter-American Telecommunications Commission(CITEL) is developing a Coordinated Standards Document (CSD) for the 1910-1930 MHz band. This contributionencloses a copy of the CSD for review for accuracy by TR-41.6 members. It proposes that TR-41 send a liaisonletter to Permanent Consultative Committee I’s (PCC-I) Working Group on Standards Coordination providingcomments on the CSD.

TR-41.6.1, PERSONAL WIRELESS TELECOMMUNICATIONS

The following contributions were submitted to the TR-41.6.1 meeting:

TR-41.6.1/97-08-23 (same as TR-41.6/97-08-14) is comments on the ballot resolution of SP-3614-1 fromW. Cruz (Lucent Technologies). Lucent did not approve the ballot resolution and therefore still does not approveSP-3614-1.

TR-41.6.1/97-08-24 (same as TR-41.6/97-08-13) is comments on the ballot resolution of SP-3614-1 fromP. Adornato (Nortel). Nortel approved the resolution to their negative ballot comments, and therefore approved SP-3614-1.

TR-41.6.1/97-08-25 , Probability of PWT-E Interference: TDMA PCS Base Station Victims, is a presentationfrom Lucent Technologies. PWT-E systems operating in the PCS licensed bands emit undesirable RF energy into



adjacent bands. Because PWT-E is a TDD system, there is no frequency separation between the FT (FixedTerminals) or PP (Portable Parts) transmit and the PCS FDD base station receive bands. This makes PCS basestations extremely vulnerable to out-of-band PWT-E emissions. PCS base station rise in noise floor and otherstatistical PCS performance degradation metrics are described and evaluated.

TR-41.6.1/97-08-26 , Comments on CPAP (W. Cruz, Lucent Technologies), proposes that two features, InfiniteDTMF Tone Length Generation and Authentication of the Fixed Part, be changed to optional from required in theCPAP requirements defined in TIA/EIA-662-9.

TR-41.6.1/97-08-27©, Proposed Solutions for RFP EIRP (Fixed Radio Part Effective Isotropic Radiated Power) andEmission Requirements of SP-3614 PWT-E (S. Lin and J.R. Wang, Lucent Technologies), provides LucentTechnologies proposals on the Radio Fixed Part EIRP and emission requirements of the SP-3514 (PWT-E). Theattachment addresses not only the rationale of some proposals but also an updated analysis on the impact of theproposed PWT-E systems on the existing Personal Communications Service (PCS) Frequency Division Duplex(FDD) technologies based on the PWT-E maximum EIRP and emission mask proposed at the TR-41.6 Meeting onMay 19, 1997.

TR-41.6.1/97-08-28©, (S. Lin and J.R. Wang, Lucent Technologies) provides comments on Ericsson’s contributiontitled “On Proposed Solutions for RFP EIRP and Emission Requirements of SP-3614 PWT-E, Rev. D” submittedto TR-41.6.1 via e-mail on July 22, 1997. Lucent suggests a guard band be included in the PWT-E band plan toensure interference between same band TDD and FDD systems is sufficiently reduced.

TR-41.6.1/97-08-29 , On Proposed Solutions for RFP EIRP and Emission Requirements of SP-3614 PWT-E(D. Akerberg, Ericsson), also provides comments on the Ericsson e-mail contribution.

TR-41.6.3 PACS-WUPE

The following contributions were submitted to the TR-41.6.3 meeting:

TR-41.6.3/97-08-009 is a TIA Project Authorization Request Form for a revision of TIA-667, Personal AccessCommunications System - Wireless User Premises Equipment (PACS-WUPE) Air Interface. The editor will be P.Weismantel (NEC). TIA-667 is an interoperability standard for a radio system operating in the unlicensed PCSband. This project is an enhancement to TIA-667 to add support for new services such as circuit switched data (32kbit/s unrestricted), supplementary services, and aggregated time slots. Estimated completion of the project is March1998. TR-41.6.3/97-08-010 is the ANSI PINS form for this project.

TR-41.6.3/96-09-10 , PACS-WUPE Unrestricted Digital Information (P. Weismantel, NEC America, Inc.),contains changes needed for the addition of Unrestricted Digital Information (UDI) transfer capability in the supportof Circuit Mode 32 kbit/s data transmission. This proposal is represented in the form of changes to the ballotedversion of PACS-WUPE, Standards Proposal No. 3447 (to be published as TIA/EIA-667). This contributionsupersedes TR-41.6.3/96-06-007.

TR-41.7 E NVIRONMENTAL AND SAFETY CONSIDERATIONS

LIAISON

T1E1.7 has not met since the last TR-41.7 meeting. All approved and default ballots have gone out and will closebefore the next T1E1.7 meeting in September 1997. There has been no meeting of IEEE 1100 since the last TR-41.7 meeting.

BI-NATIONAL TASK GROUP

The revised draft third edition of the Bi-National Safety Standard (CSA 22.2 #950/UL 1950) is expected to bepublished by year’s end. The ANSI standard, UL 1950, has completed the voting procedure.

During the review of the revisions to UL 1950, some Bi-National Working Group (BNWG) members stated thatthere are conflicting positions on the acoustic safety limits being reported by the Hard of Hearing advocates, whobelieve the limits are too low for their constituents, and the Europeans who believe the US/Canadian limits are toohigh. TR-41.7 recommended that TR-41 determine whether TR-41.3, TR-41.7 or TR-41.9 should be the focal pointfor this activity. It was pointed out that TR-41.9 has an active Ad Hoc Committee which is addressing the FCC and



Hearing Aid Compatible (HAC) volume control issues. R. Ivans (Underwriters Laboratories) agreed to provideinformation on this subject at the next TR-41.7 meeting.

NEC

The Report on Proposals (ROP) for the National Electric Code (NEC) is in the public comment period until October24, 1997 and is available as hard copy, CD ROM or on the World Wide Web from the National Fire ProtectionAssociation (sponsor of the NEC) site: www.nfpa.org.

NAFTA CCT

No significant progress was made in the Product Safety Working Group at the June 9, 1997 ConsultativeCommittee - Telecommunications (CCT) meeting in Toronto, Canada.

ANSI/TIA/EIA-631, I MMUNITY STANDARD

R. Breden (TIA) reported that the program to promote ANSI/TIA/EIA-631-1996, Standard on Radio Frequency (RF)Immunity for Telephones, discussed at the last meeting was withdrawn by TIA. TIA rejected the concept of aMemorandum of Understanding (MOU) between TIA and Manufacturers to adopt a voluntary standard written byTIA. The potential for FCC regulation mandating the requirements in TIA-631 may be increased by this decision.R. Breden proposed development of a letter and a questionnaire apprising TIA member telephone manufacturers of thepotential consequences of FCC regulation, requesting information on any difficulties in meeting TIA-631, andsoliciting recommendations. R. Breden agreed to prepare the questionnaire and letter, which will be reviewed at theNovember 1997 TR-41.7 meeting.

TR 41.7/97-08-08 (R. Ivans, Underwriters Laboratories) describes an international (Europe, USA, Japan)Electromagnetic Compatibility (EMC) mark being provided by UL in conjunction with certification of equipment tovarious national and international EMC standards. The mark is designed to be tailored to any standard or group ofstandards and was offered for use with TIA-631.

TR-41.9 L IAISON

TR 41.7/97-08-07 (L. Baker, RELTEC) is the transverse surge and the IEC AC surge waveform proposal to TR-41.9 for changes to FCC Part 68 (presented to TR 41.9 as TR 41.9/97-08-73). TR-41.7 authorized L. Baker(RELTEC) to produce the contribution based the information in section 4.3.3 of SP-3283, TelecommunicationsUser Premises Equipment Environmental Considerations, because there have been no comments on thoserequirements from the ballot. L. Baker noted that the powered up condition and the continued relevance of thetransverse surge was questioned in TR-41.9.

SP-3283 T ELECOMMUNICATIONS USER PREMISE EQUIPMENT ENVIRONMENTAL CONSIDERATIONS

The ballot for SP-3283A, Telecommunications User Premises Equipment Environmental Considerations, will notclose until after the August 1997 TR-41.7 meeting, and was not on the original agenda. TR-41.7 agreed to add SP-3283A back to the agenda to clarify members’ concerns about editorial changes. TR-41.7 agreed that some editorialchanges had introduced errors which resulted in inadvertent technical changes. L. Baker (RELTEC) proposedchanging editors for the next revision and correcting the newly introduced errors; he proposed not delaying the ballotto make changes now. There were no objections to this proposal. Possible errors included the following:

• 4.1.2: The last line in the second paragraph was to become the third paragraph. This error was also missed inthe minutes from the May 1997 TR-41.7 meeting.

• 4.3.2.2: The word telephone in the second paragraph was deleted. This was not discussed previously but seemedto be an editorial improvement.

• Figure 2: This figure became Figures 2 and 3, which moved the application drawings from Figure 2 to Figure 3and expanded them from four to seven sub figures. The new longitudinal telephone surge Figures 3d and 3e didnot reverse the surge generator polarity as they should have. The power surge Figures 3a and 3b did not show ordiscuss the isolation networks necessary when connecting the AC power to the Equipment Under Test (EUT).The Transverse surge description in 4.3.3.2(4) and Figure 3f did not match concerning the AC power connection.

• 4.3.3.3: The table format was changed from referencing the application figures to referencing the surge generator.Also the figure reference for L-1 and L-2 is reversed.

• B2: The second paragraph was re-written, broken into two paragraphs and moved. This was authorized by theTR-41.7 at the May 1997 TR-41.7 meeting and left to the editor to complete. The intent of the changes werecomplied with.



BALANCED RINGING SAFETY ISSUES

R. Ivans (Underwriters Laboratories) reported that UL had tested units which incorporated Subscriber Line IntegratedCircuits (SLICs), which provided 72 volts between tip and ring during the ringing cycle. This issue will bediscussed further at the November meeting.

LeRoy Baker, RELTEC

TR-41.8 COMMERCIAL AND RESIDENTIAL PREMISES WIRING

TR-41.8.1 COMMERCIAL BUILDING CABLING

INTELLECTUAL PROPERTY RIGHTS (IPR)

Patents and pending patents disclosed at the meeting were noted from 3M, AMP, Lucent, Panduit, and Siecor.

OPTICAL FIBER CONNECTORS

Five connector presentations were brought to TR-41.8.1 to possibly choose a new physical connector (replacementfor the SC configuration) for the TIA-568-B (Commercial Building Telecommunications Cabling Standard):

TR-41.8.1/97-08-041 (T. Szostak, 3M Volition)TR-41.8.1/97-08-042 (AMP/Siecor/NTT Mini-MPO)TR-41.8.1/97-08-039 (IBM/Siecor; SCDC)TR-41.8.1/97-08-043 (Lucent; LC)TR-41.8.1/97-08-040 (Panduit, Fiber Jack).

The fiber optic connector selection process was established in TR-41.8.1/97-08-052 (J. Siemon, The SiemonCompany). It outlines a schedule of events over three TR-41.8 meetings starting in August 1997 and concluding inFebruary 1998. TR-41.8.1/97-08-053 (J. Siemon, The Siemon Company) is a questionnaire that providescriteria and weighting factors that will be used in the decision process. The questionnaire (not to be filled out bymanufacturers of these products) was distributed to TR-41.8.1, and will also be distributed to Institute of Electricaland Electronic Engineers (IEEE) and Building Industry Consulting Services International (BICSI) members.

P. Kish (Nordx/CDT) read a letter from Fibre Channel (TR-41.8.1/97-08-051) dated June 18, 1997, stating that theirletter of February 14, 1997 was pre-mature in selecting the “Galaxy” connector (3M Volition) as their connector ofchoice.

All the fiber optic connector presentations were given to TR-41.8.1 by their respective companies. Except for the3M Volition connector, all of the connectors use ferrule technology to control fiber alignment. The 3M Volitionconnector uses a V shaped notch for fiber alignment. At the next meeting, installation of the connectors will bedemonstrated in break-out rooms.

UTP SYSTEMS TASK GROUP

Approximately fifteen contributions were submitted since the last TR-41.8.1 meeting; the TR-41.8.1 Task Groupdid not get to edit TIA-568-B.2 (UTP). An interim meeting was requested on September 28-29, 1997 in SantaClara, CA in conjunction to the BICSI conference; a conference call is scheduled for August 29, 1997 to discusscontributions to the US Technical Advisory Group (TAG).

CONNECTOR TASK GROUP

One conference call has been held since the last TR-41.8.1 meeting to work on PN-2948, TransmissionSpecifications for Unshielded Twisted-Pair (UTP) Patch Cords. The de-embedded method of testing has been put onhold while two other test methods are being investigated. Some liaison work with Germany may influence the patchcord test method. Round Robin testing also continues on patch cords. The leadership on PN-2948 has been trans-ferred to V. Rybinski (The Siemon Company).

The UTP Systems Task Group has requested that the Connector Task Group investigate connector return loss andbalance. Also, there was concern over the need for power-sum Near End Cross Talk (NEXT), or whether a 45 dBrequirement should be specified for connectors. The specification of ELFEXT (Equal Level Far End Cross Talk) mayalso be specified for links and for enhanced category 5 cables.



TR-41.8.1/97-08-046 H. Koeman and A. Bennett, Fluke, Relationship of NEXT and FEXT in modular RJ-45Connectors, concludes that NEXT and FEXT differ by twice the inductive coupling crosstalk, which can besignificant. This inductive crosstalk can be both in phase with the NEXT or out-of-phase. Therefore, the inductivecrosstalk (or rather the imbalance of inductive coupling crosstalk) should be minimized in order to optimize NEXTand FEXT at the same time.

TR-41.8.1/97-08-045 H. Koeman and A. Bennett, Fluke, LCL Measurement Accuracy Test Procedure withResults for North Hills 0322BF Baluns, establishes an LCL (Longitudinal Conversion Loss) balance measurementaccuracy test method that can be applied to all measurement methods. It determines typeical results for a North Hillsseries 0322BFA1 balun.

OPTIC FIBER TASK GROUP

The Siemon Company recommended that the connectors being decided upon be restricted to the outlet and patchpanel only. The Fiber Optic Task Group agreed to this request. Lucent Technologies recommended that reflectionbe specified at –55 dB for single mode connectors. The Task Group agreed to send liaison letters to IEEE and theAsynchronous Transfer Mode (ATM) Forum to see whether greater than –26 dB will be required in the future. Aliaison will also be sent to FO-2.2 (TIA Fiber Optics Committee Local Area Network Systems) about theimportance of test specifications for VCELS (Vertical Cavity Surface Emitting Laser). The Task Group will addressthe topics of 300 meter cable lengths; color identification of fiber optic cabling will be addressed at a later date.

EDITORIAL TASK GROUP

D. Fish (Wavetek), editor of TIA-568-B, has been waiting for information from Task Groups. At the current TR-41.8.1 meeting, information was provided by the Fiber Optics Task Group and the Installation Requirements TaskGroup. This information will be included in the next draft of TIA-568-B.

HARMONIZATION

In June 1997, the Joint Technical Committee 1 (JTC1)/SC25/WG3 met in Brazil; six US delegates attended. Flukehas joined the US Technical Advisory Group to JTC1/SC25/WG3, which will further performance testing harmo-nization. The next meeting for JTC1/SC25/ WG3 will be in September 1997 in Munich, Germany. TR-41.8 .1 /97-08-049 is a liaison letter from the US TAG (Technical Advisory Group) to TR-41.8.1, asking forcontributions that can be forwarded into JTC1/SC25/WG3 for discussions on modifying ISO/IEC-11801 (Genericcabling for customer premises). It reports that the infamous “cat-6” issue has been under discussion in WG3 for anumber of meetings. At the Buzios meeting in June, a lot of progress was made on how to move forward withspecifying higher bandwidth cabling. At this point it looks likely that ISO will standardize enhanced UTP/FTPcabling as well as enhanced STP cabling. The next WG3 meeting is scheduled for September 15-18 in Munich.The US must provide performance numbers to avoid being excluded from higher performance cabling.

NEXT GENERATION STUDY GROUP

No contributions have been brought to the Next Generation Study Group. The next generation cabling will bespecified above the 100 MHz enhanced cabling that is being worked on in the UTP Systems Task Group. F. Perry(CTC) agreed to provide a strawman on the next generation cabling.

SCTP TASK GROUP

TR-41.8.1/97-05-047 contains the ballot comments to SP-3193, Technical Specifications for 100 Ω ScreenedTwisted Pair Cabling. 10 companies voted no (Berg, Belden, AMP, Lucent, Essex, Mod-Tap NA, BTR,Nordx/CDT, BICSI and Montrose/CDT). An additional 9 companies voted yes with comments. Many changes weremade to the document. A conference call will be held for further comment resolution.

STP-A TASK GROUP

D. Hess (Alcatel), chair of the Shielded Twisted Pair (STP)-A Task Group, did not have much to report on progressto TIA-568-B.4. No comments have been received concerning the issues list distributed at the May 1997 meeting.

INSTALLATION CABLING REQUIREMENTS TASK GROUP

TR-41.8.1/97-08-UNN (M. Doorhy, Panduit), a contribution on cable ties, was accepted by the Task Group(not submitted to TR-41.8.1 and therefore unnumbered). The contribution concluded that tie wraps do not affectNEXT and Return loss when placed so that they do not deform cables and that they can be turned on the cable bundle



with ease. AMP and Belden agreed to provide a contribution for the next meeting on cable bend radius. The SiemonCompany contribution from a previous meeting (TIA-568-B Section 11 Installation Requirements StrawmanRevision 6, 6/3/97) was reviewed and the document revised. The document was turned over to the TR-41.8.1 to beincluded in the next draft. The Installation Task Group will be dormant until the Working Group can provideanswers to their questions that are imbedded in the document.

NEW ITEM

A Project Proposal was suggested for an informative applications guide (TSB) for inter-building cabling. This guidewould include typical characteristics of transmission for channels between buildings. A scope will be written andbrought to the next meeting to see if others are interested in participating.

TR-41.8.2, RESIDENTIAL & LIGHT COMMERCIAL PREMISES DISTRIBUTION

TR-41.8.2/97-08-019 , Draft 9 of the Residential Telecommunications Cabling Standard (PN-3490 revision ofEIA-570), was edited during a July 1997 editing meeting and was also modified during this meeting. TR-41.8 .2/97-08-020 (B. Jensen, dbi) is dbi’s review of items from the existing EIA-570 standard (Residential andLight Commercial Telecommunications Wiring ) to be considered in the current draft of the document. Some itemsincluded are the wall-phone mounting dimensions, and reference to TSB-31-A (Part 68 Rational and MeasurementGuidelines).

TR-41.8.2/97-08-021 (C. Klauck, The Siemon Company) provides editorial changes to the current draftdocument including revisions to figures. TR-41.8.2/97-08-022 (O. Charm, RRH and M. Shatzkin, Leviton)presents modifications to the section on “distribution device” and provides new minimum space requirements. TR-41.8 .2/97-08-023 (M. Shatzkin, Leviton) provides editorial comments as well as modifications of content,including the addition of a home office type of room and the use of non crimp type coaxial connectors (e.g.,Raychem EZ Twist connectors).

All contributions were accepted by the TR-41.8.2 with edits. Boston Optical Fiber was not ready to give itspresentation on plastic optical fiber at this meeting and will provide its contribution at the next meeting. TR-41.8.2is concerned about how to reference Society of Cable Television Engineers (SCTE) documents; B. Jensen (dbi) willaddress the issues with TIA. Definitions in section 3 will be brought to TR-41.8.5 for review at this meeting. It isanticipated that with TR-41.8.2 approval at the next meeting, PN-3490 will go to ballot in November 1997.

TR-41.8.3, BUILDING PATHWAYS AND SPACES FOR TELECOMMUNICATIONS

TR-41.8.3/97-08-002 (P. Kreager, KAI), includes the Draft E rewrite “Perimeter Pathways” for TIA-569-A.The approved standard of the Commercial Building Standard for Telecommunications Pathways and Spaces(ANSI/TIA/EIA-569-A) has been sent to TIA for publication.

B. Jensen (dbi) reported that the Cable Tray and Conduit Fill Sub-Task Groups are still working on contributions.The Conduit Fill Task Group will meet at Polywater in September 1997. TR-41.8.3/97-08-003 (J. Nienhuis,Herman Miller) discusses furniture pathways fill, proposing that pathway percent fill be calculated by dividing thetotal cross-sectional area of the cable by the total cross-sectional area of the most restricted portion of the pathway.

R. Keden (Erico) reviewed perimeter pathways (including pathway fill). TR-41.8.3/97-08-004 (C. Klauck, TheSiemon Company) provides edits on the perimeter pathway section of TIA-569-A. Both the furniture pathway filland the perimeter pathway sections were approved with edits by TR-41.8.3 for balloting as an addendum toANSI/TIA/EIA-569-A. TR-41.8.3/ 97-08-005 (G. Fishel, AMP) is a contribution on changes to accessflooring requirement to reduce the minimum height of raised floors below 6 inches. The base document used in thecontribution was from the original TIA-569 and was not current enough to provide an updated section. G. Fishel(AMP) will address this with the Access Floor Task Group and provide a contribution at the next meeting.

TR-41.8.4, CUSTOMER-OWNED OUTSIDE PLANT

TR-41.8.4/97-08-012© is Draft 9 of PN-3339, Customer-Owned Outside Plant Telecommunications Cabling. J.Baer (Essex) reported that the broadband-Outside Plant (OSP) cable document has not yet been accepted by theInsulated Cable Engineers Association (ICEA), but is anticipated to be approved at their September 1997 meeting.BICSI reported that they are waiting on updates to this standard before proceeding with their manual.

TR-41.8.4/97-08-013 (P. Kish, NORDX/CDT) is a contribution on the bandwidth of Category 3 and Category5 OSP cables. It notes that data rates up to 52 Mbit/s are practical (with sophisticated modulation) over a mile of



Category 5 cabling. A Task Group was established as a result of this contribution that will look into producing aTelecommunications Standardization Bulletin (TSB) on transmission requirements and reach.

The term “tunnel” was discussed and will be brought back to the Definitions Working Group for further disposition.A review of the draft standard was conducted among the group and several homework assignments were given. TR-41.8.4 hopes to send the document for ballot at the November 1997 meeting.

TR-41.8.5, DEFINITIONS

The Working Group discussed several items presented by P. Kreager (KAI). Many of the comments were editorial.B. Jensen (dbi) provided new definitions from the Residential Cabling Working Group. D. Ballast (BICSI) providedsome terms from the Customer-owned OSP Cabling Working Group for revision. All contributions were discussedand will be edited into the next draft of definitions.

Bob Jensen, dbi

REPORT OF TR-41.9 REGULATORY CONSIDERATIONS ON TERMINAL ATTACHMENTPROGRAMS

A. Wride (TR-41.9 Chair) asked members to identify whether there was knowledge of patents, the use of whichmight be essential to the standards being considered. None were identified.

TAPAC, TAPAC TTF, TAPAC ATF LIAISON REPORT

The Terminal Attachment Program Advisory Committee (TAPAC) and its Task Forces last met May 6 - 7, 1997 inOttawa. TAPAC and its Task Forces have not met since the last TR-41 meeting; however, the following activitiesmay be of interest to the TR-41.

The draft proposal on Hearing Aid Compatible (HAC) Receive Volume Control for Telephone Handsets has gone forTAPAC letter ballot with a due date of June 30, 1997. Although no negative ballots were received, there are com-ments requiring further technical resolution. Furthermore, the FCC has recently published an Order onReconsideration (FCC 97-242) which extended the transition period of implementing these requirements from 1998to 2000. Technical comments will be reviewed at this TR-41.9 Joint Harmonized Task Group meeting, and at thenext TAPAC/TTF meeting Oct 7, 1997 for recommendation to TAPAC. Re-balloting will be carried out afterwards.

A TAPAC letter ballot on the draft Provisional Document for Asymmetrical Digital Subscriber Loop (ADSL)Terminal equipment was issued July 8, 1997 with a due date of Aug. 8, 1997. No negative votes were received;some editorial comments have been dealt with. The document is currently being translated. It will be gazetted andpublished soon.

The TAPAC Administrative Task Force (ATF) and the Part 68 Administrative Committee have formed a joint taskgroup to compare the application form for submission to the FCC with the one submitted to the Industry Canada.Progress will be reported at the next FCC Part 68 Industry Meeting September 16, Washington DC.

FCC ADMINISTRATIVE COMMITTEES

TR-41.9/97-08-057 (FCC) is the Second Report and Order and Second Further Notice of Proposed Rulemakingon CC Docket 88-57, simple inside wiring (up to 4 lines), released June 1, 1997. TR-41.9/97-08-065 (TIA)contains comments on the original docket; August 1 was the date for reply comments. The TIA petition had an itemaddressing a Building Industry Consulting Services International (BICSI) petition for Category 3 wiring, stating thatcross talk could occur; it recommended that the FCC adopt the use of Category 3 wiring. The second FCC proposalprovides for an interim two year standard; BICSI proposed that the standard be adopted as permanent. FCC wiremarking requirements were also discussed; there was concern that only copper wire was included in the standard. TheGold and Gold equivalency standard recommended by the TIA was also adopted for two years; TIA had recommendedthat this standard be adopted permanently.

TR-41.9/97-08-056 is a list of all legal document relating to the HAC issues.

REPORT ON ADMINISTRATIVE JOINT HARMONIZATION GROUP:

TR-41.9/97-08-061 (A. Wride, TR-41.9 Chair) is TR-41.9’s overall comparison report of the CanadianCertification Procedure CP-01 and the US equivalent FCC Form 730 dated May 22, 1997. Attached is a copy of the



meeting report of the July 3, 1997 teleconference, discussing some points raised and how to move towardharmonization of these two procedures. A. French (Industry Canada) agreed to develop a first draft point-by-pointcomparison of the two procedures.

TSB-31-B PART 68 HARMONIZED STATUS PUBLICATION UPDATE

A. Wride (CCL) is attempting to obtain the master TSB-31-B file from D. Hays (Lucent), to ensure that all editorialchanges are made before sending it to TIA for publication.

ADSL

One TR-41.9 member raised concern that Asymmetrical Digital Subscriber Loop (ADSL) may be a transienttechnology. Other members reaffirmed from previous meetings that the membership had agreed that it is within thescope of TR-41.9 to deal with all emerging technologies that impact terminal attachment. TR-41.9/97-08-071(P. Walsh, Paradyne) includes Paradyne’s recommendations (based on Canadian CS-03 provisional requirements) foramending Part 68 requirements to include ADSL-R (Remote) equipment using Public Switched Telephone Network(PSTN) facilities. This addresses transverse balance limitations and interference limitations for transmission ofADSL signals, including PSD (power spectral density), total signal power and longitudinal voltage. TR-41.9concluded that the proposal required further revision, including removal of the longitudinal voltage section.Additional discussion will occur at the next TR-41.9 meeting.

TR-41.9/97-08-062 , provides Paradyne’s technical comments to the TAPAC provisional CS-03 requirements forADSL/RADSL (DMT and CAP/QAM) equipment.

PCM MODEMS

TR-41.9/97-08-070 , a liaison from TR-30.1, was the basis for discussion on 56k-bit modem technology. D.Moon (General DataComm) described the following representative circuit: in one direction a Remote Access Server(RAS) sends a digital signal to the Central Office (CO) via T1 lines, at which point the signal is converted via codecand sent from the central office to a modem over a two-wire loop to an analog modem as, at most, a 56k-bit signal.The modem would then send back a typical V.34 signal. A principal point of discussion concerned the placement ofthe attenuation pad(s) used at the central office switch. There seemed to be confusion regarding the appropriateplacement of testing pads for this technology, both for the pad placement on the two-wire analog loop between theCO and the modem, and for the pad on the T1 digital line between the RAS and the CO. The effects of crosstalk andhigh signal levels are included in TR-41.9/97-08-070 and were also discussed. C. Chamney (Sprint) indicatedthat he would be willing to work with the modem manufacturers to conduct test measurements at his test laboratory.

TR-41.9 agreed on the content of a liaison letter responding to the TR-30.1 request. The approved text is as follows:

“TR-41.9 thanks TR-30.1 for your liaison letter regarding the subject of signal power levels for PCM modems. It isobvious that a great amount of thought and effort has been spent in the preparation of the attached contribution toyour letter, and we appreciate the opportunity to share this information.

“After lengthy discussions at our meetings on August 19-20, 1997, TR-41.9 has the following responses to yourtwo questions:

1. The reference point for any measurement performed for Part 68 compliance is at the CPE/network interface.2. It was pointed out during the discussion that the network attenuation pads may be digital, analog or any

combination of digital and analog pads, and there is no standard way of implementing this pad among the centraloffice exchange carriers. Given the fact that:

(a) Part 68 jurisdiction is over the CPE and ends at the CPE/network interface point - thus, Part 68requirements are applicable on the CPE side of this point, and not at any point within or after any central officeswitch or equipment

and(b) there is lack of uniformity in the implementation of the network attenuation pads, at the present time,

there is insufficient justification to change this reference point. However, if there is supporting data that willprovide the necessary rationale for the change, TR-41.9 will reconsider this issue. Specifically, TR-41.9 wouldlike to see more details regarding the ability of the PCM modems to properly detect both digital and analog padsin the central office switches, and would like to receive written submissions of supporting test data demonstratingthe effectiveness of this process. Your request in preparing a petition for the modification of the Part 68 Ruleson encoded analog content to permit higher transmit powers than -12 dB is still under consideration.”

TR-41.9 members agreed to review TR-41.9/97-08-070 .



WEB REPORT

TR-41.9/97-05-063 (S. Roleson, Hewlett-Packard) provides web sites relating to disabled access, the 1996Telecom Act, and ADSL, and other transmission technologies.

HAC TASK GROUP

TR-41.9/97-08-064 (FCC) is FCC Docket 97-242 Order on Reconsideration of CC Docket 87-124, containingthe HAC Volume Control Implementation Date. Responding to a Consumer Electronics Manufacturers Associationpetition for reconsideration, the FCC has changed the date for all new telephones manufactured to include a volumecontrol from November 1, 1998 to January 1, 2000.

An apparent conflict exists between the Part 68 registration process and Parts 68.112 and 68.317 of theCommissions Rules as reflected in FCC Report and Order 96-285. Part 68.112 of the FCC Report and Ordersuggests that the FCC has provided an exemption for HAC Volume Control (VC) headsets in the workplace unlessthe employee requires such equipment for the performance of their employment duties. This burden is placed on theemployer and not the manufacturer. Consequently it is implied that the rules allow for the introduction of HAC VCand non-HAC VC headsets into the marketplace. Yet the FCC Part 68 registration process apparently requirescompliance to Part 68.317, the technical specification for HAC VC for both handsets and headsets. Members of theHAC Task Group will request clarification for this item and for any incremental gradient requirements for digitaltelephones from the FCC, most likely by correspondence.

STUTTER DIAL TONE TASK GROUP

TR-41.9/97-08-066 (R. M.Caughern, Industry Canada) is the provisional (until March 1, 1999) requirements forstuttered dial tone equipment. TAPAC has adopted the first seven of the eight requirements in the FCC’s decisionon Alameda’s waiver request for stutter dial tone omitting the requirement for on-hook impedance. A task group wasformed under the Technical Task Force (TTF) to investigate the rational for each requirement and to further examineits applicability to network harm for possible inclusion into CS-03. It was agreed at this meeting that TR-41.9 willwait for the completion of task by the TTF task group and then determine how to advise the FCC for incorporatingthese requirements into the FCC Part 68 Rules thus eliminating the need for a waiver.

PAY PHONE TASK GROUP

TR-41.9/97-08-058 is a list of Bellcore documents relating to pay phone coin chutes. T. Bishop (Bell Atlantic)discussed pay phone operational and toll fraud related technical characteristics and the applicable Part 68 rules. Anumber of operational tests and pay phone technologies were presented in detail and potential problems were brieflydiscussed. Several action items emerged from this Task Group’s activities:

• Review 68.304 Leakage Current Limitations for possible modification.• Review 68.310 Transverse Balance Limitations for possible modification.• Modify Form 730 Application Guide for areas that need clarification.• Modify TSB-31-B for areas that need clarification.

In addition, T. Bishop recommended that these issues be resolved and the interface be added to the matrix in TSB-31-B prior to publication.

SEMINAR TASK GROUP

Following TR-41.9/97-05-035 and TR-41.9/97-05-052 (TR-41.9 Chair), contributions to the May 1997meeting proposing subjects for the 1998 TIA/FCC two day seminar, TR-41.9/97-08-069 (TR-41.9 Chair)contains the 1998 TIA/FCC Seminar agenda, which was approved with some modifications.

TR-41.9 H ANDBOOK ON FCC PART 68 PROJECT

TR-41.9 agreed on a name for the handbook project: “TR-41.9 Responses to Part 68 Questions from the FCC”. Thescope of the project is to fulfill the need for quick reference catalog of TR-41.9 responses to the FCC.

POWER LINE SURGES UPDATE

TR-41.9/97-08-073 (L. Baker, Reltec) contains the proposal from TR-41.7 for Part 68 changes for transversesurge and AC power surges. These proposals are similar to proposals made by C. Tenorio (AT&T) in TR-41.9/95-06-032 and TR-41.9/95-06-034 . The new proposal for the Transverse Surge includes a connectionfrom the Equipment Under Test (EUT) to ground to protect certain classes of product that could have a dielectric



barrier breakdown in the input power transformer. It was mentioned that the added connection to ground couldprovide additional protection for the internal components of the EUT connected to the output of the EUT’s internalpower supply, cause less stress to the dielectric barrier on the Tip (T) and Ring (R) side of the EUT and protectcomponents connected to T and R of the EUT. It was also mentioned that this Transverse Surge may haveperformance requirement characteristics.

A. Wride (CCL) will research the history of this item for the next meeting.

MAKE BUSY UPDATE - FROM CARRIERS

TR-41.9/97-02-004 (D. Moon, General DataComm), describing the need for the Make Busy application on“inward-only” lines, provided the basis for discussion. No additional comments were received since the last TR-41.9meeting. T. Bishop (Bell Atlantic) stated that the proposed requirements as outlined in TR-41.9/97-02-004 arereasonable, and that the carriers around the table are not opposed to them. It was agreed that this consensus would bereported at the FCC Industry Meeting on September 16, when the subject will be presented by D. Moon.

E911 UPDATE

There has been no additional FCC activity on wireline equipment TIA E911 standard TIA-689 was recentlypublished. Work is in progress on an ISDN E911 standard by T1S1.

Anh Wride, CCL

TR-41.10, PRIVATE INTEGRATED SERVICE NETWORK (PISN)

QSIG

The results of ISO discussions were provided to TR-41.10 concerning requirements specified by the ITU Q seriesrecommendations (QSIG) Basic Call and Generic Functions, as well as supplementary services, including name, callcompletion, diversion and message waiting.

TR-41.10/97-08-030 (D. Lockard, TelCon) is an informal survey of eight QSIG users, conducted to ascertaintheir perspectives on QSIG service and features. Although it was recognized that the survey does not constitute astatistically valid sampling, the results do reflect certain trends. The survey was accepted as useful information tomanufacturers for structuring QSIG offerings. (The survey was also presented in the meeting of TR-41.1.)

TR-41.10/97-08-028 and TR-41.10/97-08-029 are ISO/IEC ballots DIS 15771, and DIS 15772respectively, on Additional Network Feature - Common information (ANF-CMN) stage 1, 2, and stage 3. TR-41/97-08-041 contains TR-41.10’s recommendation that the US vote “yes with comment.” The request wasunanimously approved by TR-41.

NATIONAL ISDN

There were no major remaining issues on National Integrated Services Digital Network (N-ISDN), except for the E-911 Enhancement which is being discussed in TR-41.1 and T1S1. Additional information elements may be requiredfor QSIG to support E-911 networking in North America.

PRIVATE NETWORK MOBILITY

TR-41.10 was briefed on the progress of the Mobility Principles and Service Aspects Technical Report, and alsoMobility Services including: location registration, call handling, and authentication. Since the ISO editors of thesedocuments have not released the updated versions, the detail review was postponed until the next TR-41.10 meeting.

BROADBAND

The alignment of QSIG and Private Network to Network Interface (PNNI) is progressing. TR-41.10 discussed theprogress of work in ISO, European Communications Manufacturers Association (ECMA), and the ATM Forum.Both ISO/IEC 13247 B-QSIG (Broadband) Basic call/connection control (TR-41.10/97-08-031©), and Draft StandardECMA-B-QSIG-SAAL (Signaling ATM Adaption Layer),July 1997 (TR-41.10/97-08-033), were recommendedfor “IS” status. These documents will be balloted by ISO very soon. ISO has not identified areas of cooperationwith ITU-T SG 16 and the VTOA (Voice and Telephony Over ATM) Desktop/SAA-AMS (Service Aspects andApplications - Audio/Visual Multimedia Services) group of the ATM Forum. TR-41.10 will monitor their progresson these issues and recommend US positions into ISO.



TR-41.10 reviewed TR-41.10/97-08-027 , the ISO DIS 15773 ballot on Broadband Transit Counter (ANF-TC),and recommended that the US Vote “yes with comments.” TR-41 unanimously approved the recommendation. TheISO voting period ends October 10, 1997.

Mo Zonoun, Nortel



TR-41 PARTIAL MEETING ROSTER, AUGUST 18 – 22, 1997, QUEBEC CITY, CANADA

Chuck Berestecky, Lucent Chair, TR-41John Schick, Nortel Chair, TR-41.1Pierre Adornato, Nortel Chair, TR-41.2Dennis Rittenhouse, Spectrum Sciences Inst. Chair, TR-41.3Jim Romlein, MIS Labs Chair, TR-41.5Peter Murray, Ericsson Chair, TR-41.6Leroy Baker, RELTEC Chair, TR-41.7Paul Kish, Nordx/CDT Chair, TR-41.8Anh Wride, CCL Chair, TR-41.9Mo Zonoun, Nortel Chair, TR-41.10

Bell Atlantic Trone BishopBellcore John BalinskiBellcore Jim BrunssenBellcore R. CookBellcore Charlie SaccoBell South Dennis DeaseCCL Anh WrideCertelecom Labs Inc. David DulmageComdial Corp. John GreenCompaq J. CottrelCortelco Peter MeltonETRI Woo Hyun JangExcel Erica PintoGeneral Datacom Dave MoonGTE Telephone Ops Percy PoolGTE Telephone Ops Harry Van ZandtIndustry Canada Robert CoreyIndustry Canada Jacqueline GreeningIndustry Canada Henry MarITS G. PageITS Erick WrightLucent Technologies Charles BeresteckyLucent Technologies Steve CrosbyLucent Technologies Bill SolerMitel Bob HamiltonMitel John NeedhamMobile Engineering John BipesNEC Paul Weismantel

Nortel Pierre AdornatoNortel Roger BrittNortel Katherine CheungNortel Erik HanssonNortel Dermott KavanaughNortel J. MacFieNortel John SchickNortel Scott TaylorNortel Gary WongNortel Mo ZonounParadyne Inc. P. WalshRELTEC LeRoy BakerRochelle Comm. Heather Poggi-ManisRockwell Semic Sys R. RahaminSiemens BCS Jim SeippelSiemens BCS Tailey TungSNI Innovation Tom RussellSpectrum Sciences Inst Dennis RittenhouseSprint Cliff ChamneyStentor Resource Ctr Efrain GuevaraTelCon Associates Dorothy LockardTelident Martin MoodyThomson Cons. Elec. Don McKinnonThomas Cons. Elect. Clint PinkhamUnderwriters Labs Randy IvansUniden America Corp. Al BaumUS Robotics J. TaylorWyle laboratories Larry Bell

THE CSR LIBRARY

Subscribers may order copies of documents shown in boldface typefrom Communications Standards Review, where not controlled.-e means we have electronic copy only; +e means we have electronicand hard copy available. We have a large library of standards work in process and can helpyou locate other information you may need.



REPORT OF Q19/16, EXTENSION TO EXISTING ITU-T SPEECH CODINGSTANDARDS AT BIT RATES BELOW 16 KBIT/S

SEPTEMBER 2 – 5, 1997, BETHESDA, MDQ19/16 met jointly with Q20/16 and Q21/16. The Q19 Rapporteur is S. Hayashi of NTT Japan([email protected]); the meeting report is AH-19-24 .

ANNEX C TO G.729 - FLOATING POINT IMPLEMENTATION REFERENCES

The draft text of Annex C to G.729 - Floating point implementation references - was approved in SG 16 forDetermination (TD-39(PLEN)) in March 1997. It was agreed that this Determined text is to be subject to Deci-sion at SG 16, January 1998. The rapporteur will shortly send the draft text of Annex C to the ITU-TSB as WhiteContribution.

The test vectors for the Annex C to G.729 was considered to be important. Nevertheless, no contribution wassubmitted to this meeting. The Rapporteur suggested that contributions for the test vectors be submitted.

The ANSI-C source code in electronic form for reference implementation is available through the Rapporteur forcommittee members by request, and with a signed agreement. The request form is currently provided by the Rap-porteur on request, and will be uploaded to ITU-T FTP site.

HIGHER BIT RATE EXTENSION TO G.729

AH-Q19-02 (France Telecom) contains the candidate algorithm submitted by FT/U of Sherbrooke. The high-leveldescription and the qualification test results, AH-Q19-03 (France Telecom), were reviewed. This algorithm wasconsidered to meet all the requirements and recognized to be the only candidate. The T0 point in the schedule isSeptember 1997; the selection/characterization phase has started. The Rapporteur will write a collaborative letter tothe Speech Quality Expert Group (SQEG) chairman asking for the characterization test methodology and testlaboratory as soon as possible.

AH-Q19-14, is the Subjective Qualification Test Plan for Higher Bit Rate than 8 kbit/s Extension to the G.729Speech Codec. Experiments 1, 2 and 3, from the Chairman of SQEG/SG12.

The IPR holder organizations for this candidate algorithm, FT/USH, AT&T, Lucent Technologies, and NTT, all takethe position stated in Item 2.2 of the ITU Patent Policy (reasonable and non-discriminatory licensing). Any otherorganizations believing they have an essential patent to this candidate algorithm are requested to state their patentpolicy.

The schedule for this work is shown here and in Appendix 4 of AH-Q19-24:

T0 + 4 month Approval of characterization test plan by correspondence

PC executable available preparing for laboratory sessionT0 + 6 month (SG) Review of characterization test plan and finalizing

Submission of detailed description of candidate algorithms (C source code for Determination)Complexity estimation with hardware or simulator

T0 + 10 month Submission of proceeded speech material to the listing laboratories

Laboratory session for the characterization testT0 + 15 month Evaluation of the results of the characterization test

Preparation of the complete text for Recommendation

LOWER BIT RATE EXTENSIONS TO G.729

AH-19-24 (Appendix 1) includes the ToR for the 6.4 kbit/s extensions to G.729.

Ericsson (AH-Q19-19) and NTT (AH-Q19-11) submitted candidate algorithms for a 6.4 kbit/s extension to G.729.The high level description and qualification test results, AH-Q19-12 (NTT) and AH-Q19-20 (Ericsson) were re-viewed. AH-Q19-23 from the Rapporteur provides a summary of the scores of the 6.4 kbit/s candidates. Bothalgorithms met all the requirements in Experiment #1 (Absolute Category Rating [ACR] test) and failed at least onein Experiment #2 (pair-wise tests). At least one algorithm met almost all the requirements, and both candidates willgo to the next selection/characterization phase.



AH-Q19-15, is the Subjective Qualification Test Plan for Lower Bit Rate Extension to the G.729 Speech Codec.Experiments 1 and 2, from the Chairman of SQEG/SG12.

Q19/16 felt that the decision of whether the algorithm meets the requirements should be generally consistent withG.729; thus the ACR test results apply and the pair-wise test results will be for information. The generalperformance of G.729 under the same conditions will serve as reference information.

Since all the requirements are not met and two candidates survived the qualification phase, the optimization processwill occur. Ericsson and NTT will cooperate to make a baseline algorithm by November 15, 1997. A more detaileddescription will be disclosed November 15, and any organization that can potentially contribute to the optimizationmay be invited to do so. Those organizations would receive the C-source code of the baseline codec on completing aNon-Disclosure Agreement, the text of which will be ready by November 1, 1997.

If the optimization process prior to November 15 fails, the Fall Back Process will apply and T0 shifts fromSeptember 1997 to the January 1998 meeting of WP3/SG 16. In Appendix 2 of AH-Q19-24 the remainingschedule for this work is shown as:

T0 + 6 month (SG) Review of optimized codec algorithm

Approval of characterization test methodologyFinalizing characterization test plan

T0 + 10 month Speech materials for characterization tests;

Laboratory session for the characterization test.T0 + 15 month Evaluation of the results of the characterization test;

Preparation of the complete text for Recommendation.

The Rapporteur will write a collaborative letter to the SQEG chairman asking for the characterization testmethodology and test laboratory as soon as possible. The necessity of ACR test under background noise conditionswill be noted.

EXTENSION OF G.728 MORE THAN 16 KBIT/S

AH-Q19-24 Annex C contains the requirements and objectives for variable-bit-rate LD-CELP operation mainly forvoice-band data applications in DCME at rates >16 kbit/s

SQEG/SG 12 presented AH-Q19-07, Subjective tests for the characterization of G.728 extension at more that 16kbit/s and its global analysis of the two test laboratories results (NTT AH-Q19-10, in Japanese, and FUB AH-Q19-13, in Italian). This report showed that the proposed extension met all the requirements for speech quality.

SQEG indicated their appreciation of the contribution by the two test laboratories, FUB/ Italy and NTT/Japan. Thisproposed algorithm will be subjected to Determination at the next SG 16 (to be Annex J to G.728) meeting if theVBD (voice band data) capability tests are completed and the requirements are met.

A correspondence group consisting of Rapporteurs C. Neto (COMSAT), I. Shapira (MOC Israel), Y. Naito(Mitsubishi), and L. Brown (Motorola) was organized after the meeting in March 1997 to define the VBD testmethodology. The editor for this group, C. Neto (COMSAT), presented AH-Q19-04, Test plan for non-voiceperformance assessment of a LD-CELP algorithm operating at 40 kbit/s mainly for DCME applications. However,several points need further clarification in the methodology, which will be finalized by correspondence in one month.

MAINTENANCE AND EXTENSION TO CURRENT SPEECH CODING STANDARDS

AH-Q19-01 (France Telecom) points out a problem in G.729-B (G.729 and G.729-A with VAD) implementationunder frame erasure conditions; changes are proposed. It was agreed that the corrigenda and a revising set of C-sourcecode and test vectors be available at the ITU ftp site before formal approval in the WP3/SG 16 meeting. After theformal approval, the corrigenda will be available in the formal report.

An error in Table 5/G.723.1 was reported (AH-Q19-17 from the WP3/16 Chair). It was confirmed that C code iscorrect and takes precedent. This correction will be included in the Implementers Guide planned for the next SG 16meeting.

AH-Q19-06 (University of Catania) reported that a new approach to VAD would improve the performance of G.729-B for mobile applications without harming compatibility; however, this report lacks quality assessment and itsstatus was recognized as informational.



AH-Q19-16, Use of G.729 for speech packetization in RFC 1890 (AT&T and COMSAT), presents the action takenby the volunteer group in WP3/16. It corrects Internet Engineering Task Force RFC 1890 on packetizing the speechcode sequence. Q19/16 approved the document and appreciated the work.

AH-Q19-18 (AT&T, PictureTel) reported that the virtual host laboratory (where the candidate proponents performtheir own testing) used in the wide-band coding question (Q20/16) was efficient and reliable. The Q19/16 experts feltthat this method will be applicable to the standardization process ongoing in Q19/16.

COLLABORATIVE LETTERS

A collaborative letter was drafted to SQEG/SG 12 with the following points:

1) Experts group Q19/16 appreciates SQEG/SG12 presenting the test results and its global analysis of two testlaboratories for the extension of G.728 mainly for DCME. Following the report from SQEG, the proposedextension was recognized to meet all the requirements in speech quality. This proposed algorithm will be subjectto Determination in the next SG 16 meeting if the VBD capability tests are achieved successfully and therequirements are met.

2) Experts group Q19/16 also appreciates SQEG/SG12 elaborating the test methodology for qualification testing ofhigher and lower bit-rate extensions of G.729. SQEG approved these test methodologies after slight correctionsand modifications. There was one candidate for higher rate and two for lower rate that met almost all the re-quirements. The standardization activities for these questions moved on to the selection/characterization phase(T0 started). One proposed codec from FT/USH is the recognized candidate for higher rate extension. As for thelower rate, the baseline codec for optimization will be available by November 15, 1997 after collaboration ofEricsson and NTT.

ACTION: Q19/16 kindly requests the test methodology for characterizing the higher bit-rate extension to G.729 assoon as possible. If such methodology is drafted, it will be circulated through e-mail and be approved by the expertsmeeting on correspondence. The period for this process is estimated to be about two months.

ACTION: Q19/16 also kindly requests the test methodology for characterizing/selecting the lower bit-rate extensionto G.729 as soon as possible. If such methodology is drafted, it will be circulated through e-mail and will be ap-proved by the experts meeting members on correspondence. The period for this process is estimated to be about twomonths. If the baseline codec is available by November 15, the characterization test will take place afteroptimization; otherwise the selection test will take place after the January 1998 meeting, including other proposedcodecs. The number of candidates is not yet clear.

SQEG agreed that the terms of reference of the lower rate extension will remain unchanged for the time being, butwhether the requirements are met should be carefully considered for conditions under background noise. The decisionmust comply with G.729 generally and the ACR method. The DCR (Degradation Category Rating) tests will beused for analysis and information.

ACTION: Q19/16 also kindly requests SQEG/SG12 to perform the test experiments for higher and lower extensions.If the result is not positive, Q19/16 must query SG 16 laboratories. The test laboratory session will be scheduled sothat the results are available for the January 1998 meeting.

NEAR TERM SCHEDULE (TENTATIVE)

Dates Host /Place Detai led agenda items15 Oct 97 Correspondence Finalizing the test methodology for VBD tests for LD-CELP extension >16 kbit/s1 Nov 97 Correspondence NDA text available for optimization for 6.4 kbit/s extension to G.729 by Ericsson and NTT15 Nov 97 Correspondence 1. Baseline codec description and C-source code on NDA available

2. Draft text of characterization test methodology for higher and lower rate extensions toG.729

End ofJanuary1998

ITU Geneva 1. Reviewing optimized algorithm and characterization test methodology for lower bit rateextension to G.729

2. Reviewing detailed description and characterization test methodology for higher rateextension to G.729

3. Reviewing VBD capability tests for LD-CELP extension >16 kbit/s4. Approval of Annex C to G.7295. Test vectors for Annex C.6. Maintenance of current speech coding standards

Shinji Hayashi, NTT/Japan



SG 16 MULTIMEDIA, WP1 & 2 AND RAPPORTEUR MEETINGSSEPTEMBER 4 – 12, 1997, SUNRIVER, OR

Rapporteurs meetings were held September 4-11 for ten of the 23 Questions of Study Group 16, Multimedia. Ajoint Working Party 1/16 and 2/16 meeting was held on September 12. The purpose of the joint WP meeting wasto Determine various draft Recommendations, and to approve liaison statements. The Determined documents arelisted in Table 1. Please see the Rapporteur meeting reports below for details.

TD Q TitleTD9 Q3 T.120 Annex C, Lightweight Profile for T.120TD10 Q3 T.122 Revised, MCS Service DefinitionTD11 Q3 T.125 Revised, Multipoint Communication Service Protocol SpecificationTD40 Q4 V.8 Revised, Procedures for Starting Sessions of Data Transmission over the

PSTNTD26 Q9 T.140, Text Conversation Protocol for Multimedia Application (formerly

known as V.Chat)TD27 Q9 V.18 Revised, Operational and Interworking Requirements for DCEs Operating

in the Text Telephone ModeTD29 Q9 T.Chat, Text Chat Application ProtocolTD20 Q11 H.324 Annex E, Initialisation of Acknowledgement Timer T401 to Allow

Operation Over Geostationary Satellite ChannelsTD21 Q11 H.324 Annex D, Operation on ISDN Circuits (previously H.324/I)TD35 Q11 H.223 Annex A, Multiplexing Protocol for Low Bitrate Mobile Multimedia

Communication Level 1TD36 Q11 H.223 Annex B, Multiplexing Protocol for Low Bitrate Mobile Multimedia

Communication Level 2TD37 Q11 H.223 Annex C, Multiplexing Protocol for Low Bitrate Mobile Multimedia

Communication Level 3TD38 Q11 H.324 Annex C, MultimediaTelephone Terminals over Error Prone Channels

Table 1. Draft Recommendations Determined at the WP1 & 2/16 MeetingSeptember 12, 1997.

Q3/16 , DATA PROTOCOLS FOR MULTIMEDIA CONFERENCING

The FTP site (ftp://ftp.imtc-files.org/imtc-site) contains the latest version of all T.120 series drafts. The documentsfrom this meeting are in the t120_sunriver97 subdirectory. For more information, see http://www.imtc.org/imtc.

DETERMINATION OF TEXT TELEPHONY APPLICATION PROTOCOL (T.CHAT)

A joint meeting was held with Q9/16, Multimedia Aspects of Special Interest to People With Disabilities.T120C-175 , Text Chatting Presentation Protocol - V.Chat (G. Hellström, Omnitor, Rapporteur Q9), is the draftof V.Chat; it contains the draft text conversation protocol suitable for text conversation in multimedia services.Points prompting discussion and clarification included unsupported request, erase last character, new line, designatecharacter set, and select graphic rendition. The editor will fold in the comments and re-issue a refined V.Chat.

T120C-185 , Proposed Modifications to H.245 for V.Chat (G. Hellström, Omnitor), contains a small change toH.245 to allow V.Chat to run directly in a H.245 logical channel. There was a request for additional semanticdiscussion of this new feature before inclusion into the relevant H.245/H.323 recommendation.

T120C-174 (G. Hellström, Omnitor), Text Chat Application Protocol - T.Chat, the current draft of T.Chat,proposes a protocol that supports the multipoint text conversation defined in V.chat. Reference to V.Chat was addedto the summary and scope of this document. The Abstract Symbol Notation-1 (ASN-1) is being studied forcompleteness. The current document clearly specifies the intent of T.Chat. Off line compilation of the ASN-1 willbe completed as soon as possible. Both T.Chat (TD-29)and V.Chat (T.140, TD-26) were approved forDetermination at the WP2/16 meeting.



DETERMINATION OF T.120 ANNEX C (T.LITE)

T.Lite has been re-drafted as Annex C to T.120. The intent of T.Lite is to provide a lightweight T.120 profilewhich can be implemented in products which require minimal data services such as pure audiovisual environmentsand text telephony. This draft is available in T120C-171 (B. Pulito, DataBeam), T.120 Annex c - LightweightProfile for T.120. The draft was approved by WP2/16 for Determination as TD-9.

DETERMINATION OF T.122 REV

T120C-172© (P. Murphy, DataBeam) contains the Multi-point Communication Services (MCS) Definition (T.122Revised). No changes were recommended to this draft of T.122rev which is an output of the July 1997 Q3/16meeting. It was approved by WP2/16 for Determination as TD-10 .

DETERMINATION OF T.125 REV

T120C-173© (P. Murphy, DataBeam) contains Multipoint Communication Service Protocol - T.125 (Revised). Nochanges were recommended to this draft of T.125rev which is an output of the July Q3/16 meeting. This draft wasapproved by WP2/16 for Determination as TD-11 .

RESERVATIONS

Discussion regarding the work plan for the inclusion of T.Res.2 and T.Res.3 into T.135, User to ReservationSystem Interface (T.Res.1) was held. No technical changes to the Determined T.135 were made at this meeting.

T.120/H.SERIES HARMONIZATION

T120C-183 (J. Ott, TELES AG) contains the meeting report on the second meeting of the InternationalMultimedia Teleconferencing Consortium (IMTC) Ad-Hoc Group on Harmonization of Conferencing Protocols. Itssummary includes the following:• Comments on the non-viability of the H.Unified approach• Recommendation of H-series examination of registry, collapsing capability sets, and upgrade strategy• Suggestions for short term ways to harmonize combined T.120/H.3xx conferences within the existing model (to

be reconsidered by Q14)• A philosophical statement on support which opposes the approval of T.13x• A strategy for Remote Device Control by separating it from the T.130 draft.The report also notes that continuing development with separate H.245/H.225.0 control for audio and video, andT.120 control for data is the only immediate path forward. T120C-184 (D. Skran, Ascend) comments on thereport, noting the need to support very simple terminals such as a telephone, as well as the desire to see a “true nextgeneration H-series terminal”. T120C-184 does not agreed that these requirements were met by the ad-hoc group.

Q3/16 believes many references to T.120 in the reports should more appropriately refer to T.124. Q3/16 does notendorse the conclusions of this report.

J o i n t M e e t i n g o f Q 3 / 1 6 , Q 1 2 / 1 6 , Q 1 3 / 1 6 , Q 1 4 / 1 6

The joint meeting of Q3/16, Q12/16, Q13/16, Q14/16 reviewed the following documents:

T120C-183 (J. Ott, TELES AG) contains the IMTC meeting report on Harmonization of Conferencing Protocols,as discussed above.

T120C-186 (A. Franklin, G. Freundlich, Lucent, same as APC-1309) in section 4 proposes changes to Section6 in H.323v2, attempting to clarify the procedure of adding T.120 as a H.245 logical channel in H.323. It waswithdrawn.

T120C-187 (BT), TD-10, AVC Harmonization Proposal, contains a harmonization proposal for Audio VideoControl. This proposal suggests that Audio Video Control, in both T.120 and H.245, be supported with the en-abling/disabling of each to allow full selection. A fall back position, which suggests a moratorium on all AudioVideo Control functionality in Q16/WP2/16, was also presented. The joint meeting decided to recommend that allfuture Audio Visual Control work be done in Q14/16. This includes T.130, T.131 and T.132. This was later agreedby WP2/16.

T120C-176 (B. Quinn, DataBeam) discusses coordination of H.323 and T.120 Conferences, addressing severalproblems regarding co-operation of H.323/T.120. The problems include:• Communication of T.120 capabilities,



• Call scenario (H.323 leading T.120),• Opening of T.120 data channel,• Establishment of T.120 conference name,• Disconnects.A revision of the contribution was produced and approved within the joint Q3/13/14 meeting. Text changes insection 9 of that document pertinent to T.120 are to be incorporated into the T.120 Implementers Guide.

DMIF

T120C-188 (Nortel) provides an overview and discusses the status of Delivery Multimedia Integration Framework(DMIF). DMIF (draft ISO/IEC 14496-6) is an outgrowth from DAVIC work proposing transparent control interfaceand procedures for the delivery of MPEG streams irrespective of the source site. The contribution also contains adraft of DMIF Implementation on Local Area Networks which provide a non-guaranteed quality of service. Thisimplementation consists of draft changes to H-series recommendations. No changes to T.120 series were proposed.

The following documents contain additional information regarding the DMIF work: T120C-180 (V. Balabanian,Nortel), Proposed Liaison between DMIF and SG 16; T120C-181 (R. Koenen, DMIF) Overview of the MPEG-4Standard; and T120C-182© (DMIF) ISO/IEC 14496 Part 6, DMIF. The overview of MPEG-4 and ISO/IEC 14496-6 DIF working document can be found on the MPEG home page http://drogo.cselt.it/mpeg/.

T.SECURITY

T120C-179 (P. Galvin, DataBeam) discusses T.120 Security Requirements. The contribution was presented atQ14/16 security meeting. Q3/16 will review the result of the Q14/16 discussions at the next Q3/16 meeting.

WORK PLAN

DraftRecommendation

SG 163/97

WP1&29/97

SG 161/98

T.122 revision - d DT.124 revision d - DT.125 revision d r DT.126 revision D - -T.128 d - DT.130 r - -T.131 - - -T.132 r - -T.135 d - DT.Lite(T.120 AnnexC)

- d D

T.CHAT (Q9) - d DT.MCS2 - - -T120 Security - - -

d = Determine, r = re-Determine, D = DecideAt the WP2 meeting in Sunriver, September 12, 1997 all three drafts for Determination were approved.

Q3/16 ELECTRONIC DOCUMENT DISTRIBUTION

Members are asked to distribute papers electronically for review one week in advance of a meeting to the designatedsubdirectory of ftp://ftp.imtc-files.org/imtc-site. Availability of the files should be announced by e-mail. Documentnumbers are assigned and planned dates of attendance are recorded by an automated script athttp://www.k1om.com/imtcftp.html. New drafts should have their revision date hard-coded, so that it will print thesame for all members. The next subdirectory will be t120_geneva98.

Electronic mail should be sent to members via the reflector at [email protected]. Correspondents shouldidentify themselves in the body of messages sent, since header lines showing the source do not always survive. Forinstructions to join this mailing list, send e-mail to t120-interest-request @world.std.com.

Q4/16, V.8BIS

The primary purpose of the Q4/16 meeting was to prepare a revision of V.8 for Determination at the WP1/16meeting on September 12.



V.8/V.8BIS IMPLEMENTOR’S GUIDE

Q4/16 reviewed COM-16-21, the V.8bis/V.8 Implementors Guide, and V8bis-13 , the corrigendum to theImplementors Guide. Q4/16 agreed to remove all of the material pertaining to V.8, which will be incorporated intothe revision of V.8 up for Determination. Q4/16 then agreed to prepare a revised V.8bis Implementors Guide forapproval at the January 1998 SG 16 meeting.

V.8 REVISIONS

B. O’Mahony (acting editor, Intel) presented V8bis-14 , draft revised Recommendation V.8. At the request of theQ23/16 Rapporteur group, changes to support V.pcm were then added to the draft. Q4/16 reviewed the draft page bypage and cleaned it up editorially. Finally, Q4/16 agreed to forward the revised draft to WP1/16 for Determination.The cleaned up draft is contained in TD-40 , presented at the WP1/16 meeting, September 12, where it wasDetermined.

Reporter’s Note: The draft was revised further as a result of discussions at the WP1/16 meeting and updated to TD-40R1. This will be given the number V8bis-15 and brought to the next Rapporteur meeting for information.

REDUCED INTERNET ACCESS TIME

S. Petrack (VocalTec Communications) presented V8bis-12 , a contribution from the State of Israel proposing toinitiate work in the V.8bis Rapporteur group on means to reduce Internet access time. It was the feeling of thegroup that the scope of this work goes well beyond that of the V.8bis Rapporteur group; it was agreed that thissubject needed to be addressed at the WP1/16 meeting before proceeding further.

Editor’s note: At the WP1/16 meeting, it was agreed to hold a separate meeting during the January 1998 SG 16meeting to discuss the reduction of Internet access time.

OUTGOING LIAISON

G. Griffith (Rockwell) was given the task of drafting a liaison in reply to V8bis-03 , the liaison from SG 8 thatwas presented at the last V.8bis Rapporteur group meeting. This liaison notes that SG 8 desires to retain controlover the issuance of codepoints used in its recommendations and therefore is supporting the new draftrecommendation T.codes. The text of the response liaison from SG 16, supporting the requests of SG 8, iscontained in TD-15 , presented at the WP1/16 meeting, September 12.

Reporter’s Note: This liaison was approved by WP1/16 with minor modification and updated to TD-15R1. It willbe given the number V8bis-16, and brought to the next Rapporteur meeting for information.

Les Brown, Motorola ISG

QUESTION 7/16 RAPPORTEURS MEETING, DCE/DCE PROTOCOLS,

The Q7/16 Rapporteur is F. Lucas (General DataComm).

V.VOICE ENHANCEMENTS

The primary purpose of this Rapporteurs meeting was to “clean up” the draft V.voice Recommendation (based onTIA-695, termed FCLASS 8.0) which had been Determined at the March 1997 Study Group 16 meeting. At theJuly 11 Q7/16 Rapporteurs meeting in Dublin, Ireland, Microsoft and Rockwell had presented contributions whichdescribed deficiencies they had found in V.voice as they were implementing the Recommendation. The primary areaof concern was with the lack of a complex report for the SIT Tone (Special Information Tone) and CIDCW (CallerID, Caller Waiting) events. The Rapporteurs group accepted this recommendation at Dublin. The specific wordingfor inclusion in V.voice was provided by Microsoft and Rockwell in Q0797014 , “Proposed SIT and CIDCWclarification to draft recommendation V.voice”. With a change from referring to SITT and SIT Tone to SIT Signal,the proposed wording was adopted.

During the discussion of CIDCW, it was observed that the +VCID command enables/ disables Caller ID, however acommand is not provided in V.25ter to enable/disable the Call Waiting function. It was pointed out thatFCLASS=8.0 does contain a bit mask for the function. It was agreed that a note should be added to the section on+VCID of V.voice specifically indicating that the command does not have an effect on CIDCW.



A second V.voice issue which had been raised at the July 11 meeting by Microsoft and Rockwell dealt with StutteredDial Tone. At that meeting a proposal from the two companies was not accepted since it did not address stuttereddial tones which were continuous or international tones. Q0797015 , “Proposed Stuttered Dial Tone Edits to draftRecommendation V.voice”, was presented to this meeting by Microsoft and Rockwell. The paper addresses thecontinuous stuttered dial tone issue, however it once again only addressed the North American market. It waspointed out that ETSI ETS 300 001, Section 1.7, provides a listing of dial tone characteristics from some 22countries. It was suggested that the proponents of this change make use of this information in future contributionswhich address the worldwide use of stuttered dial tone. In addition, if such a change is incorporated into V.voice inthe future, it was suggested that the information regarding specific dial tone characteristics from various countries beincluded in an informative Appendix to the Recommendation. The group did agree that a note should be added to the+VDT command in V.voice indicating that Stuttered Dial Tone is for further study.

The third issue for consideration in V.voice was a proposal from Microsoft and Rockwell, originally presented at theJuly 11 meeting, for the addition of duplex voice commands. The Q7/16 collaborators did not have a thoroughunderstanding of the need for these commands at the July 11 meeting and requested that the authors of thecontribution (who were not in attendance July 11) attend the Sunriver meeting to provide additional explanation. J.Decuir (Microsoft) and C. Sneed (Rockwell) attended and provided two documents: Q0797013 , Proposed voiceduplex operation to draft recommendation V.voice, and Q0797016 , Commentary on Q0797013, Proposed voiceduplex operation to draft recommendation V.voice. Q0797013 contains specific changes proposed for V.voicewhich include informative information. Q0797016 was provided after the initial presentation of Q0797013 todocument background information. Although the group agreed that there is a need for these commands, many of theattendees were not comfortable with adopting the specific wording without time to fully study it. It was agreed toinclude a “for further study” note in V.voice and attach Q0797013 to the meeting report. The United States wasencouraged to submit to Study Group 16 in January 1998 a contribution which recommends the specific addition ofthese changes. This will be worked on at the next TR-30.2 meeting on Friday, October 17 in Galveston, TX.

V.25TER ENHANCEMENTS AND V.25TER SUPPLEMENT

The first draft of the revision of the V.25ter (Serial Asynchronous Automatic Dialing and Control) Supplement(Q0797009) was provided by the editor, F. Lucas (General DataComm). This draft includes the GSM commandsprovided at the July 11 meeting as well as additional commands included in V.25ter from the March 1997 StudyGroup 16 plenary. The editor pointed out that commands from V.voice and V.25ter/Annex B had yet to be included.Q0797011 , Proposed additions to V.25ter and Supplement to V.25ter (J. Moughton, Hayes), proposes that asection on dial modifiers be added to the Supplement. In addition, the contribution indicates that V.25ter makes useof the “S” dial modifier in the +ASTO command, yet the modifier is not specified in section 6.3.1/V.25ter.Proposed text for the omission is provided. Additionally, text is suggested for a new dial modifier, “$” (wait forcalling card prompt). Additional study on the “$” modifier is needed regarding the universal availability of thesymbol on keyboards.

ISDN TA COMMANDS

Two contributions list the V.25ter type commands found in a number of existing ISDN Terminal Adapters:Q0797012 , Requirements for the Control and configuration of ISDN Terminal Adapters Using V.25ter Type Com-mands (R.R. Damm, Deutsche Telekom), and Q0797010 , Summary of AT commands used by selected ISDNTerminal Adapters (J. Moughton, Hayes, Rapporteur for Q5/16). Both authors had researched Terminal Adaptersfound in their countries, Germany and the United Kingdom respectively, and listed the commands. These paperscertainly show the need for a Recommendation. J. Moughton indicated that he will provide a list of what he feelsshould be the commands needed in such a Recommendation. In addition, the group gave tentative approval for theuse of “N” as the command prefix for the ISDN TA set of commands.

OTHER BUSINESS

W. Pechey (Hayes) noted that ETSI SMG 4 was initiating work on a multiplexer function for use across theDTE/DCE interface in the GSM Mobile phone. This group works very quickly and an ETSI standard could beapproved as early as December 1997. W. Pechey will keep Q7/16 informed of this work.

Fred Lucas, General DataComm

Q9/16, ACCESSIBILITY TO MULTIMEDIA FOR PEOPLE WITH DISABILITIES

Q9/16, Accessibility to multimedia for people with disabilities, made the following progress in their meeting:



• The text telephone modem Recommendation V.18 was revised, based on practical experience, support for plainMinitel and Prestel (V.23) was added. V.18 was Determined (TD-27).

• V.18 test specification was discussed based on a proposal from BT. Work will continue.• A text chat presentation protocol for common use in many multimedia environments was accepted for

Determination and allocated Recommendation number T.140.• A text chat application entity in the T.120 environment was accepted for Determination by Q3/16, and given the

Recommendation number T.134.• Modifications to the circuit switched videophone protocol H.324 and its control protocol H.245 was made in

collaboration with Q11/16 to accommodate for the text chat protocol T.140 in that environment.• A similar work item was started in Q13/16 and Q14/16 to accomodate the addition of T.140 text chatting to the

H.323 videophone protocol for the packet switched environment.• A first draft of an appendix to the video coding Recommendation H.263 about needs and optimization for sign

language and lip reading transmission was presented to Q15/16. A The goals of H.263L were amended.• It was agreed to have a rapporteur’s meeting in Europe late 1998.

The documents from the meeting are available at http://www.pi.se/~omnitor/standd.htm.Q9 issues are discussed in the reflector [email protected].

V.18, AUTOMODING PROCEDURES FOR A MODEM WORKING IN THE TEXT TELEPHONE MODE

Revision proposals for the main body of V.18 from UK were presented and accepted. They are based on labexperience and enhance interworking.

Q09A-05 (UK) is the latest version of the proposed revision of V.18. For the most part, these changes addressedthe removal of the direct tie of V.23 to Minitel. It was decided to convene a small editing group to clear up some ofthe ambiguities in these new proposals.

Q09A-04 (UK) notes a number of editorial changes resulting from continued testing of V.18 at BT labs.

Q09A-07 (BT) proposes an additional burst of 3s of 1300 Hz followed by 1 s of silence between sets of 3 CallIndicator (CI) sequences be added to the calling tone to “wake up” V.23 text telephones.

There was considerable discussion about the penalty of 4 s to the startup. It was decided to include this text but toalso continue testing both on this proposal as well as other possible modifications.

Q09-A-06 (BT) proposes that an Annex be added to V.18 which specifies V.18 Implementation Tests. The groupagreed to work to establish a test specification as a separate document or an appendix to V.18. It was clarified thatthis contribution was developed in anticipation of possible homologation requirements on text telephones. It wasdecided to keep this document under consideration although where it might end up was unclear (appendix, handbook,etc.) .

Q09A-10 (G. Hellström, Omnitor) proposes changes to V.18 to incorporate the proposal in Q09-07 (BT). Thisrevision proposal from Sweden cleans up the structure and refers to T.140 (V.Chat) for the upper layers using V.18.Q09A-15 (G. Minier, France Telecom) is a proposal from France for a way to support “Minitels” in V.18.Specifically it proposes that 2s bursts of 1300 Hz be inserted between the CI signals. It was decided that the BTproposal for handling this same condition, discussed in Q09A-07 (BT) offered a less intrusive solution.

Proposals from France Telecom and BT to incorporate support for calling plain Minitel and Prestel terminals wereaccepted backed by lab results from BT, and merged into the text of V.18. The revised V.18 was Determined asTD-27 in the WP1/16 meeting. A. Farquharson (BT) is the editor.

Q09A-14 (G. Hellström, Omnitor) is a liaison from Q17/2 offering to cooperate on the development of a servicedescription for “Accessibility to Multimedia for People with Disabilities.”

T.140 TEXT CONVERSATION PROTOCOL FOR MULTIMEDIA APPLICATION (“V.CHAT”)

The simple text conversation protocol T.140 intended to suit real time text chatting purposes together with videotelephony, text telephony and data conferencing was presented. It was called V.Chat during development. It is basedon character-by-character transmission and presentation of 16 bit coded ISO 10646 characters and a small selection ofISO 6429 control. The grouping of functions in a LIGHT and an ENHANCED level was modified slightly. Anyuse of T.140 must specify the transport mechanisms provided for that application.



Q09A-03 (G. Hellström, Omnitor) proposes a presentation level protocol for CHAT sessions: an ITU-T V.ChatRecommendation. The basic concept of this proposed Recommendation was accepted. It was decided to work off-line to edit the final version of this document.

Q9/16 agreed to the following changes:

• A command will be added to indicate the presence of a multipoint session which would have the effect ofsuppressing the “unsupported request” messages.

• The Protocol Identity, Protocol Version and Profile will be added to V.Chat• A “resend all “ command will be provided• Redundant sending of the protocol items when bandwidth is available will be provided.• During a point-to-point session require that the “unsupported request” be sent whenever the receiving terminal is

unable to comply with a requested action.

The resulting proposal, TD-26 , was Determined in the WP1/16 meeting.

TEXT CONVERSATION IN CIRCUIT SWITCHED VIDEOPHONE PROTOCOLS (“H.CHAT”)

A proposal for small additions to Recommendations H.324 and H.245 to incorporate use of T.140 for textconversation in H.324 videophones was discussed with Q11/16. Q09A-08 (M. Nasiri, Ericsson) proposesadditions to H.245 to allow for the use of V.Chat on an H.245 logical channel between to H.324 terminals. It alsoproposes the use of V.14 as the link layer.

A simple AL1 (H.223 Adaption Layer 1 logical channel for transmission of T.140 is allocated by H.245. A rule forthe case when T.140 is supported both through this mechanism and through T.120 protocols was stated. The re-sulting modifications go into H.324 and H.245 and will be handled by Q11/16 and Q14/16.

Due to the acceptance of the proposal to include the protocol and profile negotiation within V.Chat this facility wasremoved from H.Chat. It was decided that Determination not be proposed until the January 1998 meeting to allowmore time to assess the appropriate ways to accommodate V.Chat in H.324.

T.134 TEXT CHAT APPLICATION ENTITY IN THE T.120 ENVIRONMENT (“T.CHAT”)

Q09A-09 (G. Hellström, Omnitor) proposes a protocol for Multipoint text sessions referred to as T.Chat. Theproposal for a simple Application Entity in the T.120 data conferencing environment was discussed jointly withQ3/16. It provides multipoint all-to-all text conversation based on the T.140 text conversation presentationprotocol. It uses only T.120 features contained in the light profile of T.120 Annex C. The application intended isperson-to-person text conversation and multipoint discussion and subtitling in video conferences and dataconferences. It was agreed to add references to V.Chat at appropriate places in the document (including the diagrams).References to T.Lite were replaced by the appropriate Recommendation number. The need to correct the ASN-1notation was identified. The profile negotiation information was removed.

The T.134 (T.Chat) proposal in TD-29 was Determined with the remark that the ASN.1 part needs verification. Itwas agreed to implement and test it logically prior to its approval next year.

There was considerable discussion about the use of UNIFORM SEND DATA rather than SEND DATA.UNIFORM SEND DATA assures that all terminals would receive the same data at the same time. In this case datawould appear line-by-line rather than character-by-character.

Q15/16 SESSION ON SIGN LANGUAGE AND LIP READING OVER VIDEOPHONE

Video telephony can be an important step to equal opportunities for people who need sign language or lip reading fortheir communication. But performance of products has seldom taken that into account. In collaboration withQ15/16, an appendix to H.263 video coding was drafted, describing the needs for sign language and lip readingperception, and outlining optimization and test methods for this application. Q09A-11 (G. Hellström, Omnitor) isthe draft of Proposed Appendix “S” to Recommendation H.263 to address sign language and lip-reading. Usabilitystarts at 12-15 frames per second in QCIF mode and max 0.8 seconds delay, while good performance is experiencedwith 25-30 frames per second in CIF mode and max 0.4 seconds delay.

There was a discussion of using higher frame rates (presumably higher bit rates) in testing in H.263. It was pointedout was that the quality was probably more dependent on the implementation than the ability to respond to theoptions requested and that the quality of the implementation was not under the control of the ITU. It was alsopointed out that all options were “optional” in the encoder. In answer to a concern raised about loss of sync between



the picture and sound when “lip reading,” it was also clarified that there are time “tags” associated with both thesound and video and it should be possible to keep these in sync.

Q09A-12 (G. Hellström, Omnitor) proposes similar criteria to be added to the development list for the work onH.263L (new non-backward compatible, enhanced long term video coding work). It was agreed to add theserequirements to the list of considerations.

TEXT CHATTING IN OTHER MULTIMEDIA TERMINALS

Q09A-16 , a proposal to include T.140 text conversation through a logical H.245 channel in the packet switchedvideophone environment H.323 was presented and accepted as a work item in a joint session with WP1 and WP2.Q13/16 will do the H.323 and H.225 modifications needed and Q14/16 will do the H.245 modifications. The goal isDetermination at the SG 16 meeting in January 1998.

OTHER HIGHLIGHTS

A rapporteurs meeting late 1997 in Europe was asked for and approved in the WP1/WP2 meeting. The purpose willbe to verify the text of the Determined recommendations, to continue with the V.18 test specification and the videocoding appendix.

SG 16 has been appointed responsibility for a part of GII, concerning Multimedia in the IP environment and itsinterworking with the PSTN and ISDN. TD-6 is a report on the Joint Rapporteur Group on the Global InformationInfrastructure describing the GII work assigned to SG 13 and SG 16. In the WP1/WP2 meeting, Q9/16 indicatedinterest in actively participating in this work, especially in service descriptions, with the goal to make sure thatfuture services include that which disabled people need.

Dick Brandt, dB Consulting, with Gunnar Hellström, Omnitor

Q11/16 CIRCUIT-SWITCHED NETWORK MUILTIMEDIA SYSTEMS AND TERMINALS

The Q11/16 report will be published in CSR-T 8.9, November 1997.

Q12/16, Q13/16 AND Q14/16 GENERAL INFORMATION

Many documents in this report are available at: ftp://itu-t:[email protected]/ 9709_Sun/

APC-1327 (same as TD-47) is the report of this Q12/16 Broadband ISDN Multimedia Systems and Terminals,Q13/16 Packet Switched Multimedia Systems and Terminals, and Q14/16 Common Protocols, MCUs and Protocolsfor Interworking with H.300 Series Terminals Rapporteurs meeting.

TD-2(Rapp) (Q12/16, Q13/16, and Q14/16 Rapporteurs) contains a list of the 76 APC-numbered contributionsand 39 Temporary Documents for this meeting.

J. Ott (Teles) reported that the August 1997 Internet Engineering Task Force (IETF) meeting held in Munichaddressed several relevant topics: Real-Time Streaming Protocol (RTSP), session description protocol, H.332(former H.Loosely Coupled) related audiovisual transport protocol, gateway/gatekeeper topics, and security issues.

S. Okubo (GCL) reported on the August 1997 Asynchronous Transfer Mode Forum (ATMF) meeting. So far nocomments were received on H.321 V2, Annex C to H.323, which had been sent from the March 1997 SG 16meeting; reorganization is going in the multimedia area.

J. Ott (Teles) reported on the May 1997 Q3/16 meeting held in Edinburgh, Scotland, focusing on the topic ofconference control and audiovisual control services.

APC-1326 (J. Ott, Teles) contains the report for International Multimedia Teleconferencing Consortium (IMTC)ad-hoc meetings on harmonization of conferencing protocols held in Lexington, KY in July (see CSR-T Vol. 8.7)and August, 1997. The meetings suggested actions to reconsider T.130, and to make Q14/16 responsible forharmonizing audiovisual control work.

APC-1250 (S. Okubo, GCL) is the Digital Audio-Visual Council (DAVIC) call for proposals for Computer FaxProtocol-9 (CFP9) for the IP based system architecture. The Q12/16, Q13/16, and Q14/16 Rapporteurs meeting de-cided to send a correspondence to DAVIC from Q13/16 (TD-24(Rapp), D. Skran, Q13/16 Rapporteur), reporting



that an IP based system H.323 for multimedia conversational services has already been standardized. The text agreedto at the WP 1&2/16 meeting is contained in Annex 3 to APC-1327 , the Rapporteurs report.

Q12/16 B-ISDN M ULTIMEDIA SYSTEMSAND TERMINALS

H.321 VERSION 2, ADAPTATION OF H.320 TO B-ISDN E NVIRONMENTS

APC-1258 (C. Gates, First Virtual) provides the changes to H.321 Version 2 according to the June 1997 Herzliameeting determination. TD-17(Rapp) (C. Gates, First Virtual) is the revised draft Recommendation H.321 Deter-mined during the March 1997 SG 16 meeting in Geneva and edited during the September 1997 Rapporteurs meetingin Sunriver. Changes are with respect to APC-1258.

A general question was raised regarding the timing recovery in the interworking between Annex B (Use of ATMAdaptation Layer Type 5) and H.320. It was clarified this should be part of Network Adaptation Layer (NAL) func-tions and the gateway should also support NAL for the interworking. H. Harasaki (NEC) reported from hisexperience that adaptive clock recovery is implementable but jitter performance needs consideration of particular rateand application.

The Q12/16, Q13/16, and Q14/16 Rapporteurs meeting resolved the three technical notes in APC-1258 as follows:

• GIT (Generic Identifier Transport) codepoint for End Station: A note will be included in the text that thiscodepoint is pending agreement of SG 11.

• Alignment with ATM forum: In the absence of advice, this technical note No. 2 will be deleted.• Notification identifier: Because no advice has been received from SG 11 so far, this issue was not accepted in the

June 1997 interim meeting; it will come from SG 11 in September 1997. If there is any clear information fromSG 11, the Editor can incorporate it in the white contribution, otherwise the SG 11 conclusion will be reflectedin the January 1998 SG 16 meeting.

The Q12/16, Q13/16, and Q14/16 Rapporteurs meeting also agreed to clarify “under study” fields in the Q.2931signaling table as follows:

• Check if they are optional in Q.2931.• Fill out the fields as far as possible.• Include a note stating that a call should be accepted even if optional elements are missing in the SETUP message.

FEC - Forward Error CorrectorAPC-1251 (C. Wipliez, France Telecom) proposes an optional use of short interleaver Forward Error Corrector(FEC) in H.321 Version 2. In discussion, the following argument was raised: An optional function needscapability negotiation which should be through outband signaling. If the satellite link is the problem, the FECshould be in the transport layer, not in the terminal. The current I.580 (General arrangements for interworkingbetween B-ISDN and 64 kbit/s based ISDN) does not support FEC. (I.580 can be revised if so proposed.)

Since there was not enough support to accept this proposal, the Q12/16, Q13/16, and Q14/16 Rapporteurs meetingdecided to compromise by changing the current Note 3/Table A.1 not to exclude the use of FEC, and stating the needfor fallback procedures if it is used. The exact wording was left to the work of a small group.

Analog Traffic Channel (ATC)APC-1263 (C. Wipliez, France Telecom) and APC-1322 (J. Blin, France Telecom) proposes the use of DBR(Deterministic Bit Rate) as an ATM Transfer Capability in H.321 V2 to facilitate interconnection through differentnetworks. The Q12/16, Q13/16, and Q14/16 Rapporteurs meeting accepted this proposal, leaving the exact wordingin Draft H.321 V2 to an editing group.

Interface between H.320 and AAL CardAPC-1324 (J. Blin, France Telecom) addresses the enhancement of the X.21bis (Use on public data networks ofData Terminal Equipment (DTE) which is designed for interfacing to synchronous V-Series modems) interface tofacilitate clock synchronization of the H.321 terminal which consists of a separate ATM Adaptive Layer (AAL) cardand an existing H.320 terminal.

J. Blin (France Telecom) clarified that APC-1324 addresses the interface between AAL and H.221 Multiplexer(MUX) in Figure 2/H.321, splitting TE2 into two in Figure 1/H.321. He also clarified that the “Synchronousremote” transfers the information obtained through the new Protocol Discriminator Information Element (IE) forclock source information.



The Q12/16, Q13/16, and Q14/16 Rapporteurs meeting will send correspondence to Q16/16 based on APC-1324 ,seeking their advice.

H.310 VERSION 2, BROADBAND AUDIOVISUAL COMMUNICATIONS SYSTEMS AND TERMINALS

APC-1259© (K. Sakai, Fujitsu) provides an initial draft for H.310 Version 2 by incorporating the content in theImplementers Guide which was approved in March 1997. Two minor typographical errors were found.

APC-1272 (R. Kapoor, AT&T) is a draft liaison from the SG 11 interim meeting in June 1997, accepting the SG16 request of Q.2931 LLI (Lower Layer Information) for AAL indication. H.310 Version 2 should reflect this newcodepoint allocation.

The comment was raised that the Terminal Type includes the H.321 codepoint which had previously been discussedas inappropriate as it was coupled with narrowband parameters. This issue requires the confirmation of SG 11.

H.320/H.321 Interoperat ion Mode of H.310 RAST-5APC-1300 (S. Okubo, GCL) and APC-1314 (BT Labs) propose to correct the H.320/H.321 interoperation modestack of H.310 Receive And Send Terminal-5 (RAST-5).

The group supported this proposal and the proposed changes in the H.310 text, as in the Annex to APC-1300 ,confirming that this correction applies to H.310 Version 1. How to approve this correction (Implementers Guide,Corrigendum, etc.) is subject to consultation with the SG 16 management.

Procedures for Interworking Between RAST-1 and RAST-5APC-1299 (S. Okubo, GCL) proposes a specific text for inclusion in H.310 V2 to describe how interworkingbetween RAST-1 and RAST-5 terminals are achieved through a gateway.

The discussion regarding the open issues resulted in the following:

1) Should B-LLI Indication cover the gateway capability? The Rapporteur’s group felt it awkward to recommendaccepting a call even if AAL mismatch is detected. Based on the assumption that a terminal connected to a CPN(Customer Premise ATM Network) has the knowledge of its associated gateway capability, the group concludedthat a RAST-5 terminal should indicate “RAST-1&5” if it is supported by the AAL1/AAL5 conversion gateway.The mechanism for a terminal to obtain the associated gateway capability is not part of the current specification;it may be manual, it may be automatic.

2) Numbering in B-ISDN. There are three options (E.164, NSAP, private) defined in Q.2931. Whatever option isused, the gateway address as part of the gateway capability follows the Q.2931 coding.

3) Multiple numbers for gateway address. The Rapporteur’s group recognized the necessity of indicating multiplenumbers. M. Nilsson (BT) confirmed that H.245 (Control protocol for multimedia communication) has amechanism to cover this requirement.

With the above enhancements, the group agreed to include the materials in APC-1299 in the next draft of H.310V2 (see Q14/16 report below).

H.310 Communicat ion ModelAPC-1312 (D. Jung, Electronics and Telecommunications Research Institute) discusses the enhancement of H.310interworking scenario as to consideration of uni-directional terminals, provision of gateway at the service providerand network provider in addition to the customer premises network, and core/access network distinction.

APC-1313 (D. Jung, Electronics and Telecommunications Research Institute) proposes broadcast and distributionservice consideration in H.310 and inclusion of system configuration to cover interactive services.

The following comments were offered on these contributions:• There may be a case in which an access network provider for residential use provides the gateway, but the access

network can be seen as a CPN from the communication model point of view.• H.310 specifies that ROT-5/SOT-5 (Receive and Send Only Terminals with AAL-5 interfaces) can be

accommodated in B-ISDN as well as CPN. The current restriction to RAST-5 came because I.580 is based onAAL1 and RAST is mandated to provide H.321/H.320 interoperation mode.

• DMIF may help the enhancement of the H.310 interworking scenario.• A disagreement was expressed to H.245 supporting SDB (Switched Digital Broadcast) messages. The problem is

that H.245 can be common to different AALs. It was clarified that there is a provision to open a logical channelfor Digital Storage Media - Command and Control (DSM-CC) which can convey SDB messages since all theDSM-CC messages are unique.



It was agreed to instruct the Editor to investigate the current ROT/SOT interworking scenario and add someclarifying text if found necessary. It was further agreed to explore the composite terminal configuration of H.245controlled H.310 terminal and DSM-CC controlled interactive terminal.

H.245 Message Transport StackAPC-1314 (BT Labs) proposes replacement of X.224/Q.922 for the error free transport of H.245 messages withTransmission Control Protocol/Internet Protocol (TCP/IP) in the interest of interworking with H.323.

Some dissenting comments were heard to this proposal:

• T.120 has the X.224/Q.922 stack.• Conversion of the IP address and the ATM address is not clear in this proposal; also how the IP address is given

to the terminal is not clear. T.120 has the same problem.• Optional additions should be considered instead of replacement.• Object to the replacement; the current stack is preferred.• H.310 and H.323 do not have audiovisual elements in common.

Since there was no consensus, the Q12-14/16 Rapporteur’s group did not accept this proposal. They may revisit theissue if further inputs become available.

H.BMULTIPOINT

APC-1260© (H. Harasaki, NEC) presents an initial draft for H.bmultipoint using the materials input to the Junemeeting in Herzlia. This draft Recommendation addresses the system operation for a conference call between three ormore ITU native H.310 terminals.

The handling of H-series terminals other than H.310 was questioned. The Rapporteur’s group agreed to delete “usingH.246 gateways” from the second sentence and to describe in Section 9 (Interoperability with other H-seriesterminals) possibilities such as use of H.246 functions, use of interoperation mode, transcoding, etc. It was alsosuggested to focus on H.320 as a typical case of other H-series terminals.

With the amendment above, the group accepted the proposed scope and structure with confirmation that Version 1should focus on basic multipoint configurations.

The intended time schedule is for Determination in January 1998. The question arose whether SG 16 should hurrygiven the lack of strong market pressure. The Q12-14/16 Rapporteurs clarified that multipoint capability isfundamental, and should have been included in H.310 Version 1 as in H.323. Moreover, the multipoint effort isaimed at completing the H.310 work. A supporting opinion was expressed that ITU-T standardization wouldencourage the manufacturers to make products (a chicken and egg problem).

The following comments were offered to elaborate the H.bmultipoint draft:

• Dynamic Volume Control (VC) change (i.e., between a multicast leaf and a point-to-point party when the currentspeaker switches) may be expensive and suffer noticeable delay. Since VC setup is not designed to work in areal-time fashion. it needs some time (“It could be 1.5-20 seconds” was mentioned).

• Include system configuration of H.bmultipoint Multi-point Control Unit (MCU) as in H.231.• Include reference to service Recommendations such as F.700, F.710, F.720.• Concentrate on multicast by MCU and multicast by the root MCU initiated join.• Editor can use existing texts in H.140, H.231/H.243 (Multipoint control units for audiovisual systems using

digital channels up to 1920 kbit/s / Procedures for establishing communication between three or more audiovisualterminals using digital channels up to 2 Mbit/s) and other related existing Recommendations.

• Tables 1 and 2 for master-slave determination need correction.

Conference ControlAPC-1305 (L. Yan, Lucent) proposes the use of H.243-like procedures for basic configuration of switching videomultipoint, which does not need new H.245 messages. The group agreed to include these procedures in the next draftof H.bmultipoint with corrections and enhancements pointed out as listed below. However, this decision is pendingthe discussion in Q14 regarding the general guidelines for conference control. The following points were made:

• Video switching needs rate matching considering the H.222.0 (Generic coding of moving pictures and associatedaudio information: Systems) overhead, which can be achieved by H.245 FlowControlCommand as specified inSection 8.1/H.310.



• Switching of 27 MHz PCR is another problem associated with the video switching. MCU may have to be slavedto the switched video source.

• Basic multipoint procedures are acceptable, but further advanced controls should follow T/H-series harmonizationin Q14/16.

• VideoFreezePictureReleaseControl is not an H.245 message, it is a part of Video Frame Synchronous C&Isignals defined in Section 6.3.5.3/H.310.

• In case of multicast, ATM VC (virtual channel) may be switched from symmetrical to asymmetrical in bit rate tosave communication charge. However, switching SVC (switched virtual circuit) may take time (see above).

Signal Process ing at MPAPC-1301 (H. Harasaki, NEC) discusses comparison of Technical Specification (TS) level processing andelementary stream level transcoding in Modulation Parameter (MP).

The Q12-14/16 Rapporteur’s group understood that both suggestions were implementation alternatives for MP. Itwas pointed out that restamping the time stamps is required in MP to synchronize audio and video. It was alsoreported that some loss of audio samples was not objectionable in case of MPEG-1 coding.

The next draft of H.bmultipoint will include the following implementation alternatives as information:• Remultiplexing• Transcoding• Use of layered coding• Use of H.320/H.321 interoperation mode.

The Q12-14/16 Rapporteur’s meeting agreed to raise the following requirements to Q15/16 so that we can realizeH.bmultipoint MP:• Low delay transcoding• High quality cascade coding• High quality coding at 3-4 Mbit/s.

The exact wording of these requirements was left to H. Harasaki (NEC) and D. Piercy.

H.222.0 | ISO/IEC 13818-1

APC-1298 (S. Okubo, GCL) proposes the text for Amendments 3 and 4 of H.222.0|ISO/IEC 13818-1. The groupagreed to proceed to a white contribution for Decision in January 1998.

Q13/16 PACKET-SWITCHED MULTIMEDIA SYSTEMS AND TERMINALS

Summary: It was agreed to move the following documents forward for Decision in January 1998:• H.323V2 • H.450.1• H.225.0V2 • H.450.2• H.332 • H.450.3

H.323/H.225.0 V1 I MPLEMENTORS GUIDE

There were no contribution to the H.323 (Visual telephone systems and equipment for local area networks whichprovide a non guaranteed quality of service) and H.225 (Media stream packetization and synchronization on non-guaranteed quality of service LANs) implementors guide.

COORDINATION

APC-1250 (S. Okubo, GCL) requests submissions on IP systems to the Digital Audio-Visual Council (DAVIC).TD-24(Rapp) (Q13/16 Rapporteur) contains a letter to DAVIC concerning the status and progress of H.323, andasks that H.323 be considered in this work.

APC-1268 (V. Balabanian, Nortel) contains a proposed liaison between ITU-T SG 16 and Delivery MultimediaIntegration Framework (DMIF).

APC-1269 (R. Koenen) contains an overview of MPEG-4.

APC-1270© (ISO) contains working draft 1.0 of DMIF (draft ISO/IEC 14496-6).

TD-22(Rapp) includes a presentation (Z. Lifshitz, VDOnet) on putting H.323/H.310 into DMIF, and draftAnnexes B & D of DMIF implementing this approach. The contribution was considered informative but was notaccepted as the basis of on-going work.



The Q12-14/16 Rapporteur’s group approved a liaison to ISO MPEG-4, contained in TD-21rev3(Rapp) (G.Thom, Delta Information Systems), attached to APC-1327 . It notes that SG 16 envisions the creation of ITU-Tdocuments in the form of annexes to both H.323 and H.310 that would specify how these systems would work in aDMIF environment. It also notes that SG 16 is interested in specifying MPEG-4 components (e.g., audio and videocodecs) within basic H.323/H.310 systems (see also the Q14 report below).

H.323 V2

APC-1255 (G. Thom, Delta Information Systems) is the current draft of H.323 V2. TD-30(Rapp) (G. Thom,Delta Information Systems) provides a summary of changes.

DTMF RelatedAPC-1265 (D. Skran, Ascend) proposes a frame work for Dual Tone Multi Frequency (DTMF) work using H.245as the base technology, and support of APC-1262 as base text. Concern was raised about whether H.245 DTMFwould be secure.

APC-1262 (T. Nixon, Microsoft) proposes to update APC-1234 (T. Nixon, Microsoft) with subsequent input,and provides a detailed plan for using H.245 to communicate a full range of DTMF tones with time stamps forassociating the tones with audio. An issue was raised that in some cases it was desirable to disable hook-flash.Some concern was raised about the possible lack of synchronization with incoming audio/video. A request was madeto add procedures in H.323 for interworking between V1 and V2 terminals. It was noted that Multi-tone Frequency(MF) signaling is not needed since it is not used end-to-end; DTMF is end-to-end.

APC-1277 (S. Petrack, VocalTec) discusses DTMF signaling within H.245, and proposes a number of changes toAPC-1262 .

It was agreed to merge hook-flash with the DTMF field, and call it something else. The sequence number of APC-1277 was not accepted. The “reference” item of APC-1277 will be removed in favor of using RTP information.Specific text changes to H.245 were developed in an small ad hoc group and appear in TD-8(Rapp) (T. Nixon,Microsoft).

Faster Call setupAPC-1286 (P. Cordell, BT Labs) proposes a new method of fast call setup that transports H.245 messages in theH323-UserInformation field of Q.931 UUIE (user-to-user information element) SETUP message.

APC-1306 (J. Toga, Intel) is a combination of proposals on fast connect sequence for H.323 considered at Herzliain June. APC-1306 was accepted, and J. Toga (Intel) will supply supporting H.323 text to the Editor.

QOS relatedAPC-1302 (H. Salama, Cisco) discusses Quality of Service (QoS) Control in H.323 Version 2 using ResourceReservation Protocol (RSVP), and proposes some additional signaling in H.323 to inform the GateKeeper (GK) thatthe terminal can make its own reservations. The contribution also specifies in more detail the way in which theterminal can request resources using RSVP. Section 1 of APC-1309 (A. Franklin, Lucent), containing commentson H.323, was presented. TD-23(Rapp) (H. Salama, Cisco) contains changes and text added to H.323 as aninformative appendix.

APC-1308 (Y. Choi and S. Kim, Korea Telecom) discusses the necessity of standardization on reliable multicastprotocol, as well as RSVP and various QoS related matters. The Rapporteur recommended that the contribution beconsidered for future development of H.323.

Call Progress Tracing and AccountingAPC-1264 (D. Skran, Ascend) discusses proposals for more accurate call information in the direct call modelincluding the following: that an IRR (H.225 status request message, InfoRequestResponse) be sent to theGatekeeper on reception of CONNECT, and that CONNECT be valid end-to-end.

APC-1282 (L. Moscovici and S. Petrack, VocalTec) discusses announcement of a Q.931 message within an IRR,and calls for a more flexible method where the Gatekeeper will request a list of messages on which an IRR is to besent.

The major issues raised in discussion were: (1) Lack of end-to-end connect may cause interoperability and callaccounting problems and (2) Once connect arrives, the lack of a common coder may cause call failure.

TD-28(Rapp) (S. Petrack, VocalTec), a unified proposal correcting these difficulties, was adopted. Item (1) inTD-28(Rapp) was approved in a modified form with the “shall” changed to “should.” This change was contro-



versial, and the question was asked whether Version 2 terminals shall support fast call setup as an alternative. Also,it was decided to make support for reporting CONNECT with an IRR optional. Both of these decisions were quitecontroversial, with many advocates on both sides. Both concluded with the advocates of a mandatory approachwithdrawing the requirement for mandatory operation in deference to their desire to at least have the option available.

OtherAPC-1276 (D. Tirosh and S. Petrack, VocalTec) discusses using the transport layer address within H.323 ProtocolData Units (PDUs) for transparent firewall operation, and proposes a simple way for Version 2 terminals to operatewith transparent proxies and firewalls. T. Nixon (Microsoft) noted that this solution should also be applied toH.245 use of transport addresses as well. T. Nixon (Microsoft) also noted that this solution would not remove theneed for firewalls to break open frames for poor terminals. The contribution was not accepted, although it wasagreed that it seeks to address an important point.

APC-1278 (L. Moscovici and S. Petrack, VocalTec) discusses access Tokens within H.323. It was decided toremove these access tokens in deference to similar capabilities in H.235.

APC-1279 (L. Moscovici and S. Petrack, VocalTec) proposes allowing a Gatekeeper to accept a re-registrationwith a changed transport IP address assuming that the terminal followed the local security policy. The contributionwas accepted and text will be supplied to the editor of H.323.

APC-1280 (L. Moscovici and S. Petrack, VocalTec) discusses a Progress UUIE for answer supervision. Thecontribution suggests that H.225 does not adequately identify remote party answer supervision, “when the phone isanswered”. It was decided that the use of call progress to mean “true connect” was not wise since progress is notpassed end to end. It was noted that it is valid for a Gateway (GW) to return call-preceding with in-band tones andinformation for the case where the far end GW is doing Interactive Voice Response (IVR); however, in this case thereis no call accounting since the call has not officially started and there has been no connect.

APC-1281 (L. Moscovici and S. Petrack, VocalTec) proposes adding InfoConfirm (ICF) to the message to enhancereliability and security. It was noted that IRR is the only “unacknowledged” Registration, Admission, and Status(RAS) message and that this would complete the symmetry of the system. The final text is in TD-13(Rapp) (S.Petrack, VocalTec) and will be added to H.323 and H.225.0.

APC-1291 (D. Walker, Mitel) proposes to allow Master/Slave status to be re-determined if no process is on-goingthat is using the result of a previous master/slave determination. During the joint session with Q14/16, H.245super-editor M. Nilsson (BT) agreed that the proposal seemed complete and covered all matters of concern. Based onthis input, the proposal was accepted.

APC-1293 (VideoServer) discusses support of ConferenceAlias in H.323 Revision 2, and proposes the use of ahuman readable alias for the conference ID. The proposal results in a powerful set of abilities, including joining arunning conference by name. The proposal was accepted and will be added into H.323 by the Editor based on TD-19(Rapp) (VideoServer) with some small changes.

APC-1297 (M. Reid and K. Hedayat, PictureTel) contains general comments and proposals for H.323, H.225,H.245 and H.450.X (Supplementary Services). Section 2.1 discusses how the substitute conference ID is a problemfor the gatekeeper. The contribution was accepted and will be put in H.323 and H.225.0.

APC-1303 (C. Fleiner and H. Truong, IBM) proposes draft text for H.323 based on the APC-1218 (C. Fleinerand H. Linh, IBM), proposal from the previous meeting. APC-1218 seeks to clarify H.323 ad-hoc conferencingexpansion. A question was raised concerning whether this procedure allows transfer during a existing call; theanswer appears to be no. This change will be added to H.323.

APC-1304 (D. Lindbergh, PictureTel) discusses “replacementFor” draft text, previously proposed in APC-1233 ,and proposes a new method of faster mode changes in H.245. The proposal was adopted for H.245 and requires asmall change in H.323 calling for removal of an appendix.

APC-1309 (A. Franklin, Lucent) contains comments on H.323 in section 2 and 3, and prompted discussion of the“video clues” proposal. Concern was expressed about the possible complexity of the seemingly simple “video clues”solution, and it was withdrawn pending further development of a more generalized audio/visual control method. Thenew definitions in APC-1309 section 3 were generally accepted with some changes. Text is to be provided to theeditor off line. Section 4, coordinating H.323 and T.120 was also discussed, and has been withdrawn.

APC-1311 (VideoServer) discusses H.323 terminal default call signaling behavior, calling attention to the case of acall where no conference goal is known to the calling terminal software while the call is being placed. This issue



was discussed during the joint Q11-14/16 meeting, and the resulting text changes to H.323 appear in TD-20(Rapp). TD-20(Rapp) (VideoServer) provides procedures to expand from point-to-point calls into Ad HocMultipoint.

APC-1315 (P. Cordell, BT Labs) contains comments on H.323, including the following:

• Gateway registration: Editor will clarify that there is no one way of doing this.• Call Identifier interop with V1/V2: a modified version of the text will go to editor.• Other editorial issues.

APC-1318 (P. Cordell, BT Labs) discusses user location using H.225/Q.931 signaling, and shows how existingQ.931 messages could be used to find a person whose address is not known. It will be added to H.323 as anillustrative example. P. Cordell (BT Labs) will provide updated text for an Appendix.

APC-1321 (B. Quinn, DataBeam, et al) discusses coordination of H.323 and T.120 Conferences. This issue wascovered in the joint Q11-14/16 meeting under T/H-series harmonization. This proposal was accepted as the basis ofrequired or preferred H.323 V2 operation, with H.323 setup always preceding T.120 setup. A revised version appearsas TD-34(Rapp) (B. Quinn, DataBeam) and was adopted.

H.225.0 V2 MEDIA STREAM PACKETIZATION AND SYNCHRONIZATION ON NON-GUARANTEEDQUALITY OF SERVICE LANS

APC-1257© contains the H.225.0 V2 draft. It was decided to refer to H.245 and H.235 as octet strings to avoidforcing the developers to compile the whole of the ASN.1. Suggestions for a revised name were solicited. Asummary of changes appeared as TD-39(Rapp) (G. Freundlich, Lucent).

APC-1275 (L. Moscovici and S. Petrack, VocalTec) discusses endpoint type in Authentication ControlFunction/Location Confirm (ACF/LCF). The contribution was accepted. The editor changed “mdestype.” to“destination type.” The final text appears in TD-29(Rapp) (S. Petrack, VocalTec).

APC-1284 (L. Moscovici and S. Petrack, VocalTec) proposes to add additional location information for analternative end point. The proposal was accepted with the change that the three dots are moved to the end. TD-29(Rapp) (S. Petrack, VocalTec) contains textual changes for this contribution.

APC-1307 (J. Toga, Intel) discusses Real Time Transport Protocol (RTP) Payload alignment for H.245/IETF, andproposes decoupling packetization type and H.323 capability by allowing explicit passing of the RTP payload type.The proposal was accepted.

APC-1316 (P. Cordell, BT Labs) contains comments on H.225, including the following:

• RAS Retry Strategy: proposes to decrease ARQ/ACF times by allowing shorter, variable timers. There were noobjections but the text needed cleaning up. TD-26(Rapp) (P. Cordell, BT Labs) has the final text.

• Use of Facility Protocol Discriminator Information Element (IE): covered under supplementary services.• CallIdentifier: aside from the final point about adding V1/V2 interoperability issues, this section was rejected.• Delete unknownPartyNumber: suggestion will be accepted.• Conforming Facility-UUIE: suggestion was accepted for small ASN.1 change• NoPermissionsRequired Call Setup: accepted with the proviso that the noPermissionRequired be split into

“noPermissionToInitiate” and “noPermissionToReceive”. It was also proposed to add a time to live type of fieldand fields to support the gatekeeper routed model. Results with new ASN.1 appear in TD-26. A modification ofterminology to use ARQ instead of permission was agreed.

• Comprehension Required: consider for future versions of H.323 past V2.• OPTIONAL BOOLEANs: proposes some ASN.1 changes; it was accepted. Editors will incorporate them.• Change LAN Term in Line with Scope: editors will handle.• Eight additional editorial corrections

H.323.0 ANNEX B (LAYERED VIDEO CODING )

TD-7 (G. Kisor, Intel) discusses H.323V2 Layered Video Coding, and includes a few changes; they were accepted,including a new QoS section.

APC-1325 (J. Ott, Teles) discusses extensions to H.245 to Support H.263 video redundancy encoding, andincludes some additional semantics for H.245 to support layered video coding. Some editorial errors in the ASN.1involving hyphens were pointed out. The H.323 editor will add some text to refer to this feature.



H.323.0 ANNEX C (H.323 ON ATM)

APC-1261 (G. Kisor, Intel) contains Annex C to H.323.0 (H.323 on ATM). The contribution was accepted.H.245 codepoints need to be updated to match the new ITU ATM names used in the text. Also the level at which theAAL is indicated should be changed to allow future use of AAL2 for different logical channels.

H.225.0 NEW PACKETIZATIONS

AudioAPC-1283 (S. Petrack, VocalTec) discusses H.245 support for GSM speech codecs, and calls for the use of GSMas a standard coder in H.323 for interoperability with mobile systems. The syntax appears in TD-29(Rapp). Thischange will be included in H.323. Study Group 16 management has advised proceeding on the assumption thatreference can be made to ETSI GSM documents directly.

VideoQ15/16 is working on H.263+ RTP packetizations; their goal is to provide material for H.245 V3. (The Q15/16report will be published in CSR-T Vol 8.9, November 1997.)

H.332 [ former H.Loosely Coupled]APC-1256© contains the H.332 draft Recommendation. It was presented by V. Kumar (Intel), and was approved formoving forward as a white paper.

SUPPLEMENTARY SERVICES – GENERAL ISSUES

APC-1285 (P. Cordell, BT Labs) discusses use of H.245 in supplementary services, and proposes using an emptycapability set to indicate hold. There was considerable discussion, with some support and some concerns expressed.Final text appears in TD-27r2(Rapp) (P. Cordell, BT Labs).

APC-1297 (M. Reid and K. Hedayat, PictureTel) contains general comments and proposals for H.323, H.225,H.245 and H.450.X, including the following:

• Sec. 4.1 proposes that GK to GK communications should support Requirements specified by the ITU Q seriesRecommendations (QSIG). It was agreed that this direction would be the basis of future work to promoteinteroperability with Private Branch Exchanges (PBXs).

• Sec. 4.2 proposes that requestChannelClose be mandatory in Version 2 to support H.450.2 services, which useit. This was agreed.

APC-1316 (P. Cordell, BT Labs) discusses the use of Facility IE (information elements). The contribution isconcerned that version 1 endpoints may not interoperate with H.450.x services. The issue was resolved and it wasagreed to accept it into H.450.x.

H.450.1 GENERIC FUNCTIONAL PROTOCOL (FORMERLY H.323 ANNEX D)

APC-1252 (M. Korpi, Siemens AG) discusses generic functional protocol for the support of supplementaryservices in H.323. A few minor changes were made. A choice will be added for the non-standard parameters betweenH.323 style and QSIG style. The contribution was approved to move forward.

H.450.2 CALL TRANSFER (FORMERLY H.323 ANNEX D2)

APC-1253(M. Korpi, Siemens AG) discusses call transfer supplementary service for H.323. It was approved withsome small changes.

APC-1292 (D. Walker, Mitel) discusses call transfer with consultation call for Gatekeeper-Routed model. It wasadopted with some editorial changes.

APC-1297 (M. Reid and K. Hedayat, PictureTel) contains general comments and proposals for H.323, H.225,H.245 and H.450.X, including the following:

• Sec. 4.4 Call Flow Question: since it appears that the call flows in H.450.2 are not exactly the same as in PBXQSIG, interoperability problems may result. Some text will be added to a new interworking section to explainwhy this will not be a problem.

• Sec. 4.5 was withdrawn in favor of APC-1292 (D. Walker, Mitel).



H.450.3 CALL DIVERSION (FORMERLY H.323 ANNEX D3)

APC-1254 (M. Korpi, Siemens, AG) discusses call diversion supplementary service for H.323. It was approved tomove forward.

NEW TOPICS

APC-1266 (D. Skran, Ascend) proposes to use H.323 call control for real-time Internet fax. It was agreed tomodify the scope of H.323 to include call control for Real-Time Fax and to send the liaison included as TD-25(Rapp) (Q13/16 Rapporteur) to Q4/8. The text agreed to at the WP 1&2/16 meeting is contained in Annex 4APC-1327 . Work will be directed toward an additional Annex to H.323/H.225.0.

APC-1317 (P. Cordell, BT Labs) discusses alternate service signaling; it was deferred for further development.

APC-1319 (P. Cordell, BT Labs) discusses multicasting H.225/Q.931 SETUP for User Location; it was alsodeferred for future development.

APC-1323 (J. Blin, France Telecom) calls for running H.323 on ISDN and describes an experiment in whichH.323 was run on ISDN-B channels. Some of the issues involved in running Point-to-Point Protocol (PPP) over apoint-to-point link were discussed. Concerns were raised about how these issues relate to efforts to run H.324 onISDN and also to existing H.320 terminals running on the ISDN. The importance of using H.dispatch (V.108) wasemphasized. Other views were expressed that Internet connections in general should operate in a point-to-pointfashion. Support was expressed by BT and Microsoft. It was agreed to propose an Annex to H.323 for this purposeat the January 1998 SG 16 meeting. J. Blin (FT) volunteered to act as editor.

URL RelatedAPC-1273 (S. Petrack, VocalTec) puts forward requirements for H.323 URLs.

APC-1274 (S. Petrack, VocalTec) puts forward a URL for Registration, Admission, and Status (RAS) requests. Itwas agreed that creation of a position should be considered, but that it should be directed toward an input to theIETF.

Q14/16 COMMON PROTOCOLS, MCUS AND PROTOCOLS FOR INTERWORKING WITHH.300-S ERIES TERMINALS

Editor’s note: There is considerable overlap within Q12, Q13 and Q14. Where appropriate, information from theQ14 meeting is included in the Q12 and Q13 reports and not below..H.245 TOPICS

H.323 ChangesAPC-1296 (M. Reid, PictureTel) contains H.323 additions for H.245 Version 3. The contribution was reviewedalong with the list of changes collected during the meeting, which drew no objections. The revised text is provided inTD-33(Rapp) (M. Reid, PictureTel), which was accepted.

DMIF/H.245 Harmonizat ionRelevant contributions include:• APC-1268 (V. Balabanian, DMIF), Proposed liaison from MPEG (DMIF) to ITU-T SG 16, in response to

TD-38 (GEN) Geneva March 1997, July 1997• APC-1269 (R. Koenen), MPEG-4 Overview, July 1997• APC-1270 (ISO), DMIF (Delivery Multimedia Integration Framework) ISO/IEC 14496-6 WD 1.0, July 1997• TD-21rev3(Rapp) (G. Thom, Delta Information Systems), Liaison to ISO/IEC JTC1/SC29/WG11 on DMIF

TD-22(Rapp) is an overview of DMIF. It was suggested that the DMIF proponents work with the H.245 editorto incorporate the proposed additions. It was pointed out that the proposal also needs semantics for the H.245 syntaxadditions and also procedures for their use in H.3xx. The time frame for incorporating these changes was discussed.It may be practical to incorporate these changes in the next revision of the documents, but it was decided that thisshould be discussed off line.

TD-21(Rapp) (G. Thom, Delta Information Systems) proposes that annexes be developed for H.323 and H.310describing the use of DMIF in those systems. This work will be driven by contributions during the next meetingcycle. Changes in the wording of the liaison were suggested and will be incorporated in TD-21Rev3(Rapp)



(Q14/16 Rapporteur) which is contained in Annex 5 of APC-1327 . This was approved at the WP1&2/16meeting.

Other topics

Q11-B-43 (same as TD-37(Rapp), R. Ackner, Acer) discusses the interoperability of H.324 terminals usingdifferent versions of H.245. H.245 does describe how to handle fields after the extension markers which it does notunderstand. Interested parties will suggest clarifying text to the editor.

Q11-B-30r2 (same as TD-38(Rapp)) describes H.245 changes for H.324 Mobile. A brief summary of this workwas presented and accepted.

H.323/T.120 HARMONIZATION

APC-1326 (J. Ott, Teles) contains the meeting report on the second meeting of IMTC ad-hoc group onharmonization of conferencing protocols. It includes a list of seven short term issues that require addressing. APC-1321 (B. Quinn, DataBeam) describes coordination of H.323 and T.120 conferences. Three topics were reviewed.

APC-1326 issue 1, two ways to start a data-only conference, was discussed. The requirement to lead with H.323was opposed by BT. Alternate wording was discussed which was acceptable to all parties. The proposal was ac-cepted pending some rewording which discusses mandatory and optional modes. Final text is contained in TD-34(Rapp) (P. Galvin).

APC-1326 issue 4, use of H.225.0 ConferenceGoal, and APC-1311 (VideoServer), discussing H.323 terminaldefault call signaling behavior, were reviewed. The proposal was accepted pending review by interested parties anddevelopment of agreed text. This text is also contained in TD-34(Rapp) (B. Quinn, DataBeam).

APC-1309 (A. Franklin, Lucent) section 4, which discusses only using invite (not join) for joining T.120conferences within an H.323 conference, was reviewed. There were some concerns expressed and the interestedparties will discuss the issue off line. The discussion concluded that the ability to join a T.120 was necessary;consequently, the proposal in APC-1309 section 4 has been withdrawn.

T.130/H.323 harmonization was discussed at length in the joint Q3, Q11-Q14 meeting. It was decided that T.130and H.245 advanced audio visual control work will continue aggressively into the next meeting period. The schedulefor Determination of this work will be driven by contributions from interested parties.

Moving the audiovisual control work (T.130 et al) into Q14/16 was discussed. It was the opinion of Q12-14/16group that this work would best be done in Q14/16. Q3/16 and WP 2/16 agreed to this change.

H.235, SECURITY, TOPICS

APC-1290 (J. Toga, Intel) contains the draft of H.235. Small editorial issues were identified. One major issueconcerned removal of certificate key management, which will be put back into the contribution. A second majorissue concerned the use of security tokens to hide destination addressing information, and is further explained in TD-12(Rapp) (J. Toga, Intel). The comment was offered that H.235 provides a framework but lacks proceduraldescriptions for use in H.235. This procedural information is included in TD-12(Rapp) (J. Toga). It wasconfirmed that no algorithms will be mandated in H.235. The notes relating to this will be expanded and moved intothe scope.

APC-1271 (M. Euchner, Siemens AG), discusses H.235 Message integrity for the H.225.0 RAS channel; it wasaccepted and will be incorporated into H.235.

APC-1320 (BT), a proposal to improve the ASN.1 syntax used for encryption, was accepted and deferred to theH.245 discussion.

It was noted that all ASN.1 will be moved from H.235 into H.245 and H.225.0. The H.235 white paper should notcontain the ASN.1.

APC-1278 (L. Moscovici and S. Petrack, VocalTec), discusses access tokens within H.323; it was accepted andincorporated into TD-12(Rapp) (J. Toga).

APC-1316 (P. Cordell, BT Labs) discusses RAS retry strategy, and includes some editorial changes for H.235.The editor will take these under advisement.



APC-1267 (P. Galvin, DataBeam) discusses T.120 security requirements. It was decided to work towards includingT.120 security as an Annex to H.235. The work will primarily be done by Q3/16 with support from Q14/16. Dis-cussions should take place on the T.120 and the H.323 e-mail reflectors. It was requested that the Q14/16 expertsreview APC-1267 and provide feedback to Q3/16 on its content and compatibility with H.235.

H.246 TOPICS

Draft Recommendation H.246 describes gateways which provide protocol interworking between H-series multimediaterminals and other H-series terminals, voice/voiceband terminals on the PSTN or ISDN, V.70 terminals on theGSTN and multi-call applications on the PSTN.

APC-1295© (K. Sakai, Fujitsu) contains the H.246 Draft. Annex B, Voice/Voiceband terminal on the PSTNinterworking, will be removed and Determined at a later date when technical information is available. A.7.2.2,calling a wrong number, will be deleted and replaced in the future with a section on interfacing with the publicnetwork for audio prompts. It was noted that the contribution needs text for inbound calls to a Message Center(MC). This and other minor changes are contained in TD-32(Rapp)© (M. Reid, PictureTel). It was additionallynoted that TCS-4 (H.221 command) is mandatory and DTMF is optional. APC-1285 (P. Cordell, BT Labs)proposes using H.245 empty capability sets to support a form of third party call control in the GK. This proposalwill be incorporated. Section A.7.2.3, calling another gateway, is for further study.

H.MEDIAMIB TOPICS

Contributions submitted included APC-1289 (R. Webber, PictureTel, same as APC-1208 from Herzlia), whichcontains H.MediaMIB progress report and draft; and APC-1294 (VideoServer), which lists a number of concernsabout the H.MediaMIB draft and the technical direction of the work.

The current editor is interested in stepping down. It was asked whether there is interest in Q14/16 in continuing thiswork. The group indicated that there is interest if the work results in Management Information Bases (MIBs) whichare consistent with the current method of specifying protocol MIBs and not endpoint MIBs. It was also suggestedthat this work align with the Real Time Transport Protocol (RTP) MIB which has recently been developed. Theschedule for this work will be modified. H.MediaMIB will be scheduled for Determination in September 1998 andpossibly for Decision in June/July 1999. G. Kajos (VideoServer) has volunteered to be the new editor for theH.MediaMIB. Contributions are solicited.

CHAT ISSUES

TD-35(Rapp) is a proposal to Q13/16 and Q14/16 to include text chat protocols in H.245 and H.323. It was pointedout that the proposal needs text for H.323 and packetization for the chat data. It also requires some additions toH.245 to support this change. The following change was also added: “If a terminal implements T.Chat it shall alsoimplement V.Chat in a logical channel.” A new annex will be developed for H.225.0 which describes how to carryV.Chat in a logical channel for H.323. It is expected that this annex will be Determined at the January 1998meeting. T. Nixon (Microsoft) has volunteered to edit this Annex (see the Q9/16 report above).

HARMONIZATION WITH Q15/16 VIDEO CODING

Joint sessions among Q11-15/16 were held to address progress of H.263+ work, future video coding work, H.245issue and packetization.

IPR MATTER

The Rapporteur restated the ITU-T policy regarding the IPR related to draft Recommendations. Participants areencouraged to advise the group about any known patents related to draft Recommendations, either of their own or ofothers. The next step is to collect patent statements from patent holders for filing in the TSB database.

S. Okubo, GCLD. Skran, AscendG. Thom, Delta Information Systems

Q15/16 ADVANCED VIDEO CODING

The Q15/16 report will be published in CSR-T 8.9, November 1997.



Q23/16 PCM MODEMS

The primary goal of the Q23/16 PCM Modem Rapporteur meeting was to complete the work on V.pcm - Issue 1 inorder to Determine the Recommendation at the WP1/16 meeting September 12. This goal was not achieved.

LIAISONS

D. Stuart (Q4/15 Rapporteur) presented PCM97-103 , a liaison reply from the Q4/15 Rapporteur group concerningaspects of xDSL modem specifications which may affect V-series modem performance. Q4/15 replied that they dointend to develop Recommendations for xDSL modems which will be capable of supporting voice services on thesame pair in a local loop, and agreed to support, to the extent practicable, the use of V-series modems on the voicechannels associated with these xDSL devices. They also asked Q23/16 for more information on V-series modemrequirements, such as band edge attenuation, group delay distortion, and return loss.

J. Moughton (Hayes) presented PCM97-124 , a liaison from SG 15 on transport of voice band data over B-ISDN/ATM networks. Q23/16 agreed to draft a liaison reply to inform them of the impact that variable delay in thenetwork will have on echo canceling voice band modems, urging them to minimize any such variability. J.Moughton agreed to draft this liaison for approval at the WP1/16 meeting. PCM97-131, this liaison reply to SG15, was not available for review by Q23/16. It was submitted directly to the WP1/16 meeting as TD-34 and willbe brought to the next Rapporteur group meeting for information only.

PCM97-123 , a liaison statement from SG 15 in reply to Q23/16’s liaison to them on PSTN transmissioncharacteristics affecting PCM modem operation, was not considered at this meeting due to lack of time. It describesthe operation of network echo cancellers noting they may not be transparent when disabled, as well as describingpossible effects of DCME and PCME. It will be considered at the next Rapporteur group meeting.

LIST OF AGREEMENTS AND DRAFT TEXT

PCM97-95 and PCM97-100 are the updated lists of agreements for the V.pcm Recommendations from the TR-30.1 PCM modem ad hoc meeting and the TR-30.1 meeting respectively, in Quebec City, Canada, August 12-14,1997. Both were approved with minor revisions. The Rapporteur will revise the documents and post them to theftp site.

PCM97-106 (R. Williams, V.pcm editor, 3Com) is the latest revision of the baseline text for V.pcm - Issue 1. Itwas approved by Q23/16.

DOWNSTREAM DATA MODE: SPECTRAL SHAPING

PCM97-112 (S. Olafsson, Rockwell) is proposed draft text for the spectral shaping filter in V.pcm - Issue 1,using a biquad filter as the target function.

PCM97-128 (V. Eyuboglu, Motorola ISG) is proposed draft text for Convolutional Spectral Shaping.

R. Williams presented PCM97-121 and PCM97-126 (both from D. Walsh, 3Com). These contributionscompare three spectral shaping schemes on the basis of analog receiver performance, and propose that maximumsymbol inversion be selected as the spectral shaping technique for V.pcm.

DOWNSTREAM DATA MODE: MAPPING/FRAMING

PCM97-111 (S. Olafsson, Rockwell) proposes text for the mapping function in V.pcm, using the V.34 shellmapper (based on the earlier PCM97-54). As a result of discussion, S. Olafsson later presented a revision of thisdocument, PCM97-111R1 .

PCM97-122 (R. Williams, 3Com) proposes text for mapping by modulus conversion, with spectral shaping bymaximum symbol inversion using a single running digital sum without look-ahead as the metric (based on earliercontributions PCM97-46 and Norcross 14).

PCM97-101 (P. Ramaswamy, Digicom Systems) proposes a mapping scheme based on the Chinese RemainderTheorem (CRT), which can be viewed as a special case of modulus conversion, where the moduli are co-prime. Theexisting agreement concerning mapping/framing states that the only mapping schemes that will be considered (forV.pcm - Issue 1) are those that had been proposed no later than the July 1997 Rapporteur meeting. The consensusof Q23/16 was to abide by this agreement, and to not consider PCM97-101 further.



UPSTREAM DATA MODE

PCM97-130 (B. Barazesh, Lucent Technologies) proposes to make the V.pcm upstream symbol rate of 3000optional.

STARTUP PROCEDURES

PCM97-102 (B. Adams, Hayes) provides further information on the proposal to include a mechanism to allow theanalog modem to drop its transmit power to increase the downstream data rate (further to PCM97-88). In responseto a request to supply proposed text for this feature, B. Adams generated PCM97-115 . After further discussion itappeared that the implementation of this feature may be more complicated than originally thought, and so it wasagreed to not include it in V.pcm - Issue 1.

PHASE 2 STARTUP

PCM97-107 (V. Demjanenko and F. Hirzel, VoCAL Technologies) provides further information on their proposal(PCM97-91) to specify the Phase 2 probing sequence in terms of PCM codewords. The consensus of Q23/16 wasto abide by the existing agreement to specify digital modem transmit signals in an analog representation for startupPhases 1 & 2.

PHASE 3/4 STARTUP

PCM97-114 (M. McLaughlin, Lake Datacomms) proposes a digital impairment learning descriptor based onmultiple instances of the proposal in PCM97-97 (Rockwell).

PCM97-108 (V. Demjanenko, F. Hirzel and E. Freed, VoCAL Technologies) proposes additional parameters forthe digital impairment learning descriptor described in PCM97-97 to allow for different spectral content for eachrepetition of the sequence. PCM97-109 (V. Demjanenko and F. Hirzel, VoCAL Technologies) proposes anextension to PCM97-97 that results in sub-optimal digital probing sequences but uses significantly fewer bits forthe descriptor, thereby reducing the transmission time for the descriptor.

PCM97-110 (V. Demjanenko and F. Hirzel, VoCAL Technologies) proposes a digital probing sequence forsimultaneously learning digital impairments and training adaptive elements in the analog modem receiver.

PCM97-119 (B. O’Mahony, Intel) proposes a variable-length digital impairment learning descriptor that tries toaccommodate the proposals in PCM97-97 (Rockwell, 3Com, and GDC), PCM97-114 (Lake Datacomms), andPCM97-108 (VoCAL).

PCM97-105 (R. Williams, 3Com) contains a detailed proposal for the structure of the Phase 3 and 4 startupprocedure for V.pcm - Issue 1, based on the analog modem transmitting first in Phase 3. PCM97-117 (R.Williams, 3Com) is a proposed 4-level digital synchronization sequence to be used as Sd and Sdbar in PCM97-105 .

PCM97-113 (S. Olafsson, Rockwell) contains a detailed proposal for the structure of the Phase 3 and 4 startupprocedure for V.pcm - Issue 1, based on the digital modem transmitting first in Phase 3.

PCM97-120 (A. Sadri, R. Fischer and G. Ungerboeck, IBM) discusses a general method for the estimation ofsignal constellations and determination of transmit code sets in V.pcm modems.

RATE RENEGOTIATION PROCEDURES

PCM97-116 (D. Walsh, 3Com) proposes a fast retrain procedure for V.pcm to allow the analog modem to finetune its echo canceller (in half duplex). PCM modems require a much deeper echo canceller null than V.34 modems.As a result, changes in impedance of the modem (e.g., line transformer) as the modem changes temperature need tobe normalized.

OTHER CONTRIBUTIONS

PCM97-104 (J. Renkel, 3Com) is a proposed Terms of Reference for the V.pcm all-digital mode. No action wastaken on this at the meeting.

DISCUSSION

In order to facilitate the discussion and resolution of issues, the Rapporteur generated PCM97-118 , an updated listof 27 open issues. An ad hoc group was formed to address the startup issues. The output of one of these ad hoc



sessions, PCM97-125 , contains proposed draft text for the digital impairment learning sequence. However, uponreview of this proposal by the Rapporteur group, it was decided that further work was necessary. The ad hoc groupmet again to address this and other startup issues. The report of the agreements from this ad hoc session, PCM97-127 , contains alternative proposed text for the digital impairment learning sequence, proposed text for the digitalimpairment learning sequence descriptor, and a proposal for selecting the codepoint that the digital modem willtransmit during the 2-point training segment. This report was reviewed by the Rapporteur group and approved withsome revision. The final text is contained in PCM97-127R2. It was agreed that the editor will include this materialin the next revision of the baseline text for V.pcm - Issue 1, with the understanding that the digital impairmentlearning descriptor will be framed using the same structure as MP sequences in V.34.

During the discussions, after several new agreements were reached, the Rapporteur generated PCM97-129 , anupdated list of agreements for Q23/16’s review and approval. This was discussed and approved by Q23/16 with a fewrevisions and the inclusion of last minute agreements. PCM97-129R1 contains all of the agreements reached duringthe Rapporteur meeting. These agreements are summarized below.

AGREEMENTS

The following global agreements (applies to V.pcm - Issue 1 and Issue 2) were reached:

1. Modified an existing agreement on transmit power as follows:

agreed that, during startup, the digital modem will indicate its maximum transmit power (not to exceed theregulatory limit) , and the Recommendation will include text stipulating that the analog modem shall complywith this restriction in its selection of constellations.

2. Transmit power: agreed that the minimum value for the digital modem’s indicated maximum transmit power willbe -16 dBm.

The following agreements pertaining to V.pcm - Issue 1 were reached:

1. Editorial: agreed that figures for startup, retrain, and rate renegotiation will show the digital modem on thebottom and the analog modem on the top.

2. Differential encoding: agreed that the digital modem will include some form of polarity invariant differentialencoding.

3. Transmit power reduction: agreed to use the existing V.34 mechanism for control of power reduction.

4. Startup Phase 2 (previously a provisional agreement): agreed to keep probing signals as they are in V.34 (noadded frequencies, no added probing sequences).

5. Startup Phase 2: agreed that the duration of L1 and L2 will be as specified in V.34.

6. Startup Phase 2: agreed to include bits in INFO0 indicating the digital modem’s nominal transmit power forPhase 2, from -6 dBm to -21 dBm in 1 dB steps.

7. Startup Phase 2: agreed that the analog modem will indicate in INFO1 which constellation point (as a G.711 codeword) for the digital modem to use for 2-point TRN (training). The selected codepoint shall be between 0 dB and-1 dB of the digital modem’s maximum transmit power (indicated in INFO0).

8. Startup Phase 2: agreed to include a bit in INFO0 to indicate the measurement point for the digital modemtransmit power (1=codec output, 0=DPCM output).

9. Digital impairment learning: agreed that digital impairment learning will be in half duplex (Phase 3) and that thesequence will be transmitted at only one point in the startup procedure.

10. Modified an existing agreement on digital impairment learning as follows:

agreed to use a programmable approach to digital impairment learning (details are as specified in PCM97-127R2to be determined ) .

11. Digital impairment learning: agreed to add a note to the baseline text indicating that the digital impairmentlearning sequence should be designed so as not to emulate any network signaling tones, and that its power shouldbe kept high enough so as not to allow network echo control devices to become re-enabled.



12. Startup Phase 4: agreed that the digital modem should transmit a spectrally shaped multi-level constellation afterdigital probing, to allow the analog modem to fine tune its receiver.

13. Retrain procedures: agreed to include a full retrain procedure that goes back to the beginning of Phase 2.

14. Retrain procedures: agreed that fallback to V.34 is through the full retrain procedure only.

15. Retrain procedures: agreed to include a fast retrain mechanism to allow echo canceller fine tuning in half duplex.

16. Rate renegotiation procedures: agreed to include a rate renegotiation procedure that goes back to the beginning ofPhase 4.

Some key data mode issues remained unresolved by the end of the meeting and therefore V.pcm - Issue 1 was notready for Determination at the September 12 WP1/16 meeting. Q23/16 discussed a new work schedule and agreed topress for Determination at the SG 16 meeting in Geneva at the end of January, 1998, with Decision no later than theSG 16 meeting in September 1998. There was some discussion that a meeting in mid 1998 to Decide the V.pcmRecommendation might be possible if needed.

FUTURE MEETINGS

With the new schedule in mind, it was agreed to hold the next Q23/16 Rapporteur group meeting December 3-5,1997, in Lake Buena Vista, Florida, immediately after an abbreviated TR-30 meeting, and to request from WP1/16permission to hold one additional meeting (if needed) before the January SG 16 meeting.

L. Brown, Motorola ISG

PARTIAL ROSTER FOR SG 16 WP1&2 AND RAPPORTEUR MEETINGSSEPTEMBER 4 – 12, 1997, SUNRIVER, OR

John Magill, Lucent UK Chair WP1/16Federico Tosco, CSELT, Italy Chair WP 2/16

Bruce DeGrasse, BJ Communications, US Q3/16 RapporteurLes Brown, Motorola ISG, Canada Q4/16 Associate Rapporteur, V.8bisFred Lucas, General DataComm, US Q7/16 RapporteurGunnar Hellström, Omnitor, Sweden Q9/16 RapporteurTom Geary, Rockwell, US Q11/16 RapporteurSakai Okubo, GCL, Japan Q12/16 RapporteurDale Scran, Ascend, US Q13/16 RapporteurGary Thom, Delta Information Systems, US Q14/16 RapporteurGary Sullivan, PictureTel Q15/16 RapporteurLes Brown, Motorola ISG Q23/16 Rapporteur

AustriaSiemens P. Caldera

BelgiumTelindus Peter Plets

BrazilTelebras Marcio MeloniTelebras Tenio Lustosa

CanadaMitel D. WalkerNortel Tom Taylor

FinlandHelsinki Telephone Juha KauppiNokia Lippo Rantanen

FranceAlcatel N.V. B. MobasserPhilips Veronique BrunTexas Instruments Jean-Pierre Houdard

GermanyRobert Bosch P. VogelDeutsche Telekom Ralf-Rainer DammSiemens M. EuchnerSiemens Neal KingSiements W. KlasenSiemens Istvan SebestyenSiemens B. WimmerTeles Jorg Ott

IrelandLake Datacomms Michael McLaughlin

Israel G. KimchiVocalTec Comm. Scott Petrack

ItalyCSELT F. Tosco

Japan Mitsuji MatsumotoCanon M. HosakaCIAJ K. HibiFujitsu Hiroyasu MurataFujitsu Y. NishizawaGCL Sakai OkuboHitachi Y. NakayaKDD S. SakazawaKDD H. YamadaNEC Corp. Yoshihisa AotaniNEC Copr. H. HarasakiNTT KobayashiNTT H. KoyanoNTT Y. TomitaOKI Minoru MiyazakiPanasonic (MGCS) Akira (Al) Atsuta

Korea Dong-Bum JungKorea Telecom Sang-Gil KimKorea Telecom Jungja Roh

Netherlands



KPN Cor QuistNorway

Telenor H. SandgrindSweden

Omnitor Gunnar HellstromUnited Kingdom

BT Labs John BoucherBT Labs Mike NilssonBT Labs Trevor PeersHayes Bill PecheyHayes John MoughtonLucent UK Mike BuckleyLucent UK John MagillRacal Datacom Chris Firth

USA3Com Dick Stuart3Com Richard WilliamsAcer Reuven AcknerACTION Consult’g Ken KrechmerAnalog Devices Rao NuthalapatiBJ Comm. Bruce De GrasseCirrus Logic Veda KreshnanCisco Systems Greg GoodknightComsat Simao Campos-NetoCSR Elaine BaskinDataBeam Pat MurphyDatabeam Neil StarkeyDelta Info Sys Gary ThomEss Technology Ping DongEss Technology C. WangGallaudet Judy HarkinsGeneral DataCom Yuri GoldsteinGeneral DataCom Fred LucasHayes Bruce AdamsIBM Ali SadriIntel N. BhaskerIntel Chris Hansen

Intel Barry O’MahonyIntel Jim TogaIntel J. WilsonLucent Bahman BarazeshLucent G. FreundlichLucent Louise SpergelLucent Z. YangMCI Murry McEntireMicrosoft Joe DecuirMicrosoft Toby NixonMotorola Dick BrandtMotorola Les BrownMotorola Vedat EyubogluParadyne R. SmithPC Tel S. ManuelPC Tel Han YehPictureTel M. BacePictureTel Sunel BhagatPictureTel Mark DuckworthPictureTel Chuck GrandgentPictureTel Dave LindburghPictureTel Gary SullivanPolycom Pat RomanoRedwing Attow KeelRockwell Keith ChuRockwell Tom GearyRockwell Glen GriffithRockwell Sverrir OlafssonRockwell Chris SneedRockwell Z. ZhouTexas Instruments M. AliTexas Instruments P. PritchettVideoTelecom M. ChenVideoTelecom S. CheungVoice of TTY Andrea Saks

Eutelsat S. AgnelliITU F. Bigi

The next issue of Communications Standards Review – Telecommunications (Vol. 8 #9) is scheduled forNovember 1997.



ACRONYM GLOSSARY

AC alternating currentACIL Association of Independent Scientific, Engineering and Testing FirmsACR Absolute Category RatingADPCM Adaptive Differential PCMADSL Asymmetric Digital Subscriber Loop (Line)ANF Additional Network FeatureASN Abstract Symbol NotationATM Asynchronous Transfer ModeB-ISDN Broadband ISDNBFT Binary File TransferBRI Basic Rate InterfaceC&I Commands and IndicationsCA Conformity AssessmentCAP Carrier-less Amplitude Modulation Phase ModulationCI Call Indicator (V.8)CIDCW Calling Identity Delivery on Call WaitingCIF Common Intermediate FormatCM Call MenuCPAP Customer Premises Access ProfileCPE Customer Premise EquipmentCPN Customer Premise NetworkCS Canadian StandardCSA Canadian Standards AssociationDAVIC Digital Audio-Visual CouncilDCE Data Circuit Terminating EquipmentDCME Digital Circuit Multiplication EquipmentDIS Digital Identification SignalDMIF DSM-CC Multimedia Integration FrameworkDMT Discrete Multi-tone CarrierDOC Declaration of ConformityDSS1 Digital Subscriber Signaling 1DTE Data Terminal EquipmentDTMF Dual Tone Multi FrequencyELAWG EMC Laboratories Accreditation Working GroupEMC ElectroMagnetic CompatibilityETSI European Telecommunications Standards InstituteFCC Federal Communications Commission (U.S.)FDD Frequency Division DuplexingFEXT Far End Cross TalkFTP File Transfer ProtocolFTP Foiled Twisted PairGII Global Information InfrastructureGK GateKeeperGSM Global System for Mobile Communications (formerly Groupe Speciale Mobile)GSTN General Switched Telephone Network (e.g., PSTN)HAC Hearing Aid CompatibleHNW Home NetWork (VESA)ID IdentificationIEC International Electrotechnical CommitteeIEEE Institute of Electrical and Electronic EngineersIETF Internet Engineering Task ForceIMT International Mobile Telecommunications (IMT-2000, see FPLMTS)IP Intellectual PropertyIP Internet ProtocolIPR Intellectual Property RightsIRR Information Request ResponseISDN Integrated Services Digital NetworkISO International Organization for StandardizationISP International Standardized ProfileITU-R ITU Radiocommunications SectorITU-T ITU Telecommunications SectorJM Joint Menu



LAN Local Area NetworkLDCELP Low Delay CELPMCU Multi-point Control UnitMF Multi-tone FrequencyMLTS Multi-Line Telecommunications SystemsMP Modulation ParameterMPEG Motion Picture Experts GroupMRC Mixed Raster ContentNATO North Atlantic Treaty OrganizationNEXT Near End Cross TalkNLD Non-Linear DistortionNPRM Notice of Proposed Rule Making (FCC)NSAP Network Service Access PointOSHA Occupational Safety and Health Administration (U.S.)OSP OutSide PlantPBX Private Branch ExchangePCM Pulse Code ModulationPCME Packet Circuit Multiplication EquipmentPCR Program Clock ReferencePCS Personal Communication ServicesPSTN Public Switched Telephone NetworkPWT-E Personal Wireless Telecommunications - Enhanced Interoperability StandardQAM Quadrature Amplitude ModulationQCIF Quarter CIFQoS Quality of ServiceQSIG Requirements specified by the ITU Q series RecommendationsRADSL Rate-Adapting ADSLRAS Registration, Admission, and StatusRAST Receive And Send TerminalRF Radio FrequencyRFI Request for InformationRG Residential GatewayROT Receive Only TerminalRSVP Resource Reservation Setup ProtocolRTP Real Time Transport ProtocolScTP Screened Twisted PairSMG Special Mobile GroupSOT Send Only TerminalSQEG Speech Quality Expert GroupSTP Shielded Twisted PairSVF Simultaneous Voice and FacsimileTAPAC Terminal Attachment Program Advisory CommitteeTCP Transmission Control ProtocolTDD Time Division DuplexingTDMA Time Division Multiple AccessTOR Terms of Reference

TR2TF Technical Regulatory Reform Task Force

TSB Telecommunications Standardization Board (ITU)TSB Telecommunications Systems Bulletin (TIA)UL Underwriters LaboratoriesURL Uniform Resource LocatorUSB Universal Serial BusUTP Unshielded Twisted PairUUIE User-to-User Information ElementVAD Voice Activity DetectorVBD Voice Band DataVESA Video Electronic Standard AssociationWARC World Administrative Radio ConferenceWP Working Party (ITU)xDSL all the different Digital Subscriber Lines



1997 STANDARDS COMMITTEE MEETING SCHEDULESAS OF SEPTEMBER 29, 1997

Subject to Change without Notice

Committee Date(s) LocationITU-T SG 8 Oct 7 - 16 GenevaTR-30 Oct 13 - 17 Galveston, TXT1E1 CAP/QAMRADSL ad hoc

Oct 15 - 16 ---

TR-41.5 Int. with VESA Oct 20 - 21 ---SG 16 LBC Oct 20 - 24 ---ETSI MTA Oct 20 - 24 Vienna, AustriaETSI STQ Oct 22 - 24 Sophia Antipolis, FranceQ4/15 Rapp Oct 27 - 29 Redbank, NJTR-29 Oct 27 - 30 Toronto, CanadaQ3/16 Rapp Oct 27 - 31 Toronto, CanadaQ1/16 Rapp Nov ---T1A1 Nov 10 - 14 ---ETSI TIPHON Nov 11 - 14 Vienna, AustriaTR-41 Nov 17 - 21 San Antonio, TXTR-30 Dec 1 - 2 Orlando, FLQ11/16, Q15/16 Rapp Dec 2 - 5 EuropeQ1/15 Rapp Dec 2 - 5 Geneva, SwitzerlandQ23/16 Rapp Dec 3 - 5 Orlando, FLT1E1 Dec 8 - 12 Sacramento, CAETSI TIPHON Dec 9 - 11 ---

1998 Meeting Schedules are on pg. 19

NOTICE: THE CSR AREA CODE HAS CHANGED TO 650.All phone numbers in the 415 area code south of San Francisco changed toarea code 650 on August 1, 1997. Please change your records accordingly.

Visit the CSR Web Pages:http://www.csrstds.com

The Web Pages include an updated Telecom Acronym Definitions list, updated meeting schedules, a list of web sitesand ftp sites as listed in all issues of CSR journals, background material on telecom standards and CSR (thecompany), sample reports from CSR-T and CSS, data sheets on both CSR technical journals, and more.

Communications Standards Review –Telecommunications (ISSN 1081-4655) is published 8 - 9 timesper year, within days after the latest, related standards meetings. Editor: Elaine J. Baskin, Ph.D. Technical Editor:Ken Krechmer. Copyright © 1997, Communications Standards Review. All rights reserved. Copying of individualarticles for distribution within a subscriber organization is permitted. Subscriptions: $695.00 per year worldwide,$795.00 in electronic format. Corporate Intranet subscriptions and other discounts for additional subscriptions areavailable. Submit articles for consideration to: Communications Standards Review, 757 Greer Road, Palo Alto,CA 94303-3024 U.S.A. Tel: +1-650-856-9018. Fax: +1-650-856-6591. e-mail: [email protected]: http://www.csrstds.com. 18908