COMMUNICATIONS STANDARDS REVIEW TELECOMMUNICATIONS · REVIEW TELECOMMUNICATIONS Volume 9, Number 3 April 1998 IN THIS ISSUE The following reports of recent standards meetings represent

April 1998 Vol. 9.3 Copyright © CSR 1998 1

COMMUNICATIONS STANDARDSREVIEW

TELECOMMUNICATIONS

Volume 9, Number 3 April 1998

IN THIS ISSUE

The following reports of recent standards meetings represent the view of the reporterand are not official, authorized minutes of the meetings.

Rapporteurs Meeting on Questions 4/8 and 5/8, January 12 – 16, 1998, Tinton Falls, New Jersey......................3Q4/8, Document Communication Services.....................................................................................3Q5/8, Color for Telematic applications........................................................................................8

TR-29, Facsimile Systems and Equipment Engineering, February 9 – 11, 1998, Palo Alto, CA..........................10TR-29.1 Facsimile and File Transfer Protocols...............................................................................11TR-29.2 Facsimile Digital Interfaces...........................................................................................14

Study Group 15 Working Party 1, Network Access, February 9 – 20, 1998, Geneva, Switzerland........................17Q1/15 Access Network Transport (ANT)........................................................................................17Q2/15, Characteristics of Optical Systems in Local Access Networks...................................................18Q3/15, DCEs for Digital Leased Circuits.......................................................................................18Q4/15, Subscriber Access Systems..............................................................................................19SG15 WP1 Partial Meeting Roster, February 9 - 20, 1998, Geneva Switzerland.......................................27

ETSI TIPHON Meeting 6, February 17 – 20, 1998, Santa Clara, CA............................................................28WG 1, Requirements................................................................................................................30WG 2, Architecture..................................................................................................................30WG 3, Call control..................................................................................................................32WG 4, Naming, Addressing.......................................................................................................32WG 5 Quality of Service...........................................................................................................33WG 6 Verification...................................................................................................................34ETSI TIPHON Meeting Roster, February 16 – 20, 1998, Santa Clara, CA...............................................37

TR-41 User Premises Telecom Equipment, February 23 – 27, 1998, Albuquerque, New Mexico...........................38TR-41.1, Multi-Line Telecommunication Systems...........................................................................38TR-41.1.9, Multi-Line Telecommunication Systems Support of Enhanced 911 Service..............................40TR-41.2, Conformity Assessment...............................................................................................40TR-41.3, Analog and Digital Wireline Telephones, Joint Meeting with................................................43CSA T-510/IEEE.....................................................................................................................43TR-41.5, Multimedia - Building Distribution Systems......................................................................45TR-41.6, Wireless User Premises Equipment..................................................................................46TR-41.7 Safety and Environmental Considerations..........................................................................47TR-41.7.1 Harmonization of International Safety Standard................................................................48TR-41.8, Commercial and Residential Premises Wiring....................................................................49TR-41.9 Regulatory Considerations on Terminal Attachment Programs................................................49TR-41.10, Private Integrated Service Network (PISN).......................................................................52Partial Meeting Roster of TR-41, February 23 – 27, 1998, Albuquerque, NM...........................................54

TR-30, Data Transmission Systems and Equipment, March 9 – 12, 1998, Dallas, TX......................................55TR-30.1 Modems...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55TR-30.2, Data Transmission......................................................................................................56TR-30.3 Data Communications Equipment Evaluation and Network Interfaces.........................................57

COMMUNICATIONS STANDARDS REVIEW – TELECOMMUNICATIONS

2 Vol. 9.3 Copyright © CSR 1998 April 1998

TR-30 Meeting Roster , March 9–12, 1998, Dallas, TX....................................................................60Q15/16 Update on Compatibility between MPEG-4 Video and ITU-T Rec. H.263...........................................61Acronym Definitions.....................................................................................................................621998 Standards Committee Meeting Schedules as of March 30, 1998..........................................................64



REPORT OF RAPPORTEURS MEETING ON QUESTIONS 4/8 AND 5/8JANUARY 12 – 16, 1998, TINTON FALLS, NEW JERSEY

Q4/8, DOCUMENT COMMUNICATION SERVICES

The Q4/8 Rapporteur is H. Silbiger (Lucent, US). Q4/8 has taken over responsibility for various F seriesdocuments on fax and document communications service requirements which had been addressed within ITU-T StudyGroup 1 during the last study period. Q4/8 is also the question in which all work on Internet facsimile within SG8is pursued.

INTERNET FACSIMILE SERVICE

A new draft service Recommendation on Internet fax (F.Ifax) had been prepared and Determined at the October, 1997SG8 meeting. TF-08 (A. Pugh, UK) contains the latest version of this draft. Since October, various editorialchanges have been made. The term “basic” facsimile terminal was replaced by “standard” facsimile terminal.

TF-18 (L. Masinter, Xerox) was introduced by D. Crocker for the Internet Society (draft-ietf-fax-goals-01.txt). Thecontribution discusses goals and terminology for Internet fax. It is currently in an Internet Engineering Task Force(IETF) working group as “Last Call.” The next step is to forward it for publication as an Informational Request forComments (RFC).

It was noted that there are many similarities between the two contributions, but also some differences. L. Masinter(Xerox) stated that it will be useful to align the terminology used in the two documents and indicated plans to makerelated edits to produce a new version of the IETF Goals and Terminology document. During the course ofdiscussion on store and forward protocol aspects, various points were noted that would result in changes to F.Ifax. Asmall ad-hoc group led by A. Pugh created TF-08rev2, an updated version of the draft recommendation. It wasaccepted by Q4/8.

INTERNET FACSIMILE PROTOCOL

Work has been ongoing on potential standards for Internet fax protocols. The work has been split into two areas: 1)Store and Forward (which includes e-mail), and 2) Real time operation.

STORE AND FORWARD INTERNET FAX

A draft T.Ifax1 recommendation for store and forward Internet facsimile was Determined at the October 1997 SG8meeting, but a list of numerous open items was also compiled to guide additional revisions. There were severalcontributions presented proposing various edits to the base document from the October 1998 SG8 meeting.

TF-04 (M. Lake, UK) contains an updated version of T.Ifax1. It describes three modes of operation: simple, fulland tunneling. It contains edits which have been made since the T.Ifax1 document was Determined. The tunnelingmode is a new addition since the October 1997 meeting and reflects discussions held within the United Kingdom.Annex A is simple mode, Annex B defines full mode, and Annex C defines tunneling mode.

TF-10 (Xerox) is a series of proposed updates to T.Ifax1, using the editor’s latest version as the starting point. Thecontribution results from discussions held in the US TR-29 committee, and includes support for simple mode. Itproposes that full mode be left for further study. Annex A includes references to related IETF work in store andforward Internet facsimile. It was proposed that the full text of various IETF documents be incorporated at this time,but when the documents are published as RFCs, that a direct reference be made to the RFC. Annex A incorporatesthe text from the IETF service document (TF-12) by reference. Annex B on full mode and Annex C are left forfurther study. Portions of Annex A have been moved to a proposed new Appendix A, which contains an example ofTagged Image File Format (TIFF) image coding.

TF-23 (BT) contains proposed updates to T.Ifax1, using the editor’s latest version as a starting point. Thecontribution proposes that full mode be for further study. It also states a preference that tunneling mode not beincluded, since its file format is incompatible with the others contained in the draft Recommendation. Annex Aincludes markups to simple mode. Annex B on full mode is left for further study, but it is noted that this modeshould require support for the simple mode as well.

TF-09 (Japanese manufacturers) proposes that the TIFF-related material in the simple mode description contained inAnnex A be deleted in favor of references to the Tagged Image File Format-Fax (TIFF-FX/TIFFPLUS) material.The conclusion is that Annex A of T.Ifax1 (as contained in the Determined version) is still needed. It suggests that



the TIFF coding example should be included in Annex A. It is assumed that the TIFFPLUS content would beincluded in its full text form within Annex B.

TF-11 (Xerox) provides background information on the edits which were proposed in TF-10 (Xerox), explainingreasons why full mode is left for further study. It reflects related discussions held in TR-29. A series of potentialissues are outlined in areas which could result from the unusual use of mail headers which were proposed in the fullmode annex. Related problems could include security risks due to automated responses on capabilities requestexchanges, generation of unsolicited mail responses, and the release of private information. Other issues notedinclude the need to be able to process Internet Mail failure notices, which are often sent as text messages.

TF-13, TF-14, and TF-15 (all from Internet Society) are current Internet Drafts which define TIFF within the IETF.These contributions were introduced by the co-chairs for the IETF Internet fax working group (D. Crocker and J.Rafferty) on behalf of the Internet Society. (The current versions of the IETF drafts presented in this meeting maybe downloaded from the Internet fax web site at http://www.imc.org/ietf-fax; upon approval and publication, theInternet Drafts will be replaced by RFC references.)

TF-13 (Internet Society) is the draft for the “image/tiff” MIME registration (draft-ietf-fax-tiffreg-04.txt). It refinesthe definition for image/tiff to broaden its use for TIFF and its extensions and introduces a new applicationparameter. TF-14 (Internet Society) defines the F profile of TIFF and its minimum subset (draft-ietf-fax-tiff-08.txt).It is targeted as an informational RFC, primarily to document existing practice. TF-15 (Internet Society) defines sixprofiles of TIFF for Facsimile (draft-ietf-fax-tiffplus-07.txt). It incorporates the technical material from the TIFF-Fdocument and also includes other profiles for the black and white and color file formats. This contribution is targetedas a standards track document and is under a Last Call within the IETF. The contribution also defines two newMultipurpose Internet Mail Extension (MIME) application parameter values, “faxbw” and “faxcolor.”

TF-12 (Internet Society) defines a simple mode for Internet Facsimile via e-mail (draft-ietf-fax-service-03.txt). Thecontribution is a product of the IETF Internet Fax work group and is targeted as a Proposed Standard once complete.It is currently under Last Call within the IETF. It was noted that the use of the term “simple mode” is intended tobe consistent with the use of this term within the ITU-T Internet facsimile work and that the technical content ofthis document is intended to be consistent with simple mode practices. The contribution requires that senders andreceivers support the minimum subset of TIFF-F (S Profile). It was noted that Appendix A on exceptions to MIMEpractices is normative.

TF-16 (Internet Society) defines a format for the incorporation of a Public Switched Telephone Network (PSTN)address format within Internet Mail (draft-ietf-fax-minaddrgen-01.txt). It includes a template on how to generate a lefthand side (LHS) of an Internet e-mail address which includes a telephone number. TF-17 (Internet Society) is arelated document which defines a fax-specific specification of the LHS of an e-mail address (draft-ietf-fax-minaddrfax-00.txt). It contains the details needed to include support for facsimile addresses for purposes of permitting an InternetOfframp to transmit to a Group 3 facsimile device. The syntax includes support for both telephone numbers andsubaddresses. These contributions are both under consideration as IETF proposed standards and they are currentlyunder an IETF Last Call.

TF-19 (IETF) discusses the extended Internet Facsimile operation that is currently under study within the IETFInternet fax working group (draft-ietf-fax-fpim-01.txt). The contribution corresponds roughly to the ITU-T full modeand defines approaches which may be used to achieve these objectives. It builds upon the IETF simple modedocument, but includes additional facilities for capabilities identification and confirmation of receipt. It will permitthe use of any of the profiles within the TIFF-FX document. The contribution is characterized as experimental innature and is still being discussed in the IETF Internet fax working group. The feeling within the IETF group isthat these extensions will be very beneficial in doing prototype implementations prior to completing thestandardization of this level of functionality. Provisions are also made to handle capabilities expression, capabilitiesexchange and a “direct connect” session mode for Internet facsimile.

TF-22 (Canada) includes comments on Internet fax. It recommends that there be efforts made to ensure that theresult of work on Internet fax by the ITU-T and IETF result in a single set of standards, and that it is essential thatthe work of the two groups does not diverge. It proposes that the IETF documents on simple mode, TIFF imageformats and addressing be incorporated by reference or as joint text. Relevant documents from TelecommunicationStandardization Advisory Group (TSAG) on how to do references of IETF documents within ITU-T recommendationsare up for approval at the January, 1998 TSAG meeting. Technical editor’s note: The procedures to reference formalIETF documents in ITU Recommendations were approved.



TF-26 contains an ASN.1 description of the T.Ifax1 fields which have been defined in the draft Annex B from theOctober 1997 version. The contribution is targeted to fulfill one of the open items from the October 1997 meeting.

It was concluded in discussion that full mode should be marked for further study, so that the focus of the work tofollow should be on completing simple mode within T.Ifax1.

H. Silbiger (AT&T, US) concluded that the Q4/8 delegates should review T.Ifax1 section by section and decide whatneeds to be done with it, starting with the Determined document and using the contributions as input. The basedocument is the one which was attached to the October 1997 meeting report. He noted that the ISOC (InternetSociety) contributions could be noted as source material for potential reference.

The review of potential revisions to the base text of T.Ifax1 as proposed by TF-10 (Xerox) and TF-23 (BT) wasbegun.

The Summary and Scope from the base document were accepted with minor modifications based on TF-10 (Xerox).Two of the overview items outlined in TF-10 (Xerox) will be considered for inclusion in F.Ifax, since they areservice related. After some additional review, it was decided that the remainder of the main body of the T.Ifax1 textwould be addressed in an ad-hoc group.

There was some review on the contributions regarding Annex A (TF-09 (Japanese manufacturers), TF-10 (Xerox) andTF-23 (BT)). There was also the question on whether the material in the IETF Service document (TF-12) could beincorporated as is. It was agreed that TF-12 (IETF) would be reviewed in detail for potential incorporation viareference as proposed in TF-10 (Xerox). In TF-12 (IETF), it was also noted that the Addressing section (3.3) in theService draft really applied only to the case of Offramps, and that the title of the section should reflect this specialcase. There was then a detailed discussion on the Security requirements outlined in Section 5 of the Service draft. Itwas eventually concluded that this section would be informative, rather than normative in the ITU recommendation;Q4/8 agreed to review the section further within the ad-hoc group to see whether portions should be moved to anormative part of the text.

TF-31 is the resulting report from the ad-hoc group on T.Ifax1 (Store and Forward Internet Fax). The ad-hoc groupagreed on an updated version of T.Ifax1, which is contained in TF-32 (M. Lake, UK). TF-33 is a list of commentsto be sent back to the IETF on how to improve the IETF draft contained in TF-12 to better meet the ITUrequirements. This will facilitate reference of the final version of the Service RFC T.Ifax1. TF-33 was accepted byQ4/8. TF-31, the ad-hoc meeting report, was also accepted, subject to revisions noted by the ad-hoc chair.

The updated draft of T.Ifax1 (TF-32) specifies that there will be two modes for Internet Facsimile, a simple mode anda full mode. The definition of simple mode specifies that the procedures for simple mode are defined by sections 2-4of the planned RFC (final IETF version of TF-12), where those sections of the RFC shall be incorporated byreference. The image file format and addressing mechanisms are also defined in planned RFCs which shall be incor-porated by reference. The contribution also marks full mode for further study, but includes a functional summary ofprocedures and related references. There are two new informative appendices:• Appendix A provides a list of implementation requirements• Appendix B provides an image file format coding example

It was noted during review that some additional small revisions were needed within the new Appendix A. It wasagreed that a small ad-hoc group would address the necessary changes with the editor.

During the plenary session on the final day, the updated version of T.Ifax1 (TF-32 Rev1) was presented and accepted.The summary for T.Ifax1 is contained in TF-38 (M. Lake), which was also accepted. The final versions of thesedocuments will be forwarded by the Rapporteur to the ITU-T TSB for translation and eventual circulation via letterballot.

REAL TIME INTERNET FAX

A draft T.Ifax2 for real-time Internet Facsimile had been Determined at the October 1997 SG8 meeting, along with alist of open items that need further work.

TF-05 (Q4/8 Rapporteur) is a revised draft T.Ifax2 on procedures for real time Group 3 communication betweenterminals using Internet Protocol (IP) networks. It contains a plan on how to complete the various open itemswhich had been identified at the October 1997 meeting. The call control material has been moved from the mainbody to a new Annex A for purposes of editorial clarity. It is noted that considerable work has been done on addingnew material which defines a forward error correction mode for use with the User Datagram Protocol (UDP) method.



TF-05, then, contains the current draft of T.Ifax2, with a combination of some agreed material and some which hadnot yet been agreed, notably some of the additional technical work on a UDP compatible mode.

D. Duehren (Brooktrout) conducted a review of TF-05, noting that work had progressed in the following areas:

1. Appendix I - expanded session examples (needs slight updating)2. Annex A - includes call progress information moved from the main body3. Additions to Annex B4. Section 8 - This is the new material related to the UDP mode. D. Duehren notes that this material is not yet

agreed and in some respects are inconsistent with previous agreements reached in Geneva. Therefore, furtherdiscussion is required before this material can be accepted.

Two contributions which include an ASN.1 representation of the coding for T.Ifax1. TF-06 (Deutsche Telekom)derives an ASN.1 expression, but it is based on an earlier draft. H. Detlef Schulz (Deutsche Telekom) reviewed TF-06 (Deutsche Telekom). He acknowledged that the coding was based on a T.Ifax2 draft from December 1997.Within this contribution, the T.Ifax2 parameters have been extracted and then expressed using ASN.1 encoding. Inaddition, where type-length encoding had been used in parameters, it was eliminated in favor of the standard ASN.1encoding which automatically defines the lengths. It is included in Annex B.

TF-07 (Brooktrout) provides more detail for the data-field parameter. Both contributions proposed that the lengthencoding be based on the ASN.1 conventions. It was agreed that the details on ASN.1 presentation and codingshould also be reviewed in the ad-hoc group. The intent of TF-07 (Brooktrout) was to bring the coding from TF-06(Deutsche Telekom) up to date, but D. Duehren felt that the structures needed to be reviewed for technicalcorrectness. At this time, the expression of the coding is defined using ASN.1, but the actual coding of the datastream is not based on ASN.1. It was suggested that consideration should be given to using ASN.1 structures toencode the data as well, since it has a built-in method for doing the value-length encoding that is a required for en-coding fax information into a packetized form.

The new UDP Proposals contained within TF-05 (Q4/8 Rapporteur) were then reviewed. This proposal introduces anew Forward Error Correction method, which provides additional protection against errors. There are new signalswhich are also introduced, to notify the gateway about various situations. A. Ronen (Israel) expressed concern aboutthe use of a new protocol for UDP, which he felt was not consistent with the agreements from the October 1997meeting.

TF-21 on packet multimedia, H.323, is from D. Skran (Ascend), the Q13/16 Rapporteur. He notes that H.323 canmake use of either UDP or Transmission Control Protocol/Internet Protocol (TCP/IP). There is also a question onwhether Real Time Transport Protocol (RTP) adds value for facsimile. The contribution requests that one of theH.323 modes for real time Internet fax be designated as the mandatory “interoperability” mode. There is also arequest that there be interoperability between H.323 voice/fax devices and T.Ifax2 devices using CALL_REQ. It issuggested that this can be accomplished by adding a new annex to H.323 which establishes the availability of realtime fax modes during H.245 capability negotiations.

There were differences of opinion between the delegates on whether a UDP or a TCP/IP mode both needed to beincluded within T.Ifax2, and if both are included, which should be the default mode.

D. Skran noted that H.323 in theory does not require either UDP and TCP/IP. He felt that support for both TCP/IPand a datagram protocol (UDP) are practical requirements for H.323 applications. D. Skran’s key point was thatboth TCP/IP and UDP are also needed for real-time fax and that SG16 will want the fax experts to define which ofthese modes will be the “base mode” for H.323 compatible applications. It was agreed that the details of the pro-tocol layering discussion should be addressed in an ad-hoc group.

D. Skran reviewed the key points from TF-21, which comments on TF-05. The following two proposals wereaccepted by Q4/8:

• 1a, Modify the text to remove any language that implies that H.323 must be used with any one protocol.• 1b, RTP is not needed, unless there is a technical reason to use it for fax.

D. Skran reiterated the request that either UDP or TCP/IP be established as the base mode for H.323 Internet faxoperations. He noted that SG16 needs an opinion on this prior to the upcoming meeting (January 26 - February 6,1998). It was agreed that this request should be discussed in the ad-hoc group. He also suggested that there shouldbe interoperability possible between H.323 fax/voice devices and T.Ifax2 devices by using common call setupapproaches. The current area of conflict is in the call request: the H.323 fast call setup could be a useful approach,



which is an alternative to the usage of CALL_REQ contained in the current T.Ifax2 draft. By taking this approach,the fast call setup approach could be used, eliminating the need to use the more complex “full” H.245 call setupmethod. D. Duehren (Brooktrout) expressed concern about what would happen in the event that various analogsignals are received. These are beyond the scope of what will occur in the ISDN environment.

In response, D. Skran noted that the Q.931 does convey all the various capabilities used in digital signaling withinISDN. He thinks that if the T.Ifax2 messages have the same structure as the H.323 setup messages, this would beuseful, and that possibly some fax specific extensions to the Q.931 approach could be specified. He wants to avoid ascenario where real time fax devices will NOT be interoperable with the next generation of H.323 (i.e., version 2).He suggested that the group could send feedback to the SG16 group regarding potential signaling extensions toH.323, if necessary.

TF-22 (Nortel) makes some comments on real-time Internet fax. Presenter G. Parsons notes that the MMUSICIETF working group is thinking about beginning work on a real time fax protocol. Parsons suggested that the out-put of this meeting should be posted into the IETF ID archive and that the MMUSIC (IETF, MultipartyMUltimedia SessIon Control) WG be notified about the status of the real time fax work.

An ad-hoc group chaired by D. Duehren (Brooktrout) was established to address the open issues and update the text ofthe draft T.Ifax2. The report of the ad-hoc group is TF-34. TF-35 is the updated T.Ifax2. Some key agreementsincluded:

1. A single protocol will be used for UDP and TCP/IP applications.2. The base mode will be TCP/IP based; the UDP mode is optional and has an optional error correction mode.3. The ASN.1 coding has been completed; ASN.1 will be used for both representation of the expression and as the

means by which to provide length-value encoding.4. A new annex to H.323 will be written which includes the call setup requirements for real time Internet fax.

D. Duehren (Brooktrout) was appointed as editor of T.Ifax2. Section 2.2 on call setup of Annex B is not yetcomplete. It is noted that some small additions to the text are needed. The plan is to complete the editing of T.Ifax2per the editorial instructions to be contained in the Q4/8 meeting report. T.Ifax2 (TF-35) was provisionally acceptedon this basis, subject to final edits. The resulting document will be posted on the ITU Internet fax reflector. Theresults of the ad-hoc group (TF-34) were accepted. TF-28 is the summary of T.Ifax2, which was also accepted.

In order to complete the requirements for H.323 interworking, further work is required on Annex B of T.Ifax2. Thecurrent plan is to prepare an updated Annex B for submission as a contribution to the June 1998 SG8 meeting and toDetermine and “freeze” the text of this T.Ifax2 amendment at that time.

OTHER BUSINESS

TF-02 (Sagem) proposes that there is a need to indicate support for Internet fax capability on the PSTN within theT.30 protocol. It also suggests that there is a need to be able to support Internet mail addresses.

TF-03 (Sagem) proposes that there be a direct notification of fax mail transmission by creating a new T.30 framewhich would be sent by the transmitter.

TF-24 (Canon) proposes that there be additions of bits to the Digital Identification Signal (DIS) to support a seriesof possible combinations of Internet fax modes. The contributor verbally suggested that only 3 bits were needed torepresent all of the possible combinations (rather than the 4 which are proposed in the contribution).

TF-25 (T. Maeda, Canon) proposes that three new frames be added to T.30 to indicate an e-mail address for thefacsimile terminal. It is suggested that the maximum number of characters needed is 72 characters, based on RFC822. Y. Yoshiura (Canon) noted that the direct entry via the DIS method proposed in the contribution would not beacceptable to the Japanese manufacturers, as per agreements reached in previous SG8 meetings.

In discussion, there was support for the idea of representing capabilities of Internet fax and Internet addresses withinT.30. D. Crocker (IETF) stated that he is not aware of a formal limit to the length of the e-mail address. It wassuggested that it might be possible to get agreement on some technical matters at this meeting and include this asDetermined material as modifications to T.30. It was noted that some national bodies might raise objections to thisprocedure, since this is not a Working Party meeting. It was agreed that an ad-hoc group would be established andchaired by M. Lake (UK) to consider the contributions and related amendments to T.30 to support Internet facsimilecapabilities and Internet addressing.



The report from the ad-hoc group is contained in TF-37. The group agreed on a proposal to add 3 bits to the T.30protocol in order to support the indication of Internet fax capability for the three modes which are under considerationwithin the ITU-T, although some delegates expressed reservations. The ad-hoc group also believed that the conceptof exchanging Internet addresses via the T.30 protocol has value, but there are many technical details which need tobe considered further; contributions are invited. The issue of notification was also reviewed, but appeared to be quitecomplicated in practice, and some delegates did not think this approach should be included within T.30. Furthercontributions are invited on this matter.

TF-36 (T.30 editor) defines the addition of 3 bits into T.30. Some delegates expressed reservations, but in theinterest of progress, it was agreed that the contribution could be included in the amendment to T.30 that was underpreparation for submission to the ITU TSB for translation and circulation.

In other matters, some Q4/8 delegates expressed an interest in taking steps to enable the IETF and ITU to have amore formal relationship. The Rapporteur suggested that a next step would be for ISOC/IETF to make a request tothe ITU for liaison status. Contributions regarding this matter are invited for the next SG8 meeting.

LIAISONS AND COMMUNICATIONS

TF-33 (Q4/8 Rapporteur) is a proposed communication is to be sent to the IETF Internet Fax working group onrequested changes to several RFCs. It was agreed that the Q4/8 Rapporteur will put the text will into letter form andsend it.

TF-39 is the meeting report for Question 4/8.

Q5/8, COLOR FOR TELEMATIC APPLICATIONS

Question 5/8 studies the use of color in telematic applications, the best known of which is facsimile. TheRapporteur is L. McIntyre (Xerox, US).

The main action item for the meeting was to review a proposal to modify the T.44 Recommendation on MixedRaster Content (MRC) as approved in October 1997 in order to incorporate an enhanced multiple layer model.

M IXED RASTER CONTENT

At the last SG8 meeting, the T.44 recommendation and related amendments to the T.4 and T.30 recommendationswere approved. They provide support within Group 3 facsimile for an MRC model which supports imagedocuments which may include various components such as continuous tone color and text. Several contributionswere introduced at this meeting on a concept for extending the MRC model to support more than three layers.

TF 5-1 (L. McIntyre, Xerox) proposes a new extension to enable a multiple layer MRC concept. The main reasonfor the proposal is to be able to gain additional efficiencies for some types of images. The main reason for goingbeyond three layers within the MRC model is to handle the case of overlapping images. One of the key functions ofthe main mask layer (layer 2) is to define the bounds of the page. This approach was accepted as the model for theextension to MRC.

TF 5-2 (renumbered from TF-27, A. Pugh, T.30 editor) shows the proposed allocations to T.30 protocol bits withinTable 2 in going from Amendment 2 to Amendment 3. The contribution contains a series of proposed bit alloca-tions, and there is some discussion on whether changes are needed to either Amendment 2 or Amendment 3. At theQ5/8 meeting, the Rapporteur suggested that three contiguous bits are needed for MRC. It was agreed that bits 92-93 should be moved to the beginning of the next octet in order to keep the three MRC related bits together.

TF 5-3 is a draft Annex A to T.44, which shows markups which would support the addition of a multiple layermodel into MRC.

A working document (provisionally numbered TF 5-4) is an updated version of draft Annex A which reflects thediscussion from earlier in the meeting. It updates the version which was submitted as TF 5-3. There was a questionon whether any limits to the number of layers should be made, but no decision has been made. There are somestructural issues that still need to be studied, along with the aspects of marker segments. Guidance from WG1 willbe requested on the layer structure. It was suggested by the Rapporteur that the updated contribution can be targetedfor Determination at the June 1998 meeting. Since this contribution was later declared a working document, it isnot one of the official documents considered within the meeting.



M. Matsuki (NTT) had some comments related to TF-15 (the IETF TIFFPLUS draft). He noted some pointsregarding values in the table. The Rapporteur requested that the comments be forwarded to the ITU internet faxreflector and the ietf-fax reflector.

TF 5-5 is the latest updated draft Annex A which extends Mixed Raster Content to handle multiple layers. Indiscussion, L. McIntyre (Xerox) proposed to seek revision to the main body of T.44 on the “Layer Data Structure”prior to its publication. He noted a potential need in the future to be able to support compression methods which donot have their own headers and believes the provisions to satisfy this need should be in the base mode of MRC aswell as in its extensions.

TF 5-6 contains amendments to draft Annex A of Recommendation T.44 and to the main body of therecommendation. The Layer data structure is being updated to permit the addition of a Start of Layer Data (SLC)marker segment for the case where the coder being used does not itself contain a header.

The Rapporteur noted that T.44 is awaiting publication while Association Française de Normalisation (AFNOR) isregistering the new marker segments contained within T.44. Q5/8 agreed that the Rapporteur will be authorized torequest that the TSB amend the version of T.44 which has not yet been published in order to include theclarifications to the main body of Rec. T.44 as contained in TF 5-6.

The remainder of TF 5-6 contains an updated draft Annex A to T.44 which incorporates the agreed editorial changesfrom this meeting (text is shown without markups). Various editorial markups were noted. Table 3 in the annexwill be deleted. The equivalent table in the base mode will be augmented and it will be stipulated that only the firstthree layers are valid in the base mode.

It was proposed that draft Annex A within TF 5-6, as amended, will be forwarded to the ITU meeting in June forDetermination.

The Rapporteur also noted that the annexes related to this within T.4 and T.30 should be reviewed for possiblerevisions.

TF 5-7 (Q5/8 Rapporteur) contains the final meeting report for the Q5/8 meeting.

AGREEMENTS REACHED

• The method proposed in TF 5-1 to extend the MRC model was agreed.• The T.30 bits in Table 2 will be re-ordered in the amendment to T.30 that is about to be published so that the

MRC capability bits will not be split up by extend bits.• A separate document, TF 5-8, will be created; it will contain only the “editorial corrections to T.44 prior to

publication.” The Rapporteur will forward it to the TSB.• Draft Annex A which extends MRC to handle multiple layers (TF 5-6) will be submitted to the June 1998 SG8

meeting for Determination.

James Rafferty, Human Communications



REPORT OF TR-29, FACSIMILE SYSTEMS AND EQUIPMENT ENGINEERINGFEBRUARY 9 – 11, 1998, PALO ALTO, CA

X3L3 L IAISON

X3L3 met in San Jose in January. There is work beginning on Joint Photographics Expert Group (JPEG) 2000.The focus is on continuous tone images. L. McIntyre (Xerox) noted that a proposal was introduced at the X3L3meeting to use the Mixed Raster Content (MRC) architecture as the architecture for JPEG 2000 and it was supportedby the US group. As a result, this position will be brought into the next JPEG meeting to be held in March inGeneva, Switzerland.

ISO/IEC/WG1 JPEG LIAISON

There was a JPEG meeting in Sydney in December 1997 in which tests were conducted for numerous algorithms.The method which performed the best was a wavelet algorithm which also was refined using trellis encoding. TheJPEG LS (lossless and near lossless) is further advanced and is in the final approval stages.

ISO/IEC/WG1 JBIG LIAISON

Joint Binary Image Group (JBIG) also met in December 1997. L. McIntyre (Xerox) noted that there is still work inprocess to work on JBIG 2. The approach is targeted toward efficient compression for text and related images. Atthe December 1997 meeting (also in Sydney, Australia), this group suggested to the JPEG group that therequirements for efficient handling of text be considered, but no action was taken. JBIG-2 is not likely to becompleted until 1999.

TSAG LIAISON

S. Perschau (National Communications Systems, NCS) reported on the January 1998 ITU-T TelecommunicationStandardization Advisory Group (TSAG) meeting. The focus was on Electronic Document Handling (EDH) andworking methods within the ITU-T. There have been changes to add power outlets and lockers for PCs at the ITU.

Some of the following enhancements are planned to the EDH facilities of the ITU:• There will be the ability to submit a document via the Web; this is targeted for first quarter.• There will be additional Web based access to the informal File Transfer Protocol (FTP) area. Some study groups

have put TDs in the informal area during the study group meetings.• There will be web-based access to Telecom Information Exchange Services (TIES) e-mail address.• In Geneva, the delegates will be asked if they want to use a local International Standardized Profile (ISP) for the

duration of the meeting.• There will also be Local Area Network (LAN) connectivity provided in the future, perhaps by wireless.• There will also be Web-based chat facilities.• They are also expanding video conferencing capabilities.

At the last SG8 meeting, all of the documents were available on-line in the informal FTP area. RecommendationA.4 has been approved, which includes the new annex allowing reference of IETF RFC (Request For Comments)standards. There are also additional steps being taken to provide better ITU-T access by organizations like TIA.

In June 1998, when a document is Determined, a copy of the summary and the table of contents will have to beprovided. In a study by a member of the EDH department of the ITU-T, it took about 6 months on average to postnew Recommendations once approved. There is a plan to make available the white contribution and relatedtemporary documents very quickly after the meeting and these will be available to subscribers to the on-line service.These will be editor’s versions; the final versions will typically be different.

The ITU patent policy is still in flux. One possibility is that patent statements might be required for allcontributions. TSAG is sending out liaisons to all of the study groups indicating that they will be permitted tomake substantial technical changes to Determined documents in rapporteurs meetings. The Study Group does needto have a clear plan of work for such changes. However, the interpretation of the plan in the United States is thatthere will be a need to have documents at the Determination meeting which address the technical changes needed, inorder for substantial changes to take place. S. Perschau (NCS) suggested that a process for a case where there is adefect in a document would be to submit corrections in the form of a white contribution.



COLOR FAX

TR-29/98-02-03 (L. McIntyre, Xerox, Q5/8 Rapporteur) is the Tinton Falls Q5/8 meeting report (see report inthis issue of CSR-T). Q5/8 developed a draft Annex A for Mixed Raster Content (MRC) which will support amultiple layer model. The resulting document is targeted for Determination at the June 1998 SG8 meeting.

HF RADIO FAX

It turns out that there is a difference between common practice and TIA-688, HF Radio Fax, which has beenpublished. S. Urban (Delta Information Systems) thinks it can be handled via a default ballot.

TEST CHARTS AND TEST IMAGES

The IEEE has now released test charts for facsimile which are consistent with those previously standardized by theITU.

EXTENDED NEGOTIATIONS

TR-29/98-02-04 (same as TR-29.1/97-08-41R2 , J. Rafferty, Human Communications) is Draft Annex X onextended negotiations. It was suggested that the contribution be submitted without markups. It was also agreed thatthe final version of the document should be circulated to TR-29 members for review prior to the US Study Group D(SGD) meeting.

TR-29/98-02-05 (revision of TR-29.1/97-10-73) (D. Duehren, Brooktrout) discusses T.privateuse. The PrivateUse tag includes a length field to allow devices only accepting standard transmission (e.g., DCME) to “skip” theprivate field. It will follow the same circulation procedure as draft Annex X. Both documents were supported by themembers as proposed white contributions to SG8 which will be submitted for review in SGD.

INTERNET FAX

H. Silbiger (Applicom) moved that TR-29 support the Internet fax RFCs referenced in T.Ifax1(store and forwardusing TIFF profile S) to go forward as white contributions from the Internet Society (ISOC). Four of the referencedRFCs (file format, address format [2] and TIFF profile S) are still in the process of IETF standardization. There wasdiscussion on the procedure to be followed. After discussion, the motion was supported.

S. Perschau (NCS) suggested that the process should be as follows: The RFCs, once published, should be sent toS. Urban (TR-29 chair) for circulation among TR-29 members for review. If there is support for the RFCs amongthe members, S. Urban can forward them to D. Bodson (NCS), noting that TR-29 supports the documents to goforward as Internet Society documents. The documents could then be circulated among Study Group D members tosee whether SGD will support the documents being submitted.

Reporter’s note: During the meeting, S. Perschau (NCS) indicated that ISOC (Internet Society) ITU contributionswould need to go via SGD. It turns out that ISOC is an international member, so its contributions do not need togo via SGD.

TR-29.1 FACSIMILE AND FILE TRANSFER PROTOCOLS

LIAISON REPORTS

IETFJ. Rafferty (Human Communications) reported on the Internet fax work within the Internet Engineering Task Force(IETF). IETF held a meeting in December 1997 at which directions on the three main components of the simplemode of store and forward fax were established. The three main components were a service description for the simplemode of store and forward Internet fax, file image formats (TIFFPLUS) and addressing for Internet fax offramps. Thedocuments are under consideration by the Internet Engineering Steering Group (IESG) to complete the approvalprocess.

ITU-T Quest ion 4/8 MeetingH. Silbiger (Applicom) reported on the January Q4/8 meeting (see the report in this issue of CSR-T). Agreementswere reached on updated text for three draft recommendations:

• T.37 - Store and Forward Internet fax (formerly T.Ifax1, TR-29.1/98-02-08)• T.38 - Real Time Internet fax (T.Ifax2, TR-29.1/98-02-09)• F.185 - Service Recommendation (F.Ifax1)



The work from TR-29 on store and forward Internet fax as discussed at the last meeting was submitted in the form ofcontributions from Xerox; many of the proposals in these documents were accepted as updates to draft T.Ifax1. Akey result was that agreement was reached to reference the IETF Service document as the definition of procedures forthe simple mode of store and forward Internet fax. “Full mode” from the original T.Ifax1 was deleted and the sectionhas been marked for further study. Some guidelines on directions for full mode have been included in the currentdraft, pointing to future requirements for file format, capabilities negotiation and confirmation of receipt. The detailsare not yet defined.

Contributions were received on how to represent an Internet fax capability; there was agreement to include three newDigital Identification Signal (DIS) bits related to this. There were additional contributions on Internet addressing forwhich no agreements were reached.

Study Group 7S. Perschau (NCS) reported on SG7. SG7 made a request that SG8 forward two recommendations to them. SG7 issending a liaison to various study groups on the status of the old ASN.1 recommendations; SG7 is offeringassistance to convert references to use the updated versions of ASN.1. The contact e-mail address is [email protected](B. Scott).

SG13H. Silbiger (Applicom) noted that SG13 is working on fax over Asynchronous Transfer Mode (ATM). T. Lyons(Lucent) is sending a contribution to SG13 requesting that there be interaction with SG8.

TSAGThe ITU-T TSAG has decided to reject the proposal from SG8 that SG8 take over the X.38 and X.39 “FaxPad”Recommendations; they will continue to be under the control of SG7.

INTELLECTUAL PROPERTY

Per current TIA policy, a request was made to determine if attendees were aware of intellectual property rights (IPR)associated with committee work. The status of IPR was noted as follows:

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. There is IPR onthe T.30 security page from France Telecom and on public key management from Public Key Cryptosystem (RSA).

DIRECTIONS FOR FUTURE WORK

TR-29.1/98-02-03 (D. Duehren, Brooktrout and J. Rafferty, Human Communications) discusses considerationson the evolution of fax. The contribution was developed to serve as a basis for discussion on future directions ofwork that should be pursued by TR-29.1. The contribution notes that fax is at a point where both telephonenetwork and IP networks are to be used for fax.

During discussion, it was agreed that the focus of fax is on document communications. TR-29.1 listed severalfeatures where fax has advantages for communication, including backward compatibility, ease of use, a guaranteedleast common denominator, immediacy of communication and immediate receipt.

There was also a discussion on why users are moving to e-mail for some applications. Advantages which were notedinclude immediacy, delivery at the desktop, ease of reply and ease of distribution.

There was a further discussion on applications. Two applications were considered as example cases: color fax andmulti-function devices. For color fax, requirements include color scanning, color printing and the ability to transfera large amount of data in a timely manner. J. Dahmen (Lanier Worldwide) suggested that the engines for MFPdevices are moving toward scan and print engines, replacing the fax engines which were formerly used. It was notedthat one of the limitations of using the fax protocol for higher speed is the need to update the protocol support in thedevice to support new facilities such as V.34 fax or T.30 Annex C (duplex) fax. The TCP/IP protocols do not haveto be upgraded in order to be able to run at higher data rates.

There was then a review of four possible options for enhanced operation:

1. Extend T.30 native (over PSTN)2. Extend IP native3. Run T.30 over IP4. Run IP protocols over T.30



There was discussion on the advantages and disadvantages of these approaches. One advantage of PSTN extensionsis that they will continue to get the benefit of the PSTN inertia. However, the IP modes are now gaining the benefitof the tremendous marketplace momentum of TCP/IP solutions. The IP-based solutions will also need to deal withfirewall issues. After much discussion, the consensus of the group was that both the PSTN fax approaches and IPapproaches are likely to both be in place for some time to come, so it makes sense to continue working on faxextensions over both the PSTN and IP networks.

TR-29.1 felt it would be useful to have the set of capabilities that are negotiated be the same in the PSTN and the IPenvironments. There is also the question of whether it is possible to use the same means in both cases for“expression of capabilities.” It was noted that in the PSTN environment, extended negotiations provides a way ofexpressing content. It is too early to say if the methods of capabilities expression in the two environments would bethe same or different.

The results of the ad-hoc meeting are summarized in TR-29.1/98-02-11 . The document also includes someadditional related comments from D. Duehren (Brooktrout).

PN-3675, EXTENDED NEGOTIATIONS

TR-29.1/97-08-41R2 (J. Rafferty, US) is an updated draft Annex X to T.30 on extended negotiations. Thecontribution has the following changes from previous versions: 1) Additional revisions to flow charts 2) Proposalon return to traditional negotiations from extended negotiations. This is to resolve the issue raised at the October1997 SG8 meeting: how do two fax devices without common capabilities in extended negotiations fallback totraditional DIS/DCS negotiations. It was noted that some ITU delegates have requested that the updated version ofthe Annex be submitted as a white contribution. TR-29.1 discussed the contribution and what it will take toproceed.

