Mar/Apr 1999 - Linda Hall Library

Transcrição

COMMUNICATIONS STANDARDS
REVIEW
Volume 10, Number 3
March - April 1999
In This Issue
The following reports of recent standards meetings represent the view of the reporter
and are not official, authorized minutes of the meetings.
Q3/16 Rapporteurs Meeting, January 19-21, 1999, Monterey, CA ...............................................................2
TR-29, Facsimile Systems and Equipment, February 8-10, 1999, Dana Point, CA .................................. 4
TR-29.1, Facsimile and File Transfer Protocols..................................................................................... 5
TR-29.2, Facsimile Digital Interfaces ......................................................................................................7
TR-30, Data Transmission Systems and Equipment, February 8-10, 1999, Dana Point, CA ...................11
TR-30.1, Modems .......................................................................................................................................11
TR-30.2, Data Transmission .....................................................................................................................11
TR-30.3, Data Communications Equipment Evaluation and Network Interfaces ............................. 13
Q11-14/16 Rapporteurs Meeting, February 15-19, 1999, Monterey, CA ..................................................... 19
Q11/16, Circuit-Switched Network (CSN) Multimedia Terminals and Systems ................................19
Q11/16 Mobile .............................................................................................................................................19
Q11 - 15/16 Joint Meeting ..........................................................................................................................21
Q12/16, B-ISDN Multimedia Systems and Terminals ..........................................................................25
Q13/16 Multimedia over Packet Networks ............................................................................................. 26
Q14/16, Common Protocols, MCUs and Protocols for Interworking with H.300-series Terminals .. 33
TR-41, User Premises Telecom Equipment, February 15-19, 1999, Sarasota, FL .....................................41
TR-41.1, Multi-Line Telecommunication Systems .................................................................................41
TR-41.1.2, VoIP Transmission................................................................................................................. 45
TR-41.2, Conformity Assessment .............................................................................................................46
TR-41.3, Analog and Digital Wireline Telephones, November 18-19, 1998 ......................................... 48
TR-41.5, Multimedia Building Distribution Systems ............................................................................51
TR-41.6, Wireless User Premises .............................................................................................................52
TR-41.6.1, PWT (Personal .........................................................................................................................52
TR-41.6.3, PACS-WUPE .......................................................................................................................... 54
TR-41.7, Safety And Environmental Considerations .............................................................................55
TR-41.7.1, Harmonization of International Safety Standards ...............................................................56
TR-41.7.2, Bonding and Grounding ..........................................................................................................57
TR-41.9, Terminal Attachment Programs ...............................................................................................59
TR-41.10, Private Integrated Services Network (PISN) ....................................................................... 63
TR-41.11, FCC Administrative Committee ............................................................................................63
TR-42, User Premises Telecommunications Infrastructure, February 15-19, 1999, Sarasota, FL ...........66
TR -42.1, Commercial Building Cabling.................................................................................................. 66
TR -42.2, Residential & Light Commercial Premises Distribution ...................................................... 66
TR -42.3, Building Pathways and Spaces for Telecommunications.......................................................68
TR -42.4, Customer-Owned Outside Plant.............................................................................................. 68
TR -42.5, Definitions...................................................................................................................................69
Q21/15, Transp. Network Eqpt for Interconnect’g GSTN and IP Networks, Feb. 17-18, 1999, SF, CA.. 70
ETSI TM6, Access Transmission Sys. on Metallic Cables, February 22-26, 1999, Villach, Austria ........75
SDSL .......................................................................................................................................................... 76
VDSL.......................................................................................................................................................... 81
ADSL Revision of TS 101 388 v1.1.1 ....................................................................................................... 83
Broadband-ISDN Access .......................................................................................................................... 84
Acronym Definitions .........................................................................................................................................86
1999 Standards Committee Meeting Schedules, as of March 8, 1999 ......................................................... 90
March-April 1999
Vol. 10.3 Copyright © CSR 1999
1
COMMUNICATIONS STANDARDS REVIEW
REPORT OF Q3/16 RAPPORTEURS MEETING, JANUARY 19 - 21, 1999,
MONTEREY, CA
Q3/16 rapporteur meeting documents are available at: ftp.imtc-files.org/imtcsite/Data_Conferencing_AG/T120-top/Monterey
STATUS OF DETERMINED RECOMMENDATIONS
T.123 rev for Security
T123-Security-mechanism (M. Morris, Microsoft, T102C-Mont-unn3) proposes additions to
Annex B of T.123 (revised) to support the security framework of the IETF Generic Security
Application Programming Interface (GSS-API). Changes as detailed in sections 3.2 to 3.4 of the
contribution will be made to T.123 rev. The background information contained in the document is
to be re-edited for inclusion into the T120 Implementers Guide.
T.123rev was Determined at the most recent SG16 meeting. If the changes agreed from this
contribution are considered by SG16 as too extensive to be editorial changes, then Q3/16 agreed
to re-Determine T.123rev at the next SG16 meeting with these changes.
T.136 and H.282
No contributions were received on T.136 (T.RDC) or on H.282 (V.RDC). No changes are expected
to current draft texts prior to the SG16 meeting in May.
M EETING ROOM M ANAGEMENT REQUIREMENTS
T.mrm-Draft-G-Jan99 (J. Boucher, BT Labs, T120C-Mont-unn1) was reviewed in detail. This
recommendation provides extensions to the Generic Conference Control functionality to support
the specification and management of virtual meeting spaces (meeting rooms) within a conference.
This work is expected to find application in the provision of commercial conference services.
Procedures are defined for arbitrating use of real time media services such as telephony, for
advertising those services to participating nodes, and for managing and controlling those
services once they are activated. These services include the following:
•
•
•
•
•
•
Virtual meeting rooms - creation, entering, leaving, destroying
MRM management roles - conductor, chair, secretary, user defined
MRM framework
Audio management - mixing, channels
Groups
Channels and token
T.MRM also defines a Conference Server that takes responsibility for the running of the MRM
Conference and a service access channel for communication between the clients and server.
T120C-Mont-uun2, T.MRM ad hoc meeting report (P. Murphy, DataBeam), identifies issues
that need to be addressed or clarified in the draft text. Areas include:
•
•
•
•
•
•
•
Roles and Permissions
Virtual Rooms
Groups
Data Applications
Non-MRM Participants
Supported Conference Topologies
DCOM/CORBA/etc. vs. ASN.1
This work is estimated to be about 85 to 90% complete; Q3/16 was satisfied with the progress
thus far. More detailed comments are expected at an audio conference March 11. A new version
of the document will be issued two weeks before the review.
2
March-April 1999
T.120 SECURITY REQUIREMENTS
T120C-Mont-unn4a, Data Security Scenarios (J. Dailey, Microsoft) was reviewed. It contains
six sample scenarios that illustrate corporate user environments and requirements for using data
conferencing security. These scenarios are primarily user scenarios, and not necessarily
deployment scenarios, meaning that complex details of network architecture and hardware
configurations are not addressed. Each scenario was reviewed and comments relative to security
concerns were made. These comments (integrated into the body of the contribution) are in
T120C-Mont-unn4b.
Q3/16 WORK P LAN
In a brainstorming session, the group discussed the future of Q3/16. The end of the study period
is approaching and much of the work is complete or nearing completion. Suggestions included
downsizing to maintenance mode for existing T120 Recommendations, joining another Question
which has related work, waiting for implementation to catch up with state of the standards,
developing a next generation set of data conferencing, and shifting emphasis to IP-friendly
protocols including light GCC (Generic Conference Control) client protocol with companion GCC
server. It was recognized that there are a number of issues outstanding in important areas
where improvements are desirable.
It was pointed out that the T.120 infrastructure was developed before IP became the primary
transport; there are a number of areas where the protocol could be changed and enhanced to
better accommodate IP networks. Issues with MCS include single point of failure and
hierarchical topology. Issues with GCC include complexity. One suggestion is to divide
functionality up into session start-up, conference administration and application support. The
value of standardizing applications such as whiteboard was discussed. The growing use of webbased solutions was also discussed as well as the possibility of dealing with all of these issues as
part of a new initiative to produce a second generation solution. Input is solicited for the future
meetings.
No conclusions were agreed. This topic is expected to be discussed at the Q3/16 meeting at the
SG16 meeting in May.
The following table summarizes the current status of the T.120 Recommendations and Q3/16
work in progress:
Draft Recommendation
Status
SG16 Sept 98
T.120
D-1996
Annex C
D-Feb 98
T.121
D-1996
T.122 Rev
D-Feb 98
T.123 Rev
D-1996
d
T.124 Rev
D-Feb 98
T.125 Rev
D-Feb 98
T.126
D -Mar 97
T.127
D- Mar 95
T.128
D-Feb 98
T.134 (T.chat)
D-Feb 98
T.135 (T.RES)
D-Feb 98
T.136 (T.RDC)
d
H.282 (V.RDC)
d
T120 Security
Meeting Room Management
(d= determine, r= re-determine, D= decide)
Note 1: Possible alternate schedule, see above.
SG16 May 99
Implementers Guide
D (note 1)
D
D
Continuing investigation
d
Bruce DeGrasse, BJ Communications
March-April 1999
3
Q3/16 RAPPORTEUR MEETING ROSTER, JANUARY 19 - 21, 1999, MONTEREY, CA
Bruce DeGrasse, BJ Communications
Host: IMTC
BJ Communications
DataBeam
BT Labs
Octave Communications Inc.
Microsoft
Infocus
Q3/16 Rapporteur
Bruce DeGrasse
Patrick A. Murphy
John Boucher
Chuck Grandgent
Jane Dailey
Rene Poston
REPORT OF TR-29, FACSIMILE SYSTEMS AND EQUIPMENT
FEBRUARY 8 - 10, 1999, DANA POINT, CA
The current TR-29 chair, S. Urban (Delta Information Systems) will be resigning. D. Duehren
(Brooktrout) announced that he will be stepping down as chair as of TR-29.1 as of the next
meeting (May 1999). S. Urban proposed that the committee be restructured so that the TR-29
committee and its subcommittees TR-29.1 and TR-29.2 be consolidated. The committee agreed to
make this re-structuring effective as of the next meeting. The net result will be to consolidate all
current projects into the TR-29 committee.
TR-29.3, Data Protocols for Multimedia Conferencing (B. DeGrasse, BJ Communications, Chair),
met in January, 1999 (see Q3/16 report in this issue of CSR). It is much smaller and is focusing
on data conferencing. Since much of the T.120 work has been embedded within popular operating
systems such as Windows, there appears to be less private company interest in further
enhancements.
TR-29.4, Secure Facsimile (B. Robinson, L-3 Communications, Chair), did not meet.
INTELLECTUAL PROPERTY
Per current TIA policy, a request was made to determine intellectual property rights (IPR)
associated with TR-29 committee work. The status of IPR was noted as follows:
Mixed Raster Content: Xerox may have IPR related to this work and has submitted an updated
IPR statement (see TR-29/96-11-55).
JBIG2: Xerox may have IPR related to this work with respect to the rendering of JBIG-2 images.
LIAISON R EPORTS
ANSI/X3L3: The January meeting focused on the JPEG-2000 algorithm. There are currently
two candidate versions for reference codec and a need for consolidation. There was more activity
on architecture and file format. A version of the FlashPix format
(http://www.kodak.com/US/en/digital/flashPix/flashPixFAQ.shtml) has been submitted as a
candidate. The current thinking is that there are likely to be several possible file interchange
formats. MRC (Mixed Raster Content) was proposed as the overall architecture for JPEG 2000.
AT&T has promoted another architecture approach, known as “Déjà vu,” for consideration for a
fast track approval process. A number of companies object to this approach, since it is not
consistent with the technical work that has undergone review within X3L3.
JBIG-2 is in a CD ballot phase. The US has agreed to support the current draft within WG1.
The next meeting of WG1 is in March in Seoul.
4
March-April 1999
ISO: The version of the German proposal on an office equipment standard has been considerably
watered down from previous versions. Further action is pending.
ISO/IEC JTC1 SC6 WG1: JURA (JPEG Utilities Registration Authority) has resolved the issue
on the Application marker for facsimile in assignments. The duplicate assignment of the APP1
marker has now been resolved and it will be used exclusively for color facsimile as originally
intended. However, the assignment of the APP markers for T.43 and T.44 is pending. WG1
convener D. Lee (HP) is requesting a resolution of these assignments on an expedited basis.
PROJECTS
There was no new business regarding Color Fax at this meeting. There will be a decision
meeting at SG8 on the Mixed Raster Content documents (T.44, along with related parts of T.4
and T.30). The JBIG-2 specification is likely to be determined at the SG8 meeting as well.
The updated version of High Frequency Radio Facsimile (SP-3394) has been published as
TIA/EIA-668. It is available through Global Engineering Documents.
There is no new business to report regarding test charts and test images. D. Bodson has retired.
REVIEW OF PROPOSED SG8 CONTRIBUTIONS
The TR-29.1 potential US contributions were re-numbered as TR-29 documents for review in
advance of the SG8 meeting. The TR-29.1 and TR-29 numbers were assigned in the same
sequence.
TR-29 affirmed the support for the five documents which had been supported in TR-29.1 as
follows (see the TR-29.1 report, below, for further descriptions of each):
• TR-29/99-02-04 (same as TR-29.1/99-02-04R1), Proposed T.30 Revision to Phase B BFT
Negotiations for MIME Media Types
• TR-29/99-02-05 (same as TR-29.1/99-02-05R2), Application for Private Use
• TR-29/99-02-06 (same as TR-29.1/99-02-06R2), Additional edits accommodating introduction
of higher resolutions
• TR-29/99-02-07 (same as TR-29.1/99-02-07R2), Proposed Draft Recommendation
T.PrivateUse
• TR-29/99-02-09 (same as TR-29.1/99-02-09R1), Identification of high resolution for color
TR-29 also confirmed the authorization of further work via correspondence which may result in
US contributions to Study Group D. These documents are:
• TR-29/99-02-03 (same as TR-29.1/99-02-03R2), Additional material enhancing the Draft
Amendment to Recommendation T.38 to Support The Use of V.34 Modulation in COM-8-70-E
• TR-29/99-02-10 (same as TR-29.1/99-02-10), Proposed Revisions to Annex H
TR-29.1, FACSIMILE AND FILE TRANSFER PROTOCOLS
INTELLECTUAL PROPERTY
Per current TIA policy, a request was made to determine intellectual property rights (IPR)
associated with TR-29.1 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 is aware of potential IPR that may apply for real time fax over
the Internet. There are patents from Biscom, Matsushita, and Open Port on some aspects of
Internet fax (see http://www. patents.ibm.com for details on US patents).
Fax Security: There is IPR on the security page from France Telecom and on public key
management from RSA.
March-April 1999
5
LIAISON R EPORTS
US Study Group D: The next meeting is March 9, 1999.
TR-30 and SG16: Intellectual property rights issues on V.90 and V.91 are still pending. V.91 is
proposed for Decision at SG16 in May, 1999.
SG 8 November 1998 (see also CSR Vol. 10.1 report)
Q1/8: Agreement was reached on inclusion of non-square resolutions in the T.30 amendment.
The support for Cellular bits and V.21 half duplex (Annex K) was deleted from the proposed white
contribution. T.66 (Facsimile code points for use in V.8/V.8bis) was Determined. H. Silbiger
(Lucent), as editor, submitted a contribution on an extension to T.35 to permit support for
additional IDs. There is also related text in the amendment to T.30.
Q3/8: Work was done on the amendment to T.434 (BFT) and decisions were reached on changes
to the draft text to add support for MIME media types. A white contribution has been submitted
by the editor.
Q4/8: There was ongoing discussion on the pending amendment to T.38 (Procedures for real time
G3 facsimile communications between terminals using IP networks to be added to Annex B).
There still are some concerns from Japan about issues such as firewalls and remote access.
There was agreement on the latest text to the Annex B of T.38. There was agreement reached on
Amendment 1 to T.37 for the establishment of the full mode using reference to IETF RFCs. The
procedures for full mode are defined by reference to an IETF draft eifax
(http://www.imc.org/draft-ietf-fax-eifax). The resulting draft text has been Determined.
IETF: J. Rafferty reported on the status of the three RFCs which are needed for references by
T.37. These documents have passed the IETF Last Call and will be approved and published
shortly. There is a pending open reference to the “syntax” document that has been developed by
the IETF content negotiations working group. The SIP (Session Initiation Protocol) document
was approved as a proposed standard in the IETF in early February. There are evidently drafts
for a competing approach called MGCP (Media Gateway Control Protocol). The MGCP approach
is under study within ETSI.
The Internet Printing Protocol (IPP) version 1.0 documents have been submitted for publication
as an informational RFC. The main open issues that need to be resolved for version 1.1 are
security and the IPP specific URL. There is interest in proceeding with a Fax application over
IPP; a separate draft charter is being developed for that work in the IETF. (The mailing list for
fax over IPP is: [email protected]. Subscribe to the list by sending a message to
<[email protected]> with a message body containing “subscribe ifx <your-e-mail-address>”.)
IMC Fax Connect: An Internet fax interworking event called Fax Connect I took place in
December in San Jose. Seventeen companies participated. The focus of activity was on
interworking of T.37 and RFC 2305 simple mode features. In addition, there was testing on TIFF
profiles of RFC 2301. A copy of the test results can be found on the IMC web site under reports
(see http://www.imc.org/fc1-final.html).
EMA: J. Rafferty reviewed the status of interworking activities in the EMA. There is interest in
having a public interworking demonstration at the EMA 99 and at other trade shows in the
future. The goal of the demonstrations will be to re-introduce Internet fax as a standards-based
technology. Interested people should contact J. Rafferty to get involved in the planning.
PN-3675, EXTENDED N EGOTIATIONS
It was proposed that the T.PrivateUse document should be re-submitted to ITU-T Q1/8 for
Determination. There is also a need for a companion document on the application of PrivateUse.
T.PrivateUse provides: standard signals for multi-pass private negotiations, modular coding of
data using a private supergroup, multiple private use profiles, and high level typing (four
categories) of private use data. A small ad hoc group worked on the PrivateUse document.
6
March-April 1999
The resulting document is TR-29.1/99-02-07 (D. Duehren, Brooktrout Technology). During
review, TR-29.1 suggested that the overview material should be re-cast to emphasize the positive
new benefits of the protocol and note that it builds on the useful features of Group 3 Non-Standard
Facilities. After further revisions, the updated document, TR-29.1/99-02-07R2, was supported as
a proposed US contribution to be forwarded to Study Group D.
J. Dahmen (Lanier) reviewed TR-29.1/99-02-05 as an example of the use of the extended
negotiation procedures private use feature. The application involves a distributor’s monitoring
for billing (e.g., remote page count reading) and maintenance purposes for a multi-function
facsimile terminal. The final version of the document, TR-29.1/99-02-05R2, was supported by
TR-29.1 to be forwarded as a proposed US contribution to Study Group D.
There is also a need to edit Annex H to T.30 on RSA security to remove redundant material that
can be referenced via Annex X. TR-29.1 authorized extended negotiations editor J. Rafferty to
produce a document with the necessary edits for circulation among committee members. If
agreement is reached on the content of the document, it could be submitted to Study Group D as a
proposed US contribution. TR-29.1 document number TR-29.1/99-02-10 has been reserved for
this document.
PN-3799, INTERNET FAX
Chair D. Duehren noted that the main open item for the T.38 real time Internet fax activity is to
define how V.34 fax devices would be supported within T.38. Some attendees also had questions
for clarification on T.38 as it has been defined to date. TR-29.1 agreed that an ad hoc group
should be formed to review questions for clarification about T.38 and to work on additional
technical content required to define the V.34 fax support within T.38. Previous work from TR-29
had resulted in the development of the white contribution, COM 8-70E, which has a timing
diagram for support of V.34 fax operations within a draft Appendix J to T.38.
TR-29.1/99-02-03 is a result of the ad hoc activities. It specifies some additional considerations
for the practical implementation of V.34 fax via T.38. It was felt that additional work was needed
to put the document into the proper form and address some open technical issues. The resulting
updated and expanded version is contained in TR-29.1/99-02-03R1. The new version includes:
• Additional proposed text for inclusion in Appendix J
• Additions to the list of terms defined in the main body of T.38
• Small revisions to the ASN.1 syntax contained in Annex A.
Some additional edits were noted and an updated version, TR-29.1/99-02-03R2 (H. Silbiger,
Lucent) was produced. TR-29.1 felt some further editing and discussion of issues was needed.
The ad hoc group was authorized to proceed with further editing and study on the timing issues
and on the support for V.8 signals within T.38. The final decision on whether the document as
edited will be submitted to Study Group D as a proposed US contribution will be made by March
5, based on circulation of the updated document among committee members.
There was interest expressed at the November Question 4/8 meeting in having TIFF coding
examples available for the full mode of T.37, for inclusion within an appendix. TR-29.1/99-02-08
(L. McIntyre, Xerox) is a series of TIFF profile coding examples. Examples are included for all of
the profiles within RFC 2301 (TIFF-FX). Several typos were noted during review. An updated
version (TR-29.1/99-02-08R1) contains the requested edits. L. McIntyre plans to add other
samples added for the Profile M (T.44, MRC color coding). TR-29.1 supported the document for
forwarding to Study Group D as a Xerox contribution, subject to inclusion of the additional
examples. L. McIntyre will circulate the updated version of the document prior to Study Group
D.
It was also suggested that it would be useful to have the actual TIFF sample files be made
available by some means, such as via a web site link. L. McIntyre agreed to look into this
possibility.
March-April 1999
7
PN-3364, ENHANCED BINARY FILE TRANSFER
Editor J. Rafferty proposed that there should be an additional amendment to T.30 Annex B to
add support for MIME (Multipurpose Internet Mail Extension) media types in the Phase B BFT
(Binary File Transfer) negotiations. The contribution is being targeted for submission to Q1/8.
Applications where this could be useful include voice mode, image file transfer, electronic
document distribution and remote printing. TR-29.1 agreed that the enhancement would be
useful. J. Rafferty will develop a paper which makes the amendment proposal and notes the
applications. The resulting document is TR-29.1/99-02-04. One small change was requested.
The document as edited (TR-29.1/99-02-04R1) was supported for submission as a proposed US
contribution to Study Group D.
PN-3826, BINARY FILE TRANSFER
There was a brief discussion on the status of PN-3826, Binary File Transfer. TIA-614-A is still
being edited. The intention is to complete the document by including additional material on store
and forward attributes that was approved as Amendment 1 to T.434 last year. At some point, it
may also be useful to work on BFT examples for the T.434 protocol version 3 which will be up for
Decision at the March SG8 meeting. No contributions were available at this meeting.
T.30 FAX PROTOCOL
Further work may be needed for the V.90 and V.91 modes to be used by facsimile. H. Silbiger
(Lucent) plans to consult informally with TR-30 to check on the status of this work. There were
no related contributions at this meeting, but related content was included as an annex to the SG8
November meeting report (see CSR Vol. 10.1).
TR-29.1/99-02-06 (L. McIntyre, Xerox) provides additional edits regarding the introduction of
higher resolutions. These result from a review of the COM 8-76 draft amendment to T.30. Since
the proposed edits include both editorial items and corrections, it was suggested during
discussion that the items of a technical nature should be extracted into a separate contribution.
The committee supported the third proposal in the document, which would add two new bits and
two new notes as part of the support for the recently proposed 600 x 600 and 1200 x 1200
resolutions. An updated version of the original document (TR-29.1/99-02-06R1) was produced
which only includes proposed editorial changes to COM 8-76. Some small additional edits were
made and the contribution, as TR-29.1/99-02-06R2, was supported for forwarding as a potential
US contribution to US SG D.
TR-29.1/99-02-09 contains the proposal for adding two new T.30 DIS bits in order to support the
ability to use resolutions of 600 x 600 and 1200 x 1200 for color documents. Bits already exist to
indicate the support of these resolutions for black and white documents. There were several
suggested edits, primarily to clarify that the proposed additions to the DIS bits and notes only
pertain to support of higher resolutions for color documents. The document as edited (TR29.1/99-02-09R1) was supported for forwarding to Study Group D as a potential US contribution.
TR-29.2, FACSIMILE DIGITAL INTERFACES
No statements on Intellectual Property were made.
LIAISON R EPORTS
Q1/8: J. Rafferty (Human Communications) reported on the ITU-T Question 1/8 meeting from
November. The joint company contribution (ASH-038) on requirements for multi-function
interfaces was reviewed. Unless technical contributions are received at the upcoming March
SG8 meeting, there will be no further effort on this activity.
The Printer Working Group: (or PWG) http://www.pwg.org/chair/index.html) is an
unincorporated alliance among printer manufacturers, print server developers, operating system
8
March-April 1999
providers and print management application developers. Their charter is to make printers and
the applications and operating systems supporting them work together better. The chair is
making informal efforts to check on the status of activities which could have an impact on TR29.2.
MFPA: V. Cancio (Xerox) reported on the MFPA (Multi-Function Peripheral Association). There
is activity on various matters taking place on their mailing list. In a related point, J. Dahmen
(Lanier) noted that the current industry direction is toward digital products, with copying taking
the lead in many product configurations. J. Rafferty (Human Communications) reported on the
proposed meeting of April 20 to address color document communications and related issues. The
meeting is scheduled for San Diego. The goal is to develop a road map for advancing consensus
and standards for color document communication.
ECTF: J. Rafferty reported on the Enterprise Computer Telephony Forum. ECTF now believes
that there will be a need for greater cooperation between ECTF and other groups, especially with
the advent of the Internet. There will be a need to clarify the issues of which body has copyrights
and other intellectual property rights.
J. Rafferty noted that the ECTF has a MIB development activity which supports fax and other
resources. There was a motion for TR-29.2 to develop a liaison to ECTF, to be relayed by J.
Rafferty, to get access to the ECTF MIB for review and discussion, since TR-29 has interest in
developing a Fax MIB as a US standard. This was agreed.
CLASS 1, PN-3626
PN-3626 has been retrofitting ITU-T T.31 (Class 1) for incorporation in an updated TIA-578-B.
The document recently passed an industry ballot. J. Dahmen (Lanier) is editor. Ballot comments
from K. Krechmer (ACTION Consulting) were incorporated. The references from V.25ter needed
to be changed to reference the replacement recommendations V.250 and V.251 instead. The
document will be forwarded to TIA for publication.
CLASS 2.1, PN-3625
PN-3625 is closed. However, TR-29.2/99-02-03 (J. Rafferty, Human Communications) was
presented on potential extensions to Class 2.x. It proposes that new commands be created to
support changes to the T.30 protocol without requiring changes to the command syntax for DTEs
or DCEs. It also proposes an approach for handling extended negotiations within a future
extension to Class 2.x. There was discussion on the document. It was felt that this approach still
requires a DCE to report back to a DTE regarding which features of T.30 it can support. Thus,
the command input from a DTE would not be followed blindly by the DCE, but would need to take
into account the capabilities of the DCE. It was clarified that it is likely that a DCE’s firmware
probably would still have to be updated in order to support new T.30 features, but the syntax for
the command that helped to establish the negotiating position would not have to be changed. It
was further noted that it would be very useful for the DCE to be able to report back on what T.30
protocol version is supported. Members were encouraged to review the paper; a decision on
whether to open up a new project will be made at the next meeting.
CLASS X, PN-3130
J. Dahmen (Lanier) agreed to be editor of PN-3130, Asynchronous Facsimile DCE Control
Standard, Service Class 4. The current direction is to develop a new specification on increments
to Class 1.0 (TIA/EIA-578-B). It was suggested that the intended end result should be to develop
an interim standard. TR-29.2 has not yet decided whether the additional Class X functionality
would result in a new FClass designation (i.e., other than 1.0).
James Rafferty, Human Communications
March-April 1999
9
TR-29 MEETING ROSTER, FEBRUARY 8 - 10, 1998, DANA POINT, CA
Steve Urban, Delta Information Systems
David Duehren, Brooktrout
Vivian Cancio, Xerox
Bay Networks
Brooktrout Technology
Conexant
Conexant
Conexant
Delta Information Sys.
Dialogic
Hewlett Packard
Hewlett Packard
Human Comm.
Lanier
Lucent
Xerox
Xerox
TR-29 Chair
TR-29.1 Chair
TR-29.2 Chair
Moshe Staler
David Duehren
Keith Chu
Frank Hansen
Yu-Shian Lee
Stephen Urban
Michael Spann
Paul Albitz
Megan Hsin
James Rafferty
Jim Dahmen
Herman Silbiger
Vivian Cancio
Lloyd McIntyre
Communications Standards Review
formerly Communications Standards Review-Telecommunications
regularly covers the following committee meetings:
10
TIA
TR-29
TR-30
TR-41
Facsimile
Modems
User Premises Equipment
ITU-T
SG8
SG15 WP1
SG16
Telematic Terminals
Network Access
Multimedia
ETSI
ATA
DTA
TIPHON
TM6
Analog Terminal Access
Digital Terminal Access
Voice Over Internet
Transmission & Multiplexing
March-April 1999
REPORT OF TR-30, DATA TRANSMISSION SYSTEMS AND EQUIPMENT,
FEBRUARY 8 - 10, 1999, DANA POINT, CA
TR-30.1, MODEMS
The following companies have changed their names: Bay was changed to Nortel Networks, and
Rockwell was changed to Conexant.
The chair reported that the next meeting of TR-30.1 will be April 14 in San Jose and will be
hosted by PC-Tel. The next meeting of SG16 will take place in Santiago, Chile, in May.
F. Lucas (3Com, Vice Chair TR-30) reported on a recent ex-parte meeting with the FCC held at
the request of the Common Carrier Bureau. The topic was Docket No. 98-163 which investigates
the possibility of changing the encoded analog content rules in FCC Part 68 from -12 dbm to -6
dbm. TR-30.1/99-02-003 is the report from P. Adornato (Nortel), TIA User Premises Equipment
Division Chair.
At the meeting the FCC explored a possible plan of action, which would consist of a waiver or
“interim order” applying only to PCM modems. Under the “interim order,” the increased power
level would be permitted pending completion of specific tests performed jointly by manufacturers
and carriers within a specified time frame (perhaps 2 years). The carriers would have the right
to remove offending equipment and ask for repeal of the “interim order” if crosstalk interference is
demonstrated either by test or in the field. This proposal seemed a workable compromise.
(Editor’s note: see also the TR-41.9 report in this issue for the carrier’s perspective, in particular
TR-41.9/99-02-024, H. Van Zandt, GTE.)
Subsequent to that meeting, the FCC informed TIA that they would like to have test results prior
to rendering a decision. The proposal is that the FCC may request that Bellcore run the tests
using the test procedures defined by T1A1.7. It was further suggested that industry provide
some of the funds for these tests. The group offered no objections to this proposal from the FCC.
TR-30.1/99-002 (F. Lucas, 3Com) states that the turning on of Circuit 107 during startup was
inadvertently left out of the proposed text for draft Recommendation V.91. A proposal for a
revision to the text of section 8.2.1.6 was also provided. The group accepted this as a proposed
USA contribution to the May SG16 meeting.
TR-30.1/99-004 (J. Heath, Hughes Network Systems) describes in detail a new data compression
algorithm (“LZH”). LZH is LZ78 (LZ2) based, similar to LZW (V.42bis), but provides significantly
better (25-40%) compression ratios with improved software execution times. There was some
concern that the statement “Hughes Proprietary II” occurs throughout the document. It was
clarified that Hughes is proposing this as the basis of a new compression algorithm (e.g., V.42ter)
and has applied for a patent on LZH which is pending. Hughes believes that LZH does not
infringe upon the Welch patent (used in V.42bis and owned by Unisys). As a result of the
discussion, a project will be started for this work; a call for papers was issued.
Dick Brandt (dB Consulting)
TR-30.2, DATA TRANSMISSION
REAFFIRMATION OF TIA/EIA-612 AND TIA/EIA-613
F. Lucas, TR-30.2 Chair, stated that the ballots for the reaffirmation of TIA/EIA-612 (SP-4394,
Electrical Characteristics for an Interface at Data Signaling Rates up to 52 Mbit/s) and
TIA/EIA-613 (SP-4395, High Speed Serial Interface for Data Terminal Equipment and Data
Circuit-Terminating Equipment) close on February 22. He indicated that balloting is now done
electronically via the TIA web site.
March-April 1999
11
ITU-T STUDY GROUP 16
The next ITU-T Study Group 16 meeting is scheduled for May 19-28 in Santiago, Chile. J. Magill
(Lucent, WP1/16 chair) indicated that details of the meeting should be available within days and
he would notify TR-30 members of the details. F. Lucas indicated that there will be a US Study
Group D meeting the week of April 19 to review/approve contributions for the Study Group 16
meeting.
The proposal to revise ITU-T Recommendation V.24 (TR-30.2/98-11-032), List of definitions for
interchange circuits between data terminal equipment (DTE) and data circuit-terminating
equipment (DCE), will be considered at the SG16 meeting. If the US has any concerns with this
major revision of V.24, the April TR-30.2 meeting will be the last chance to review a contribution.
In addition, draft Recommendation V.25I, Command Set for ISDN Basic Rate Terminal
Adapters, is scheduled for Determination at SG16. There is a possibility that this Determination
could be delayed due to the unknown status of the present editor, J. Moughton (Hayes). (Editor’s
note: Hayes has ceased business operations in the USA.)
REVISION OF TIA/EIA-334-B
TR-30.2/99-02-003 (F. Lucas, 3Com, TR-30.2 chair) proposes that TIA/EIA-334-B, “Signal
Quality at Interface between Data Terminal Equipment and Synchronous Data CircuitTerminating Equipment for Serial Data Transmission,” be revised. F. Lucas indicated that 1999
is the time for the 5-year review of the standard. Apparently when TR-30.2 had last revised this
standard, an attempt was made to consolidate a number of the drawings. This resulted in
making the standard somewhat difficult to understand. In addition, three new standards
approved by TR-30.2 since the last revision need to be referenced. These standards are:
• TIA/EIA-687, “Medium Speed Interface for Data Terminal Equipment and Data CircuitTerminating Equipment”
• TIA/EIA-723, “High Speed 232 Type DTE/DCE Interface”
• TIA/EIA-694, “Electrical Characteristics for an Unbalanced Digital Interface for Data
Signaling Rates Up to 512 kbit/s”
TR-30.2 agreed to open a new project for this work. F. Lucas will act as editor.
REVISION OF ITU-T RECOMMENDATION V.250
The chairman reviewed the status of the work in Q4/16 (Modem Diagnostic Commands) to revise
Rec. V.250, Serial asynchronous automatic dialing and control. That work is resulting in a new
draft Recommendation V.mmo, Modem Managed Objects for Diagnostics. In support of this, a
new command, or commands, will be needed in V.250 to retrieve the data. TR-30.2/99-02-002
had been brought to the December 1998 Q4/16 Rapporteurs meeting (as Q4-16_98-10) regarding
possible V.250 commands. It proposes a number of commands to retrieve various groups of data.
F. Lucas has been approached by a number of companies that are concerned that the work might
be deviating greatly from the Microsoft Unimodem specification. TR-30.2/99-02-004 (F. Lucas,
3Com) proposes that TR-30.2 support a command similar to the Unimodem AT#UD, which would
bring back raw data in a fashion similar to the Microsoft command. This would not prevent
additional commands from being adopted, but it would provide a parallel to the existing
embedded base of modems which provide #UD. TR-30.2 agreed to this proposal; it will be put
into the appropriate format for submission to SGD as a proposed USA contribution to Study
Group 16, Question 7.
TDDS ON CELLULAR
D. Brandt (Motorola) reported that there was no news on any possible changes which might be
needed in TIA/EIA-688 (DTE/DCE Interface for Digital Cellular Equipment) from work in the
12
March-April 1999
Cellular Telecommunications Industry Association. He agreed to keep TR-30.2 informed of the
status of this continued work.
UNIVERSAL SERIAL BUS
TR-30.2 has considered the possibility of standardization of portions of the Universal Serial Bus
over past meetings. Unfortunately, the owners of the Universal Serial Bus specification have
been less than supportive of this effort. The chairman reported that he had been approached by
one of the sub-committee chairs in TR-29 regarding TR-29’s concerns on the Universal Serial
Bus, in particular, mapping of the TIA/EIA-232 interchange circuit functions. TR-29 plans to
submit a contribution on this issue at the April TR-30.2 meeting. TR-30.2 again discussed the
standardization issue; TR-30.2 continues to feel it should be done and would be a benefit to the
USB in general. TR-30.2 asked the chair to formally write to the chairman of the USB group
expressing the interest and concerns of TR-30.2 on this matter.
TIA/EIA-644 FUTURE REVISION
J. Goldie, TR-30.2 ad hoc chairman on electrical characteristics, indicated that the ad hoc group
is looking at a revision of TIA/EIA-644, Electrical Characteristics of Low Voltage Differential
Signaling (LVDS) Interface Circuits. This work would be to complete the study item on multidrop
operation. It was agreed that a project should be opened for this work; the work will take place in
the ad hoc group.
Fred Lucas, 3Com
TR-30.3, DATA COMMUNICATIONS EQUIPMENT EVALUATION AND NETWORK INTERFACES
The following companies will become members of TR-30.3 Subcommittee: Satchell Evaluations,
ESS, Mediagate, Paradyne. The following companies will be removed from the membership:
AMP, and Hayes per TR-30.3/99-02-13, e-mail from B. Adams (Hayes) concern the demise of
Hayes and their withdrawal from TR 30.3 membership.
L. Brown (Motorola) will clean up the documents on the FTP site (password protected) and will
setup a committee reflector for PN-4254, Telephone Network Transmission Model for Evaluating
xDSL Systems.
The following procedure was setup for submitting and electronic posting of all TR-30.3
documents:
• A blank documents list will be posted on the committee FTP site. Each time a document is
added to the site, the originator of the document should add the document number and Title to
the list.
• If a document is electronically posted by Thursday before the meeting, the originator of the
document should bring 10 copies of the document to the meeting.
• Committee members should bring their own copies of documents that are posted.
• If a document is not electronically posted by Thursday before the meeting, the originator of the
document should bring 40 copies of the document to the meeting and an electronic copy. The
electronic copy must be posted after the meeting.
• Documents can’t be presented without an electronic copy.
• A Flashcard will be used to distribute electronic copies of the documents at the meeting.
TR-30.3/99-02-02 is the Assignment List from the November 1998 TR-30.3 meeting.
TR-30.3/99-02-14 is the list of TR-30.3 Projects from Communications Standards Summary.
TR-30.3/99-02-27 (J. Douglass, Oak Technology) is a Project Number Request for Telephone
Network Transmission Model for Evaluating V.91 Modem Performance. A PN (project number)
has not yet been received from TIA. J. Douglass will contact B. Zidec-Conner (TIA).
March-April 1999
13
LIAISON R EPORTS
TR-30.3/99-02-11 (G. Ratta, Chairman, ATM Forum Technical Committee) is a reply to the TR
30.3 liaison on DSL Testing. It notes that the ATM Forum Technical Committee (TC) will defer
to the ADSL Forum with regard to physical layer ADSL Testing, as the ATMF TC is involved
with ATM layer testing.
TR-30.3/99-02-05 (D. Brandt, Motorola) is a proposed liaison to T1E1.4, T1M1.3, ITU-T Q4/15
Rapporteurs Group, ADSL Forum, ATM Forum, and UAWG. It describes the scope of the work
in TR-30.3 on the network transmission model for xDSL.
TR-30.3/99-02-09 (P. Adornato, Nortel, Chairman, User Premises Equipment Division) is Notes
on the ex-parte meeting regarding the PCM Modem. TR-30.3/99-02-12 is e-mail from F. Lucas
(3Com) concerning FCC ex parte meeting. F. Lucas (3Com) reviewed these documents. He
indicated that the FCC commissioners were uneasy about allowing a trial period without testing
and making a ruling. F. Lucas said that Bellcore was willing to run the tests for a fee, but
funding issues still needed to be resolved. A letter concerning testing would be sent out to T1E1
and TR-30 membership. A comment was made that broadcast for TV and radio are allowed to be
sent out over the telephone lines at +8 dBm Levels.
TR-30.3/99-02-16©, T1A1.7 Technical Report #58, is a Test Plan for Investigating the Crosstalk
potential of Digital Modems Conforming to ITU-T Recommendation V.90.
J. Douglass (Oak Technology) had e-mailed information about the Bellcore Test Procedure in
December, but it was not formally reviewed. The test procedures are typical of those presently
used for measuring crosstalk. Questions were raised about whether the test procedure was
meaningful. However, the time to comment on the test procedure is past. It cannot be changed
now. Assuming the tests are run by Bellcore, TR-30.3 membership was asked what they thought
about paying for the testing and providing the test equipment. In general, it was felt that the
cost per company would be very small once it is divided among a number of companies. The
biggest cost would be loaning the equipment to run the test and manpower to support the testing.
It was noted that it is in TR-30.3’s and modem companies’ best interest to help the FCC do the
testing. It will also help maintain a good relationship with the FCC.
SP-3459, REVISING TSB-37-A (TELEPHONE N ETWORK TRANSMISSION MODEL FOR EVALUATING M ODEM
PERFORMANCE )
TR-30.3/99-02-18 A - G are the ballots from SP-3459, revision of TSB-37-A, Telephone Network
Transmission Model for Evaluating Modem Performance.
Approve:
5
No comment: 2
TR-30.3/99-02-20 provides the changes to SP-3459 based on the first ballot comments. J.
Douglass (Oak Technology, TR-30.3 chair) will send information on how to access the electronic
ballot to the TR-30.3 mailing list.
PN-3509, REVISION OF TSB-38 (TEST PROCEDURES FOR EVALUATING M ODEM PERFORMANCE), AND
PN-3856, TEST PROCEDURES FOR EVALUATING PCM-MODEM PERFORMANCE
TR-30.3/99-02-24-e (S. Satchell, Satchell Evaluations) is Draft 7 of PN-3509, Test Procedures for
Evaluating Modem Performance. This is a “Heavy” draft: it was created from combining TSB38, a draft of PN-3857, and draft 3 of PN-3509.
TR-30.3/99-02-06, Extending Throughput vs. File Type Test Duration (W. Henderson, Henderson
Communications Labs), proposes to review the PN-3509 methodologies for V.90 modems. Testing
has shown that V.90 modem speed changing ability (as many as 2-3 times per test) makes it
desirable to use longer test files.
14
March-April 1999
TR-30.3/99-02-07, Performance Evaluation of Controllerless and HSP (Host Signal Processing)
Modems (W. Henderson, Henderson Communications Labs), proposes to review the PN-3509
methodologies to accommodate host-based applications. This requires a supplemental test
condition that exercises the HSP PC using a special program for this purpose.
H. Holzbaur (NSTL) and S. Satchell will prepare a contribution listing the tests and their
purpose. This information will be included in an annex. H. Holzbaur (NSTL) will create a new
test file.
It was agreed to change the tests in section 7 to time-based instead of file size-based.
There was a call for contributions on PC-based modem tests. Real data transmission typically
isn’t in one direction for long periods of time. The tests need to accurately reflect real data
transmission.
PN-3857, TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING PCM MODEM PERFORMANCE
TR-30.3/99-02-03© is a copy of the Ballot version of PN-3857, Telephone Network Transmission
Model for Evaluating PCM Modem Performance.
TR-30.3/99-02-19 A - L are PN-3857 Ballots:
Approve:
7
Approve with comments:
4
Do not approve with comments: 1 (TAS)
TR-30.3/99-02-25 is e-mail from G. Hillman (Motorola, PN-3857 editor, who was not present)
concerning PN-3857 ballot responses and how to handle them.
TR-30.3/99-02-10, Proposed Changes to 60 Hz and Harmonic Noise Impairments (R. Perez,
Bellcore), proposes a new (reduced) set of 60 Hz noise impairments based on laboratory tests (by
P. Dillon, BellSouth contractor) of V.90 performance over IDLC copper channels. The report
from the BellSouth tests is included.
TR-30.3/99-02-17, V.90 Field Testing (J. Douglass, Oak Technology), is a list of the statistics
being gathered in a V.90 field test to help validate the Network model in PN-3857. The results
are expected to be available at the April TR-30.3 meeting.
TR-30.3/99-02-22, Robbed Bit Signaling (RBS) Patterns for IDLC Systems (R. Perez, Bellcore),
provides several pages from Bellcore documents (TR-08 and GR-303) that depict the signaling
states that are available on IDLC (Integrated Digital Loop Carrier) systems.
TR-30.3/99-02-34 (S. Satchell, Satchell Evaluations) provides modified text for two sections of
PN-3857.
TR-30.3/99-02-35, Test Data for the Proposed V.90 Network Model (J. Douglass, Oak
Technology), provides extensive test data from six different client modems and three different
server products of different manufacturers (not identified ny manufacturer).
All ballot comments were reviewed and changes were agreed. B. Anders (3Com) will supply a
list of these changes in TR-30.3/99-04-37. G. Hillman (Motorola - editor PN-3857) will
incorporate the changes into a draft for the next meeting.
PN-4254, TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATION XDSL SYSTEMS , AND
PN-4255, TEST PROCEDURES FOR EVALUATING XDSL SYSTEM PERFORMANCE
TR-30.3/99-02-04 (B. Anders, 3Com) is notes from a brainstorming session on xDSL testing held
in Clearwater at the November TR-30.3 meeting. It develops a rough view of the test equipment
model.
March-April 1999
15
A small ad hoc group in Clearwater created TR-30.3/99-02-026, Draft 1 of PN-4254, Network
Access Transmission Model for Evaluating xDSL Modems. A disclaimer needs to be added to the
draft of PN-4254 stating that it is very preliminary and for information only. PN-4254 will keep
the same document number but the revision will change (i.e., TR-30.3/99-02-026 R1).
TR-30.3/99-02-15, Voice Grade (Analog) Loops (M. Kalb, AT&T, same as T1A1.7/98-15R5),
contains text for a draft T1 technical report describing unbundled loops, NI-to-switch segments,
and treated lines.
TR-30.3/99-02-21 (R.K. Smith, Paradyne) presents the two additional North American
Residential Wiring Models approved for inclusion in draft Recommendation G.996.1 (formerly
G.test) at the January Q4/15 meeting.
TR-30.3/99-02-23, Methodology Involving Loop Selection for xDSL Model (R. Perez, Bellcore),
demonstrates an analysis of non-loaded loops in a BellSouth contribution to Universal ADSL
Technical Group (TG/98-057, G. Tennyson) and compares the aggregate to the first three loops
from ANSI T1.601. The paper suggests that a set of frequencies needs to be agreed to represent
the xDSL bandwidth.
TR-30.3/99-02-28, Transmission Model for Evaluating xDSL Communications Systems: Network
Topology (J.-P. Houdard, TI), analyzes the xDSL environment related to Telephone Network
Topology, for the purpose of defining the basic elements of the network model for evaluating the
performance of xDSL communications systems.
TR-30.3/99-02-29 (J.-P. Houdard, TI) analyses the xDSL environment including transmission
impairments and power spectral density of most of the xDSL signals.
TR-30.3/99-02-30 (J.-P. Houdard, TI) provides Impairment Combinations, Test Loops and
Network Model Coverage scores for most of the xDSL communication systems under deployment
on today’s telephone network.
TR-30.3/99-02-31 (J.-P. Houdard, TI) provides a test set-up for evaluating xDSL communications
systems that share the same subscriber loop for providing simultaneous broadband and
voiceband services.
TR-30.3/99-02-32, Consideration of non-xDSL spectrum, especially Home LAN (Y. Okamura,
NEC Corporation, same as T1E1.4/99-039), notes that power coupled into line (noise injection)
from non-DSL, especially HomePNA, has to be considered as part of the spectrum management.
TR-30.3/99-02-33, G.996.1: Residential Telephone Wiring Survey & Proposed Premises Wiring
Models (R.K. Smith, Paradyne), summarizes the results of a survey: premises wiring
configuration of most residences differs significantly from the model adopted in at the Q4/15
meeting in Antwerp (August 1998).
TR-30.3 felt that the loop characteristics vary for each region and that we should contact each
region to get Loop Statistics. P. Kyees (Paradyne) will contact US West about Loop Statistics.
R. Perez (Bellcore) will gather information on loop characteristics. R. Hamdi (Compaq) will
provide J. Douglass (Oak Technology) with a list of contacts for each region, so that he can
contact them concerning Loop Statistics. TR-30.3 will consider loops from other models, but
wants an accurate model that is not technology-dependent.
R. Hamdi (Compaq) will be the liaison to the ADSL Forum for at least the next meeting. He will
forward TR-30.3/99-02-026R1, the agreements/issues list and associated documents to the ADSL
Forum.
TR-30 and T1E1 will jointly submit the final contribution to the ITU. The document will be
passed back and forth between the committees, and the work will alternate between the
16
March-April 1999
committees. P. Kyees (Paradyne) will be the editor for both committees. L. Brown (Motorola) and
J.-P. Houdard (TI) will be assistant editors.
L. Brown (Motorola) will chair the T1E1 ad hoc committee for xDSL testing. The next T1E1
meeting will be held in Tustin, CA, March 8-12. L. Brown will also be the TR-30.3 liaison.
Members of TR-30.3 and the T1E1 ad hoc committee are encouraged to attend both meetings.
An assignment list will be created for each section of the document. It will be kept as part of the
draft document. L. Brown will keep an agreement/issues list and rules for agreement/issues list
that will be passed between the committees.
PN-4256, REVISION OF TIA/EIA-496-A, INTERFACE BETWEEN DCE AND THE PSTN
An ad hoc committee consisting of L. Smith (Lucent), H. Hagan (Lucent) and R. Perez (Bellcore)
met to review TIA/EIA-496-A in detail. They decided the following:
•
•
•
•
•
•
A revision to TIA/EIA-496-A is needed.
Many of the minimum requirements are not documented anywhere else.
No major changes will be required.
References will be made to other standards where appropriate.
A rationale will not be included.
The echo control section needs some research.
The final draft will be posted on the FTP site before the next meeting, because it must be released
for ballot before June.
Jack Douglass, Oak Technology
TR-30 MEETING ROSTER, FEBRUARY 8 - 10, 1999, DANA POINT, CA
Dick Brandt, Motorola (dB Consulting)
Les Brown, Motorola
Fred Lucas, 3Com
Jack Douglass, Oak Technology
Host: Conexant
3Com
3Com
3Com
3Com
3Com
Analog Devices
Ascend Comm.
Bellcore
Cisco Systems
Cisco Systems
Compaq Computers
Conexant
Conexant
Conexant
Conexant
Davicom
EICON (formerly Trisignal
Communications)
ESS Technology
GAO Research
Henderson Comm. Labs
March-April 1999
TR-30 Chair
TR-30.1 Chair
TR-30.2 Chair
TR-30.3 Chair
Bryan Anders
John Feagang
Fred Lucas
Wayne Park
Richard Williams
Haim Primo
Sandeep Agaswal
Ricardo Perez
Tom Martin
Kevin Riley
Rabah Hamdi
Stan Bacon
Keith Chu
Joe Hoang
Craig Mellon
Bryan Gillette
Claude Tremblay
Jordan Cookman
Alan Marion
Warren Henderson
17
Henderson Comm.Labs
Hewlett Packard
Hughes Network Sys.
IBM
Lucent
Lucent
Mediagate
Motorola
Motorola
MultiTech Systems
National Semiconductor
Nortel Networks
NSTL
Oak Technology
Paradyne
Paradyne
PC-Tel
Satchell Evaluations
Siemens Microelec.
TAS
Texas Instruments
Texas Instruments
Texas Instruments
VoCAL Technologies
W.E. Martin Consulting
Donald Pile
Megan Hsin
Jeff Heath
Ali Sadri
Horace Hagen
John Magill
Mendel Aizner
Dick Brandt
Les Brown
Sam Gopalan
John Goldie
Slabodon Jovanovic
Helen Holzbaur
Jack Douglass
Philip Kyees
RK Smith
Gary Anwyl
Stephen Satchell
Neal King
Mike Pellegrini
Kevin Gingerich
Jean-Pierre Houdard
Jose Soltero
Alberto Torres
Wayne Martin
COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:
Communications Standards Summary (ISSN 1075-5721), a quarterly publication
reporting on all active projects 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 of
either of CSR’s technical journals, please contact Elaine Baskin, tel +1 650 856-9018,
fax +1 650 856-6591, e-mail: [email protected]
18
March-April 1999
REPORT OF Q11-14/16 RAPPORTEURS MEETING
FEBRUARY 15 - 19, 1999, MONTEREY, CA
Editor’s note: Q15/16 also met concurrently in Monterey. The Q15/16 report will be in the next
issue of CSR.
Q11/16, CIRCUIT-SWITCHED NETWORK (CSN) MULTIMEDIA TERMINALS AND SYSTEMS
The ninth meeting (“I”) of Q11/16 Circuits switched network (CSN) multimedia systems and
terminals experts met co-located with Q12-15/16 Experts. Twenty six contributions were
submitted, of which 18 were technical (see document list Q11-I-00r1, and
ftp://standard.pictel.com//lbc-site/). Q11-I-TD2r3 is the draft agenda. Q11-H-25d4 is the draft
report from the Torino Q11/16 meeting November 17-20, 1998 (see also report in CSR 10.2).
Q11-I-22d1 is the draft report of this meeting. A list of MPEG-4 IP holders will be attached to
Q11-I-22d2.
Q11-I-10 (Nokia) is the Interoperability Experiments Ad hoc report. Three companies performed
H.324M interoperability tests February 5, 1999 in Stockholm. The three arranged test sessions
covered initial level set-up, CCSRL layer and dynamic level change verification. No additional
insufficiencies in the standards were identified, other than those already noted in Q11-H-22. The
group proposes that further tests of the mobile annexes could be performed by the IMTC.
I. Sebestyen (Siemens, IMTC) provided guidance on how this work could be carried out in IMTC
and it was agreed that M. Luomi (Nokia) and T. Geary (Conexant) would generate a communiqué
from this meeting to the IMTC conveying this request.
Members were reminded of the ITU patent policy and provided the URL for the information at
ITU: http://www.itu.int/ITU-Databases/TSBPatent/
H.324 SYSTEM , CONTROL AND MUX
Q11-I-13 (M. Luomi, Nokia) is proposed text for the H.223 (multiplexing) Implementer’s Guide
and for the H.324 (circuit mode video telephone) Implementer’s Guide. The group agreed to
accept the portion of the addition applicable to H.324. M. Luomi (Nokia) will serve as editor to
revise the H.324 Implementer Guide for the SG16 May meeting.
Q11-I-06 (TI, MIT, UCLA) describes the use of H.223 Annex C (multiplexing protocol over high
error rate channels) to achieve Unequal Error Protection of MPEG-4 video data. UEP supports
video packet error protection by coding the most important information (RS and header) with
more bits than the motion video and where the texture (DCT coefficients) use the least number of
error protection bits. The proposal was reviewed and the group felt that additional study was
desired. The contributor asked for assistance to expedite this work as the work in MPEG is
being finalized in the near future. Several members agreed to work with the contributor.
H.320 SYSTEM
No contributions against the white documents for H.263+ in H.320 were received at this meeting.
Q11/16 MOBILE
H.223 ANNEX D MULTIPLEXING OVER ERROR -PRONE CHANNELS
Q11-I-04© is a copy of the white document of H.223 Annex D as submitted to the ITU. It was
provided for information.
March-April 1999
19
C LARIFICATIONS TO H.223 ANNEX B TEST MODEL
Q11-I-05 (T. Suzuki, NTT DoCoMo) contains draft text for the H.223 Implementer Guide. It
includes clarifications to H.223 Annex B. The group accepted it after the changes as defined in
Q11-I-05r1 were included.
INTEROPERABILITY EXPERIMENTS
Q11-I-12, the now completed Interoperability Experiments Test Plan for Mobile v.2 (Nokia), was
presented for information (Table 1).
Phase
0
1
2
3
4
Description
Approval of plan
Bit syntax verification
Connection set-up
The usage of CCSRL for a control channels
Dynamic level change
Location
Cannes, France
between meetings
Geneva
Torino
Stockholm
Date
June 98
6/98-9/98
Sept 98
Nov 98
Feb 99
Table 1. Interoperability Experiments Test Plan for Mobile v.2
Q11-I-26 (T. Geary, Q11 Rapporteur) is a draft letter to IMTC requesting their support for
future mobile interoperability testing. It was approved.
M ULTIMEDIA SERVICES IN IMT-2000
Q11-I-11, WCDMA Error Patterns (Nokia), is a response from Q11/16 to a request by Q15/16
and provides a set of simulated Wideband CDMA error patterns for error resilience simulations.
The channel models used in generating the error patterns are based on the latest air interface
specifications by ETSI. Q15-G-38, Pseudomux8.c: Simple Video Packet MUX Simulator (G.
Sullivan, PictureTel et al), was also presented for information. An ad hoc chaired by B. Wimmer
(Siemens) worked to establish a minimum set of base line patterns which they felt would be
representative for the Q15/16 experts to use in their work.
Q11-I-15, Satellite Component of IMT-2000 (L. Christodoulides, Inmarsat, same as APC-1539a),
was presented to the joint group and discussed; the points will be considered by the ad hoc group
when selecting representative error patterns which will be recommended to Q15/16 for use in
their video development work.
ERROR CHANNEL SIMULATION
See Q11-15/16 Joint report, below.
Q11/16 CLOSING SESSION
Q11-I-27 is the ad hoc report on error patterns for Q15/16. During discussions the group decided
on 64 SCN and WCDMA. The group reported they defined eight error patterns for WCDMA
where the mean focus is 64kbit/s, two for DECT, and two for Satellite. Worst case patterns were
defined. These patterns will be generated along with descriptions and put on the Q11/16 ftp site
and announced on the SG16 Q11/16 lbc and video reflectors.
MPEG-4 on H.223 update: The group met and believe that code points will be required along
with some descriptions for use in H.223.
N EW W ORK ITEMS
Q11-I-16 (Ericsson) proposes a new study item: H.226 (multilink protocol)-like functionality for
H.324/M. It notes an interworking problem where H.324/I terminals invoke H.226 at bit rates
exceeding 64kbit/s, making inter-operation with H.324/M terminals impossible. The group
20
March-April 1999
accepted this work; it was agreed that a Mobile Multilink ad hoc chaired by G. Roth of Ericsson
would be established to further this effort. A very aggressive preliminary schedule for this work
has a target of Determination in February 2000. This schedule may change as the ad hoc
evaluates the extent of the effort required.
What is required of a H.324 Annex D terminal to support H324 Annex C endpoints? No
contributions were received toward this item but the Mobile Multilink ad hoc agreed to consider
this item in their work.
PLANS FOR FUTURE W ORK
Table 2 presents the status of Q11/16 Recommendations.
Recommendation
H.320 (Revision)
H.221 (Revision)
H.230 (Revision)
H.242 (Revision)
H.223 Annex D
H.324 I/G update
H.223 I/G update
H.mml (Mobile
Multilink)
Determination
9/98
9/98
9/98
9/98
9/98
Decision/Approval
5/99
5/99
5/99
5/99
5/99
5/99
5/99
2/00
Comment
White generated
White generated
White generated
White generated
White generated
In work
In work
In work
Table 2. Q11/16 Recommendations Status.
The following ad hoc committees were approved for work until the May SG16 meeting. The group
agreed that the Non-Conversational Services ad hoc should be abandoned.
Ad Hoc
System
Mobile
H.263+ in H.320
Interoperability Testing (Mobile
terminals)
Mobile Multilink
Chair
M. Nasiri
B. Wimmer
S. Gupta
M. Luomi
G. Roth
Q11 - 15/16 JOINT MEETING
Q15-G-04, Status Report of H.263+ in H.320 ad hoc (S. Gupta, VTEL), was briefly presented.
The drafts of H.320, H.221, H.242 and H.230 were reviewed by Q11/16 in November 1998 in
Torino, Italy. Minor editorial changes to H.221 and H.242 were made. More significant changes
to H.230 included modifying the commands videoNotDecodedMBs, videoFastUpdateGob and
VideoFastUpdateMBs to clarify numbering of MBs and GOBs. Also “shall” and “should” usage
was reviewed and changed. For H.320 a couple of lines were added to establish support for text
conversation facilities. It was noted that the white document revisions have been sent to the ITUT TSB.
VIDEO C ODECS
G. Sullivan (PictureTel, the Q15/16 rapporteur), presented the status of the Q15/16 work on
H.263++ and H.26L. He provided a chart of various elements of the current work for both
projects. The group believes they can achieve the same quality at 50% of the bit rate required for
H.263. The targets for H.263++ and H.26L are Decision in February 2000 and Determination in
late 2001, respectively. Two of the seven key areas in H.263++ are fairly mature: error resilient
Data Partitioning, and enhanced reference selection with long term memory. Affin motion
compensation is at the next level of maturity. H.26L has six key technical areas. The intention
March-April 1999
21
is to create a new standard that is not necessarily backward-compatible. The compression
improvement is expected to be today’s typical H.263 compression at half bit rate. The features
include:
• Back to the basic approach
• Low delay
• Error resilience
• High quality
• Network friendly
Q15-G-40, the status of Video coding for sign language and lip reading, was presented.
Q11-I-15, Satellite Component of IMT-2000 (L. Christodoulides, Inmarsat, same as APC-1539a),
requests consideration of the requirements for satellite use in mobile communications and
provides a good technical tutorial on the effects of satellites on data communications. After
discussion, it was noted that bit error rate requirements for the satellite mobile environments are
less stringent than those for the land mobile environments. The meeting was also advised that
IETF working group tcpsat (Transmission Control Protocol over satellite) is working on an
Informational RFC draft due January 1999. It was noted that the Satellite Group of IMT-2000
will meet in March.
J. Villasenor (UCLA) presented Q15-G-14, the current status of the third generation mobile work
in TIA TR-45.5 (CDMA 2000). The CDMA 2000 work is broken into two phases: phase 1 data
rates up to 144 kbit/s and phase 2 data rates up to 2 mbit/s with QoS capabilities. TR-45.5
expressed high interest in the ITU video work over the longer term.
Q15-F-16 (Effects of error prone channel on video data, G. Sullivan, PictureTel, see CSR Vol
10.2) and Q15-G-38 (Simple Video Packet MUX Simulator, G. Sullivan, PictureTel) representing
the error channel simulation used by Q15/16 were briefly discussed; one member offered a
contribution. There were no other comments. Q15/16 asked if the worst case channel should
continue to be used. It was suggested that it should be retained. Q11/16 Mobile group agreed to
review further details and make a response to Q15/16 at this meeting. Q11-I-23 (B. Wimmer,
Siemens, same as Q15-G-42) is the response; it proposes improvements to the H.223/Annex B
Test Model by enhanced resynchronization structure and optional multiplex header. The Mobile
group supported delivery of this information to Q15/16.
(NON -ITU) AUDIO CODECS
Q11-I-03, Requirements for Layered Codec (H. Harasaki, NEC, same as APC-1536), clarifies
the aspects of the MPEG-4 codec and makes note of the features that are relevant for use in
H.32X: layered coding, bit rate scalability, and bandwidth scalability. It was not presented as a
substitute for the layered codec work of Q20/16 but is desirable because it exists today and the
work of Q20/16 is in the future. The paper proposes support for all profiles. The meeting
concluded that the definition of the H.245 codepoint should be made at the May SG16 meeting
after consultation with the WP3/16 audio coding experts.
Q11-I-18, MPEG-4 Audio codec support in H.245 (same as APC-1489), is MPEG’s response to a
SG16 liaison requesting more information as to the status of the quality testing and benefits of
MPEG-4 Audio to H.32X systems. The ISO/IEC JTC 1/SC29/WG11 (MPEG) liaison points out
the value of the audio tools that can be used for transmitting audio at low bit rates suitable for
the Internet, digital radio, or other bandwidth-limited delivery. The group noted that the testing
results provided have not yet had time to be reviewed by relevant ITU experts. The results
referenced by this contribution will be submitted to the relevant Questions within ITU SG16. The
Q11/16 experts will review the status and make a recommendation to SG16 at the SG16 meeting
in Santiago (May 1999). It was agreed that a liaison providing the status of this work in ITU
would be returned to ISO/IEC; H. Harasaki will draft this liaison response.
Q11-I-19 (R. Roy et al, AT&T, same as APC-1494), Q11-I-20 (D. Gal, Lucent, same as APC1530), and Q11-I-14 (Nokia, NTT DoCoMo, Ericsson and Siemens) propose definition of H.245
22
March-April 1999
codepoints for TIA IS-641 enhanced full-rate speech codec and TIA IS-95 (CDMA) enhanced
variable-rate speech codec and IS-136 (TDMA) ACELP codec. A discussion took place over the
abundance of different audio coding for H.323 systems, and criterion to define H.245 codepoints
for non-ITU coding. The status of the “IS” codec in the development process was questioned; it
was noted it is still an “IS” (Interim Standard), which, in the TIA, indicates that a standard has
not yet completed the ANSI standardization process. The exact status could not be verified at
this meeting. The general question was posed as to what the ITU-T policy for inclusion of non-ITU
codecs should be. It was noted that the ITU has a specific process for recognition of standards
from other standards organizations but only after the process necessary for reference has been
completed. The issue will be posed to SG16 management. Further action was deferred pending
the answer to the policy issue raised. It was also noted that an H.245 generic object capability
mechanism might eliminate the problem. This issue will be revisited at the May SG16 meeting
after obtaining the guidance of SG16.
Q11-I-14 (Nokia, NTT DoCoMo, Ericsson and Siemens) proposes H.245 support for AMR speech
codec. This codec was approved by ETSI during the past week.
The H.245 Editor noted that an alternative format for revision and additions to H.245 is being
considered and all proponents were asked to provide the requested changes in both formats for
consideration at the upcoming meeting.
MPEG-4 SYSTEM
Q11-I-17 (MPEG, same as APC-1488) is MPEG’s liaison to SG16 regarding MPEG4 Systems on
H.32X. It advises that ITU-T member organizations would provide specific proposals. Q11-I-08
(Bosch, Ericsson, NTT DoCoMo, same as APC-1521) proposes support of full MPEG-4
functionality in H.324 terminals as another type of optional data stream. While there was
general support, the group expressed concern in a number of areas and felt inclusion at this time
was premature and not properly thought out. Items noted included operation in the H.223 SCN
environment where bit errors will occur, clarification/correction of the proposed syntax to avoid
confusion with the use of MPEG-4 Visual only, and defining in a suitable location in the H.324
recommendations where the complete details relating to proper use of this technology would
appear. The contributor was asked to address these concerns in subsequent contributions for the
upcoming SG16 meeting. It was agreed that a liaison providing the status of this work in ITU
would be returned to ISO/IEC; J. Vollmer (Bosch) will draft this liaison response. This work was
coordinated with the response liaison generated by H. Harasaki and was reviewed at the closing
session as Q11-I-25 (same as APC-TD49).
MCV IN H.230 AND H.243
There is no reliable means for a terminal to know when its video signal is being broadcast to all
remote sites, so there is a risk that transmission may begin before all sites are ready to receive
the still image. Q11-I-09, Correction of problems related to MCV (Multipoint Command
Visualization) in H.230 and H.243 (P. Luthi, PictureTel, B. Hill, VideoServer, same as APC1549), proposes text for corrections to both Recommendation H.230 and H.243. Inclusion of this
change would require minor changes to the white document for H.230 and a revision of H.243.
The group accepted the proposal; P. Luthi (PictureTel) was nominated editor for revision of
H.243. It is expected that contributions requesting the changes to H.230 and proposing draft
text for revision of H.243 will be submitted to the SG16 May meeting from a national body or
member company.
ITU-R TG8/1 AND SG13/Q23
The group continued the discussion suspended at the Torino (November, 1998) meeting (see CSR
Vol 10.2 Joint Q11-14 report). Considering that no new inputs were made at this meeting and
that answering ITU-R TG8/1 was important, the group concluded that the introductory part of
the previous draft liaison response (Annex 5 to APC-1485, Annex A to Q11-H-25d4) and the
comment provided after the Torino meeting (Annex B to Q11-H-25d4) be combined and
March-April 1999
23
dispatched. Q11-I-24 (same as APC-TD44) is the resulting liaison to ITU-R TG8/1 concerning
requirements for IMT-2000. It provides general information on the work in Q11-14/16 and
requests support of IMT-2000 network message capabilities.
H.32L
It was noted that there have been no additional contributions regarding H.32L (future terminal
interworking); it was suggested that this work be identified as work for the Study Period 20012004.
AAL2 SIGNALING AND SWITCHING
Q11-I-07 (Chairman WP2/13, same as APC-1508) is a status report on AAL2 signaling and
switching. SG13 is the lead SG in B-ISDN. SG13 is working to resolve the following questions:
• Is there sufficient benefit to dynamic switching of AAL2 compared to multiplexing at AAL2,
to warrant the additional complication in ATM networks?
• Does the introduction of AAL2 switching really complicate the ATM network and what is the
likely impact on the ATM market in the next five years?
• Will statistical multiplexing of low bit rate channels offer a better architecture and overall
solution than AAL2 switching?
The Joint meeting took note of this status report.
Q12-14/16 RAPPORTEURS M EETING
This Q12-14/16 Rapporteur meeting was held under the joint chairmanship of S. Okubo (TAO), D.
Skran (Ascend) and G. Freundlich (Lucent). G. Thom (Delta Information Systems) advised the
meeting that he would step down as Rapporteur for Q14/16 and that SG16 management had
agreed to the replacement by G. Freundlich.
APC-1554 is the report of this meeting. 68 APC-numbered documents and 50 Temporary
Documents were submitted to this meeting. They are available at ftp://standard.pictel.com/avcsite/9902_Mon/. This meeting was operated almost totally electronically; documents were
distributed as PC files and presentations were given by use of an LCD projector.
The major objectives of this meeting were preparation of draft Recommendations for
Determination at the May 1999 SG16 meeting. Considering the refinement of the draft
Recommendations listed below: The meeting agreed to distinguish between purely editorial
improvements which will be submitted as Rapporteur’s TDs, and other proposed changes which
will be submitted as contributions of the member organizations after coordination at this meeting.
Advancement of the ongoing works included:
• GK-GK communications
• ISUP signaling transport
• New SUDs
• H.321 Implementers Guide
TD-6 contains a Call for Papers for a special issue of IEEE Communication Magazine on
Internet Telephony (due June 30, 1999, to be published April 2000). This is a good opportunity to
publicize the Q12-14/16 work. D. Skran (Ascend) and other collaborators will submit a paper on
H.323.
REVIEW OF RELATED MEETINGS
GII workshop, December 1998
The workshop discussed how ITU addresses IP. SG15’s new Question 21 on gateway equipment
interconnecting PSTN and IP networks was also discussed (see below TD-08).
24
March-April 1999
IETF, December 1998
• SIP: Session Initiation Protocol Draft 12 is going to proposed standard.
• SIGTRAN: Signaling transport over the internet, reissue basic architecture, Annex E was
presented as one of 12 documents
• MEGACO: This work is active, the draft device control protocol (media gateway control) is on
the table this month. The H.GCP draft was input. There is a meeting next month about
intermedia gateway. APC-1547 (IETF Megaco WG) is a copy of Media Gateway Control
Protocol Architecture and Requirements.
• IPTEL is developing the gateway location protocol, which is related to Annex G.
• AVT: Audio/Video Transport developer of RTP is now working on multiplexing payload
formats; 4 to 6 proposals have been made
DAVIC, January 1999
DAVIC is now working on “TV Anytime” and “TV/Anywhere” systems. Audiovisual transport
over IP is addressed in the latter system.
ATM Forum, February 1999
The draft on the H.323-H.323 gateway was put to straw ballot. It starts the gateway
decomposition work at the ATMF.
TIA
TR-41.3 is now handling VoIP telephone terminals.
European Compute Manufacturers Association
ECMA TC TG32 is working on internet and gateway, see http://www.ecma.ch.
TIPHON, January 1999
TIPHON is working on the H.GCP related area. As to protocol supported, MEGACO is
expected. A new working group on mobility was formed. (See report in CSR 10.2.)
IMTC
The IMTC held Interop tests of H.320 in December 1998; there will be a joint test with TIPHON
in January 1999. SuperOp is next September in Hawaii. A market-oriented IMTC Forum will
be held next April in Munich. The conferencing compatibility program is aiming at an IMTC
approval logo. There are two new WGs: audio codec program, and mobility mobile system.
Multiservice Switching Forum
The Multiservice Switching Forum was created in Dec. 1998 for interoperability arrangements to
facilitate procurements. It will use Packet switching IP or ATM, based on existing standards.
Q12/16, B-ISDN MULTIMEDIA SYSTEMS AND TERMINALS
S. Okubo (TAO) is the Rapporteur for Q12/16.
IMPLEMENTERS G UIDE FOR H.321
APC-1486 (SG11) is a liaison response to SG16 regarding the use of Broadband Report Type IE
for clock source indication. APC-1509 (S. Okubo, Rapporteur Q12/16) is proposed draft text to
reflect SG11’s advice on the H.321 Implementers Guide. The meeting agreed to this text and the
proposal that SG16 approve this Implementers Guide after the Decision of the Q.2931
amendment expected at SG11 in December 1999. This draft will also be submitted to the next
SG16 meeting.
INTEGRATED EDITION OF H.222.0|ISO/IEC 13818-1 AND H.262|ISO/IEC 13818-2
APC-1490 (MPEG) is a liaison response advising that Amendment 7 to H.222.0|ISO/IEC 138181 (MPEG-4 stream carriage over Transport Streams) is being worked out and should be part of
the integrated edition. The meeting agreed to this plan; the response liaison is in TD-45. MPEG
March-April 1999
25
also responded agreeing to the Q12/16 liaison (Nov 20, 1998) with changes and corrections for the
integrated edition of H.222|ISO/IEC 13818-1 and H.262|ISO/IEC 13818-2.
FUTURE W ORK IN Q12/16
Table 1 presents the status of Recommendations in Q12/16.
Recommendation
H.222.0|ISO/IEC 13818-1 Amendment 5
H.321 Implementers Guide
Security for broadband systems
VBR aspects
H.246 Annex (broadband system
interworking)
MPEG-2 packetization (joint with Q.13)
Det.
TBD
TBD
TBD
Dec.
99/05
99/05
00/02
00/02
TBD
TBD
TBD
Editor
S. Okubo (TAO - Japan)
{solicited}
M. Nilsson (BT - UK)
{solicited}
TBD
TBD
{solicited}
98/09
99/05
Table 1. Status of Q12/16 Recommendations.
Q13/16 MULTIMEDIA OVER PACKET NETWORKS
D. Skran (Ascend) is the Rapporteur for Q13/16.
TD-8, New Question on Functionality and Interface Specifications for GSTN Transport Network
Equipment for Interconnecting GSTN and IP Networks (new Q21/15, source WP2/15 Rapporteur
D. Sparrell, AT&T), describes the new work on telephony to IP gateways being started in
Q21/15. (See report in this issue of CSR.)
TD-42, ISDN Aspects of Internet Interworking (USA, S. Rengasami, Bellcore), is a paper to
Q11/11 which was provided to Q13/16 for information. It explores the ISDN aspects of Internet
interworking and areas that may require further study. It is of great interest to the H.323
community.
Several delegates expressed concern about duplicate work in other SGs. The rapporteur urged
the delegates and administrations to take appropriate actions to ensure their views are
represented in SG11 and SG15.
APC-1487, draft liaison statement to ITU-T SG16 on webcasting from Q31/9, is a progress
report on Webcasting. Webcasting is a term for the distribution of sound and TV programs over
IP networks. This proposes using IETF protocols RTP and RTCP to webcast, using all the
standardized forms of audio and video coding including MPEG. It was noted by the delegates.
H.323 IMPLEMENTERS G UIDE
Changes to H.323, H.255.0, H.235, and H.450.x recommendations are all included in a single
implementers guide so that implementers need look in only one place for all corrections to
documents related to H.323.
APC-1511, Master/Slave determination for inter-zone calls in H.323 (Madge Networks), proposes
adding a clarification of the Master-Slave determination procedure into the implementers guide.
TD-13 (C. Purvis, Madge, and D. Walker, Mitel) proposes text for this clarification. It will be
added to the implementers guide and H.323 V3.
APC-1512 (Madge) covers a number of points for the H.323 Implementer’s Guide. Point 1
(Multiple aliases in ARQ, setup, and LRQ messages) was accepted for the implementers guide. It
was noted that the GK may transform the alias before identifying the user. Point 2A proposes
26
March-April 1999
that the GK be able to send the H.245 control signaling and the call signaling to different places.
It was agreed that in principle H.323 V3 would move in this direction, but concerns were raised
that this requires careful study; it will not be put into the implementers guide at this time. Point
2B proposes clarification that the GK need not have an MC to route the H.245 control channel;
this was agreed for the implementers guide. Other aspects of this proposal require further
consideration.
APC-1520 (F. Audet, Nortel Networks) provides corrections to H.323 and H.245 regarding fast
start procedures. The comments of section 2 (Indication of ATM capabilities in
TransportCapability) were accepted for the implementer’s guide and H.323 V3. The comments of
section 3 (Setting the flowControlToZero) will be accepted toward H.323 V3 and the
implementer’s guide, but with the modification that instead of a new field in H.245, fast start will
be modified to allow additional H.245 messages in/after the initial OLC (Open Logical Channel).
APC-1522 (D. Walker, Mitel) proposes additions to the H.323 Implementer’s Guide.
• The comment of section 1 (H.245 Tunneling) was accepted for the implementer’s guide and
H.323 V3.
• The comments of section 2 (Endpoint registration) were accepted for the implementer’s guide
and H.323 V3, with some additional changes and deletions.
• The comments of section 3.1 (Transport Addresses) were considered as part of the SUD/SET
work.
• The comments of section 3.2 (Terminal Capabilities) were accepted for the implementer’s guide
and H.323 V3 but some additonal text is needed before it is given to the editors.
• The comments of section 3.3 (H.245 Logical Channel Signaling Procedures) were also
considered as part of the SUD/SET work.
• The comment of section 3.4 (Logical Channel Alternatives) were accepted for H.323 V3 and
H.245 V6; the delegates will review the text in detail. Solution (3) in section 3.4 (Extension of
the dataType parameter) was favored.
APC-1533 (Editor J. Toga, Intel) provides additions to the text of TD-60(PLEN) (approved
Geneva 9/98) for the H.323 Implementers Guide. This document was reviewed in detail. The
earlier sections related to remote device control were moved to H.323 V3 only. A number of other
changes were made as shown in TD-14. Note that TD-14 includes TD-13 changes (see above).
The section 8.2 “if required” language in TD-14 will be re-written. TD-33, Limitations of the
ipAddress type of Transport/Address in H.225.0 (Madge Networks, Ericsson), will be put into the
implementers guide while the change relating to the current section 7.6 firewall text will be
removed. Review is encouraged of this, and also of the proposed UDP port usage changes.
TD-10, Version numbers in GK routed calls (D. Lindbergh, PictureTel), notes and resolves a
problem related to gatekeeper-routed calls originating from H.225.0 V1 endpoints toward
H.225.0 V2 endpoints. If the GK sends its own H.225 version number (version 2) in the SETUP
message, the V2 endpoint will not fall back to V1 procedures. This change will be included in the
implementers guide and toward H.323 V3.
H.450.X IMPLEMENTERS G UIDE
APC-1506 (Siemens) proposes to add a statement to the H.323v2 Implementers Guide regarding
the setting of the H.255.0 elements CallIdentifier and ConferenceIdentifier in H.450.2 transferred
calls and in H.450.3 diverted calls. These changes were accepted for the implementers guide
with modification and a rule that conference IDs of existing conferences shall not be altered.
H.323 ANNEX E, CONNECTION OVER UDP
APC-1496 (Editor G. Kimchi, VocalTec) proposes editorial changes to the Determined H.323
Annex E text. These changes were accepted and will be submitted to the SG16 Decision meeting
as shown in draft form as TD-41 (entire text with change marks, TD-12 comprises the changes
only).
March-April 1999
27
APC-1507 (M. Duckworth, PictureTel) proposes minor changes to the text of H.323 Annex E to
avoid inconsistencies between Annex E and H.283 and H.225.0 Annex G. It was agreed to
remove the references to H.283 as proposed. It also was concluded that Annex E wire protocol
will not be used to carry Annex G messages.
H.323 ANNEX F, SIMPLE ENDPOINT TYPE
The meeting agreed to change “SUD” or Single Use Device to “SET”, Simple Endpoint Type.
APC-1523 (below) notes that single use implies disposable.
APC-1501 (Editor J. Ott, TELES) contains the H.323 Annex F White Paper submission for
Decision at the May SG16 meeting. It shows changes against the output of the Torino
(November) meeting.
In section 7.3.2.8, Function Not Understood should not be mandatory; indeed, it should not be
used. It was also noted that the samples/frame terminology was confusing. The 10 sample/frame
for GSM should be 1. Additional changes will be made relating to conference awareness. The
white paper submission will be corrected via TD-11.
APC-1502, Encoding of H.245 OpenLogicalChannel Structures for Single Use Devices (J. Ott,
TELES), contains packet formats for the OLC appendix.
APC-1503, H.323 Appendix “SUD Text,” Text Conversation Capable Single Use Device (G.
Hellström, PTS Sweden), describes a simple IP text telephone with real time simultaneous voice
and text conversation features. It was agreed that J. Ott would slightly modify the scope and
title of Annex F to better indicate that Annex F is a “core SUD” that can be referred to by other
SET annexes. It was agreed that APC-1503 would be the basis for the SET part of H.323 Annex
G “Text Conversation;”) See H.323 V3 Packet mode Video Telephony section, below). G.
Hellström will function as editor with J. Ott’s assistance.
APC-1523, Comments on H.323 Annex F (Mitel), identifies several areas of concern in H.323
Annex F. Section 1 (Interoperability) was partially addressed in TD-11. One unaddressed point
has been agreed as an open issue. Section 2 (Editorial comments) was added to TD-11 except for
the comment related to the interoperability table. Section 3 (disagreement with the name “SUD”)
was withdrawn, as it was agreed to change SUD to SET.
H.225.0 V3 ANNEX G (INTER -DOMAIN COMMUNICATIONS )
A well-known port for Annex G has been applied for with the IETF. J. Ott will manage this.
Based on TD-22 (Factors affecting the choice of transport for Annex G, A. Draper, Madge
Networks, VocalTec), it was agreed that Annex G would use TPKT (Transport Packet, T.123)
over UDP (User Datagram Protocol) and TCP (Transmission Control Protocol) rather than Annex
E.
APC-1510 (A. Draper, Madge Networks) suggests use of CryptoTokens in H.225.0 Annex G
messages. It was agreed that this is a good idea; this change is reflected in TD-20, Summary of
Comments on Annex G.
APC-1525 (Editor G. Freundlich, Lucent) is the draft H.225.0 Annex G white paper. APC-1526
(G. Freundlich, Lucent) provides H.225.0 Annex G Clarifications and Improvements. It was
agreed that these clarifications were editorial in nature and should appear at the May Decision
meeting as part of a rapporteur’s TD.
APC-1546 (Ascend, ITXC, Lucent, OzEmail, Siemens, VocalTec) proposes modifications to H.225
Annex G to support features (per-call authorization and routing, terminating end validation and
usage reporting) for placing calls between administrative domains. It was discussed, and it was
28
March-April 1999
noted that TD-20 contains some additional proposed changes. It is expected that this proposal
will appear at the May SG16 meeting via a national body.
APC-1551 (S. Sengodan, J. Rajahalme, Nokia) provides comments to Annex G. It was agreed to
replace the aliasAddress with a sequence of transport addresses. The proposed clarifying note
(“Where possible the responding BE shall use the Transport address.”) for the
ContactInformation was accepted. Other editorial corrections were accepted; some were rejected.
Several points are similar to those in APC-1526 and APC-1546.
O THER DRAFT RECOMMENDATIONS FOR DECISION
There were no submissions on the following draft Recommendations for Decision:
•
•
•
•
H.450.4
H.450.5
H.450.6
H.450.7
(Call Hold)
(Call Park and Call Pickup)
(Call Waiting)
(Message Waiting)
H.323 V3 PACKET M ODE VIDEO TELEPHONY
H.323 V3 is expected to be proposed for Determination at the May SG16 meeting.
APC-1492 and APC-1493 (R. Roy, AT&T) present H.323 Differentiated Services and their
protocol architectures. APC-1492 is text, and APC-1493 is a view graph presentation. These
contributions propose application level signaling of H.323 classes of services. The view was
expressed that TIPHON was looking into this area (see TR 101329 “Telecommunications and
Internet Protocol Harmonization over Networks” and also DTR/TIPHON 5002 “QoS Signaling”).
It was agreed to develop this work toward H.323 V3. Views were expressed that an OID (Object
Identifier)-based implementation be considered as well as that presented in APC-1492.
Contributions toward this are solicited for the May meeting. It was decided that changes to
Annex G were premature and would be considered again at the May meeting based on written
inputs.
TD-21, Enhancements to ITU-T Recommendation H.323 and its Annexes, H.225.0 and its
Annexes, and H.245 and its Annexes: Support of QoS (R. Roy, AT&T), notes that TIPHON TR
101329v1.3 (General Aspects of QoS) and TIPHON 11TD-123 (Requirements of an end-to-end
application, M. Buckley, Lucent) complement APC-1492.
APC-1498, H.323 QoS in the Policy Based Network (J. Maeng, VTEL, APC-1499 is the
presentation), identifies a need for a protocol between the gatekeeper and the policy server. It
was agreed to develop this work toward H.323 V3 and H.225.0 Annex G V2. This work may
also include consideration of how to best make use of various IETF policy-related work; it may be
that making use of such IETF policy protocols is the most appropriate way forward; this will be
considered as part of the work. Contributions are solicited.
APC-1503, H.323 Appendix “SUD Text,” Text Conversation Capable Single Use Device (G.
Hellström, PTS Sweden), was again discussed (see above, under Annex F for Decision). The
Annex F Editor, J. Ott, was charged with developing a method of managing various SUD-type
terminals, including the proposed Text SUD. This Annex, which will be H.323 Annex G, will
refer to H.323 Annex F, treating Annex F as a template and only specifying additions. The name
will now be SET rather than SUD. The general text conversation Annex and the SUD (now SET)
Text terminal Annex will be the same annex.
APC-1504, H.323 Text Conversation (G. Hellström, PTS Sweden; TD-19 is the presentation), is
a proposal for a new Annex to H.323 to include a general add-on to H.323 functionality for text
conversation. Contributions are solicited toward May 1999 Determination. G. Hellström was
named editor.
March-April 1999
29
APC-1524, Improving H.245 Channel Opening After Media Pause (P. Cordell, M. Nilsson, BT; D.
Walker, Mitel), proposes an H.245 Annex for describing the use of pre-opened channels to reduce
the establishment time of H.245 logical channels. The delegates noted this as an interesting
proposal that demonstrates the power of the H.245 generic capabilities. An alternative of using a
modified FAST START OLC was suggested as described in APC-1522 (above). It was noted that
these ideas are very important and have a bearing on Annex F (SETs). This issue remains open
and may result in a contribution through a national process.
APC-1527, Caller ID Support (G. Freundlich, Lucent), proposes modifications to H.225.0 and
H.323 to support Caller ID features. It includes modifying H.225.0 V2 via the implementers
guide to allow the transit of previously forbidden presentation information, and also to add
similar information for non-E.164 identifiers in H.323 V3. This document was accepted as
proposed; delegates are STRONGLY WARNED that part of this is a correction of a past error
that might potentially affect some existing implementations. Text will be added to both the
implementers guide and to draft H.323 V3.
APC-1528 (G. Freundlich, Lucent) proposes specification of four Name Identification features
(calling party name presentation, calling party name restriction, connected party name
presentation, busy party name presentation) for H.323 systems. It was adopted (with some
changes), and will be standardized as an H.450.x supplementary service, with Determination
proposed in May 1999.
APC-1543, Indication of H.323 Annex E capabilities to gatekeeper (E. Skjaeran, LM Ericsson),
optimizes for the GK-routed call model; the current method is optimized for the direct call model.
Concerns were raised about interoperability between zones where Annex E is supported to where
Annex E is not supported. It was agreed that this proposal has merit, but must be considered in
the larger context with Annex F. This proposal was accepted toward V3. It was also agreed
that signaling of transport and signaling of protocol support are separate items.
It was agreed to add appropriate warnings and text/ASN.1 in TD-46, Include endpointIdentifier
in SETUP message (W. Eriksen, LM Ericsson), to the implementers guide; the mandatory use of
this feature would only begin in H.323 V3.
TD-36, Changes to H.323 to support operation via basic NAT (Network Address Translation)
devices (Madge Networks, VocalTec), was considered briefly and will be brought to the next
meeting for possible inclusion in H.323 V3. Due to IPv4 address exhaustion, many networks are
deploying simple NAT devices. Such devices allow the same IP address to be used in two
separate IP networks connected by a NAT device. Some NAT devices examine both the headers
and the payload of a TCP/IP or UDP/IP packet and substitute IP addresses wherever they are
found. However there are many NAT devices that examine and modify only the packet header.
This document examines the changes to H.323 to allow it to communicate through these NAT
devices. The issue of firewalls was recognized as important.
APC-1553, H.323 Changes for multi-point support (R. Even, Accord), will be adopted toward
H.323 V3.
TD-18 is a liaison from TIPHON on ringing tone issues. TIPHON has a need for tones and
announcements to be provided on calls originated in the SCN and terminating in the IP network,
and vice versa. If ringing tone needs to be provided by the IP network, a mechanism is needed to
ensure that some entity within the IP network actually provides the tone. TIPHON would like
SG16 to examine the problem and provide some solution. It was agreed that this TD presented a
real problem but needs more work, including consideration of the direct call model. Contributions
are solicited for the May meeting, but it was agreed that this must be resolved as part of the
H.323 V3 work and/or in H.246.
30
March-April 1999
INTRA -DOMAIN COMMUNICATION
APC-1535 (Siemens) proposes the need for services and procedures for charging, accounting, and
advice of charge in H.323. It was agreed that billing is clearly out of the scope of this work. It
was agreed that this topic is very related to signaling for QoS. The priorities presented were not
agreed, but it was agreed that this was a valuable contribution and that it should be considered
as input to H.323 V3 and H.450.x. Contributions are solicited.
APC-1541, (E. Skjaeran, LM Ericsson), proposes a new call signaling address parameter to be
added to the RAS GatekeeperConfirm message for inter-GK discovery. It was not accepted at
this time, but will be developed further by the author.
APC-1540, Adding Pricing information to terminals in call (E. Skjaeran, LM Ericsson), proposes
to provide an indication of the call’s price in the Admission Confirm RAS message, and to return
to the user the total price of the call in the Disengage Confirm RAS message. A vigorous
discussion ensued; it was agreed that this should be developed further toward H.323 V3. A
suggestion was that AccessRequest should be used rather than LRQ as it had more information.
It was noted that the GK routed path may not be the cost generating path. Contributions are
solicited that consider:
• Both direct and GK-routed call models
• MultiMedia
• A general GK-GK scheme.
• Annex G multi-domain interactions
• Interactions with the SCN
H.323 ANNEX C (ATM) V2 & ATM RELATED M ATTERS
H.323 V3 Annex C V2 is planned for Determination at the May SG16 meeting.
APC-1516©, Gateway for H.323 Media Transport over ATM (F. Audet, Nortel Networks, for
ATMF), is the baseline text for the RMOA (Realtime Multimedia Over ATM - ATM Forum)
H.323 Media Transport over ATM specification (STR-SAA-RMOA-01.00). The proposed plan is
to refer to this document in a normative fashion in H.323 V3. A communication of technical
comments to the ATM Forum will be prepared, addressing, among other things, section 4.5 for
H.323 Annex C interworking, in which a number of difficulties were pointed out. A number of
delegates called for seamless interworking with H.323 Annex C terminals.
Some concerns were raised about the ATMF Annex B terminal that appears to be defined, and
how it would interwork with other H.323 terminals. Delegates were urged to consider carefully
any issues raised by the ATMF Annex B.
TD-35 is the liaison from Q12-14/16 to the ATM Forum. It notes that the current text in
4.5/STR-SAA-ROMA-01.00 (APC-1516©) is not very clear on how compatibility with
H.323/Annex C is maintained and proposes replacement text. This liaison also proposes that one
codepoint with a parameter should be used instead of two codepoints, to indicate RTP header
compression, with a fixed or variable length delta field. Replacement text for 4.6 (H.245
transport capabilities is also offered. This response is based on the liaison APC-1517 from the
ATM Forum (F. Audet, Nortel) which contains the request (to Q13/16) for H.245 codepoints to
support APC-1516. See also Q14/16 report, below.
APC-1518, GIT for transporting the portNumber (F. Audet, Nortel Networks), is a proposed
liaison to SG11 to request a GIT (Generic Identifier Transport) information element (in Q.2941.1),
as had been previously suggested, instead of the B-HLI (Broadband-High Layer Information)
information element in H.323. The agreed version is TD-50.
APC-1532, Consideration for MPEG-2 stream packetization (S. Okubo, TAO), discusses the
available packetization methods of MPEG-2 audio, video, and system streams. Three methods
were presented: (1) separate audio and video as per RFC2250, (2) bundled audio and video as per
March-April 1999
31
RFC2343, and (3) audio and video in an MPEG-2 TS packet. Based on the discussion at the
meeting, (1) and (3) appear to the leading candidates. The intention of the rapporteur is to
standardize this as part of H.225.0 V3, with Determination in May 1999, if possible.
Contributions are solicited.
H.323 ANNEX D
H.323 Annex D is expected to be proposed for Determination at the May SG16 meeting.
TD-28 is a liaison from Q4/8 requesting information on possible difficulties that firewalls will
impose on T.38 Annex B devices. TD-29 is a copy of the revised Annex B to Rec. T.38 (call
establishment procedures for facsimile communications over IP networks). TD-39 (draft return
liaison to Q4/8), notes that T.38 does both Call Signaling and T.38 via well-known port(s) which
simplifies the configuration of firewall types that use Packet Filtering (Stateless Inspection).
Convincing system administrators to properly configure their Packet Filtering firewalls is
another matter. Also many firewalls use Stateful Inspection or Application Level Gateway; these
require application level knowledge. This means that T.38 Annex B firewalls have to be deployed
to let T.38 Annex B traffic through. The approved liaison is contained in Annex 6 to APC-1554,
the meeting report.
H.225.0 V3 MULTIPLEXER
H.225.0 V3 is expected to be proposed for Determination at the May SG16 meeting.
APC-1544© (Editor G. Freundlich, Lucent) is Draft H.225.0 V3. The editor reviewed the
changes to H.225.0 for Version 3.
TD-40, Comments on APC-1544 (OzEmail), proposes to add the language identifier element to
the ACF message (AdmissionConfirm) so that this information may be obtained from the
gatekeeper. It was accepted toward H.323 V3/H.225.0 V3.
APC-1491, GSM Audio Packetization in H.323 (H. Mäenpää, Nokia), shows how RTP
packetization and the standard GSM codecs should be used together. It was agreed to include
this in H.225.0 V3. The delegates were encouraged to work in the IETF to ensure that the RFC
for GSM is aligned with this work, and with that of ETSI.
APC-1542, Extending the pre-granted ARQ (E. Skjaeran, LM Ericsson), fixes two shortcomings
of the pre-granted ARQ in H.225.0. The shortcomings are: There is no bandwidth agreement
between the terminal and its gatekeeper. The terminal cannot be instructed to send unsolicited
IRR messages in a call. This proposal was adopted toward H.225.0 V3. The IRR change, to
indicate the frequency in seconds of IRR messages sent to the gatekeeper when the endpoint is in
one or more calls, will also go in the implementers guide.
H.450.8
APC-1505 (Editor M. Korpi, Siemens) is a draft of Rec. H.450.89, Conference out of Consultation
Supplementary Service for H.323.
TD-26 comprises comments on H.450.8 from IBM, DataBeam and Madge Networks. The main
concern is that the two different ways of doing conferencing (H.323 Section 8.4.3 and H.450.8)
differ only marginally. It recommends including the H.450.8 material in H.323 V3, and where
appropriate, in the related versions of H.225.0 and H.245. It was agreed that the advocates of
TD-26 would bring into the May SG16 meeting a complete proposal for fixing the current
conferencing method in H.225.0 V3 as appropriate. The meeting agreed in principle that such
fixes are desirable. Although TD-26 argues that H.450.8 (APC-1505) is not strongly needed,
several voices expressed support for H.450.8. The rapporteur requested that the advocates of
H.450.8 develop a clearer case for the value added by this feature relative to the existing method.
In any case, H.450.8 can be used optionally in addition to the current method. A final decision on
32
March-April 1999
H.450.8 will be taken at the May meeting. A view was expressed that further development of the
H.245/H.225.0 conferencing methods would be desirable.
H.332 V2, A TOPIC FOR FUTURE W ORK
APC-1519 (S. G. Kim, Korea Telecom) proposes a Dynamic Multicast Tree Building Procedure
for H.332 (H.323 Extended for Loosely-Coupled Conferences). After the presentation, views were
expressed that:
• The products in which these ideas might be used were unclear
• These ideas should be submitted to the IETF multicast lists
• There was no clear need for a hierarchy of multi-uni cast trees. To a large extent, this need is
fulfilled by cascaded MCUs.
Q13/16 WORK P LAN
The status of recommendations in Q13/16 is shown in Table 2.
Recommendation
May 1999 Decision
H.323 Annex E (Call Connection over UDP)
H.323 Annex F (Single Use Terminal)
H.225.0 Annex G (Communication between
Administrative Domains)
H.225.0 Annex I (H.263+ Packetization)
H.450.4 (Call Hold)
H.450.5 (Call Park/Pickup)
H.450.6 (Call Waiting)
H.450.7 (Message Waiting)
February 2000 Decision
H.450.8 (Conference out of Consultation)
H.450.9 (Call Completion on Busy
Subscriber)
H.323 V3 (Packet Mode Video Telephony)
Det.
Dec.
Editor
9/98
9/98
9/98
5/99
5/99
5/99
G. Kimchi (VocalTec)
J. Ott (TELES)
L. Moscovici (VocalTec)
9/98
9/98
9/98
9/98
9/98
5/99
5/99
5/99
5/99
5/99
G. Freundlich (Lucent)
M. Korpi (Siemens)
M. Korpi (Siemens)
M. Korpi (Siemens)
D. Walker (Mitel)
5/99
??
2/00
??
M. Korpi (Siemens)
(looking for editor)
5/99
2/00
H.225.0 V3 (Multiplexer)
H.323 Annex G (Text Communication in
H.323 & Text SETs)
H.450.10 (Name Identification Services)
5/99
5/99
2/00
2/00
G. Thom (Delta Information
Systems)
G. Hellström (PTS, Sweden)
5/99
2/00
Table 2. Status of Recommendations in Q13/16.
Q14/16, COMMON PROTOCOLS, MCUS AND PROTOCOLS FOR INTERWORKING WITH
H.300-SERIES TERMINALS
H.283 REAL-TIME DEVICE CONTROL
H.283 Real-Time Device Control, was Determined in September 1998. APC-1507, Fixing
Inconsistency between H.323 Annex E and H.283 and H.225.0 Annex G (M. Duckworth,
PictureTel), proposes minor changes to the text of H.323 Annex E to avoid inconsistencies
between Annex E and H.283 and H.225.0 Annex G. It was agreed to remove the references to
H.283 as proposed in APC-1507.
TD-27 (Editor M. Duckworth, PictureTel) proposes minor changes to the H.283 white draft.
They were accepted and will be brought into the May meeting as a rapporteur’s TD.
March-April 1999
33
H.341 MULTIMEDIA M ANAGEMENT INFORMATION BASE
APC-1495 (Editor G. Kajos, VideoServer) proposes changes to the Determined H.341 Annexes to
support multiple instances, clean up syntax, adding comments, and fixing compilation problems.
The proposed changes were accepted in total.
APC-1513, Extension Proposals for Gateway MIB of H.341 (P. Wang, Ascend), proposes three
extensions for the gateway MIB of H.323:
1. Support a new type of H.323 entity: H.323-to-H.323 gateway.
2. Add additional index to support multiple instances of the gateway within same interface.
3. Introduce a cross-reference connection table to facilitate lookup from connection’s endpoint
address.
Item 1 is targeted for H.341 V2. H.341 Editor G. Kajos (VideoServer) believes the current
H.341 with changes from APC-1495 can support item 2, but will add text to H.341 to state that
an H.323-H.323 gateway is in H.341’s scope. G. Kajos was opposed to Item 3 because it is an
optimization for a particular architecture and the existing mechanism is sufficient. Items 2 and 3
were not accepted.
APC-1548, Suggested Changes to H.341 (R. Seiler, PictureTel, on behalf of IMTC), proposes
changes to definitions and a new MIB code based on studies of failed video calls over the past
year. Questions were raised about the proposed definitions which will require some clarification.
D. Lindbergh (PictureTel) will work with IMTC to get these clarifications, with the expectation
that they will appear in a submission to the next SG16 meeting.
H.235 H.323 SECURITY
APC-1533 (Editor J. Toga, Intel) proposes text for the H.323 Implementers Guide. Section 7.5
proposes two corrections to H.235. The first correction, to the comment to include the password
in the ClearToken, was accepted for inclusion into the implementer’s guide. The second correction
was not accepted, since this changes the ASN.1 that was approved in the implementer’s guide at
the September 1998 SG16 meeting. Notification needs to be sent to the implementer’s list.
Editor J. Toga should verify that the implementer’s guide from the September meeting showed
the tokenOID (Object Identifier) at the top of the structure. If this is the case, then the current
implementer’s guide should revert back to the document after the September meeting.
APC-1552, Token OID for Crypto Tokens (L. Moscovici, VocalTec), presents the problem of
populating the tokenOID field in the clear version of the CryptoToken and CryptoH323Token
structures, and proposes to have fixed value for specific-purpose tokens, and to copy the
tokenOID from the outer (clear) part of the crypto token for the general purpose token. For the
first issue of making both tokenOIDs identical, there seemed to be disagreement on the best
approach. The proposal in TD-43, Token OID for Crypto Tokens (Madge, VocalTec), was
accepted. The tokenOID in the specific H323CryptoTokens will be {itu-t (0)}.
G ATEWAY PROTOCOLS AND H.GCP
To achieve greater scalability, H.gcp decomposes the H.323 gateway function defined in H.246
into functional sub-components and specifies protocols these sub-components use to communicate.
This allows implementations of H.323 gateways to be highly scalable and encourages leverage of
widely deployed SCN network capabilities such as SS7 switches. Multiple vendors may also
produce the different gateway sub-components.
APC-1514, Comparison of Tunneling and Interworking (R. Callaghan, Siemens), discusses
implementations using tunnels of the external protocol versus an implementation that interworks
the external protocol to native H.323 with H.450 services. It does not recommend one approach
over another, but suggests some advantages and disadvantages of each. Among the issues:
34
March-April 1999
• Mixing may be a good compromise, but could be dangerous for supplementary services
operations
• If a protocol is tunneled, there may be a need to modify contents of elements in tunnel (for
example, an 800 number might be resolved but would need to be changed in the tunneled
message)
• Need to avoid remapping between protocols (e.g., don’t let ISUP network modify QSIG
signaling)
• When tunneling, functionality of previous network may be lost
APC-1515, H.450.x - Tunnel Transport of SCN Signaling Protocols (R. Callaghan, Siemens),
proposes using an H.450 supplementary service for tunneling. This proposal seems to align with
GIT work in SG13 (SG13 works on architecture for transport of foreign networks, and has asked
others to conform). An advantage to this approach is the ability to indicate the interpretation a
node should take (e.g., ignore if can’t read). Concerns were stated regarding performance
problems with additional ASN.1 encode/decode, ability to work with pre-granted admission, and
proposed rules for gatekeeper involvement. This was discussed in general with other tunneling
proposals, APC-1531, APC-1534, and APC-1538.
APC-1531, ISUP-Based Signaling for H.225 Control (R. J. Abrams, Lucent), attempts to
optimize ISUP tunneling. There were concerns that this proposal introduces a new protocol
which appears to be outside the scope of H.323. Other concerns were that this proposal does not
support multimedia, ISUP should not be central to H.323, and that there is a need for some
method for transporting private/public network things transparently. There should be a method
that works for all protocols.
APC-1534, Generic Mechanism for SS7 Transport in H.323-based networks (C. Groves,
Ericsson), proposes schemes for transport of generic SS7 (not limited to ISUP). It suggests a
short term approach of using codeset 6 in H.225.0 to carry ISUP information, and a longer term
approach using Annex E or CTP (from IETF Sigtran) as a tunneling mechanism. The need for
interworking is discussed.
APC-1538, Requirements For Tunneling of ISUP and Other Protocols (T. Taylor, Nortel
Networks), suggests some requirements to support tunneling. Among the issues raised were:
• How to achieve service interworking for different levels
• There appears to be a need to support tunneling of some kind
• Providers are interested in more elaborate service interworking
During later discussions, it was determined that an annex to H.246 is needed to define
interworking between ISUP and H.323, similar to Q.699 which defines interworking between
ISUP and Q.931. This annex should identify services that are supported. Tunneling is
interesting but there exists no consensus at this time. Proposals are encouraged in this area.
APC-1497©, Requirements for a Protocol at Reference Point N: Media Gateway Controller to
Media Gateway (ETSI TIPHON), is a copy of DTS-02005 V0.1.1. It was noted that the
requirements listed in H.GCP are based on an earlier version of the TIPHON requirements.
These newer requirements will be considered in H.GCP. Figure 1 below is from this document. It
shows a basic call reference configuration.
March-April 1999
35
D
GK
GK
G
Back
End
A
C
H.323
Media GW
Terminal
Controller
B
F
J
Signalling
E.b
GW
N
Media GW
E.a
Figure 1: Basic call reference configuration, taken from DTS-02005 V0.1.1.
APC-1547 (T. Taylor, IETF Megaco) is the latest draft of the Media Gateway Control Protocol
Architecture and Requirements document from IETF Megaco working group. TD-16 is the slide
presentation, summarizing the requirements. These requirements will be considered in H.GCP.
It became apparent that terminology used by various interested groups differs and carries some
baggage, so it is suggested that H.GCP create new definitions for the various elements.
APC-1537, Requirements Across the B, C, and D Interfaces of a Decomposed Gateway (T.
Taylor, Nortel Networks), notes that in general, these interfaces must support the transfer of call
signaling information, and that each is a component of end-to-end call signaling paths. Discussion
noted that it is hard to define A without understanding B, C, and D. B, C, and A should be
addressed together, but it should also be possible to separate them. This could mean they have
the same transport (possibly same messages), or do they need to be defined simultaneously?
Could be that these are carried in something like Annex E; the important thing is that they are
defined together. Billing protocols also need some more work.
There was debate that the requirements should be completed and adopted by this group before
proceeding on the actual protocol definitions. The procedure to this point has been to develop the
requirements and protocol in parallel. TD-24 is a draft scope of H.GCP from an ad hoc group.
The ad hoc group took into consideration the requirements documents presented in this meeting
(APC-1529, MDCP from Lucent, and APC-1550, MGCP from Bellcore and the IETF, see
additional discussion below) and the original terms of reference formed during the September
1998 SG16 meeting.
It was also noted that TR-41.5 is addressing residential gateways (see report in this issue of
CSR).
APC-1545, Internal Connection Model for Generic Media Gateways (P. Sijben, Lucent), proposes
an internal connection model for use in a decomposed gateway (or any gateway), with the intent
that this can help in the definition of H.GCP.
36
March-April 1999
APC-1500 (Editor B. Hill, VideoServer) is a draft of H.GCP, Gateway Control Protocol. After
lengthy discussion about the basis for creation of this draft, the group began to review the
requirements. Some of the many comments were:
• Resource management needs more specific definition; ability to report on availability of
resources is a requirement; does not exclude other means of resource management
• Control session management - availability and reliability of control
• General design goals - scalability is essence of protocol style - it’s a low level control interface,
so message processing efficiency is critical
• Connection control - circuit to packet - ATM should mean circuit ATM and not IP over ATM;
change circuit side “fallback” to “loopback”; keep in mind that ATM can be circuit or packet;
• A interface shall be able to establish and control signaling interfaces B & C if B & C are
supported
• Protocol abstracts the things it acts on (so can also support wireless, etc.)
Editor B. Hill was tasked to update the requirements based on input from TIPHON and IETF
Megaco. The entire APC-1500 was not reviewed in detail, only the requirements and the
connection model.
APC-1529, Media Device Control Protocol (MDCP) (P. Sijben, Lucent), and APC-1550, Media
Gateway Control Protocol (MGCP) (H. Liu, Bellcore), are two protocols proposed to address the
terms of reference for gateway decomposition. The proposals were presented; lengthy discussions
and debate followed. Both proposals have a number of similarities, but the significant differences
seem to include:
• Connection model (these are compared in TD-25, R. Coldren, Lucent)
• PDU encoding scheme
• Use of SDP to describe media stream aspects
After lengthy meetings, there appeared to be no compromise between the connection models in the
two proposals. In order to identify some direction for H.GCP, an indicative poll was held to select
a connection model to use in drafting H.GCP. This poll was held according to guidelines
described in the SG16 Rapporteurs Manual (TD-47), with one tally allowed per company and
passed to S. Okubo so that no representative revealed their position on this issue. S. Okubo
figured the results, which are shown below (and in TD-48):
Voters:
3Com, Accord, Ascend, AT&T, Bell Atlantic, Bellcore, Cisco, DataBeam, Dialogic,
Ericsson, France Telecom, Intel, KPN Research, Lucent, Madge Networks, Mitel, Motorola,
Nokia, Nortel, NTT, OzEmail, PictureTel, Siemens, Sun, TELES, Texas Instruments,
VideoServer, VocalTec
Total number of votes:
Endpoint model as used in MGCP
Edgepoint model as used in MDCP
Abstain:
Others:
28
6
16
5
1 (investigate WAP architecture)
Considering the above results, the rapporteur directed Editor B. Hill to draft H.GCP using the
edgepoint model of MDCP for guidance where applicable. A protocol will be drafted that reflects
that model. However, B. Hill should feel free to use ideas from all proposals. It should be noted
here that creation of Recommendations is driven by contribution, and contributions that help
progress H.GCP are encouraged. This includes proposals to utilize a different connection model,
such as WAP (Wireless Application Protocol see http://www.wapforum.com/), which was
mentioned as an alternative.
H.245 V6
APC-1517, H.245 Codepoint for Transport of Compressed RTP over AAL5 (F. Audet, Nortel
Networks, on behalf of ATMF), contains a request for H.245 codepoints to support APC-1516©,
March-April 1999
37
Gateway for H.323 Media Transport over ATM (F. Audet, Nortel Networks, for ATMF). There
was some concern about the structure of the definition, which was addressed in TD-35 (liaison to
ATMF). The definition in TD-35 contains a definition of BOOLEAN OPTIONAL, but the
OPTIONAL is unnecessary. The new definition will be added to H.245 V6. See also Q13/16
report, above.
APC-1522, Additions to the H.323 Implementers Guide (D. Walker, Mitel), was discussed during
Q13/16 (see Q13 above under H.323 Implementers Guide). Section 3.4 solution 3 will be added
into H.245 V6.
6.5 PLANS FOR FUTURE W ORK
Table 3 presents the status of recommendations in Q14/16.
Recommendation
H.245 V5
H.245 V6
H.246 Annex C (ISUP-H.225.0 Interworking)
H.283
H.341
H.341 V2
H.GCP
H.243
Det.
9/98
5/99
5/99
9/98
9/98
5/99
5/99
5/99
Dec.
5/99
2/00
2/00
5/99
5/99
2/00
2/00
2/00
Editor
M. Nilsson (BT Labs)
M. Nilsson (BT Labs)
C. Groves (Ericsson)
M. Duckworth (PictureTel)
G. Kajos (VideoServer)
G. Kajos (VideoServer)
B. Hill (VideoServer)
P. Luthi (PictureTel)
Table 3. The status of recommendations in Q14/16.
Q11-14/16 RAPPORTEURS MEETING ROSTER, FEBRUARY 15 - 19, 1999, MONTEREY, CA
Tom Geary, Conexant
Sakae Okubo , TAO Japan
Dale Skran, Ascend
Glen Freundlich, Lucent
Gary Sullivan, PictureTel
Host: IMTC
Country
Australia
Australia
Finland
Finland
Finland
Finland
Finland
Finland
Finland
France
France
France
Germany
Germany
Germany
Germany
Germany
Germany
Germany
Germany
Israel
Israel
38
Q11/16
Q12/16
Q13/16
Q14/16
Q15/16
Company name
Ericsson
OzEmail Interline
Helsinki Telephone Corporation
Nokia
Nokia
Nokia
Nokia
Nokia
Tecnomen
Alcatel
France Télécom
France Télécom
Bosch
Deutsche Telekom Berkom
Siemens
Siemens
Siemens
Siemens
Teles AG
Uni Erlangen
Accord Video Telecommunication
VocalTec Communications Ltd.
Rapporteur
Rapporteur
Rapporteur
Rapporteur
Rapporteur
Last,First
Groves, Christian
Clowes, Douglas
Backstrom, Markus
Karczewicz, Marta
Lainema, Jani
Luomi, Marko
Muaenpaa, Henri
Rissanen, Pekka
Kemppainen, Vesa
Mobasser, Bahman
Blin, Jean-Pierre
Boissonade, Patrick
Vollemer, Jens
List, Peter
Klaghofer, Karl
Korpi, Juha
Sebestyen, Istvan
Wimmer, Bernhard
Ott, Jörg
Wiegand, Thomas
Even, Roni
Kimchi, Gur
E-mail address
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
N/A
[email protected]
[email protected]
March-April 1999
Israel
Israel
Italy
Japan
Japan
Japan
Japan
Japan
AETHRA
KDD R&D Laboratories Inc.
Mobile Communications Network, Inc
NEC Corporation
NTT Corporation
Telecommunications Advancement
Organization of Japan
Japan
Toshiba Corporation
Japan
Toshiba Corporation
Netherlands KPN Research
Norway
Telenor Satellite
Norway
Telenor Satellite
R.O.Korea
KAIST
R.O.Korea
LG Electronics
R.O.Korea
LG Electronics
R.O.Korea
LG Electronics
Sweden
Ericsson
Sweden
Ericsson
Sweden
Ericsson
Sweden
Ericsson
Sweden
Ericsson
Sweden
Swedish Post and Telecom Agency
Taiwan
Industrial Tech. Research Institute
U.K.
BT
U.K.
FHTW Berlin
U.K.
Inmarsat
U.K.
Lucent Technologies
U.K.
Lucent Technologies
U.K.
Madge Networks Ltd.
U.K.
Madge Networks Ltd.
U.K.
Motorola
U.K.
University of Strathclyde
U.S.A.
3Com Corporation
U.S.A.
3Com Corporation
U.S.A.
8x8, Inc.
U.S.A.
8x8, Inc.
U.S.A.
8x8, Inc.
U.S.A.
ADC Telecommunications, Inc.
U.S.A.
AirTouch
U.S.A.
Ascend Communications
U.S.A.
AT&T
U.S.A.
AT&T
U.S.A.
Bell Atlantic
U.S.A.
Bellcore
U.S.A.
Bellcore
U.S.A.
Cisco Systems, Inc.
U.S.A.
Conexant
U.S.A.
DataBeam Corporation
U.S.A.
DataBeam Corporation
U.S.A.
Delta Information Systems, Inc.
U.S.A.
Delta Information Systems, Inc.
U.S.A.
Dialogic Corporation
U.S.A.
DiviCom Inc.
U.S.A.
ECI Telecom (Israeli Ministry of
Communication)
U.S.A.
Ericsson
U.S.A.
GRIC Communications
U.S.A.
Hitachi America, Ltd.
U.S.A.
Intel Corporation
U.S.A.
Intel Corporation
U.S.A.
Intel Corporation
U.S.A.
Intel Corporation
March-April 1999
Michaely, Boaz
Moskovichi, Lior
Flaiani, Roberto
Yamada, Hideaki
Suzuki, Takashi
Harasaki, Hidenobu
Seki, Ichiro
Okubo, Sakae
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Minami, Shigenobu
Tanaka, Hirokazu
Muijnck, Jeroen De
Bjontegaard, Gisle
Langoy, Inge Lille
Lee, Yung-Lyul
Hong, Min-Cheol
Jeong, Yeong-An
Kim, Chul-Woo
Burman, Bo
Holm, Jan
Nasiri, Mickey
Roth, Goran
Sjoberg, Rickard
Hellström, Gunnar
Lin, Ming-Feng
Nilsson, Mike
Cycon, Hans
Chrisodoulides, Louis
Buckley, Mike
Eryurtlu, Faruk
Draper, Andrew
Purvis, Chris
Guram, Paul
Fryer, Richard J
Dalgic, Ismail
Fang, Hanlin
Andrews, Barry
Bryant, Stephane
Singh, Hardish
Noah, Matt
Jaques, Eric
Skran, Dale
Haskell, Barry G
Roy, Radhika R
Hopkins, Katrina C
Hapeman, Raymond
Liu, Hong
Bowen, Rich
Geary, Tom
Jones, Paul
Starky, Neil
Thom, Gary
Urban, Stephen
Magnell, Steven
Shen, Ke
Dragiff, Matthew A
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
eryurtlu@lucent com
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Eriksen, Werner
Leckner, Erik
Lu, Naiqian
Bhasker, Narjala
Elgebaly, Hani
Gardos, Tom
Kumer, Vineet
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
39
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
U.S.A.
40
Intel Corporation
ITXC
Lucent Technologies
Lucent Technologies
Lucent Technologies
Lucent Technologies
Lucent Technologies
Microsoft Corporation
Microsoft Corporation
Mitel
Motorola
Motorola
NetSpeak
Nokia
Nortel Networks
Nortel Networks
NTT Corporation
PictureTel Corporation
Polycom
Real Networks, Inc.
Samsung
Samsung
Sharp Labs of America
Siemens
Siemens
Siemens
Sorenson Vision, Inc.
Sun Microsystems Inc.
Tekelec
Telogy Networks
Texas Instruments
Texas Instruments
Toshiba Corporation
Trillium Digital Systems, Inc.
UBC
UCLA
UCLA
UCLA
University of Southern California
University of Wisconsin
University of Wisconsin
VideoServer
VideoServer
VTEL
Lillevold, Karl O
Yu, Jim
Abrams, Robert J
Coldren, Rex
Freundlich, Glen
Gal, Dan
Orsic, Milo
Deshpande, Neeta
Morris, Max
Walker, Dave
Martinez, Edgar
O'connell, Kevin
Kelly, Keith C
Sengodan, Senthil
Audet, François
Taylor, Tom
Doyama, Shinichi
Duckworth, Mark
Lindbergh, Dave
Luthi, Patrick
Sullivan, Gary
Collier, Matthew
Greenbaum, Gary S
Park, Dong Seek
Park, Jeong Hoon
Ribas, Jordi
Callaghan, Robert
Korpi, Markku
Wuerful, Randy
Huang, Chien-Min
Yeh, Jenn
Long, Virgil
Spitzer, Roy
Budagavi, Madhukar
Nandakumar, Anand K
Aronson, Barry
Patwardhan, Rajesh
Gallant, Michael
Luttrell, Max
Tisserand, Matthieu
Villasenor, John
Kim, Jong Won
Kittitornkun, Surin
Li, Adam
Hill, Bryan
Kajos, George
Baskin, Elaine
Krechmer, Ken
Maeng, Joon
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
March-April 1999
REPORT OF TR-41, USER PREMISES TELECOM EQUIPMENT
FEBRUARY 15 - 19, 1999, SARASOTA, FL
TR-41.1, MULTI-LINE TELECOMMUNICATION SYSTEMS
T. Tung (Siemens) is the interim chair of TR-41.1, as the previous chair, J. Schick (Nortel) has
retired. In accordance with TIA procedures, the chair asked if there is any knowledge of patents,
the use of which may be essential to any standards being considered. There were no replies by
attendees.
PN-4157, BRI LINE -SIDE INTERFACE REQUIREMENTS
All members active on PN-4157, BRI Line-Side Interface Requirements, stated that due to their
respective companies’ work interests, they no longer have sufficient resources to work this issue.
Also, given the advent of the new IP Telephony standards work, ISDN BRI telephones no longer
seem to be of interest to the marketplace. There have been no new technical contributions on this
topic at the previous two meetings. The chair called for a vote to cancel this topic; it was
canceled without any protest.
PN-4422, QSIG INTEROPERABILITY TEST
TR-41.1/99-02-08, QSIG Interoperability Test Plan for North America (Lucent Technologies), is a
cleanup effort to the previous version that was issued in November (TR-41.1/98-11-027). TR41.1/99-02-10, Proposed Additions and Changes to Draft QSIG Interoperability Test Plan
(Cortelco Systems), includes a cross-reference between the ISO QSIG PICSs (Protocol
Implementation Conformance Statement) and the test cases in the plan. The existing PICSs
questionnaires from the QSIG standards are to be used by the vendor community to refer to this
cross-reference which will list all the necessary test cases to verify the PICSs statement.
When looking at TR-41.1/99-02-10, the test case numbers at this point will need to be referred
back to TR-41.1/98-11-027, which was the first issue of this document and the basis of the crossreference in TR-41.1/99-02-10.
Specific comments and open issues are included in TR-41.1/99-02-10. There may need to be
specific extensions to the PICSs to cover items that pertain to implementation details, e.g.,
invocation of Path Replacement.
There was a question about the B-channel negotiation test cases. The issues revolve around two
items: 1) Is the acceptance of the channel encoding mandatory? and 2) Do we need to support BChannel Negotiation according to the QSIG standards?
There was a discussion on the need for a regression testing cross-reference that talks about how
to re-verify some basic elements of interoperability when vendors come together for testing at a
subsequent testing event to test new features.
During the discussion, it became clear that there are three layers to testing at subsequent testing
events: 1) Basic Regression, 2) Some test cases based upon what is to be newly added (what the
new feature could have impacted), and 3) Rigorous testing of the new feature.
Items on the issues list (TR-41.1/99-02-13) include:
• Test house not looked into
• Functionality testing (ok procedure)
• Protocol level testing should not be specified and left up to the vendors
• Feature/Feature interaction? Supplementary Services /ANF (Additional Network Features)
need to be clear as to what is the baseline for the testing. Working Group will look into the
particular level of testing.
• Move table of contents to the front
• Consistent numbering
March-April 1999
41
A conference call will be setup to discuss the Feature/Feature testing and the B-Channel
negotiation issues.
TSB-32-A
TSB-32-A, Overall Transmission Plan Aspects for Telephony in a Private Network, has been
published; copies are available from Global Engineering.
The North American Scenario Companion Document for TSB-32 is still outstanding. R. Britt
(Nortel) and a colleague have found a number of small errors that require them to rerun the
models; no significant changes in the results are expected. R. Britt plans to rerun the models in
April and provide a ready-for-print version in May. T. Tung (Siemens) mentioned that this
companion document has been pointed to by ETSI.
The PINS form for this project was approved by TIA. The Project submission calls for this
companion document to be an addendum to TSB-32-A. There was a question as to whether or not
this document should be an addendum or a companion document. The project submission will
need to be altered to give this companion document its own TSB number and to create a one page
addendum to TSB-32-A so that it will act as a pointer to the new TSB companion document. The
issue is that the companion document is fairly self-contained and standalone, so it is not
necessary to have them sold as one document (which is what happens with an addendum).
PN-3673, UPDATE/REVISE TIA-464-C
TR-41.1 is ready to start on the updating of the TIA-464-B (Requirements for PBX switching
equipment) so that it will be completed by the 2001 deadline.
TR-41.1/98-11-28 (R. Britt, Nortel, submitted to the previous TR-41.1 meeting) was reviewed,
focusing on the notion of why the loss plan should be simplified. This tutorial document explains
that TIA-579 converted from IEEE units to ITU-T units (SLR, RLR and OLR [Overall Loudness
Rating] based on PCM 64k standard). TIA-464-B will be modified to support IP telephones.
T1E1.7 has a carrier loss plan (T1.508) which has also made the conversion from IEEE units to
ITU-T support of SLR (Send Loudness Rating) of 8 dB and RLR (Receive Loudness Rating) of 2
dB. TIA-464 should now be modified to support these new levels to make the PBX port-to-port
loss plan consistent with all other loss transmission planning documents. The recent work
completed on the TSB-32-A update also includes the converted units.
TIA-464-B had a number of analog and digital trunks that had the same port losses but varying
insertion losses. These differences were a result of various implementations between vendors of
similar interfaces. R. Britt determined the Optimum OLR (Objective Loudness Rating) and also
re-normalized all the port-to-port connections. Changes were made in the loss plan to meet the
acceptable OLR while consolidating a number of ports which in turn would reduce the complexity
of the loss plan. TIA-464-C should not have differences of 1 or 2 dB in similar digital connections
since these differences are becoming less and less important due to the nature of the network
today. The shift to IP telephony, where transmission and loss characteristics will be more of a
function of the set/endpoint rather than the network, also assists in the reduction of this need for
similar digital trunks with varying insertion losses. TIA-464-C should now amalgamate a larger
number of digital ports. The notion is any digital device with SLR and RLR of 8 and 2
respectively should have the same loss plan regardless of the direction and nature of the trunk.
There were a number of digital interfaces in TIA-464-B that had the same receive and transmit
levels but in fact had different loss plan numbers; those loss plans were different due to changes
requested by many manufacturers for various reasons.
T. Tung (Siemens) found a number of port-to-port connections (in the proposed TIA-464-C loss
plan) that are currently in violation of FCC through gain requirements in FCC Part 68. There
are two ways of proceeding with the necessary changes: 1) Change the FCC Part 68 through
gain requirement in order to have it meet what the proposed TIA-464-C loss plan calls for, or 2)
42
March-April 1999
Change the modified table to meet FCC requirements. It was decided to allow those connections
in the proposed TIA-464-C amalgamated loss plan that are in violation of FCC to be altered to
meet the Part 68 requirements. TR-41.1/99-02-03, Impact of Nortel 464-C Loss Plan on MLTS
(Siemens Business Communication Systems, Inc.) addresses these ports that exceed the FCC
throughput requirements.
Siemens states that the proposed TIA-464-C loss plan is untested and the industry at large will
take 3-5 years to comply with the new loss plan. The contribution argues that the loss plan
should be simplified but with minor changes to the values in the table. Using the Emodel
Optimum OLR model, Siemens states that if you take the 96% line and above, then the OLR
levels should be acceptable to the user. Comparing TIA-464-B loss plans to this E-Model OLR
diagram, there appears to be no need to change since TIA-464-B fits inside the curve. TR41.1/99-02-03 also details this discussion.
In subsequent discussion, it was decided that the TIA-464-C proposed loss plan will become
optional rather than mandatory. At this point, TIA-464-C will contain a simplified TIA-464-B
loss plan that has the same values with some digital ports having been amalgamated. The
document will also have a C version that will be the Nortel proposed TIA-464-C plan with the
FCC Part 68 modifications and a caveat that states that it is recommended for use going
forward.
TR-41.1/99-02-09, Simplified Loss Plan Table Format (Mitel), states that the B matrix has a
mirroring effect with the values; Mitel proposes to make the table simplified by making the table
simply a one-way connection on either side. D. Frank (Siemens) stated that this is good from a
design point a view; however, the old table was used by transmission people.
Two proposals were made for TIA-464-C:
• Move B current loss plan to an appendix where the B will be migrated to 8 and 2 values for
SLR and RLR and the format will be altered to meet the Mitel contribution.
• Have the C (Nortel-proposed) loss plan be in the text of the document with the OLR of 10 and
the new SLR and RLR values. Adjust the loss plan to conform to Part 68 throughput
requirements.
R. Haterhill (Mitel) agreed to modify the existing C loss plan to meet Part 68.
Other TIA-464-C issues include:
• Should there be a new document number and title for TIA-464-C? This was proposed by R.
Britt in order to remove the PBX stigma for the non-PBX market.
• Current section 4.2 covering E&M (Ear and Mouth: separate signaling lines) will be moved
into an Annex without any content changes.
• P. Weismantel (NEC) requested that members review the need to include an OC3 fiber
interface into TIA-464-C. He noted that many of the RBOCs are terminating OC3 fiber to the
facility even if one needs only a T1 interface.
• xDSL requirements will not be included in TIA-464-C.
• The interconnection between wireless base stations and the PBX should not be defined since
there is no standard for interconnections. This proposal for a new section has been removed.
• The proposal for ISDN BRI Line side requirements will be removed.
• The addition of VoIP requirements is desired; however, there is no commitment at this time
from the participating members to know if it shall be included in another document or if it will
be included in this document.
• The new Annex B will be the old B loss plan along with “Acoustic Reference Level Plan” which
is currently Annex C.
• Members should consider whether, in the Analog section, the document should talk about the
public network potential for sending backwards voice announcements rather than tone
strategy, e.g., no dial tone…, “Please dial…,” and instead of busy tone: “The Station is Busy.”
March-April 1999
43
The current time schedule calls for completion in 8/99; contributions need to be submitted to next
meeting (May, in Portland).
N EW C ONTRIBUTIONS FOR TIA-464-C
TR-41.1/99-02-02, Proposed Changes to OPS Ringing Trip Requirements in the new
ANSI/TIA/EIA-464-C (Siemens Business Communication Systems, Inc.), recommends changing
the diagram from the existing 464 to the FCC Part 68 diagram. The proposal is to further align
with FCC Part 68.
TR-41.1/99-02-04, Proposed Changes to Digital Network Interface Jitter Requirements in the
new ANSI/TIA/EIA-464-C (Siemens Business Communication Systems, Inc.), proposes a change
to Jitter requirements for DS1 from TIA-464-C level to AT&T Technical Reference. The feeling
was that since it is not necessary, there is no need to make a change. AT&T cannot refuse the
connection as long as it meets Part 68. This proposal will not be included in TIA-464-C.
TR-41.1/99-02-05, Proposed Changes to Digital Network Interface Jitter, Wander, and Phase
Transients Requirements in the new ANSI/TIA/EIA-464-C (Bellcore), is designed to contest TR41.1/99-02-04 to maintain the jitter requirements at a minimum level rather than be networkservice-provider-specific. It proposes only a single change to the Jitter T1 requirements where in
Band 2 the UI is at 0.1. This actually only applies at the signal at the NI (Network Interface)
where the jitter at the source equipment within the CI (Customer Interface) shall stay the same.
This modification was accepted for TIA-464-C since it aligns TIA-464 with a T1 standard.
TR-41.1/99-02-06, Proposed Changes to Digital Signaling and Supervision Requirements in the
new ANSI/TIA/EIA-464-C Standard (Bellcore), proposes a new section to TIA-464-C since it is a
network offering.
TR-41.1/99-02-07, Proposed Changes to Digital Network Interface MTIE Requirements in the
new ANSI/TIA/EIA-464-C (Siemens Business Communication Systems, Inc.), requests a change
from MTIE to AT&T stratum level network timing. Review of this contribution is needed; other
contributions are needed that will state emphatically what will be done. The current TIA-464
does not discuss the various Stratum Level requirements, which is an omission of the table from
B.
E911
TIA-689 (PBX and KTS support of enhanced 911 emergency service calling) handles the E911
requirements. TIA-689 should be revised in the next few years. The T1S1 standard should be
finalized soon to include the ISDN reference where it defines the Layer 3 protocol for ISDN E911
transport. There are actually three interfaces: analog CAMA (Centralized Automatic Message
Accounting), digital CAMA, and ISDN.
With respect to TIA-464-C work, there should be pointer references within TIA-464-C to cover all
the different applications. With respect to wireless location information, a request is going from
TR-41.1.9 to TR-41.6 through P. Weismantel (NEC) for information to include in TIA-689 which
will assist in reporting the location of a phone behind a PBX that fits the mandated cell site/sector
information locator.
TIA-464 LIVING LIST
TR-41.1/99-02-01 is the Living List for PN-3673, TIA-464-B, dated February 17, 1999. The only
change from the previous version is in item 3, OPS Ring Trip. This will be the last issue of the
Living List since all changes will be tracked as action items in the meeting notes going forward.
TR-41.1 thanked R. Frank (Siemens) for his diligent effort in maintaining the TIA-464-B living
list.
44
March-April 1999
PN-4468, PRIVATE DIGITAL N ETWORK SYNCHRONIZATION (TIA-594)
PN-4468, Private Digital Network Synchronization, was established to reaffirm TIA-594. The
suggestion was made to rescind TIA-594 and the Synchronization Standard and instead support
ANSI Adoption of ISO 11573.
LIAISON R EPORTS
T1E1: DS1 T1.403 (Network to customer installation - DS1 metallic interface) has been balloted
and should be voted into publication soon. The digital signaling document, T1.403.01, went for
ballot and should pass as well. The PRI Interface T1.403.02 was accepted and passed. The
SONET interface, both Single Mode and Multi Mode and electrical interface specifications, were
accepted.
ETSI STQ - VoIP Interface: J. Horrocks (DTI) has requested a formal liaison with TIA TR41.1 for transmission work in the future pertaining to the following topics:
• End to end performance requirements study
• Non-linear effects
• Packet loss
• Jitter delay
TR-41 and T1 chairs had a meeting to discuss the IP overlaps between the groups. R. Britt
(Nortel) will attend the ETSI TIPHON meeting to report to TIPHON on the TIA and T1 work
items that are of interest to TIPHON. STQ was requested by TIPHON to do work in the
characterization and measurement issues between acoustic and electrical connections. The
packet loss and related information is also lacking. Characterization of wideband codecs and the
use of E-model as it is applied to IP networks is another potential work area.
TR-41.1.2, VOIP TRANSMISSION
In the first meeting of this working group, the major work item was to perform a readout of the
existing state of IP-related transmission work in the world where the major players are ETSI
TIPHON, ETSI STQ, and ITU-T SG12.
ETSI TIPHON WG5 has produced a number of documents that have some questionable validity
when applied to voice quality. This has been pointed out to TIPHON by STQ and SG12. ETSI
STQ is currently in a consulting mode with TIPHON in the development of E-Model-based
transmission requirements. ITU-T SG12 has just recently proposed a new question to ITU-T
(Question 23/12) which is extremely similar to the press release the TIA issued on TR-41.1.2.
After a discussion of the state of IP transmission work today, the chairman, R. Britt (Nortel),
opened the floor. The subsequent discussion revolved around what would be the potential
outcome for any work done by this body and where would liaison best benefit this team. T. Tung
(Siemens) proposed that we look to provide a document that would be similar to the TSB-32-A
companion document which would detail specific IP-related scenarios. There was much interest
in this proposal; however, Nortel has stated that due to the lack of resources, they are incapable
of providing the appropriate scenarios. They are, however, willing to provide their resource in
performing the E-Models if and when the scenarios are appropriately designed by others.
It was eventually seen that many of the participants in this meeting did not have the special
expertise required to specify such IP-related scenarios for E-Model use. All members were asked
to determine within their respective organizations the need for this type of work and to determine
if more appropriate representation can be provided.
William Soler, Lucent Technologies
March-April 1999
45
TR-41.2, CONFORMITY ASSESSMENT
EUROPEAN UNION - CANADA MRA
Implementation of the European Union - Canada MRA (Mutual Recognition Agreement) began in
November, 1998. A number of workshops and forums have been scheduled to facilitate
implementation of the MRAs. Canada and the US will have a joint workshop with the EU at the
Department of Commerce (DOC) Auditorium in Washington, DC, tentatively scheduled for April
27, 1999. Canada will have a workshop in the EU on May 25, 1999 covering telecommunication
safety and EMC.
Other European MRA activity:
• A Canadian - Swiss MRA has been signed; its implementation is tied to the EU- Canadian
MRA.
• A Canadian - EEA (European Economic Area) is currently under negotiation covering
Canada, Liechtenstein, Norway and Iceland.
Standards Council of Canada (SCC) has established a program for accreditation for
telecommunications, EMC, and safety.
EUROPEAN UNION - US MRA
Implementation of the European Union - US MRA began in December, 1998. The FCC has
released a Report and Order, FCC 98-338, for the implementation of MRAs and
Telecommunications Certifications Bodies (TCBs) (available at
http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/1998/fcc98338.pdf). Canada and
the US will have a joint workshop with the EU at the DOC Auditorium in DC, tentatively
scheduled for April 27, 1999. NIST will also have a workshop in Gaithersburg, MD on April 28,
1999. To facilitate implementation of the Order, TIA, ACIL (Association of Independent
Scientific, Engineering and Testing Firms), the FCC and NIST have formed a task force with
industry to further develop implementation strategies. The next task force meeting is on Feb. 2223, 1999.
R&TTE DIRECTIVE
The EU R&TTE (Radio and Telecommunications Terminal Equipment) Directive (TR-41.2/99-02003) was approved by the EU Parliament and will be effective in March 2000. SDoC (Suppliers
Declaration of Conformity) will be used for most wireline equipment, however radio equipment
will continue to be subject to third party certification requirements. A TR-41.2 task force will
analyze the Directive (available at http://europa.eu.int/eur-lex/en/index.html) and develop a series
of questions to present to the US government for discussion at the April 26, 1999 Joint Sectorial
meeting.
R&TTE TF Members:
J. Cottrell
S. Crosby (chair)
R. Gubisch
J. Lambert
H. Mar
Company
Compaq
Lucent
ITS
Cisco
IC
APEC STATUS R EPORT
The APEC (Asia Pacific Economic Cooperation Forum) Mutual Recognition Arrangement, like
the MRAs with Europe, is also a two phase arrangement that includes a mutual recognition of
test results phase followed by a mutual recognition of certification competency. An
implementation schedule was issued by the APEC telecom ministers. The next round of APEC
46
March-April 1999
MRA discussions will be held in Miyazaki, Japan, the week of March 8, 1999. The CIAJ
(Communications Industry Association of Japan) web page is
http://inetsrv.cian.or.jp/ciaj/welcome.html. The Australian Telecom Industry Association is at
http://www.atia.aeema.asn.au. Both of these groups are partially responsible for working out the
implementation details.
CITEL MRA
Activities within CITEL (Comision Internamericana de Telecomunicaciones) are occurring in the
form of workshops; there is an interest by the economies to develop an arrangement similar to
APEC. TR-41.2/99-02-007 is the CITEL MRA Overview. At the last round of MRA discussions
in Columbia, November, 1999, A. Kwan accepted the task of drafting an MRA modeled after the
APEC MRA. The one significant deviation: the agreement is intended to be a true multilateral
MRA rather than a series of individual bilateral agreements. There will be a government-only
meeting held at OAS headquarters on Feb. 23-24, 1999. The next round of CITEL MRA
discussions will take in Iguacu Falls, Brazil, on March 18, 1999. The CITEL home page is
http://www.oas.org/EN/PROG/CITEL/citel.htm.
SEMINARS AND W ORKSHOPS
P. Adornato (Nortel Networks, TR-41.2 chair) reported on two useful workshops in Washington,
DC Feb. 9-10, 1999:
• Workshop on Conformity Assessment (Feb. 9, 1999): current issues relating to SDoC,
Certification Registration, testing, integrated services, accreditation of labs, registrars and
certifiers, and MRAs
• EMC Globalization Workshop (Feb. 10, 1999): MRA implementation for EMC and
telecommunications
ITI ACTIVITIES
ITI (Information Technology Industry Council [formerly CBEMA]) is developing strategies to
support its 1-1-SDoC proposal, especially in the areas of the SDoC form, accountable parties
under an SDoC scenario, and the contents and maintenance of an SDoC compliance folder. ITI
believes that the Transatlantic Business Dialog, Asian Pacific Economic Cooperation
Subcommittee on Standards and Conformance, and other forums will be useful in promoting 1-1SDoC.
ITI has had several meetings with the FCC to promote the use of SDoC for equipment subject to
Part 68 requirements. It was reported that the FCC has indicated it is now willing to consider
such a move to SDoC.
D OCKET 98-68 REPORT AND O RDER (FCC 98-338)
TR-41.2/99-02-002 is a copy of the FCC’s GEN Docket No. 98-68 (FCC 98-338) relating to MRAs
for product approvals with the EC, APEC and other foreign trade partners. The FCC is
encouraging an on-going dialog with industry to promote understanding of the authorized role of
TCBs (Technology Certification Bodies) and their limitations as well. B. Howden (FCC)
presented a list of concerns (TR-41.2/99-02-008, same as TR-41.11/99-02-001) relating to the
implementation of 98-68 and the impact to Part 68 regulations. The group identified the TCB
Implementation Task Group, TR-41.9 and TR-41.11 for various follow-up activities.
SINGLE SYMBOL A CTION PLAN
A small group was formed to brainstorm on possible strategies to promote the Single Symbol
concept.
March-April 1999
47
Single Symbol TF
J. Cottrell
S. Crosby (chair)
J. Lambert
J. Sterling
Company
Compaq
Lucent
Cisco
ITS
SDOC ACTION PLAN
Regulatory approaches to implementing DoC for network terminal equipment varies around the
world. Several members volunteered to investigate these differences, and to provide input to J.
Wronka (Lucent) for the development of an SDoC white paper outline.
SDoC White Paper Action Item:
1. Investigate SDoC terminal attachment issues and liabilities for:
• Australia
• Singapore
• Other regions
• EU
2. Obtain input from network service providers:
3. Database issues:
4. Explore present FCC SDoC application for equipment subject to Parts
15 and 18 and possible deviations for network terminal equipment:
5. Explore confidence building for test lab under DoC:
Volunteer:
J. Cottrell
J. Cottrell
J. Cottrell
C. Lee
P. Adornato
G. Slingerland
P. Adornato
S. Crosby
J. Lambert
C. Pinkham
These groups will communicate via e-mail to develop additional input for TR-41.2 discussions.
Any draft output of the ad hoc groups will be circulated to TR-41.2 members at least one week
prior to the Ottawa meeting in August.
TR-41.3, ANALOG AND DIGITAL WIRELINE TELEPHONES, NOVEMBER 18-19, 1998
PALM SPRINGS, CA
Editor’s note: TR-41.3 meeting reports have not been included in CSR for the last two meetings.
CSR regrets this omission and includes the report below from the previous TR-41.3 meeting. The
TR-41.3 report from the February, 1999 meeting was not available as we went to press.
This TR-41.3 meeting (November 18-19, 1998, in Palm Springs, CA) was held jointly with CSA
T510/T515.
Members were asked if they were aware of any patents, the use of which might be essential to the
work being considered by the subcommittee. As previously reported, Bellcore, Cidco, Nortel, and
Philips Broadband hold intellectual rights that may be relevant to the Caller ID work being done
by TR-41.3.1. Active Voice and Notify Corporation have intellectual property rights that may be
relevant to TR-41.3.2.
A request was received by all the TIA chairs to review all standards and projects for which their
subcommittees are responsible to make sure there are no Y2K problems. S. Whitesell (TR-41.3
chair) has replied that none of the TR-41.3 documents are Y2K sensitive; he confirmed that
statement with the members present.
S. Whitesell (TR-41.3 chair) reminded TR-41.3 that TIA is going electronic and all ballots,
meeting minutes, etc., would be handled via the TIA website www.tiaonline.org. Where possible,
all submissions should be accompanied by a soft copy so that they can be more easily managed.
S. Whitesell and P. Holland (Circa Communications, TR-41.3 secretary) agreed to gather and
upload the required documents to the TIA web site.
48
March-April 1999
TIA 579-A, Telecommunications Telephone Terminal Equipment Transmission Requirements for
Digital Wireline Telephones (PN-3724), has been published.
TR-41.3.1 REPORT ON PN-3674, TYPE 1 CALLER ID
The PN-3674 Committee Ballot, Type 1 (on-hook) Caller Identity Equipment Performance
Requirements, closed on October 28, 1998. There were 10 affirmative votes, 4 affirmative votes
with comments, 4 negative votes with comments and 2 no comments. TR-41.3.1 resolved all
negative votes and addressed the comments during this meeting.
TR-41.3.1 stated its intention to have the PN-4078 Type 2 (off-hook) draft ready after some
editorial cleanup in December. It was agreed that the amended draft would be sent for a second
ballot in early January so that the ballot could close in time for the comments to be reviewed at
the February meeting.
TR-41.3.2 REPORT ON PN-4159, STUTTER D IAL TONE
The “Recommendations for Changes to the Alameda Order” as outlined in TR-41.3/98-11-23 were
sent to TR-41.9 for review and release to the FCC. TR-41.9 agreed to forward these to the FCC.
TR-41.3/98-11-23 is a summary of requirements and rational of the eight conditions required for
a waiver of FCC Part 68.312(k) for connection of a SDD (Stutter Dialing Device) to the network.
Work continued on PN-4159, Stutter Dial Tone Detection Requirements; progress to date
indicates that the proposed standard should be complete within six months.
LIAISON R EPORTS
ITU Study Group 12
The next meeting of Study Group 12 is November, 1998. S. Whitesell (Philips Consumer) made
available a contribution with regard to Test Heads to those who were interested in reviewing it.
R. Britt (Nortel Networks) has made a submission regarding STMR (Sidetone Masking Rating).
IEEE Subcommittee on Telephone Testing
Work on the hands-free measurement standard continues. A firm completion date has not been
set although the end of the year could be possible so that the requirements can be referenced in
PN-4352, Transmission Requirements for Voice over IP and Voice over PCM Digital Wireline
Telephones.
IEEE 269-1992, Standard Methods for Measuring Transmission Performance of Analog and
Digital Telephone Sets is up for revision. TR-41.3/98-11-30 provides the IEEE STIT to-do-list of
22 items for Standard 269. Due to the current workload of the IEEE committee, it is not possible
to do a revision now. A ballot to reaffirm the existing standard will be issued, with plans to do a
revision at a later date.
FOLLOW -UP ON FCC EX -PARTE ON HAC
S. Whitesell (Philips Consumer), accompanied by C. Berestecky (Lucent), P. Adornato (Nortel
Networks), and R. Breden (TIA) gave an ex-parte presentation to the FCC on October 28, 1998.
The subject was the differences between EIA RS-504 and TIA/EIA-504-A, Magnetic Field
Intensity Criteria for Telephone Compatibility with Hearing Aids. TR-41.3/98-11-25 (S.
Whitesell, Lucent) summarizes that presentation:
• Magnetic field strength numbers appear lower, but real world magnetic field strength is the
same, except the “Loop hole” for meeting magnetic field strength requirement by increasing
gain level was eliminated
• Frequency response requirements appear different, but are the same, except a relaxation of
limits for higher magnetic field strengths was eliminated
• Includes same receive volume control requirements for acoustic output as in present Part 68
rules
March-April 1999
49
• Applies receive volume control gain requirements to magnetic field strength as well as acoustic
output
• Adds distortion requirement for both acoustic and magnetic output at maximum volume
control setting
• Applicable to all types of telephones
Following the presentation, the FCC asked that TIA provide a draft of the wording to incorporate
TIA/EIA-504-A into the FCC Rules for Hearing Aid Compatibility. S. Whitesell prepared the
draft (TR-41.3/98-11-026). After discussion of the wording, it was agreed that the text proposed
in the contribution be sent to the TR-41 Plenary to be forwarded to the FCC.
PN-4350, REVISION OF TIA-470-B
Work was initiated on the revision of TIA-470-B, Telecommunications-Telephone Terminal
Equipment-Performance and Compatibility Requirements for Telephone Sets with Loop
Signaling.
TR-41.3/98-11-24, FCC 68.317 Change Proposal (Handset Rx volume control), proposes revised
wording for Part 68 Section 68.317.
TR-41.3/98-11-22, ETSI Ringer Level Measurement Method (R. Magnuson, Siemens) proposes
that the measurement methods (from ETSI TBR-8-1994) could be used in place of the current
TIA-470-B requirements. After discussion, the decision to change was subject to further review
and was deferred to the next meeting.
TR-41.3/98-08-17, Recommended Changes to 470-B (J. Freestone, Nortel), was presented at the
previous meeting in August, but action on the proposals was delayed until this meeting. The
contribution included the following proposals:
• Reduce the current distortion measurement requirement (Section 4.2.2.4) to one point at 1
kHz. After discussion, the consensus was that the proposed change should not be made. It
was also decided that a sidetone distortion requirement should be added; contributions
proposing the requirement are requested.
• Change the requirements in Section 4.3.1.3 for ringer response to non-ringing signals. This
was tabled until T1E1 determines if the signals that gave rise to these requirements are still
used.
• Redefine the phantom ring or bell tap test requirements (Section 4.3.1.3) so that common test
equipment can be used. The proposed need to change was accepted; contributions that propose
new test methods are needed.
• Devices that use high frequency ringers for the hard of hearing or small piezo ringers because
of design requirements (e.g., cordless phones, battery operated devices, adjuncts, etc.) should
be exempt from Clause 4.3.2.2.1 requirement to have a major frequency component below
1300 Hz. This was considered in conjunction with TR-41.3/98-11-31 (S. Whitesell, Philips
Consumer Communications) which explains the rationale for the original requirement. The
proposal to change the requirement was not accepted, but a change to a two level requirement
would be considered if a proposal is submitted.
• Change the measure for ringer acoustic output as described in Section 4.3.2.3.1, from A
weighted sound power to phons. This was discussed along with a suggestion that sones be
used. No support was received for the proposals so the requirement will remain unchanged.
• Reduce the DC voltage used to measure the DC current during ringing as described in Section
4.4.3.1. It was agreed that this should be done; 78 volts was accepted as the DC component of
the test voltage.
50
March-April 1999
• Reduce the On-Hook impedance requirement in Section 4.4.3.2 to 10K. This was considered in
conjunction with TR-41.3/98-11-31, which supported the change but gave a rationale for a
higher limit. Consensus was reached to change the limit to 60 kohms over the full frequency
range.
• Change the handset cord test described in Section 4.5.2.3. This was considered in conjunction
with TR-41.3/98-11-31, which supported the change based on different limits. It was agreed
that with the exception of the button markings, the mechanical requirements section should be
moved to an Annex where it would be informative rather than mandatory.
The following were presented and reviewed for detailed consideration at the next meeting:
• TR-41.3/98-11-27, 5ESS V-I Curves (S. Whitesell, Philips Consumer)
• TR-41.3/98-11-28, DMS-100 Voltage-Current Measurements
• TR-41.3/98-11-29, V-I Curves (S. Whitesell, Philips Consumer)
PN-4352, TRANSMISSION REQUIREMENTS FOR VOICE OVER IP AND VOICE OVER PCM DIGITAL WIRELINE
TELEPHONES
S. Whitesell and R. Britt outlined the intent of the initiative to create a new voice transmission
standard for internet telephony as described in the TIA Press Release (TR-41.3/98-11-32). R.
Britt led TR-41.3 through a review and discussion of the initial document (TR-41.3/9811-33)
which is based on TIA-579-A. Good progress was made and work will continue at the Sarasota
meeting in February. Discussion indicated that completion by the end of 1999 is realistic.
N EW PROJECT ON IP TELEPHONES
P. Holland (Circa Communications) proposed a project to develop a standard for IP Telephones
and agreed to act as chair of the working group that would prepare the proposed standard. The
working title was agreed as “Performance and Interoperability Requirements for VoIP Telephone
Terminals.”
The scope would be to define the performance and interoperability requirements for H.323-based
VoIP telephones. The proposed document will identify and incorporate by reference relevant
existing standards, supplementing them with additional requirements where necessary, in order
to completely characterize a fully functional VoIP telephone. The standard will include reference
to ITU Recommendations H.323 and Q.931, G-Series codecs, TIA PN-4352, IEEE 802, and IP
protocols such as TCP/IP, UTP, UDP, RTP, and RSVP.
Phil Holland, Circa Communications
TR-41.5, MULTIMEDIA BUILDING DISTRIBUTION SYSTEMS
Thirteen ballot responses to PN-4407, TSB-110, “Residential Gateway - Recommended minimum
application, feature and operational requirements,” were received. TR-41.5/99-02-003 is the
summary of the 13 responses:
No with comments:
1 (Lucent)
Yes:
7
Yes with comments
3
No Comment:
2
Changes were incorporated into the proposed TSB based on the 33 comments received. It was
agreed that some of the changes constituted technical changes. However, because a quorum was
not present, the resulting document could not be approved and moved forward. As a result, the
updated TSB will be posted to TR-41.5’s website, and the membership will be queried via e-mail
for acceptance to move forward for default ballot. It is expected that this can be completed prior
to the next meeting.
March-April 1999
51
Work was started on the development of PN-4408, TSB-111, Residential Gateway - Physical
Specifications. TR-41.5.1/99-02-002© (K. Kerpez, Bellcore) is a preliminary working document.
It specifies that the Residential Gateway internal digital interface (DI) shall conform to the PCI
Local Bus Specification Rev 2.2. Additional contributions are requested to move the work
forward.
No action was taken on the development of PN-4409, TSB-112, Residential Gateway - Software
Specifications.
TR-41.5/99-02-004 is an update from TIA on TIA’s Intellectual Property Rights Policy. It is
Advisory Note #11C which supersedes Advisory Notes 11, 11A and 11B. This update is to have
the TIA policy conform to ANSI Guidelines (see
http://www.ansi.org/public/library/guides/ppguide.html).
Richard Cochran, GTE
TR-41.6, WIRELESS USER PREMISES
EQUIPMENT SYSTEMS
At the Chairs meeting, a change in the IP question procedure was made. The old practice was
just to ask if anyone present held IP, which affected the standard being considered. A note was
made of those companies. The change is that if someone answers in the affirmative, they are
instructed to access the TIA web site and complete the IP form registering their claim.
The TIA is now using the Internet for balloting and comments, with comment resolution
information e-mailed to the commentor (with a copy to B. Zidec-Connor, TIA Secretariat). This
fulfills ANSI’s requirement that there be a record of replies to people who respond and/or
comment on Ballots.
A soft copy of the latest PPI document (PN-4000, Licensed PCS to PCS Interference, to become
TSB-84-A) from TR-46.2.1 is available on the TIA website; the document is starting Validation
and Verification (V&V). Any comments should be transmitted to TR-46.2 using the forms
available on the web site.
The Chair read a letter from B. Scales (Panasonic), Chair of TR-41.6.3, resigning his position
effective at the end of this meeting.
There was a proposed liaison from TR-41-6.3 to the PHSMoU organization, formed to promote
PHS awareness in the Americas; the liaison requests that a representative from TR-41.6.3 be
permitted to attend a future meeting. The purpose would be to inform them of TIA activities in
PHS and discuss future collaboration.
TR-41.6.1, PWT (PERSONAL WIRELESS TELECOMMUNICATIONS)
The representatives from Lucent and Ericsson said that they have patents that may be pertinent
to the PWT standard.
TR-41.6.1/99-02-003 provides four Ballot Summaries discussed below.
PWT-E, SP-3614
TR-41.6.1 has been unable to resolve the No ballot comments on SP-3614-A, Personal Wireless
Telecommunications - Enhanced Interoperability (to become TIA-696). This is a DCT 1900
interoperability standard for the licensed 1.9 GHz band. Ericsson stated that it could not
support a standard that mandated such large guard bands, as proposed by Lucent, thereby
eliminating a large amount of spectrum from the licensees’ use. Ericsson was agreeable to have
52
March-April 1999
the ability to create guard bands that were found to be necessary upon installation and
coordination with adjacent licensees; the document already includes this requirement. Ericsson
maintains that the PCS to PCS interference coordination Bulletin TSB-84 should be used to
determine the need for guard bands on a case by case basis.
W. Cruz, TR-41.6.1 chair, will check with representatives of Lucent to determine if the latest
proposed changes to the PWT-E standards proposal will resolve Lucent’s “no” ballot comments. If
they are not acceptable, TR-41.6.1 will close SP-3614 without completion of the standard.
PWT TEST SPECIFICATIONS (SP-3951 AND SP-3949)
TR-41.6.1 received the ballot responses for SP-3951, The Physical Layer Conformance Test
specification (TR-41.6.1/99-02-003):
•
•
•
•
10 companies approved
1 company, Frank Stein Consultant, approved with editorial comments
1 company, Siemens, disapproved with comments
4 companies had no comment.
The Siemens “No” ballot was an editorial comment seeking information.
The group agreed that the editorial comment did not warrant a No vote and agreed to
recommend to TR-41.6 that the document be approved as a standard (TIA-662-10A) after
incorporating the editorial changes proposed by F. Stein. W. Cruz provided a response to
Siemens via e-mail; R. Frank (Siemens) filled out a blue card approving the standards proposal.
The
• 9
• 1
• 4
group received the ballot responses for the Voice Test Specification, SP-3949:
companies approved
company, F. Stein Consultant, approved with editorial comments
companies had no comment.
The group voted to recommend SP-3949 for approval as a standard (TIA-662-10-C) after
incorporating the editorial comments from F. Stein.
PWT DATA (SP-4199, SP-4201, SP-4200, SP-4247, SP-4353)
The group received the ballot responses for SP-4199, Data Service Access Profile 0, Class 1 (TR41.6.1/99-02-003):
• 11 companies approved
• 2 companies, F. Stein Consultant and 3Com, approved with editorial comments
• 4 companies had no comment.
The group voted to recommend approval as a standard (TIA-662-13C) after incorporating the
editorial comments from F. Stein and 3Com.
The group received the ballot responses for SP-4201, Data Services Access Profile E, Short
Messaging, Class 2 (TR-41.6.1/99-02-003):
• 1 company, F. Stein Consultant, approved with editorial comments
The group voted to recommend approval of SP-4201 as a standard (TIA-662-13F) after
SP-4200, Data Service Profile C, Class 2, Data Link, was approved for balloting at the TR-41.6
meeting in November. TIA will be balloting this document before the next meeting. This
document is scheduled to be approved as a standard (TIA-662-13D) at the next meeting on May
19, 1999.
March-April 1999
53
The group received the ballot responses for SP-4247, Data Service Profile A & B, Class 2 (TR41.6.1/99-02-003):
• 1 company, F. Stein Consultant, approved with editorial comments
The group voted to recommend approval of SP-4247 as a standard (TIA-662-13B) after
TR-41.6.1 completed comments on PN-4353, Service Profile F, Class 2, Fax. They approved it
for Industry ballot after the editor incorporates the agreed changes. The work plan is to:
• Resolve letter ballot comments at the next meeting on May 19, 1999
• Approve the document as a standard (TIA-662-13H) after resolving the ballot comments.
TR-41.6.1/99-02-004 is a ballot draft of SP-4353, Multimedia Messaging Service (MMS) with
Specific Provision for Facsimile Services, Service Profile F, Class 2.
W ORK PLAN
The status of the work plan for TR-41.6.1 data is shown in Table 1.
Service
Profile
A & B Class I
Description
Frame Relay Service
TIA/EIA-662
Section
662-13A
Project
Number
SP-4079
A & B Class 2
C, Class 1
C, Class 2
Frame Relay Service
Data Link Access
Data Link Access
662-13B
662-13C
662-13D
PN-4247
SP-4199
PN-4200
E,
E,
F,
F,
Short Messaging
Short Messaging
Fax
Fax
662-13E
662-13F
662-139
662-13H
NA
SP-4201
NA
PN-4353
NA
662-13J
NA
Multimedia
662-13J
NA
Class
Class
Class
Class
1
2
I
2
NA
Multimedia
Status
Published as a standard; Work is
complete
Approval as a standard February 1999.
Approved for balloting. Scheduled for
approval at the May 19, 1999 meeting.
Reserved for future use
Reserved for future use
Approved for balloting on Feb 1999.
Scheduled for approval as a standard on
May 19, 1999.
Section 662-13 1 will not be used
because the letter I will cause confusion
between 1 & I
TR-41.6 is awaiting the completion of
this DECT standard by ETSI.
Table 1. The Work Plan and Status of TR-41.6.1 Data.
LIAISON TO TR-46
TR-41.6.1 agreed to request that TR-41.6 send a liaison to TR-46 specifying that the occupied
bandwidth and emission bandwidth of PWT-E is 745 kHz and 840 kHz respectively. TR41.6.1/99-02-05© (P. Murray, Ericsson) notes both the PWT-E occupied and the emission
measured bandwidths. TR-41.6 approved the liaison letter asking to review TR-46.2’s PN-4000,
Licensed PCS to PCS Interference (to become TSB-84-A).
TR-41.6.3, PACS-WUPE
NEC answered “yes” in response to the question of patents pertaining to the PACS-WUPE
(Personal Access Communications System, Licensed Band - Wireless User Premises Equipment)
work.
B. Scales (Panasonic) announced via a letter to TR-41.6 that he is resigning as chair of TR41.6.3, effective at the close of this meeting. He will still participate in future meetings as a
representative of Panasonic. P. Weismantel (NEC) agreed to take the chair of TR-41.6.3.
54
March-April 1999
A liaison letter to the Vice Chairman of the PHS Forum of the Americas was introduced and
approved for forwarding to TR-41.6.
An article in Wireless Week of January 4, 1999, was brought to the committees’ attention by P.
Weismantel. In the article, a Mr. Jeff Crollick, identified as the chair of the wireless emergency
services subcommittee for the TIA, was quoted as saying “From my committee’s standpoint, I
believe that the standards [the wireless industry has] built for phase I and II are totally
applicable to PBX.” TR-41.6.3 believes that J. Crollick was not representing the PBX industry or
the TIA when he made this statement. Clarification should be sought through the TR-41 chair.
TR-41.7, SAFETY AND ENVIRONMENTAL CONSIDERATIONS
LIAISONS
T1E1.7
Under project T1Y1-27, the draft standard Classification of Above-Baseline Physical Threats to
the Telecommunication Links was scheduled for ANSI review on February 16. Under project
T1Y1-13, the Electrical Protection of Broadband Facilities standard was scheduled for ANSI
review on February 7. Both these standards will be published if there are no comments
generated during the ANSI reviews. A project on Bonding and Grounding of Telecommunications
Network Equipment is under way jointly with T1E1.5. The five year revision of the standard on
Electrical Protection Applied to Telecommunications Network Plant at Entrances to Customer
Structures or Buildings, T1.318, will begin at the next meeting.
IEEE 1100
The standard, Recommended Practice for Powering and Grounding Sensitive Electronic
Equipment, has been completed and has been sent to the IEEE Standards Board. The
Subcommittee will meet in October to begin work on the next revision.
National Electric Code (NEC)
The deadline for proposals for the 2002 version of the NEC is November 5, 1999.
NAFTA CCT
Mexico has adopted a voluntary Standard, NMX-250-NYCC-1998, based on IEC 950 Second
Edition, Fourth Amendment. A Memorandum of Understanding (MOU) has been signed between
the US and Mexico for mutual acceptance of test data for safety for telecommunication
equipment. Canada has signed a MOU for both IT and telecom safety. The next meeting will be
September 21, 1999, in Arlington VA.
ANSI/TIA/EIA-631, RF IMMUNITY FOR A COUSTIC O UTPUT EQUIPMENT STANDARD
The decision on the choice of formats for the RF Immunity brochure is still under way. The
Brochure should be available for review at the May TR-41.7 meeting.
BROADBAND SAFETY AND PROTECTION
The Network Powered Broadband Working Group is going to be reactivated to determine if an
acceptable high power proposal can be generated. The WG will be made up of a more balanced
membership of power and cable interests. See also the T1E1.7 liaison report, above.
SP-3283A, TELECOMMUNICATIONS USER PREMISES EQUIPMENT ENVIRONMENTAL C ONSIDERATIONS
All ballot actions on SP-3283-A-3 have been completed It will be published as ANSI/TIA/EIA571-A. PN-4509 is starting the process of rescinding ANSI/TIA/EIA-571, subject to approval at
the TR-41 Plenary.
March-April 1999
55
TR-41.7.1, HARMONIZATION OF INTERNATIONAL SAFETY STANDARDS
BI -NATIONAL SAFETY STANDARD, UL-1950/CSA-950
The last meeting of the BNWG (Bi-National Working Group) was December 8-10, 1998. A formal
report was not available. J. Brunssen (Bellcore) attended the meeting and was accepted as a
member representing the carriers through ATIS. C. Tenorio and P. Taver (as TIA
representatives) also attended the meeting. Proposals for the next revision were completed.
These include increasing the maximum voltage for TNV (Telephone Network Voltage) from 60
volts to 80 volts and improving the test procedure for ring trip current measurement. TR41.7.1/98-11-20 (from the previous meeting) contains a list of technical topics and their respective
discussions, proposals and rational for the BNWG to consider. The changes proposed by the
BNWG will be reviewed April 7-8. It was proposed that UL 1950 be changed to UL 60950
(60950 is the IEC designation) third edition for the next revision.
LISTING TELECOMMUNICATION CO EQUIPMENT TO UL 1950
TR-41.7.1/99-02-03, Impact of Transition to UL 1950 on CO equipment (J. Weise, Adtran),
contains copies of e-mail correspondence between Adtran and various parties including UL,
discussing the listing of various standard shelves and the corresponding cards used by the
telecom industry. All of this equipment is owned by the carrier although some is located on
customer premise. The NEC (National Electric Code) does not require listing of telecom carrierowned equipment as long as it is not on the customer premise. The requirements for co-location in
the Telecommunications Act of 1996 is causing many carriers to require listing of all new
equipment.
In many cases hazardous voltages are present in this equipment in the form of non-cadenced
ringing and/or remote power feed telecommunication circuits with voltages up to 200 volts to
ground. The creepage and clearance requirement for these lines in UL 1950 exceed those in the
shelves and external cable connectors. The requirements for separation in UL 1459 are
demonstrated using dielectric breakdown tests. These shelves and cards meet the UL 1459
requirements which are grandfathered until 2005. Any cards with new technology cannot be
listed to UL 1459 after March 15, 2000. While the technology to design these products to meet
UL 1950 is available, the new products will likely be larger, cost more, and will require new
shelves.
The two avenues for addressing this issue is the BNWG through TIA TR-41.7.1 and UL through
the IAC for 1950 and/or 1459. Two changes (not an exclusive list) which would address this issue
are 1) Extend the listing date for UL 1459 and add CO and telecom network equipment to the
scope, or 2) Expand the scope of UL 1950 to include CO and telecom network equipment and add
deviations for creepage and clearance requirements for this equipment.
TR-41.7.1 requested that all interested parties provide a contribution(s) which lists their
respective issues so that a better understanding of the magnitude of the problem could be
determined.
IEC 60950 (INTERNATIONAL)
There was no report of IEC activities. TR-41.7.1 expressed concern that this is becoming a
problem. The next US TAG will be held March 23-25 in Fort Lauderdale FL.
The In-Country deviations and levels are defined in a document from the CB Scheme organization
(The Certification Body Scheme of the IECEE for Mutual Recognition of Test Certificates for
Electrical Equipment); it is available at http://www.cbscheme.org. A. Bal (CSA) volunteered to
bring what is available to this meeting. The CB Scheme was originally developed for the safety
standards prepared by the then European organization CEE. In 1985, the CEE and its
Certification Body and Committee of Testing Laboratories was integrated into the IEC as the
IECEE.
56
March-April 1999
R. Ivans (UL) provided a copy of the FDIS (Final Draft International Standard) of IEC 60950 to
some members of TR-41.7 and TR-41.7.1 via an e-mail attachment.
ETR 300-012, CENELEC DOCUMENT ON CLASSIFICATION OF INTERFACES
There was no contribution on the CENELEC (Commission Europeenne de Normalisation
Electrotechnique: European Electrotechnical Standards Committee) document; the second part of
TR-41.7.1/99-02-04 is an IEC TC-74 document which provides guidance on the classification of
interfaces in accordance with the circuit types in IEC 60950. It was provided for information.
C OAX SURGE REQUIREMENTS
TR-41.7.1/99-02-04 contains two separate documents. The first three pages compare the
requirements for lightning and power cross in coaxial outside plant from Bellcore GR 1089
(Electromagnetic Compatibility & Electrical Safety - in process), UL 497C (Protectors for Coaxial
Communications Circuits - 1998) and CCITT K.17 1988 (Tests on power-fed repeaters using
solid-state devices in order to check the arrangements for protection from external interference).
The second document is a draft proposal for the Safety Classification of Interfaces for
Telecommunications equipment from IEC TC-74. Both were provided for information.
TR-41.7.2, BONDING AND G ROUNDING
DISCUSSION OF JOINT TR-41.7.2/T1E1.5 & T1E1.7 MEETING (MARCH 10, 1999)
The applicability of the proposed agenda to the joint TR-41.7.2/T1E1 meeting was discussed. R.
Keden (ERICO) stated that the proposed agenda is acceptable for this TR-41.7.2 meeting, but
may be inappropriate for the joint meeting. One should not expect the joint TR-41.7.2/T1E1
meeting to get into a detailed review of the TIA-607 revision (see PN-4351, below). N. Tullius
(Astec) stated that grounding issues will be discussed: there should be harmonization of
terminology between the T1E1 bonding and grounding standard and TIA-607. Therefore, two
areas of concern will be discussed at the joint meeting: length of the primary protector grounding
conductor and harmonization of grounding and bonding terminology.
The May 1999 TR-41.7.2 meeting schedule was discussed. WG consensus was that a May 1999
meeting of TR-41.7.2 is necessary so that work on the revised TIA-607 can begin in earnest. The
WG felt that the joint TR-41.7.2/T1E1 meeting will review proposals for revision of TIA-607 and
seek T1E1 concurrence, but that no real re-writing of the TIA-607 standard will be performed at
the joint meeting.
VERTICAL G ROUND RISER ISSUES
N. Tullius (Astec) discussed TR-41.7.2/99-02-002, Vertical Ground Riser Issues. A major issue
is: do we need a copper ground riser conductor or can we use building steel? Rebars
(reinforcement bars) in a steel reinforced concrete building could conceivably be used. The
general perspective appears to be that a welded steel frame building is OK. Steel reinforced
concrete construction is not generally acceptable as a ground riser because the wire-wrapping
technique used to connect segments of the rebars do not ensure adequate electrical conduction
between rebars. TR-41.7.2/99-02-002 makes the case for a separate vertical ground riser
conductor and suggests the size (wire gauge). Sizing should consider the available power fault
current, and the conductor should be sized to carry approximately 10 times the rated device
(breaker) current for a short time. A No. 6 AWG (American Wire Gauge), minimum and up to 3/0
should be considered for low-rise buildings, larger for high-rise buildings. A discussion ensued
regarding sizing of the riser conductor as a function of the building height. It does not seem
intuitive that the riser cross-sectional area has to increase as a function of building height. TR41.7.2/99-02-002 makes no specific recommendation for TBB (Telecommunications Bonding
Backbone) size. TR-41.7.2 consensus was to revise TIA-607, Clause 5.3.4.1, as follows: Retain
March-April 1999
57
first and second sentences, revise third sentence to state: “The TBB should be sized at 2 kcmil
(kcmil = 1000 circular mills or 0.001 sq. inch) per linear foot of conductor length.”
G ROUNDING & BONDING TERMINOLOGY
TR-41.7.2/99-02-003 (N. Tullius, Astec) extols the benefits of harmonization with ITU
Recommendation K.27 (05/96) - Bonding configurations and earthing inside a telecommunication
building. The contribution contains a cross-reference table of grounding and bonding terminology
used in various standards. It suggests that terminology in TIA-607 be revised to harmonize with
ITU K.27. A table could be provided, such as is included in the contribution, in the style of TIA607, Annex A. It was suggested that the table have three columns:
• TIA-607
• International
• Others
CLAUSE 5.3, SPLICING OF TBB
TR-41.7.2/99-02-004 (P. Pool, GTE), notes there appears to be a conflict between clauses 5.3.4.3
and 5.3.5.2. Clause 5.3.4.3 states that the TBB may be spliced; clause 5.3.5.2 states the TBB
conductors should be installed without splices, where practicable. TR-41.7.2/99-02-004 suggests
that clause 5.3.4.3 be deleted and that clause 5.3.5.2 be revised to state that the number of
splices should be a minimum. The proposal was accepted.
G ROUND BAR BOLT HOLE SIZING/SECONDARY TELECOM SURGE PROTECTION
Ground Bar: The objective of TR-41.7.2/99-02-005 (R. Keden, ERICO) is to standardize and
reduce the number of different ground bars that must be stocked. A BICSI contribution will
follow.
Secondary Surge Protection: There is a need to provide a grounding means for telecom secondary
protectors at patch panels. TR-41.7.2/99-02-005 proposes to add text to TIA-607, clause 4.1.
Upon review of the proposed text, N. Tullius (Astec) stated that he felt that the language of the
first sentence is too strong, implying that manufacturers are now designing and providing
equipment that is more susceptible to damage. TR-41.7.2 concurred with the deletion of the first
sentence. TR-41.7.2 also expressed concern that the reference to patch panels is equipmentspecific. The following text was suggested to cover grounding of the secondary protector:
“It is beyond the scope of this standard to specify secondary protection. When provided, the
secondary protector grounding conductor shall be connected to the nearest telecommunications
grounding busbar (e.g., TGB, TMGB), using the shortest grounding conductor practicable.”
TR-41.7.2 consensus was to insert this sentence as clause 4.1.3, and renumber existing clauses
4.1.3, 4.1.4, and 4.1.5 as clauses 4.1.4, 4.1.5, and 4.1.6, respectively. Clause 2.2(e) is revised to
state: “(e) Protector/arrester specifications and applications.”
PROPOSED ELECTRICAL PROTECTION A NNEX
TR-41.7.2/99-02-006 (J. Brunssen, Bellcore) proposes an informative Annex C to provide general
information concerning the primary telecommunications protector and to direct the reader to both
ANSI T1.318 (Electrical protection applied to telecommunications network plant at entrances to
customer structures or buildings) and the National Electrical Code for specifics regarding its
application and grounding. TR-41.7.2 accepted the proposed contribution with five minor
revisions.
PN-4351, REVISION OF ANSI/TIA/EIA-607-1994
PN-4351 is Commercial Building Grounding and Bonding Requirements for Telecommunications,
to become TIA-607-A. TR-41.7.2/99-02-007 (L. Baker, RELTEC) proposes changes to the sheath
58
March-April 1999
fire rating of the insulation of the TBB (Telecommunications Bonding Backbone) in section 5.3.4.
During the review of TR-41.7.2/99-02-007, a discussion arose as to whether the TBB (riser) needs
to be insulated. It was stated that the NEC requires the primary protector grounding conductor
to be insulated. The NEC rules should be reviewed and the appropriate requirements placed in
TIA-607.
LeRoy Baker, RELTEC
TR-41.8, COMMERCIAL AND RESIDENTIAL PREMISES WIRING
TR-41.8 has become TR-42. See report in this issue.
TR-41.9, TERMINAL ATTACHMENT PROGRAMS
The TR-41.9 Chair, A. Wride (CCL), asked members to identify if there was knowledge of
patents, the use of which might be essential to the standard being considered. None were
identified.
C. Berestecky (TR-41 chair, Lucent) provided a summary of TR-41.9’s change in scope, as part of
the TR-41 reorganization. There are two major issues: TR-41.9 will be working more closely
with TIE1.4 and will arrange meetings to take place at the same time and place. TR-41.9 hopes
this can be done by the November 8-12 meeting. The new TR-41.11 (FCC ad hoc administrative
working group) subcommittee will be important to TR-41.9 since their scope will go beyond TR41.9. FCC has an Administration ad hoc group which will come under TR-41.11.
TAPAC, TAPAC TTF, TAPAC ATF L IAISON
H. Mar (Industry Canada) reported. On December 2, 1998, CRTC, the Canadian regulator,
issued Telecom Public Notice 98-35 on the demarcation point for inside wire in multi-tenant
buildings and associated issues. Comments and reply comments are due Jan. 18 and Feb. 1,
1999, respectively. A decision on this may come out soon.
Industry Canada has developed draft procedures for designation and accreditation of testing
laboratories. They will be finalized when the actual implementation of Phase 1 of Canada-EC
MRA takes place, estimated to be June 1999.
A TAPAC letter ballot on Stutter Dial Tone Detection Devices has been conducted with a due
date of Feb. 19, 1999. At the next TAPAC meeting comments will be reviewed and a decision will
be made.
An MOU between Industry Canada and SECOFI (Mexican Ministry of Commerce and Industrial
Development) regarding mutual acceptance of product safety test data for IT&T equipment will
be signed this week in Ottawa.
The next meeting of TAPAC will be March 3-4, 1999 in Ottawa.
IMPLEMENTATION OF TCBS
J. Wronka (Lucent) provided a summary report (TR-41.9/99-02-018) of the TCB (Technology
Certification Bodies) task group meeting on Feb. 4, 1999. Seven major tasks were assigned to
two different Task groups (RF, Radio Frequency, and TTE, Telecom Terminal Equipment).
These tasks are: Scope, Confidentiality, Probation, Competence, Documentation, Test Capability,
and Interpretations. TR-41.9/99-02-023 is a presentation on the TCB Scope (task 1), from C.
Berestecky. It describes the core set of product certification requirements for RF or TTE devices
that a TCB must demonstrate.
March-April 1999
59
FCC ACTIONS
W. Howden (FCC) reviewed the FCC Order 98-68 (TR-41.9/99-02-002, same as TR-41.11/99-02002) 1998 Biennial Regulatory Review - Amendment of Parts 2, 25 and 68 of the Commission’s
Rules to Further Streamline the Equipment Authorization Process. W. Howden made a list of
action items (TR-41.11/99-02-001). This list will be reviewed by TR-41.11 and an action plan will
be developed. There was discussion on some of the items on the list. A reference to NPRM issues
can be found in FCC Docket 98-146 and 99-05.
There is concern that FCC Form 730 is not the optimal format for use among TCBs and the
Commission; FCC’s interest in developing an electronic filing system and common data base for
electronic filing relating to Part 68 was discussed. Some of the issues were the necessary
hardware, the record keeping, cost, and enforcement.
Based on input from TR-41.9, TIA wrote to FCC to clarify Paragraph 68.317 on volume control
issues. TR-41.9 is also waiting for comments from TR-41.3 since TR-41.3 will provide the
technical expertise in this area. It was noted that the FCC might release a Public Notice shortly.
TR-41.9/99-02-006 is a notice of FCC Part 68 Subpart D corrections (Connection of CustomerProvided Terminal Equipment to the Telephone Network). It notes that Paragraph (c) to 68.300
Labeling requirements, will be added. This paragraph was inadvertently removed from the 1997
version of the Code of Federal Regulations.
FCC PART 68 ISSUES
TR-41.9/99-02-012, Stutter dial tone (E. Guevara, Bell Canada), is a letter to Mr. Bress (FCC)
commenting on the TR-41.3 proposed revision to remove what was thought to be a redundant
statement: “(1) The device performs no periodic testing for stuttered dial tone.” A. Wride
provided a summary and asked all members to review TR-41.9/99-02-012. A formal voting
process was conducted. The vote was anonymous. TR-41.9 accepted TR-41.9/99-02-012 which
proposes, “ (1) The device does not perform any testing for dial tone in absence of a dial event.”
TR-41.9/99-02-014 (R. Britt, Nortel Networks same as TR-41.1/98-11-028 see CSR Vol 10.1 for
details) proposes modifications to the TIA-464-C proposed Loss plan. TR-41.9/99-02-016, Impact
of Nortel proposed 464C Loss plan on MLTS (T. Tung, Siemens), notes that the Nortel
suggestions in TR-41.9/98-02-014 will make all 464B compliant MLTS systems fail to meet the
464C requirements. TR-41.9/98-02-014 proposes maintaining the 464B loss plan with the
changes as proposed in TR-41.9/98-02-016. Discussion revolved around Table 12 (Proposed
464C Loss Plan for ISPBX lines and private trunks). There were some concerns regarding the
work done when the original table was developed.
TR-41.9/99-02-013 is a letter from T. Tung (Siemens) to A. Write (TR-41.9 chair) on OPS Loops).
It presents an issue concerning DC current of OPS line simulator circuits. A determination was
reached that the requirement is stated in Paragraph 68.308 (c) with 20 mA limit: when testing is
conducted, manufacturers should use the test set-up outlined in Figure 68.3 (f), with 16 mA. This
is also an issue for the TSB-31-B revision.
S. Roleson (HP) provided a summary of his TR-41.9 Web Report (TR-41.9/99-02-005). It can be
found at http://www.wp.com/SRoleson. It provides resources and links from the Internet of
interest to TR-41.9.
TR-41.9/99-02-010 notes that an errata to FCC Part 68 (as harmonized with Canadian CS-03) is
needed to include inadvertent omissions related to the ISDN/PSDS (Public Switched Digital
Service) order. The adopted Part 68 as a result of FCC 97-270 (Harmonization order) did not
include changes to Part 68 made in the ISDN/PSDS order (FCC 96-1). This happened because
the TIA petition (for harmonization) was based on the Part 68 Rules prior to the ISDN/PSDS
order. A Correction Notice is anticipated from the FCC.
60
March-April 1999
TR-41.9/99-02-004 is the draft of the FCC Form 730 Application Guide, dated January 18, 1999.
G. Slingerland (Mitel) and W. Howden (FCC) worked on this document. G. Slingerland gave a
summary of their work. They developed the document from the last issue of the Guide, May
1998. The main objective was to capture all of the information and include it in the working
document. This item will be brought up in TR-41.11.
In TR-41.11/99-02-003, G. Slingerland (Mitel) notes the regulatory requirement to provide
customer instructions and required notices. However, in general practice, PC equipment
integrators buy bulk shipments from manufacturers with such written material. Some
manufacturers direct customers to their web sites to obtain this information. Mitel asked if such
practices are acceptable.
HOME N ETWORKING SIGNAL POWER ISSUES
TR-41.9/99-02-011, Consideration of non-xDSL Spectrum, Especially Home LAN (Y. Okamura,
NEC, same as T1E1.4/99-039) notes that power coupled into line (noise injection) from non-DSL,
especially HomePNA, has to be considered as part of the spectrum management and is a possible
interference source for VDSL. T. Bishop (Bell Atlantic) gave a brief summary of the contribution.
VDSL bandwidth is between 5 and 8 MHertz. This is a concern because metallic voltage
requirements cover between 4 and 6 MHertz bandwidth. One suggestion was that consideration
should be given to adding a filter. While it is technically good, it is not practical. T. Bishop will
bring information concerning the metallic voltage requirements frequency limits to T1E1.
TSB-31-B TECHNICAL/EDITORIAL C HANGES
TR-41.9/99-02-008 (G. Slingerland, Mitel) is the TSB-31-B errata list (12 items). There was a
proposal that all members review TR-41.9/99-02-008 and then TR-41.9 will vote on the errata as
amendment for publication to TSB-31-B. This proposal was accepted. G. Slingerland will reissue
the list.
J. Bipes and S. Bipes (Mobile Engineering) will bring in a contribution concerning transverse
balance requirements.
ADSL AND O THER DSLS
TR-41.9/99-02-015, Provisional Requirements and Test Methods for xDSL Terminal Equipment
(B. Corey, Industry Canada), is a draft from the working group. It sets forth the provisional
minimum network protection requirements for certification of ADSL (DMT and CAP) and HDSL
(DMT, CAP, QAM). This will be first time the Canadian Technical group sees this report. They
have to approve the draft and then pass it on to TAPAC.
The next revision of the Industry Canada draft will be distributed to T1E1.4. A request was
made from T1E1; a representative from Bell Canada will bring this work to T1E1. TR-41.9/9902-003 is the liaison letter on xDSL from E. Eckert, Chair of T1E1 to TR-41; it provides the
recommended PSD masks for G.992.1 (T1.413 issue 2, formerly G.dmt) and G.992.2 (G.lite).
J. Carlo (TI) and T. Bishop (Bell Atlantic) reported on the work being conducted by T1E1. They
are looking at the entire system, not just ADSL. They are reviewing T1, ADSL, ADSL Lite,
HDSL, xDSL etc. One thing they have determined is that for DSL, there are six bandwidth
requirements: ADSL, HDSL, high band symmetric (HDSL2), high band asymmetric, high band
normal, and very high band (VDSL). The plan is to have a system (a generic mask) to protect
different types of interfaces; their goal is to have a draft standard in June for balloting. The final
document is expected to be issued three months after that. There was some discussion on the
limitation of network harms and the compatibility of services.
More information can be found at www.t1.org. Go to file index, click T1E1, then T1E1.4
March-April 1999
61
PCM MODEM U PDATE
TR-41.9/99-02-007 (P. Adornato, Nortel, Chair User Premises Equipment Division) is a summary
of the PCM modem Ex-parte meeting on January 13. TR-41.9/99-02-024, GTE Comments to
Notes of PCM Modem Ex-parte, (H. Van Zandt, GTE), strongly opposes providing a waiver or
interim order for PCM modems until the modem manufacturers have clearly demonstrated no
harm to the network quality. (Editor’s note: see also the TR-30 report in this issue for the modem
manufacturer’s perspective.)
LOOP C URRENT
The Bellcore requirements for COs to determine current at loop state was discussed at the last
meeting. See also ANSI T1.401-1993 (Analog voicegrade switched access lines), Annex B, Figure
B.2. It was determined at that time that 17 ma was a closed loop current. All members are
asked to review this subject for discussion at the next meeting.
RING VOLTAGE
TR-41.9/99-02-020, Off Premise Circuit Ringing Voltage Measurements (E. Wright, Intertek
Testing), identifies how voltages are measured. This was in response to a question from the
previous meeting (see CSR Vol. 10.1). No further action is required from TR-41.9.
FIELD TRIAL
TR-41.9/99-02-019 (S. Plasencia, S. Roleson, HP, same as TR-41.11/99-02-004) is a proposal for
the review and documentation of the Field Trial process. HP seeks a revised field trial process
that does not limit pre-registration field trials to technical purposes only, increases the number of
test samples to the range of 30-50 units, specifies other test process elements, and allows for
rapid processing of temporary registration requests (see also CSR Vol. 10.1). This subject will be
brought to TR-41.11.
SDOC: CARRIER INVOLVEMENT
There was discussion concerning Document 98-68, item 13. Cisco, in response to the Notice,
questioned having Part 68 registration included under this Notice, as currently it is not. This
would be an extension to allow manufacturers to perform Part 68 tests and attach labels to their
products. There was concern on how this would affect the TCB Scheme.
NORTEL 1 MBITS M ODEM
TR-41.9/99-02-009 is the Nortel Petition for waiver so that it can register its Elite Modem under
Part 68.200. Nortel claims a high degree of spectrum compatibility with T1E1.4 PSD masks
(T1E1.4/98-030R1). The FCC file is DA 98-2639. TR-41.9/99-02-022 are the generally
supportive comments and reply from Nortel on the 1 Mbits modem. BellSouth was the only
commenter opposed to the Nortel waiver request; on broad-based grounds, Part 68 is no longer
adequate to prevent harm to the network. The subject is being reviewed by the FCC.
C ABLE LEAKAGE
TR-41.9/99-02-021© is an article from American Radio Relay League QST, February 1999,
decrying the use of “unsuitable cables” (i.e., telephone and power lines) for high data rate data
transmission (e.g., xDSL, HomePNA), due to RF leakage from cables and its deleterious effect on
amateur radio bands. J. Bipes (Mobile Engineering) provided the summary.
Anh T. Wride, Dir. of Engineering, CCL
62
March-April 1999
TR-41.10, PRIVATE INTEGRATED SERVICES NETWORK (PISN)
The focus of this meeting was the review and results of the ISO/IEC JTC1/SC6/WG6 Private
Integrated Services Network (PISN) meeting, TR-41.10/99-2 January 10-16, 1999, in Sydney
Australia. TR-41.10/99-02-03, TR-41.10/99-02-04 and TR-41.10/99-02-05 below are from this
meeting.
Consensus was reached on the need to press ahead with the IP/PISN interworking and trunking.
ECMA will continue the development of its Technical Report on IP/PISN interworking with input
from ISO. TR-41.10/99-02-05 is a report on PISN-IP Interoperability and Broadband PISN
Sessions. There was consensus on the need to press ahead with work on PISN/IP interworking
and trunking, including the three trunking scenarios on the table:
1. QSIG over TCP for the control plane (without using H.323 protocols) and voice over RTP/UTP.
2. Use of H.323 for basic call control and voice, but with all QSIG supplementary services
information encapsulated in H.225/H.245 messages.
3. Use of H.323 for basic call control and all QSIG supplementary services for which H.450
equivalents exist, with other supplementary services information encapsulated in H.225/H.245
messages.
In connection with the PISN/IP interworking, TR-41.10 reviewed TR-41.10/99-02-02 (M Zonoun,
Nortel Networks), a Nortel proposal on the IP performance monitoring when voice is transferred
between two PISNs across an IP network with the fallback mechanism to PSTN. Members were
asked to bring alternative proposals for discussion and contribution to the next ISO meeting in
July, 1999.
TR-41.10/99-02-04 is the meeting report of Session 2, on Scenarios and Architecture. Reference
configuration for extension lines and mapping functions for VPN were progressed and will go out
for FCD ballots. The second edition of Scenario document was reviewed and is ready for as DTR
ballot.
Name Identification (IS-13868) was enhanced to include all European character sets. PDAM1
was issued for this change. TR-41.10/99-02-03 is the meeting report for Session 1, on Services,
Protocols, and Mobility which includes this issue.
TR-41.10/99-02-06 (P. Weismantel, NEC) proposes running the Q.SIG D-channel and related Bchannel over the Switched Public ISDN network. This implementation provides a method for
connectivity to public networks when dedicated facilities are not feasible.
M. Zonoun, Nortel Networks
TR-41.11, FCC ADMINISTRATIVE COMMITTEE
Editor’s note: The TR-41.11 report was not available as we went to press. However, the TR-41.2
and TR-41.9 reports in this issue of CSR provide information on the work in this committee.
March-April 1999
63
TR-41 PARTIAL MEETING ROSTER, FEBRUARY 15 - 19, 1999, SARASOTA, FL
Chuck Berestecky, Lucent
Chair,
Chair,
Chair,
Chair,
Chair,
Chair,
Chair,
Chair,
Chair,
Chair,
Pierre Adornato, Nortel
Steve Whitesell, Phillips Consumer
Jim Romlein, MIS Labs
Peter Murray, Ericsson
Leroy Baker, RELTEC
Anh Wride, CCL
Mo Zonoun, Nortel
Ron Provost, BICSI
Adtran, Inc
Alcatel
Anritsu
ASTEC
BABT Product Service
Bell Atlantic
Bellcore
Bellcore
Broadcom Corporation
CCL
Jim Wiese
Travis Berry
Al Fisher
Nick Tullius
L. Richardson
Trone Bishop
Jim Brunssen
Jon Balinski
Rafi Rahami
Anh Wride
Cisco Systems
Cisco Systems
Christopher Saleem
James Lambert
Cisco Systems
Cobra Electronics
Comdial
Compaq Computer Corporation
Cortelco Systems Inc.
CSA
ERICO
Ericsson
Ericsson
Ericsson
Ericsson
FCC
GTE
GTE
GTE Telephone Operations
Hewlett-Packard
Industry Canada
John Combs
T. Anh
John Green
Jim Cottrell
Peter Melton
Ajmer Bal
Ray Keden
N. Asahina
Roger Liu
Peter Murray
Leigh Warren
William Howden
Jack Smith
Percy Pool
Harry Van Zandt
Scott Roleson
Robert Corey
Industry Canada
Le Khiem
Industry Canada
Intertek Testing Services
Henry Mar
Ron Bernot
G. Page
Joan Sterling
KTL-Certelecom
Lucent Technologies
Lucent Technologies
Lucent Technologies
Lucent Technologies
Lucent Technologies
Lucent Technologies
Erick Wright
David Dulmage
Charles Berestecky
Tony Caggiano
Steve Crosby
William Cruz
Mahesh Shah
William Soler
64
TR-41
TR-41.1
TR-41.2
TR-41.3
TR-41.5
TR-41.6
TR-41.7
TR-41.9
TR-41.10
TR-41.11
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected] or
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
March-April 1999
Lucent Technologies
John Wronka
Matsushita
ME Telecom
Mitel
Mitel
Mitel
Mitel
Mobile Engineering
NEC
NEC
NEC
Nortel
Nortel
Nortel
Nortel
Nortel
Panasonic
Paradyne Inc.
Raychem
Reltec Corp.
Siemens Business Comm.
Kyle Kim
Steven Bipes
Richard Haterhill
Phil Holland
John Needham
Greg Slingerland
John Bipes
Yoshihiko Miyamoto
Jim Parker
Paul Weismantel
PierreAdornato
Roger Britt
Dermot Kavanagh
Bao Tran
Mo Zonoun
Bill Scales (via
Telephone)
Peter Walsh
Al Martin
Leroy Baker
Richard Frank
W. Kammer
Jim Seippel
Stentor Resource Centre Inc.
Teccor
Telcon Associates
Thomson Consumer Products
Transition Networks
Tailey Tung
Ephrain Guevara
Phillip Havens
Dorothy Lockard
Clint Pinkham
Robert Busse
TUV
Lee Chun
UL
Anh Nguyen
March-April 1999
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected],
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
65
REPORT OF TR-42, USER PREMISES TELECOMMUNICATIONS
INFRASTRUCTURE, FEBRUARY 15 - 19, 1999, SARASOTA, FL
The TR-42 Engineering Committee was established at this meeting from the previous TR-41.9
committee. It has eight subcommittees:
Subcommittee
TR-42.1, Commercial Building Telecommunications Cabling
TR-42.2, Residential Telecommunications Infrastructure
TR-42.3, Commercial Building Telecommunications Pathways and Spaces
•Pathway Separation Task Group
•Pathway Fill Task Group
•Access Floor Task Group
•Underfloor Systems Task Group
•Poke-Thru Device Task Group
TR-42.4, Outside Plant Telecommunications Infrastructure
TR-42.5, Telecommunications Infrastructure Terms
TR-42.6, Telecommunications Infrastructure Administration
TR-42.7, Telecommunications Copper Cabling Systems
•Copper Connectors Working Group
•Copper Cable Working Group
•ScTP Task Group
•STP-A Task Group
TR-42.8, Telecommunications Optical Fiber Cabling Systems
Chair
J. Siemon (The Siemon Co.)
B. Jensen (3M)
B. Jensen (3M)
D. Ballast (BICSI)
T. Toher (IBM)
M. Lesperance (Ortronics)
M. Shariff (Lucent)
T. Beam (AMP, Inc.)
Only the first five subcommittees met at this meeting. Their reports are below.
TR-42.1, COMMERCIAL BUILDING C ABLING
Electronic contributions are available on the TIA FTP site (password protected). Currently, the
TR-42 contributions are contained within the TR-41.8 structure; the folders will be modified in the
near future.
TR-42.1/99-02-017 (J. Kee, Lucent Technologies) is a proposal for a new TR-42.1 project on
Intelligent Building Systems (IBS). The goal is to develop a standard that addresses the cabling
infrastructure of the building controls industry building on the success of structured cabling (e.g.,
Cat 5) for voice and data.
UTP SYSTEMS TASK G ROUP
PN-4292, Additional Transmission Performance Guidelines for 100 ohm 4-Pair Cat 5 Cabling, to
become TSB-95, and SP-4195, Addendum #5 to ANSI/TIA/EIA-568-A Additional Transmission
Performance Specifications for 100 ohm 4-pair Category 5 Cabling, need extensive work. Most of
this work centers around determining the correct specification for return loss and will mandate
changes to component specifications to ensure the model will work. TR-42.1/99-02-002 (S. Vaden,
Superior Modular Products) compares two 2m Category 5 patch cords. It was found that
movement of patch cords had a significant effect on return loss, to the extent that it could fail the
channel. An interim meeting is planned for March 30-31, 1999 in Phoenix, AZ, to resolve the
return loss cabling issues.
Category 6 cabling is rising in interest for national and international standards. Comments on
the PN-3727-406 and PN-3727-407 proposals are due before April 12 in order to formulate the
national position. TR-42.1/99-02-013-e and TR-42.1/99-02-014-e are important documents
concerning the international position on components. TR-42.1/99-02-013-e (H. Koeman, Fluke) is
an overview of the (new) Class D, E, F ISO/IEC 11801 specifications (Generic cabling for
customer premises). TR-42.1/99-02-014-e (H. Koeman, Fluke) is a copy of a contribution to
ISO/IEC/JTC1/SC25/WG3, an overview of proposed performance specifications for (new) Class D,
66
March-April 1999
Class E and Class F Cabling. V. Rybinski (Siemon Company) will serve as editor of the
Category 6 document.
C ONNECTOR TASK G ROUP
The Connector Task Group worked on backward compatibility and interoperability between the
future category systems and earlier category systems. A draft document was edited and will be
released as a press release. The sixth draft of the connecting hardware performance
specifications was distributed; it was agreed to roll the appropriate sections of the document into
PN-3727, the draft Category 6 specification, and into PN-4195, the Category 5e document.
Comment resolution was not held on SP-4349, Production Modular Cord NEXT Loss Test Method
and Requirements for Unshielded Twisted-Pair Cabling, because TIA distributed it too late.
Comments will be resolved at the interim meeting in March.
O PTIC FIBER TASK G ROUP
The Optical Fiber Task Group resolved comments on PN-3894, TIA-568-B.3 (see the TIA-568-B.3
Editorial report, below). A March 24, 1999, interim meeting will be held to discuss the next
generation premises cabling.
SC TP TASK G ROUP
The default ballot on SP-3193, Technical Specifications for 100 ohm Screened Twisted-Pair
Cabling, was resolved at this meeting. TR-42.1/99-02-015 is the ballot summary (43 approvals,
no “No” votes). SP-3193 was approved to be published as an Interim Standard. The plan is to
incorporate the document into TIA-568-B.2.
LIAISON REPORTS
It is possible that the 1000 BASE-T standard could be finalized by June 1999. One “No” vote is
yet in place asking for a demonstration of the technology. Although the 1000 BASE-SX standard
has been approved since last summer, a new project will likely be proposed at the next meeting
for a 10 Gigabit Ethernet system.
Optical Fiber cabling concerning Gigabit applications is planned to be discussed in Berlin at the
next SC25 WG3 meeting. The FO (Fiber Optics) Task Group will hold an interim meeting on
March 24, 1999 to provide input to SC25 WG3 for this important meeting.
EDITORIAL TASK G ROUP
TIA-568-B.1
TR-42.1/99-02-016 is a summary of the PN-4426 ballot, Commercial Building
Telecommunications Cabling Standard: Part 1, General Requirements, to become TIA-568-B.1.
TR-42.1 reviewed the technical comments. TR-42.1/99-02-009 is a copy of Section 10, Cabling
Installation Requirements. The group agreed to give the editorial comments to the editor for
resolution. The revised TIA-568-B.1 will be sent out for a second committee letter ballot.
TIA-568-B.2
TIA-568-B.2 is the proposed standard for copper cabling components that is intended to be used
by manufacturers. TR-42.1/99-02-004 is draft 2 of TIA/EIA-568-B.2, 100 ohm Unshielded
Twisted Pair Cabling Standard, dated January 7, 1999. Changes were reviewed. After the
review, the document was approved for ballot. TIA-568-B.2 will be the province of the new TR42.7 subcommittee, Telecommunications Copper Cabling Systems.
March-April 1999
67
TIA-568-B.3
TIA-568-B.3 (PN-3894) is the proposed standard for optical fiber cabling components that is
intended to be used by manufacturers. TR-42.1/99-02-007 is a draft of the optical fiber cabling
standard dated December 4, 1998 (document labeled PN-3723-1). TR-42.1/99-02-006 is the
report of the TIA/EIA-568-B Editor’s teleconference on PN-3894, on December 14, 1998.
TR-42.1/99-02-005 are Ballot comments on PN-3894 (document labeled PN-3723), from
November 1998. There were two “No” votes from EDS and Siemon. There is one outstanding
comment remaining to resolve. A conference call will be held on March 12, 1999 to discuss how
to test cables under a one-inch, no-load condition, in order to resolve the one comment of a “No”
vote. It was agreed to send the revised draft out for third committee letter ballot after resolution
of comments during the March 12 teleconference. TIA-568-B.3 will be the province of the new
TR-42.8 subcommittee, Telecommunications Optical Fiber Cabling Systems.
A proposal supported by the Fiber Optic Task Group to remove the 568-SC connector
requirement at the work area outlet did not receive consensus support for change. The vote was
14 for the proposal with 9 against. Even though this was a majority in favor of the Task Groups
proposal, it did not meet the 2/3 rule established by the committee for consensus.
TIA-568-B.4
TIA-568-B.4 is the proposed standard for screened and shielded copper cabling components,
intended for use by manufacturers. TR-42.1/99-02-010©, is a draft of Part 4: 150 Ohm Shielded
Twisted Pair Cabling Standard, dated January 11, 1999. TR-42.1/99-02-011 is a copy of the
ANSI PINS (Project Initiation Notification System) form; TR-42.1/99-02-012 is a copy of the TIA
project request and authorization form. It was agreed to have TIA-568-B.4 incorporated as an
annex to the B.2 draft prior to release as a committee letter ballot. TIA-568-B.2 and B.4 are
both the province of the new TR-42.7 subcommittee, Telecommunications Copper Cabling
Systems.
TR-42.2, RESIDENTIAL & LIGHT COMMERCIAL PREMISES DISTRIBUTION
TR-42.2 has responsibility for TIA-570-A, Residential and Light Commercial Telecommunications
Wiring Standard.
Ballot resolution was held on SP-3490-C (ballot version: TR-42.1-99-02-00), Proposed TIA-570
Addendum A-4, Production Modular Cord NEXT Loss Test Method and Requirements for
Unshielded Twisted-Pair Cabling. TR-42.2/99-02-003 is a compilation of the Ballot comments.
Overall there were 23 technical comments from thirteen companies. Three companies voted “Yes”
with comments (Lucent, Bellcore and Leviton), while Siemon voted “No” with comments. Seven
other companies voted to approve the standard without comments, and two companies had no
comment. The comments were reviewed, the proposed standard updated, and the resolution to
the ballot comments compiled. Two definitions were at question during ballot resolution. TR-42.2
agreed to accept the outcome from TR-42.5. The one “No” vote was resolved in the meeting with
the company present and to their satisfaction. The results of the resolution of comments require
that a default ballot of the document is necessary. TR-42.2 reached consensus on a default ballot
of SP-3490-C.
An issue was raised over specifying category 5e within the residential standard since there is not
such a document released today - rather there is work still being done on this document in TR42.1. TR-42.2 decided to wait until the May meeting to determine how to handle this issue.
TR-42.2 also approved a liaison to send the draft residential cabling standard to the US TAG for
use with the international SOHO document.
TR-42.3, BUILDING PATHWAYS AND SPACES FOR TELECOMMUNICATIONS
TR-42.3 has responsibility for TIA-569-A. P. Kreager (KAI) announced that he is stepping down
as chair of TR-42.3 and that B. Jensen (3M) agreed to become the chair. P. Kreager will continue
68
March-April 1999
to participate in the group. B. Jensen thanked P. Kreager for all his hard work on TIA-569 and
for resolving so many issues since the beginning of the work on this document.
P. Kreager introduced M. Lesperance of Ortronics as the new chair of TR-42.6,
Telecommunications Infrastructure Administration, responsible for TIA-606-A. The restructure
of TIA-606 is planned to incorporate a choice of the areas that an end-user would like to have
documented such as just the cabling, or just the pathways, or everything. A news release will be
sent out to invite contributions and participation in TR-42.6.
PATHWAY FILL TASK G ROUP
B. Jensen reported that the Pathway Fill Task Group is working on cable tray fill. He read an
outline that the group will be working on for the addendum. Ballot resolution on SP-4125-2,
Furniture Pathway Fill Addendum and SP-4126-2, Perimeter Pathways Addendum will be held
until the next meeting.
UNDERFLOOR SYSTEMS TASK G ROUP
P. Kreager reported that the Underfloor Systems Task Group intends to have a draft for the May
TR-42.3 meeting.
A CCESS FLOOR TASK G ROUP
The Access Floor Task Group is not ready to proceed with ballot resolution to SP-4198-1,
Amendment to Access Floor Section of ANSI/TIA/EIA-569-A.
POKE-THRU DEVICES TASK G ROUP
S. Bambardekar (Wiremold) reviewed comments concerning the draft addendum on poke-thru
devices. After the review of comments, the document was displayed on a screen and edited.
After the editorial review, S. Bambardekar agreed to obtain one technical comment resolution
and to send the document to B. Jensen for balloting. B. Jensen will also initiate a Project Request
(ANSI PINS) Form with TIA.
TR-42.4, CUSTOMER-OWNED OUTSIDE PLANT
The work of TR-42.4 was completed at the last meeting. It was reported, however, that the
Customer Owned Outside Plant Telecommunications Cabling Standard and its addendum #1 are
on the way to being published.
TR-42.5, DEFINITIONS
Several terms had been submitted to resolve ballot comments on the pending Residential Cabling
Standard. TR-42.3 asked TR-42.5 to review the term “telecommunications closet” to ascertain
whether it should be replaced by the term “telecommunications room.”
Bob Jensen, dbi
THE CSR LIBRARY
Subscribers may order copies of documents shown in boldface type from Communications
Standards Review, where not controlled. Documents listed with © are controlled
documents. These documents are not for sale, but we can provide you with the author’s
contact information. -e means we have electronic copy only; +e means we have electronic
and hard copy available. We have a large library of standards work in process and can
help you locate other information you may need.
March-April 1999
69
REPORT OF Q21/15, TRANSPORT NETWORK EQUIPMENT FOR
INTERCONNECTING GSTN AND IP NETWORKS,
FEBRUARY 17 - 18, 1999, SAN FRANCISCO, CA
Question 21/15 (Functionality and Interface Specifications for GSTN Transport Network
Equipment for Interconnecting GSTN and IP Networks) was chartered at the October 1998
meeting of SG15 in Geneva. This was the first meeting of Question 21 since its approval. J.
Skene (Tellabs) is the rapporteur. The purpose of the meeting was to agree upon the terms of
reference and to advance the drafting of Recommendation G.TIGIN, Transport Network
Equipment for Interconnecting GSTN and IP Networks.
SFO 21-1 is the meeting Agenda. SFO 21-3 is the list of attendees. There were 34 participants.
The home page for the question is in the SG15 web site:
http://TIESid:[email protected]/u/tsg15/sg15/wp2/q21/q21_index.htm.
SFO 21-2 is the list of documents. There were 15 contributions. All referenced documents are
available on the ITU web site at:
http://TIESid:[email protected]/u/tsg15/sg15/wp2/q21/meetings/9902_SanFran.
The Rapporteur indicated that, in order to achieve the progress desired, he expected much of the
work in this question to take place via the existing ITU e-mail list. His intention is to set up a
discussion group to allow continuous availability of electronic discussions. An e-mail request has
been sent to TSB-EDH services. Attendees were encouraged to join the Q21/15 mailing list, by
following the instructions on SG15’s new EDH page, at http://www.itu.int/ITU-T/com15/edh/or by
sending an email to [email protected] with the content: subscribe tsg15q21 your_email_address.
E-mail subscription may require an ITU TIES account. It is the understanding of the WP2
chairman (D. Sparrell, AT&T) that any participant, whether or not they are an ITU member,
may obtain a TIES account. Request for a TIES account may be obtained from the TIES
Helpdesk at [email protected], Tel: +41 22 730 6666.
The Rapporteur would like to work towards holding paperless meetings, where all documents are
available electronically well before the meeting. To this end, he requests that any contributions
for future meetings be sent not only to the ITU but also to the Rapporteur. He will then put them
on the Q21/15 web site, where all delegates may download them and read them prior to the
meeting.
SFO 21-4 contains the revised text of Question 21, relative to that approved at the last SG15
meeting. It was explained that there were several changes in wording from the original to clarify
what would and would not be covered in this question. It suggests liaison with ITU-T SGs 4, 7, 8,
11, 12, 13, 16, ITU-R TG8/1, IETF transport areas, IMTC VoIP, ETSI TIPHON, and ANSI
T1A1. Comments were received that additional standards bodies should be considered for
liaison, including the Multi Service Switching Forum (MSSF), Network Access Server
Requirements for the Next Generation (NASRNG), IETF SS7 group, the ATM Forum and the
IETF AVT group.
It was mentioned that a diagram illustrating the relationship of this question to other standards
organizations would be useful. The Rapporteur will develop this and post it for discussion.
During the discussion, the group made it clear that it would not be Q21/15’s main task to develop
new protocols for TIGIN equipment, but rather to identify those that are relevant and to suggest
modifications where necessary to the responsible body. It may be necessary to develop
“etiquette” rules, for example on how to negotiate which protocols are to be used in certain
circumstances, if none are otherwise available.
70
March-April 1999
SFO 21-10 (D. Sparrell, AT&T) suggests terms of reference for the work in Q21/15, and assists
in determining what is inside and what is outside of the scope of the Question. It was pointed out
that RFC1619, which is referenced by this document, is now obsolete.
SFO 21-10 also includes a list (acknowledged to be incomplete) of relevant standards that may be
referred to in G.TIGIN. It was decided to build an on-line, comprehensive list of such standards,
with pointers to the standards themselves. The Rapporteur will initiate this, and requests
assistance from all interested participants. Signal processing Recommendations to be added
include G.168, G.169, G.763-768 and G.776.1.
The general content of section 2, List of Recommendations of Potential Interest, will be included in
G.TIGIN. SNMP will be added to the TMN standards referenced in section 2.7, and will appear
in a section titled “OA&M Interfaces.”
In discussing Section 3, which describes the scope of G.TIGIN, it was agreed that G.TIGIN will
apply to bulk conversion from GSTN - IP, rather than support Single User Devices (SUDs)
directly.
It was agreed that Question 21/15 would not attempt to develop a new functional architectural for
TIGIN equipment, but would use existing architectures, such as the decomposed model being
developed within SG16. It may be necessary to develop an equipment architecture. The basic
content of G.TIGIN will focus on what TIGIN equipment should do, and not how it should do it.
It was clarified that as G.TIGIN covers GSTN interfaces on the “TDM” side, it would also
necessarily cover ATM interfaces here. There was a general agreement that this would include
support of AAL1, not AAL2. Contributions are invited on how G.TIGIN would support ATM on
the IP interface side.
G.TIGIN will need to include some coverage of billing, but only to the extent of capturing and
making available information that may be needed to support billing in another device.
SFO 21-5© is the first draft version of G.TIGIN, in outline form. It was agreed to include a
diagram of a “decomposed” media gateway (similar to that in Figure 1 in the Q11-14/16 report,
above). It is expected that a discussion and refinement of this diagram will take place between
now and the June SG15 meeting via electronic means.
It was decided not to include the text of section 2 (General Description of GSTN TIGIN) in
G.TIGIN. The application diagram indicated as Figure 1 (Functional Location of TIGIN
Equipment) will be moved to an Appendix. The title “Voiceband Traffic Interface” will be changed
to “Bearer Interface.” Section 4, Interfaces, will be moved ahead of section 3, TIGIN
Functionality. Sections 5 (Interworking), 6 (Speech Quality) and 3 will be combined. The term
“Signaling” will be changed to “Call Control” to help differentiate it from equipment control, or
OA&M.
The draft Recommendation G.TIGIN will be broken into several sections by the Rapporteur, each
with a separate document name and revision level. Electronic discussion will take place on a
section-by-section basis. This will obviate the printing of large, unchanged sections of text as the
entire Recommendation progresses towards Determination.
SFO 21-8, Functions related to telecommunications equipment for interconnecting GSTN and IP
networks (D. Parola, B. Abbot, Y. Tao, Lucent), presents features and functions that would be
incorporated into TIGIN equipment, as well as a proposed draft layout of G.TIGIN.
The figure in Section 1.1 (functional block diagram) will be used, but will contain only the
functional elements indicated in SFO 21-8, and not the interconnecting lines. A statement will be
added indicating that the functional elements illustrated indicate functions performed by TIGIN
equipment, and do not specify how they are implemented.
March-April 1999
71
Section 1.2, Abbreviations, will be incorporated into G.TIGIN.
Section 2.1, TDM Interfaces, is not complete, and other interfaces may be added. This will be
organized by line rate, such as 1.544 Mbps, 2.048 Mbps, etc., and by line coding - G.704, ATM,
etc. Contributions are invited.
Section 2.2, IP Interfaces, was accepted. Contributions are invited on details describing the
interface at the IP side of TIGIN equipment.
Section 3, Control Interfaces: It was agreed that packet size of each direction should be
negotiable. Contributions are invited on allowable packet sizes.
The phrase “for example” will be added to the second section of 3.1 (Per Call Control), as the list
is not all-inclusive. Contributions are invited on other functions of PCC control.
A discussion on editor’s notes took place, with the decision that these would be used specifically
by the editors of the various sections to capture “immature text.” Notes on future work that is
needed in various sections would be included not as editor’s notes but rather in the overall
workplan for Q21/15, maintained by the Rapporteur. This will be developed and published well
before the next meeting. Active discussion on this workplan is encouraged, as it will be the main
driver for development of Recommendation G.TIGIN.
Section 4, Internal Functions, provides a good starting point for G.TIGIN text. It was decided
that Announcements would be optional in TIGIN equipment.
A section on Signaling Classification will be added. It will describe how voice, fax, data, tones,
etc., are detected and handled. Contributions are invited.
A description of codec characteristics relating to tone transparency was agreed upon.
Contributions are invited.
It was agreed to use the term voiceband data, which in turn would be broken down into speech,
data, and facsimile.
In section 4.2 (Echo Cancellation), it was agreed to add the item “tail capacity” to the list.
It was agreed that section 4.3 (Connection & Routing) would not be added to G.TIGIN draft text.
Section 4.4, Packetization, was felt to contain a more specific description than is necessary of the
way in which a TIGIN would work. It will not be included. Contributions on alternate wording
for the content of this section are welcome.
Section 5, Performance/Interworking, will be included in an appendix at this time, in order to not
lose some valuable content. Specific comments on this section should be made on the discussion
list and sent in as contributions to the next meeting.
SFO 21-9, Definitions for G.TIGIN (D. Sparrell, AT&T), proposes some definitions and a
glossary. This section will eventually be included with G.TIGIN text, but for the time being will
be maintained as a separate document. SFO 21-9 will form the basis for this document.
SFO 21-6, Pre-Standards Check of functionality (G. Mariano, AT&T), received strong support.
It proposes that certain features in compression equipment (e.g., compression algorithms such as
G.726, G.728 and G.729, and fax remod/demod such as G.766) be evaluated to verify
functionality before completing the corresponding Recommendation’s final approval. It was
agreed to use procedures similar to those described here as G.TIGIN nears completion. The
contribution will remain on-line for future reference.
72
March-April 1999
SFO 21-7, Proposal for a New Study Item on IP-based Channel Multiplexing Equipment (Y.
Yamada, T. Oda, KDD), proposes the standardization of an IP-based DCME. It is closely
associated with Q13/16, but coordination between Q6/11 and Q21/15 will also be necessary, as
there is expected to be considerable similarity between IP-based DCMEs and TIGIN equipment.
It was noted that an IP-based DCME would add more delay than current DCMEs; this will need
to be taken into account in the delay budget on international links.
SFO 21-11, TIGIN Equipment Arrangements (D. Sparrell, AT&T), was presented as background
information. It will be included in an appendix, but must be reviewed periodically to ensure that
the diagrams are up to date.
It was agreed to use SFO 21-12, Study Items, as a starting point for a Q21/15 study item list.
This list will be kept separately from G.TIGIN, and will be used as guidance on unresolved issues.
G.TIGIN
Draft 1 of G.TIGIN will be generated based on the agreed contributions in this meeting. It will be
available in the FTP area of SG15 in the WP2 stable_text area as g_tigin-rev1.doc. An e-mail
will be sent to Q21/15 participants when this is available.
LIAISONS
There was one incoming liaison, from ITU Qs11-14/16, in SFO 21-13. It describes relevant work
being done in these questions, and notes their desire for cooperation and coordination with SG15
in the area of service requirements, quality of service, and testing of PSTN to Internet Protocol
gateways. Q11-14/16 said about Q21/15’s charter: “This is very timely work which is
immediately relevant to a growing trend of transmitting voice over IP networks.”
A return liaison was sent back to Q14/16 (SFO 21-14), indicating that Q21/15 has modified the
original text of the Question for purposes of clarity; it notes where this revised text can be found
on the web site.
FUTURE W ORK
It was agreed that the schedule for release of G.TIGIN would be discussed at the next Q21/15
meeting in June. Work will continue on the refinement of the terms of G.TIGIN and on its content
through the Q21 mailing list.
March-April 1999
73
Q21/15 MEETING ROSTER, FEBRUARY 17 - 18, 1999, SAN FRANCISCO, CA
Jerry Skene, Tellabs
Hosts: Ditech, Sprint and Siemens
Company
ADC Telecommunications
Ascend Communications
AT&T
AT&T
AT&T
BT
Communications Stds Review
Communications Stds Review
Deutsche Telekom
Ditech
DSPG Ltd.
ECI Telecom
ECI Telecom
Ericsson
France Telecom-CNET
GL Communications
GL Communications
KDD
KDD
KDD
Lucent Technologies
Lucent Technologies
Lucent Technologies
MCI
Mitsubishi
Nokia
Nokia IP Telephony
Nortel
Salix Technologies
Sprint
Tellabs
Tellabs
Tellabs
74
Q21/15 Rapporteur
Participant
Matt Noah
Matt Holdredge
Gonzalo A. Mariano
Steve Phillips
Duncan Sparrell
Bob Reeves
Elaine Baskin
Ken Krechmer
Harald Kullmann
Tom Oshidari
George Skorkowski
Meir Leshem
Gil Levy
Tonu Trump
Valérie Turbin
Vijay Kulkarni
Kerry Wilson
Toshikane Oda
Hideaki Yamada
Yasuyuki Watanabe
Dario Parola
Avi Perry
Ying T. Tao
Robert Born
Yushi Naito
Tommi Koistitnen
Melinda Shore
Dominic K. C. Ho
Ken McInerney
Marchan Tokugawa
Charles E. Balogh
Maurice Givens
Jerry Skene
Email
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Dspg.co.uk
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
March-April 1999
REPORT OF ETSI TM6, ACCESS TRANSMISSION SYSTEMS ON METALLIC
CABLES, FEBRUARY 22 - 26, 1999, VILLACH, AUSTRIA
H. Frizlen (Ericsson) is the chair of ETSI TM6. This meeting included a parallel session of the
ANAI group and ad hoc meetings for SDSL line code platform and for the VDSL open issues.
TD-00 is the list of TDs available as of February 19. TD-02 is the list of ETSI Work Items
assigned to TM6.
The following permanent documents apply to this TM6 meeting:
TM6(98)05
TM6(98)06
TM6(98)07
TM6(98)08
TM6(98)09
TM6(98)12
TM6(98)13
TM6(98)14
TM6(98)15
TM6(98)19
980p05r4.PDF Living list for DTS/TM-06003-1 (VDSL)
980p06a2.pdf Current draft of DTS/TM-06003-2 (VDSL)
980p07r4.PDF Living list for DTS/TM-06003-2 (VDSL)
980p08a0.pdf Current Draft of DTS/TM-06011-1 (SDSL)
980p09a3.pdf Living List for DTS/TM-06011-1 (SDSL)
not available Current RTS/TM-06006 (TS 101 388 v1.2.1) ADSL
not available Living List for RTS/TM-06006 (ADSL)
980p14a0.pdf Current draft of RTS/TM-06012 (Broadband NT)
980p15a1.pdf Living List for RTS/TM-06012 (Broadband NT)
980p19a0.pdf Report of ANA meeting in Bonn
T1E1 LIAISON
J. Boström (Ericsson) gave a short account of the last T1E1 meeting (December 1998) dealing
mainly with HDSL2, and spectrum management. T1E1 also spent time preparing documents
going into ITU-T for approval.
ITU SG 15 QUESTION 4 LIAISON
D. Stuart (3Com, Q4/15 Rapporteur) gave a verbal report of the last Q4/15 meeting in Sunriver,
Oregon, January 1999. The VDSL work seems to be moving toward several separate documents
such as G.hs, G.framing, and G.line code. D. Stuart still hopes that an agreement may be
reached on a single line code for VDSL. This “multiple” document could very well apply to ETSI
SDSL.
ATA LIAISON
Several liaisons have been exchanged between ATA and TM6. TD-09, Ad-hoc Group ATA-TM6ERM on xDSL issue (G. Zedler, DTAG), requests TM6 experts to attend the March ATA
meeting. J. Besseyre will attend the forthcoming ATA meeting in Sophia Antipolis and will
report to TM6 at the Grenoble meeting in May.
ERM LIAISON
No formal liaison has been established; ERM (EMC and Radio spectrum Matters) was supposed
to send an expert to TM6 meetings. J. Besseyre mentioned that ERM has been appointed as the
focal group for ETSI for the RTTE New Directive from the European Commission; he noted the
applicability of the RTTE Directive to xDSL equipment.
FSAN LIAISON
WD-03 is a liaison from FSAN responding to the liaison TM6 sent to them (November 27, 1998).
LIAISONS FROM TM6 TO O THER BODIES
WD-08 contains the ETSI TM6 comments on current G.shdsl open issues, in reply to ITU-T on
SDSL. WD-17 (P. Brackett, Adtran; J. Hausner, Siemens) is another proposal to promote PAM
March-April 1999
75
16 as the preferred ETSI TM6 line code; this proposal was not accepted by TM6 Chair who
stated that it was premature.
WD-25 is the draft liaison to ITU-T on answers to questions on VDSL. WD-26 is the liaison to
FSAN on VDSL.
O THER BUSINESS
In honor of Austrian-born Goettfried Ungerboeck, WD-21 proposes a resolution to name TCM
(Trellis Coded Modulation) Ungerboeck Coded Modulation (UCM) in all ETSI documents. ETSI
TM6 adopted it unanimously.
SDSL
SCOPE REFERENCE M ODEL
TD-34 (S. Schmoll, Alcatel) contains comments to multiple proposals for SDSL that were
presented at the last meeting.
TD-27, Compatibility of SDSL Systems (A. Ehre, FT/DTAG), requests that the requirement of
compatibility (and exchangeability) between SDSL systems and chip sets produced by different
sources be emphasized in the SDSL TS part 1. Interoperability of multiple manufacturers’
equipment must be one of the main tasks in the SDSL TS part 2.
TD-41, Class of services for SDSL (M. Kimpe, Siemens), proposes two classes of services - Class
I: transceivers between 384 kbit/s to 2304 kbit/s, and Class II: transceivers offering all rates up
to max (TBD). TM6 agreed to create a new study point for this; contributions are invited.
TD-45, Consistent Data Rates for SDSL with ANSI and ITU (D. Daecke, Siemens), proposes
optimum payload bit rates for SDSL systems. Transmission at 384 kbit/s for residential users
and at 2048 kbit/s for business use is essential for SDSL. Since consistency with ANSI rates and
the flexibility to include further services are important factors for the future success of SDSL,
data rates with 8 kbit/s granularity are proposed. SDSL systems with 8 kbit/s granularity can
be realized at the same cost as systems with 64 kbit/s granularity. What is actually needed is
n*64kbit/s +8 kbit/s at some pre determined bit rates such as T1. TM6 agreed to create a study
point for this.
TD-15 (M. Meninger, SPT Telecom, Czech Republic) proposes modifications (up to 6 B channels
and multiplexing in the V5.1 format as well as Nx64) of the SDSL reference model resulting from
service demand analyses of SPT Telecom’s SOHO customers. It also proposes to move
information concerning SDSL network applications and relevant structure into informative
Annexes.
WD-19 (L. Humphrey, Nortel Networks) proposes text for the SDSL reference model; not all
delegates agreed on the model which introduces new requirements not expressed by operators.
WD-22 (G. Eisler, Conexant) proposes 11 bit rates (208 - 2320 kbit/s) for SDSL granularity; this
WD needs study by the delegates.
TEST LOOPS/PERFORMANCE
TD-5, (A. Carrick, Ascom AG) SDSL: comments on the test loops of Vienna TD-27 (see CSR Vol
9.8 under ADSL), suggests, on the basis of TS101 135 experience with HDSL performance tests,
that two additional cases are required, in addition to the proposed a minimum test loop set for
SDSL proposed in TD-27 of Vienna (984t27):
• A long large diameter cable (e.g., 0.8 mm PE)
• A loop exhibiting a very low input impedance (< 50 ohms) at some frequencies.
76
March-April 1999
TM6 was not convinced of the need to add test loops especially if it is to measure performances
without noise.
TD-18, Wire lines and Test Loops for SDSL (J. Eyres, Consultronics), suggests that wire lines
already specified by TM6 be used for SDSL testing in lieu of new ones, particularly the test loops
outlined in TD-27 of Vienna (984t27). TM6 generally agreed with this proposal.
TD-28 (L. Tempestilli, L. Magnone, Telecom Italia) is a proposal to include bridged taps in the set
of DLL physical characteristics for the Single Digital Subscriber Line transmission system and,
as a consequence, to define adequate testing scenarios and procedures. This was also requested
by Spain at a previous meeting. TM6 agreed to add some test loops with bridge taps (only for
SDSL, not for VDSL).
POWER SPECTRAL DENSITY
TD-04, Swiss limitations on PSD (A. Carrick, Ascom AG), summarizes the Swiss regulatory
authority’s current limits for the Power Spectral Density of SDSL systems. These can be used as
an upper bound for the PSD of any optimal line code chosen for SDSL. TM6 rejected this
proposal as a starting point for the PSD. A new study point for PSD mask in part 1 was created;
L. Magnone is the owner of this study point.
TD-44 (D. Joffe, Adtran; J. Hausner, Siemens) examines practical low frequency cut-off in real
systems using transformers; it concludes that cutoff frequencies approaching 1 kHz are practical
with compact transformers.
TD-08, SDSL power cut-back offers significant performance improvements (J. Stiscia, Alcatel; H.
Takatori, Level One), notes that performance improvements in HDSL2 and FDM ADSL are
possible with an HDSL2 power cutback. Simulations and lab measurements show that the
ability to reduce the HDSL2 output power for each line individually can lead to significant
performance improvements for HDSL2. These results can be extended to SDSL as it is defined in
ETSI.
TD-23, Report on HDSL2 Power Back-off from ANSI T1E1.4 (M. Rude, ADC; H. Takatori, LOC),
reports agreements reached and issues raised during the informal power back-off discussion at
ANSI T1E1.4. Power back-off is a mandatory function for the HDSL2 system. It states that
both maximum and minimum allowed power back-off shall be specified. A CO-configurable
“disable” capability shall be also specified.
TD-22, A Guideline for SHDSL Power Cutback (H. Takatori, LOC; M. Rude, ADC; G.
Zimmerman, PairGain), discusses the stable power cutback scheme that was submitted to
T1E1.4. It presents a guideline for power cutback of HDSL2. Power back-off can be used to
improve spectrum management in the local loop. Back-off has been implemented in ADSL
systems and is currently being defined for ANSI HDSL2. T1E1.4/99-045 was provided to inform
ETSI TM6 of the work being done to define a stable power cut-back. The objective of the HDSL2
solution is to guarantee stable operation and still achieve 6 dB of coded margin after power cutback.
M ANAGEMENT
TD-14, Management of SDSL system (M. Meninger, SPT Telecom) specifies basic configuration
management functions and a functional model of SDSL systems. TD-14 will be submitted to the
ANAI working group (Access Network Architecture and Interfaces) for comments and approval.
POWER FEEDING
TD-36, Power feed issues for xDSL (I. Cook, B. Vos, M. Simpkins, Lucent Microelectronics), takes
work from previous contributions and provides further input to allow a better understanding of
the remote powering requirements for xDSL systems requiring “Life Line” support. TD-36 notes
March-April 1999
77
that the power transfer and the Off Hook power consumption are the limiting constraints on
system design. It summarizes the requirements of the POTS interfaces that are required to be
supported under “Life Line” applications, and provides details of CO power requirements based
on current practice gathered from the ISDN arena.
TD-35, Input from ITU-T and IEC concerning Remote Power Feeding (S. Schmoll, Alcatel),
contains draft Recommendation K.sov from ITU-T SG 5 Question 5 and the relevant draft IEC 60
950. These papers have been provided by the Rapporteur of Q5/5 (J. Erreygers) to support
discussion in ETSI TM6. S. Schmoll commented that the feeding voltages allowed (800 VDC) by
this contribution are interestingly high.
N OISE
TD-20 (R. van den Brink, KPN, on behalf of FSAN) is a revised proposal on noise models, for
performance testing on SDSL. The underlying scenarios have been redefined into three versions:
a high penetration, a medium penetration, and a legacy scenario. TD-20 addresses the length
dependency of the FEXT, and is supported by a large number of operators (BT, CSELT, DTAG,
Telia, and France Telecom) that work together in the FSAN (Full Service Access Networks)
xDSL working group.
TD-38, Residual Echo and Transformer Coupling in SDSL simulation models (M Sorbara, R.
Gut, J. Besseyre, Globespan), recommends that the noise model developed for SDSL systems
include the effects of the transformer coupling frequency and the residual echo at the output of the
echo canceler. This noise model will provide a more accurate noise model at low frequencies
where the cross-talk coupling is low. Defining such parameters is essential for performing
computer simulations of SDSL systems that more accurately reflect expected performance. TM6
agreed to create a new study point on the SDSL living list; J. Besseyre is the designated
champion.
TD-39, Proposal to add self-NEXT in SDSL noise masks B and C (M. Kimpe, Adtran; J. Hausner,
Siemens), proposes to amend scenarios B and C such that the total number of interferers
considered remains around 50 and various self-NEXT (Near End Cross Talk) effects are taken
into account. TD-39 will also be considered in the ad hoc group on line coding platform.
WD-11 (W. Henkel, T. Kessler, DTAG) summarizes results of a test campaign for impulse noise in
the German Public operator network. A short demonstration of recorded impulse noise was
given; DTAG likes to show that “Cook” pulses are not appropriate.
LINE CODE
TD-3, Comments on Adtran document: ETSI line code platform (A. Carrick, Ascom AG), presents
Ascom’s 11 comments on the Adtran proposals contained in document LCprop.pdf (dated
01/25/99 and circulated by email on January 28. 1999). The comments were discussed during
the ad hoc meeting and were generally agreed.
TD-30, Spectral Compatibility and Performance of HDSL2 based SDSL System (R. Jonsson,
Conexant Systems Iceland; A. Kantschuk, Orckit Comm.), provides preliminary evaluation of the
performance of a HDSL2-based SDSL line code. The system demonstrates good performance
with reach in excess of 2000 m at 2340 kbit/s under the revised FSAN-B noise model.
Comparison between the HDSL2-based code and HDSL 2B1Q-based line code at SDSL rates
show better performance of the HDSL2-based line code both with respect to reach and spectral
compatibility with ADSL.
TD-31 (J. Benndorf, R. Fischer, J. Huber, Alcatel, Ke, Univ. Erlangen-Nürnberg) assesses and
compares three types of line codes for SDSL systems: PAM, CAP, and discrete multitone (DMT).
In contrast to prior contributions, this comparison is done for a data rate of 2.32 Mbit/s and not
only for one-dimensional trellis-codes. By combining subsequent PAM symbols to hyper-symbols,
78
March-April 1999
a flexible adjustment of the rate is possible. The numerical evaluations show a clear advantage of
PAM. The optimum is found for 8-ary PAM with 2D trellis coding.
TD-32 (J. Benndorf, R. Rischer, J. Huber, Alcatel, Ke, Univ. Erlangen-Nürnberg) assesses and
compares asymmetrical line codes for SDSL systems. The comparison is restricted to M-ary
PAM and the E1 data rate. In addition to one-dimensional (1D) trellis-codes for PAM, two and 4dimensional trellis of 2.32 Mbit/s codes were studied. Numerical evaluations show that a
variation of the cut-off frequency of the transmit filter does not provide any gain.
TD-40, Ideal Margin Calculations for PAM/CAP/DMT (M. Kimpe, Adtran; J. Hausner, Siemens),
is an excellent paper which shows that all three contender codes are extremely close one to
another; a decision will have to be made on other criteria than just performances. The ideal
margins are computed for some representative CAP (Coded 32-CAP, Coded 64-CAP and Coded
128-CAP), DMT (Coded DMT with 2 or 4 kHz carrier spacing), and PAM (Coded 8-PAM and
Coded 16-PAM) line codes.
TD-43 (M. Kimpe, Adtran; J. Hausner, Siemens) proposes 11 points as a basis for a line code
evaluation platform. The points detailed in this paper include loop models, noise model, impulse
noise, SNR calculations, SNR min values, interferer PSD, NEXT and FEXT expressions, mix of
NEXT and FEXT, number of self-NEXT, transformer transfer function, and non linearity below
10 kHz. These points have been released for comments on the TM6 exploder and will be
discussed during the break out session on line codes.
TD-49 (P. Brackett, Adtran; J. Hausner, Siemens) suggests ten criteria under which a line code
proposal could be judged:
1. Spectral Compatibility
2. Reach
3. Impairment Tolerance
4. Bandwidth Efficiency
5. Latency
6. Peak to Average Ratio PAR
7. Power Consumption
8. Impulse Immunity
9. Narrow-band interference immunity
10. Complexity
TD-51, ETSI Line code Bibliography (P. Brackett, Adtran; J. Hausner, Siemens), is contributed
to ETSI TM6 at Villach 1999 “as is.” This bibliography is not intended to be complete. Rather, it
is a short list, related to line code technology; its intention is to direct the reader to original
contributions in each area, as well as to material of a general tutorial nature.
WD-01, Spectral compatibility of SDSL with existing HDSL systems (M. Sorbara, J. Besseyre,
Globespan), suggests a new study point on spectral compatibility of new SDSL systems with
existing deployed HDSL systems. TM6 agreed to assign this item to the existing study point on
PSD mask.
WD-18 gives results of the first ad hoc group meeting on line code evaluation platform; WD-27
gives the results of the second meeting of the ad hoc group. Four general criteria were agreed for
the purpose of line code evaluation: loop and noise model, SNR calculation, and mix of interferers.
WD-28 asks that contributions on the line code indicate the assumptions made in the simulation
on A/D resolution and on echo cancellation residual noise.
REUSE OF HDSL2
TD-08, SDSL power cut-back offers significant performance improvements (J. Stiscia, R. Hipps,
Alcatel; H. Takatori, LOC), demonstrates the merit of requiring HDSL2 power cutback in the
upcoming HDSL2 standard; it provides some guidance in the cutback levels required for best
system performance. Simulations and lab measurements show that the ability to reduce the
March-April 1999
79
HDSL2 output power for each line individually can lead to significant performance improvements
for HDSL2. These results can be extended to SDSL as it is under definition in ETSI.
TD-21, Adopting HDSL2 components in SDSL (R. Jonsson, Conexant), states that rapid
development of the SDSL standard is desirable. At the same time, it is very important to ensure
the quality and performance of the SDSL standard. By adopting the appropriate components
from the HDSL2 work and adapting them to SDSL specific needs, considerable effort can be
saved without sacrifice of quality or performance. This may also facilitate international
standardization and development of new SDSL products.
TD-42, Potential Common Elements Between ANSI HDSL2 and ETSI SDSL (M. Kimpe, Adtran;
J. Hausner, Siemens), reviews the various elements of the ANSI HDSL2 draft standard physical
layer, and discusses ways that those elements could be reused in a device which contains both the
ANSI HDSL2 standard and an ETSI SDSL standard. The conclusion is that most of the
physical layer blocks used for HDSL2 can be reused for SDSL.
WD-02, HDSL2 PMD layer elements applicable for ETSI SDSL (A. Kliger, Metalink), is actually
a delayed TD. This contribution considers PMD layer elements in HDSL2 and their applicability
to ETSI SDSL. It concludes that TC PAM with a variable constellation size should be applied to
ETSI SDSL. The transmitted PSD mask should be flat and similar in the upstream and
downstream transmitters.
A GREEMENTS
TD-50, SDSL - Three Agreements in Principle (P. Brackett Adtran; J. Hausner, Siemens),
proposes that TM6 send an official communication to the ITU Q4/SG15 meeting in March 1999 in
Melbourne; this communication should outline three agreements in principle regarding TM6’s
wishes for the implementation of the proposed ITU SHDSL Recommendation. In summary,
analog splitters for the purpose of supporting narrow band services should not be a requirement.
The line code should make as much use as is reasonably possible of the lower frequency range.
The line code should be based upon trellis coded PAM.
SDSL LIVING LIST
TD-33 is the Living List for DTS/TM-06011 (SDSL).
The following study points existed prior to this TM6 meeting in Villach:
SP 1-1 Functional requirements for SDSL
SP 1-2 Power spectra density
SP 1-3 Rate adaptation
SP 1-4 Asymmetric transmission methods
SP 1-5 European noise model for SDSL
SP 1-6 Multiplexing functions for sub-channels in the NT
SP 1-7 Investigation of a MIB at the operator management interface
SP 1-8 Management of link bit rate failure
SP 1-9 Power budget for remote powering feeding
SP 1-10 Transport of narrow band services
SP 1-11 Impact of wiring in the customer premises
SP 1-12 Reference model
SP 1-13 Frame structure
The following study points were created at this meeting:
SP 1-14 Classes of services
SP 1-15 Bit rate granularity
SP 1-16 Value of residual echo in canceler
Even though there is no formal work item for SDSL part 2 (to be created at the next TM6
meeting), part 2 of SDSL living list first study point was created:
80
March-April 1999
SP 2-1
Investigation of an optimal line code.
VDSL
The VDSL session was chaired by B. Waring (Lucent Technologies); WD-06 is the agenda.
VDSL, PART 1
Two documents address some general issues for VDSL Part 1.
TD-48, VDSL scalability and back compatibility with ADSL/ADSL-lite (seven companies [VDSL
Alliance]), discusses the merits of a new VDSL concept, referred to as Scalable-VDSL. It has the
capability of fall-back modes of operation for interoperability with existing ADSL and ADSL-Lite
ITU-T standards. It introduces a family of VDSL modems spanning the gap between
ADSL/ADSL-Lite and full-rate VDSL. The main attributes of this scalable approach for VDSL
are outlined both from the network operators’ as well as from the end users’ viewpoints. This
contribution led to an animated discussion; some delegates felt that this contribution supported
by the VDSL Alliance is a way to impose DMT as the line code for VDSL; other delegates felt
that this constitutes an extension to the existing functional requirements and needs to be put for
further study.
TD-16, Draft Liaison to ITU-T SG15 re VDSL Open Issues (B. Waring, VDSL Rapporteur),
comments on some open issues for G.vdsl for the SG15 draft recommendation. D. Stuart
(Rapporteur for SG15 Q4) wishes ETSI to use the same format for SDSL and VDSL in its replies
to ITU-T.
Two working documents address the SDH (Synchronous Digital Hierarchy) payload rates (study
point 1-5). WD-07 (V. Oksman, Lucent) is an exchange of e-mail messages on this topic; it recalls
that the payload rates are for evaluation of line codes and for testing, and recommends not
eliminating other payload rates. WD-12 (A. Ehre, TZD) summarizes the agreement (correcting a
small error by changing 450x64kbit/s to 441x64kbit/s) reached on study point 1-5.
WD-14 (V. Oksman, Lucent, for VDSL Coalition) outlines the proposed values for the reflection
coefficient for the VDSL splitter in part 1. The values seem to be agreed although some delegates
stated that the way the values were derived is not the proper way.
TD-17, Generator-based noise models for VDSL (J. Cook, BT, for FSAN), proposes new noise
models which use the generator-based approach, and therefore correctly model the decline in
ADSL downstream FEXT (Far End Cross Talk) with increasing range of the disturbed VDSL
systems. The results, presented here, use a small collection of generator models but cover a wide
range of operators’ expected xDSL deployment situations. TM6 delegates were informed that
FSAN will contribute to the forthcoming Q4/15 meeting in Melbourne.
WD-15 is a report of a break-out session on VDSL on part 1 study points. The meeting reviewed
the PSD masks generated in Sophia Antipolis WD 11 (see CSR Vol 10.2) and made some
revisions to the lower frequency part of the band. In the FTTEx deployment scenario, allowance
has been made for the possible provision of POTS/ISDN on the same pair as VDSL. Other
changes reflect the current thinking on PSD levels needed to provide spectral compatibility with
other DSL systems.
WD-23 is proposed text for the VDSL modem initialization “line is good” test. It also proposes to
use a handshake procedure to identify a VDSL transceiver in the power-on state at the other end
of the line and avoid any high power levels until there is an established handshake between the
VTU-T and the VTU-C.
March-April 1999
81
VDSL, PART 2 LINE CODE/DUPLEXING
TD-10, Proposal for VDSL Duplexing Method (FSAN VDSL Working Group), is provided for
information. The FSAN VDSL Working Group has been analyzing the issue of Duplexing scheme
in the context of their work on xDSL spectral compatibility, and VDSL standardization, and
concludes that there are no clear advantages for either TDD or FDD in scenarios of interest to
FSAN. Synchronization is believed to be very problematic, especially when multiple operators
share the same cables. TD-10 concludes that FDD is the preferred Duplexing scheme for VDSL
from the operator perspective, with no opinion on line code. This document is quite important
since it is the first time that FSAN Telecom operators have indicated a choice for an
implementation solution.
TD-37, Universal Band Allocation for VDSL (V. Oksman, Lucent Technologies for VDSL
Coalition), proposes a universal band allocation for VDSL which includes two possible
transmission bands in both directions. The proposal is both line code independent and TC layer
independent. It easily meets the spectral compatibility requirements for other xDSL services and
provides VDSL mixed services in the same cable binder. This important contribution led to
several questions: Is it not a regulator task to define the allocated bands to different services?
Has RFI been taken into account? Why allocate the low band to either Downstream or Upstream?
This TD was accepted as a study point related to PSD mask; L. Magnone was appointed
“champion.”
TD-24, VDSL Overhead Control Channel (VOC) (V. Oksman, Lucent Technologies for the VDSL
Coalition), is a part of the current working draft specification for VDSL systems. It proposes
VDSL overhead control (VOC) channel specification for a VDSL link using Single Carrier
technology. The document includes VOC message structure, handshaking protocol, and a
detailed list of VOC messages. The proposed text is intended for section 7.5.2 of the VDSL
Transceiver specification DTS/TM-06003-2 (Part 2).
WD-04 (D. Mestdagh, SGS Thomson, et al) is a proposal for changes in the Zipper DMT PMD
section of the VDSL part 2 draft document to handle the new FSAN requirement for no TDD and
to ensure ADSL compatibility. Some delegates felt that this leads to a change of part 1
requirements and that part 1 should not be delayed by introduction of this new item.
TD-19 (K. Jacobsen, TI) summarizes the status of the upstream power back-off study point. It
raises several questions and suggests a plan for resolution via discussion over the TM6 reflector
between now and the next meeting in May.
Due to lack of time, TD-25 and TD-26 (both from VDSL Coalition) were not presented. TD-25,
OAM Primitives and Parameters, proposes a list of definitions for anomalies, defects, and failures
to be monitored in a VDSL link. TD-26, VDSL OAM Reference Model and Communications
Channels, proposed a VDSL OAM reference model based on ITU-T Recommendation X.700.
WD-20 (T. Stefansson, Telia; L. Humphrey, Nortel) lists some new applications for VDSL and
provides text for an Annex to VDSL part 1 on these applications.
VDSL LIVING LIST PART 1
SP 1-1, SP 1-2, and SP 1-3 (respectively: Low frequency cut off, VDSL PSD boost at low
frequency, and use of rates S3 and S4 with mask M1) have been merged into one study point
which is summarized in WD-15. The effect of unbundling in Europe may lead to revision of any
conclusion that ETSI TM6 may reach on power spectral density by the regulators.
SP 1-4
SP 1-5
SP 1-6
SP 1-7
82
Latency vs. impulse noise is deleted
SDH payload rates (the proposal of WD-07 modified by WD-12 is provisionally agreed to
replace the existing text)
Definition of impulse noise margin is deleted
Cross-talk transfer functions deleted
March-April 1999
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
1-8
1-9
1-10
1-11
1-12
1-13
1-14
1-15
1-16
1-17
1-18
1-19
1-20
1-21
1-22
NEXT noise model (provisionally agreed)
Test sets U2, U3, U7 and U8 deleted
test sets D2, D3, D7 and D8 deleted
Duration of micro interruptions
Installation procedure
Splitter filter requirements
Implementation of EOC channel
Test loops
White noise generator (noise model)
Statistics of noise test signal
Power back-off
Clarification of activation states
Study of other applications
Return loss values
Non-stationary cross-talk
VDSL LIVING LIST PART 2
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
SP
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
Line coding/Duplexing method
Pilot tone modulation
G.803 functional modeling
Service payload requirements
Advanced splitter requirements
ATM TPS TC
Dynamic power saving
Reference model
Spectral compatibility impact on PSD masks
Deployment scenarios and allowable impairment
Noise model for mixed services
Implementation of EOC channel
Non-stationary cross-talk
Band allocation
OAM
ADSL REVISION OF TS 101 388 V1.1.1
A brain-storming session was opened by the Rapporteur L. Magnone (Telecom Italia) to discuss
the work that could be done within ETSI TM6; the following items are applicable within the
ADSL project:
•
•
•
•
•
•
•
•
•
Alignment of the test procedure with those derived by VDSL and SDSL
Addressing non-stationary noise and dynamic power saving
Study of improved framing methods (better efficiency)
Noise model for broadcast RFI ingress
In-band transmission of POTS, ISDN and sub-rate ISDN PRA
Relationship with G.lite
Transmission of symmetrical services (overlap with SDSL?)
Use of ADSL without POTS splitter and no POTS transmission
Use of ISDN band (without ISDN)
TD-12, Unification of ADSL over ISDN Power Spectral Density Spectral Masks for 2B1Q and
4B3T ISDN (E. Balocating, TI; J. Waldinger, Siemens), recommends that the ADSL over ISDN
PSD high pass frequency response be combined for 2B1Q and 4B3T. Specifically, the 2B1Q
power spectral density mask for ISDN upstream (downstream) meets the 4B3T PSD mask for
ISDN upstream (downstream). TD-12 proposes one PSD mask for the upstream and one PSD
mask for the downstream. It was placed for further study to give a chance to other chip
manufacturers to study the consequences of such a change on their own ISDN basic rates access
chips.
March-April 1999
83
TD-13, Splitter for ADSL over ISDN or POTS (R. Wu, YCL Electronics, not an ETSI member but
an invited guest), describes an outlined design for POTS Splitter which separate high frequency
ADSL signal and ISDN or POTS signal at network end and premises end. Experimental
performance is shown for a manually selectable POTS/ISDN filter using a 9th order elliptic filter
with smaller than 0.05 dB passband ripple and 70 dB minimum attenuation in stopband with
fadsl being set to 138 kHz and fisdn being suited to 90 kHz. With a POTS splitter, ADSL delivers
high speed performance over existing copper telephone line while allowing traditional voice
service to coexist without interruption. It was considered a very useful contribution.
TD-07, Adjustment of the Downstream Power Cutback (P. Reusens, Alcatel), proposes a small
adjustment in the set of sub-carriers used for measuring the Downstream Power Cut-back. The
proposal is backwards compatible with the existing text, as proposed by TM6 for Annex B, and is
already part of the Oct. 1998 version of ITU-T G.dmt (G.992.1).
TD-06, Quiescent Mode, a tutorial on dynamic power saving methods (P. Reusens, Alcatel), notes
that a “quiescent mode” (Qmode) for ADSL is needed. The methods seem to converge, but it
seems unavoidable to adapt the existing ADSL standard slightly to support Qmode. TD-06
requests that TM6 state a clear opinion on the guidelines for Qmode.
TD-29, ADSL over POTS/ISDN: support for revision of TS 101 388 v1.1.1 and ETR 328 ed.1 and
proposal for performance and objectives criteria (L. Magnone, Telecom Italia), proposes a set of
performance objectives for ADSL over POTS/ISDN, in conjunction with revision of two ETSI
documents.
WD-24 (L. Humphrey, Nortel) presents proposed values for ingress noise test source as a basis
for further study.
BROADBAND-ISDN ACCESS
The Broadband-ISDN Access rapporteur group met under the leadership of A. Profumo (Telecom
Italia). The following contributions were introduced at the ANAI (Access Network Architecture
and Interfaces) sub group meeting; WD-16 is the plenary report.
TD-11 contains the Revised Table of contents for RTS/TM-06012 (TS101 012 v1.2.1),
“Broadband Access Digital Section and NT Functional Requirements.”
TD-46, Proposed modifications to ADSL management functions (A. Profumo, Italtel), proposes
some modifications to the functional modeling of ADSL atomic transfer and layer management
functions, as given in TD-05 from last WP ANA meeting in Bonn. These modifications fully meet
the functional modeling requirements. Figure 1 compares the previously proposed functional
modeling with the present one. Figure 2 briefly describes the functions of each included functional
block.
TD-47, Consideration of ETSI ISDN reference configuration (B. Orth, DTAG), proposes the usage
of the ISDN reference configuration as a basis for the modeling of xDSL-based access types in
addition to the User Network Interfaces (UNI) and the so called access digital section. Interfaces
for further studies are proposed.
Jacques Besseyre, Telecomsult
84
March-April 1999
TM6 MEETING ROSTER, FEBRUARY 22 - 26, 1999, VILLACH, AUSTRIA
Hans-Jörg Frizlen, ETSI
TM6 Chair
Host: Siemens Semiconductor Electronics
Austria
Belgium
Czech Republic
Finland
France
Germany
Greece
Israel
Italy
March-April 1999
FEEI-Fachverband ... Technik
Telekom Austria AG
Alcatel
Alcatel
SPT Telecom a.s
Nokia Telecommunication
Nokia Telecommunication
Tellabs Oy
3Com
Conexant Systems SAS
Conexant Systems SAS
ETSI
France Telecom
France Telecom
Level One Com Europe
Level One Com. Europe
Level One Com. Europe
ST Microelectronics
ST Microelectronics
ST Microelectronics
Texas Instruments SA
Alcatel
Globespan Semiconductor
KE Kommunikations Elektronik GmbH
Bosch Robert GmbH
Deutsche TelekomAG
Deutsche Telekom AG
Deutsche Telekom AG
Lucent Technologies
Lucent Technologies
Philips GmbH
Quante AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Siemens AG
Intracom SA
IAEI
IAEI
ITALTEL S.p.A.
Marconi Communications
Marconi Communications
Telecom Italia SPA
Telecom Italia SPA
Telecom Italia SPA
Franz Haberl
Manfred Gindel
Thierry Pollet
Peter Reusens
Milan Meninger
Paulus Carpelan
Jari Lindholm
Janne Väänänen
Richard Stuart
George Eisler
Ragnar Jonsson
Hans-Jörg Frizlen
Pascal le Guern
Marc Vautier
Jim Girardeau
Jim Quilici
Hiroshi Takatori
Denis Lacloche
Simone Mazzoni
Denis Mestdagh
Jacky Chow
Krista Jacobsen
Neil Quarmby
Siegfried Schmoll
Jacques Besseyre
Jens Benndorf
Werner Stenzel
Andreas Ehre
Werner Henkel
Günter Zedler
Chris Jolly
Mark Simkins
Ralf Boden
Manfred Folger
Peter Brackett
Dick Daecke
Josef Hausner
Hagen Henniger
Christian Hinterberger
Marc Kimpe
Stefan Lüthi
Shimon Peleg
Klaus Starnberger
Armin Tannhäuser
Dimitris Giannakopoulos
Avi Kliger
Eli Shusterman
Lucio D’Ascoli
Sabrina Lettere
Davide Pagnotta
Lorenzo Magnone
Carla Montanari
Letizia Tempestilli
85
Norway
Slovenia
Spain
Sweden
Switzerland
The Netherlands
UK
USA
Unknown
Norwegian Post&Telecomms Authority
Standards & Metrology Institute of Slovenia
Telefonica de Espa-a
Ericsson Telecom AB
Telia AB
Telia AB
Ascom AG
BAKOM / OFCOM
Pro Telecom
KPN Research
Lucent Technologies EMEA B.V.
Lucent Technologies EMEA B.V.
BT plc
BT plc
Consultronics Europe
Fujitsu Europe
Fujitsu Europe
Marconi Communications Ltd.
Motorola Ltd.
NEC Technologies (UK) Ltd.
NORTEL NETWORKS
Westell Europe
Broadcom Corporation
Rasmus Trevland
Janez Smid
Angel Guerrero
Jan Boström
Per Ödling
Tomas Stefansson
Angus Carrick
Kurt Bartschi
Christof Heidelberger
Rob van den Brink
Vladimir Oksman
Brian Waring
Don Clarke
Rob Kirkby
Steve Mlikan
Graham Arnold
Martin Pollakowski
Peter Dixon
Bernard Dugerdil
Carmelo Bonaccorso
Les Humphrey
Mike Bryant
Gottfried Ungerboeck
Eric Berthaud
Paul Doyle
Heikki Suonsiuu
Roger Wu
ACRONYM DEFINITIONS
AAL
ACELP
ANSI
APEC
ARQ
ASN
ATA
ATF
ATIS
ATM
ATMF
B-ISDN
BFT
BNWG
BRI
CAP
CCSRL
CD
CDMA
CO
CTP
DAVIC
DC
DCE
DCME
DCT
DCT
86
ATM Adaptive Layer
Algebraic Code Excited Linear Predictor
American National Standards Institute
Asia Pacific Economic Coop. Forum
Automatic Repeat Request
Abstract Symbol Notation
Analog Terminal and Access Project
Administrative Task Force
Alliance for Telecom. Industry Solutions
Asynchronous Transfer Mode
ATM Forum
Broadband ISDN
Binary File Transfer
Bi-National Working Group
Basic Rate Interface
Carrier-less Amplitude Modulation Phase Modulation
Control Channel Segmentation and Research Layer
Committee Draft
Code Division Multiple Access
Central Office
Common Transport Protocol
Digital Audio-Visual Council
Directionality Classification
Data Circuit Terminating Equipment
Digital Circuit Multiplication Equipment
Data Calling Tone
Discrete Cosine Transform
March-April 1999
DECT
DIS
DMT
DS1
DSL
DTE
DTR
EC
ECMA
EDH
EMA
EMC
ERM
ETSI
EU
FCC
FCD
FDM
FEXT
FSAN
FTTEx
FX
GCC
GII
GIT
GK
GOB
GSM
GSTN
HAC
HDSL
IAC
IDLC
IEC
IECEE
IETF
IMC
IMT
IMTC
IP
IPR
IPTEL
IRR
ISO
ISPBX
ISUP
IT
JBIG
JPEG
KTS
LAN
LCD
LRQ
MB
MC
MCS
MCU
MDCP
Digital Enhanced Cordless Telecom. (ETSI standard ETS 300 175)
Digital Identification Signal
Discrete Multi-tone Carrier
1.544 Mbit/s T1 Interface
Digital Subscriber Line
Data Terminal Equipment
Draft Technical Report
European Commission
European Comm. Mfrs Association
Electronic Document Handling
Electronic Messaging Association
ElectroMagnetic Compatibility
ETSI committee on EMC and Radio spectrum Matters
European Telecom. Standards Institute
European Union
Federal Comm. Commission (U.S.)
Fast Track Committee Draft (ISO)
Frequency Division Multiplexing
Far End Cross Talk
Full Service Access Networks
VDSL to the exchange
Foreign Exchange
Generic Conference Control
Global Information Infrastructure
Generic Identifier Transport
GateKeeper
Group of Blocks (H.261, H.263)
Global System for Mobile Comm. (formerly Groupe Speciale Mobile)
General Switched Telephone Network (e.g., PSTN)
Hearing Aid Compatible
High-rate Digital Subscriber Loop
Industry Advisory Committee
Integrated Digital Loop Carrier
International Electrotechnical Committee
Compliance with IEC for Electrical Eqpt
Internet Engineering Task Force
Internet Mail Consortium
International Mobile Telecommunications (IMT-2000, see FPLMTS)
International Multimedia Teleconferencing Consortium
Internet Protocol
Intellectual Property Rights
Internet Protocol Telephony (IETF WG)
Information Request Response
Int’l Organization for Standardization
Integrated Services Private Branch Exchange
ISDN User Part
Information Technology
Joint Binary Image Group
Joint Photographics Expert Group
Key Telephone System
Local Area Network
Liquid Crystal Display
Location Request
Macro Block
Message Center
Multi-point Control Services (T.122)
Multi-point Control Unit
Media Device Control Protocol
March-April 1999
87
MEGACO
MGCP
MIB
MIME
MLTS
MOU
MPEG
MRA
MRC
MRM
MTIE
NAT
NEC
NEXT
NI
NT
OA&M
OAM
OAS
OID
OPS
PACS
PAM
PBX
PCI
PCM
PCS
PDAM
PDU
PHS
PICS
PISN
PMD
POTS
PRA
PRI
PSD
PWT
PWT-E
QAM
QoS
QSIG
RAS
RBOC
RF
RFC
RFC
RFI
RFI
RLR
RS
RSVP
RTCP
RTP
RTTE
SC
SC
88
MEdia GAteway COntrol
Media Gateway Control Protocol
Management Information Base
Multipurpose Internet Mail Extension
Multi-Line Telecommunications Systems
Memorandum of Understanding
Motion Picture Experts Group
Mutual Recognition Agreements
Mixed Raster Content
Meeting Room Management
Maximum Time Interval Error
Network Address Translation
National Electric Code (U.S.)
Near End Cross Talk
Network Interface
Network Termination
Operations, Admin., & Maintenance
Operations, Admin., & Maintenance
Organization of American States
Object Identifier
Off Premise Station
Pers. Access Comm. Sys, Licensed Band
Pulse Amplitude Modulation
Private Branch Exchange
Peripheral Component Interface
Pulse Code Modulation
Personal Communication Services
Proposed Draft Amendment
Protocol Data Unit
Personal Handyphone System
Profile Implementation Conformance Statement
Private Integrated Services Network
Physical Media Dependent Layer
Plain Old Telephone Service
Primary Rate Access
Primary Rate Interface (ISDN)
Power Spectral Density
Personal Wireless Telecommunications
Personal Wireless Telecommunications - Enhanced Interoperability Standard
Quadrature Amplitude Modulation
Quality of Service
The signaling protocol used at the Q-interface between two switches in a
private network. ECMA/ISO have defined a set of QSIG standards.
Registration, Admission, and Status
Regional Bell Operating Company
Radio Frequency
Remote Feature Control
Request for Comments (Designation for an Internet Standard)
Radio Frequency Interference
Request for Information
Receive Loudness Rating
Reed-Solomon (code)
Resource Reservation Setup Protocol
Real-time Transport Control Protocol
Real Time Transport Protocol
Radio and Telecommunication Terminal Equipment
Subscriber Confidentiality
Type of commercial fiber optic connector (Push-Pull)
March-April 1999
SCN
SDOC
SDP
SDSL
SHDSL
SLR
SNMP
SNR
SOHO
SONET
SS7
STQ
SUD
TAG
TAPAC
TBD
TC
TC
TCB
TCP
TCP/IP
TDD
TDM
TDMA
TIA
TIFF
TIPHON
TMN
TS
TSB
TSB
TTE
TTF
UDP
UL
URL
UTP
VDSL
VPN
VTU
WCDMA
WG
WUPE
Switched Circuit Network
Suppliers Declaration of Conformity
Session Description Protocol
Symmetrical high bit rate Digital Subscriber Line
Single-line High Speed DSL
Send Loudness Rating
Simple Network Management Protocol
Signal to Noise Ratio
Small Office Home Office
Synchronous Optical Network
Signaling System 7
Speech Transmission Quality
Single Use Device
Technical Advisory Group
Terminal Attach.Prog. Advisory Comm.
To be Determined
Technical Committee
Trellis Coded
Technology Certification Bodies
Terminal Connection Point
Trans. Control Protocol/Internet Protocol
Time Division Duplexing
Time Division Multiplexer
Time Division Multiple Access
Telecom. Industry Association
Tagged Image File Format
Telecom. and Internet Protocol Harmonization Over Networks
Telecom. Management Network
Technical Specification
Telecom. Standardization Board (ITU)
Telecom. Systems Bulletin (TIA)
Telecom. Terminal Equipment
Technical Task Force
User Datagram Protocol
Underwriters Laboratories
Uniform Resource Locator
Unshielded Twisted Pair
Very high speed ADSL
Virtual Private Network
VDSL Transceiver Unit
Wideband Code Division Multiple Access
Working Group
Wireless User Premises Eqpt (TR-41.6)
The next issue of Communications Standards Review - Telecommunications (Vol. 10 #4) is
scheduled for May 1999.
March-April 1999
89
1999 STANDARDS COMMITTEE MEETING SCHEDULES AS OF MARCH 8, 1999
Subject to Change without Notice
Committee
ETSI DTA
T1E1
ITU-T SG8
Q4/15 Rapp.
TR-30
T1E1.4
ETSI TIPHON
ETSI TM6
TR-29
Q4/15 Rapp.
T1E1.4 Interim
TR-41 and TR-42
ITU-T SG 16
T1E1
TR-30
ITU-T SG15
ETSI ATAc WG
ETSI TIPHON
Q11-15/16 Rapp.
TR-29 (Proposed)
TR-30
TR-41 and TR-42
T1E1
ETSI TM6
ETSI TIPHON
TR-30
ETSI ATA
Q11/16 Rapp.
Q15/16 Rapp.
TR-41 and TR-42
TR-30
ETSI TM6
T1E1
Date(s)
Mar 8 - 12
Mar 8 - 12
Mar24-Apr 1
Mar29-Apr 2
Apr 12 - 15
Apr 19 - 23
May 3 - 7
May 3 - 7
May 10 -12
May 10 - 14
May 17 - 18
May 17 - 21
May 18 - 28
Jun 7 - 11
Jun 14 - 17
Jun 21-Jul 2
Jun 29 - 30
July 19 -23
Aug 2 - 6
Aug 9 - 11
Aug 9 - 11
Aug 16 - 20
Aug 23 - 27
Sep 20 - 24
October 4 - 8
Oct 11 - 14
Oct 11 - 15
November
Nov - Dec
Nov 8 - 12
Nov29-Dec 2
Nov29-Dec 3
Dec 6 - 10
Visit the CSR Web Pages:
Location
Sophia Antip, FR
Costa Mesa, CA
Geneva
Melbourne, AU
San Jose, CA
Washington, DC
--Grenoble, France
East Coast US
Boston, MA
Boston, MA
Portland, OR
Santiago, Chile
Ottawa, Ont.
Lake Tahoe, NV
Geneva
Sophia Antip, FR
Amsterdam
Berlin, Germany
West Coast
Quebec City, PQ
Ottawa, Ont
Portland, OR
Edinburgh, Scot.
--Baltimore, MD
----Reno, NV
Clearwater, FL
Amsterdam,
---
http://www.csrstds.com
The Web Pages include an updated Telecom Acronym Definitions list, updated meeting schedules,
a list of web sites and ftp sites as listed in all issues of CSR journals, background material on
telecom standards and CSR (the company), data sheets on both CSR technical journals, and
more.
Communications Standards Review -Telecommunications (ISSN 1081-4655) is published
8 - 9 times per year, within days after the latest, related standards meetings. Editor: Elaine J.
Baskin, Ph.D. Technical Editor: Ken Krechmer. Copyright © 1999, Communications Standards
Review. All rights reserved. Copying of individual articles for distribution within a subscriber
organization is permitted. Subscriptions: $695.00 per 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 10903.
90
March-April 1999
FAX BOUNCE-BACK
The fastest and easiest way to get the standards information you need!
FAX this form to Communications Standards Review (or mail or phone) and
the standards contributions ordered will be shipped the next business day.
FAX: +1-650-856-6591
757 Greer Road
Palo Alto, CA 94303-3024 USA
Tel: +1-650-856-9018
e-mail: [email protected]
WWW: http://www.csrstds.com
BILL TO:
_________________________
_________________________
_________________________
_________________________
SHIP TO: (Include Telephone)
____________________________
____________________________
____________________________
____________________________
CSR provides to CSR subscribers copies of communications standards
work in process. Once standards are completed and available,
they should be acquired from the appropriate, authorized source.
Documents Ordered:
______________
______________
______________
______________
______________
_________________
_________________
_________________
_________________
_________________
_________________
_________________
_________________
_________________
_________________
Documents in addition to those listed in boldface in this issue of CSR may
also be ordered. Please ask if we have what you are looking for.
Subscribers, Per Order
1st Document
2nd Document
3rd + Documents
Shipping
North America
$50.00
$40.00
$25.00
2nd day air included
Outside North America
$50.00
$40.00
$25.00
Invoiced at cost
Shipping Instructions: _________________________________________
Invoices for documents and any applicable shipping charges or sales tax are
included with the order.
Payment may be made through MasterCard or Visa.
_________________________
Authorizing Signature
CSR Vol. 10 #3
_____________
Date
PO (if Appl.)
Documents Cited in Communications Standards Review
Vol 10 #3, March – April, 1999
All documents listed in boldface in the text are for sale
to CSR subscribers. They are copies of work in progress.
These documents are not approved or published standards.
Documents listed with © are controlled documents.
These documents are not for sale, but we can provide you with
the author’s contact information.
Documents in addition to those mentioned in this issue of CSR-T
may also be ordered. Please ask if we have what you are looking for.
TIA Standards,
SP- documents,
and ITU Recommendations
may be ordered from
Global Engineering Documents
Tel: 800 854-7179, +1 303 792-2181
Fax : +1 303 397-7935.
http://global.ihs.com

Mar/Apr 1999 - Linda Hall Library

Transcrição

Documentos relacionados

Baixar este arquivo PDF

INFORMAÇÕES ÚTEIS

integrating csr in the smes strategies responsabilidade

Janeiro/Fevereiro 2015 Caros amigos, este é nosso segundo

Exploring the relationship between environmental regulation and