The current applications that have been identified are Binary File Transfer (BFT) negotiations and private use. As aresult, it was suggested that the T.privateuse document from the last SG8 meeting be reviewed to see if it could befinalized for submission as a white contribution.

It was also envisioned that the following documents should be prepared as delayed contributions:

1. Re-submission of Phase B version of BFT negotiations2. Re-submission of amendments to main body of T.30 needed to support ENP (Extended Negotiation Procedure).3. Paper which summarizes potential applications of ENP.

H. Silbiger (Applicom) noted that it would be useful to prepare a short paper which re-visits what ENP will do andwhy it is important to proceed. This contribution would serve as an introduction to all of the other documents.

TR-29.1 supported the plans to produce the documents proposed. An ad-hoc meeting was set up to review technicaldetails of the draft Annex X and review requirements needed to put T.privateuse into the form of a white con-tribution. It was agreed that the completed documents would be reviewed by TR-29 prior to forwarding them asproposed US contributions to SG8 via Study Group D.

PN-3799, I NTERNET FAX

The current draft recommendations for Internet fax were provided for information. TR-29.1/98-02-09© is draftRecommendation T.Ifax2 from the Q4/8 Rapporteurs meeting in January 1998. It defines procedures for real timeGroup 3 fax over the IP networks.

During discussion, M. Spann (Dialogic) suggested that it would be useful to add the ability to negotiate buffer sizes.D. Crocker (Brandenburg) noted that some routers will now refuse to accept current types of packets that exceed acertain size. D. Duehren (Brooktrout) will look at adding the following items to Annex B of T.Ifax2:

1. Fill bit removal and regeneration,2. Transcoding to and from Modified Modified Read (MMR) and JBIG for the transport over the IP network,3. Advertisement of maximum buffer size.He will also look at adding some information on flow control to section 7.

TR-29.1/98-02-10 (H. Silbiger, Applicom) contains a liaison statement from SG16 in response to requests fromthe Q4/8 Rapporteurs group regarding the potential use of H.323 for real time Internet fax. The liaison indicates thatthe fast connect mode of H.323 was Decided at the February 1998 SG16 meeting and an annex defining a real timefax mode of H.323 using T.Ifax2 was Determined at the same meeting. It was noted that the timing of the Q11/16,and Q9/16, Q12/16, Q13/16, Q14/16, and Q18/16 Rapporteurs meetings coincide with the next SG8 meeting.



TR-29.1/98-02-07© is draft Recommendation F.Ifax from the January 1998 Q4/8 meeting. It defines guidelines forthe support of facsimile over the Internet.

TR-29.1/98-02-08© is draft Recommendation T.Ifax1 from the January 1998 Q4/8 meeting. It defines proceduresfor Internet facsimile via store and forward operations.

TR-29.1/98-02-06 (Same as TF-37 from the Q4/8 Rapporteurs meeting) is a report from an ad-hoc group onchanges to T.30 for Internet fax. The Q4/8 meeting agreed to support the addition of three new bits to DigitalIdentification Signal (DIS) to indicate Internet fax capabilities, although there were reservations about this fromsome delegates. There was also discussion in the Rapporteurs’ ad-hoc meeting on the addition of support for Internetaddresses within T.30 frames. During discussion at this (TR-29.1) meeting, M. Spann (Dialogic) suggested that itwould be a natural development to use the DIS bit indications as a way to indicate a need to do things like relaxtimers. This led to a discussion on possible ways to implement a session mode of IP fax; it was concluded thateither an Extended Simple Mail Transfer Protocol (ESMTP) stack or T.30 stack could be extended to do this.

There was some question on the extent to which the Internet fax facilities should be added into the T.30 protocol.TR-29.1 felt that this should be studied. It was noted that the type of information needed for Internet fax is likely toinclude variable length data, a substantial amount of capabilities data and multiple stage negotiations and thus isconsistent with some of the original design goals of extended negotiations.

PN-3364, ENHANCED BINARY FILE TRANSFER

TR-29.1/98-02-04 (J. Rafferty, Human Communications) is a proposed amendment to Annex B of Rec. T.30which adds a definition of the Phase C method of BFT negotiations and refines the definition of the File DiagnosticMessage (FDM) frame. TR-29.1/98-02-05 (J. Rafferty, Human Communications) is a proposed amendment toAppendix D of T.30, which provides session examples for BFT and BFT negotiations. These versions were sub-mitted to the ITU, and have since been incorporated in a single document on amendments to T.30 (produced by T.30editor A. Pugh, MGCS, UK). The contributions were presented for information.

J. Rafferty (Human Communications) suggested that the contributions defining the Phase B method of BFTnegotiations should be submitted again as delayed contributions out of the May 1998 TR-29 meeting.

In discussion, V. Cancio (Xerox) noted that Xerox desires that there be a least common denominator for a binary fileagreed as part of an ITU standard for BFT and BFT negotiations, for example, that a particular binary file type suchas Postscript or Portable Document Format (PDF) be agreed as a minimum requirement for a specific BFTapplication. J. Rafferty (Human Communications) noted that the G5 messaging concept also supports the idea of aleast common denominator format for various types of documents and multi-media.

SP-3826, B INARY FILE TRANSFER

D. Duehren (Brooktrout) reviewed the Industry ballot version of SP-3826, TIA-614-A (BFT for G3). It containsT.434 version 2 and also includes the implementor’s guide material. The ballot closes March 5, 1998.

TR-29.2 FACSIMILE DIGITAL INTERFACES

ITU-T LIAISON

H. Silbiger (Applicom) noted that V.pcm has been Determined (as V.90). He stated that there may be a need to havefax DTE/DCE interfaces to support this in the future.

MFPA LIAISON

There are some Multi-Functional Peripheral Association (MFPA) members who wish to initiate activity related tointerface specifications. However, there has not been agreement within the MFPA to proceed. V. Cancio (TR-29.2chair) noted that HP had made another presentation at MFPA recently, which was more extensive than previouspresentations. However, there still seems to be confusion on their part on what it will take to support fax. V.Cancio noted that the IETF IPP (Internet Printing Protocol) approach still requires drivers, whereas the JetSendinitiative from Hewlett Packard is a driverless architecture.

IEEE LIAISON

L. Farrell (Canon) reported on the current status of the balloting for the latest IEEE 1284.3 and 1284.4 initiatives.It appears that IEEE 1284.4 has further editing that is required (editor B. Batcheldor, Hewlett Packard). Microsoft has



expressed interest in the specification. It was noted that there is still a need for fax interfaces that can work withUniversal Serial Bus (USB) and Firewire (IEEE 1394) interfaces.

ECTF LIAISON

J. Rafferty (Human Communications) reported on the status of the Enterprise Computer Telephony Forum (ECTF)work. S.100 rev2 is undergoing final editing related to a ballot cycle. There is also an S.200 specification that per-mits S.100 function calls to be wrapped up to be communicated in a Client Server environment. J. Dahmen(Lanier) noted that Japan is rapidly going in the direction of requiring digital interfaces instead of analog interfaces, asdriven by the movement toward digital copier products. A related implication is that the layer of interface may be ata software API interface layer, rather than the traditional RS-232 type of interface between a computer and an officeperipheral device. This is a reason why specifications such as S.100 are now being requested by customers, becausethey want to have fax support in a network environment.

SALUTATION CONSORTIUM LIAISON

J. Dahmen (Lanier) noted that there is work going on within Salutation and JetSend that may address some of thesame areas regarding interfaces as the Multi-Function Peripheral (MFP) work in TR-29.2.

TR-45 L IAISON

J. Rafferty (Human Communications) raised the question about whether the digital cellular community needs morework done in the area of fax interfaces, since they previously have made use of the Class 2.0 interface. V. Cancio(Xerox) will check with TR-45 to see if it makes sense to review IS-99 and IS-135, the related interim standards.

FAX APIS

V. Cancio (Xerox) has a physical copy of a draft Microsoft fax API for Windows NT 5.0 which was not distributed,but members are invited to review it and make contact if needed. A contact point was listed (P. Carver:[email protected]). It was suggested that a beta version may be available to Microsoft Developer Networkmembers.


No statements were made.

COMMITTEE DIRECTIONS

J. Dahmen (Lanier) noted that there is a movement toward interfaces that will work in a network connectedenvironment. J. Rafferty (Human Communications) noted that there is probably a need to do an assessment of whatthe updated mission of TR-29.2 should be. V. Cancio (Xerox) noted that this will be somewhat dependent upon thediscussions going on within TR-29.1. TR-29.2 is also working on MFPs, which are not specifically beingaddressed within TR-29.1. D. Crocker (Brandenburg Consulting) noted a sea change going on. MIS (theManagement Information Systems Dept.) is now the decison maker for fax within an organization’s networkenvironment and fax technology now becomes “strategic” if there is a requirement to interwork in the organization’snetwork.

D. Crocker (Brandenburg Consulting) noted that the new IETF working group on content negotiations is working ona standard method of capabilities exchange. He also noted that the IPP group is working on a way to package jobsthat can use an IP network (via HTTP). He suggested that TR-29.2 should NOT help proprietary initiatives, butrather support public standards activities and define a piece that it makes sense for TR-29.2 to work on. V. Cancio(Xerox) felt that the discussions within TR-29.1 about future directions will have an impact on TR-29.2.

PN-3626, CLASS 1.0 DIGITAL INTERFACE

Editor J. Dahmen (Lanier) reported on the status of PN-3626, which updates TIA-578-A incorporate the revisionsmade within ITU-T T.31. He has added an Appendix E as an informative annex which covers changes from TIA-578-A to draft TIA-578-B. J. Dahmen (Lanier) also communicated with B. DeGrasse (BJ Communications, ChairTR-29.3) about a potential problem of implementation. B. DeGrasse’s issue was on fallback from V.34 down toV.17. However, J. Dahmen felt that this was an implementation issue and did not reflect a problem with theinterface itself. He was not aware of any further issues which would prevent the updated specification from beingballoted. The last version of the full document was TR-29.2/97-08-07 (J. Dahmen, Lanier). It was suggestedthat the new Annex E be printed out, since this is the only change since the last version was distributed.



The Annex E for PN-3626 was distributed as TR-29.2/98-02-03 (TR-29.2 Chair). Some minor editing forpunctuation may be needed, but otherwise the content looked acceptable. It was agreed to submit draft PN-3626,with minor edits as needed to TIA for industry ballot.

PN-3625, CLASS 2.1 DIGITAL INTERFACE

V. Cancio (Xerox) and TIA have not had any success getting feedback from Datarace on their “No” vote regarding theindustry ballot of PN-3625, Class 2.1. As a result, it has been sent out for publication as TIA-592-A. A copy ofthe corrigendum to ITU-T T.32 which establishes the Fclass=2 assignment was distributed, but not numbered.

PN-3130, CLASS X D IGITAL INTERFACE

PN-3130 was previously Class 4. There is no editor currently assigned to this project. The current direction is tomake a small set of extensions to Class 1 in order to meet the Class X requirements. V. Cancio (Xerox) noted thatS. Gebala, independent consultant, is willing to do this work, but there is an issue about his ability to physicallyattend the meetings. It was suggested the work should begin anyway and that it could continue via correspondence.V. Cancio (Xerox) agreed to contact S. Gebala to see if he could meet with TR-29.2 members this week. J. Dahmen(Lanier) asked whether the Class X effort will still be relevant. Since it appears that it would be straightforward, J.Dahmen (Lanier) suggests that he may be able to do it, if S. Gebala is not available. V. Cancio (Xerox) noted thatthe value of Class X may be greater for MFPs than for fax modems.

PN-3756, MULTI-FUNCTION INTERFACE

There is no editor assigned to PN-3756 at this time and no contributions were received.

James Rafferty, Human Communications

Communications Standards Review – Telecommunicationsregularly covers the following committee meetings:

TIA TR-29 FacsimileTR-30 ModemsTR-41 User Premises Equipment

ITU-T SG8 Telematic TerminalsSG 15 WP1 Network AccessSG16 Multimedia

ETSI ATA Analog Terminal AccessDTA Digital Terminal AccessMTA Multimedia TerminalsTC SP Speech ProcessingTC STQ Speech Transmission QualityTIPHON Voice Over InternetTM6 Transmission & Multiplexing



REPORT OF STUDY GROUP 15 WORKING PARTY 1, NETWORK ACCESSFEBRUARY 9 – 20, 1998, GENEVA, SWITZERLAND

Working Party 1/15 (Network Access) chair is A. Nunn (British Telecom, UK). The report of the previous meetingof WP1/15 is contained in COM 15-R 4©. TD-17(PLEN) provides the applications guidelines on referencesstandards from other organizations (including ISOC/IETF).

Recommendations Determined at this meeting of WP1/15 are shown in Table 1, below.

Q1/15 ACCESS NETWORK TRANSPORT (ANT)

Question 1/15 is chaired by D. Curtis (AT&T, USA). TD-29(PLEN) is the revised work plan which defines theaccess network as an implementation comprising those entities (such as cable plant, transmission facilities, etc.)which provide the required transport bearer capabilities for the provision of telecommunications services between aservice node interface (SNI), an interface that provides customer access to a service node, and each of the associateduser network interfaces (UNI). The UNI interface is defined as the interface between the terminal equipment and anetwork termination at which the access protocols apply.

TD-22(WP1/15) is the report of Q1/15 meetings in London (August 26-29, 1997) and Geneva (December 2-4,1998) from the Rapporteur. Annex 7 of this report notes 11 areas, as seen by the Rapporteur, where there are holesand overlaps in ANT standardization with some commercial products and services examples.

ANT STANDARDIZATION PLAN

Primary effort was devoted to development of the ANT (Access Network Transport) Standardization Plan, particularlythe development of models for depicting ANT configurations and applications, and response to liaisons regardingANT issues. Although there was provisional agreement, the issue of placement of the user to access networkinterface will continue to be discussed as input is received from other bodies.

Stable draft text for the ANT standardization plan was agreed and is given in TD-28(PLEN). This documentprovides useful diagrams of all types of access networks, cable, fiber, wireline, wireless and satellite.

Regarding the scope of ANT, the following agreements were reached:

• GII project N.1 (Architecture and Layer 1 aspects of wideband/broadband access infrastructures for the GII) stopsaccess at “terminal equipment;” Q1/15 needs to confirm that this is consistent with Q1/15 “network terminatingequipment” and consistent with the access interface at the “boundary between operator domain and user domain.”

• Although GII project N.1 scope appears restricted to residential, Q1/15 considers that Multi-Media services areapplicable to wider applications.

• The apparent overlap between GII projects N.1 and N.4 (Access to/interworking with IP-based networks) onInternet access needs to be resolved.

• Most delegates agree that the ANT can end at a cable interface but further study is required.• ANT does not include LANs (supported by the JRG on GII - this may need further study) and ANT does not cover

“payload” (i.e., above the link layer) information was confirmed.

LIAISONS

TD-16(GEN) provides copies of draft Recommendations J.131 (transport of MPEG2 via PDH, ex J.tmp) andJ.132 (transport of MPEG2 via SDH, ex J.tms) from SG 9.

TD-17(GEN) from SG 7 provides a list of the Recommendations related to security, in particular the X.800 series,and a list of security terms definitions.

Q2/15 Draft Recommendation G.983, G.PONB for ATM-PON (AsynchronousTransfer Mode - Passive Optical Network) System

TD-26(PLEN) plusTD-39(WP1/15)

Q4/15 Draft Recommendation G.991.1, High Bitrate Digital Subscriber Line(HDSL) Transmission System on Metallic Local Lines (formerly G.hdsl)

TD-38(PLEN)-e

Table 1. Determined Recommendations of WP1/15.TD-6(WP1/15) is a liaison statement from SG9 Q20 and Q24 providing copies of two ETS, DVB (digital videobroadcasting) A021 and A022, being proposed as draft Recommendations: Network Independent Protocols forInteractive Services (J.ini), and Digital Video Broadcasting Interactive Channel through the PSTN (J.ivpn). Thiswork is based on DAVIC and MPEG2.



TD-8(WP1/15) from SG9 provides a list of 15 Recommendations related to cable distribution and digital broadcastsystems which they are developing.

TD-9(WP1/15) from SG13 strongly supports the need to include power feeding interfaces in access networks, asSG15 has proposed.

FUTURE WORK FOR Q1/15

Future will include resolution of the user-network interface point location, addressing the list of ANT issues in theANT Standardization Plan, refinement of the Standardization Plan and a stable ANT Standardization Work Plan. Inorder to progress this work, an interim Q1/15 experts meeting is planned for June 29-July 1 1998, in Tel Aviv,Israel, hosted by MOC (Ministry of Communications).

Q2/15, CHARACTERISTICS OF OPTICAL SYSTEMS IN LOCAL ACCESS NETWORKS

The Chair of Question 2/15 is Dr. T. Finegan (BT, UK). G.983 (ex G.PONB, Passive Optical Network-Broadband)was Determined at this meeting.

G.983 (EX G.PONB)

D.258 , a draft of G.PONB for ATM-PON (Asynchronous Transfer Mode - Passive Optical Network) System, waspresented by NTT on behalf of an agreement reached by the group of interested parties:

Bell Canada, Bell South, BT, DTAG, France Telecom, GTE, Telecom Italia / CSELT, NTT, SBC, Swisscom,Telefonica, Telstra, Alcatel, Ascom, BBT, Bosch Telecom, Ericsson, Fujitsu, Italtel, Lucent Technologies, NEC,Nortel, SAT and Siemens, and Telecom Italia.

It was agreed to use this document as the basis of the editing sessions on G.983.

COM 15-36© is the draft Recommendation resulting from the interim meeting in August 1997.

TD-15(WP1/15) , Suggested Input to Draft G.PONB, and TD-16(WP1/15) , General Suggestions for G.PONB,were produced by the Rapporteur. TD-15(WP1/15) contains some text for scope, definitions, abbreviations andreferences.

The revised text of Recommendation G.983 as Determined by SG15 is given in TD-26(PLEN) plus TD-39(WP1/15) .

HYBRID FIBRE RADIO (HFR) SYSTEMS FOR DIGITAL BIDIRECTIONAL BROADBAND ACCESSNETWORKS

A new study item was agreed to look at Hybrid Fibre Radio systems for access networks (COM 15-38©, Alcatel).These HFR systems support multi-service access of distributive and interactive (future) services. As an alternative toother broadband access types, HFR can be used for new access infrastructures but can also complement or replaceexisting broadband access networks.

HFR systems consist of an optical distribution segment (optical feeder) and a radio drop segment. Several conceptsfor the optical feeder system exist: e.g., Baseband-Feeder (e.g., ATM-PON) and Radio-Frequency-Feeder (RF-Feeder).In the case of the RF-Feeder, an RF signal (to be used for the radio drop segment) is directly transported over theoptical fiber.

TD-7(GEN) from ITU-R is a copy of Recommendation F.1332, Radio Frequency Signals transported throughOptical Fibers. It defines the use of optical fiber systems to transport RF signals to out stations for RFamplification and wireless transmission. This technique can greatly simplify the equipment required at wireless outstations (e.g., cell sites).

Q3/15, DCES FOR DIGITAL LEASED CIRCUITS

The Q3/15 Rapporteur is G. Sebek (France Telecom/CNET, France). The meeting report is TD-43(WP1/15) .The meeting objectives were to finalize as much as possible draft new Recommendations V.144k (48/56/64/128/144kbit/s DCE for use on digital point-to-point leased circuits) and V.2M (DCE providing a signaling rate up to 2048kbit/s). A number of documents were considered, including TD-21(WP1/ 15)©, the first proposal for draft



Recommendation V.144k. No contributions for V.2M have been received, therefore the time schedule for thisRecommendation has been pushed back.

There is a strong relationship between Q3/15 and Q4/15. How the Q3/15 work on V.2M and V.nx2M progressesdepends partly upon results in Question 4/15. The Q4/15 work on G.hdsl in clause 7 of draft, Application SpecificRequirements, (TD-5(WP1/15) and WD-1(WP1/15)) provides requirements for a digital leased circuit DCE.

Q3/15 TIME SCHEDULE

The objectives of Q3/15 are to develop draft Recommendations as follows:• V.144k (G.300) for Determination, October 1998.

–Specification for back-up facilities, October 1998.–Management functions, July 1999.

• V.nx64k (DCE providing a signaling rate of n x 64 kbit/s with n <= 31), 1999.• V.2M, July 1999• V.nx2M (DCE providing a signaling rate of n x 2048 kbit/s), March 2000.

DRAFT RECOMMENDATION V.144K

TD-21(WP1/15)© is the input draft Recommendation V.144k, A 48/56/64/128 (144) kbit/s Data CircuitTerminating Equipment Standardized for Use on Digital Point-To-Point Leased Circuits. The line signaling isconsidered a national option and is not specified in this Recommendation although 2B1Q signaling is defined inAppendix IV, Example of Implementation of the Transmission Unit.

NTT identified the existence of an additional DTE-DCE interface according to I.430 (ISDN User-Network Interfaces).Currently V.24 and X.24 interfaces are supported. NTT may submit a contribution after further review.

DT identified a number of areas where the content of the draft needs improvement. The requirements related to bitrates below 128 kbit/s should be deleted. The inclusion of a scrambler/descrambler should be mandatory, especiallyin the case of using back-up facilities. The scrambler/descrambler may be different from V.38 (A 48/56/64 kbit/sdata circuit-terminating equipment standardized for use on digital point-to-point leased circuits). V.144k should becompatible with V.38. The usefulness of retaining the 144 kbit/s bit rate should be clarified. Depending on theleased line network characteristics, an inverse multiplexing function may be required. Depending uponcontributions, V.144k could include the requirements for ISDN back-up facilities.

TD-42(WP1/15)© is revised text for V.144k. Some editorial work still needs to be done on this document (e.g.,renumbering of sections and appendices).

Q4/15, SUBSCRIBER ACCESS SYSTEMS

The Rapporteur of Question 4/15 is D. Stuart (3Com, USA). The discussion was focused on a number of newRecommendations initiated during the interim period and on final preparation of G.hdsl for Determination in theclosing SG15 Plenary. Four Rapporteur meetings are planned before the next SG 15 meeting in October (see theCSR calendar on the back cover of this issue of CSR-T).

The following Recommendations are under development in Q4/15:

• G.dmt, Digital Transmission System on Metallic Local Lines for High Bit-Rate Asymmetrical (ADSL) Services• G.lite, Digital Transmission System on Metallic Local Lines for Low Bit-Rate Asymmetrical (ADSL) Services• G.test, Test Procedures for ADSL Digital Transmission Systems for Metallic Local Lines• G.hs, Procedures for Starting Sessions of xDSL Transmission Systems over Metallic Local Lines• G.ploam, Physical Layer Management for ADSL Digital Transmission Systems• G.991.1 (G.hdsl), High bit rate Digital Subscriber Line (HDSL) transmission system on metallic local lines

G.hdsl was Determined at this meeting as TD-38(PLEN)-e. It was agreed that Q4/15’s goal is to Determine theremaining draft Recommendations at the October 1998 SG15 meeting.


The following companies have been identified as potentially having IP (Intellectual Property) associated with thiswork:



• 3COM/U.S. Robotics • Fujitsu• Alcatel • Motorola• Amati • Racal Datacom• Analog Devices • Texas Instruments• Aware

Additionally, Telebit (and its successor, Cisco) was identified as a potential IP holder at an earlier meeting. It wasnoted that Stanford University may also have Intellectual Property. Paradyne indicated that they are reviewing theirsituation regarding Intellectual Property as well.

LIAISONS

TD-13(GEN) is a liaison from SG4 on the TMN (Telecommunications Management Network) document plan. Itwas agreed to review this document with respect to the management work.

TD-17(GEN) is a general liaison from SG7 to all study groups listing all recommendations relating to securityand requesting updates. There was no response.

TD-17(WP1/15) (M. H. Sherif, AT&T, Rapporteur Q18/16) provides information on two service scenarios usinga modem with a voice/ data multiplexer (H.324/H.223 or V.70/V.76) on the access link and having the voice anddata separated in the network, with data over the IP network and voice over the PSTN. Specifically, information wassought on the use of xDSL modems in this sort of application.

TD-18(WP1/15) (R.-R. Damm, Q6/16 Rapporteur, and F. Lucas, Q7/16 Rapporteur) announces that a study ofDTE/DCE interfaces for xDSL has been started in SG16 and requests guidance on the requirements of such DTE-DCE interfaces. Interest was expressed in using USB, PCI and IEEE 1384 physical interfaces with a modification ofV.250 as the logical interface. An ad hoc on DTE/DCE interfaces met (report is WD-14(WP1/15)), but did notreach any significant technical conclusions. The ad hoc drafted a liaison inviting the Q6/16 and Q7/16 experts to theQ4/15 Rapporteur meeting in April. The liaison was approved by SG15.

G.DMT

P. Melsa (TI) is the new editor for G.dmt taking over from J. Bingham (Amati), who is retiring.

Annex 1 of TD-4(WP1/15) is a draft of G.dmt. J. Bingham (Amati) reported that the main document is a first cutat a generic Recommendation and that Annexes would be added for specific scenarios (ADSL over POTS, ADSL overISDN, and ADSL over TCM ISDN [G.961 Appendix III] have been identified so far). The Rapporteur identified thisdocument as a working text (having no special status, i.e., basically a strawman). Since T1.413 Issue 2 is in theprocess of completion, necessary changes to G.dmt to maintain compatibility with T1.413 Issue 2 would beproposed as appropriate.

D.156 (Y. Okamura, NEC, Japan) proposes a framework of “Option for an ADSL service that co-exists with TCM-ISDN.” This “Dual Bitmap” proposal has dual bit rates under FEXT and NEXT noise requiring an additional bit andgain table. This proposal expands the upstream carriers from 32 to 256 when used with TCM-ISDN and supports aTCM-ADSL mode for the simplest implementation. Since the line data rate varies, this proposal requires anadditional buffer to provide the user with a constant bit rate.

D.241 (A. Johansson, Ericsson, Sweden) proposes specifications for a European oriented POTS splitter based onwork in ETSI. This paper is a good overview of the European POTS electrical parameters.

WD-3(WP1/15) is the Work Program for G.dmt. It includes a table of contents (ToC) and an overview of thestructure of the current working text. WD-16(WP1/15) is text for draft Recommendation G.dmt. P. Melsa,Editor of G.dmt, conducted a review of the ToC. The following agreements were reached:

• Section 1.1, system reference model, was moved to Annex A• Sections 7.5-7.13 (ATU-C), 8.5-8.13 (ATU-R), In section 10, Initialization, 10.1, 10.4-10.7 with the exception

of 10.6.2, 10.6.4, 10.7.4, and 10.7.6, were accepted as baseline text.• Sections 10.2 (handshake ATU-C) and 10.3 (handshake ATU-R) were removed to be included in G.hs.• It was further agreed that any T1.413 issue 1 items would be removed.

Contributions were sought on information for the Annexes specifically addressing such issues as the specification ofa POTS Splitter. It was decided to move all information relative to POTS splitters to a new Annex E. The US text



from Annex A and D.241 were inserted as working text in this new Annex. These changes were posted in WD-15(WP1/15) , Agreed Modifications to G.dmt Working Text.

WD-16(WP1/16) reflects all of agreements reached at these meetings. There was considerable discussion onprocedural and structural issues. During this discussion it was decided to re-designate the sections which referred toIssue1 (i.e., Sections 10.1.1, 10.4.1 and 10.5.1) from “baseline” to “working” text.

The following fundamental areas require contributions to help facilitate resolution:• Support for modes of operation for compatibility with T1.413 Issue1• ATM or STM modes mandatory• Compatibility of (external ATM TC with STM mode) with (ATM mode)• Bit Swap Optional/Mandatory• Dual Latency Optional/Mandatory• Annex B (ADSL above ISDN) – no papers to date• Annex C (ADSL coexistence with TCM ISDN)• POTS Splitter requirements/specifications for various regions• Definition of PSD masks for Annex A, B, and C• PAR reduction techniques

Previous drafts of Recommendation G.dmt have been structurally modified to provide a core, generic, document withthree annexes, which define specific ADSL services. It was originally based on the letter ballot of Issue 2 of ANSIcommittee T1 standard T1.413. This text has been furthered modified based upon agreements reached at this SG15meeting. Appropriate portions of previous drafts been deleted from G.dmt and adopted into G.hs, G.oam or G.test.

TD-41(WP1/15) is the output draft Recommendation G.dmt, Digital Transmission System on Metallic LocalLines for High Bit-Rate Asymmetrical (ADSL) Services. The editor is P. Melsa (Texas Instruments). TD-41(WP1/15) is composed of both baseline text and working text. To indicate which sections are “baseline text”rather than “working text,” the text of the appropriate headings have been modified. The presence of “(baseline)” inthe heading indicates that section and subsequent subsections are baseline text. For example, if 12.2 is markedbaseline then 12.2.2 is also baseline. However, if 12.2.2 is marked baseline then 12.2.1 would not necessarily bebaseline.

G.LITE

Annex 4 of TD-4(WP1/15) (pp. 248) is the Terms of Reference issues for G.lite. C. Hansen (Intel, editor) brieflyreviewed the “Terms of Reference” Table which is organized by issues.

D.147 (F. Van der Putten, Alcatel, Belgium) proposes terms of reference for G.lite. Specifically it proposes the useof DMT line code and ATM for the TC layer. In the presentation, it was stressed that Belgium wanted G.lite to beDetermined at the next meeting and to make the choice on line code at this meeting. D.147 notes that thisBelgium proposal was made after consultation with France, Italy, Germany and Spain.

D.152 (G. Zelder, Deutsche Telekom, Germany) proposes that Q4/15 concentrate on G.adsl and G.hdsl even if thatmeans delaying G.lite. The presenter also suggested that G.lite should use DMT and could be an annex to G.DMT.

D.175 (T. Cole, AMD, USA) proposes extensions to T1.413 to create G.lite. The specific proposals are thatstandard and country parameters and the maximum number of upstream and downstream tones should be negotiatedwith G.hs.

D.176 (J. Kubinec, AMD, USA) presents results of a very small sample of home wiring and home equipment inthe USA (5 homes/ apartments). Measurements were made within the frequency band from 40 kHz to 4 MHz, withphones in both “on-hook” and “off-hook” conditions. The presenter (T. Cole, AMD) stated that the purpose of thiscontribution was to stimulate other companies to conduct other studies and bring these results to future meetings.The channel transfer characteristic when a phone was off-hook shows that nulls as large as -23 dB can occur in theband 40 kHz to 1 MHz. During the discussion it was made clear that the proximity to a local radio station had animpact on the results. There was an extraordinary amount of detailed questions for such a small sample study.

D.182 (K. Foster, BT, UK) proposes that G.lite be based on T.413 as much as possible. It should use DMT andwork with T.413 Issue 2 line cards if at all possible.

D.191 (R.K. Smith, Paradyne, USA) proposes that a liaison be sent to SG16 soliciting their opinion onrequirements for G.lite needed to support multimedia applications.



D.192 (R.K. Smith, Paradyne, USA) proposes two checklists for G.lite characteristics. The first checklist isbroken down into Fundamental and Performance characteristics. The second specifies salient end-point characteristics,which are broken down into Premise and CO Characteristics.

D.193 (R.K. Smith, Paradyne, USA) expresses support for G.lite but stresses that a better understanding ofrequirements is needed before proceeding with developing the Recommendation.

D.207 (J. Carlo, TI, USA) proposes terms of reference that are broken down into user premise and CO items. Itsupports the proposal of Germany, i.e., that G.dmt should be given priority over G.lite. It also proposes that G.liteinteroperate with G.dmt.

D.208 (P. Melsa, TI, USA) highlights issues surrounding splitterless operation. It also looks at three possiblesolutions to the problems associated with splitterless operation. It concludes that none of the solutions discussed sofar appears to offer the ideal solution.

The following two contributions are similar to D.147 from Belgium, in that they propose terms of reference andthe use of DMT:• D.222 (Italy)• D.242 (A. Johansson, Ericsson, Sweden)

D.210 (S. Abbas, USA) proposes a list of goals for inclusion in the terms of reference for G.lite. (this is the listdeveloped by T1E1.4). This list is the same as the Belgium contribution (D.147 ) without the statement ofpreference for DMT line code.

D.244 (multi-source: six US carriers, eight US companies [including Microsoft and Compaq], presented by C.Hansen, Intel, USA) also includes much of the same points raised in D.147 with some amplification; it alsoproposes the use of DMT.

D.247 (F. Aalaei, Centillium, USA) proposes terms of reference for G.lite including:• Definition up to the TC layer• G.lite should be rate adaptive• G.lite should have low complexity• G.lite should operate in all environments• G.lite should make use of network timing.

D.248 (F. Aalaei, Centillium, USA) proposes an upstream rate of 512-768 kbit/s and possibly symmetric rates.

D.249 (F. Aalaei, Centillium, USA) proposes that G.lite not preclude the use of a splitter.

D.256 (K. Ko, Rockwell, USA) suggests a methodology for evaluating the effect of interference from the upstreamADSL into existing telephones in splitterless systems. Test results over a sample of 30 telephones are supplied forDMT, QAM and a Rockwell proprietary line code (Continuous Phase Modulation, CPM); they indicate that differentline codes will produce significantly different SPL (sound pressure levels) in locally attached telephones. CPMperformed best, QAM very similar, while DMT performed worst in this test. However CPM requires greatertransmit power than DMT or QAM to provide the same data rate.

D.272 (A. Norrell, 3Com, USA) proposes Terms of Reference for G.lite. Specifically it proposes an order ofmagnitude improvement over voice-band modems, that G.lite be easy to install and configure and that it use DMT.

D.273 (M. Tzannes, Aware, USA) proposes Terms of Reference, and supports the use of DMT and interoperabilitywith G.DMT.

D.274 (M. Tzannes, Aware, USA) provides experimental and theoretical results for a splitterless system usingDMT.

D.206 (P. Melsa, TI, USA) proposes that a technique for clipping mitigation be specified in G.dmt and G.lite.Two techniques are described and proposed. It was clarified that this adds 8 multiply/adds to the complexity.

D.150 (3Com, USA) proposes another technique for improving PAR by adding a time domain signal to thetransmitted DMT signal to reduce the PAR. Using the low complexity algorithms, D.150 proposes achievementof 3 dB PAR reduction with 2N multiply/adds per DMT symbol and a data rate loss of less than 0.2%, orachievement of 4 dB PAR reduction with 6N multiply/adds per symbol and a data rate loss of less than 1%. Thiswork was done by J. Cioffi, Assoc. Prof. Stanford, and Stanford graduate students.



In response to a question, it was suggested that a power reduction of approximately one half (this is independent ofthe receiver) would be achieved. The point was raised that these techniques are needed because of low precision in theD/A converter. It was pointed out that there could also be a benefit with splitterless operation through a reduction ofthe tones into the handset. Considerable discussion followed with each of the line code camps trying to makecomplexity points about DMT. The point was made that these techniques only address transmitter clipping and aretransparent to the receiver.

It was finally proposed that “PAR” be added to the list of requirements and that the technique be added to the livinglist. It was also proposed that any trade-off between PAR and monitoring of unused channels should taken carefully.The final agreement was to add, “clip mitigation” to the call for papers and mark it as “under study” in theAgreement column.

WD-5(WP1/15)(C. Hansen, Editor G.lite) lays out the present status of the work on G.lite. It includes a Termsof Reference and Scope.

The Rapporteur noted that there was only one candidate for line code in any of the papers. He also noted that DMThad been proposed by three Administrations. He further observed that from the contributions it was evident thatDMT had broad support from service providers and companies. He then obtained the meeting’s acceptance of DMTas the line code by requesting Administrations to state if they had any objections to specifying DMT as the line codefor G.lite (nine were present and no objections were expressed). The Rapporteur then attempted to get agreement onthe other items, which had received support in multiple contributions. The agreements reached are listed in Table 2.

Toward the end of the discussion there was an attempt to re-open the line code decision; it was met with a strongrebuff from those representing Administrations. The line code decision was also raised in the US Delegationmeetings during the week. The US delegation held a long evening meeting to attempt to resolve the issue and amemorandum was developed and signed by the US participants to support the

1 Agreed(2/20/98)

Req The linecode for G.lite shall be DMT.

2 Agreed(2/20/98)

Goal Application to be supported are: Internet access, web browsing, IP telephony, distancelearning, work-at-home, video telephony, interactive games, file backup services andanalog telephony. Others may be considered in the future.

3 Agreed(2/20/98)

Goal Bitrate downstream: 64kbit/s – 1.5 Mbit/sBitrate upstream: 32 kbit/s – 512 kbit/sThe data rates are specified at the PMD layer to support the above applications.

4 Agreed(2/20/98)

Goal G.lite should be rate adaptive. Transceivers support rate adaptive operation providingthe ranges in (3), dependent upon loop conditions and bit error rate.

5 Agreed(2/20/98)

Req G.lite shall meet TBD POTS interference requirements. Test procedures will beincluded in G.test.

6 Agreed(2/20/98)

Goal G.lite should accommodate changing line characteristics due to POTS services.

7 Agreed(2/20/98)

Goal G.lite should include a low complexity PAR reduction technique.

8 Agreed(2/20/98)

Goal When installed without a splitter, G.lite should support:• Ease of installation and use• Minimize the need for changes to premise wiring• Permit voice-band and G.lite to operate simultaneously on the same inside wire

pair• It is desirable to avoid the need for a POTS splitter at the point of entry. A

splitter may be provided as an option.9 Agreed

(2/20/98)Req The startup for G.lite shall use G.hs.

10 Agreed(2/20/98)

Req G.lite shall support management functions consistent with other xDSL systems byusing a clear Embedded Operations Control (EOC) channel.

11 Agreed(2/20/98)

Req G.ploam shall be used for operations and management of G.lite using the clear EOCchannel.

12 Agreed(2/20/98)

Goal G.lite should support low equipment complexity and high network operation andadministration efficiency, given the mass market focus of the applications.



13 Agreed(2/20/98)

Goal Loop reach is of primary importance.

14 Agreed(2/20/98)

Goal Spectrum compatibility with standardized xDSL (e.g., ADSL, HDSL, Basic rateISDN) services.

Table 2. Agreements Reached on G.lite during the Q4/15 Meeting.

decisions of Q4/15, subject only to papers identifying technical points.

TD-46(WP1/15)© is the output draft Recommendation G.lite, Digital Transmission System on Metallic Local Linesfor Low Bit-Rate Asymmetrical (ADSL) Services.

G.TEST

The G.test recommendation describes the testing procedures for all ITU xDSL standards. The G.test recommendationwill provide descriptions of the test procedures, test configurations, test loops, crosstalk models, etc. The xDSLstandards (such as G.dmt and G.lite) will reference this G.test document for testing procedures and configurations,however performance requirements will be outlined in each particular xDSL standard.

M. Tzannes (Aware, US, G.test Editor) briefly reviewed Annex 3 of TD-4(WP1/15) , G.test agreed terms ofreference; proposed draft text will based on T1.413 issue 2. This document will be referenced by all of the xDSLRecommendations for methods but the actual values will be in the individual Recommendations.

WD-6(WP1/15)© (M. Tzannes, Editor G.test) is a copy of the draft Recommendation G.test. All items on theliving list, which relate to the ToR for this work, were agreed. This working draft contains sections 11 and annexesB, C, E, H, G of T1.413 issue 2, test loops from V.56 bis and G.961, a model for POTS QoS Testing, and an in-home wiring model from D.175 . The group agreed that these sections would be used as a working text for G.test.

The following additional agreements were reached during the meeting:

• HDSL: not to be covered in the first version• G.961: will be added to the working papers

There was a prolonged discussion on what to do if this particular work was not ready in October. The decision wasthat this Recommendation would not hold up the others. This issue was raised again during the second review ofthis document with no change in the status. It was additionally decided to add selected text from D.175 to thePOTS QoS test section.

The following areas need technical proposals to complete the G.test document:

• Definition of testing procedures for G.dmt and G.lite modems (Are these completely separate procedures becauseof the splitterless nature of G.lite?)

• Definition of worst case loops and crosstalk for G.dmt• Definition of worst case loops, crosstalk, phone sets, in-home wiring and in-home crosstalk (AM radio, etc.)

TD-44(WP1/15)© is a copy of the draft document for G.test, Test Procedures for ADSL Digital TransmissionSystems for Metallic Local Lines. The schedule for completion of G.test is October 1998.

G.HS

G.hs, Procedures for Starting Sessions of xDSL Transmission Systems over Metallic Local Lines (Hand Shake)(Editor L. Brown, Motorola), proposes a framework for the development of a G.hs Recommendation. Specifically,it proposes that a single document be maintained containing the following three parts:1. Work program and Terms of Reference.2. An Issues List that tracks all material proposed for inclusion in the Recommendation.3. Draft text for the Recommendation: revision control will be used to show additions and deletions. As text is

approved by the Rapporteur group, revision marks will be removed.

Annex 2 of TD-4(WP1/15) , the report of the October 1997 Q4 meeting in Redbank NJ (pp. 201), is the draftRecommendation G.hs. L. Brown (Motorola, Editor) briefly reviewed the agreements reached to date as reflected inthe table on page 202.

D.204 (S. Palm, Matsushita, Japan) describes a line probing technique referred to as a “channel audit” which wouldbe used to help choose the correct type of xDSL technique. Eight specific methods are proposed to be used to



determine the various aspects of the channel. D.204 proposes a tone-based method for the exchange of information,and proposes that these techniques be included in the Terms of Reference.

D.271 (A. Norrell, 3Com, USA) proposes the use of a variation of Recommendation V.8 to accomplish thecapabilities exchange. It proposes that the exchange be modulation-based.

D.174 (T. Cole, AMD, USA) states that the USA has not yet formed a position on G.lite or G.hs, and hastherefore encouraged member companies to bring forward their independent viewpoints.

There was a subsequent discussion in which it was suggested that the vendor IDs be moved from G.dmt to G.hs andthat the vendor codes assigned in T1.413 be replaced with T.35 vendor IDs. A decision on this was put off until thenext meeting.

TD-45(WP1/15) includes the agreements reached during this meeting (Table 3).

G.PLOAM

Annex 5 of TD-4(WP1/15) includes the issues for the G.oam terms of reference, as per the Red Bank Rapporteur’smeeting in October 1997. A. Johansson (Ericsson, Sweden, new G.oam editor) briefly reviewed the status of thiswork, which basically does not yet even have a terms of reference.

It was noted that G.oam would be called G.ploam in the future as three letter extensions containing the letter “o” arereserved for “optical” in SG15.

WD-12(WP1/15)© (A. Johansson, Editor G.oam) is text for the proposed draft of Recommendation G.oam.Appendix 3 of G.dmt, support for an eoc (embedded operations control) full-duplex data-streaming mode (Annex L ofT1.413), was moved to G.ploam. The operations channel proposed for G.hdsl will be studied. The followingadditional agreements were reached:

Status Issue DateAgreed Physical layer management only 02/98Agreed as working assumption Management from the CO/LE (ATU-R via proxy) 02/98Agreed as working assumption Management of ATU-R over the ‘T’ interface 02/98Agreed as working assumption Separate Management Entities for ATU-R and ATU-C &

ATU-R (at CO/LE).02/98

TD-40(WP1/15)© is the output draft Recommendation G.ploam, Physical Layer Management for ADSL DigitalTransmission Systems. This recommendation specifies the physical layer management for xDSL transmissionsystems. It specifies means of communications on a transparent embedded operations channel in the physical layer.It specifies network element content and syntax for configuration, fault and performance management.

TD-35(WP1/15) contains liaisons to ITU-T SG 4 noting the beginning of the work on G.ploam.

G.991.1 (G.HDSL)

G.991.1 supports three operational modes, one transporting 784 kbit/s over each of three wire pairs in parallel, asecond with 1168 kbit/s over two wire pairs in parallel and a third with 2320 kbit/s over a single wire pair. Each ofthese modes is duplex, echo canceled (either CAP or 2B1Q line codes) and capable of supporting the 2048 kbit/shierarchy (E1). Operation using the T1 rates (1.544 Mbit/s) is also shown.

TD-5(WP1/15) (S. Schmoll, Alcatel, G.hdsl editor) plus WD-1(1/15) is a draft version of RecommendationG.hdsl. It is closely modeled on the ETSI Technical Report 152. With some clean-up editing, this document wasresubmitted as TD-38(PLEN)-e.

The text of draft new Recommendation G.991.1 (G.hdsl), High Bit Rate Digital Subscriber Line (HDSL)Transmission System on Metallic Local Lines, is given in TD-38(PLEN)-e. The Editor is S. Schmoll (AlcatelSEL, Belgium). This recommendation was Determined by SG15.

The majority of the work on this Recommendation is based on existing technology developed in ANSI T1E1.4,ETSI TM6 and the ITU.

A draft Recommendation based on the latest Technical Specification of ETSI TM6 was presented. The main resultsof discussion were:



1) A note has been inserted directly under §6.3.3.2 indicating that the test noise with a crest factor of 2.8 which isdefined there may not be representative for noise found in real networks and that further study is necessary. In courseof this work, an equal test procedure for the two line code options 2B1Q and CAP shall be created.

2) The proposal to reorganize the whole Recommendation into a main part and two equal annexes for the line codeswas appreciated but not adopted because of the large amount of purely editorial work.

3) The CAP line code (Annex B) and the 1544 kbit/s two pair frame structure (Annex A) get the same level as the2B1Q of the main body. The line codes are marked as alternative options in the scope and the relevant annexes.

4) As the main change, §7 “Application specific requirements” was renamed to “Application specific examples” anddowngraded from the main part to Appendix I. An additional chapter “1.5 Mbit/s ISDN-PRA” will be included.

5) The term “line baud rate” is changed to “line symbol rate.” The references of §9 Environmental Requirements aregiven as examples only.

Dick Brandt, dB Consulting

Status Issue DateAgreed to adopt a modulation based G.hs with fallback to tone based support of

T1.413.2/98

Agreed that future enhancements to existing ITU-T DSL Recommendations and futureITU-T xDSL Recommendations will be negotiated through G.hs.

10/97

Agreed that G.hs will identify and select between multiple xDSL Recommendations. 10/97Agreed that G.hs should support portability across regional and international

boundaries.10/97

Agreed that G.hs will be invoked prior to modem initialization. 10/97Agreed to absorb functionality from G.dmt sections 10.2, 10.3 (handshakes), Annex A

(Specific requirements for an ADSL system operating above POTS) and AnnexD (ATU-C and ATU-R state diagrams)

2/98

Agreed that the spectrum for G.hs should be completely outside of the POTS band. 2/98Agreed that G.hs will include a non-standards facilities field, to be coded using the T.35

approach (as in V.8bis)2/98

Table 3. Agreements on G.hs Reached During the Q4/15 Meeting.



SG15 WP1 PARTIAL MEETING ROSTER, FEBRUARY 9 - 20, 1998, GENEVA SWITZERLAND

P. Wery, Canada SG15 ChairG. Bonaventura, Italy SG15 VicechairM. Yamashita, Japan SG15 VicechairA. Nunn, U.K. & Northern Ireland WP1/15 Chair

AustriaPost & Telekom G. Reisinger

BelgiumAlcatel Bell J. De Groote

CanadaMitel G. ReesorNewbridge Networks F. TianNortel P. WeryStentor Res. Ctr J. ZebarthTéléglobe Canada S.K. Sharma

DenmarkDanish Electronics N.Ch. JensenTele Danmark P. Gronbaek

FinlandHelsinki Telephone S. TormalaNokia L. RantanenNokia J. TormanenNokia L. WikbergTelecom Finland E. JauhiainenTellabs Oy M. PikkarainenH. Tuomisto

FranceFrance Telecom T. Ben MeriemFrance Telecom B. CraignouFrance Telecom M. Le LigneFrance Telecom J. ThiennotIBM Europe S. Oelcer

GermanyAlcatel SEL G. DiveAlcatel SEL K. FussgaengerAlcatel SEL G. GruellAlcatel SEL W. KoerberAlcatel SEL S. SchmollBosch R. FeigelBosch J. PomyDeutsche Telekom R.R. DammDeutsche Telekom J. RoeseDeutsche Telekom A. Templin-Plus Mobilfunk W.H. DreherSiemens P. DrughSiemens F. FimpelSiemens N. KingWandel und Golter. W. Miller

GreeceOTE G. BathasOTE P.Th. Verrios

HungaryMATAV Hun. Tele. L. Barna

ItalyCSELT M. De BortoliCSELT P. Di VitaCSELT C. MogaveroMarconi S. TorassaMarconi D. PagnottaPirelli Cavi e Sistemi P. BoeroPirelli Cavi e Sistemi G. CarabelloTelecom Italia G. BonaventuraTelecom Italia L. TempestilliTelecom Italia C. Montanari

JapanDDI K. TaharaFujitsu R. OkitaFujitsu H. YamashitaHitachi T. KazawaHitachi M. TakatoriJapan Telecom M. SomaKDD S. RyuMatsushita Electric S. PalmMitsubishi Electric W. Matsumoto

Mitsubishi Electric Y. NaitoNEC T. KanekoNEC Y. MoriguchiNEC Y. OkamuraNEC K. SakaiNEC H. YasuiNTT M. KawasakiNTT K. KikushimaNTT Y. MaedaNTT K. OdaNTT M. OhashiNTT S. TomitaNTT M. YamashitaOki Electric Ind. K. KawaguchiOki Electric Ind. Y. KondoOki Electric Ind. A. TakahashiToshiba T. Atsumi

NetherlandsKPN J.W. PedersenLucent Tech NL K. Den HollanderLucent Tech NL G. ManhoudtLucent Tech NL P. Stassar

NorwayTelenor AS S.M. Svendsen

SingaporeSingapore Telecom K. Kuran Choon Shiong

Slovak RepublicSlovak Telecom B. IlavskySlovak Telecom J. Nosik

SpainTelefónica de Espana E. De SaavedraTelefónica de Espana Gilo G.Sanchez

SwedenL.M. Ericsson J. ArrasL.M. Ericsson A. Johansson

SwitzerlandAscom Tech A. CarrickAscom Tech Y. WangSwisscom Ph. Schroeter

U.K. & No. IrelandBT T. FineganBT K.T. FosterBT I. MannCable and Wireless Ph. KingCoherent Comm. Sys J. SkeneGPT G. AbbasLucent Technologies J. MagillRacal Datacom Ch. FirthTektronix UK M. Lum

USA3Com A. Leke3Com A.J. Mueller3Com R. Stuart3Com R. WangAdv. Mico Devices T. ColeAdv.Mico Devices M. JohnsonAmeritech Services T. StarrAMP B. BennettAnalog Devices R. NuthalapatiAnalog Devices A. ZarolaAT & T R. Ben-MichaelAT & T D. CurtisAT & T J. EavesAT & T B. WangAware M. TzannesBay Networks A. PurkovicBellcore J. SpencerBell South G. Tennyson



Centillum Tech. F. AalaeiCIENA Corporation J. ShrimptonCirrus Logic K. KrishnanCompaq R. HamdiCompaq W. MansellCOMSAT Corp. S. Campos NetoCorning T. HansonCorning J. MatthewsCorning M. SoulliereGeneral DataCom Y. GoldsteinGlobeSpan Tech. M. SorbaraGlobeSpan Tech. M. HumphreyGTE G. McaninchHayes E. BaskinIntel C. HansenIntel K. KahnLevel One J. GarzaLucent Technologies S. AmbatiLucent Technologies P. BonenfantLucent Technologies J. ChenLucent Technologies N. Dagdeviren

Lucent Technologies W. KremerLucent Technologies H. MildonianLucent Technologies C. PostumaLucent Technologies R. TownsendMicrosoft T. KwokMotorola R. BrandtMotorola L. BrownMotorola K. CavanaughMotorola B. DugerdiNorthern Telecom S. AbbasParadyne Corp. R.K. SmithPC-Tel K. MirfakhraeiRockwell Int’l T. GearyRockwell Int’l G. GriffithRockwell Int’l K. KoRockwell Int’l I. TalerRSA R. ChenTexas Instruments J.A.C. BinghamTexas Instruments J. CarloTexas Instruments P. MelsaUS West Adv. Tech. J. Dahl

REPORT OF ETSI TIPHON MEETING 6FEBRUARY 17 – 20, 1998, SANTA CLARA, CA

There is a growing market for real time voice communication and related voiceband communication over IP basednetworks. The objective of the TIPHON (Telecommunications and Internet Protocol Harmonization Over Networks)project is to support telecommunications and Internet technologies thereby enabling communications over IP-basednetworks to work with existing PSTN/ISDN/GSM networks and vice versa. The focus is on interoperabilitybetween the two networks and not on the actual individual network itself.

H. Schink (Siemens, TIPHON Chairman) noted ETSI’s IPR policy. No announcements of IPR relevant toTIPHON were received during the meeting. For current IPR declarations made to ETSI, see ETS 314 (a publicdocument) at www.etsi.fr/ipr. TD-05, the TIPHON 5 meeting report from Sophia Antipolis, was approved.

The next meeting, TIPHON 7, will be April 27-30, in Munich; TIPHON 8 will be held June 15-19, location to bedetermined.

ETSI BOARD

H. Schink reported on the meeting of the ETSI board on Feb. 10, 1998 (TD-29):• TIPHON should continue until interoperability testing is completed.• It is proposed to consider a change in the type of documents, e.g., from TS and TR to ETSI Standards, at least in

the long run to ensure stability and acceptance of documents.• An extension to multimedia should not be precluded.• A discussion on an extension after the end of TIPHON should be considered.• Make sure that TIPHON Net does not evolve into a commercial network.• Consider the possibility of additional marketing towards ETSI technical bodies.• Consider contributing to the work performed by the OCG (Operational Coordination Group) to collect IP related

work items in ETSI and prepare ideas on how to widen ETSI’s activity in this area.

SPECIALIST TASK FORCE (STF) WORK PLAN/ DELIVERABLES

The tasks of the STF (Specialist Task Force) are summarized in TD-53 of the TIPHON 5 meeting in SophiaAntipolis:• Completion of DTR/TIPHON-01001 (Requirements, phase 1), approved during this meeting, and DTS/TIPHON-

02001 (Architecture, phase 1)• Extraction of ITU-T Recommendation H.323v2 requirements should be done within the context of WG1 and

WG6• Detailed description of the TIPHON Net, creation and maintenance of the TIPHON Net web site• Analysis of requirements for gatekeeper-to-gatekeeper interoperability and study of solutions

TD-53 (of TIPHON 6) is a report of recent STF activities. TD-78 contains a report of the TIPHON 6 activities ofthe STF.



MARKETING ACTIVITIES

B. Castle (3Com) reported about recent and coming events with participation of TIPHON officials as speakers.WG6 will give a presentation at the VON conference in San Jose and at VON Europe in Oslo. Several contributionsto international magazines are to be submitted soon, e.g., the IEEE special edition on standards.

A brochure about TIPHON was held back due to recent ETSI board decisions. Copies of the brochure will be mailedto the TIPHON email participants before the CeBIT exhibition.

Reports about TIPHON have been published in different press releases, e.g., in Irish Times.

ITU-T SG16 M EETING

D. Gurle (ETSI) and G. Meyer (Siemens) reported on the SG16 meeting Jan. 26 – Feb. 6 (TD-55). During theSG16 meeting, D. Gurle gave a presentation about TIPHON (see CSR Vol. 9.2 for a report on the SG16 meeting).

SG16 reviewed the liaison from TIPHON concerning the E.164 number allocation and supported this request to theITU. SG16 drafted a liaison to SG2 supporting the TIPHON request.

TD-55 also lists the status of SG16 Recommendations (H.225, H.235, H.245, H.323) which are relevant toTIPHON.

IETF

S. Petrack (VocalTec) discussed the upcoming IETF meeting March 30 - April 3, 1998 in Los Angeles. Since thereare new elements in the charter of SIPTEL (Voice over IP), the group will possibly become an IETF working groupin the future. New items in their charter are concerned with gatekeeper-to-gatekeeper communication and gatewaylocation.

Because this IETF work already interacts with ITU-T SG16, H. Schink prepared a liaison (TD-70 r1) requestingadditional coordination from SG16/WP1.

MODIFICATIONS TO WORK DESCRIPTIONS

TD-43 (S. Moore, Siemens AG) proposes a replacement of the term “PSTN/ISDN/GSM” in deliverable documents.After discussion it was agreed to use “SCN” (“switched circuit network”) instead, and to provide an explanation inthe TIPHON terms of reference and in the overview and architecture deliverables.

TD-45 (J.P. Albinet, Alcatel Telecom R&D) proposes to include the operation with PABXs (Private AutomatedBranch Exchange) and private circuit switched networks within the TIPHON scope. This was accepted by themeeting; the necessary details (QSIG, PNNI, etc.) will be discussed in Working Group 2.

REPORT ON OCG 4

H. Schink reported (TD-26) on the last meeting of the ETSI OCG (Operational Coordination Group) meeting.During this meeting, the Common ETSI Approach to Standards Development (CEASD) was presented (in TD-26Annex A). In order to strengthen ETSI’s position in ITU meetings, ETSI Technical Bodies are requested to installand to nominate coordinators for their area of standardization. TIPHON was requested to comment on the CEASDand the coordination with ITU.

ITU-T SG 2

A contribution was sent from the TIPHON 5 meeting to SG2 requesting a country code for a global numberingscheme for internet telephony. In addition, a liaison was drafted by Working Group 4 (reported in TD-52, LiaisonReport).

LIAISONS

The liaison report (TD-52) summarizes internal (to ETSI) and external (of ETSI) liaisons. Current liaisons includeSMG, TC STQ (TD-34), SPS 5 (TD-66), ITU-T SG 2, ITU-T SG16 (TD-51), and ATM Forum.

The following outgoing liaisons or replies to liaisons were drafted (see WP reports below for details):TD-64: Liaison Statement from TIPHON (WG3) to SMG (Special Mobile Group, GSM) requesting information on

the desirability of GSM codecs in VoIP applications.TD-68: Request for Study of the E.164 Numbering Requirements for Internet Telephony (for SG2)



TD-70: Liaison to ITU-T on coordination issuesTD-79: Liaison Statement to ITU SG16 requesting a change in wording in H.323 to reflect the wide use of GSM

codecs and other codecs in the future. The desired wording was not included.TD-80: Liaison Statement to ETSI project STQ responding affirmatively to their offer to assist on end-to-end QoS

issues.TD-84: Liaison to ISO/IEC/JTC I/SC6/WG6 providing TD-76r2 (TIPHON-02001) for information and requesting

comments.TD-85: Liaison to TIA TR-41 (ANSI) providing TD-76r2 (TIPHON-02001) for information and requesting

comments.

A liaison contact person within ITU-T SG16 was not appointed during this meeting. The liaison contact personwill need to have a long affiliation with the Study Group work.

WORK PLAN AND PROJECT PLAN

TD-28, Issues for Interoperability between IP based networks and PSTN/ISDN/GSM Overview, indicates theproposed new structure of TIPHON documents. The ideas of “phone to PC”, “PC to phone” etc. now should becalled “scenarios.” The documents would be assigned to the following project phases:

Phase 1: Covering all issues of scenario 1Phase 2: Covering all issues of scenario 1 and 2Phase 3: Covering all issues of scenarios 1, 2, 3, and 4, and amendments to documents of Phases 1 and 2The meeting agreed to the new document structure.

Scenario 1: Communication between IP network based users and PSTN/ISDN/GSM users, in which the call set-upis originated by the IP network user.

Scenario 2: Communication between IP network based users and PSTN/ISDN/GSM users, in which the call set-upis originated by the PSTN/ISDN/GSM user.

Scenario 3: Communication between PSTN/ISDN/GSM users, using IP based networks for the connection/trunkingbetween the involved users

Scenario 4: Communication between IP network based users, using PSTN/ISDN/GSM for the connection/trunkingbetween the involved users.

During the currently planned phases of the project it is assumed that the IP connectivity is already established. Dial-in procedures, ISP authentication, LAN access protocols etc. are for further study.

D. Gurle (ETSI) presented the chart of the project plan (TD-19). See www.etsi.fr/tiphon (public area) for the currentproject plan.

WG 1, REQUIREMENTS

TD-12 is the report of WG1. WG1 decided to reuse DTR-01001 (Requirements for service interoperability, Scenario1) as a base for DTR-01002 (Requirements for Service Interoperability Technical Aspects of Accounting [Charging/Billing] and Security, Phase 2). During drafting sessions, the group made appropriate modifications to supportPhase 2. Due to lack of time, chapters 7.2 (Supplementary Services), 8 (Addressing), 10 (Accounting), and AnnexA (Business Rules) could not be completed; it was agreed that they will be discussed via the email reflector.

TD-24, Revisions to the Security section of DTR/TIPHON-01001 V1.2.2 (1998-01) (P. Sijben, LucentTechnologies), was addressed in WG1. The WG1 chairman will send the latest version of DTR-01002 to TCsecurity for review.

The following time table for DTR-01002 was agreed:

Milestone Expected dateStable Draft 15 March 1998 (email reflector)Approval by WG1 15 April 1998 (TIPHON-7)Approval by TIPHON 15 June 1998 (TIPHON-8)

WG 2, ARCHITECTURE

DTS/TIPHON-02001 was approved by WG2 and was submitted to the plenary as TD-76r1. Approval at projectlevel is expected during the next TIPHON meeting. The full title of this document is: “Interoperability for Voice



Services Between Switched Circuit Networks (SCN) and IP Networks; WG 2: Network Architecture and ReferenceConfigurations; Phase 1: Telephone Calls Originating in an IP Network and Delivered to SCN Networks.” TD-13r1is the report of WG 2.

ARCHITECTURE RELATED TOPICS

TD-25, Gateway Location (P. Sijben and L. Spergel, Lucent), proposes an approach for defining the TIPHONGateway location and proposes to use the Wide Area Network Service Location protocol (an IETF Internet draft).This paper assumes the gateway is linked to the service provider and therefore may provide different services (cost,QoS, capabilities) depending on the service provider.

TD-49, Gatekeeper Cloud Architecture (G. Kimchi, ETSI STF 114), indicates that SG16 decided to start work on theGatekeeper to Gatekeeper interface and asks whether TIPHON should be involved in the definition of this interface.It also discusses the capabilities to be provided by this interface. TD-50, Interworking Between TIPHON Networksand GSM Networks (also from STF 114), provides an interworking scenario between IP-based networks and GSMnetworks. Roaming is supported by using functions provided within the GSM network.

Based on these contributions, WG2 decided:• To add a function called “backend services” to the TIPHON reference configuration as well as the related reference

points• To further discuss whether to add a function called “Gateway advertising” or “Gateway reachability”• To further discuss whether to define in detail the relationship between two or more Gatekeeper functions

(capabilities supported on the interfaces, Gatekeepers architecture, etc.)• To check whether the interoperability with mobile networks is sufficiently covered in the security section

In order to progress the Gatekeeper to Gatekeeper architecture, an ad-hoc session was chaired by G. Kimchi (ETSISTF 114, VocalTec). TD-74r1, the ad hoc report, proposes that TIPHON WP2 define the scope of applications forGatekeeper to Gatekeeper communications. Further email discussion is necessary in order to deliver protocolrequirements to the next Q13/16 Rapporteur’s meeting (April 14–17, before the next TIPHON meeting April27–30).

SECURITY ASPECTS

TD-23, Security Considerations for DTS/ TIPHON-02001 (S. Thomas, TransNexus), proposes text for section 8 ofDTS/TIPHON-02001, regarding trust relationships. The meeting agreed to integrate the text into the deliverableafter some amendments. It was agreed to add information on the relationship between the reference points in TD-23(subsequently changed into information flows) and those in Figure 1 of the deliverable.

TD-48 (H. Schink and P. Kainser, Siemens) provides comments on security issues to an earlier draft. Commentswere either taken into consideration in the new version or have become obsolete.

PRIVATE ISDN / PABX

TD-38 (S. Moore, Siemens) provides a number of additions to DTS/TIPHON-02001 to include information onprivate ISDNs. TD-45 (J.P. Albinet, Alcatel) provides a number of additions for DTR/TIPHON-01001 regardingoperation with PABXs and private circuit switched networks.

WG2 agreed to include information related to PABX, where applicable in the architecture deliverable. It also agreedto use the term PISN (Private Integrated Services Network) in accordance with ETS 300 172.

M ISCELLANEOUS

TD-37 (B. Van Doorselaer, Alcatel) proposes that TIPHON introduce profiles in order to improve the specification ofspecific cases. It was indicated that WG1 will work along this concept and that other WGs are supposed tocomplement their deliverables accordingly. No action was required from WG2.

TD-40 (S. Moore, Siemens) provides both technical and editorial comments to the deliverable, while TD-41 (S.Moore, Siemens) proposes a number of changes to current text in order to make it normative.

TOPICS FOR FURTHER STUDY

• Gatekeeper to Gatekeeper architecture (first inputs provided in TD-74)• Impact of H.323 proxy on the TIPHON architecture (ref. TD-36, see WG5 report below)• Real-time fax



PROGRESSION OF WORK FOR DTS/TIPHON-02002

The current version of DTS/TIPHON-02002 (V 0.0.2), provided by the editor, B. Van Doorselaer (Alcatel), includesthe new outline. TIPHON members are requested to provide contributions on commonalties and differences betweenthe TIPHON Scenario 1 and Scenario 2 architectures.

WG 3, CALL CONTROL

TD-14 is the report of WG3. DTS/TIPHON-03002, Call Control Flows for Basic Calls from an H.323 Terminal toa PSTN/ISDN/GSM terminal, was considerably extended and is expected to become a stable draft during the nextTIPHON meeting. A new version (V1.3.1) of DTS/TIPHON-03002 will be distributed.

TD-22, Carrier Selection for TIPHON (L. Spergel, Lucent), regards three different scenarios in which a selection of aspecific PSTN/ISDN/GSM carrier is desired. After clarifying the scenarios during the discussion, it was agreed toperform carrier selection by transmitting the necessary information to the gatekeeper and gateway within the calledparty number field. This functionality is already supported by H.323; no changes are necessary. This procedure doesnot preclude overlap sending.

TD-32 (G. Meyer, Siemens) provides an amendment to DTS/TIPHON-03002 (Basic Call Setup) on Call Release,Gatekeeper Disconnect. Since H.323 also allows the gatekeeper to be an entity which may clear an active call, WG3agreed that the corresponding message flows shall be mentioned in DTS/TIPHON-03002. The text of thecontribution will be inserted into the basic call deliverable.

TD-35, Basic Call (J. Holm, Ericsson Infocom), contains many suggestions of new text for the basic call deliverableand for the structure of DTS/TIPHON-03002. After discussing the structural proposals, WG3 agreed to a completerevision of DTS/TIPHON-03002, using much of the proposed text of TD-35 but stating that this new text is not yetapproved.

TD-36 (M. Lucchina, Cisco) suggests deployment of proxy for multimedia traffic. After discussion, it was agreed tostate that the use of a proxy is not within the scope of DTS/TIPHON-03002. The implications of using a proxy arefor further study.

TD-39 (S. Moore, Siemens) requests that DTS/ TIPHON-03002 include support for Private ISDNs in order to alignit with the current WG2 deliverable. The suggestion was accepted. Some editorial changes are also requested in thetext of the Call Clearing specification to allow for the possibility of delaying the clearing on the SCN side foradministrative reasons. This was agreed; it was also agreed that a basic call should normally clear as soon aspossible.

TD-44, Preferred Codec Selection (G. Kimchi, STF 114), proposes to perform the selection of a codec and thespecification of a certain preferred codec in accordance with chapter 7.2.2.2 of H.245v3 using CapabilityDescriptors.WG3 agreed to this mechanism and clarified that its application is also possible if H.323v2 FastConnect is used.

TD-47 (P. Mart, GPT Ltd.) contains some new text proposals for the basic call deliverable. It was agreed to copythe text to the deliverable and to indicate the non-approved state of this text in the deliverable.

TD-77 contains a description of “H.245 tunnelling” which is allowed by H.323v2. The point was made that thistechnique will be very important for future call set-up scenarios. It was agreed that the issue of tunnelling of H.245is independent of the issue of using FastStart. There was consensus that FastStart should be mandatory, both forinterworking reasons and to minimize Call Set-up times. Whether support for tunnelling in a basic TIPHON call isoptional or mandatory will be the subject of future contributions.

WG 4, NAMING, ADDRESSING

DTS/TIPHON-04001 was approved by WG4 and submitted to the Plenary as TD-72. Approval at project level isexpected during the next TIPHON meeting. The full title of DTS/TIPHON-04001 is “Interoperability for Voiceservices between SCN and IP Networks; WG 4: Naming and Addressing; Scenario I: Interworking from IP Terminalsto SCN Terminals.” TD-15 is the report of WG 4.

ITU SG2 CONTRIBUTION

At the previous TIPHON meeting (#5), there was a joint WG4/NA2 meeting which sent a contribution to a SG2Rapporteur’s meeting. This contribution was delivered by T. Holmes (BT and NA2), who prepared an informalmeeting report with suggestions for a follow-up contribution. This report was circulated on the TIPHON mail



exploder. PTA (Austria) offered to bring a follow-up contribution to the ITU-T SG2 meeting March 3-13 inGeneva.

The new contribution, TD-68, Request for Study of the E.164 Numbering Requirements for Internet Telephony, wascompleted during the WG4 meeting and was sent to ITU-T SG2 as a PTA contribution (K. Sambor and R. Stastny).

PHASE 1 DELIVERABLE DTS/TIPHON-04001

TD-41 (S. Moore, Siemens) provides suggestions on the structure of the DTS/TIPHON-04001 documents. It wasaccompanied by a working document with specific examples of how the suggestions in TD-41 could be applied tothe WG4 deliverables. This working document was used during the line by line review and most of its suggestionswere adopted.

TD-42 (S. Moore, Siemens) provides input on private numbering plans. Many of the proposals were directed at theScenario 2 deliverable. The proposals directed at the Scenario 1 deliverable were discussed and incorporated.

Drafting was completed on the Phase 1 deliverable, DTS/TIPHON-04001. WG4 approved it as TD-72.

PHASE 2 DELIVERABLE

The chair will modify the Phase 2 deliverable consistent with the editorial changes to the Phase 1 deliverable.

WG 5 QUALITY OF SERVICE

TD-16 is the report of WG5. The primary objective of this meeting was to reach consensus on the draft documentDTS/TIPHON-05001, General Aspects of QoS, and to approve it as a stable draft.

EFFECTS OF ECHO CANCELLERS ON MOS

TD-69 (T. Hatala, Motorola) describes the negative effects of echo canceling on MOS. It describes convergence (thedelay of the canceller, up to 2 sec in real world) and contrasting based on experience using G.165 (echo canceller).Contrasting occurs when comfort noise with echo cancellers is used where background noise is present. This causesa disturbing effect of alternate comfort noise and background noise. Contrasting becomes more noticeable withdigital end to end circuits which enable users to hear noises of less than -60 dBm. Echo cancellers may cancel about-34 dB ERL (echo return loss) and then employ echo suppression, with comfort noise insertion to attain a betterERL. This came to light during the work of the Voice over Frame Relay forum. The paper notes that MOS testsshould include testing under conditions of convergence and contrasting to realistically reflect the VoIP systemperformance.

DEPLOYMENT OF PROXY FOR MULTIMEDIA TRAFFIC

TD-36 (M. Lucchina, Cisco) suggests deployment of proxy for multimedia traffic. A discussion ensued concerningthe effects of implementing such a proxy architecture on QoS. At a separate meeting to discuss this in more detail,Cisco explained how a proxy might be used to carry out address translation (similar to the action of IP security firewalls) and also to carry out intelligent routing for QoS. An example of this intelligent routing was given where avoice call might be routed over the PSTN instead of IP during severe congestion.

One issue raised was, if each ISP establishes border proxies like this, then their use may seriously degradeperformance as call setup is established across multiple ISPs.

Although the discussion was of interest, it was suggested that, in order for WG5 to include this architecture in itswork:

1. WG2 should formally include it in TIPHON architecture2. More detailed information on the call setup protocol was needed.

Cisco continued the discussion in WG2 which agreed to study the issue further.

PREFERRED CODEC SELECTION

A broad discussion was held concerning the proposal from Ericsson to recommend the inclusion of GSM as a defaultCodec. WG5 was reminded that it was not within the scope of TIPHON to recommend default or baseline codecs ofany kind. It was decided to send a liaison to the ITU SG16 requesting that additional codecs be added to H.323. TD-79 is the approved liaison.



REVIEW OF DRAFT DTR/TIPHON-05001

D. Gurle (ETSI), who chaired the WG5 meeting in Sophia Antipolis, presented the changes that he had made to draftDTR/TIPHON-05001, General Aspects of Quality of Service (QoS). WG5 supported the new structure. A laterdiscussion was held to determine how the document might be structured so that it could evolve in line with theevolution of TIPHON’s scenarios. It was decided to isolate issues that would be generic to all scenarios.

M. Buckley (Lucent) had suggested that, given the importance of the work of WG5, it would be of benefit to have aseparate editor for the deliverables. M Buckley was approved as editor by WG5.

The document was further reorganized during separate sessions and an additional table was added to the QoS budgetsection. These changes were incorporated into the latest draft, TD-54. This document is still in process and cannotyet be considered stable.

The reference architecture diagram is required by WG5 so that clear points of measurement can be provided to WG6.Agreement was obtained from WG1, WG2 and WG3 that WG5 could draft this reference architecture and that theywould reference this. G. Kimchi (STF 114) helped to build a more detailed architectural diagram which was alsoincorporated.

WG 6 VERIFICATION

DTR/TIPHON-06001, Verification and Demonstration Implementation; Implementers Handbook and Test Reports,is expected to be approved at working group level during the next TIPHON meeting (#7). Final approval is plannedfor TIPHON Meeting 8. TD-17r1 is the report of WG6.

TD-39, Proposal for applications trials (H. Schink, Siemens), proposes a structure to support evaluation of trials.

TD-75 has been prepared outlining the relations between TIPHON-Net and the IMTC H.323 Implementers group.For the present, the two groups will keep each other informed. In the future it may be desirable for the H.323Implementers group to utilize TIPHON-Net for WAN testing. J. Toga of Intel offered to provide the relevantdocuments from the H.323 Implementers group to WG6.

TIPHON-NET DEPLOYMENT

TIPHON-Net is a permanent installation of TIPHON gateways and gatekeepers all over the world which will serveprimarily for validation of the TIPHON specifications.

Microsoft informed the WG6 chair that, due to organizational considerations, it appears that Microsoft will be unableto set up a TIPHON-Net node in the near future. The possibility exists that they may be able to do so at somepoint. Microsoft still expects their NetMeeting product to be widely used as the PC client for TIPHON-Net.

The protected TIPHON-Net WWW server containing the site information has been set-up by Infonova (URL:www.infonova.at/tiphonnet). Sites-owners have access to all the information required to configure the gateways forall TIPHON scenarios.

VocalTec kindly offered their gateway to companies that want to participate in TIPHON-Net. The details of thisoffer are in TD-83.

Status of current TIPHON-Net sites are shown in Table 1.

MANUFACTURER DECLARATION OF CONFORMITY

TIPHON5 TD-39 was presented by M. Blaschitz at the previous TIPHON meeting. It was approved on the WGlevel with some modifications. WG6 decided to forward the document to the ETSI legal department for approval.

It was agreed that there shall be two different TIPHON-logos: One for marketing general information, and anotherfor indicating TIPHON compliance.

NEW TIPHON-RELATED EQUIPMENT AND SERVICES

Reconc i l ia t ion Serv iceThe following TIPHON-Net sites showed interest in a clearing house functionality service offered by TransNexus andwish to experiment with that service for the purpose of TIPHON-Net:

–PTA–VocalTec



–Ericsson–ETSI

This service actually verifies a scenario which is currently discussed in WG 2 “Architecture.”

TIPHON-Net Site Status CommentsPost and Telekom Austria(Vienna, Graz)

Up and running. Currently the VocalTec Gateway 3.1A is used. It is expected infuture to update the gateway to version 4.0 and also to test alsoother gateway manufacturers in TIPHON-Net.

France Telecom (Caen) Up and running.ETSI (Sophia Antipolis) Up and running.Deutsche Telekom (Berlin) Up and running. Currently the VocalTec Gateway 3.1A is used. ISDN-Router

should be investigated. MICOM sites could be available infuture.

Ericsson (Stockholm) Up and running.CSELT (Torino) No new information available.Sprint (Kansas City) No new information available.VocalTec (Israel) Site will be set up

before nextmeeting.

Version 3.1 A of the VocalTec Gateway will be used. ISDNconnectivity will be investigated. Another possibility is toinstall a 2 MB satellite connection to INRIA in SophiaAntipolis. This will be investigated further.

TransNexus (Atlanta, USA) Up and running.pulver.com (New York, USA) No new information available.Mediatrix (Quebec, CAN) No new information available.3Com (Utrecht, NL, possibleother sites)

Set up before thenext meeting.

The site will be connected via an ISDN router to TIPHON-Net.

Lucent (site to be determined) It has been confirmed that Lucent will participate at TIPHON-Net.The details still have to be established.

Ascend (site to be determined)) D. Nastri, Sales Director EMEA Multimedia Access Business,announced at the NGI conference in Paris that Ascend wouldparticipate in TIPHON-Net. Site location (UK?)

Motorola (site to be determined)) Motorola expressed interest in TIPHON-Net. Detaileddiscussions will take place before the next meeting.

Cisco (site to be determined) Cisco is considering joining TIPHON-Net. The details arecurrently established. It is envisaged that one site will be inEurope and another in San Jose.

China Telecom China Telecom is very interested in this project. They willdiscuss whether and how to participate. China Telecom also has asimilar project. China Telecom has requested access to theTIPHON documentation (account, password).

Table 1. Current Status of TIPHON-Net Sites.

Address Resolution ServerExperimental test server for phase two address resolution to prove the feasibility of a global service code for IPtelephony. Implementation is available for WG6 members for the purpose of testing within TIPHON-Net.

Speaker Phone SoftwareSpeaker phone software will be provided by Lucent (Contact point: M. Buckley).

Evaluat ion of Service Provis ionSiemens proposed to conduct an evaluation of service provision on TIPHON-Net. It was felt that this would giveimportant feedback to user requirements group and to the QoS group.

IPv6Digital is offering support for migrating and testing of TIPHON-equipment with regard to IPv6.

QoS InternetCisco is offering support for migrating and testing of TIPHON-equipment with regard to QoS Internet.

IP-Telephony Cl ientVocalTec Communications will make Internet Phone client software TIPHON-compliant and expects it to be widelyused. The Internet phone client is also being offered to TIPHON-Net.



Microsoft also expects their NetMeeting product to be widely used as the PC client for TIPHON-Net.

Network Performance Test SoftwarePTA will develop a software that can be installed on TIPHON-Net sites to gather statistics about networkperformance achieved in TIPHON-Net. PTA will provide an evaluation of the data collected.

DEFINITION OF TIPHON-NET TESTS AND INTEROPERABILITY TESTING

Detailed definitions of test will be made on the WG6 exploder based on the progress made in WG5. A firstverification of the QoS assumptions made in WG5 shall be performed prior to the next meeting.

SUPPORT OF THE EUROPEAN COMMISSION

The TEN-Telecom (Trans-European Telecommunications Networks) program promotes the implementation of thetrans-European services and applications of the information society, based on the use of telecommunication infras-tructures. The current TEN-Telecom call for proposals was published on January 15, 1998 on the Basic Network.The following (more related) call for proposals will be published on March 15, 1998 on the Generic services andApplications. The calendar and the new work program of TEN-Telecom can be found on the European CommissionDirectorate General XIII (Telecommunications, Information Market and Exploitation of Research) web sitewww2.echo.lu.

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.



ETSI TIPHON MEETING ROSTER, FEBRUARY 16 – 20, 1998, SANTA CLARA, CA

Helmut Schink, Siemens TIPHON ChairmanMohammad Mahloujian, Ericsson WG1 ChairmanJozef Vandenameele, Alcatel WG2 ChairmanGerald Meyer, Siemens WG3 ChairmanLouise Spergel, Lucent WG4 ChairmanBarry Castle, 3Com WG5 ChairmanMichael Blaschitz, Infonova WG6 ChairmanHost: Cisco Systems

3Com Barry Castle3Com Ismail Dalgic3Com Stan NaudusAlcatel Lee JenkinsAlcatel Jozef VandenameeleAlcatel Bell Bart Van DoorselaerAlcatel Bus. Sys. France Jean-Pierre AlbinetAT&T Vito JokubaitisAT&T Laboratories Hal PurdyBellcore Michael RamalhoBritish Telecom Morgan PotterCisco Systems Michael FrendoCisco Systems Greg GoodknightCisco Systems Steve HratkoCisco Systems Mike KnappeCisco Systems Massimo LucchinaCisco Systems Craig MulhollandCisco Systems Hussein SalamaCisco Systems Ashok SarafDeutsche Tele. Berkom Ingmar KlicheDeutsche Tele.Berkom Thomas ScheerbarthDialogic Corporation Steven MagnellDSP Group, Inc. Murat SonmezDSP Group, Inc Serdar YurdakuleFusion, Inc. John ElliotEricsson Infocom Jan HolmEricsson Telecom Mohammad MahloujianEricsson Telecom Ulf ThuneETSI Laurence FerrandETSI David GurleETSI STF 114 Gur KimchiFrance Telecom Olivier HersentFrance Telecom Christophe ProustGPT Philip MartHewlett-Packard Labs Claudio CataniaHitachi, Ltd Tohru HoshiHitachi, Ltd. Keiko TanigawaInfonova Michael Blaschitz

InnoMedia, Inc. Nan-Sheng LinInnoMedia, Inc. Jacek MinkoIntel Corporation James TogaKPN Research Daniel MaddenLucent Bell-Labs Thomas AprilleLucent Technologies Mike BuckleyLucent Technologies Paul SijbenLucent Technologies Louise SpergelLucent Technologies Hans Van der VeerMaxim Chris LawsonMotorola Ted HatalaMotorola Defu ZhangMSAF Ron HirstNokia Jarno RajahalmeNokia Research Center Marko SuoknuutiNokia Telecom. Tapio SiikNortel Francois AudetNortel Mo ZonounOefeg/PTA Richard StastnyPost & Telekom Austria (PTA) Klaus SamborRadvision, Inc. Orit LevinRoyal Dutch PTT Richard WestergaSiemens Helmut SchinkSiemens AG Thomas GrewingSiemens AG Gerald MeyerSiemens AG Wilhelm WimmreuterSiemens GEC Steve MooreSiemens Telecom Nwks Tom MillerSiemens Telecom Nwks Mourad Oulid-AissaSiemens Telecom Nwks Sergio VerduciSonus Networks Inc. Rubin GruberSonus Networks Inc. Michael HluchyjTelia Prosoft AB Stefan BerggrenTransNexus Stephen ThomasTrillium Digital Sys Rajeev GuptaUnisys Gerfried HandkeVocaltec Comm. Ltd. Scott PetrackWMA Securities, Inc Philip Wang

The next issue of Communications Standards Review – Telecommunications (Vol. 9 #4) is scheduled for May -June 1998.



REPORT OF TR-41 USER PREMISES TELECOM EQUIPMENTFEBRUARY 23 – 27, 1998, ALBUQUERQUE, NEW MEXICO

TR-41.1, MULTI-LINE TELECOMMUNICATION SYSTEMS

Reporter’s note: Due to internal changes, the TR-41.1.1, MLTS Transmission chair (C. Sacco, Bellcore) wasunable to attend and will not continue as chair. Thus, transmission issues were covered as a discussion item in TR-41.1. It was proposed that both working groups’ activities should be treated this way; the rationale being that: a)generally, the same people attend the working group and subcommittee meetings, b) the administrative work ofreports, document control, etc., could be reduced, and c) the level of activity is decreasing in the groups - particularlyin TR-41.1.9, E911. For this time, TR-41.1.9 did have a separate meeting; this will probably not be the case at thenext TR-41 meeting.

T1E1 LIAISON

There was no formal T1E1 liaison report. T1.411 (E911) is now finalized and has been forwarded to the AmericanNational Standards Institute (ANSI); availability is expected soon. Work is proceeding on network-implementedcoin-operated pay phones; issues concern signaling methods. Work continues to update T1.401-1993 (InterfaceBetween Carriers and Customer Installations - Analog Voicegrade Switched Access Lines Using Loop-Start andGround-Start Signaling); a letter ballot is expected by year-end. A proposal was made for a new standard on networkdata messages to off-hook Customer Premise Equipment (CPE), e.g., calling identity delivery on call waiting.

TIA-464B: R EQUIREMENTS FOR PRIVATE BRANCH EXCHANGE (PBX) SWITCHING EQUIPMENT

(A) Living List for Future Revis ionTR-41.1/98-02-001 (R. Frank, Siemens) contains the current living list for TIA-464-B, Private BranchExchange (PBX). The only additions relate to alignment with changes in FCC Part 68 on ring trip and transversebalance requirements, per TR-41.1/97-11-033 (J. Schick and E. Hansson, Nortel). There were no other changesto the contribution.

(B) Cross Reference to Related StandardsTR 41.1/98-02-003 (J. Schick, Nortel) provides a listing of TIA-464-B clauses which have pertinent cross-references in other published standards. The intent of this contribution is to provide readers of TIA-464-B withbackground of the source of many of the requirements in TIA-464-B. It was noted, however that this document isbased on the 1994 work towards preparing TIA-464-B and that the references have not been updated to reflect morerecent publishing of the referenced documents, nor is there any intent at this time to do so.

LINE-SIDE INTERFACE REQUIREMENTS

TR-41.1/97-11-032R1 (J. Schick, Nortel) is mainly an update of the project authorization request form (nowPN-4157) for writing a Technical Service Bulletin (TSB) for Basic Rate Interface (BRI) Terminal LinesideInterconnection to Multi-Line Telecommunications Systems (MLTS). It was again emphasized that the project goalis a TSB, not a standard; thus text in the contributions need to reflect guidelines for interconnection rather thanspecific requirements on either PBXs or terminals. The intent of this work item is to provide BRI Terminalmanufacturers with guidance in the development of terminals which would be broadly compatible across manyvendor BRI implementations, and to provide PBX vendors with knowledge of what terminal manufacturers areexpected to provide when operating behind a PBX. The contribution is not intended to serve as an implementationguide for PBX vendors on how to create a BRI interface.

TR-41.1/98-02-007 (P. Melton, Cortelco) describes high-level functional requirements for an MLTS BRI,compatible with public network BRI terminals. It covers physical access, bearer services, terminal modes, interfaceconfigurations, and supplementary services, as well as terminal-to-terminal information transfer. The contributionwill be modified in the context of stating guidelines, rather than requirements, for enabling BRI terminals to functionas PBX line-side equipment.

TR-41.1/98-02-009 , Proposed outline for a TSB defining an ISDN basic rate line side interface for PBXs (J.Needham, Mitel), identifies the basic [ISDN] message subset required for BRI terminal-PBX interoperability as wellas information elements which will not be supported. This contribution also will be modified in the context ofstating guidelines, rather than requirements for terminal/PBX messaging.



In addition to being a guide for BRI terminal manufacturers and PBX vendors, the TSB will also be of interest totelephony consultants and end users as customers. This TSB would better educate these classes of customers with re-spect to purchasing and integrating various BRI and PBX equipment.

P. Weismantel (NEC) offered to take on the editor role for this TSB and to provide a contribution for the nextmeeting which will be the strawman for the TSB. This contribution will be based on the above contributions, asmodified.

TRANSMISSION ISSUES : PRIVATE NETWORK TRANSMISSION PLANNING GUIDE (JOINT WORK WITHETSI)

There was extensive discussion on TR-41.1/98-02-008 (T. Tung, Siemens Business Communications, K.Cheung and J. Schick, Nortel). It represents North American network planning transmission parameters andplanning examples for inclusion in the global private network transmission guide being developed jointly with ETSISpeech Transmission Quality (STQ). It provides drafts of Annex C (Transmission Parameters for SpecificElements) and Annex D (Planning Examples). In general, there was agreement that the document is on track forconsolidation with the ETSI material; in order to complete the document, it was agreed that comments would be sentto the authors by March 20, 1998 and ratified via teleconference on April 3, 1998. The contribution would then bemerged, and the complete text sent to ETSI STQ. STQ has been invited to meet jointly with TR-41.1 during theregular TR-41 meeting in May in Norfolk, VA. [Reporter’s note: as of this writing, at least two STQ members haveaccepted the invitation to participate. It is planned that a full day’s meeting will be held to finalize the planningguide, as well as to explore potential future harmonization work between ETSI and TIA.]

Specific comments made during the meeting included:• Global concurrence of the long-term ISDN loudness values of Send Loudness Rating (SLR) = +8 dB, Receive

Loudness Rating (RLR) = +2 dB• Explicit identification of default values to be used in E-model analysis for parameters not specified in other

documents• Classifying wireless technologies as licensed and unlicensed (instead of “high-tier” and “low-tier”, as now in the

document)• Identifying wireless technologies by the appropriate North American termsR. Frank (Siemens) agreed to edit the draft with the above comments.

TRANSMISSION ISSUES : UPDATE OF TSB-32, L OSS PLAN APPLICATION GUIDE

TIA TSB-32, originally titled “DPBX Loss Plan Application Guide,” will be updated as a companion document tothe Private Network Transmission Planning Guide, based on examples for using the ETSI E-model in network lossdesign. The document will be based on the contributions made in 1997 on these examples; members were againasked to review TR-41.1.1/97-08-021 and TR-41.1.1/97-11-026 (both from J. Schick, K. Cheung and R.Britt, Nortel) so that the update could be completed.

QSIG INTEROPERABILITY

TR-41.1/98-02-002 (R. Frank, Siemens Business Communications) poses the question of whether or not TIAshould become more involved in conformance testing of Requirements specified by the ITU Q series Recommenda-tions (QSIG) between vendors in North America. Currently the ISDN PBX Network Specification Forum (IPNS)(secretariat in Dublin Ireland; www.qsig.ie/index.htm) provides similar testing for European vendors; there is asimilar forum in Japan. It was noted that IPNS is only open to vendors with a European presence. There is noNorth American equivalent organization.

TR-41.1 generally agreed that such involvement could be fruitful. Customers are now becoming motivated aboutQSIG and, without interoperability testing guidelines to ensure interworking between multiple vendors, interworkingissues will be resolved in the field on customer premises.

The proposal asks whether TR-41.1 should devise a Protocol Implementation Conformance Statement (NA PICS)which would delineate the minimum set of services/capabilities that all PBX vendors in NA would be required tosupport. [Reporter’s note: ISO (ISO/IEC 11572, Annex A) and ETSI (ETS 300-172) PICS could serve as startingpoints for the development of an NA PICS.]

It was agreed that the development of an interoperability test plan for QSIG is needed for any implementation of atesting environment. It was also suggested that, while standards for interoperability testing may not fall withinTIA’s charter, TIA needs to be consulted as to what its role could be in such a work item.



There may be a benefit in enlisting the efforts of other interested vendor/customer forums to assist in this effort.One such forum mentioned is Vendors ISDN Association (VIA); however, their interest in interoperability issues andactivity in testing, if any, needs to be ascertained.

R. Frank (Siemens) will provide a project proposal for the next meeting. J. Schick (Nortel) will investigate TIA’sposition relative to formulating QSIG interoperability test standards. Inputs from the membership on this issueshould be submitted as contributions for the next meeting. This proposal was also discussed in TR-41.10, see reportbelow.

TR-41.1 & TR-41.1.1 REFOCUS AND STREAMLINING

TR-41.1/98-02-005 (R. Frank, Siemens) addresses possible restructuring of TR-41.1 and its working groups. Itstates that there is too much overhead redundancy in separate working group and subcommittee meetings while theattendance at each is very low and to a large extent involves the same people. The goal would be to hold a singlemeeting at the TR-41.1 level which would span all the technical areas that are now covered by the separate workinggroups. Each technical area would have a designated discussion leader. Time and effort savings would come in theconsolidation of liaison reports, meeting requests, document control, rosters, and other administrative aspects. Inaddition, the contribution proposes that there again be a formally appointed secretary to enable the chair to focus onconducting the meeting.

TR-41.1/98-02-004 (J. Schick, Nortel) deals with TIA TR-41 as a whole and its strategic direction. The opinionexpressed is that the model of TR-41 has worked well for the last 20 years, but may not be adequate for the future.The world of technology is growing so quickly that customers and vendors do not want to wait several years before atechnology is adopted as a standard; therefore, a number of separate industry/customer fora have developed to assist inthe definition of new technologies. Participation from many companies have disappeared in TIA, particularly fromthe non-manufacturer segment. Nor is there participation from data networking companies which are increasinglymaking inroads into the voice market; e.g., Cisco, Bay Networks, Newbridge, etc. Globalization within TIA has tobe addressed considering that our markets as vendors are becoming increasingly more global each day. Standardsdevelopment should be performed in concert with international and other regional standards forums. [Reporter’s note:this contribution was also distributed at the TR-41 chair’s meeting, requesting that each subcommittee chair socializethe issue within their subcommittee, as well as their companies. It was learned that TIA, on a still higher level, hasa “TIA 2000” program in process to define how TIA as a whole should function in the coming years.]

TR-41.1.9, MULTI-LINE TELECOMMUNICATION SYSTEMS SUPPORT OF ENHANCED 911SERVICE

Only one issue was addressed: ISDN solutions for E911 signaling. TR-41.1.9 discussed the T1S1 proposed revisionof ANSI T1.607, ISDN-PRI Layer 3 Signaling. The issue is discussed in TR-41.1.9/98-02-002 (R. Frank,Siemens) (same as TR-41.1/98-02-006). The revision allows the passage of the caller “location” information forboth wired and wireless E911 calls, and is highly compatible with existing SS7 protocol. The Working Groupchair, A Caggiano (Lucent) gave a slide presentation of the proposed changes to the ISDN layer 3 signaling protocol,accompanied by TR-41.1.9/98-02-003 . The proposal will eventually be submitted to ITU-T for consideration,possibly this year. The chair requested all parties to submit comments on the revision to him by March 10 forconsolidation and submission to T1S1 prior to their March 23 meeting.

John Schick, Nortel

TR-41.2, CONFORMITY ASSESSMENT

EUROPEAN UNION - US MRA

TR-41.2/98-02-003 (TR-41.2 Chair) provides a list of Issues to be Resolved with the EU, in three separateareas:• Telecommunications (Product Certification)• EMC (Electromagnetic Compatibility)• Electrical Safety

TR-41.2/98-02-004 (European Commission) is a Status Report on European Union TelecommunicationsPolicy. TR-41.2/98-02-005 , Accreditation and the Community’s Policy in the Field of ConformityAssessment, is also an EC report.



Representatives from FCC, Association of Independent Scientific, Engineering and Testing Firms (ACIL), otherlaboratories and National Institute of Standards and Technology (NIST) will be meeting with EU officials to discussthe designation of Conformity Assessment Bodies (CABs) and other issues related to the implementation of theMutual Recognition Agreements (MRA). The MRA should be signed by the Parties by the end of April 1998.

Note: the US Department of Commerce has decided not to pursue additional agreements with countries belonging tothe European Free Trade Area (EFTA) at this time.

EUROPEAN UNION - CANADA MRA

It was reported that a delegation from Canada had met with the European Union to discuss concerns related to safetyissues. A working group has been formed in Canada to address safety issues.

At the January 1998 meeting in Brussels, the delegation continued to press for movement on the non-harmonizedradio regulations. The next issues being worked on are labeling and marking. The Canadian government is workingon their submission to the government council for the ratification of the MRA. It will likely be May or June 1998before this submission is ratified. The Canadian government has essentially completed drafting of agreements withsome of the EFTA countries. These MRAs are basically the same as the EU MRA.

APEC STATUS REPORT

The text of the MRA is being actively worked with the USA and Canada as leads (Canada holds the chair). It isplanned to have text available for agreement by June of this year. A proposal for designation of conformity as-sessment bodies has been put together on the basis of input received from other working groups (including the MRATask Force). TR-41.2/98-02-002 (P. Adornato, TR-41.2 Chair) is “Draft Designation and Monitoring Require-ments for CABs.” It is being discussed as part of the Asia Pacific Economic Cooperation Forum (APEC) MRA andwill be the basis of the Proposed FCC Notice of Proposed Rule Making (NPRM) on the changes to the regulatoryprocess due to MRA activities.

The next APEC meeting is scheduled for early March 1998 in Brunei. One of the contentious issues in the text ofthe proposed MRA is that for new technology, layers 2 and 3 testing should not be mandatory. A number of theeconomies are not prepared to agree to the clause at this time. The US and Canadian delegations are adamant thatthey want this clause to be included.

The criteria for definition of network harm have been agreed to previously in APEC and is consistent with theUS/Canada philosophy.

H. Mar (Industry Canada) has agreed to provide liaison to TR-41.2 on developments in the technical group onStandards Related Matters which is addressing safety related matters.

It was noted that the MRA will be a voluntary, not mandatory, agreement.

NAFTA/CCT PROGRESS

It was reported that the pending Memorandum of Understanding (MOU) for Canada and Mexico for exchange of testdata covers Information Technology Equipment (ITE) as well as telecom, but the USA MOU does not.

The Mobile Services Working Group (MSWG) completed a high level assessment of the major differences in thestandards issued by the three countries in the authorization procedures for cellular and mobile radio. The delegationgave a formal presentation of the homologation process.

Representatives from COFETEL (Comisión Federal de Telecomunicaciones de México) made a presentation to theConformity Assessment and EMC working groups on the rationale and procedures for the immunity requirements ofthe Emergency Mexican National Standards (NOM) Electromagnetic (EM)-151. Even though there is strongalignment of test methodologies, there are significant differences in frequencies and requirements between the NOMand ANSI-TIA/EIA-631 (Telecom-munications Telephone Terminal Equipment: Radio Frequency ImmunityRequirements for Equipment Having an Acoustic Output).

The Conformity Assessment Working Group reviewed a number of documents, including one which specifiesprocedures for laboratory accreditation. This document specifies a time frame of eighty days from the date of receiptof the application for completion of an accreditation. Other information presented at this and the Product SafetyWorking Group meetings had been that accreditation could take up to three years. The Mexican delegation has agreedto provide information on the status of the document (with the eighty day time frame) presented.

It was reported that the draft of NMX-250 (on safety) has been prepared but has not been reviewed by the board ofNYCE. NYCE is the Certification Body accredited by SECOFI (Mexican Ministry of Commerce and Industrial



Development) for the electronic and processing data sector. The next meeting of this board is in March 1998. Thisstandard will be an NMX (Normas Mexicanas, i.e., not mandatory). SCT (Ministry of Communications andTransports) cannot make this a NOM (i.e., mandatory standard). The SECOFI DGN (Director General de Normas)will have to make the determination of whether this should be a NOM. At present, Mexican laboratories are not setup to test to this new NMX. A logical proposal will have to be made to SECOFI so that an appropriate transitionperiod can be determined. Mandatory standards are the exclusive purview of the government, and SECOFI will haveto be convinced of the need to change the standard. The NMX-250 standard would replace three individual standardsthat apply to equipment at present. It was stated that if SECOFI were to agree to change today, it would take aminimum of eighteen months for the transition.

Once the board of NYCE approves the NMX-250, application is made to the SECOFI DGN’s national standardscommittee for acknowledgment to publish it as an NMX. This would happen no sooner than April 1998 and itwould be published in the Official Gazette.

The next Consultative Committee - Telecommunications (CCT) meetings are scheduled for Toronto the last week ofSeptember 1998.

OSHA RELATED ACTIVITIES

P. Adornato (Nortel, TR-41.2 Chair) reported that a letter had been sent in January from the Presidents of TIA andInformation Technology Information Council (ITI) to OSHA executives asking for a meeting to discuss ourindustries’ position on changes to OSHA’s requirements for accreditation and testing for safety in the workplace.

RECIPROCITY DISCUSSION

The ITI has pressed for removal of the MRA clause from the declaration of conformity requirements for Part 2equipment authorization requirements. This clause requires that parties located outside of the United States or itspossessions will be accredited only if there is a mutual recognition agreement between that country and the UnitedStates that permits similar accreditation of U.S. facilities to perform testing for products marketed in that country.

The rationale of the ITI is that the FCC is not a trade agency and this is outside their terms of reference. However, itwas pointed out at the TR-41.2 meeting that the Trans-Atlantic Business Dialog (TABD) Conformity Assessmentposition paper calls for regulatory agencies to facilitate trade in addition to their primary functions, public health andwelfare. The FCC clause does not appear to be significant with respect to the European-US MRA since its signingis expected shortly. However, TR-41.2 believes the FCC clause provides significant leverage for futuretelecommunications trade negotiations such as the APEC MRA and the Free Trade Agreement of America.

There was consensus in TR-41.2 that the clause in Part 2 should be retained for equipment authorized under aDeclaration of Conformity. However, the FCC should allow for an interpretation of the clause that permits sub-contracting arrangements by accredited laboratories as permitted by ISO Guide 25. TR-41.2 agreed that the textwithin the clause, “the party performing the measurement,” should be interpreted to include accredited laboratories,including those covered within the scope of the Note to paragraph (d) in Part 2. TIA, ITI, ACIL and other interestedindustry groups will develop a consensus position to present to the US Government.

CONFORMITY ASSESSMENT MATRIX

There was a brief presentation of the updated conformity assessment matrices. These matrices were included in thehandout material at the “Removing Technical Barriers to Trade” seminar. There was agreement to add Part 2 underEMC requirements for United States. It was also noted that the FCC has now issued the harmonized Part 68 rules.

The summary of outstanding issues for NAFTA implementation was presented by D. Haataja (UL).

The working group on the matrices will meet (likely in April 1998) to revise the matrices prior to the next TR-41.2meeting.

MARKING AND LABELING

TR-41.2 will continue to follow the activities related to this subject. In the TABD, the concept of single marking isbeing addressed. P. Adornato (Nortel) has agreed to provide a copy of a related TABD paper to TR-41.2 members.

OTHER HIGHLIGHTS

TIA will be instituting a reaffirmation process for subcommittee chairs every three years. Therefore candidates whoare interested in being considered for a chair were requested to identify themselves to the TR-41 chair and provide aletter of commitment from their companies.



A working group met to draft comments on the proposed CAB designation proposal. A second working group metto draft a letter to US Department of Commerce (DoC) and FCC on the accreditation clause related to Declaration ofConformity for PC’s.

TR-41.3, ANALOG AND DIGITAL WIRELINE TELEPHONES, JOINT MEETING WITHCSA T-510/IEEE

No patents relevant to the work in TR-41.3 were identified.

LIAISONS

CSAD. Rittenhouse (Spectrum Sciences Institute) reported that Canadian Standards Association (CSA) has changed themembership matrices of committees. CSA practice has been to have balanced membership matrices with equalrepresentation from four categories of participants. They have opened membership to all interested parties on a trialbasis.

IEEER. Magnuson (Siemens) reported that IEEE recently met in New Orleans, LA. It is anticipated that PN-1329,Standard Method for Measuring Transmission Performance of Hands-Free Telephone Sets will be published in 1999.

IEEE-269, Standard method for measuring transmission performance of analog and digital telephone sets, is due forreaffirmation by the end of this year. However, the IEEE committee is in the process of redefining the scope of thisstandard. They are considering whether to include wireless devices, artificial ears other than the IEC type, andwhether to coordinate IEEE-269 with TIA/EIA-579. Because of these considerations, work on the new issue ofIEEE-269 will likely not be completed this year.

The next meeting of IEEE is in Quebec City, June 3-5, 1998.

ETSID. Rittenhouse reported he had received a list of draft ETSI standards available for comment. He will distribute thislist by E-mail.

EDC FUNCTION

D. Dulmage (CLI) reported that he will not be able to act as ED Coordinator due to uncertainty of continuedparticipation on this committee. D. McKinnon (Thomson) has volunteered to take on this responsibility.

INVESTIGATION OF REPLACEMENT OF WECO 221 RELAYS

J. Bipes (Mobile Computing) reported that Midcom has develop inductors that give essentially equivalent results tothe WECO relays in side-by-side comparisons. He has tested these in his lab with good results. The part numbersare as follows:

WECO Relay Midcom Substitute221FAE 671-4893 rev.02221A 671-4905221FAC 671-4251

Midcom has published application notes for these relays. The application notes are identified as Midcom no. AD-671-9235 and are available electronically on Midcom’s web site: http://www.midcom-inc.com.

TIA-470-B P UBLICATION STATUS

It was reported that TIA/EIA-470-B, performance and compatibility requirements for telephone sets with loopsignaling, had gone to Global Engineering Documents (http://global.ihs.com) for publication. TR-41.3/98-02-003is a list of errors in the recently published TIA/EIA-470-B. These errors were discussed at TR-41.3 and it wouldappear they were the result of conversion from one software format to another when the document was being preparedfor publishing. It was reported that Global has suspended distribution of the new standard pending correction of theseerrors. Chair D. Rittenhouse will obtain an electronic copy of the document from TIA and make the corrections.



R. Magnuson (Siemens) reported that the capacitor specified in the feed circuit of Figure 44 of the standard for off-hook metallic impedance measurement gives rise to non-compliant results for telephones which previously met theserequirements. The capacitor value was 125 µF in the previous version of the standard and has been changed to 10 µF(20 µF in parallel with 20 µF). TR-41.3/98-02-005 (R. Magnuson, Siemens) provides the ERL Measurementsper TIA-470-B. There was substantial discussion of this issue. It was decided that a contribution would besubmitted for a revised value. This will discussed at the next TR-41.3 meeting.

TIA/EIA-504-A AND CSA-T515 PUBLICATION STATUS

Both TIA/EIA-504-A and CSA T-515 have been published. These two harmonized standards define acoustic andmagnetic output requirements for handset telephones intended for use by the hard of hearing.

EIA/TIA-579 L ETTER BALLOT STATUS

PN-3724-1, Telecommunications Telephone Terminal Equipment Transmission Requirements for Digital WirelineTelephones, Revision of EIA/TIA-579, was sent for a default ballot to those who had responded to the originalballot. Sixteen responses were received: 11 approved, 1 approved with comment, and 4 no comment.

The ballot with comment was received from C. Mandeville, P.E., US Navy. The comment was: “Suggest addIEEE-661 as a reference document.” It was noted that IEEE-661 is referred to in Annex B.

PN-4078 TYPE II ENHANCED CALLING FEATURES

PN-4078 is performance and multiple extension interworking for Type II (off-hook) CPE caller ID. D. McKinnon(Thomson Consumer) reported that TR-41.3.1 had made very good progress on PN-4078. Bellcore will provide di-rect feedback on MEI (Multiple Extension Interworking). Bell is still conducting field tests and requesting comment.See http://www. bellcore.com/DIGEST/JAN98/hala.html for further information. In order to review the Bellcoreresults, TR-41.3.1 plans to have an extended two day meeting at the next TR-41 meeting, with evening sessions.The Bellcore contact is S. Pitrowicz ([email protected]).

PN-3674 TYPE I ENHANCED CALLING FEATURES

It was reported that the Type I (on-hook) document SP-3674 for default ballot closed January 6, 1998. One ballotwas received from Mitel. The comments were accepted. The document will now go to the next level of approval

FCC NEGOTIATED RULEMAKING ON HEARING AID COMPATIBILITY

TR-41.3/98-02-002 is a letter from TR-41.9 to Ms. G. Matise, Chief, Network Services Division, Common CarrierBureau, FCC. This letter addresses a number of issues related to the interpretation of Parts 68.112 and 68.317. Thisletter was provided for information of TR-41.3 members. (See additional details in the TR-41.9 report, below.)

A. Wride (TR-41.9 chair) reported that TR-41.9 will be sending a letter to FCC with the following information:

“It was the consensus of the group that a minimum gain of 12 dB meets the intent of the rule. The limit of 18dB maximum is a requirement to provide automatic reset to nominal level when the device is placed back on-hook; e.g.,• Telephone provides gain adjustable from 0 dB through 11 dB - Does not comply• Telephone provides gain adjustable from 0 dB through 12 dB - Complies• Telephone provides gain adjustable from 0 dB through 18 dB - Complies• Telephone provides gain adjustable from 0 dB through 19 dB- Complies if reset provided.”

TR-41.3 considered adding an addendum to TIA/EIA-504-A providing a specification for the number of steps for gainadjustment. Some members indicated they intend to provide a contribution for consideration as an addendum to thestandard.

There was consensus that TR-41.9 should be advised that TIA/EIA-504-A has been published. It was agreed topropose to TR-41.9 that they consider introducing this for rulemaking on Part 68 to replace the existing HACrequirements.

FCC COMPLAINT ON BELL TAP

It was reported that FCC Common Carrier Bureau had indicated that they receive about one-half million complaintsper year on bell tap. J. Balinski (Bellcore) stated that carriers have not been experiencing significant complaints.



J. Bipes (Mobile Engineering) reported that some measurements of signals occurring on a subscriber line have beenmade. Recurring 100 Vp-p 1/2 Hz square wave signals were recorded. J. Bipes proposed that it might be appropriateto specify a similar type of signal as a means of evaluating terminal equipment. L. Bell (Wyle Labs) has agreed tosend D. Rittenhouse copies of the measurement information, for distribution to TR-41.3.

As discussed at the previous meeting, TR-41.3 sent a letter to T1E1 requesting information on line test signals sentout by carriers that might contribute to Bell Tap. No response has been received. Chair D. Rittenhouse (SpectrumSciences Institute) agreed to send a letter to T1E1 with information on the signals recorded by Wyle Labs (100 Vp-p1/2 Hz square wave), asking them to advise if this is a known network signal.

STUTTER DIAL TONE PROJECT, PN-4159

A new Working Group has been formed, TR-41.3.2, to develop a standard for Stutter Dial Tone, PN-4159. J. Bress(AST Technology Labs) has agreed to chair this working group. D. McKinnon (Thomson Consumer) has agreed tobe the editor.

PROPOSED NEW PROJECT - STANDARD FOR COMBINED WIRELESS HANDSFREE/HANDSET DEVICE

It was reported that a standard is being developed by ETSI for wireless devices (such as cellular and in-house PCS),which switch from a handsfree level to a handset level. R. Britt (Nortel) proposed that TR-41.3 take on a project todevelop requirements for volume control adjustment of devices which switch from handsfree to handset mode, but usethe same transducer. This will be discussed at the next TR-41.3 meeting.

TR-41.5, MULTIMEDIA - BUILDING DISTRIBUTION SYSTEMS

TR-41.5 continued their work on development of a standard that will establish the minimum application, feature, andoperational requirements for a Residential Gateway.

TR-41.5/98-02-004 (R. Cochran, GTE) discusses the services that will be delivered via the Residential Gatewayand proposes minimum requirements for Entertainment, Communication, Information, and Home AutomationServices. TR-41.5/98-02-003© (R. Cochran, GTE) contains the draft Residential Gateway Standard. The systemoverview and functional requirements sections are well along. The physical requirements section is at an early stage.TR-41.5/97-02-007 (K. Kerpez, Bellcore) discusses the significance of the internal digital interface of theResidential Gateway (RG) and provides tutorial overview of the possible “bus” technologies: PCI, Compact PCI,Small PCI, CardBus (PCMCIA), IEEE 1394, ATM-Utopia (Universal Test and Operations Physical layer Interfacefor ATM), Fibre Channel and Universal Serial Bus (USB). This document recommends that a single internal digitalinterface technology be specified as mandatory and that one or two optional internal digital interfaces be specifiedwhich are bridged to the mandatory internal digital interface.

TR-41.5/98-02-004 (R. Cochran, GTE) proposes simultaneous service delivery activities and provides theimpetus to establish minimum bandwidth requirements for internal digital interface as well as the associated activeport requirements of the Residential Gateway. It proposes that the RG must be capable of the followingsimultaneous service activities:• Four set top boxes (STB) or equivalent• One user connected to a remote LAN via protected QoS IP (work-at-home)• One user browsing the Web, non-protected QoS• One active voice band circuit capable of all CLASS services and ISDN-BRI• One lifeline POTS circuit powered from the CO

Following discussion of the issues, TR-41.5 agreed the criteria were valid and decided to incorporate the essence ofthe proposal into the draft working document in a new section covering “Bandwidth Requirements.” It was lateragreed that the bandwidth issue will be revisited again when an internal digital interface technology is selected.

TR-41.5/98-02-005 (E. Boye, Lucent) proposes revised text for Section 5.13 which covers SecurityRequirements. Although it was agreed that the text is not stated in requirement terms, it will be used to replace theexisting text in the draft working document with the understanding it will be “refined” at the meeting.

TR-41.5-02-006 (K. Kerpez, Bellcore) notes the strategic role of the RG controlling all communications into/outof the premise and therefore the need to protect the RG from hacker and environmental hazards. This requires a fire-wall of some kind between the premise system (e.g., CEBus) and the RG, an interface agreement between thenetwork interface and the RG, and a responsibility boundary between the service provider and the user, both of whommay have some level of access to the RG.



TR-41.5/97-02-007 (K. Kerpez, Bellcore) discusses the significance of the internal digital interface of theResidential Gateway and provides tutorial information about possible “bus” technologies. Based on the ensuingdiscussion, TR-41.5 agreed that selection of a single technology for the internal digital interface is essential to enablefurther development of the RG specification. Accordingly, TR-41.5 established the framework of a process that willlead to selection of the technology at the November 1998 meeting.

TR-41.5/97-02-009 from the TR-41.5 Chairman describes the process of establishing a single internal bustechnology. The framework involves refining the scope, decision process, and polling procedures of the selectionprocess at the next TR-41.5 meeting (Norfolk, VA, May 11-12, 1998), presentations and contributions keyed to thedecision process at the following meeting (Calgary, ALB, August 16-17, 1998, and summaries and voting at theNovember 1998 meeting (Palm Springs, CA, November 16-17, 1998). Also included in the process are attendanceguidelines for new and lapsed members to enable them to establish voting status by the November 1998 meeting. Inthe meantime, parties interested in development of the Residential Gateway specification are being invited by a letterfrom the TR-41.5 Chairman to participate in refinement of the selection criteria and in the ensuing digital interfaceselection process.

TR-41.5/97-02-008 is a TR-41.5 working document. This first pass lists criteria and weighting of the criteriafor the selection process.

For additional details on TR-41.5’s activities, contact Jim Romlein, Chairman, +1 920 262-8000, or via email [email protected], or Richard Cochran, Secretary, +1 972 718-6293, [email protected].

TR-41.6, W IRELESS USER PREMISES EQUIPMENT

TR-41.6 is working on standards based in large part on DECT (ETSI 300 175) standards.

TR-41.6.1 (Personal Wireless Telecommunications) requested three new project numbers from TIA for adding threesupplemental data sections to the TIA/EIA-662 Personal Wireless Telecommunications (PWT) standard:

1. Data Service Profile C Class 1 (ETS 300 699, interworking with V.24 interfaces)2. Data Service Profile C Class 2 (ETS 300 651, interworking with V.24, connection oriented)3. Data Service Profile E Class 2 (ETS 300 757, messaging)

TR-41.6.1 received the results of the Industry ballot on SP-3952, Personal Wireless Telecommunications: CustomerPremises Access Profile (CPAP) Test Specification:Yes: 8No: 0No comment: 3

SP-3952, the supplement to TIA/EIA-662, was approved to be sent to TIA for publication as TIA-662-10B.

TR-41.6.1/98-02-03© (P. Murray, Ericsson) provides revisions to PN-4079, Draft Data Services Access Profiles A(low speed frame relay) and B (high speed frame relay) Class 1. The work on PN-4079 is now complete and it willbe sent out for a committee letter ballot.

Resolution of ballot comments on SP-3614-1, Personal Wireless Telecommunications - Enhanced InteroperabilityStandard (PWT-E), will continue. A conference call will be held March 31, 1998. Details will be on the TR-41.6reflector.

Work on the TIA memo referencing “Request for Information” regarding wireless (and related) TIA standards is notyet complete.

TR-41.6.3 (PACS-WUPE) received editorial corrections to PN-3447, Personal Access Communications Systems-Wireless User Premises Equipment (PACS-WUPE) Minimum Performance Standard for Personal Stations Sup-porting Common Air Interface Interoperability Standard, from the TIA. These changes will be incorporated into PN-3447, and sent to TIA for publication as soon as possible. TR-41.6.3 is working on PN-4127, Revision A of thisstandard, and had been unaware of the outstanding editorial corrections.

TR-41.6.3/97.11-014R1 (B. Scales and M. Karimian, MTCC Panasonic), discusses adjacent channel emissionlevel modification, proposing a new specification for the out of band emission level to comply with the FCCrequirements.

TR-41.6 met jointly with TR-41.10 to review several ISO mobility documents. Please see the report of the jointmeeting under TR-41.10, below.



TR-41.7 SAFETY AND ENVIRONMENTAL CONSIDERATIONS

T1E1.7

The next revisions of T1.313, Electrical Protection of Central Office Facilities and T1.316, Electrical Protection ofTelecommunications Outside Plant Facilities, have been submitted for final publication by ANSI. Work is continu-ing on the “Electrical Protection of Broadband Facilities” project. A project on Bonding and Grounding ofTelecommunications Network Equipment is under way jointly with T1E1.5.

IEEE 1100 EMERALD BOOK

The IEEE Committee has reviewed and resolved all comments and re-circulated the IEEE 1100 document (theequivalent to a default ballot). The next meeting on IEEE 1100, Recommended Practice for Powering and GroundingSensitive Electronic Equipment, is May 1998.

NEC (NATIONAL ELECTRIC CODE )

The Report on Comments (ROC) on the 1999 National Electric Code (NEC) has been generated. It is available tothe public as hardcopy, CD ROM or on their Web Site: www.nfpa.org. The only issues mentioned by the NECrepresentative were the separation distance between the telecom and power ground, not allowing the telecom entranceto be mounted on the power mast and the separation of telecom and power service mast. If the ground separation isgreater than 5 feet but less than 20 feet, a separate ground rod must be driven and connection provided to the powergrounding system with #6 cable. The co-location of power and telecom facilities on the same entrance mast is notallowed. The annual meeting to finalize the code will be held in May 1998. The beginning of the cycle for the2002 NEC will be the fall of 1999.

NAFTA CCT

Significant progress was made in the Product Safety WG at the February Consultative Committee -Telecommunications (CCT) meeting in Mexico City. The Mexican delegation had obtained Mexican governmentapproval for the format of their IEC-950-based voluntary Standard, NMX-I-250-1997. Underwriters Laboratories (UL)is going to generate a document comparing the NMX to the Bi-National UL-1950/CSA-950 Safety Standard for thenext meeting, which will be held mid-year, likely in Canada.

ANSI/TIA/EIA-631, I MMUNITY STANDARD

TR-41.7/98-02-03 (R. Breden and S. Jones, TIA) contains the marketing plan timeline for ANSI/TIA/EIA-631-1996, Standard on Radio Frequency (RF) Immunity for Telephones. The plan includes press releases, articles in theTIA Industry Pulse publication, developing measures of success, preparing promotional material, preparing amember questionnaire, adding Radio Frequency Interference (RFI) web pages to the TIA website, reviewing andupdating, if necessary, the TIA RFI brochure, supporting a half day seminar on RFI and EMI at SUPERCOMM’99,and measuring the success of the program. There was basic agreement with the plan and timeline. The measures ofsuccess, member questionnaire, and review of the RFI brochures are scheduled for the May 1998 meeting. Otherissues of concern voiced by TR-41.7 were label recognition and TIA-631 problems. UL provided formal informationabout a program they have initiated which could provide label recognition and/or certification. The cordless testingrequirements in TIA-631 were found to be too constraining. Contributions on the subject are invited. They couldprovide the basics for an amendment to TIA-631.

SP-3283A, ENVIRONMENTAL CONSIDERATIONS

TR-41.7/98-02-02 (TR-41.7 Chair) contains the balloted draft of SP-3283-A-1, Telecommunications UserPremises Equipment Environmental Considerations. TR-41.7/98-02-04 (TR-41.7 Chair) contains all thecomments on SP-3283-A-1. There were three no votes, but Lucent did not receive a ballot and likely would havevoted no. There were several yes votes but none with comments. The no votes still concerned the M-2 surge in4.3.3.3. The reason for the three no votes was the M-2 surge had too low an I2t value.

The Bellcore ballot had one editorial and four minor technical comments. Technical comments 1 and 3 recommendedremoving the diodes from figures 3 (c), (d), and (e) and adding the following after the first sentence of 4.3.3.2, “TheEUT shall be dc powered and the normal operating interfaces shall be applied to telephony leads, including the leadsbeing surged, unless stated otherwise. NOTE:” Technical comment 2 would not be applicable if there wasconsensus on the e-mail discussed below for the M-2 surge. Technical comment 4 recommended changing the L-3peak voltage from 1500 to 1000. Comments 1, 3, and 4 were approved. The editorial comment was not discussed.



It concerned the term Customer Premise Equipment (CPE), which is not defined in this standard. Its use in thisstandard is probably consistent with the use by the telephone industry.

Bellcore and GTE had proposals for other surge generators for M-2. There was no consensus on either proposal.Another proposal was discussed which did have consensus. This proposal was the FCC Type A 800V, 10x560microsecond 100A surge. It has an I2t of 4.0 which is about 4 times the highest value of I2t recorded in the BellLabs surveys made in the 70’s. The characteristics of the generator provide reduced I2t values when a few ohms ofEquipment Under Test (EUT) resistance is present. For example, the I2t value is reduced to approximately 1.0 whenthe EUT has 8 ohms of surge impedance. Two of the manufacturers present stated that many of their CPE had atleast 8 ohms of surge impedance and survived the FCC Type A surge. There was consensus that CPE whichsurvived that surge would be reliable in the field. The disadvantage of that surge is that CPE which uses a protectioncircuit with no significant surge impedance, for example a solid state sideactor in series with a fuse, which would seethe entire 4.0 I2t; yet if it survived a surge with an I2t of 1.0 it would likely be equally reliable in the field. It wasagreed to approve SP-3283-A-1 for default ballot with the changes discussed above, if consensus was reached on theM-2 surge proposal after being e-mailed to TR-41.7. The TR-41.7 Chair agreed to e-mail the proposal.

TR-41.7.1 H ARMONIZATION OF INTERNATIONAL SAFETY STANDARD

BI-NATIONAL SAFETY STANDARD, UL-1950/CSA-950

The revised draft third edition of the Bi-National Safety Standard, Standard for Information Technology Equipment,Including Business Equipment, Canadian Standards Association (CSA) 22.2 no. 950/UL 1950, was expected to bepublished by year end 1997 but publishing has been delayed. It contains the fourth amendment of InternationalElectrotechnical Committee (IEC) 950 Second Edition as deviations since the IEC 950 Fourth Amendment has notbeen published. The Fourth Amendment of IEC 950 is expected to be published early this year. Once IEC 950Second Edition, Fourth Amendment is published, CSA 950/UL 1950 can be republished with the respective devia-tions changed to requirements. There was no report from the November 1997 CSA 22.2 Committee meeting inToronto. There is a meeting of the UL 1950 Industry Activity Committee (IAC) scheduled for April 23-24 in SantaClara, CA. The member list will be trimmed to remove multiple company attendance and non-UL members.Telecom representation could become a problem in the future. For now J. Brunssen is representing Bellcore andcould represent Alliance for Telecommunications Industry Solutions (ATIS). It was suggested that UL contact ATISfor a formal liaison and at that time suggest that J. Brunssen (Bellcore) could provide a liaison. The Bi-NationalWorking Group (BNWG) may be scheduled as an action of the UL 1950 IAC meeting.

IEC 950 (INTERNATIONAL)

Voting on the Committee Draft for Vote (CDV) for the Third Edition of IEC 950 has completed. This will becomeIEC 60950, Third Edition, when published. The acoustic safety limits may be removed from this edition because ofthe threat of a no vote on the CDV by some nations. Final approval and publication of the third edition is estimatedto be late 1998 or early 1999. Work items on the first amendment of the third Edition have begun and will bediscussed at the next WG7 and WG8 meetings. The next US Technical Advisory Group (TAG) will be in Aprilwhen the CDV will be considered for a simple yes/no vote from the TAG. The WG7/8 and TC 74 meetings willfollow in May. Any new work items such as Telephone Network Voltage (TNV) circuit changes, remote feed, andcoaxial connection safety will be slated for the First Amendment of the Third Edition. Work is under way on aproposal to add requirements for coax interfaces to IEC-950 including, under certain conditions, a 10 kV impulse likethe one in IEC-65. TR-41.7.1/98-02-03 (TR-41.7 Chair) contains the draft IEC proposal to IEC 60950 forremote power feeding over a telephony twisted pair facility. In the US this has been traditionally used for poweringT1 repeater spans. The modern spans provide up to 140 volts at a constant current of 60 milliamps. The span volt-age may be negative or positive and negative. The proposal limits the current on any line on the span to 60 ma butallows the voltage to reach 800 volts between lines and under certain controlled conditions to reach 1500 volts.There is a limit of 2 milliamps which may be conducted to ground through 2000 ohms. This is likely to be a hotlydiscussed item.

LeRoy Baker, RELTEC

TR-41.8, COMMERCIAL AND RESIDENTIAL PREMISES WIRING

The TR-41.8 report will be published in the next issue of CSR-T.



TR-41.9 REGULATORY CONSIDERATIONS ON TERMINAL ATTACHMENT PROGRAMS

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

A. Wride reported that TIA has revised the Engineering Manual, and has changed the period of reaffirmation ofcommittee chairs from two years to three years. This means that every third year, an incumbent chair needs to bereaffirmed by the committee in order to continue serving. This also means that it is an opportunity for anycommittee member to submit his candidacy for the position. Any committee members interested in being consideredas the Chair of TR-41.9 should let C. Berestecky (TR-41 Chair) or R. Breden (TIA) know by the May 1998 TR-41meetings. Candidates will have to provide a letter of support from their companies.

TAPAC, TAPAC TTF, TAPAC ATF LIAISON

H. Mar (Industry Canada) reported that the Terminal Attachment Program Advisory Committee (TAPAC) and itstask forces last met February 3-4, 1998, in Ottawa.

The re-balloting of the draft proposal on Hearing Aid Compatible (HAC) Receive Volume Control has beencompleted. All the members voted yes, some with editorial comments. These comments were incorporated in theproposal and voted out at this meeting. Industry Canada is translating it into French and will publish an amendmentto CS-03 with a Canada Gazette notice soon.

It was reported that Bill C-17, amending the Telecommunications Act and the Teleglobe Canada Reorganization andDivestiture Act, was passed by the Canadian House of Commons in December 1997. The bill is now in the handsof the Senate for approval. The text of the bill can be viewed and downloaded at the web site of the CanadianParliament:

http://www.parl.gc.ca/3b/l/parlbus/chambus/ house/bills/government/C-17/C-17_3/C-17-coverE.html.

Industry Canada is also preparing an amendment to CP-01, Issue 8, for all the proposed changes TAPAC hasapproved so far.

The next meeting of TAPAC and its task forces will be June 17–18, 1998, in Quebec City.

B. Corey, (Industry Canada, IC) made a brief presentation on Specific Absorption Rate (SAR).

SAR is the rate that electromagnetic energy is absorbed in the human body, expressed in W/kg. Radio devices usedwithin 20 cm of the body will require SAR evaluation. In Canada, SAR is measured by use of an artificial subject(phantom) with simulated brain tissue. Canada’s Safety Code 6 contains the limits for exposure. Industry Canada’sRSS 102 Draft incorporates these limits. SAR Measurement facilities must be accredited by Industry Canada.Interim measurement guidelines are provided by IEEE C95.3. The specified measurements include SAR for the eye.SAR by numerical simulation methods is not allowed.

FCC ADMINISTRATIVE COMMITTEES AND PROCEEDINGS LIAISON

R. Cook (Bellcore) reported that this working group has not met since the last TR-41.9 meeting.

ADMINISTRATIVE JOINT HARMONIZATION GROUP LIAISON

The Administrative Joint Harmonization working group had worked to simplify the process for application forregistration/ certification in the U.S. and Canada. A number of meetings have been held and the process ofcomparing the FCC and Industry Canada application requirements has been completed. The working group will nowbegin a proposal for a harmonized application form (using the Industry Canada application form software). TR-41.9/98-02-004 (TR-41.9 Chair) contains the summary record of a December 2, 1997 subcommittee conferencecall. TR-41.9/98-02-012 (TR-41.9 Chair) contains the summary record of a January 13, 1998 subcommitteeconference call. A nearly complete comparison document (Version VI) has been created. The next steps are: topropose a common application format suitable for both the FCC and IC with as little variances as possible;harmonize the format of the test reports.

TIA SEMINAR

It was reported that there was a TIA seminar, addressing issues related to removal of technical barriers to trade,conducted on February 18 and 19. This was well attended and a successful enterprise.



FCC

A task group was formed at the November 1997 meeting of TR-41.9 because the FCC had inadvertently redefined thebandwidth as 500-4,000 Hz. After a small working group had met in Washington DC to review this issue and workon a solution, the group became aware that the FCC had corrected this error. TR-41.9/98-02-015 (FCC)provides the correction. No further action was necessary.

TR-41.9/98-02-020 (FCC) contains a list of 31 FCC proceedings as part of the 1998 biennial regulatory review(http://www.fcc.gov). Among items of direct interest to TR-41.9 are Common Carrier Bureau (CCB) proposals forTesting New Technologies, Part 68, Mutual Recognition Agreements and Part 68, 56 Kbit/s Modems (power levelchanges). The Office of Engineering Technology (OET) will be looking at Part 2, Subpart J: Private SectorApproval. This is a proposal to streamline the equipment authorization program by implementing the recent MutualRecognition Agreements (MRA).

TSB-31-B PART 68 HARMONIZED STATUS

The 43rd FCC Industry meeting was held February 20, 1998. TR-41.9/98-02-019 (W. von Alven, FCC)contains information on the items presented at that meeting.

The FCC Part 68 harmonized rules have been published in the Federal Register. These rules will become effectiveApril 20, 1998. There are numerous mistakes, both technical and non-technical associated with the rules. The FCCspecifically asked TIA to submit a list of all the errors to the order and offered to issue an errata list without anypetition from industry. T. Tung (Siemens) and Anh Wride (CCL) prepared a 17 page list. The FCC published thetechnical errata list (TR-41.9/98-02-022) February 12, 1998. The list of non-technical errors has not beenpublished yet.

TSB-31-B has been published by TIA. A limited number of copies were available at the TIA seminar on February18-19, 1998. Copies may be ordered from Global Engineering Documents (http://global.ihs.com).

Test procedures for the harmonized Part 68 rules must be filed with the FCC by April 1, 1998. Only those testprocedures which are additional or have changed because of the harmonized rules need be filed (provided procedureshave been previously filed for Part 68 testing).

PCM MODEMS (V.90)

TR-41.9/98-02-016 (R. Perez and B. Lerich, Bellcore) contains the results of preliminary testing on December16–17, 1997. Tests were conducted with up to six modems with output analog power of -6 dBm. No crosstalk wasdetectable on a cable pair in a 25 pair cable.

Review of signal power level limits to accommodate 56 kbit/s modems has been proposed by the FCC CCB(Common Carrier Bureau) as part of their 1998 proceedings, which may give rise to a Notice of Inquiry or a Noticeof Proposed Rulemaking. There was consensus that there was still insufficient data to enable the development of arecommendation on this issue. It was agreed that further action on this item should be deferred pending the outcomeof activities in committees such T1A1.7, as well as FCC proceedings. J. Bipes (Mobile Engineering) and S. Bipes(CoEv) have volunteered to prepare a summary of the general opinions of TR-41.9 as expressed around the tableregarding 56K modems. This summary will be submitted at the May 1998 meeting.

ADSL

TR-41.9/98-02-006 (A. Wride, CCL) and TR-41.9/98-02-008 (A. Wride, CCL) contain liaisons to T1E1.4on Asymmetric Digital Subscriber Line (ADSL) requirements to be added to Part 68. TR-41.9/98-02-009 (T.Starr, T1E1.4) contains the reply from T1E1.4 noting that T1E1.4 is currently discussing PSD (power spectraldensity) requirements for ADSL and feels it is premature to make a specific proposal to the FCC. TR-41.9/98-02-010 (P. Walsh, Paradyne) proposes FCC Part 68 technical requirements and definitions for customer premiseslocated ADSL terminal equipment. The contribution is principally based upon the Canadian CS-03 provisionalADSL requirements.

FCC/IC REQUESTS:

Class Dev icesTR-41.9/98-02-007 . In response to a request from Telephone Equipment Supply Inc. (forwarded to TR-41.9 byW. von Alven, FCC) for the means to control multiple message waiting lights on a single line (e.g., several collegestudents using a single phone), TR-41.9 agreed with the response provided to A. Wride (CCL) by T. Russell



(Philips). This response notes that the request is for a new feature that is technically possible but needs to be addedto the appropriate CLASS standards and implemented by the equipment vendors and service providers. This is not aPart 68 issue.

On-Premises S/T with Encoded Analog ContentTR-41.9/98-02-005 (W. von Alven, FCC) was the basis of a discussion on whether an attestation should beused in lieu of testing for analog content at the ISDN S/T interface. Discussion on the Canadian CP-Ol/CS-03section 5.2 exemption provision revealed that it was an obsolete requirement adopted in 1989-90 when testequipment was difficult to obtain. TR-41.9 recommended that because testing is applied at the U interface, there isno technical reason to use attestation for analog content in lieu of testing at the S/T interface. TR-41.9 agreed torecommend that TAPAC revisit the exemption as stated in CP-01 and delete this obsolete provision.

Flash and Dial ing To Control On-Premises DevicesTR-41.9/98-02-011 (W. von Alven, FCC) provides a technical description of the Door Answering System(DAS). The DAS uses a pushbutton at the front door to initiate a distinctive ringing on a standard telephone andthen uses the telephone hook switch to signal to open the door. The issues were divided into two categories:

1) The case when the door controller system was activated by the use of hook flash

2) The case when the door controller was activated by the use of digit dialing. It was unanimously concluded thatthe second case, (when the door controller was activated by the use of digit dialing) definitively violates68.312(k). In the first case, (when the door controller was activated by the use of hook flash), it was stated thatwhen the user was already off hook in an ongoing conversation, there is no harm generated; whereas the userpicking up the phone to answer the doorbell while not requesting network services would be considered aviolation of 68.312(k). It was mentioned that the FCC has already allowed CPE (customer premise equipment)to go off hook in violation of 68.312(k) for programming purposes, and that the hookflashing situation could beconstrued as another application of “exceptional uses.” The hook flash area was considered to be a “gray” area,and timing considerations were discussed. In the end, it was concurred that although the user of a CPE may beinitiating the action, and that CPE, not users, fall under the jurisdiction of Part 68, CPE should not be designedin such a way that would allow the user to intentionally violate Part 68 rules.

Reporter’s Note: C. Berestecky (Chair of TR-41) commented after the meeting that the intent of Section 68.312(k)is to prevent permanent shorting of the telephone line. Going off hook and drawing dial tone without a request fornetwork services is a violation of 68.312(k) in the truest sense. However, since the hookflashing lasts basically fora very short period, there should be no network harm generated in the practical sense.

Defect ive Equipment/ServicesTR-41.9/98-02-013 (A. Wride, CCL) is in response to a problem (passed to TR-41.9 by W. von Alven, FCC)with multiple telephones from several manufacturers in which the “four” digit in Dual Tone Multi Frequency(DTMF) mode is incorrectly received. The consensus of TR-41.9 was that there was not sufficient informationpresented to show conclusively whether the problem was one of improper generation of digits by the telephone or ifit was a problem with the Central Office tone receivers. It was identified that there are a number of voluntary per-formance standards which specify both DTMF dialer and DTMF receiver parameters, both for the CPE and for theswitch at the Central Office.

HAC TASK GROUP AND ACCESS BOARD

TR-41.9/98-02-014 (A. Wride, TR-41.9 Chair) is a copy of TR-41.9 correspondence on the FCC Report andOrder on Reconsideration, FCC 97-242, in the matter of “Access to Telecommunications Equipment and Services byPersons with Disabilities” (CC Docket No. 87-124). It proposes changes to text in Part 68 (68.112 and 68.317) toreflect the FCC decisions about Hearing Aid Compatibility (HAC).

TR-41.9/98-02-017 (FCC) and TR-41.9/98-02-018 (J. Green, Comdial) concern the interpretation of FCCPart 68.317 (HAC volume control). It was the consensus of TR-41.9 that a minimum gain of 12 dB meets theintent of the rule. The limit of 18 dB maximum is a requirement to provide automatic reset to nominal level whenthe device is placed back on-hook.

A proposal for correspondence to FCC on this issue was approved by TR-41.9. TR-41.9 Chair A. Wride willforward the proposal to B. von Alven at the FCC CCB, and to the Chief of the FCC CCB, as W. von Alven plansto retire in April 1998.



It was reported that the Architectural and Transportation Barriers Compliance Board (ATBCB) guidelines werereleased February 3, 1998 with an effective date of March 5, 1998. However, until the FCC issues its Notice ofProposed Rule Making (NPRM), it remains unclear how these guidelines are to be implemented.

It is expected there will be an NPRM issued by the FCC on the recommendations of the ATBCB during 1998, E.Hansson (Nortel) reported that the Americans with Disabilities Act (ADA) will be reissued with the interpretation inline with that of the ATBCB (as discussed in TR-41.9/98-02-017). He proposed that correspondence on theinterpretation on the required gain be copied to Ms. G. Matise at the FCC Network Services Division of the CCB.

TR-30.3 REQUEST FOR TIA-496 REVIEW

TR-30.3 previously asked TR-41.9 to review TIA-496, Interface between Data Circuit-Terminating Equipment(DCE) and the Public Switched Telephone Network (PSTN), to see whether it conforms with the latest Part 68rules. The reason for this request was that TR-30.3 is interested in updating this standard to bring it into alignmentwith Part 68, but their membership did not include those with Part 68 proficiency. A small working group wasformed at the November TR-41.9 meeting, in San Antonio, TX. TR-41.9/98-02-021 (TR-41.9 Chair) wasprepared as a result of the review, discussed and revised. It notes that chapters 3 and 4 and Appendix B need updating.In Appendix B, the methodology for calculating REN is different from Part 68. From Chapter 3 and 4, two pagesof items with differences were noted in the comparison of TIA-496 to the TIA submission of Part 68 (the FederalRegister version of Part 68 has many errors).

WEB REPORT

TR-41.9/98-02-023 (S. Roleson, Hewlett-Packard) contains a collection of web sites that are of interest to TR-41.9. A. Wride (CCL) and S. Roleson (Hewlett-Packard) have developed a beta version of the Part 68 issues webpages on the TIA website.

EU MRA AND APEC MRA - EFFECTS ON PART 68

P. Adornato (Nortel) reported that there have been numerous meetings in the past three months identifying questionsand concerns to be resolved by the respective governments during the upcoming familiarization period. A delegationfrom the US was in Brussels discussing questions and concerns with the European Community. It is expected thatfinal ratification of the EU/US and EU/Canada MRAs will take place in the May 1998 time frame.

It was also reported that Asia Pacific Economic Cooperation Forum (APEC) MRA discussions are moving forwardat a speedy pace. At the Hong Kong meeting in early January 1998, a proposed set of requirements for the designa-tion of CABs (Conformity Assessment Bodies) was prepared by the FCC and is under current discussion. The nextAPEC meeting will be in Taipei the week of March 8, 1998. The objective is to have finalized MRA text ready forsigning by the June 1998 time frame.

Anh T. Wride, Telecom Engineering Dir., CCL

TR-41.10, PRIVATE INTEGRATED SERVICE NETWORK (PISN)

The TR-41.10 meeting was chaired by M. Zonoun (Nortel).

US TAG REQUIREMENTS

TR-41.10 voted unanimously to become a US Technical Advisory Group (TAG) to ISO/IEC/ JTC1/SC6 WG6.This means that TR-41.10 will play two distinctive roles: one with respect to TR-41, and the other in connectionwith ISO/IEC/JTC1/SC6. As US TAG, TR-41.10 will directly input into ISO and will not require TIA approval.EIA, which has an administrative role between TR-41.10 and ISO, requested that TR-41.10 become a US TAG. TheUS domicile companies who wish to join the US TAG will have to pay $300 or $600, based on their level ofparticipation. TR-41.10/98-02-010 provides information on the EIA International Program Fee Policy. TR-41.10/98-02-012 (H. Cuschieri, EIA) is the request to TR-41.10 to become a SC6 US TAG.

US COMMENTS ON ISO/IEC 13869 ANDISO/IEC 13873

TR-41.10 approved two US contributions for submission to ISO/IEC/JTC1/SC6, for the May meeting. Lucent (M.Shah, Temporary Editor of the ISO/IEC standards above) submitted TR-41.10/98-02-017 and TR-41.10/98-02-018 on the interaction between Call Transfer (ISO/IEC 13869) and Diversion (ISO/IEC 13873). These two



defect reports address issues between US and ECMA approaches on how much of the information of a diverted callshould be preserved and provided on the redirected calls.

ETSI TIPHON - INTERNET INTEROPERABILITY WITH LEGACY VOICE NETWORKS

ETSI project TIPHON is working to develop standards for IP interworking with legacy voice networks includingPSTN/ISDN and GSM (see report in this issue of CSR-T). ETSI works closely with relevant committees and foraincluding ITU-T, IMTC/VoIP Forum. The TIPHON project focuses on voice communication and related voicebandcommunication applications as required to enable IP and PSTN/ ISDN/GSM interoperability. TIPHON project hasimpacts on enterprise network and other works in which TR-41.10 is involved. TR-41.10/98-02-015 , NewProject Proposal for TIPHON (M. Zonoun, Nortel), proposes to establish a new project to review TIPHON activi-ties and provide US views to ETSI. TR-41.10/ 98-02-015 includes the ETSI TIPHON Terms of Reference. TR-41.10 supported this project, and will monitor and determine the impacts on PISN and work with ISO/IEC/JTC1 toaddress any issues that arise.

Q-SIG COMPLIANCE

TR-41.1/98-02-002 proposes that TIA develop a conformance testing for Q-SIG for North America. Currently,the IPNS (ISDN PBX Network Specification) Forum provides similar testing for European vendors; there is asimilar forum in Japan. It was noted that IPNS is only open to vendors with a European presence. There is noNorth American equivalent organization.

This issue was also discussed in TR-41.1 (see report above). Both Nortel and Lucent suggested that ISO PICSalready specifies that compliance requirements (national specific requirements) should be avoided if at all possible.There are, however, a couple of exceptions that N.A. standards may differ from ISO (e.g., overlap sending) whichshould be addressed.

TR-41.10/98-02-016 , MLTS (multi-line telephone systems) Interoperability in QSIG (R. Frank, Siemens),addresses the Protocol Implementation Conformance Statement (PICS) Proforma, and MLTS interoperabilitytesting. The document questions whether TR-41.1 should be involved in PICS Proforma and MLTS interoperabilitytesting. It was decided that N.A. Q-SIG compliance should not be more than a one page document that will be anaddendum to the ISO PICS.

B-QSIG

TR-41.10 was debriefed on the progress of B-QSIG activities in ATM Forum. There have been several delays in thePNNI 2.0 (Private Network-Network Interface) schedule. A proposal was made in the ATMF that B-QSIG and GSS(Generic Supplementary Services) which were going to be included in the PNNI 2.0 should instead go out as separateballots for inclusion in PNNI 1.0. This will allow the B-QSIG standards which have already been completed tobecome available to the public. TR-41.10/98-02-019 , ECMA B-QSIG/DSS2 (Bosch Telecom), the 13th draft,was provided for information.

PRIVATE NETWORK MOBILITY

TR-41.10 met jointly with TR-41.6 and reviewed several ISO mobility documents:• TR-41.10/98-02-004©, ISO/IEC FCD 15431, Wireless Terminal Call Handling, ANF• TR-41.10/98-02-005©, ISO/IEC FCD 15429, Wireless Terminal Registration Supplementary Service• TR-41.10/98-02-006©, ISO/IEC FCD 15433, Signaling protocol - Wireless terminal authentication

supplementary service• TR-41.10/98-02-007©, ISO/IEC FCD 15430, Signaling protocol - Wireless terminal call handling additional

network features• TR-41.10/98-02-008©, ISO/IEC FCD 15432, Wireless terminal authentication supplementary service• TR-41.10/98-02-009©, ISO/IEC FCD 15428, Signaling protocol - Wireless terminal location registration

supplementary service and information exchange ANF• TR-41.10/98-02-013 , ECMA PUM Call Handling ANF• TR-41.10/98-02-014 , ECMA PUM Registration Supplementary Service

The first six documents are ISO FCD ballots. The last two documents, PUM (Private User Mobility) Call Handlingand Registration were for information. As a result of discussions, the US voted yes with comments on the ballots.A contribution will be submitted for the May meeting of ISO to propose several editorial changes based on thecomments.

Mo Zonoun, Nortel



PARTIAL MEETING ROSTER OF TR-41, FEBRUARY 23 – 27, 1998, ALBUQUERQUE, NM

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

Advent Instruments D. StennerAST Technology Labs James BressBABT Product Service Gene PangerBell Atlantic Trone BishopBellcore John BalinskiBellcore Jim BrunssenBellcore Ken KerpezBellcore B. LerichCCL Anh WrideCIDCO R. AndlikowskiCLI David DulmageCobra Electronics T. AhnCoEv, Inc. S. BipesComdial Corp. John GreenCompaq Jim CottrellCortelco Peter MeltonCSA Ajmer BalDSC Communications Marcus MaranheoEnergy Info Systems Jack AndresenEssex Group James TylerGTE Richard CochranGTE Rich PankoGTE Percy PoolGTE J. SmithGTE Telephone Ops Harry Van ZandtHewlett-Packard Scott RolesonIBM Microelectronics Wayne CaswellIBM Tom ToherIndustry Canada Robert CoreyIndustry Canada Henry MarIntelidata R. BradyIntertek George PageIntertek Testing Svcs G. PageITS Testmark Labs Ronald BernotITS Testmark Labs Cliff JonesIwatsu Bob ChrostowskiKTL-Certelecom David DulmageLucent Technologies Charles BeresteckeyLucent Technologies Emmanuel BoyeLucent Technologies Anthony CaggianoLucent Technologies Steven CrosbyLucent Technologies Bill Soler

Lucent Technologies Chuck TenorioMIS Labs Jim RomleinMitel P. ChingMitel Robert HamiltonMitel John NeedhamMobile Engineering John BipesMotorola Tim CottonMotorola Bruce NealeNEC America, Inc. Paul WeismantelNortel Pierre AdomatoNortel Roger BrittNortel Katherine CheungNortel J. FreestoneNortel Erik HanssonNortel Dermot KavanaghNortel John SchickNortel Scott TaylorNortel Bao TranOrthronics Greg ShankParadyne, Inc. P. WalshRaychem Al MartinReltec Corp. LeRoy BakerRockwell Semicon. R. RahamimSiemens Richard FrankSiemens R. MagnusonSiemens J. SieppelSiemens Tailey TungSpectrum Sci. Inst. Dennis RittenhouseSprint Amar RayStentor Efrain GuevaraTeccor Electronics Phillip HavensTeccor P. HavensTelCon Associates Dorothy LockardThomson Consumer Tuan LaThomson Consumer D. McKinnonThomson Consumer Clint PinkhamUnderwriters Labs David HaatajaUnderwriters Labs Randy IvansUnderwriters Labs Anh NguyenUniden America A. BaumUniden America J. ReynoldsWyle Laboratories Larry Bell



REPORT OF TR-30, DATA TRANSMISSION SYSTEMS AND EQUIPMENTMARCH 9 – 12, 1998, DALLAS, TX

TR-30.1 MODEMS

The TR-30.1 Chair announced that Adtran, Altocom, Cisco, Equator, Floreat, SGS Thompson, and ZyXEL werebeing removed from the voting list for failure to attend three consecutive meetings. Paradyne, which was reinstatedat the last meeting, was removed from the voting list for failure to attend the meeting immediately following themeeting in which they were reinstated.

TR-30.1 agreed to a proposal from the chair for cancellation of PN-3838, to develop a US PCM modem standard, inlight of the Determination of Draft Recommendation V.90 in the ITU-T. The chair also obtained permission toclose the TR-30.1 PCM ad hoc group.

The TR-30.1 Chair reported that document number TR-30.1/98-003-002 , Reasons to Implement Revised V.8bisin V.90, had been requested by ACTION Consulting but he had not received a copy of this proposed contribution andACTION Consulting was present. Technical editor’s note: This contribution was later distributed via the PCMmodem reflector.

LIAISONS

TR-30.1/98-03-004 (E. Eckert, T1E1 Chair), a liaison from T1E1, reports that the signal to noise number inSection I.2.1.5 of Annex of T1.413 Issue 2 was removed. It also reports that they are continuing to study thepotential non-linear effects of the POTS Splitter.

TR-30.1/98-03-003 (J. Magill, Chair WP 1/16) provides highlights of the recent SG16 meeting. It summarizesall the major items of work in WP1/16, touching on the progress in Q4/16, Q8/16, Q9/16, Q18/16, and Q23/16. Italso lists the meetings for the remainder of 1998. (See also the SG16 report in CSR-T 9.2.)

The V.90 editor (R. Williams, 3Com) requested to be notified of any editorial errors.

V.8BIS REVISION

TR-30.1/98-03-005 (L. Brown, Q4/16 V.8bis Rapporteur) is the draft revision to V.8bis which was Determinedat the last SG16 meeting. This is a proposal to provide a quicker startup using V.8bis. L. Brown asked thateveryone study this proposal closely as it is scheduled for Decision in September 1998.

V.90 (V.PCM)

TR-30.1/98-03-006 (L. Brown, Q23/16 Rapporteur) is the list of agreements for the V.pcm Recommendation,prior to the SG16 meeting.

TR-30.1/98-03-008 is a proposed list of agreements for V.pcm issue 2 and beyond from the Rapporteur. It wasagreed to expand the scope of the study to include the possibility of analog access at both ends of the connection anddata signaling rates of a non-synchronous nature. The TR-30.1 Chair promised that he would have an issue 2version of this document (retaining all global and issue 2 agreements) available at the April 1998 meeting.

The following V.90 items require further discussion:• The timing in Section 9.4.2 needs clarification. One possibility is 5 RT delays.• Clarify when signals are not spectrally shaped (e.g., DPCM in Phase 3)• Clarify how spectral shaping is controlled, and how it changes during rate negotiation.

Members were encouraged to discuss these and any other problems that they identify on the reflector.

INTEROPERABILITY

TR-30.1/98-03-007 (K. Chu, Rockwell) identifies a problem created for existing modems by the implementationof V.8bis. Specifically the CRe (capabilities request sent by autoanswering station at call initiation) signal isincorrectly detected as voice and causes modems to disconnect. Initial testing indicates that shortening the CResignal significantly reduces the problem. The proposal is to change the minimum duration of the CRe signal from400 ms to 285 ms. It was decided that companies should study this proposal with the goal that it be approved as aTR-30 contribution out of the next meeting.



The TR-30.1 Chair raised the issue of a recent problem with Motorola V.34 modems, which was created by theassignment of bit 5 in the recently approved revision of Recommendation V.8. When a modem detects a value inthis bit position, it disconnects. Remedies will be pursued prior to the April meeting.

Dick Brandt, dB Consulting

TR-30.2, DATA TRANSMISSION

ITU-T STUDY GROUP 16

The Chairman reported on the work relating to TR-30.2 at the ITU-T Study Group 16 meeting January 26 - February6 in Geneva.

TR-30.2/98-03-003 is the Q6/16 Rapporteurs Report. Attached to this report is D.92 (from the SG16 meeting,Deutsche Telekom AG, Germany), which proposes changes to Recommendation V.24. These changes would extendthe definitions of the interchange circuits to include statements on the sensitivity (state sensitivity and transitionsensitivity) as well as the appropriate changes in support of this proposal throughout the Recommendation. TheQ6/16 Rapporteur also intends to review the numerous V.24 interchange circuits and eliminate those which are nolonger used. The TR-30.2 chair requested that the members consider writing a response or proposal in the future.

TR-30.2/98-03-002 is the Q7/16 Rapporteurs Report. Of particular interest to TR-30.2 is the work on a newRecommendation for an AT Command set for use in ISDN Terminal Adapters, the draft of the revised Supplement toV.250 (ex V.25ter) and liaisons with Study Group 15 on xDSL work. TR-30.2/98-03-004© (same as D.134©) is acopy of the Proposed Draft New Recommendation V.25I, Commands for the Control and Configuration of ISDNTerminal Adapters. Although ISDN Terminal Adapters are not widely used in the United States, they are commonin Europe. Manufacturers in the US however do produce the units and have an interest in this draft Recommendationwhich is planned to be Determined at the September 1998 SG16 meeting.

The latest draft of the Revision of the Supplement to V.250 (TR-30.2/98-03-005©, same as TD-29(WP1/16)©) wasdistributed for review. This document is intended for approval at the September 1998 Study Group 16 meeting. Thesupplement provides a catalog of all known AT commands. TR-30.2 members were asked to do an in-depth reviewof the draft to assure its correctness.

Attached to the Q7/16 Rapporteurs Report is a liaison sent to Study Group 15 from Q6/16 and Q7/16 (TD-35(WP1/16)) offering their assistance in the xDSL work taking place in Study Group 15. In particular, the offeris to work on DTE/DCE interfaces and protocols for xDSL equipment. A response liaison (TR-30.2/98-03-006 ,same as TD-34(WP1/15)) from SG15 indicates that the xDSL group has not reached a decision on interfacerequirements. However they have invited the Q6/16 and Q7/16 Rapporteurs (R.R. Damm, Germany, and F. Lucas,3Com, respectively) to attended the Q4/15 Rapporteurs meeting in Chicago the week of April 6, 1998. TR-30.2 hasalso started to look at this matter (see PN-4149, below).

PN-3615 TSB-89, A PPLICATION GUIDELINES FOR TIA/EIA-485-A

The draft of TSB-89, Application Guidelines for TIA/EIA-485-A (electrical characteristics of generators and receiversfor use in balanced digital multipoint systems) had been placed on the TR-30.2 ftp site for committee review. Nocomments had been received; TR-30.2 approved the draft for committee letter ballot. This bulletin will assist usersof TIA/EIA-485-A and is intended to answer common questions.

PN-3760, TSB-54A, DTE/DCE I NTERFACE SELECTION GUIDE

TR-30.2/98-03-007 is the final draft of PN-3760, DTE/DCE Interface Selection Guide (TSB-54-A). ThisSelection Guide provides a means for users of the TIA DTE/DCE Interface standards to see in one document thevarious functional and electrical characteristic standards available and to see their relationship to one another. TR-30.2 agreed that the draft was ready for committee ballot. Comments on the ballots should be ready for considerationat the April TR-30.2 meeting.

PN-4149, S TUDY OF DTE/DCE INTERFACES FOR XDSL MODEMS

The chairman once again reviewed the discussions which took place at the ITU-T SG16 meeting regarding DTE/DCEInterfaces for xDSL modems. TR-30.2/98-03-010 (R. Moser and B. Bennett, AMP) provides an overview of themethodology for using simulation and modeling techniques as a tool for the development of new connector standards.The techniques described could be most helpful to TR-30.2 in future interfaces, especially at high data rates. TR-



30.2 discussed moving forward on the standardization of the Universal Serial Bus (USB), or those portions of thatspecification which would fall under the scope of TR-30.2. The USB specification was written and is maintained bya group of companies rather than a standards organization or formal forum. TR-30.2 agreed that the TR-30.2chairman should contact the USB group to determine their interest in the standardization of the interface. In itspresent form, the USB cannot be used as a requirement in a standard written by an accredited standards organizationsince the USB specification was not written by an accredited group. This work will continue at the April meeting,and is expected to be the major item of discussion.

EXTENDED DTE/DCE PROTOCOL FUNCTIONS

Two contributions from VocalTec Communications (K. Krechmer) address V.8bis revisions. TR-30.2/98-03-009 , Reasons to Implement Revised V.8bis in V.90, was provided as background information regarding recentproposed changes to V.8bis. TR-30.2/98-03-008 , Common North American V.8bis NSF Data Format for ISPAccess, proposes that TR-30.2 specify a V.8bis NSF frame format in TIA-602 in support of the V.8bis changes. Aconcern was voiced that this work should be in the form of additional commands for the V.25x Recommendationseries rather than in TIA-602. Since there was no representative from VocalTec Communications in attendance,further discussion was put off until a representative was present.

FUTURE ELECTRICAL CHARACTERISTIC WORK

J. Goldie (National Semiconductor, chair, TR-30.2.1 ad hoc group on electrical characteristics), reported that there isa user need for a new electrical characteristic for a multipoint LDDS (limited distance data service) interface whichwould be similar to TIA/EIA-485. He indicated that he would bring forth a project proposal if the ad hoc groupdesires to pursue this new item.

Fred Lucas, 3Com

TR-30.3 DATA COMMUNICATIONS EQUIPMENT EVALUATION AND NETWORK INTERFACES

No patents essneital to the work in TR-30.3 were identified.

LIAISON REPORTS

TR-30.3/98-03-05 (S. Roleson, Hewlett-Packard) concerns the TR-41.9 review of TIA-496-A, Interface betweenDCE and the PSTN, and new commercial “voice over IP” service offered by Quest Communications and calledQ.talk. S. Roleson noted that this service does not support G3 fax currently but that Quest indicated they mayprovide such a service in the future.

TR-30.3/98-03-06 (R. Breden, TIA) notes the publication of the Part 68 Harmonization Comments. Thecontribution was distributed for information. See the TR-41.9 report in this issue of CSR-T for details.

TR-30.3/98-03-007-A , TR-30.3/98-03-007-B , and TR-30.3/98-03-007-D contain FCC Billboards forDecember 1997, January 1998 and February 1998. They were distributed for information.

TR-30.3/98-03-07-C (W. von Alven, FCC) asks two questions about PCM modems: telco support for highertransmit levels and how V.90 modems train. The following comments were made concerning these questions:• Bellcore did some preliminary testing with the host PCM modem operating at a -6 dBm signal level and saw no

degradation of the line as a result of crosstalk. T1A1.1 will do more testing.• It is not the intent of V.90 to raise the level on the local loop. It is the intent to raise the level of the encoded

content to compensate for digital Packet Assembler Disassemblers (PADs).• The telcos have requested that a study be made to determine if V.90 modems can effectively determine whether

digital PADs are present in the network. They want to ensure that the level on the network doesn’t go too high.

R. Perez (Bellcore) agreed to write a contribution outlining his findings. TR-30.3 decided to send a letter to B. vonAlven (FCC) and A. Wride (Communications Certifications Laboratory) that answers B. von Alven’s (FCC) ques-tions and includes information from the Bellcore tests.



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

TR-30.3/98-03-013©, Telephone Network Transmission Model for Evaluating Modem Performance, Draft 10 (B.Anders, 3Com), was reviewed section by section during the ad-hoc meeting. The new draft of PN-3459 will beposted for a one week comment period. TR-30.3 agreed to send the final draft to TIA for Industry Ballot.

PN-3509, REVISION OF TSB-38 (TEST PROCEDURES FOR EVALUATING MODEM PERFORMANCE)

B. Anders (3Com) agreed to be editor for PN-3509. He will prepare a revised draft that has been modified to matchthe new network model.

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

There was no activity on PN-3251 and PN-3507.

PN-3856, TEST PROCEDURES FOR EVALUATING PCM-MODEM PERFORMANCE

TR-30.3/98-03-008 (W. Henderson, Henderson Communications Laboratories) is draft 1 of PN-3856, TestProcedure for Evaluating Analog and Digital ITU V.90-Compliant Modem Performance. Comments were made thatsome new file types need to be considered which would be more representative of Internet activities. J. Douglass(Oak Technology) will contact J. Decuir (Microsoft) requesting information on characteristics of TCP/IP filetransfers and statistical information on connect rates for PCM modems.

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

The following documents were discussed:• TR-30.3/97-12-088AH , Bellcore Loop Survey (J. Moran, Motorola)• TR-30.3/97-12-089AH , Test Loop Distribution for PCM Network Model using only Business Loops (R.

Perez, Bellcore)• TR-30.3/97-12-090AH , Business Loops from 0 ft to 50,000 ft for 1984 Loop Survey (Histogram) estimate

(R. Perez, Bellcore)• TR-30.3/97-12-090AH R1 , Test Loop Set for PCM Network Model (R. Perez, Bellcore)• TR-30.3/97-12-091AH , figures for end-to-end office simulation in test equipment configuration (ad hoc

group)• TR-30.3/97-12-092AH , PN-3857 Introduction (ad hoc group)• TR-30.3/97-12-093AH , PN-3857, International Telephone Network Transmission model for evaluating

PCM modems (same as PCM97-171)• TR-30.3/97-12-094AH© (same as PCM97-170), PN-3857 Draft 3, Telephone Network Transmission Model for

Evaluating PCM Modem (J. Douglass, Oak Technology, prepared by TR-30.3 as a submission to Q23/16)• TR-30.3/97-12-095AH , Digital Switch - Echo Return Loss (H. Hagen, Lucent)• TR-30.3/98-03-003 , 60 Hz and Harmonic Noise Impairments for PCM Network Model (R. Perez, Bellcore)• TR-30.3/98-03-009 , Modification to the Network Configuration Percentiles (R. Perez, Bellcore)• TR-30.3/98-03-010©, Proposed Draft V.56xxx, International Network Transmission Model for Evaluating V.90

Modem Performance (J-P. Houdard, TI)• TR-30.3/98-03-011 , Update of Impairment combinations Scores associated to Integrated and Universal

Network Access Arrangements complying with Bellcore information (J-P. Houdard, TI)• TR-30.3/98-03-012 , Codec Transmission Characteristics (J-P. Houdard, TI)

TR-30.3/98-03-014©, PN-3857 Draft 4, North American Telephone Network Transmission Model for EvaluatingPCM Modem Performance (G. Hillman, Motorola) was reviewed section by section. Placement and quantities ofRobbed Bit Signaling (RBS) sections need to be defined.

A Q23/16 Rapporteur meeting (prior to the SG16 meeting in February 1998) noted the following issues. The firsttwo were resolved in Draft 4 of PN-3857:• Are the loops and percentages from V.56 bis? The percentages should be modified since only one loop is used.• Codec filter characteristics should be split into transmit and receive sections.• The beginning and ending connect speeds should be recorded.

The number of tests need to be significantly reduced. The following suggestions were made to reduce the number oftest channels:



• Initially TR-30.3 should look at all test channels based on an accurate model of the network then reduce thenumber of channels by providing alternate truncated test channels.

• Drop loop 6 (loaded loop) for PCM modems.• Drop Level A impairments for PCM capable channels.• Drop Level D impairments for Fall-Back Mode channels.

TR-30.3 decided to modify the impairment combinations and figures based on the recommendations in TR-30.3/98-03-004 , Modification to the Cases in Annex D: Basis for Network Models and IC Tables (R. Perez,Bellcore). The model will now be divided into four groups:1. Integrated Network Access Arrangement using D4 (INAA/D4)2. Integrated Network Access Arrangement using ISDN (INAA/ISDN)3. Universal Network Access Arrangement using D4 (INAA/D4)4. Universal Network Access Arrangement using D4 (INAA/ISDN)

H. Hagen (Lucent) will prepare Echo Return Loss (ERL) graphs and text to be placed in Appendix C (Basis forNetwork Models). TR-30.3 decided to add an impairment for 60 Hz noise and its harmonics. There are no zero lossconnections in a PCM application. Some digital switches have analog PADs. L. Chenier (Consultronics) willprovide Digital PADs tables showing binary values for input and output. H. Hagen (Lucent) will provide PAD in-formation for the Enhanced Signaling Systems (ESS) switch.

T. Martins (Cisco) will provide information on PCM connect rates. W. Henderson (Henderson Labs) and R. Perez(Bellcore) will run tests using the new Sage transmission impairment measurement set.

The following documents were created during the ad hoc meeting:

• TR-30.3/98-03-015AH (L. Chenier, Consultronics) and TR-30.3/98-03-015AH R1 (L. Chenier,Consultronics), End to End Office Simulation for Integrated and Universal Network in Test EquipmentConfiguration, includes updates of the integrated and universal network models.

• TR-30.3/98-03-016AH (R. Perez, Bellcore) contains a modification to the Cases in Annex D. Basis forNetwork Models and IC Tables Edition 2.

• TR-30.3/98-03-017AH and TR-30.3/98-03-017AH R1 (both from J-P. Houdard, TI) contain tablesproviding impairment combinations for network configurations: INAA/D4, INAA/ISDN, UNAA/D4 andUNAA/ISDN.

Jack Douglas, Oak Technology



TR-30 MEETING ROSTER , MARCH 9–12, 1998, DALLAS, TX

Dick Brandt, Motorola (dB Consulting) Chair TR-30Les Brown, Motorola Chair TR-30.1Fred Lucas, 3Com Chair TR-30.2Jack Douglass, Oak Technology Chair TR-30.3Host: Texas Instruments

3Com Bryan Anders3Com Fred Lucas3Com Wayne ParkAMP Ben BennettAMP Russell MoserAnalog Devices Rao NuthalapatiBay Networks Slobodan JovanovicBellcore Ricardo PerezCirrus Logic Vedavali KrishnanCirrus Logic Troy RussoCisco Systems Tom MartinCompaq Computers Edward NewmanCompaq Computers Jess OswaltConsultronics Louis ChenierDavicom Yaopei ChangDiamond Multimedia Dan MooreDigicom Zhi-yuan GuanESS Technologies Jordan CookmanESS Technologies Ping DongForteMedia Ching-Yih TsengHayes Bruce AdamsHenderson Testing Labs Warren HendersonIBM Ali SadriIBM Gotfried UngerbockLucent Bahman BarazeshLucent Horace HagenLucent John MagillMotorola Dick BrandtMotorola Les BrownMotorola Dave ForneyMotorola Garth HillmanMultitech Systems R.S. GopalanMultitech Systems Timothy GunnNational Semiconductor John GoldiePCTel Gary AnwylRockwell Stan BaconRockwell Keith ChuRockwell Glen GriffithRockwell Craig MellonSiemens Microelec. Neal KingTAS Mike PellegriniTexas Instruments Murtaza AliTexas Instruments Kevin GingerichTexas Instruments Jean-Pierre HoudardTexas Instruments Jose SolteroTexas Instruments Nirmal WarkeTri Signal Comm. Jean Belleau



Q15/16 UPDATE ON COMPATIBILITY BETWEENMPEG-4 VIDEO AND ITU-T REC. H.263

The ISO/IEC MPEG-4 committee draft achieved compatibility with ITU-T H.263: an important step in video codingstandardization.

March 23, 1998. MPEG created a “final committee draft” of its draft MPEG-4 video coding standard last week(March 16-20) at its 43rd meeting in Tokyo. Compatibility with the prior video coding standard ITU-TRecommendation H.263 was adopted into that draft. The compatibility was achieved by an alignment of completesyntax support for the primary “Baseline” interoperability operational mode of Recommendation H.263. This willgive all MPEG-4 video decoders the ability to decode bitstreams produced by Recommendation H.263 Baselineencoders. (Since MPEG-4 also has many additional features that cannot be represented using H.263 Baseline syntax,the reverse is not true in general -- H.263 Baseline decoders will not be able to decode all MPEG-4 video bitstreams.)

This is an important step in video coding standardization development, ensuring that the new implementations of thefuture MPEG-4 video standard (FCD for ISO/IEC 14496-2) can have full compatibility with the millions of de-ployed implementations of Recommendation H.263 worldwide. This action sends a clear message that interoper-ability of these standardized systems is necessary world-wide.

ITU-T Recommendation H.263 is a video coding standard developed by the ITU-T (formerly CCITT). It wasoriginally approved in November 1995 and is maintained by the ITU-T Advanced Video Coding Experts Group,formally chartered as Question 15 of the ITU-T Study Group 16 for Multimedia Standardization. Newly approved ina second-generation specification completed in September 1997 and approved in January 1998, RecommendationH.263 is the current “flagship” ITU standard for low bit rate video communication coding. The “Baseline” modewhich forms the heart of H.263 operation was the fundamental requirement for all implementations of the originalH.263 specification and is now also fully supported in both the second version of H.263 and in the new draft ofMPEG-4 video. The H.263 Baseline mode provides an interoperable common core for video coding systems.

MPEG-4 video, to be formalized in ISO/IEC 14496-2, is a project of the Moving Picture Experts Group (MPEG)formally chartered as Working Group 11 of ISO/IEC JTC1 SC29. The MPEG-4 video coding standardization projectis developing its specification to provide a broadly-applicable and flexible set of video coding tools and definedconfiguration profiles for a wide range of multimedia applications with new functionalities such as object-segmentedcoding and the handling of hybrids of natural and synthetic content. The first of two planned versions of MPEG-4video is now in a “final committee draft” stage and is expected to receive final approval in December 1998.

Gary Sullivan, PictureTel Corporation

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]



ACRONYM DEFINITIONS

ACIL Assn of Ind. Scientific, Engring & Testing FirmsADSL Asymmetric Digital Subscriber Loop (Line)ANF Additional Network FeatureANT Access Network Transport (Q1/15)APEC Asia Pacific Economic Cooperation ForumAPI Application Programming InterfaceASN Abstract Symbol NotationATBCB Architectural and Transportation Barriers Compliance BoardATM Asynchronous Transfer ModeATU-C ADSL Transceiver Unit - Central Office EndATU-R ADSL Transceiver Unit - Remote Terminal EndBFT Binary File TransferBRI Basic Rate InterfaceCAB Conformity Assessment BodyCAP Carrier-less Amplitude Modulation PhaseCCB Common Carrier BureauCCT Consultative Committee - TelecommunicationsCEBus Consumer Electronics BusCO Central OfficeCPE Customer Premise EquipmentD/A Digital to AnalogDAVIC Digital Audio-Visual Councildc Direct CurrentDCE Data Circuit Terminating EquipmentDCME Digital Circuit Multiplication EquipmentDCS Digital Command Signal (T.30)DECT Digital European Cordless TelephoneDGN Director General de NormasDIS Digital Identification SignalDMT Discrete Multi-tone CarrierDPCM Digital PCMDTE Data Terminal EquipmentECMA European Communications Mfrs AssociationEDC Electronic Document CoordinatorEFTA European Free Trade AreaEMC ElectroMagnetic CompatibilityEMI Electromagnetic InterferenceEOC Embedded Operations ChannelETS European Telecommunications Standard (ETSI)ETSI European Telecommunications Standards Insti.EU European UnionEUT Equipment Under TestFCC Federal Communications Commission (U.S.)FCD Fast Track Committee Draft (ISO)FEXT Far End Cross TalkFTP File Transfer ProtocolGII Global Information InfrastructureHAC Hearing Aid CompatibleHFR Hybrid Fibre RadioIC Interexchange CarrierIEC International Electrotechnical CommitteeIEEE Institute of Electrical and Electronic EngineersIETF Internet Engineering Task ForceIMTC Int’l Multimedia Teleconferencing ConsortiumIP Internet ProtocolIPP Internet Printing ProtocolIPR Intellectual Property RightsISDN Integrated Services Digital NetworkISO International Organization for StandardizationISOC Internet SocietyISP International Standardized ProfileITI Information Technology Industry CouncilJPEG Joint Photographics Expert GroupJRG Joint Rapporteurs GroupLAN Local Area NetworkLE Local ExchangeMFP Multi-Function PeripheralMIME Multipurpose Internet Mail ExtensionMLTS Multi-Line Telecommunications Systems



MOS Mean Opinion ScoreMPEG Motion Picture Experts GroupMRA Mutual Recognition AgreementsMRC Mixed Raster ContentNA North AmericaNAFTA North American Free Trade AgreementNEXT Near End Cross TalkNMX Normas MexicanasNOM Mexican National StandardsNPRM Notice of Proposed Rule Making (FCC)NSF Non-Standard FacilitiesNYCE Certification Body accredited by SECOFI (Mex.)OSHA Occupational Safety and Health Admin. (U.S.)PAD Packet Assembler DisassemblerPAR Peak to Average RatioPBX Private Branch ExchangePC Personal ComputerPCI Personal Computer InterfacePCS Personal Communication ServicesPDH Packet Digital HierarchyPISN Private Integrated Services NetworkPMD Physical Media Dependent LayerPNNI Private Network to Network InterfacePOTS Plain Old Telephone ServicePRI Primary Rate Interface (ISDN)PSD Power Spectral DensityQAM Quadrature Amplitude ModulationQoS Quality of ServiceQSIG Req’ts specified by the ITU Q series RecsQSIG ISO standard for signalling between two PBXsREN Ringer EquivalenceRF Radio FrequencyRFC Request for CommentsRG Residential GatewayRT Round TripRTP Real Time Transport ProtocolSAR Segmentation And Re-assemblySCN Switched Communications NetworkSDH Synchronous Digital HierarchySECOFI Mexican Ministry of Commerce & Ind. Dev.SMG Special Mobile GroupSPS Signaling Protocol And System TC (ETSI)SS7 Signaling System 7STF Specialist Task ForceSTM Synchronous Transmission ModeSTQ Speech Transmission QualityTABD Trans-Atlantic Business DialogTBD To be DeterminedTC Technical CommitteeTC Transmission Convergence LayerTCM Time Compression MultiplexTCP Transmission Control ProtocolTIES Telecom Information Exchange ServicesTIFF Tagged Image File FormatTIFF-F Tagged Image File Format-FaxTIPHON Telecommunications and Internet Protocol Harmonization Over Networks (ETSI Project)TR Technical ReportTS Technical SpecificationTSAG Telecom. Standardization Advisory GroupTSB Telecom. Standardization Board (ITU)TSB Telecommunications Systems Bulletin (TIA)UDP User Datagram ProtocolUSB Universal Serial BusVoIP Voice Over Internet ProtocolVON Voice on Network CoalitionWAN Wide Area NetworkxDSL all the different Digital Subscriber Lines



1998 STANDARDS COMMITTEE MEETING SCHEDULESAS OF MARCH 30, 1998

Subject to Change without Notice

Committee Date(s) Location

Q4/15 Rapp. Apr 6 - 9 Chicago, IL

ETSI DTA Apr 7 - 8 Sophia Antipolis,France

TR-41.8 Interim TaskGroups

Apr 7 - 9 Rosemont, IL

TR-41.8.1 FO TGInterim meeting

Apr 20 - 21 Charlotte, NC

ETSI TM6 Apr 20 - 24 Antwerp, Belgium

Q3/16 Rapp. Apr 20-22 Lexington, KY

Q11/16 (Mobile) andQ15/16 Rapp.

Apr 21 - 24 Tampere, Finland

ETSI TIPHON Apr 27 - 30 Munich, Germany

TR-30 Apr 27 - 29 Red Bank, NJ

Q23/16 Rapp. Apr30-May1 Red Bank, NJ

Q4/16 V.8bis Rapp May 4 - 5 Red Bank, NJ

TR-29 May 4 - 7 Atlanta, GA

TR-41 May 11 - 15 Washington DC

Q4/15 Rapporteurs May 11-14 Nice, France

TR-41.8.1 May 13 - 14 Norfolk, Virginia

Q4/16, Q10/16,Q23/16 Rapp.

Summer Europe

Q1/16 Rapp. June France

T1E1 Jun 1 - 5 Huntsville, AL

Q11/16 Jun 9 - 12 Nice, France

Q9/16, Q12/16,Q13/16, Q14/16,Q18/16 Rapp.

Jun 9 - 12 Nice, France

SG8 Jun 9 - 18 Geneva

ETSI TIPHON Jun 16 - 19 Helsinki, FinlandCommittee Date(s) Location

TR-30 Jun 15 - 19 Raleigh, NC

Q3/16 Rapp. Jun 22 - 26 Colorado, USA

ETSI ATA Jun 22 - 26 Sophia Antipolis,France

ETSI TM6 Jun 22 - 26 Lulea, Sweden

ETSI MTA Jun 29 - Jul 3 Munich, Germany

Q1/15 Rapp. Jun 29-Jul 1 Tel Aviv, Israel

Q4/15 , with Q6/16& Q7/16 Rapp.

Jun 29-Jul 3 Hawaii, USA

Q11/16 and Q15/16Rapp.

Jul 21 - 24 ---

Q4/15 with Q6/16and Q7/16 Rapp.

Aug 3 - 7 Antwerp, Belgium

TR-30 Aug 10 - 14 Quebec City, Que

TR-41 Aug 17 - 21 Calgary, Alberta

T1E1 Aug31-Sep 4 California

ETSI TIPHON Aug31-Sep 4 Portland, OR

SG16 Sep 14 - 25 Geneva

ETSI TM6 Sep 21 - 25 Vienna, Austria

SG 15 Oct 12 - 23 Geneva

ETSI TIPHON Oct 26 - 30 ---

TR-30 Nov 9 - 13 San Antonio, TX

TR-41 Nov 16 - 20 Palm Springs, CA

ETSI TM6 Nov 23 - 28 Sophia Antipolis,France

T1E1 Nov30-Dec 4 Texas

ETSI TIPHON Nov30-Dec 4 ---

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 published8 - 9 times per year, within days after the latest, related standards meetings. Editor: Elaine J. Baskin, Ph.D.Technical Editor: Ken Krechmer. Copyright © 1998, Communications Standards Review. All rights reserved.Copying of individual articles for distribution within a subscriber organization is permitted. Subscriptions: $695.00per year worldwide, $795.00 in electronic format. Corporate Intranet subscriptions (site license for multiple copies)are available. 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]. WWW:http://www.csrstds.com. 19903