DSL Forum Liaison to:

TR41.9-01-08-052

Anh Wride, Chair TIA TR41.9 [email protected]

From: Gavin Young, DSL Forum Technical Committee Chair [email protected] Date: June 22, 2001 Subject: DSL Forum Liaison regarding xDSL test plans and xDSL equipment qualification, invitation to next meeting Dear

Anh,

The DSL Forum would like to thank you for establishing a liaison with our organization. We would welcome a further discussion of how our organizations can work together on xDSL test plans and xDSL equipment qualification. To this end, we wish to encourage a representative of your group and members of TR41.9 who are members of the DSL Forum to attend the DSL Forum meeting that will be held in New Orleans, Louisiana from August 27th to 31th, 2001 or the following meeting to be held in Munich, Germany from December 3rd to 7th, 2001. Please find the minutes of our most recent meeting you requested attached to this liaison. We would be interested in any additional information you can provide regarding your work on Part 68, such as description or mailing list. We would be pleased if you could provide a confirmation of your planned representation at the abovementioned meetings.

Best regards,

Gavin Young DSL Forum Technical Chair CC: Ed Eckert, Technical Subcommittee T1E1 Chairman [email protected] attachment: Approved meeting minutes from the March 14th – 16th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum

dslforum2001.143.1

Project:

Testing & Interoperability Working Group

Title:

Approved meeting minutes from the March 14th – 16th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum

Source:

Fred Kaudel Fluke Networks, Inc. 6920 Seaway Blvd., #279F Everett, WA, 98203-5829 U.S.A. +1 425 446 6101 (v), +1 425 446 5043 (f) [email protected]

Date:

June 20 – 22, 2001

Distribution:

Testing & Interoperability Working Group

Abstract: This contribution contains the approved T&IWG minutes from the March 14th - 16th, 2001 meeting in Vancouver, British Columbia. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on the minutes of our previous meetings, dslforum2001.033.0 – 033, 117.1, and 126). See 107 for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on March 16th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included. See 113 for the draft minutes of the joint session with the A&T WG. See 122 for the draft minutes of the joint session with the EDSL WG. See 109 for the draft minutes of the joint session with the VODSL WG.

Notice: This contribution has been prepared to assist the DSL forum. It is offered to the Forum as a basis for discussion and is not a binding proposal on the author(s), parent companies or any other company. The requirements are subject to change after further study. The author reserves the right to add, amend or withdraw any and all statements made herein.

repTIWG010314-16-010626a.doc

Page 1 of 28

dslforum2001.143.1 Approved Meeting Minutes (April 23, 2001 version) Kind of meeting: Testing & Interoperability Working Group (T&IWG) Name of organization: DSL Forum Place of meeting: Vancouver, British Columbia Date of meeting: April 14th – 16th, 2001 Time of meeting: see agenda in Attachment 1 Approval of minutes of previous meeting(s): 033†, 027, 002 Next meetings (until June 22, 2001) teleconference #1 (T&IWG and ISWG): April 5th, 11am – 12:30pm EDT; access details: 877.520.6874 (US), +1.303.563.6312 (International)1 teleconference #2 (T&IWG and ISWG): April 20th, 11am – 1pm EDT; access details: 877.520.6874 (US), +1.303.563.6312 (International) teleconference #3 (T&IWG and ISWG): May 15th, 11am – 1pm EDT; access details: 877.520.6874 (US), +1.303.563.6312 (International) face-to-face (T&IWG and ISWG): June 20th – 22nd, Oslo, Norway, (access information at: http://www.dslforum.org/oslo_mtg.html) Contribution deadlines for next face-to-face meeting: upload: 5pm PDT, Tuesday, June 12 th, 2001 [http://www.dslforum.org/private/index.html#contrib] Presiding officer: Fred Kaudel (contact: +1.425.446.6101, [email protected]) Substitutes for secretary: Fred Kaudel, Scott Harris (for G8 portion of Section 1) Presence of a quorum: see attendance lists in Attachment 3 Scope of meeting: proposed agenda (March 12th draft of Attachment 1) accepted and modified during meeting, as shown with changemarkings in Attachment 2 Table of contents: 1. 1.1. 1.2. 1.3. 1.4. 2. 3. 4. 5. 6. 7. 8. 9. 10.

1.

All Sessions (T&IWG) ....................................................................................................................... 2 Housekeeping/attendance............................................................................................................ 2 Joint session with G8 .................................................................................................................. 3 Higher/regular-priority action items/living list items ................................................................... 4 Other topics: contributions (TR30.3 liaison), future teleconferences, new action items, plugfests. 4 Meeting outputs.................................................................................................................................. 4 Summary/plan for next meetings (changes of 033 accepted, updates from 033 marked) ....................... 4 Relationship of T&IWG documents (updates of 033 accepted, updates to 033 marked) ....................... 6 Summary of changes to and status of T&IWG documents (updates of 033 accepted, updates to 033 marked).............................................................................................................................................. 7 Action items (changes of 033 accepted, updates from 033 marked) ..................................................... 8 Living list (changes of 033 accepted, updates from 033 marked) ........................................................11 Request For Information (RFI) respondents contact information .........................................................13 Revision history.................................................................................................................................13 Table of Attachments.........................................................................................................................13

All Sessions (T&IWG)2 1.1. Housekeeping/attendance

Attendees introduced themselves during the first T&IWG/ISWG session (see the attendance lists in Attachment 3). The preliminary agenda of March 12th was approved (Attachment 1), and annotated heavily during the meeting (with changemarkings) to show our progress and decisions. The most recent draft minutes were reviewed and agreed, per the annotated agenda of Attachment 2. For all sessions but the joint session with the G8 on Thursday afternoon, see Attachment 2 for the draft minutes (as distributed during the Vancouver meeting). † Contribution dslforum2001.abc is herein denoted as abc, and dslforum2000.abc is denoted as 00.abc. For authors, titles, abstracts and soft-copies of any DSL Forum contribution, please browse URL: http://www.dslforum.org/contrib/assocs/dslforum/members/documents.cgi.

1 2

The minutes for this are in 117.1. All T&IWG sessions were jointly held with the ISWG. ISWG is not separately listed.

repTIWG010314-16-010626a.doc

Page 2 of 28

dslforum2001.143.1 See 107 for the updated work plan, with partial targets for straw and letter ballots. These documents are available on the DSL Forum web-site (www.dslforum.org). 1.2. Joint session with G8 • • • • • • • • • • • • • • • • •

• • • • • • • • •

• • •

Scott Harris presented the ITL Process (066) Will the test lab have to do all annexes to be “recognized”? No, they need to do the minimum piece, and the annexes are optional. June to kick off the process, but what? Annexes be ready by then? Annex A will be ready by then. DSL Forum recognition could be revoked by some process if there are deficiencies in the ITL. As new Annexes are created, they will be folded into the test plan. Service provider is not the sole driver, Vendors could decide for testing themselves. Contribution 103 is ready to use for ITL 2001.012 is also good to fold into the ITL test plan. TIA/EIA-876. RSL had a “gold standard” set of equipment. How will ITL stock the same set of equipment? The market and ITLs will decide which equipment is used. Is RSL being dissolved then? No, RSL will continue in the interim while the ITL is being set up. RSL has scalability problems that preclude its work as the DSL testing goes worldwide. Test labs will have it in their best interest to work with many equipment and service providers so that the ITL can make business and this will drive us towards global P-n-P. ITL addresses all people in the food chain: chipset, equipment vendor, test lab, and service provider. Does this get us to mass market right away? No, this is not a panacea, but it’s an important first step in the process. Network models are dictated by the test plans which are developed by the DSL Forum body in the TIWG. What would the sticker indicate? It would indicate that the testing passed between a pair of vendors? We’re still iffy on the whole sticker issue. Conformance and compliance are tough issues for the group. Service providers today have not yet embraced any-to-any interoperability. They are still working with specific sets of DSLAMs and CPEs. Retailers can decide which service providers they care about, and they can buy equipment and even test through the ITL themselves, so they know which DSL equipment to stock. Since it is a “closed process” between the vendor and the ITL, how does the information trickle out to the public to show universal interoperability? Break Comments on contribution 073 followed the break. It was reviewed without comments. No comments were mentioned on 011 either, as it was a previous version to 073. Back to 066: All contributions to the test plan will drive its content, including the TIA document, if it is folded in. Performance and interoperability are well addressed, and conformance needs to be folded into the process test plan. Done with Q/A. On 2001.002: Minutes from last time. Should PD-7 continue, and how? Does 425 and 011/073 address these issues enough? Right now, we have a somewhat messy trail on the changes to 425 which are captured in the minutes, but never made it into PD-7. That is okay, and we’ll record that here. On 2001.043: General comments and questions cleared up. Next steps: getting ready for Oslo, replacing the seat that Greg vacated on the G8, call for other issues that we may need to be aware of? Plugfest activity on G.SHDSL has been outside of the forum and not well advertised. We wish to bring that more to the forefront.

repTIWG010314-16-010626a.doc

Page 3 of 28

dslforum2001.143.1 •

•

•

Oslo will launch the ITL process! Lots of work, but we can get there. We wish for the ITLs to be ready to go in June! No need to wait for June to begin acquiring equipment and developing test plans. Could the ITLs have the information from the RSL on code versions. The right way to get this is for the equipment vendors to provide the ITLs the latest code. The RSL cannot divulge the versions because of the NDAs for RSL. done early! 1.3. Higher/regular-priority action items/living list items

It was agreed to not discuss each action/living list item in detail. See Section 6 for the updated action items (change-markings from higher-priority items discussed above). See Section 7 for the updated living list items. 1.4. Other topics: contributions (TR30.3 liaison), future teleconferences, new action items, plugfests Arrangements for future teleconferences were discussed, including continuing to list the higherpriority items (action and living list) to be addressed. New action items are listed (in Section 5): See Section 5 for an updated summary of changes to and status of T&IWG documents. See Section 4 for an updated relationship of T&IWG documents. The times for the next meetings were reviewed (see page 2). 2. Meeting outputs 107: Testing & Interoperability Working Group Presentation to Mar. 16, 2001 DSL Forum (i) Closing Plenary on Status after Meeting in Vancouver 108: Liaison to ITU-T Q4/15 Chair: Regarding DSL Forum Testing & Interoperability (ii) Activities (Completed DSL Forum Output Liaison to ITU-T Q4/15 from March14 -- 16, 2001 Testing & Interoperability Working Gr… 112: Liaison from TIA TR30.3 Chairman: Regarding the Updated TR30.3 Inputs to the DSL (iii) Forum’s Testing & Interoperability Working Group’s Meeting of March 14-16, 2001 … 118: Memorandum of Understanding Letter to ETSI TM6 Chairman: Regarding DSL Forum (iv) Request for DSL Testing and Interoperability Documents (Completed DSL Forum Output Memorandum of Understanding Letter to ETS… 119: Liaison to OpenVoB Chair: Regarding DSL Testing and Interoperability (Completed (v) DSL Forum Output Liaison to OpenVoB from March14 -- 16, 2001 Testing & Interoperability Working Group and VoDSL Working G… 120: Liaison to TIA TR30.3 Chair: Regarding DSL Testing and Interoperability (Completed (vi) DSL Forum Output Liaison to TIA TR30.3 from March 14 -- 16, 2001 Testing & Interoperability Working Group Meeting in V… WT-051v4: ADSL dynamic interoperability testing (vii) WT-052v5: PPP static interoperability testing (viii) WT-062v1: ADSL Interoperability Test Plan (ix) PD-002v2/v3: G.992.1 (G.dmt) testplan (x) PD-003v2/v3: G.992.2 (G.lite) testplan (xi) PD-004v2: HDSL2 testplan (xii) PD-005v2: G.991.2 (G.shdsl) testplan (xiii) PD-006v2: PPP-based solutions interop testplan (xiv) 3. Summary/plan for next meetings (changes of 033 accepted, updates from 033 marked) This is an overall summary of the status of the T&IWG and the ISWG after this meeting. See 001.107450 for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Technical/Marketing Plenary on MarchDecember 168, 20010, including key results, information on outgoing liaisons (to ETSI TM6, TIA TR30.3 and TIA TR41.9), T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. Contributions are requested to our April 5th, April 20th,January 23rd, and repTIWG010314-16-010626a.doc

Page 4 of 28

dslforum2001.143.1 MayFebruary 152th teleconferences, and JuneMarch 2014th — 2216tndh face-to-face meeting in the areas listed under next steps below. An updated summary based on 00.3381 and 00.351 follows (changemarkings appear). Overview: The Testing & Interoperability Working Group (T&IWG) is concerned with cross-vendor interoperability, DSL Implementation Conformance Statements (ICS), test procedures and configurations. It examines test parameters and test conditions both at the electrical/physical layer and higher protocol layers. It examines the types and levels of interoperability testing, produces test suites, test configurations and captures experience from test cases. The T&IWG will expands and developes testability requirements, hooks for testing and testability, and Design For Test recommendations. The T&IWG liaises with the ITU-T, T1E1, TIA TR30, TIA TR41 and ETSI TM6 to help expedite the arrival of interoperability within the DSL industry. The Interoperability Sub-Working Group (ISWG) of the T&IWG addresses interoperability testplans and testing events. The ISWG includes vendors planning to participate in interoperability testing events and demonstrations. The ISWG agrees on and refines the testplans and technical focus of subsequent interoperability plugfest/staging events. Completed Work: The T&IWG has completed the following work items: • Issued an RFI to key industry test laboratories to assist in this work. • Issued a technical report overviewing ADSL testing (TR-023: a framework for interoperability testing enabling vendors and service providers to understand the logical steps and techniques required to investigate static and dynamic interoperability between different vendors' DSL equipment), • Issued a technical report on T1.413-1998 ATM-based ADSL ICS (TR-026), • Assisted in producing an RFI to select a test house for the DSL Forum (ISWG, fall ’99, with G8), • Issued a technical report on ADSL dynamic interoperability testing (TR-029: under revision), • Issued a technical report on ADSL T1.413-1998 conformance testing (TR-031), • Issued a technical report on ITU-T G.992.2 (G.lite) ICS (TR-033), and • Developed, with the G8, a test matrix for reference system testing, with an open process for updates to the criteria. Priorities and Target Plan: The immediate priorities for the T&IWG follow: • WT-030 (ed. B. Wiseman): ADSL T1.413-1998 static interoperability testing, • WT-051 (ed. D. Hay): ADSL dynamic interoperability testing (revision/update of TR-029), • WT-052 (ed. A. Bichon): PPP static interoperability testing, • Qualification program (PD-007, joint with G8), and • Refinement of the G.lite (PD-003, ed. B. Wiseman), G.dmt (PD-002, ed. E. Seagraves/S. Kiykioglu), G.shdsl (PD-005, ed. T. Ahmed/K. Atwell), HDSL2 (PD-004, ed. T. Ahmed/K. Atwell), and PPP (PD-006, ed. A. Bichon) testplans in the ISWG. The T&IWG also holds joint planning sessions with the marketing group to plan for interoperability demonstrations at public events such as SuperComm, CeBIT and CES. There are four dimensions that are being explored to extend interoperable capabilities. These are: 1. Interoperability with line cards capable of full rate AND lite operation via G.994.1 (G.hs) to demonstrate flexibility and wider applicability of the modems. 2. Extend performance for data transfer over longer copper loops in the presence of realistic noise to demonstrate increased customer reach potential of the technology. 3. Extend interoperability to higher layers in the protocol stack (ATM, PPP, IP) to demonstrate a wider range of applications. 4. Testing aspects of network management/configurability of the technology to demonstrate automated flow-through provisioning and order handling to ISPs and to demonstrate “plug & play” capability for service turn-up to consumers. Next Steps: • Contributions are requested for: o technical testplans (G.lite: PD-003, G.dmt: PD-002, G.shdsl: PD-005, HDSL2: PD-004, PPP: PD-006 and VDSL) and for interoperability events (ISWG). repTIWG010314-16-010626a.doc

Page 5 of 28

dslforum2001.143.1 o Progressing WT-030v10, WT-051v43, and WT-052v54, and WT-062v1. o OAM interoperability testing. o Qualification program (PD-007). o Action and living list items. Progress at VancouverPortland Meeting: • Testplans for G.dmt, G.lite, G.shdsl and, HDSL2 and PPP progressed (now proposed drafts). • Working text Ttestplan for G.dmtPPP initiated (WT-062also a proposed draft). • WT-030 (ADSL T1.413-1998 static interoperability testing), WT-051 (ADSL dynamic interoperability testing) and WT-052 (PPP static interoperability testing) progressed. • WT-030 (ADSL T1.413-1998 static interoperability testing) stalled. • Liaisons from and to TIA TR30.3, TIA TR41.9 and ETSI TM6. • Liaison to ITU-T SG15. • Developed, with the G8, an open process for updates to the reference system testing test matrix criteria. • See 010.14507 for additional results. For more detail on progress in the T&IWG, contact Fred Kaudel of Fluke Networks (see cover page for contact details). For more detail on progress in the ISWG, contact Scott Valcourt of UNH (via [email protected]). 4.

Relationship of T&IWG documents (updates of 033 accepted, updates to 033 marked) Testing Application Test Suite Document Role Interoperability ICS Conformance Static Dynamic Framework WT-027v5+/TR-023 WT–028v9+/ T1.413 Issue 2 WT-034v4+/TR-026 WT-030v10 (T1.413-1998) ATM-based TR-031 STM-based (was expected) Needed (base on WT-029v7+/ G.992.1 WT-034v4+/TR-026 TR-029/ (G.dmt) and 99.005) WT-051v43 G.992.2 (G.lite) WT-035v6+/TR-033 Further study Further study G.997.1 WT-035v6+/TR-033 (G.ploam), G.994.1 (G.hs) G.991.2 Further study Underway Underway (G.shdsl) ETSI Further study Further study PPPoA (RFC2364, WT-052v54 based on 99.018), Further study Layer 2 RFC2684 (updated RFC1483) (PPPoE, IPx) VoDSL Further study Further study HDSL2 Further study Further study

repTIWG010314-16-010626a.doc

Test Plan Interoperability Static+Dynamic

PD-007 N/A

PD-002v31 WT-062v1 PD-003v31 N/A

PD-005v21 N/A PD-006v21

N/A PD-004v21

Page 6 of 28

dslforum2001.143.1 5.

Summary of changes to and status of T&IWG documents (updates of 033 accepted, updates to 033 marked) Number (editor(s), Title completion Changes [status] most recent firs†t) date3 WT-027v5+ Completed. [TR-023] Overview of , (Barry Lerich, Fadi ADSL testing [3Q99] Daou) WT-028v9+ (Scott Valcourt, Peter Macaulay, Peter Silverman)

ADSL ANSI T1.413-1998 conformance testing ADSL dynamic interoperability testing ADSL ANSI T1.413-1998 static interoperability testing

, [2Q00]

Completed. [TR-031]

, [1Q00]

Completed. WT-051 is revising/updates. [TR-029]



T1.413 Issue 2 ATM-based ADSL ICS ITU-T G.992.2 (G.lite) ICS

, [4Q99]

Progress; editorial and technical changes. Close to being ready for straw ballot. [updated, call for contributions/editor]; there are outstanding issues and there has been slow progress; it is hoped that straw ballot status can be reached in Oslo Completed. STM-based addendum was planned [3Q99]. [TR-026]

, [2Q00]

Completed. [TR-033]

ADSL dynamic interoperability testing



WT-052v54 (Antony Bichon)

PPP static interoperability testing



WT-062v1 (Ron Brost)

ADSL Interoperability Test Plan See WT-027. See WT-034. See WT-029. See WT-028. See WT-035. G.992.1 (G.dmt) testplan

?

Revision/update of TR-029. 00.129, 00.087.2 and 00.059 not fully considered yet; tests for Annex C and Annex H added. [Revised draft generated and reviewed.] next steps: edits, stacks, network architecture, scope, test template. [Revised draft generated and reviewed.]; comments invites; several outstanding issues from Portland meeting with A&TWG. Initial draft, integrating two proposals.

G.992.2 (G.lite) testplan

N/A

WT-029v7+ (William Picken, Herman Verbueken) WT-030v10 (Ben Wiseman, Peter Macaulay, Peter Silverman)

WT-034v4 (Herman Verbueken) WT-035v6+ (Shai Finkman, Sandra Lopez) WT-051v43 (Douglas Hay, William Picken)

TR-023 TR-026 TR-029 TR-031 TR-033 PD-002v2/v31 (Ernest Seagraves/ Serdar Kiykioglu)

PD-003v2/v31 (Ben Wiseman)

† 3

See WT-027. See WT-034. See WT-029. See WT-028. See WT-035. N/A

See WT-027. See WT-034. See WT-029. See WT-028. See WT-035. Stable, being used for CES2001 admission testing. Similar to PD-00302.; tests at end are very weak; new tests on autoconfig may be added (these new tests may eventually be split out to a new PD) Stable, being used for CES2001 admission testing, some incomplete sections (not used yet, including 10 and

sequence of editors is denoted with “,”, multiple simultaneous editors is denoted with “/”. , [actual]

repTIWG010314-16-010626a.doc

Page 7 of 28

dslforum2001.143.1

PD-004v21 (Taufique Ahmed/ Keith Atwell) PD-005v21 (Taufique Ahmed/ Keith Atwell) PD-006v21 (Antony Bichon) PD-007v1 (?)

11), for further elaboration; tests at end are very weak; new tests on autoconfig may be added (these new tests may eventually be split out to a new PD). Revised version, distributed during 12/00 meeting; still has holes.

HDSL2 testplan

N/A

G.991.2 (G.shdsl) tesplan

N/A

Revised version [12/8/00]; still has holes.

PPP-based solutions interop. testplan ?

N/A

Initial version distributed during 12/00 meeting; same status as WT-052 (above).

?

Agreed in 12/00. Joint with G8. Not available yet. Based on 00.425, with changes from discussions of Attachment 9 in 002.

6. Action items (changes of 033 accepted, updates from 033 marked) This section lists the updated action items for the next T&IWG meetings. Some items were updated or generated during this meeting, as marked. 1)

2)

3)

4)

Request joint session with NM&O WG on OAM test requirements (update on 6/98 request by network management WG) covering: loopback test, ATU-R selftest, [11/99 update: ISWG has place holders in test plans that reference.] [2/00 update: Consider joint meeting with Operations & Network Management WG to discuss in 5/00.] [3/8/00 update: will be considered during planning 5/00 agenda] [5/19/00 update: no time was available for a joint meeting; loopback test and ATU-R selftest are open issues; they are in TR-005, but not in the MIB (TR-024 and RFC2662); they are partly covered in an ID supplementing RFC2662; discussion on loopback test and ATU-R selftest will continue during a joint session with the NM&OWG at our 8-9/00 meeting; the other parts of this item are covered, as updated above [7/19/00 update; a joint session with the NM&O WG has been scheduled for 10:30-11am on Sept. 1/00] [9/1/00 update 10:40am GMT: joint session required for Portland meeting (will schedule for earlier in meeting; O&NMWG already adjourned/no attendance from O&NM attendees in Dublin); area four of extensions for testing & interoperability (flow-through); action item 3 of 230; living list item 1 of 230] [10/25/00 update: earlier joint session planned for Portland meeting]. Request joint session with Architecture & Transport and VoDSL WGs again in 12/00 on PPPoA/RFC1483 [Fred]. This joint session will allow discussion of the (set of) higher layer protocol(s) for testing and potential interoperability issues in end-to-end testing. Discussion on this topic is invited for the T&IWG [email protected] e-mail reflector. Fred will contact an earlier interested party, in addition to the three responding participants to help progress this item. [3/8/00 update: progress reviewed, contact [email protected] for details] [5/19/00 update: WT052v1 and the joint session at this meeting with the A&TWG have progressed this item.] [7/19/00 update: a 9-10am meeting with the A&T WG has been scheduled for Aug. 30/00] [9/1/00 update: see action item 6, based on joint session; joint session in Portland expected on alignment of PPP testsuite/testplan with A&T WG WT on higher layers.] [10/25/00 update: Antony is progressing]. [3/14/01 update: done] Investigate ETSI noise models (high/low impedance in liaison after memorandum of understanding is settled) [expect WG draft as contribution in 8-9/00] [5/19/00 update: MoU to ETSI is TBD; expect to send liaison to ETSI in 8-9/00; may be covered by G.test.bis and G.dmt; mentioned in 160.] [7/19/00 update: awaiting MoU; Fred to contact Bernard to see if we can get these for our 8-9/00 meeting] [9/1/00 update: requested indirectly in liaison to ETSI TM6] [10/25/00 update: Bernard is requesting information; MoU is still not complete]. Contribution of TR30.3 reference (TR-30.3/99-04-620) on impairments (per 2/00 review of TIA TR30.3 incoming liaison 00.059) [Fred] Update 3/00: done, see 087. [3/8/00 update: maybe for Appendix C & figures A.1 and C.1; now these are undefined references; this contribution can help clarify.] [5/19/00 update: Fred Kaudel to update 087 to include revised figure from Randy Brown.] [7/19/00 update: in progress; AI:12 with the figure is complete and resulted in 087.1] [9/1/00 update: 087.2 is required, figure is still incorrect; will be corrected] [10/25/00 update: Randy gave Fred corrected figure to include in 087.2] [12/8/00 update: completed].

repTIWG010314-16-010626a.doc

Page 8 of 28

dslforum2001.143.1 5)

6)

7)

8)

9)

10)

11) 12) 13)

14)

15) 16)

17) 18) 19) 20) 21) 22) 23) 24)

25)

26) 27)

Frank V. to notify us on information on ETSI call for interoperability testing permanent setup for Sophia Antipolis; this may assist us in formulating future liaisons to ETSI (after our Memorandum of Understanding is agreed) [Frank V.] [5/19/00 update: information expected for 8-9/00 meeting.] [9/1/00 update: information available, see Attachment 3] [10/25/00 update: revisit with Bernard in Portland. Liaison input from ETSI expected] List of extra RFCs to consider in our work on PPP and higher-layer testing. [David Allen] [7/19/00 update: list of seven extra RFCs has been sent to Antony; Antony will put comments on the exploder by our 8-9/00 meeting] [9/1/00 update: agreed to keep LQM (RFC1989), NAI (RFC2486), too early for DHCP and WINS extensions; will add IPCP for IPv6.] [10/25/00 update: review with Antony and joint A&TWG/T&IWG session in Portland.] Send re-revised Figure 3 from 087 (transistor missing) [Randy Brown] [7/19/00 update: done, to be included in AI:6] [9/1/00 update: expected for 12/00 meeting] [10/25/00 update: corrected figure received, AI:4 handling.] Inquire about Request For Information respondents’ RFI testing capabilities [Fred Kaudel] [7/19/00 update: done; RFI respondents were encouraged to reply by our 8-9/00 meeting] [9/1/00 update: request followed up, open issue: how to deal with future responses] [10/25/00 update: specialized area, no detailed responses from our RFI respondents available.] Submit as liaison contribution and present TIA TR41.9 contributions 00029 and 030 (on transverse balance). [Randy Brown] [7/19/00 update: in progress] [9/1/00 update: transverse balance contribution presented; delete this item in 12/00.] Find out more about potential liaison(s) with TIA TR41.9 [Fred Kaudel] [7/19/00 update: to do by 8-9/00 meeting] [9/1/00: contact information available; contribution on transverse balance reviewed; Fred to contact chair on possible future liaison] [10/25/00 update: initial invitation received, liaison results expected in 12/00]. [1/24/01 update: done] Request information from ETSI TM6 on approved SM document [Bernard Dugerdil] [7/19/00 update: expect for 8-9/00 meeting] [9/1/00: not complete] Consider 00.087.2 and Paris TIA TR30.3 liaison (00.059 and 00.074) references in WT-051 [Willie Picken] [5/18/00 update: partly done in editing session of 5/17/00] [9/1/00: awaiting 00.087.2 for 12/00] Contribution of testplan for G.991.2 (G.shdsl) [Danny Gur] [7/19/00 update: Taufique and Scott will provide contribution for 8-9/00 meeting and discuss on e-mail list] [9/1/00 update: 276.1 is draft testplan, expecting inputs on tests.] Contribution on VoDSL test procedures for Dublin [Peter Macaulay] [7/19/00 update: Fred to check with Peter on status] [9/1/00 update: Peter is active in this area and plans to contribute to our 12/00 meeting.] Resolve the use of testplans with TR-023 (WT-027), start to address in 12/00 meeting [T&IWG] Contribution on an additional test requirement for WT-051 (ADSL Dynamic Interoperability Testing) relating to modem recovery after line fault conditions. [Philip Rakity] [10/25/00 update: expect for Portland meeting.] Update on status of G.dmt testplan changes that would support Annex C and Annex H operations [] Ask help to resolve Living List items 4.1, 4.2, 4.3 and 4.4 for WT-051v2 [Fred K.] [10/25/00 update: Fred to send on exploder.] [12/8/00 update: done.] Develop a living list item summarizing 00.210 and the dsl-testing list traffic on TR-031 [Scott V., Fred K.] [10/25/00 update: expect contribution for Portland.] Provide a contribution of the .zip file containing the hypertext files related to 253 for use in a web browser [Ashley P.] Consider 00.253 (and the extra contribution thereon) in enhancing WT-051 [WG] Provide a contribution of the testcase pass-fail criteria for tests of 00.253 [Ashley P.] Request contributions on conformance tests and ICS for G.shdsl and HDSL2 [WG] [10/25/00 update: Fred to send on exploder.] [12/8/00 update: done.] Which conformance tests (e.g., psd) should be performed before running G.shdsl interoperability tests [T&IWG] [10/25/00 update: possibly in contribution for Portland.] Provide contribution(s) on G.shdsl static and dynamic interoperability test suites, for consideration as working texts [Scott V.] [10/25/00 update: on track for Portland.] Provide contribution on optional testcases for G.dmt testplan testing support for Annex B [Frank V.] [10/25/00 update: expect for Portland.] Provide contribution of certification survey discussed in Orlando (5/00) [Mark P.]

repTIWG010314-16-010626a.doc

Page 9 of 28

dslforum2001.143.1 28) Provide contribution on SBC perspective for step-by-step test methods with pass-fail criteria for 12/00 meeting [Tom S.] [10/25/00 update: progressing internally, expect for Dec.; departure from prev. work in DSLF and standards; will propose tighter performance limits.] [1/24/01 update: done with 00.394] 29) Contribution of revised G.shdsl testplan, with G.hs.bis considered [Scott V.] 30) Check with Taufique A. and Keith A. for 00.270.1 (update from Dublin) [Fred K.] 31) Ask Sandra Lopez if reference paragraph for Section 6.5, paragraph 1 of WT-051 is available [Fred K.] [1/24/01 update: discuss during joint session with TR30.3 in Vancouver meeting 3/01] 32) Request TR41.9 liaison [Fred] [12/8/00 update: new item, completed by outgoing liaison to TR49.1.] 33) Put list of outgoing/incoming liaisons into minutes (use to answer, e.g., when got last PN4254 draft) [Fred] [12/8/00 update: new item] 34) Need TR30.3 liaison person (volunteer requested), status quo is direct e-mails to TR30.3 chair [volunteer] [12/8/00 update: new item] 35) Get TR30.3 868 document and ask how we can use 00.433 in our dynamic interoperability testing work. [Fred] [12/8/00 update: new item] 36) Inform ITU that some of our testplans and technical reports may have criteria beyond ITU recommendations; when stable, these may be contributed for revisions to future versions of some ITU recommendations (parts of G.99x). [Frank] [12/8/00 update: new item] 37) For 00.295, need to invite for specific (.5 day session in Vancouver), with objective for them to review agenda [12/8/00 update: new item; done with .25 day Vancouver invitation in outgoing liaison] 38) 00.296: interoperation between G.991.2 and G.994.1 (answer should be clarified in our summary that all is clear (?)). [12/8/00 update: new item] 39) Thank TR30.3 for 00.087.2 liaison, we are considering. [12/8/00 update: new item] 40) 00.376 to be testplan (proposed draft formatted/released) for further use, like other testplans. [editing this week] [12/8/00 update: new item; done, as PD-006] 41) Contribution on test mode for out of band signal level measurement [Ashley P.] [12/8/00 update: new item] 42) Review with secretariat corruption in .pdf version of WT-051v2 in 446 (OK in source, not .pdf); also for 00.347 (changebars lost). [Fred K.] [12/8/00 update: new item] 43) Report back on 00.382 incorporation into WT-051 (Ashley to coordinate at break, 12/6/00; two Steves & Andreas to help); issue of testmethods in WT-051 to be reviewed [Ashley] [12/8/00 update: new item; done] 44) Incorporate changes of 00.347 into 00.082 and consider comments in bold [Ernie S.] [12/8/00 update: new item; done, in PD-002] 45) Contribution of white paper into WTSA G.992.1 Annex X [Frank] [12/8/00 update: new item] 46) Editing of 00.385.5 (corrected .doc) into WT-051, include editing note of jitter and wander requirements for annexes C & H not yet specified, and clock signal definition, and is being worked on [Yasumasa] [12/8/00 update: new item] 47) Contribution on jitter and wander requirements for Annex H of G.992.1, and also clock signal for figure in Section D.2 for Vancouver meeting [Yasumasa] [12/8/00 update: new item] [1/24/01 update: recognized as high priority action item] [2/12/01 update: on track for Vancouver meeting (3/01)] 48) Upload ETSI liaison contribution [Bernard] [12/8/00 update: new item] [1/24/01 update: recognized as high priority action item] [2/12/01 update: liaison from TM6 discussed in Portland (12/00), and distributed, but not uploaded yet; contact Fred for softcopy in interim; G.992.1 Annex H was also reviewed.] 49) Consider disturber models based on 00.087.2 in dynamic interoperability performance work (WT-051) [12/8/00 update: new item] [1/24/01 update: recognized as high priority action item] [2/12/01 update: to be discussed jointly with TIA TR30.3 in Vancouver (3/01).] 50) Propose enhanced test procedure for PD-002 Section 4.3.2 (“Fixed Data Rate Test With FEC” [Serdar] [12/8/00 update: new item] [1/24/01 update: recognized as high priority action item] [2/12/01 update: no update available.] 51) Consider bold items of 00.347 (internal inconsistencies in 00.082) for PD-002 enhancements (e.g., Section 4.3.2: not in PD-002v1): all have been addressed with changemarkings (no outstanding bold items) [12/8/00 update: new item; done] [1/24/01 update: recognized as high priority action item] [2/12/01 update: no update available.] 52) Correct or provide a fixed version legibility troubles in both G8 attachments (8 and 9) of 002 (some of the test conditions and feature description cells for some of the rows - from 00.425 for the 3/01 meeting. [Fred] [new 1/24/01] 53) Get copy of ETSI TR 101 728 draft for living list item 3.2 [Bernard] [new 1/24/01] 54) Get ATM Forum definition of CLR [Fred] [new 1/24/01] 55) Considering chipset only interoperability events/plugfests for 2001 [new 2/12/01]

repTIWG010314-16-010626a.doc

Page 10 of 28

dslforum2001.143.1 56) Start new testplans or testcases for autoconfiguration (the existing testplans are pre-autoconfig) [new 2/12/01] 57) Start VoDSL test procedures/documents to keep up with the new developments outside the T&IWG [new 2/12/01] 58) Upload updated presentation and EIA/TIA 876 as contribution [Fred] 59) Discuss further ETSI liaison from this meeting with Bernard [Fred] 60) Give updated summary of T&IWG/ISWG work to Gavin for roadmap (00-381) potential update [Fred] 61) Submit contribution proposing content for new PD on VDSL MCM interoperability, based on ADSL testplans [Reuven] 62) Consider extra failure scenarios related to 013 and 031 jointly with A&TWG in Oslo (PPP LCP echo and I.610 fault management subset) [A&TWG, T&IWG] 63) Consider progress on L2TP tunnel establishment for WT-053/WT-052 or PD-006 in Oslo [A&TWG, T&IWG] 64) Use parts of text from 094 (for Section 2.2 and Section 3 of WT-052) in WT-052 and all of text from 094 (for Section 2.2 and Additional Work Section) for PD-006 [Antony Bichon] 65) Plan to bring extensions of PD-002 for Annex H to Oslo meeting [Masami Ueda] 66) Editing changes to PD-002 to require test functions (with details (e.g., G.992.1 loop definition) and give example(s) of equipment realizing these functions for Table 1 Loop simulator and Error rate) [editing session on 3/14/01] 67) Use 045 for PD-002v2 [editing session on 3/14/01] 68) Editing changes to PD-003 to require test functions (with details (e.g., Section 3.4) and give example(s) of equipment realizing these functions) [editing session on 3/14/01] 69) Further results of discussions on first 3 questions for 045 and 046 for 3/16/01 [Frank V., Masami U.] 70) Further results of discussion on fast retrain question for 046 for 3/16/01 (is this required in spec?; is it required given use of splitters?) [Frank V., Masami U.] 71) Use 046 for PD-003v2 [editing session on 3/14/01] 72) Liaison to ETSI TM6 to get ETSI TS 101 524 and TR 101 830 for use in testplan development in DSL Forum. [maybe via MoU instead; Fred to draft for 3/16/01] 73) Use sections 2, 3, 4, 5, not 6, 7 as optional (if implemented) for PD-005v2 (3 of 7 loops from TS 101 524) [editing session on 3/14/01] 74) Put pointer to 072 on living list (new item) [Fred] 75) Upload revised presentation and PN4254 (TIA/EIA 876 draft) as liaison [Fred] 76) Draft liaison response for TIA TR30.3 (on usefulness; may be able to use; marketing ?s, refer on) [editing session on 3/14/01, finalize 4:30-5:45pm 3/15/01] 77) Upload 10-868 as liaison from TR30.3 (addressing 12/00 question) [Fred] 78) Propose draft liaison to ITU-T on G.hs issue for review 4:30-5:45 pm on 3/15/01(discussion on nonstandard fields & management issues) [PeterS and volunteers] 79) Get new WT # for 103, Ron to be editor (draft for 3/16/01 distribution) [Fred]

7. Living list (changes of 033 accepted, updates from 033 marked) This section lists the updated living list items for the next T&IWG meetings. Due to time limitations, no items were updated during this meeting, as not marked. 1. Continue/consider/establish liaisons with standard development organizations (ETSI TM6 [Bernard D.], T1E1.4 [Tom Starr], ITU-T SG15/Q4 [Tom Starr], TIA TR30.3 [Jack Douglass], ATM Forum [Subra Ambati], IMTC (voice on DSL) [Gavin Young]), TIA TR41.9 [Anh Wride] [11/24/01 update: no new liaisons or groups were proposed.] 2. Dial Mode Impairments: for dynamic interoperability testing [based on TR30.3 liaison 11/99, 99.339 item 1] Decide if for testplans or for WT-029 revision; waiting for response from TR30.3; new [2/00] living list item on TR-029; distribute requested TR30.3 reference (087) of 2/00 liaison response (059). [3/8/00 update: 087 is available; expect to use some of its information during 5/00 meeting, for for TR-029 revisions and possibly for testplan revisions.] [5/19/00 update: references partly used for WT-051v1.] [9/1/00 update: consider in 12/00 meeting.] [1/24/01 update: review with TR30.3 in 3/01 meeting] repTIWG010314-16-010626a.doc

Page 11 of 28

dslforum2001.143.1 3.

4.

5.

ETSI xDSL Work Items in progress in EP-ATAc [source: Jean Montenot, Cetecom, jmtelecowanadoo.fr, 2/00]: This living list item provides information about xDSL Work Items in progress in ETSI, EP ATAc about POTS/xDSL compatibility and ADSL/POTS splitter specification. This item draws the attention of the DSL forum members on xDSL working items (WI) in progress under the hospice of the ETSI Project Technical Body, EP ATAc. The ATA xDSL activity is dealing with the following items: - XDSL / POTS compatibility (TR 102 139) - POTS / ADSL splitter specification (TR 101 728) The output is planned to be ETSI Technical Report (TR) providing an overview on the main issues to assist further Standardisation work. The xDSL/POTS compatibility addresses also Regulatory issues. TR 102 139: Terminal Equipment (TE); Compatibility of xDSL systems with POTS terminal equipment SCOPE: “This report reviews technical issues on the mutual compatibility of current and future POTS terminal equipment with xDSL systems operating at frequencies up to 30 MHz. This report considers both TE intended to support simultaneous operation with xDSL on the same cable pair, and TE co-existing with xDSL systems in the same access cables. The impact of home LANs working on the same cable pair as the POTS and xDSL systems is also considered.” STATUS: Draft, planned to be approved in the next ATA plenary (April 2000). TR 101 728: Specification for POTS / ADSL splitters SCOPE: “This Technical Report (TR) provides the basis for specification and test methods for the low pass section of POTS / ADSL splitters. ” STATUS: Draft, planned to be approved in the next ATA plenary (April 2000). [1/24/01 update: the 9/00 version is still the most recent, new action item taken to get a copy] [5/19/00 update: hope further information will be available after ETSI memorandum of understanding is completed (>5/00).] [9/1/00 update: ETSI is meeting next week on splitters; input expected to 12/00 meeting and teleconference.] WT-051/updated TR-029 work item [source: William Picken, 2/00] 1. Remove paragraph or provide a reference for the Telcordia study [sect. 6.5, para 1] (13/C5) [3/8/00 update: Fred to ask Telcordia (Sandra L.?) if reference paragraph is available.] [1/24/01 update: see AI:31 for update] 2. Clarify inconsistency of AAL0/AAL1 in definition of BER-application [Annex A, sect. A.3.1.2, part 3)] (28/C6) [3/8/00 update: incomplete] [8/30/00 update: clarification needed about CLR definition] [10/25/00 update: similar to WT-29 text, need to bring in ATM Forum’s CLR definition; issue of grouped/clustered errors; measure cells, but need to measure BER; TR has measure, but only for low error rate; AAL1 aggregate issue to to extra field.] [1/24/01 update: see new AI:54] 3. Expand/Clarify Dynamic Interoperability testing with POTS handset and ringing impairments – ref. to ETSI and G.TEST? [Annex C, sect. C.2, para. 4] (45a/C16) [3/8/00 update: consider 087, G.test and ETSI in 5/00.] [1/24/02 update: see 00.087.2] 4. Get better data for Fig. C.4 (Xtalk generated transfer function ripple) [Annex C] (69/C19) [3/8/00 update: incomplete data illustrated; need a volunteer, perhaps as interop test or in any test lab.] [10/25/00 update:ask Scott V. in Portland.] [1/24/01 update: Scott asked for help; expects to be able to help.] At the Vancouver meeting (3/01), UNH brought up a proposal to test EOC messages on lower layers. The approach was of good interest. It was agreed to keep the contribution in the living list, and to invite members to contribute to its further development.

repTIWG010314-16-010626a.doc

Page 12 of 28

dslforum2001.143.1 8. Request For Information (RFI) respondents contact information4 e-mail Organization contact Telephone [email protected] Westell Paul Harrington +1 630 375 4472 [email protected] Telcordia Sandra Lopez +1 732 758 3222 [email protected] UNH Scott Valcourt +1 603 862 4489 [email protected] CETECOM Andreas Ehre +49 (0) 681 598 85 52 [email protected] Admit Design Systems Douglas Hay +44 1383 828300 Ltd. [email protected] The Silicon Valley Steve Bell +1 408 432 3840 Networking Lab, Inc. x111 9. Revision history Updates to these minutes are in reverse chronological order and of the following two types: Format-change: date(m/d/yy) time(hh(0-23):mm): location: change description [changemark-status] Format-release: date(m/d/yy) time(hh(0-23):mm): released contribution#, announced (status: automatic and/or separate to T&IWG) 6/26/01 15:30 PT: released dslforum2001.143.1 (repTIWG010314-16-010626a.doc), announced (automatic + separate to T&IWG) [where usual] 6/26/01 15:15 PT: headers: convert to .pdf again and use contribution number 143.1 [none] 6/20/01 1:00 PT: Attachment 3: correct attendee names/information based on feedback in/before meeting [none] 5/14/01 16:00 PT: released dslforum2001.143.0 (repTIWG010314-16-010512b.doc), announced (automatic + separate to T&IWG) [where usual] 10. Table of Attachments The agenda and contribution log, attendance lists, and presentations of this meeting are attached, per the following table. Attachment 1: Pre-Meeting Draft Agenda and Document Log Attachment 2: Revised and Annotated Approved Agenda and Contribution Log, with Partial List of New Action Items (already integrated into Section 3): fully annotated and altered with changemarkings from Attachment 1 Attachment 3: Attendance Lists (individually for joint or editing sessions, and generally for all other sessions) Attachment 4: Presentation of Wed. morning (joint session with A&TWG) by Bruce Trumbo on 094 Attachment 5: Presentation of Jack Douglass on Wed. afternoon Attachment 6: Presentation of Thurs. morning by Peter Silverman on Use and Extension of the Vendor ID fields in G.994.1 (G.hs) Attachment 7: Presentation of Thurs. morning by Andreas Ehre on Interoperability and Performance Requirements Attachment 8: Presentation of Thurs. morning by Ashley Pickering on ADSL Physical Layer Performance Requirements Attachment 9: Presentation of Thurs. morning by Stephen Aspell on ADSL Interoperability Test Plan for DSL Forum 2001: Contribution # 2001-088 Attachment 10: Presentation of Thursday Morning by Ericka Katz on Joint Session – Trade Shows & Events, Testing & Interoperability Attachment 11: Presentation of Thursday Morning by Scott Valcourt on DSL Forum Plugfest Program Attachment 12: Presentation resulting from Thurs. morning by Scott Valcourt and Frank Van der Putten on SuperComm 2001 Interop Demonstration Attachment 13: Presentation on Thurs. afternoon by Scott Harris on the Independent Testing Labs (ITL) Process Attachment 14: Presentation on Fri. morning by Paul Drew on the OpenVoB D1 Model Implementation Guide

4

This section lists RFI respondents to the T&IWG’s 1998 RFI (http://www.dslforum.org/private/RFI_interoperability.doc). Note that Alcatel responded to that RFI, but was removed from this list during the 11/17-19/99 T&IWG meeting.

repTIWG010314-16-010626a.doc

Page 13 of 28

dslforum2001.143.1

repTIWG010314-16-010626a.doc

Page 14 of 28

dslforum2001.143.1

Attachment 1: Pre-Meeting Draft Agenda and Document Log

repTIWG010314-16-010626a.doc

Attachment 1 TIWGagnd+logVancouver010312f.doc

1 of 8

Testing & Interoperability Working Group (T&IWG1) Draft Agenda2 - Vancouver

Wednesday T&IWG: 9:30-10am (Aspen): Administrative, Liaisons, Process, Overview: Agenda Attendance Minutes: 002†, 027, 033 Liaisons (outgoing, as agreed in Portland) review/responses: 004, 005, 006 Liaisons (incoming) introduction: 00-451, 012, 026 Process: 030 Overview of all contributions: (introduction, categorization review, per draft document log herein) Other administrative: 00-381:roadmap (status of work needs tuning, e.g., updates to TR-029), 00-450:Portland closing plenary presentation (need to refine timelines) Joint (Architecture&Transport,T&IWG): 10:30-11:30am (Park Ballroom “C”): Higher Layer Protocols (PPPoA/RFC1483) and Potential Interoperability Issues: PPP: 094, WT-052; PD-006 (consider next steps: was 00-376) Minutes: 024 (page 2 for Portland joint session), 033 (open issues: action item 2 for WT-052/PD-006) T&IWG: 11:30am-noon (Aspen): Test Requirements: Previews: 055, 069, 088 (consider updates to PDs/WTs) T&IWG: 1-3pm (Aspen): Testplans: Testplans: 045, 046, 056, 072 (consider updates to PDs/WTs) T&IWG: 3:30-5pm (Aspen): Joint meeting with TIA TR30.3: Agenda Liaisons (outgoing): 005 Liaisons (incoming): 012, 026, updated PN4254 and presentation Questions: 00-295 questions; TR30.3/00-08-868 (how proposed to use, based on 12/00 review of 00-433 [002, Att. 1]) Other topics T&IWG: 7:30-10pm (Aspen): Editing Session: Edit T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) WT-051v4 (changes from contributions, editing) WT-052v5 (changes from contributions, editing) WT-030v11 (changes from contributions, editing) PD-002v2 (changes from contributions, editing) PD-003v2 (changes from contributions, editing) PD-004v2 (changes from contributions, editing) PD-005v2 (changes from contributions, editing) PD-006v2 (changes from contributions, editing)

1

All Vancouver T&IWG sessions are joint with the Interoperability Sub-Working Group (ISWG). Format: orange background=not covered; green background=covered (during meeting); annotations: “()”=before meeting; “”=during meeting † Contribution dslforum200x.abc.d is herein denoted as: abc if x is 1 and d is 0, abc.d if x is 1 and d is not 0, 0x-abc if x is not 1 and d is 0, and 0x-abc.d if x is not 1 and d is not 0. 2

Attachment 1 TIWGagnd+logVancouver010312f.doc

2 of 8

Thursday T&IWG: 8:30-10am (Aspen): Revised WTs/PDs, G.hs, Test Requirements (continued), Liaison Responses: Distribute/review revised T&IWG WTs/PDs: WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006 G.hs: 058.2 Test requirements: 055, 069, 088 Liaisons review/respond: 000-451, 012, 026, later TIA TR30.3 inputs (numbers TBD), outgoing (to ITU-T: consider possible question on G.hs/G.shdsl interoperation of 00-295 [002, Att. 1]; to ETSI TM6, to TIA TR30.3, to TIA TR41.9) Joint (Marketing:Tradeshow committee,T&IWG): 10:30am-noon (Aspen): CeBIT 2001, SuperComm 2001, Plugfests, Planning: CeBit 2001 staging results: 057 Plugfest plans for 2001: 092 CeBIT 2001 Planning SuperComm 2001 Planning T&IWG: 1-2pm (Aspen): Editing Session (continued): Edit T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) Joint (G8,T&IWG): 2-4:30pm (Garibaldi): G8 Update: Q&A, Reference Systems, ITL/RTL, Qualification: Reference Systems FAQ: 011 G8 Independent Test Lab Process: 066 Reference Systems Lab and Qualification Project: 073 Brief question & answer session Open issues (review of previous minutes: 002 Section 3, 043) Q&A Next steps T&IWG: 4:30-5:45pm (Aspen): Remaining Contributions, Liaison Responses, WTs/PDs: Review revised T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) Remaining contributions Finalize liaison responses (TIA TR30.3, TIA TR41.9, ETSI TM6, ITU-T SG15)

Attachment 1 TIWGagnd+logVancouver010312f.doc

3 of 8

Friday T&IWG: 8:30-9:15am (Aspen): Wrap-ups (1/3): Distribute/Review revised T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006), and outgoing liaisons (posted) Revise minutes document tables (relations/status), decide on straw ballot(s) Plugfest plans for 2001 (continued) Review action items Joint (Emerging DSLs,T&IWG): 9:15-10am (Aspen): Joint Items: VDSL MCM Interoperability: 059.1 Open issues/next steps T&IWG: 10:30-10:45am (Aspen): Wrap-ups (2/3): Review action items (continued) Review living list items Schedule: teleconference(s): (try three before Oslo); agenda item: future interop event scheduling discussion, and next/interim meeting(s) Joint (VoDSL,T&IWG): 10:45-11:15am (Park Ballroom “A”): Joint Items: OpenVoB Model Implementation Guide: 089 Open issues/next steps T&IWG: 11:15am-noon (Aspen): Wrap-ups (3/3): Plenary report (with next steps/timelines) Adjournment

Attachment 1 TIWGagnd+logVancouver010312f.doc

4 of 8

Testing & Interoperability Working Group (T&IWG) Draft Document Log - Vancouver format: number

title [organization/company/companies] {abstract} (note(s))

contributions (33): 098.1 097 094

092

089

088

073

072

069

066

059.1

Vancouver Contributions - PDF Files [Association Management Solutions] {Zip file of Vancouver contributions - PDF files} Vancouver Contributions - Source Files [Association Management Solutions] {Zip file containing Vancouver contributions - source files.} Proposed Additions to WT-052 for PPP Tunneling [3Com] {Additional material is proposed for WT052 to help maintain alignment with WT-053. PPP encapsulations using L2TP and PPPoE are included.} Interoperability Plugfest Plans for 2001 [University of New Hampshire] {This contribution provides a theoretical reminder of the nature of Plugfest and Group Testing, and the DSL Forum's initial plugfest raison d'etre (reason for being). Following, the major complaints that were aired in the January, 2001 Testing and Interoperability Working Group Conference Call are reviewed. Lastly, a proposed Plugfest topic list and proposed testing plan from today through December, 2001 is presented for discussion and consensus.} OpenVoB D1 Model Implementation Guide [OpenVoB, Intel, Accelerated Networks, Avail Networks, Broadband Gateways, Metaswitch Group, Data Connection, Efficient Networks, General Bandwidth, Ishoni Networks, Polycom, Santera Systems, Sedona Networks, Texas Instruments/Telogy Networks] {OpenVoB, a special interest group seeking to accelerate the deployment of standards-based voice over broadband technologies, has released its first implementation guide based on the ATM Forum’s Loop Emulation Services specification (af-vmoa-0145.000). This guide is being submitted to the DSL Forum to assist discussions related to VoDSL interoperability testing within the testing and interoperability group. It is OpenVoB’s intention to migrate our CallFestsTM (testing events) and test plan development into organizations, like the DSL Forum, as they begin to take on these activities. The member companies of OpenVoB would like to explore opportunities on how we can coordinate our work with the DSL Forum’s VoDSL interoperability efforts.} ADSL Interoperability Test Plan [SBC Technology Resources, Bell South Telecommunications, Verizon Communications] {This contribution presents a test plan for evaluation of ADSL interoperability. The tests and requirements demonstrate interoperability of ADSL modems with various DSLAMs included in the reference model. The key items of loop reach and data handling performance are tested to demonstrate compliance with deployment based requirements. This test plan is submitted to the DSL Forum for a letter ballot vote. It is proposed that the DSL Forum issue this test plan as a Technical Report.} Reference Systems Lab and Qualification Project [G8, Texas Instruments, Simpler Networks, 3COM, Alcatel, Cisco Systems, Fluke Networks, SBC, ECI Telecom, British Telecom] {This contribution summarizes the work performed by the G8 organizing committee to establish and administer an Interoperability Testing Ptogram for DSL solutions. It is the goal of this project to establish and maintain universal interoperability of modems in support of mass market deployments for DSL.} ADSL EOC Interoperability Test Suite v1.0 [University of New Hampshire] {This contribution provides a high-level Embedded Operations Channel Register Interoperability Test Plan. From this basic register test plan, several additions could be made to specifically examine op codes assigned to each register and the reaction of devices to specific op codes. The intent of this document is to provide a structure for basic vendor-to-vendor interoperability testing, as well as lead to the potential development of conformance tests.} ADSL Physical Layer Performance Requirements [BT, BTExaCT] {This contribution offers some baseline text for the DSL Forum's Independent Test Lab scheme. It is based on a combination of BT's own performance requirements [see DSLForum2000-383] and the relevant European performance requirements detailed in the ITU ADSL recommendation [G.992.1].} G8 Independed Test Lab (ITL) Process [ECI Telecom, G8] {This presentation describes the transition from the Reference System Lab (RSL) Process to the Independent Test Lab (ITL) process, to further the aims of global DSL interoperability.} VDSL - MCM Interoperability Project [Ikanos Communications, Alcatel, ST Microelectronics] {VDSL standards are in an advanced phase of approval. The authors recommend that the DSL Forum initiates work on a Interoperability Test Plan for Multi Carrier Modulation VDSL.}

Attachment 1 TIWGagnd+logVancouver010312f.doc

058.2

057 056

055

046

045

043 033

030

027

026

5 of 8

Use and Extension of the Vendor ID fields in G.994.1 (G.HS) [3Com] {The contribution discusses the importance of proper use of the Vendor ID field in G.994.1 (G.HS) to support interoperability of DSL equipment. Requests support from the DSL Forum for efforts in ITU SG 15/4 to extend these fields. It proposes rules for the appropriate population of these fields and suggests conformance tests to verify their proper use by DSL network equipment and CPE.} Summary of CeBIT Staging Results [Alcatel] {This contribution is a ppt presentation summarizing the results of the CeBIT staging event, 26 Feb to 2 March in Munich Germany.} G.shdsl Interoperability Test Plan – Proposal for Amendments [CETECOM ICT Services GmbH] {This paper discusses the plan for performing G.shdsl (ITU G.991.2) interoperability tests between system providers. After evaluating the needs for interoperability testing specific enhancements to PD-05 are proposed.} Interoperability and Performance Requirements [CETECOM ICT Services GmbH] {This document intends to initiate a discussion on performance requirements as they should appear in interoperability test plans. It raises the question if it were acceptable to reduce the performance requirement of an interoperability test but to have a performance goal which could be achieved with acceptable effort in a mixed scenario.} G.992.2 Annex A/B & C Interoperability Test Plan [Sumitomo Electric Industries, Ltd.] {This contribution provides a revision marked update to the G.992.2 Interoperability Test Plan PD-3 to extend its scope to Annex C (ADSL co-existing with TCM-ISDN). This document defines a suite of basic physical layer tests for G.992.2 Annex A/B (ADSL over POTS) and Annex C (ADSL co-existing with TCM-ISDN).} G.992.1 Annex A, B & C Interoperability Test Plan [Sumitomo Electric Industries, Ltd.] {This contribution provides a revision marked update to the G.992.1 Physical Layer Interoperability Test Plan PD-2 to extend its scope to Annex C (ADSL co-existing with TCM-ISDN). This document defines a suite of basic physical layer tests for G.992.1 Annex A (ADSL over POTS), Annex B (ADSL over ISDN) and Annex C (ADSL co-existing with TCM-ISDN).} G8 Interim Meeting Minutes - Ft. Lauderdale [ECI Telecom] {These are the minutes from the G8 interim meeeting in Ft. Lauderdale, Florida on Feb. 12, 2001.} Draft meeting minutes from the February 12th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the February 12th, 2001 meeting via teleconference at +1.303.563.6312. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on the minutes of our previous meetings, dslforum2001.027.0 – 027, and 002). See dslforum2000.450.0 – 00.450 - for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Formal Documents Process [Nortel Networks] {This process describes the progress of formalizing a Forum document from a proposal stage to becoming a Working text to finally becoming a Technical Report.} Draft meeting minutes from the January 23rd meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the January 23rd, 2001 meeting via teleconference at +1.303.563.6312. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on the minutes of our previous meeting, dslforum2001.002.0 -- 002). See dslforum2000.450.0 -- 00.450 -- for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Liaison from TIA TR30.3 Chairman: Regarding the TR30.3 Liaison Report for the December meeting and the cover letter with the PN4254 draft [TIA TR30.3/Conexant Systems] {This contribution is a liaison from the TIA TR30.3 Chairman containing the TR30.3 Liaison Report for the TR30.3 December meeting and the cover letter with the PN4254 draft (similar to PN4254-ITU in dslforum2001.012.0). TR30.3 is looking forward to having the joint meeting with the Testing & Interoperability Working Group on March 14 (Wednesday) at 3:30 pm and to presenting to the BOF meeting on March 15 (Thursday) at 6:00 to 8:00 pm. TR30.3 welcomes feedback on PN4254. Please

Attachment 1 TIWGagnd+logVancouver010312f.doc

024

012

011

006

005

004

002

00-451 00-450

00-381

6 of 8

respond by March 1, 2001, using table format referencing page number, section number, line number, type of change (technical, editorial, etc.), recommended change and reason for change.} Architecture Minutes, Portland [Nortel Networks] {This paper is the minutes for the architecture WG meetings, and also covers the joint arch/T&I effort and joint arch/VoDSL sessions and includes the slides from contribution 376 presented and the joint Arch/Test session.} Liaison from TIA TR30.3 Chairman: Regarding a Proposal for a new Project (G.eval) and an International Network Access Transmission Model for Evaluating xDSL Modem Performance (PN4254ITU Draft 1) [TIA TR30.3/Conexant Systems] {This contribution is a liaison from the TIA TR30.3 Chairman concerning a proposal for a new project (G.eval) and an international network access transmission model for evaluating xDSL modem performance (PN4254-ITU Draft 1). There are five parts to this liaison: this cover page, the project proposal (presented to T1E1.4 this week), the cover for PN4254-ITU Draft 1, the body of PN4254-ITU Draft 1, and the presentation for PN4254-ITU Draft 1 (also presented to T1E1.4 this week).} Reference Systems FAQ [Simpler Networks, G8, Texas Instruments, 3COM, Alcatel, Cisco Systems, Fluke Networks, SBC, ECI Telecom, British Telecom] {This contribution provides a summary of Frequently Asked Questions (FAQ) for the work performed by the G8 organizing committee to establish and administer an Interoperability Testing Program for ADSL solutions. It is the goal of this project to establish and maintain universal interoperability of modems in support of mass market deployments for ADSL.} Liaison to TIA TR41.9 Chair: Regarding Liaison Invitation and Invitation to Next Meeting (Completed DSL Forum Output Liaison to TIA TR41.9 from December 6 -- 8, 2000 Testing & Interoperability Working … [AdEvia Limited] {This contribution is a liaison to the TIA TR41.9 Chair concerning a liaison invitation and an invitation to our next meeting. This is the completed DSL Forum output liaison to TIA TR41.9 from the December 6 -- 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Liaison to TIA TR30.3 Chair: Regarding DSL Testing and Interoperability (Completed DSL Forum Output Liaison to TIA TR30.3 from December 6 -- 8, 2000 Testing & Interoperability Working Group Meeting in … [AdEvia Limited] {This contribution is a liaison to the TIA TR30.3 Chair concerning DSL testing and interoperability, focusing on dynamic interoperability testing work. This is the completed DSL Forum output liaison to TIA TR30.3 from the December 6 -- 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Liaison to ETSI TM6 Chairman: Regarding DSL Testing and Interoperability (Completed DSL Forum Output Liaison to ETSI TM6 from December 6 -- 8, 2000 Testing & Interoperability Working Group Meeting in P… [AdEvia Limited] {This contribution is a liaison to the ETSI TM6 Chairman concerning DSL testing and interoperability, focusing on SHDSL/SDSL work. This is the completed DSL Forum output liaison to ETSI TM6 from the December 6 – 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Draft meeting minutes from the December 6th -- 8th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the December 6th -- 8th, 2000 meeting in Portland, Oregon. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on dslforum2000.381.0 -381, and 351). See 450 for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. See another contribution for the minutes of the joint session with the Architecture & Transport Working Group on December 6th. Minutes of the Interoperability SubWorking Group (ISWG) meetings are included. Minutes of the joint session with the Operations & Network Management Working Group on December 8th are included. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Liaison from ETSI Monterey meeting [Motorola Semiconductors] {This is a liaison from the ETSI TM6 Monterey meeting regarding interoperability.} Testing & Interoperability Working Group Presentation to Dec. 8, 2000 DSL Forum Closing Plenary on Status after Meeting in Portland [Fluke Networks] {This contribution summarizes recent progress in the Testing & Interoperability Working Group (T&IWG) and the Interoperability Sub-Working Group. Included are key results, relationship of T&IWG documents, information on outgoing liaisons and joint activities, the teleconference dates, information on interoperability testing events, G8 activities and areas for which contributions are requested. Several typos on slide three were corrected.} Technical Committee Roadmap [AdEvia Limited] {This contribution provides the latest

Attachment 1 TIWGagnd+logVancouver010312f.doc

00-295

7 of 8

revision of the technical roadmap for the DSL Forum. It presents a top-level overview of the structure of the technical committee together with a summary of the key objectives, priorities and timescales for the individual technical working groups. The objective is to provide a complete overview of the DSL Forum’s technical work in terms of both scope and timescales. This should be particularly useful for new members to understand the key technical issues that the Forum is addressing and in which working groups the various tasks are being dealt with. It is hoped that the individual technical working groups will find time either during or between meetings to review their objectives, priorities and next steps in order that a detailed and up to date timeline for each groups work can be incorporated in the next iteration of this roadmap.} Liaison to TIA TR30.3 Chair: Regarding Liaison Report on TR30.3 Meetings -- August 2000 (Completed DSL Forum Output Liaison to TIA TR30.3 from August 30 -- September 1, 2000 Testing & Interoperability [AdEvia Limited] {This contribution is a liaison to the TIA TR30.3 Chair concerning the recent TIA TR30.3 input liaisons dslforum2000-287 (Regarding Liaison Report on TR30.3 Meetings -- August, 2000: Simulator Diagram), dslforum2000-280 (Regarding liaison report on TR30.3 meetings - August 2000) and dslforum2000-206 (Regarding Liaison Report on Joint TR30.3 and T1E1.4 Meetings -- May 9-10, 2000). This is the completed DSL Forum output liaison to TIA TR30.3 (copying T1E1.4) from the August 30 -- September 1, 2000 Testing & Interoperability Working Group meeting in Dublin.}

testplans (5): PD-006v1 PPP-based Solutions Interoperability Test Plan [Network Equipment Technologies] PD-005v1 G.991.2 (G.shdsl) Physical Layer Interoperability Test Plan [Intel/Adtran] PD-004v1 HDSL2 Physical Layer Interoperability Test Plan [Intel/Adtran/University of New Hampshire] PD-003v1 G.992.2 (G.lite) Interoperability Test Plan [Texas Instruments] PD-002v1 G.992.1 (G.dmt) Interoperability Test Plan [Centillium Communications] working texts (3): WT-052v4 PPP static interoperability testing [Network Equipment Technologies] WT-051v3 ADSL dynamic interoperability testing [Admit Design Systems/National Semiconductor] WT-030v10 ADSL ANSI T1.413-1998 static interoperability testing [Texas Instruments/East by North/3COM] technical reports (5; completed, for reference and enhancement): TR-033 ITU-T G.992.2 (G.lite) ICS [Orckit/Telcordia Technologies] TR-031 ADSL ANSI T1.413-1998 conformance testing [Texas Instruments/East by North/3COM] TR-029 ADSL dynamic interoperability testing [National Semiconductor/Alcatel] (being enhanced by WT-051) TR-026 T1.413 Issue 2 ATM-based ADSL ICS [Alcatel] TR-023 Overview of ADSL testing [Telcordia Technologies/GenRad]

Attachment 1 TIWGagnd+logVancouver010312f.doc

8 of 8

Testing & Interoperability Working Group (T&IWG) Draft Contribution Categories - Vancouver administrative (10; see contribution entries above for details): 098.1 Contributions - .pdfs 097 Contributions - sources 043 Feb. 12th G8 meeting minutes 033 Feb. 12th T&IWG teleconf. minutes 030 Formal documents process 027 Jan. 23rd T&IWG teleconf. minutes 024 Portland Architecture minutes (joint session record) 002 Portland T&IWG minutes 00-450 Portland T&IWG closing plenary presentation 00-381 Roadmap (not on CD-ROM) working texts/proposed drafts (1; see contribution entries above for details): 094 WT-052 proposed additions plugfests/tradeshows (2; see contribution entries above for details): 092 2001 plans for interoperability plugfests 057 Summary of CeBIT staging results voice testing (1; see contribution entries above for details): 089 OpenVoB model implementation guide VDSL testing (1; see contribution entries above for details): 059.1 VDSL – MCM interoperability project G.hs interoperability (1; see contribution entries above for details): 058.2 Use and extension of the vendor ID fields in G.994.1 (G.hs) testplans (4; see contribution entries above for details): 072 ADSL EOC interoperability test suite v1.0 056 G.shdsl interoperability test plan 046 G.992.2 Annex A/B & C interoperability test plan 045 G.992.1 Annex A/B & C interoperability test plan test requirements (3; see contribution entries above for details): 088 ADSL interoperability test plan 069 ADSL physical layer performance requirements 055 Interoperability and performance requirements G8 (3; see contribution entries above for details): 073 Reference systems lab and qualification project 066 G8 independent test lab (ITL) process 011 Reference systems FAQ liaisons (6; see contribution entries above for details): 026 TIA TR30.3 incoming 012 TIA TR30.3 incoming 006 TIA TR41.9 outgoing 005 TIA TR30.3 outgoing 004 ETSI TM6 outgoing 00-451 ETSI TM6 incoming 00-295 TIA TR30.3 outgoing (not on CD-ROM)

dslforum2001.143.1

Attachment 2: Revised and Annotated Approved Agenda and Contribution Log, with Partial List of New Action Items (already integrated into Section 6): fully annotated and altered with changemarkings from Attachment 1

repTIWG010314-16-010626a.doc

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Testing & Interoperability Working Group (T&IWG1) Draft Agenda2 - Vancouver

Wednesday T&IWG: 9:030-10am (Aspen): Administrative, Liaisons, Process, Overview: Agenda Attendance Minutes: 002†, 027 , 033 Liaisons (outgoing, as agreed in Portland) review/responses: 004 , 005 , 006 Liaisons (incoming) introduction: 00-451 , 012 , 026 Process: 030 Overview of all contributions: (introduction, categorization review, per draft document log herein) Other administrative: 00-381:roadmap (status of work needs tuning, e.g., updates to TR-029), 00-450:Portland closing plenary presentation (need to refine timelines) Other: Proposal to initiate work on VDSL MCM Interoperability (059.1) ; additional liaison from Don Clarke on VDSL is expected to generate a liaison response from our liaison officer (Harry Mildonian) Joint (Architecture&Transport,T&IWG): 10:30-11:30am (Park Ballroom “C”): Higher Layer Protocols (PPPoA/RFC1483) and Potential Interoperability Issues: Agenda Discussion of additional work for WT-047 (extra failure scenarios, related to 013 and 031) PPP: 094 , WT-052 ; PD-006 (consider next steps: was 00-376) Minutes: 024 (page 2 for Portland joint session) , 033 (open issues: action item 2 for WT-052/PD-006 ) T&IWG: 11:30am-noon (Aspen): Test Requirements: Previews: 055 , 069 , 088 (consider updates to PDs/WTs) T&IWG: 1-3pm (Aspen): Testplans: Testplans: 045 mandatory; mode selection is made at ATU-C in spec, can discuss more); 3. on 400Hz DCS clock, does the ATU-C need to generate its own clock if an external one isn’t provided (e.g., for one-line for plugfests)? (A: can be done with internal clock; ATU-C generates)>, 046 , 056 this is for an Annex B testplan; ? on compliance/then interoperability for spectral aspects (do you want to include testplan from standard?) A: until now, we don’t have such a testplan (for G.shdsl, this is a proposal: dynamic interop isn’t enough; maybe this is for a conformance doc); ? on spectral compatibility section (all rqmts related to psd should be done wrt a specific set of speeds): A: use parts of a table from ETSI TR 101 830; ?: IP systems, why not others (e.g., G.703); A: for mass market, can be extended.; ? may need to be extended for North American applications, A: need contribution (not all loops from TS 101 524)>, 072 PD, maybe TR/WT; not complete (values in registers); propose for living list on EOC testing; Matt to present again on Thursday> (consider updates to PDs/WTs) T&IWG: 3:30-5pm (Aspen): Joint mMeeting with TIA TR30.3 representatives: Agenda Quick review of BoF: update to 012 folded into biggest bin; new technologies can go longer); loops with bridged taps (all new, existed in Telcordia study), T1E1 is working on connection type 2 (slide 28); extra 400 feet of loop in CO (not considered elsewhere; also 300 feet of drop wire that isn’t in other models); wants input on transient impairments; concern about complexity -> to run less of test, use truncated impairments (stays statistically accurate); seven premises wiring models; 276 tests times seven types (for 100% models; can run 20 or 40 seconds for each test); model may be used for certification test/process;; future inputs on PN4255 requested (work has just started)> Liaisons (outgoing): 005 Liaisons (incoming): 012 , 026 , updated PN4254 and presentation Questions: 00-295 questions ; TR30.3/00-08-868 (how proposed to use, based on 12/00 review of 00-433 [002, Att. 1]) Other topics: next steps (how to use, plans for future liaisons) T&IWG: 7:30-10pm (Aspen): Editing Session: Edit T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) WT-051v4 (changes from contributions, editing) WT-052v5 (changes from contributions, editing) WT-030v11 (changes from contributions, editing) PD-002v2&v3 (changes from contributions, editing) PD-003v2&v3 (changes from contributions, editing) PD-004v2 (changes from contributions, editing) PD-005v2 (changes from contributions, editing) PD-006v2 (changes from contributions, editing) Integration of 069, 088 Draft liaison to TIA TR30.3 Draft liaison to OpenVoB

3 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Thursday T&IWG: 8:30-10am (Aspen): Revised WTs/PDs, G.hs, Test Requirements (continued), Liaison Responses: Distribute/review revised T&IWG WTs/PDs: WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006 G.hs: 058.2 don’t use vendor ID (standard is supposed to be good enough): A: slop is there -> address real problems in standards (this is a patch; not a fix; proprietary extensions are fact of life); need to protect base (may put in EOC in future); some proprietary features are denied by vendor ID> Test requirements (continued): 055 no minimum perf or guarantees)>, 069, 088, combined draft (103) Moved to 3/15/01 afternoon: Relationship to WT-051/TR-029 Moved to 3/15/01 afternoon: Liaisons review/respond: 000-451, 012, 026, later TIA TR30.3 inputs (numbers TBD), outgoing (to ITU-T: consider possible question on G.hs/G.shdsl interoperation of 00-295 [002, Att. 1]; to ETSI TM6 , to TIA TR30.3, to TIA TR41.9) Joint (Marketing:Tradeshow committee,T&IWG): 10:30am-noon (Aspen): CeBIT 2001, SuperComm 2001, Plugfests, Planning: Invitation to help Peter S. during lunch for ITU-T liaison drafting Attendance/agenda CeBit 2001 staging results: 057 Plugfest plans for 2001: 092 CeBIT 2001 Planning SuperComm 2001 Planning Plugfest plans for 2001: 092

4 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Other items T&IWG: 1-2pm (Aspen): Editing Session (continued): Edit T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) Joint (G8,T&IWG): 2-4:130pm (Garibaldi): G8 Update: Q&A, Reference Systems, ITL/RTL, Qualification: Reference Systems FAQ: 011 G8 Independent Test Lab Process: 066 Brief question & answer session Break from 3-3:30pm: dessert downstairs Reference Systems Lab and Qualification Project: 073 Reference Systems FAQ: 011 Brief question & answer session (continued) Brief question & answer session Open issues (review of previous minutes: 002 Section 3, 043) Q&A Next steps T&IWG: 4:230-65:145pm (Aspen): Remaining Contributions, Liaison Responses, WTs/PDs: Continued from 3/15/01 morning: Test requirements (continued): (069 and 088 are in combined draft) 103 Moved from 3/15/01 morning: Relationship to WT-051/TR-029 Moved from 3/15/01 morning: Liaisons review/respond: 00-451 , 012, 026, later TIA TR30.3 inputs (numbers TBD), outgoing (to ITU-T: consider possible question on G.hs/G.shdsl interoperation of 00-295 [002, Att. 1] ; to ETSI TM6 , to TIA TR30.3, to TIA TR41.9) Review revised T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, PD-002, PD-003, PD-004, PD-005, PD-006) Remaining contributions Ersatz bar Finalize liaison responses (TIA TR30.3, TIA TR41.9, ETSI TM6, ITU-T SG15/Q4), OpenVoB partial, VDSL MCM interoperability (059.1) EOC testplan: 072 Other topics

5 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Friday T&IWG: 8:30-9:2015am (Aspen): Wrap-ups (1/3): Distribute/Review revised T&IWG/ISWG WTs and PDs (WT-030, WT-051, WT-052, WT-062, PD-002, PD-003, PD-004, PD-005, PD-006v2), and outgoing liaisons (posted) Revise minutes document tables (relations/status), decide on straw ballot(s) Plugfest plans for 2001 (continued): 092 Review action items Joint (Emerging DSLs,T&IWG): 9:2015-10am (Aspen): Joint Items: FSVDSL input document FS-109-R0: structure VDSL MCM Interoperability: 059.1 Open issues /next steps T&IWG: 10:30-10:45am (Aspen): Wrap-ups (2/3): PD-002v3/PD-003v3 update discuss/distribute Plugfest plans for 2001 (continued) No time: delayed: Review action items (continued) No time: delayed: Review living list items No time: delayed: Schedule: teleconference(s): (try three before Oslo); agenda item: future interop event scheduling discussion, and next/interim meeting(s) Joint (VoDSL,T&IWG): 10:45-11:2015am (Park Ballroom “A”): Joint Items: OpenVoB Model Implementation Guide: 089 Liaison response to OpenVoB Open issues/next steps Other items

6 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

T&IWG: 11:215am-noon (Aspen): Wrap-ups (3/3): Review action items Review living list items Schedule: teleconference(s): (try three before Oslo); agenda item: future interop event scheduling discussion, and next/interim meeting(s) Does Annex B testplan (PD-002v3) contain/allow echo cancellation for Europe? A: Annex B leaves it open, but most operators use FDD (Freq. Div Dup.; not FDM) instead of echo cancellation (combinations are possible; partial overlapping). Plenary report (with next steps/timelines) No time: Revise minutes document tables (relations/status), Adjournment

7 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Testing & Interoperability Working Group (T&IWG) Draft Document Log - Vancouver format: number

title [organization/company/companies] {abstract} (note(s))

contributions (33): 098.1 097 094

092

089

088

073

072

069

066

059.1

Vancouver Contributions - PDF Files [Association Management Solutions] {Zip file of Vancouver contributions - PDF files} Vancouver Contributions - Source Files [Association Management Solutions] {Zip file containing Vancouver contributions - source files.} Proposed Additions to WT-052 for PPP Tunneling [3Com] {Additional material is proposed for WT052 to help maintain alignment with WT-053. PPP encapsulations using L2TP and PPPoE are included.} Interoperability Plugfest Plans for 2001 [University of New Hampshire] {This contribution provides a theoretical reminder of the nature of Plugfest and Group Testing, and the DSL Forum's initial plugfest raison d'etre (reason for being). Following, the major complaints that were aired in the January, 2001 Testing and Interoperability Working Group Conference Call are reviewed. Lastly, a proposed Plugfest topic list and proposed testing plan from today through December, 2001 is presented for discussion and consensus.} OpenVoB D1 Model Implementation Guide [OpenVoB, Intel, Accelerated Networks, Avail Networks, Broadband Gateways, Metaswitch Group, Data Connection, Efficient Networks, General Bandwidth, Ishoni Networks, Polycom, Santera Systems, Sedona Networks, Texas Instruments/Telogy Networks] {OpenVoB, a special interest group seeking to accelerate the deployment of standards-based voice over broadband technologies, has released its first implementation guide based on the ATM Forum’s Loop Emulation Services specification (af-vmoa-0145.000). This guide is being submitted to the DSL Forum to assist discussions related to VoDSL interoperability testing within the testing and interoperability group. It is OpenVoB’s intention to migrate our CallFestsTM (testing events) and test plan development into organizations, like the DSL Forum, as they begin to take on these activities. The member companies of OpenVoB would like to explore opportunities on how we can coordinate our work with the DSL Forum’s VoDSL interoperability efforts.} ADSL Interoperability Test Plan [SBC Technology Resources, Bell South Telecommunications, Verizon Communications] {This contribution presents a test plan for evaluation of ADSL interoperability. The tests and requirements demonstrate interoperability of ADSL modems with various DSLAMs included in the reference model. The key items of loop reach and data handling performance are tested to demonstrate compliance with deployment based requirements. This test plan is submitted to the DSL Forum for a letter ballot vote. It is proposed that the DSL Forum issue this test plan as a Technical Report.} Reference Systems Lab and Qualification Project [G8, Texas Instruments, Simpler Networks, 3COM, Alcatel, Cisco Systems, Fluke Networks, SBC, ECI Telecom, British Telecom] {This contribution summarizes the work performed by the G8 organizing committee to establish and administer an Interoperability Testing Ptogram for DSL solutions. It is the goal of this project to establish and maintain universal interoperability of modems in support of mass market deployments for DSL.} ADSL EOC Interoperability Test Suite v1.0 [University of New Hampshire] {This contribution provides a high-level Embedded Operations Channel Register Interoperability Test Plan. From this basic register test plan, several additions could be made to specifically examine op codes assigned to each register and the reaction of devices to specific op codes. The intent of this document is to provide a structure for basic vendor-to-vendor interoperability testing, as well as lead to the potential development of conformance tests.} ADSL Physical Layer Performance Requirements [BT, BTExaCT] {This contribution offers some baseline text for the DSL Forum's Independent Test Lab scheme. It is based on a combination of BT's own performance requirements [see DSLForum2000-383] and the relevant European performance requirements detailed in the ITU ADSL recommendation [G.992.1].} G8 Independed Test Lab (ITL) Process [ECI Telecom, G8] {This presentation describes the transition from the Reference System Lab (RSL) Process to the Independent Test Lab (ITL) process, to further the aims of global DSL interoperability.} VDSL - MCM Interoperability Project [Ikanos Communications, Alcatel, ST Microelectronics] {VDSL standards are in an advanced phase of approval. The authors recommend that the DSL Forum initiates work on a Interoperability Test Plan for Multi Carrier Modulation VDSL.}

8 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

058.2

057 056

055

046

045

043 033

030

027

026

Use and Extension of the Vendor ID fields in G.994.1 (G.HS) [3Com] {The contribution discusses the importance of proper use of the Vendor ID field in G.994.1 (G.HS) to support interoperability of DSL equipment. Requests support from the DSL Forum for efforts in ITU SG 15/4 to extend these fields. It proposes rules for the appropriate population of these fields and suggests conformance tests to verify their proper use by DSL network equipment and CPE.} Summary of CeBIT Staging Results [Alcatel] {This contribution is a ppt presentation summarizing the results of the CeBIT staging event, 26 Feb to 2 March in Munich Germany.} G.shdsl Interoperability Test Plan – Proposal for Amendments [CETECOM ICT Services GmbH] {This paper discusses the plan for performing G.shdsl (ITU G.991.2) interoperability tests between system providers. After evaluating the needs for interoperability testing specific enhancements to PD-05 are proposed.} Interoperability and Performance Requirements [CETECOM ICT Services GmbH] {This document intends to initiate a discussion on performance requirements as they should appear in interoperability test plans. It raises the question if it were acceptable to reduce the performance requirement of an interoperability test but to have a performance goal which could be achieved with acceptable effort in a mixed scenario.} G.992.2 Annex A/B & C Interoperability Test Plan [Sumitomo Electric Industries, Ltd.] {This contribution provides a revision marked update to the G.992.2 Interoperability Test Plan PD-3 to extend its scope to Annex C (ADSL co-existing with TCM-ISDN). This document defines a suite of basic physical layer tests for G.992.2 Annex A/B (ADSL over POTS) and Annex C (ADSL co-existing with TCM-ISDN).} G.992.1 Annex A, B & C Interoperability Test Plan [Sumitomo Electric Industries, Ltd.] {This contribution provides a revision marked update to the G.992.1 Physical Layer Interoperability Test Plan PD-2 to extend its scope to Annex C (ADSL co-existing with TCM-ISDN). This document defines a suite of basic physical layer tests for G.992.1 Annex A (ADSL over POTS), Annex B (ADSL over ISDN) and Annex C (ADSL co-existing with TCM-ISDN).} G8 Interim Meeting Minutes - Ft. Lauderdale [ECI Telecom] {These are the minutes from the G8 interim meeeting in Ft. Lauderdale, Florida on Feb. 12, 2001.} Draft meeting minutes from the February 12th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the February 12th, 2001 meeting via teleconference at +1.303.563.6312. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on the minutes of our previous meetings, dslforum2001.027.0 – 027, and 002). See dslforum2000.450.0 – 00.450 - for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Formal Documents Process [Nortel Networks] {This process describes the progress of formalizing a Forum document from a proposal stage to becoming a Working text to finally becoming a Technical Report.} Draft meeting minutes from the January 23rd meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the January 23rd, 2001 meeting via teleconference at +1.303.563.6312. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on the minutes of our previous meeting, dslforum2001.002.0 -- 002). See dslforum2000.450.0 -- 00.450 -- for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Liaison from TIA TR30.3 Chairman: Regarding the TR30.3 Liaison Report for the December meeting and the cover letter with the PN4254 draft [TIA TR30.3/Conexant Systems] {This contribution is a liaison from the TIA TR30.3 Chairman containing the TR30.3 Liaison Report for the TR30.3 December meeting and the cover letter with the PN4254 draft (similar to PN4254-ITU in dslforum2001.012.0). TR30.3 is looking forward to having the joint meeting with the Testing & Interoperability Working Group on March 14 (Wednesday) at 3:30 pm and to presenting to the BOF meeting on March 15 (Thursday) at 6:00 to 8:00 pm. TR30.3 welcomes feedback on PN4254. Please

9 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

024

012

011

006

005

004

002

00-451 00-450

00-381

respond by March 1, 2001, using table format referencing page number, section number, line number, type of change (technical, editorial, etc.), recommended change and reason for change.} Architecture Minutes, Portland [Nortel Networks] {This paper is the minutes for the architecture WG meetings, and also covers the joint arch/T&I effort and joint arch/VoDSL sessions and includes the slides from contribution 376 presented and the joint Arch/Test session.} Liaison from TIA TR30.3 Chairman: Regarding a Proposal for a new Project (G.eval) and an International Network Access Transmission Model for Evaluating xDSL Modem Performance (PN4254ITU Draft 1) [TIA TR30.3/Conexant Systems] {This contribution is a liaison from the TIA TR30.3 Chairman concerning a proposal for a new project (G.eval) and an international network access transmission model for evaluating xDSL modem performance (PN4254-ITU Draft 1). There are five parts to this liaison: this cover page, the project proposal (presented to T1E1.4 this week), the cover for PN4254-ITU Draft 1, the body of PN4254-ITU Draft 1, and the presentation for PN4254-ITU Draft 1 (also presented to T1E1.4 this week).} Reference Systems FAQ [Simpler Networks, G8, Texas Instruments, 3COM, Alcatel, Cisco Systems, Fluke Networks, SBC, ECI Telecom, British Telecom] {This contribution provides a summary of Frequently Asked Questions (FAQ) for the work performed by the G8 organizing committee to establish and administer an Interoperability Testing Program for ADSL solutions. It is the goal of this project to establish and maintain universal interoperability of modems in support of mass market deployments for ADSL.} Liaison to TIA TR41.9 Chair: Regarding Liaison Invitation and Invitation to Next Meeting (Completed DSL Forum Output Liaison to TIA TR41.9 from December 6 -- 8, 2000 Testing & Interoperability Working … [AdEvia Limited] {This contribution is a liaison to the TIA TR41.9 Chair concerning a liaison invitation and an invitation to our next meeting. This is the completed DSL Forum output liaison to TIA TR41.9 from the December 6 -- 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Liaison to TIA TR30.3 Chair: Regarding DSL Testing and Interoperability (Completed DSL Forum Output Liaison to TIA TR30.3 from December 6 -- 8, 2000 Testing & Interoperability Working Group Meeting in … [AdEvia Limited] {This contribution is a liaison to the TIA TR30.3 Chair concerning DSL testing and interoperability, focusing on dynamic interoperability testing work. This is the completed DSL Forum output liaison to TIA TR30.3 from the December 6 -- 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Liaison to ETSI TM6 Chairman: Regarding DSL Testing and Interoperability (Completed DSL Forum Output Liaison to ETSI TM6 from December 6 -- 8, 2000 Testing & Interoperability Working Group Meeting in P… [AdEvia Limited] {This contribution is a liaison to the ETSI TM6 Chairman concerning DSL testing and interoperability, focusing on SHDSL/SDSL work. This is the completed DSL Forum output liaison to ETSI TM6 from the December 6 – 8, 2000 Testing & Interoperability Working Group meeting in Portland.} Draft meeting minutes from the December 6th -- 8th meeting of the Testing & Interoperability Working Group (T&IWG) of the DSL Forum [Fluke Networks] {This contribution contains the draft T&IWG minutes from the December 6th -- 8th, 2000 meeting in Portland, Oregon. An overall summary is provided of the status of the T&IWG and the ISWG after this meeting (based on dslforum2000.381.0 -381, and 351). See 450 for the summary presentation of T&IWG and ISWG results and status to the DSL Forum Closing Plenary on December 8th, including key results, information on outgoing liaisons, T&IWG/ISWG teleconference dates, information on interoperability events, G8 activities and areas for which contributions are requested. See another contribution for the minutes of the joint session with the Architecture & Transport Working Group on December 6th. Minutes of the Interoperability SubWorking Group (ISWG) meetings are included. Minutes of the joint session with the Operations & Network Management Working Group on December 8th are included. The approved, updated and annotated agenda, updated opens (relationship of documents, summary of documents, action items, living list items, areas for which contributions are requested), RFI respondent contacts, and attendance lists are included.} Liaison from ETSI Monterey meeting [Motorola Semiconductors] {This is a liaison from the ETSI TM6 Monterey meeting regarding interoperability.} Testing & Interoperability Working Group Presentation to Dec. 8, 2000 DSL Forum Closing Plenary on Status after Meeting in Portland [Fluke Networks] {This contribution summarizes recent progress in the Testing & Interoperability Working Group (T&IWG) and the Interoperability Sub-Working Group. Included are key results, relationship of T&IWG documents, information on outgoing liaisons and joint activities, the teleconference dates, information on interoperability testing events, G8 activities and areas for which contributions are requested. Several typos on slide three were corrected.} Technical Committee Roadmap [AdEvia Limited] {This contribution provides the latest

10 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

00-295

revision of the technical roadmap for the DSL Forum. It presents a top-level overview of the structure of the technical committee together with a summary of the key objectives, priorities and timescales for the individual technical working groups. The objective is to provide a complete overview of the DSL Forum’s technical work in terms of both scope and timescales. This should be particularly useful for new members to understand the key technical issues that the Forum is addressing and in which working groups the various tasks are being dealt with. It is hoped that the individual technical working groups will find time either during or between meetings to review their objectives, priorities and next steps in order that a detailed and up to date timeline for each groups work can be incorporated in the next iteration of this roadmap.} Liaison to TIA TR30.3 Chair: Regarding Liaison Report on TR30.3 Meetings -- August 2000 (Completed DSL Forum Output Liaison to TIA TR30.3 from August 30 -- September 1, 2000 Testing & Interoperability [AdEvia Limited] {This contribution is a liaison to the TIA TR30.3 Chair concerning the recent TIA TR30.3 input liaisons dslforum2000-287 (Regarding Liaison Report on TR30.3 Meetings -- August, 2000: Simulator Diagram), dslforum2000-280 (Regarding liaison report on TR30.3 meetings - August 2000) and dslforum2000-206 (Regarding Liaison Report on Joint TR30.3 and T1E1.4 Meetings -- May 9-10, 2000). This is the completed DSL Forum output liaison to TIA TR30.3 (copying T1E1.4) from the August 30 -- September 1, 2000 Testing & Interoperability Working Group meeting in Dublin.}

testplans (5): PD-006v1 PPP-based Solutions Interoperability Test Plan [Network Equipment Technologies] PD-005v1 G.991.2 (G.shdsl) Physical Layer Interoperability Test Plan [Intel/Adtran] PD-004v1 HDSL2 Physical Layer Interoperability Test Plan [Intel/Adtran/University of New Hampshire] PD-003v1 G.992.2 (G.lite) Interoperability Test Plan [Texas Instruments] PD-002v1 G.992.1 (G.dmt) Interoperability Test Plan [Centillium Communications] working texts (3): WT-052v4 PPP static interoperability testing [Network Equipment Technologies] WT-051v3 ADSL dynamic interoperability testing [Admit Design Systems/National Semiconductor] WT-030v10 ADSL ANSI T1.413-1998 static interoperability testing [Texas Instruments/East by North/3COM] technical reports (5; completed, for reference and enhancement): TR-033 ITU-T G.992.2 (G.lite) ICS [Orckit/Telcordia Technologies] TR-031 ADSL ANSI T1.413-1998 conformance testing [Texas Instruments/East by North/3COM] TR-029 ADSL dynamic interoperability testing [National Semiconductor/Alcatel] (being enhanced by WT-051) TR-026 T1.413 Issue 2 ATM-based ADSL ICS [Alcatel] TR-023 Overview of ADSL testing [Telcordia Technologies/GenRad]

11 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

Testing & Interoperability Working Group (T&IWG) Draft Contribution Categories - Vancouver administrative (10; see contribution entries above for details): 098.1 Contributions - .pdfs 097 Contributions - sources 043 Feb. 12th G8 meeting minutes 033 Feb. 12th T&IWG teleconf. minutes 030 Formal documents process 027 Jan. 23rd T&IWG teleconf. minutes 024 Portland Architecture minutes (joint session record) 002 Portland T&IWG minutes 00-450 Portland T&IWG closing plenary presentation 00-381 Roadmap (not on CD-ROM) working texts/proposed drafts (1; see contribution entries above for details): 094 WT-052 proposed additions plugfests/tradeshows (2; see contribution entries above for details): 092 2001 plans for interoperability plugfests 057 Summary of CeBIT staging results voice testing (1; see contribution entries above for details): 089 OpenVoB model implementation guide VDSL testing (1; see contribution entries above for details): 059.1 VDSL – MCM interoperability project G.hs interoperability (1; see contribution entries above for details): 058.2 Use and extension of the vendor ID fields in G.994.1 (G.hs) testplans (4; see contribution entries above for details): 072 ADSL EOC interoperability test suite v1.0 056 G.shdsl interoperability test plan 046 G.992.2 Annex A/B & C interoperability test plan 045 G.992.1 Annex A/B & C interoperability test plan test requirements (3; see contribution entries above for details): 088 ADSL interoperability test plan 069 ADSL physical layer performance requirements 055 Interoperability and performance requirements G8 (3; see contribution entries above for details): 073 Reference systems lab and qualification project 066 G8 independent test lab (ITL) process 011 Reference systems FAQ liaisons (6; see contribution entries above for details): 026 TIA TR30.3 incoming 012 TIA TR30.3 incoming 006 TIA TR41.9 outgoing 005 TIA TR30.3 outgoing 004 ETSI TM6 outgoing 00-451 ETSI TM6 incoming 00-295 TIA TR30.3 outgoing (not on CD-ROM) new action items: -

Format: text [actionee(s)] Upload updated presentation and EIA/TIA 876 as contribution [Fred]

12 of 139

Attachment 2 TIWGagnd+logVancouver010316g-final.docAttachment 1 TIWGagnd+logVancouver010312f.doc

-

Discuss further ETSI liaison from this meeting with Bernard [Fred] Give updated summary of T&IWG/ISWG work to Gavin for roadmap (00-381) potential update [Fred] - Submit contribution proposing content for new PD on VDSL MCM interoperability, based on ADSL testplans [Reuven] - Consider extra failure scenarios related to 013 and 031 jointly with A&TWG in Oslo (PPP LCP echo and I.610 fault management subset) [A&TWG, T&IWG] - Consider progress on L2TP tunnel establishment for WT-053/WT-052 or PD-006 in Oslo [A&TWG, T&IWG] - Use parts of text from 094 (for Section 2.2 and Section 3 of WT-052) in WT-052 and all of text from 094 (for Section 2.2 and Additional Work Section) for PD-006 [Antony Bichon] - Plan to bring extensions of PD-002 for Annex H to Oslo meeting [Masami Ueda] Editing changes to PD-002 to require test functions (with details (e.g., G.992.1 loop definition) and give example(s) of equipment realizing these functions for Table 1 Loop simulator and Error rate) [editing session on 3/14/01] Use 045 for PD-002v2 [editing session on 3/14/01] Editing changes to PD-003 to require test functions (with details (e.g., Section 3.4) and give example(s) of equipment realizing these functions) [editing session on 3/14/01] Further results of discussions on first 3 questions for 045 and 046 for 3/16/01 [Frank V., Masami U.] Further results of discussion on fast retrain question for 046 for 3/16/01 (is this required in spec?; is it required given use of splitters?) [Frank V., Masami U.] Use 046 for PD-003v2 [editing session on 3/14/01] - Liaison to ETSI TM6 to get ETSI TS 101 524 and TR 101 830 for use in testplan development in DSL Forum. [maybe via MoU instead; Fred to draft for 3/16/01] Use sections 2, 3, 4, 5, not 6, 7 as optional (if implemented) for PD-005v2 (3 of 7 loops from TS 101 524) [editing session on 3/14/01] - Put pointer to 072 on living list (new item) [Fred] - Upload revised presentation and PN4254 (TIA/EIA 876 draft) as liaison [Fred] Draft liaison response for TIA TR30.3 (on usefulness; may be able to use; marketing ?s, refer on) [editing session on 3/14/01, finalize 4:30-5:45pm 3/15/01] - Upload 10-868 as liaison from TR30.3 (addressing 12/00 question) [Fred] - Propose draft liaison to ITU-T on G.hs issue for review 4:30-5:45 pm on 3/15/01(discussion on non-standard fields & management issues) [PeterS and volunteers] - Get new WT # for 103, Ron to be editor (draft for 3/16/01 distribution) [Fred]

13 of 139

dslforum2001.143.1

Attachment 3: Attendance Lists (individually for joint or editing sessions, and generally for all other sessions)

repTIWG010314-16-010626a.doc

Attachment 3

Attachment 3: Attendance Lists

Table of attendance lists Attendance at joint session with Architecture & Transport Working Group ............................................... 1 Attendance at editing session .................................................................................................................... 3 Attendance at joint session with Trade Shows (Marketing Committee) ...................................................... 3 Attendance at joint session with G8 .......................................................................................................... 4 Attendance at joint session with VODSL .................................................................................................. 5 Attendance at Editing Sessions ................................................................................................................. 6 Attendance at TIA TR30.3 session............................................................................................................ 7 Attendance for all other sessions............................................................................................................... 7

Attendance at joint session with Architecture & Transport Working Group Name – last Aboukarr Almog Ambrose Aspell Atwell Bienert Bono Bower Bowlin Bichon Brost Brusca Chan Claessen Cresswell DeCelles Doligez Doucette Douglas Doukoglou Duft Edeen Edmon Ehre Ekman Finguelernt Gade Gee Gemmer Haag Hart Harvey Hay Herring Hoo Jackson Jayavaman Jones

Name – first Bakra Yossi Matt Steve Keith Rolf David Jeff Chris Antony Ron Michael Dennis Guus Jason John Thierry Marc Jack Tilemachos Brad Dan Gene Andreas Per-Ove Jacob Raja Ralph Thomas Thomas Charles Roy Doug Malcoum Kenneth Martin Shankav David

Company Alcatel Telrad Knowledge Junction SBC TRI Adtran TUV Rheinland Pulse Qwest Intertek Testing Service Net.com SBC Verizon Analog Devices Alcatel VIRATIA LSI Logic LEA Catena Networks Conexant/Mindspring OTE SA (“”) Nokia Qwest SBC Cetecom Ericsson ADC ECI Telecom LSI Logic Siemens Deutsche Telecom State Farm Analog Devices Admit System TUT Systems Legerity Inc. Virata Wind River Fujitsu

Att3corrected-attendancelists-010620a.doc

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] [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]

Page 1 of 9

Attachment 3 Jones Jones Juhava Juras Kaudel Kennedy Kido Kikunaga Kim Kingdom Kitai Langhamme Lindecke LU MacLachlan Maierhofer Molinari O’Donnell Ohara Okado Pennington Phelan Pickering Pizzi Polychronopoulos Raskin Roberts Russell Russell Saito Sarmiento Say Schewe Schwantje Silveran Starr Tilocca

Stephen K. Sharyl Pasi Walter Fred Larry Yuichi Yasumasa Anne Steve Atsushi Michael Sascha Yaran Al Herbert Mauro Paul Yasuo Hiroshi Mark Martin Ashley Steven Spyros Rick David Mary Mark Russ Romy Sabit Millard Ken Peter Tom Mauro

Samsung Nortel Networks Elisa Communications Siemens/Infineon Fluke Networks PMC-Sierra NTT Toshiba 3Com KTL OKI Electric Deutsche Telecom Siemens/Infincon Broadcom Corp Spirent Aheadcom Marconi Comm Acterina Toshiba NEC Corning Cable Systems Eicon Networks BT 3Com OTE Verizon Advanced Data Microsoft Adtran Cisco Verizon Sprint Next Level Comm.s Excelsus Technologies Alcatel 3Com SBC Telecom Italia

Trumbo Tsukioka Tucker Ueda Varatzas Wang Wiseman Wood Yang Zagabley Zimmerman

Bruce Yoichi Curtis Masami Ilias Isaac Ben John Max Nelson Michael

3Com/commworks Hitachi, ltd. Sprint Sumitomo Electric OTE (Hellenic Telecom Org) Ishoni Networks TI Otorola ADC ADC ADC

Att3corrected-attendancelists-010620a.doc

[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] alt: mauro.tilocca@tilabit [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Page 2 of 9

Attachment 3 Attendance at editing sessions Name – last Bichon Bowlin Brost Doligez Ehre Gee Hoo Kaudel Kido Kikunaga Kitai Lindecke Pickering Russell Silverman Tsukioka Ueda

Name – first Antony Chris Ron Thierry Andreas Ralph Ken Fred Yuichi Yasumasa Atsushi Sascha Ashley Mark Peter Yoichi Masami

Company Net.com Intertek Testing Services SBC LEA CETECOM LSI Logic Legerity Fluke Networks NTT Toshiba OKI Electric In/incom/Siemens BT Cisco 3Com Hitachi, Ltd. Sumitomo Electric

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]

Attendance at joint session with Trade Shows (Marketing Committee) Name – last Adcock Bahalul Bienert Bono Bowlin Burd Calderon Davis DeCelles Doligez Doucette Ehre Ekman Ezra Fausch Fim Gee Gur Henter Hoo Jackson Jones Jones Juraidiai Juras Kaudel Kido Kim King

Name – first Martin Rammy Rolf David Chris Nick Peter Jeff John Thirry Marc Andreas Per-oue Avi Jay Chandler Ralph Danny Mahnaina Ken Martin Sharyl Stephen K Ramey Walter Fred Yuichi Anne Neal J.

Company Comtest Networks Conexant TUV Rheinland of NA Pulse Intertek Testing Services Conexant Paradyne Paradyne Networks LSI LEA Catena Cetecom Ericsson BeConnected Alcatel Nortel LSI Logic Metalink Westell Legerity Virata Nortel Samsung Siemens Infineon Fluke Networks NTT 3Com Infineon

Att3corrected-attendancelists-010620a.doc

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] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Page 3 of 9

Attachment 3 Kingdom Kitai Lang Langlois Langston Lindeke Loh Melvin Mildoman Morley Mosley O’Donnell Okado Ovor Peden Russell Russell Sarmiento Sawyer Schwazzband Suyderhoud Stanberger Steenstra Tsukioka Ueda Valcourt Yang Zagalsky

Steve Atsushi David Matthew Daun Susche Carolyn David Harry Tim Tony Paul Hiroshi Moshe Mark Mark Mary Romy Bob Ishai Henri Franz Mark Yoichi Masami Scott Max Nelson

KTL OKI Electric Infineon/Siemens UNH Sismatel Inl/incon/Siemens Ahead Communications ADTRAN Lucent Xavi Technology Verizon Acterna NEC AFC Simpler Networks Cisco ADTRAN Sprent Communications Wilccom Telrad networks Oki Alicad Communications Conexant Hitachi, ltd Sumitomo Electric UNH ADC ACD Telecommunications

[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] nelson_zagalsky#adc.com

Attendance at joint session with G8 Name – last Alfonso Atwell Bieert Bono Bowlin Brost DeCelles DiGiulio Doligez Doucette Douglass Edeen Ekman Gee Gemmer Gur Harris

Name – first Eddie Keith ROLF David Chris Ron John Tony Thierry Marc Jack Dan Per-ove Ralph Thomas Danny Scott

Company Verizon - Telus ADTRAN TUV Rheinland of NL Pulse Intertek Testing Services SBC LSI Logic Arescom LEA Catena Networks Conexant/Mindspeed Qwest Erisson LSI Logic Siemens Metalink ECI

Att3corrected-attendancelists-010620a.doc

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]

Page 4 of 9

Attachment 3 Harvey Hay Hoo Jeffries Jenness Jones Jones Juraidini Kaudel Kido Kikunaga Kim Kingdom Mildonian O’Donnell Okado Peden Pickering Radde Raskin Russell Saito Sarmiento Schneider Schwarzland Segeu Segev Tsukioka Ueda Webster Wiseman Wu Yang Yi Zagalsky

Roy Doug Ken Ron Bob Sharyl David Ramey Fred Yuichi Yasumasa Anne Steve Harry Paul Hiroshi Mark Ashley Dirk Rick Mark Russ Romy Ken Ishai Reuven Reuven Yoichi Masami Jim Ben Tony Max Hon Nelson

Analog Devices Admit Systems Legerity Occam Networks Siemens Nortel Fujitsu Siemens Fluke Networks NTT Toshiba 3Com DTL Lucent Acterna NEC Simpler Networks BT QSC Verizon Advanced Data Cisco Verizon Spirent Telebyte Telrad Networks Ikanos Comm Ikanos Hitachi,ltd Sumitomo Electric Conexant TI Motorola ADC Telecream ADC Telecommunication

[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]

Attendance at joint session with VODSL Name – last Afzal Bienert Bowlin Doloik Drew Edeen Ehre Gee Hoo Ishii Jones Jones Juraidimi

Name – first Mohammad Rolf Chris Benjamin Paul Dan Andreas Ralph Ken Hiroshi Sharyl Stephen K Ramey

Company Teradyne TUV Rheinland NA Intertek Testing Services Voip Metaswitch Qwest CETECOM LSI Logic Legerity Inc. NTT Nortel Samsung Siemens

Att3corrected-attendancelists-010620a.doc

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]

Page 5 of 9

Attachment 3 Kaudel Kido Kikunaga Kitai Kroninger Macgerl O’Donnell Okado Saracino Tilocca Tsukioka Ueda Van der Putten Wetzel

Fred Uuichi Yasmasa Atsushi Bob Gerhard Paul Hiroshi Concita Mauro Yoichi Masami Frank Greg

Fluke Networks NTT Toshiba OKI Electric ADC Siemans Acterna NEC Telecom Italia Lab Telecom Italia Lab Hitachi, ltd Sumitomo Electric Alcatel Covad

[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]

Attendance at Emerging DSLs joint session Name – last Alfono Bienert Bowlin Brost Doligez Ehre Ezra Gee Greggains Hoo Jones Jones Juraidini Kaudel Kido Kitai Korolkiewicz Langlois Ngo O’Donnell Okado Owr Pickering Russell Schwarzband Segev Starr Storry Tilocca

Name – first Eddie Rolf Chris Ron Thierry Andreas Avi Ralph David Ken Sharyl Stephen K. Ramey Fred Yuchi Atsushi Piotr Matthew Paul Paul Hiroshi Danny Ashley Mark Ishai Reuven Tom Chuck Mauro

Company Verizon/Telus TUV Rheinland NA Intertek Testing Services SBC LEA CETECOM BeConnected LSI Logic Gorham & Partners, Ltd. Legerity Nortel Samsung Siemens Fluke Networks NTT OKI Electric Ericsson UNH Conexant/Mindspeed Acterna NEC Metalink BT Cisco Telrad Networks Ikanosq SBL ALCATEL Telecom Italia

Tsukioka Ueda Valcount Van der Putten

Yoichi Masami Scott Frank

Hitachi, ltd Sumitomo Electric UNH ALCTEL

Att3corrected-attendancelists-010620a.doc

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] piotr.korolkiewicz@ ericsson.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] alt [email protected] [email protected] [email protected] [email protected] [email protected]

Page 6 of 9

Attachment 3 Wienhofer Yang

Herbert Max

Aheadcom ADC

[email protected] [email protected]

Attendance at TIA TR30.3 session Name – last Adcock Aspell Bienert Bower Bowlin Chan DeCellesi DeVries Doligez Douglass Doucette Edeen Ehre Gee Hill Hoo Jones Juraidini Kaudel Kitai Nguyen O’Donnell Okado Raskin Russell Russell Sarmiento Schneider Ueda Webster Yang Zagabley

Name – first Martin Steve Rolf Jeff Chris Dennis John Jo Dee Thierry Jack Marc Dan Andreas Ralph Dan Ken Sharyl Ramey Fred Atsushi Loc Paul Hiroshi Rick Mary Mark Romy Ken Masami Jim Max Nelson

Company Comtest Networks SBC TRI TUV Rheinland NA Qwest Intertek Testing Services Analog Devices LSI Logic Intertek Testing Services LEA Conexant/Mindspeed Catena Networks Qwest Cetecom,ict LSI Logic Jetstream Legerity Nortel Siemens Fluke Networks OKI Electric TDK Semi. Corp Acterna NEC Verizon Advanced Data Adtran Cisco Spirent Telebyte Sumitomo Electric Conexant ADC ADC

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] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] nelson.zagabley@adc/cp,

Company Comtest Networks SBC TRI Net.com TUV Rheinland of N.A. Pulse Qwest Intertek Testing sergices SBC Analog Devices Spirent Communications Intertek Testing Services

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]

Attendance for all other sessions Name – last Adcock Aspell Bichon Bienert Bono Bower Bowlin Brost Chan DeSchiffart DeVries

Name – first Martin Steve Antony Rolf David Jeff Chris Ron Dennis Charley JoDee

Att3corrected-attendancelists-010620a.doc

Page 7 of 9

Attachment 3 DiGiolio Digiulio Doligez Doucette Douglass Edeen Ekman Ezra Gee Greggains Gur Haag Harvey Hay Hoo Jones Jones Juraidini Juroidius Kaudel Kelliher Kido Kikunaga Kim Kingdom Kitai Korolkiewicz Koshiba Landis Langlois Lanjhammer Lindecke Malinari McKee Ngo Nguyen O’Donnell O’Shea Ohara Okado Peden Pennington Pickering Raskin Ray Russell Russell Sarmiento Sawyer Schneider Schwarzband

Tony Tony Thierry Marc Jack Dan Per-Ove Avi Ralph David Danny Thomas Roy Doug Ken Sharyl Stephen K. Ramey Ramey Fred Patrick Yuichi Yasumasa Anne Steve Atsushi Piotr Kuoru Ed Matthew Michael Sascha Mauro Tom Paul Loc Paul Lisa Yasuo Hiroshi Mark Mark Ashley Rick Bob Mark Mary Romy Bob Ken Ishai

Arescom Arescom LEA Catena Networks Conexant/Mindspeed Qwest Ericsson Beconnected LSI Logic Gorham & Partners, Ltd. Metalink Deutsche Telekom Analog Devices Admit Systems Legerity Inc. Nortel Networks Samsung Siemens Siemens Fluke Networks Aware NTT Toshiba 3Com KTL` OKI Electric Ericsson NTT Globespan UNH Deutsche Telekom Siemens/Infineon Marconi Comm Centillium Conexan/Mindspeed TDK Semiconductor Acterna Tut Systems Toshiba NEC Simpler Networks Corning Cable Systems BT Verizon Advanced Data Verilink Cisco Adtran Spirent Wilcom Telebyte Telrad Networks

Att3corrected-attendancelists-010620a.doc

[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] [email protected] [email protected]

Page 8 of 9

Attachment 3 Segev Silverman Smith Starr Steenstra Stevens Storry Suyderhoud Tsukioka Tucker Ueda Valcourt Van der Putten Webster Wiseman Wu Yang Yi Young Youngberg

Reuven Peter Art Tom Mark Tamara Chick Henri Yoichi Curtis Masami Scott Frank Jim Ben Tony Max Hon Gavin Pete

Ikanos Comm 3Com Suttle SBC Conexant Nokia ALCATeL OKI Hitachi, ltd Sprint Sumitomo Electric UNH Alcatel Conexant TI Motorola ADC TeleDream Adevia Sprint

Att3corrected-attendancelists-010620a.doc

[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]

Page 9 of 9

dslforum2001.143.1

Attachment 4: Presentation of Wed. morning (joint session with A&TWG) by Bruce Trumbo on 094

repTIWG010314-16-010626a.doc

Modifications to WT-052 for PPP Tunneling Bruce Trumbo / CommWorks Vancouver, B.C.

DSLF2001-XXXX

WT-052 Addresses PPP • Current Focus Is TR-012, PPPoA • WT-053 Is Follow-On to TR-12 – PPP Tunneling

>L2TP (RFC 2661) over ATM >PPPoE (RFC 2516) over ATM – Additional, non-PPP transports

• Proposed Additions Encompass Tunneling – L2TP and PPPoE DSLF2001-XXXX

End-to-End Protocol Diagrams • WT-052 Describes “Core Network Architectures” TR-025 – Figures 2, 3, 4 in Section 2 – Endpoint protocol stacks and end-to-end protocols on one diagram – Focus on PPP endpoints – Different PPP encapsulations at each endpoint – Only PPPoA shown at CPE end

DSLF2001-XXXX

End-to-End Protocol Diagrams PPP over ATM

Network Protocol

Network Protocol

PPP

PPP

AAL5

AAL5

ATM

ATM

ATM

ATM

PHY

PHY PHY

PHY DSL

DSL

NSP/LNS Router

ATM Switch

Access Node (DSLAM)

PC/ATU-R

DSLF2001-XXXX

End-to-End Protocol Diagrams PPP over ATM

Network Protocol

Network Protocol Network Protocol

PPP

PPP AAL5

IP, FR, ATM etc.

IP, FR, ATM etc.

AAL5

PHY PHY

PHY

PHY

NSP/LNS Router

ATM

BAS

DSLF2001-XXXX

ATM PHY

DSL

Access Node (DSLAM)

ATM DSL PC/ATU-R

Multiple PPP Protocol Stacks • WT-053 Has Additional PPP Encapsulations – Avoid n x m diagram problem

• Proposals: – Show WT-053 PPP stacks in separate diagrams – Keep PPPoA as “reference” stack for end-to-end diagrams (Figures 2, 3 & 4) – Tunneled PPP stacks only apply to LAC, BAS architectures

DSLF2001-XXXX

PPP Stack Diagram - L2TP L2TP over ATM

PPP

PPP

L2TP

L2TP

AAL5

AAL5

ATM DSL LAC or BAS

ATM PHY

DSL

Access Node (DSLAM)

DSLF2001-XXXX

ATM DSL PC/ATU-R

PPP Stack Diagram - PPPoE PPPoE over RFC 2684

PPP

PPP

PPPoE

PPPoE

RFC2684

RFC2684

AAL5

AAL5

ATM DSL LAC or BAS

ATM PHY

DSL

Access Node (DSLAM) DSLF2001-XXXX

ATM DSL PC/ATU-R

Scope of Static Interop Testing • Add Tunneling to Diagram A11

Service Provider

L3

Regional Broadband Network

U Access Node

T Network Termination

IP

L2½

PPP

L2TP

L2¼

V

A10

PPPoA or L2TP or PPPoE DSLF2001-XXXX

S Customer Premises Network

Customer Premise

Additional Work - Test Groups • PPP Tunneling Protocols – Use standard PPP (RFC 1661) with simple wrapper encapsulation – Also have separate, non-PPP control channel

• All PPP Tests Are Applicable • Additional Test Groups Needed – Tunneling control channel protocols

DSLF2001-XXXX

dslforum2001.143.1

Attachment 5: Presentation of Jack Douglass on Wed. afternoon

repTIWG010314-16-010626a.doc

dslforum2001.143.1

Attachment 6: Presentation of Thurs. morning by Peter Silverman on Use and Extension of the Vendor ID fields in G.994.1 (G.hs)

repTIWG010314-16-010626a.doc

Use and Extension of the Vendor ID fields in G.994.1 (G.HS) DSL-Forum 2001-058 Peter Silverman 3CO M

An Example of the Problem Interoperability between XXXXX-based CPE and AAAAA or BBBBBB-based DSLAMs is not very clear cut. The XXXXX chipset provides flexibility to the modem implementers (i.e. these values have to be tweaked for each type of DSLAM to achieve a “good” connection). There is no clear mechanism, especially use of VENDOR ID fields, to determine the right DSLAM/chipset parameters. To make matters more complicated, the VVVVV DSLAM deviates from the reference design for the AFE necessitating yet another set of tweak values.

Vendor ID Interop Problems • Vendor info required to allow high quality interop - both in development, testing, and in field • Current Vendor ID in G.HS not adequate – No rules on use, thus inconsistent use by vendors – No enough ‘space’ to transmit required data

• Issue for both CPE and DSLAM Vendors • Chipset ID alone not sufficient

What is required in the Vendor ID Field • .A consistent identification of the vendor of the modem at the • • • •

other end of the U interface (in the case of a DSLAM we mean the vendor of the line card that supports the port). .A consistent identification of the specific modem type or model being communicated with over the U interface. .A consistent identification of the version or release of the modem model being communicated with. .A consistent identification of the vendor of the chipset being used to provide the physical layer in the remote device. .A consistent identification of the version or release of both the chipset and the firmware loaded into the chipset.

Existing G.994.2 Vendor ID • 8 Octets – 2 octet Country ID – 4 octet Vendor ID – 2 octet Version ID

• The problems – No rules on use – not enough info • need more then one ID • Version ID does not have enough points (only 256)

What the Industry Needs to do • .A consistent set of rules for the use of the vendor ID and version ID must be developed by the industry. • .Tests for the use of these fields must be developed as part of interoperability and conformance testing. This is to ensure that developers of modems properly identify their products. • .Unfortunately the existing code space in G.HS does not provide sufficient code space to carry the information to properly identify a modem’s vendor and version to those who wish to interoperate. Identification of both the builder of the DSL equipment and of the 'chipset' supporting the PHY layer is required at the time of initialization to ensure interoperability.

What DSL Forum Needs to do • .Support for an initiative in the ITU SG 15/4 to add code points to G.HS (G.994.1) to extend the information available at PHY layer initialization about the 'vendor' of components in a DSL Modem. The DSL Forum should indicate its support for this effort via Liaison. • Help Develop Interoperability rules for the use of both the existing Vendor ID fields in G.HS and for the proposed extensions. Unless there is an agreement on conventions as to how these are to be used by implementers of DSL equipment, the existence of the fields will be of little use. • Develop proposal to define tests to ensure these fields are used properly by DSL equipment as part of the interoperability and conformance.

Changes to G.994.2 • G.994.1 defines an expedited procedure for defining new code points in G.994.1. Backward compatible changes such as those proposed in T1E1.4/2000-123 can be added directly by the study group and do not require more formal and time consuming procedures such as 'Determination and Decision'. Therefore the proposed changes can be made in as few as two meetings of ITU-T SG 15/4. • It is proposed that the DSL Forum Testing and Interoperability group liaison ITU-T SG 15/4 indicating our support for proposals in T1E1.4/2001-123.

What Needs to Be Done • We Recommend liaisoning to ITU SG 15/4 • .That a backward compatible rules be developed for the existing vendor ID • .That the proposed new 'Npar' fields for the 'equipment vendor ID' also be defined as it will allow additional information in the four byte version field and can be used to identify the line card provider within a DSLAM. • .That the new 'equipment vendor ID' will be used in the case of CO side equipment to identify the vendor of the Line Card in the DSLAM. In the case of CPE equipment the 'equipment vendor ID' will identify the vendor of the modem. • .That the proposed new 'Npar' fields for the 'chipset' (tranceiver vendor id) be required to be used.

What needs to be done - cont. • .That the proposed four octets of version id for both equipment vendor and chipset in the new 'Npar's' be used as follows - the first two octets be used by the vendor to identify a 'part number' that is a specific product ID or part number for the equipment or tranciever. - that the third octet be used to identify the hard ware version or release of the 'product'. - that the fourth octet be used to identify the software/firmware version or release of the 'product'. - that the vendor will update the various fields defined above whenever significant changes occur in the device. It will be entirely up to particular vendor as to what constitutes a new 'part' or 'product' (a change in the first two octets),or a new version (a change in either of the last two octets of the version ID).

Issues • ITU-T vs. DSL Forum Responsibilities – Are rules for the use of the new fields ITU or DSL Forum Reponsibility

• Backward Compatibility of use of existing Vendor ID – Need new info, but cannot effect existing interop

• Development of G.994 Test plans by DSL Forum

Proposals • .That the DSL Forum Liaison ITU-T SG 15/4 to request enhancement to the vendor ID fields in G.994.1, supporting the concepts in T1E1.4/2001-123. • .That this liaison include specific requests to support both an equipment vendor ID and a transceiver ID in the new codepoints. Also that the liaison request that the new codepoints include a four octet version code. • That the Liaison indicate that a backward compatibility with existing use of the Vendor ID be protected for existing equipment • .

Proposal Continued • That the interoperability testing and conformance specification being developed by the DSL Forum include specifications for the use of the vendor fields and that population and transmission of these fields be required as part of meeting any conformance requirements for initialization of DSL interfaces. • That specific tests on the use of the vendor Ids be included in any conformance testing requirements for initialization of DSL connections based on ITU-T Recommendations. • It is appropriate to develop a specific, and focused, TR on the use and testing G/HS including these fields. As G.HS issues are common to all PHY layers that use G.HS

dslforum2001.143.1

Attachment 7: Presentation of Thurs. morning by Andreas Ehre on Interoperability and Performance Requirements

repTIWG010314-16-010626a.doc

DSL-Forum 2001.055

Interoperability and Performance Requirements

Andreas Ehre CETECOM ICT Services GmbH Untertuerkheimer Straße 6 – 10 66117 Saarbruecken Germany

What is Interoperability? Many things are clearly defined and the question of Interoperability reduces to a “yes“ or “no“ assessment. e.g. synchronisation, exchange of OAM information

But how to deal with performance? • dependent on many aspects of the line interface and signal processing • definitely not a “yes” or “no” characteristic, but a “as good as” or “better than” characteristic.

The world of performance in practice OPTIMAL SCENARIO - Standard or Specification in progress - contains characteristics of the line interface - Simulations lead to a performance goal - performance goal gets adopted for the standard or specification - performance goal is based on more or less ideal assumptions

The world of performance in practice PROPRIETARY SCENARIO - both line terminations are developed by the same company - good chance to achieve acceptable performance - however, in most cases more than one development loop is needed to achieve the full standard performance

The world of performance in practice REAL SCENARIO - line terminations in one link are developed by different companies - developers of the line terminations do follow the standard, but implementations will differ from company to company - full standard performance can only be achieved in several loops and only with the close contact to the developers of the counterpart unit

The world of performance in practice We live in the REAL SCENARIO! In the REAL SCENARIO one must expect a long and cost-intensive process to achieve full standard performance. BUT: Network Operators and their Customers need interoperability with acceptable performance as soon as possible to launch/use a flexible and cost-effective service.

The Way Out: Definition of Performance Classes Performance Class „expected performance“ definition: a system achieving 90 % or more of the standard performance when operating in an interoperability test environment can claim interoperability serving „expected performance“. Performance Class „full standard performance“ definition: a system achieving 100 % or more of the standard performance when operating in an interoperability test environment can claim interoperability serving „full standard performance“.

The Way Out: Definition of Performance Classes Performance Class „exceeding performance“ definition: a system achieving 108 % or more of the standard performance when operating in an interoperability test environment can claim interoperability serving „exceeding performance“.

DSL-Forum 2001.055

Interoperability and Performance Requirements

Andreas Ehre CETECOM ICT Services GmbH Untertuerkheimer Straße 6 – 10 66117 Saarbruecken Germany

dslforum2001.143.1

Attachment 8: Presentation of Thurs. morning by Ashley Pickering on ADSL Physical Layer Performance Requirements

repTIWG010314-16-010626a.doc

Ashley Pickering BTexaCT DSLForum2001-069 ADSL Physical Layer Performance Requirements

DSLForum2001-069 ADSL Physical Layer Performance Requirements • Baseline text proposal for the DSL Forum’s Independent Test Laboratory scheme • A combination of BT’s requirements [DSLForum2000-383] and European requirements from the ITU recommendation G.992.1 • Details physical layer requirements • Covers full rate, ADSL over POTS systems only

DSLForum2001-069 ADSL Physical Layer Performance Requirements • It is proposed to combine these requirements with others into a living document at this meeting • Higher layer and service specific requirements should be separated from the physical layer requirements • Other operators should be encouraged to contribute their own requirements before we finalize the document

dslforum2001.143.1

Attachment 9: Presentation of Thurs. morning by Stephen Aspell on ADSL Interoperability Test Plan for DSL Forum 2001: Contribution # 2001-088

repTIWG010314-16-010626a.doc

ADSL Interoperability Test Plan for DSL Forum 2001: Contribution # 2001-088 Vancouver, BC March 12 - 16, 2001 Stephen M. Aspell, P.E., Ron Brost, P.E., Tom Starr - SBC TRI James Viator - Bell South Michael Brusca – Verizon Communications

Introduction • SBC, Bell South and Verizon are three of the largest DSL providers in the US • Over 1,500,000 DSL lines installed, millions more to come • SBC - 61 million access lines • Bell South - 25 million access lines • Verizon - 71 million access lines

ADSL Interoperability Test Plan Changes between Portland and Vancouver Test Plans: • Reduce the number of test points: – white noise - 50% reduction – 24 HDSL - 68 % reduction – 24 DSL - 63 % reduction – 5 T1 - 63 % reduction – low fixed rate test - 58 % reduction – bridged tap tests - 47 % reduction in 9 and 12 kft, 79% reduction in 17.5 kft tests

ADSL Interoperability Test Plan Changes between Portland and Vancouver Test Plans: • Decreased required rates for 5 T1 tests • Completed bridged tap requirements, RFI ingress, and modem startup time • Added Verizon as co-contributor

ADSL Interoperability Test Plan What constitutes Deployable Interoperability? • • • •

No loop reach penalty No throughput penalty No latency penalty Same operating performance regardless of chipset or software load

ADSL Interoperability Test Plan What is the goal for Deployable Interoperability? • • • • •

Any modem on any DSLAM No degradation in performance Off the shelf Dial up modem model Consumer’s freedom of choice depends on interoperability

ADSL Interoperability Test Plan • The proposed interoperability test plan has requirements in the following areas: – – – – – – – – – – – –

Loop reach - Variable and Fixed Rate Standard and Bridged Tap loops FTP Throughput Latency Frame Size Noise Survivability ATM Connectivity Electrical Compatibility ADSL Functionality Usability RFI ingress Modem start up time

ADSL Interoperability Test Plan • Loop reach testing: – No Noise – White Noise – 24 HDSL + white noise – 24 DSL + white noise – 5 T1 adjacent binder + white noise • Loop models: – Variable length – CSA 4 – ANSI 13 • Fixed rate testing - commercial rate, no noise • Bridged tap tests

ADSL Interoperability Test Plan • Interoperability Testing – 3rd party lab evaluation/certification – minimize test time/maximize test usefulness – test model: 5 days against multiple DSLAMs • Against current reference system – carrier request complete test against x DSLAMs – short sample test against all remaining DSLAMs

ADSL Interoperability Test Plan • When do we need this ? – Before DSL can reach its full potential • Timeline – When – How

ADSL Interoperability Test Plan • Conclusion – A test plan that can be used to demonstrate deployable interoperability has been submitted as contribution #2001-088. The test plan has been cosponsored by SBC, Bell South and Verizon. – Motion: This test plan should be put out for letter ballot as a technical report from the DSL Forum and adopted as the interoperability test plan for the DSL Forum. – Seconds?

dslforum2001.143.1

Attachment 10: Presentation of Thursday Morning by Ericka Katz on Joint Session – Trade Shows & Events, Testing & Interoperability

repTIWG010314-16-010626a.doc

Joint Session Trade Shows & Events Testing & Interoperability March 15, 2001 1

High Level Network Architecture DSL Forum Interoperability Showcase

t e n er t n I

FTP Server DT POP

25 CPEs

DSL

HUB

A D S L

VideoConf Server

100 Base-T

10 DSLAMs

STM1

STM1

Passport 7480Half Class C IP address for DSL network ATM VoDSL Switch Gateway Forum Booth CeBIT 2001 2

Shasta 5000 BSN

CeBIT Test Results As reported by Frank Van der Putten

CeBIT Technical Lead 3

Backend Equipment þ DSLAMs connect through the Nortel Passport 7000 ATM Switch and Nortel Shasta 5000 BSN BRAS (Alternative is to connect directly to 100Base-T hub). þ The staging internet connection is ISDN-BRA with PPP access and single dynamic public IP address. Nortel provides router and 100Base-T hub to staging. Router connects to ISDN-BRA and to hub. þ The CeBIT internet connection is 100Base-T Ethernet with 124 fixed public IP addresses. Deutsche Telekom provides 100Base-T hub. þ BRAS performs NAT to build private network and limit need for public IP addresses. BRAS runs DHCP for dynamic addresses within private network.

Sponsored by 4

DSLAM ADSL Technology List AL = G.hs indicates G.dmt Annex A and G.lite capability A = G.hs indicates G.dmt Annex A only capability B = G.hs indicates G.dmt Annex B only capability # 1 2 3 4 5 6 7 8 9 10

DSLAM Paradyne Ericsson NettoNet Alcatel CopperM Siemens ECI Nortel Marconi Iskratel 10

#LT 1 2 1 2 1 2 1 2 1 1 14

Annex A A A AL AL A AL A AL 8 5

Annex B

Lite

B B B B

AL AL

AL B AL B 6

4

CPE ADSL Technology List (1) AL = G.hs indicates G.dmt Annex A and G.lite capability A = G.hs indicates G.dmt Annex A only capability B = G.hs indicates G.dmt Annex B only capability # 1 2 3 4 5 6 7 8 9 10 11 12

Company Aztech Intel

#CPE 1 1

Annex A A AL

Annex B

Alcatel Alcatel ME Ambit Globespan Broadxent

2 1 1 2 1

AL

B B

Arescom TI Nokia

1 1 1

AL A AL

AL A A

6

Lite AL AL AL

B

AL AL

CPE ADSL Technology List (2) AL = G.hs indicates G.dmt Annex A and G.lite capability A = G.hs indicates G.dmt Annex A only capability B = G.hs indicates G.dmt Annex B only capability # 13 14 15 16 17 18 19 20 21 22

Company Ericsson AVM Proscend RAD Excelsus Agere Eicon ST MicroElec LEA Samsung 20

#CPE 2 2 1 1 1 2 1 1 1 1 25

Annex A A A AL A A AL AL AL A AL 19 7

Annex B B B

Lite

AL

B

6

AL AL AL AL 10

Qualification Requirements G.dmt-Annex A and G.lite kTest on NULL loop and 4.5 km 0.4mm (15 kft 26awg) k Initialization Procedure using G.994.1 k Data rate at least 384 kbit/s down and 128 kbit/s up k Error rate better than 1E-7 k E2E check with PPP or 1483 (web surf and ftp)

G.dmt-Annex B k Test on NULL loop and 3 km 0.4mm (10 kft 26awg) k Initialization Procedure using G.994.1 k Data rate at least 384 kbit/s down and 128 kbit/s up k Error rate better than 1E-7 k E2E check with PPP or 1483 (web surf and ftp)

Any-to-any interoperability ! 8

Notes on Annex A/G.lite Results þ Qualified 17 out of 19 participating CPEs. þ Qualified all 8 participating DSLAMs. þ Qualified CPE can connect to any DSLAM during CeBIT and change connection during show. þ TI will show VoDSL application using 2 CPEs connected to 2 different DSLAMs, no change of DSLAM during show. þ Overall appreciation: Interoperability in good shape.

ý Issues observed: ý Some CPEs have too low transmit power and required some DSLAMs to configure severe downstream data rate limitation to qualify. 9

Notes on Annex B Results þ Qualified 5 out of 6 participating CPEs. þ Qualified all 6 participating DSLAMs. þ Qualified CPE can connect to any DSLAM during CeBIT and change connection during show. þ Overall appreciation: Interoperability better than expected, given this was first annex B interoperability test ever.

ý Issues observed: ý Large variation in achieved upstream data rates (up to 1:6 over different implementations). ý Interpretation of G.992.1 Annex B concerning G.hs indication of usage of upstream tones 1 to 32 and subsequent signal format. 10

Applications Test Results þ Pod#1: Online Gaming þ Intel, Alcatel, Alcatel ME, Ambit þ Pod#2: VoDSL/Enhanced Internet þ Globespan, TI, RAD, Nokia

ý Pod#3: Streaming Video ý Aztech, Broadxent, Arescom, AVM þ Pod#4: Video Conferencing with Imajet þ Ericsson, Agere, Eicon, LEA þ Pod#5: Peer-to-peer File Sharing with BareShare þ Proscend, Excelsus, ST ME, Samsung 11

Notes on Applications Test Results þ All applications (except Video Streaming) have been installed and tested on the allocated CPEs. þ CPEs are located in a POD dedicated to one application. Only this application shall be demonstrated at CeBIT. þ NetMeeting has been installed as Enhanced Internet application. ý Video Streaming Server not present at staging. Test and integration of Video Streaming application is left for CeBIT setup phase. 12

Booth Allocation for CPEs

All 20 registered CPE vendors will be on show ! 13

Booth Allocation for DSLAMs

The DSLAM interfaces are, from left to right: 1) Iskratel 3) Nortel 5) Copper Mt. 7) Alcatel 9) Ericsson

2) Marconi 4) Siemens 6) Net to Net 8) ECI 10) Paradyne

þ UNH will provide racks at CeBIT with transparent front and back (plastic cover). þ DSLAMs and backend equipment must be mounted in these racks to be visible to the audience. All 10 registered DSLAM vendors will be on show ! 14

What’s Next? SUPERCOMM 2001

15

Key Messages • Interoperability for SUPERCOMM 2001 – Technical Messaging-Requirements determined HERE! • Each participant will test their equipment against all other opposing equipment demonstrating the same technology, (technologies demonstrated are still tentative, but are slated as G.dmt (Annex A and Annex B), G.lite and G.shdsl.

• Marketing Messages – DSL is your passport to reach the BEST in new application; on-line education, entertainment and communications. – DSL Service is easy to use, and to install – There is any-to-any interoperability in DSL – DSL availability is widespread and there are active deployments around the world. – Wow, DSL is fast, and gives you the competitive edge. 16

Conditions • Want to guarantee good share of showcase goes to G.shdsl. • Percentage needs to be decided for each technology? • DSLAMs with multiple linecard types in one rack are preferred to save space. • Fee for multiple technologies? 17

Participation guidelines for SuperComm 2001 • ADSL: Same requirements as previous shows (G.dmt Annex A) • SHDSL: can show both ADSL and SHDSL in the same DSLAM (20% additional costs) • CPE: reference designs can be shown; they get a kiosk, ref design in plastic case for viewing, optional connection in kiosk to both CO and other ref designs in booth • One Pod will be of SHDSL Reference Designs only • SHDSL Focus: ATM and/or TDM • Up to 33% for SHDSL for18CPE kiosks

a G.shdsl Requirements kTest on NULL loop and 15 kft 26awg k Initialization Procedure using G.994.1 k Data rate at least 384 kbit/s k Error rate better than 1E-7 k E2E check with PPP or 1483 (web surf and ftp) k Interoperability at PHY layer; 3 in total; 1 can be self a G.dmt-Annex A and G.lite kTest on NULL loop 15 kft 26awg k Initialization Procedure using G.994.1 k Data rate at least 384 kbit/s down and 128 kbit/s up k Error rate better than 1E-7 k E2E check with PPP or 1483 (web surf and ftp) kAny-to-any interoperability 19

dslforum2001.143.1

Attachment 11: Presentation of Thursday Morning by Scott Valcourt on DSL Forum Plugfest Program

repTIWG010314-16-010626a.doc

Interoperability Plugfest Plans for 2001 Scott A. Valcourt Chair, ISWG DSL Forum

DSL Forum Plugfest Model n n n n n n

Major tool towards interoperability Used by ITU, ANSI, ETSI, IEEE Types and Procedures decided in advance Tests developed against known standard or draft Tend to occur early in development process Smaller matrix to support wider interaction

Plugfest Process n Approve

Plugfest Documents (PD) n Information about existing PD learned during testing fed back to Forum n Migrate into Working Texts (WT) and Technical Reports (TR) for long-term

Test Schedule for 2001 (Proposed) n

n n

n n n n n n

Mar 12-16 – DSL Forum Meeting, Vancouver – Finalize SC2001 technical focus (60 days) – Determine preparation time needed for successful demo May 16-25 – SuperComm Staging Event – Focus: ADSL, SHDSL Jun 18-22 – DSL Forum Meeting, Olso – Approve PD for first test event (45 days) – Approve PD for second test event (75 days) Jul 30-Aug 3 – First Test Event – Focus on ? Aug 27-31 – DSL Forum Meeting, New Orleans – Approve PD for third test event (75 days) Sep 24-28 – Second Test Event – Focus on ? Nov 5-9 – Third Test Event – Focus on ? Dec 3-7 – DSL Forum Meeting, Munich, Germany – Approve PD for fourth test event (30 days) Jan 7-11, 2002 – Fourth Test Event – Focus on ?

Plugfest Model n New/Emerging

Technology Areas only n Process for test plan development in place n Mechanism for Feedback into test plans

New Areas for Plugfests n n n n n n n n n n n n n

ADSL EOC G.dmt/G.lite ADSL Auto-Provisioning/Auto-Configuration ADSL Upper Layer Testing (PPP, L2TP, etc.) over G.dmt/G.lite ADSL Voice over DSL (VoDSL/CVoDSL) ADSL Annex B PHY ADSL Annex C PHY ADSL Annex H PHY SHDSL (G.shdsl) PHY w/G.hs SHDSL (G.shdsl) end-to-end interoperability ADSL G.lite fast retrain PHY VDSL PHY(s) HDSL4 PHY G.shdsl

Actions n Select

Area(s) for Next Plugfest(s) n Develop Timetable to Test Plans n Agree on Date(s) for Plugfest(s)

dslforum2001.143.1

Attachment 12: Presentation resulting from Thurs. morning by Scott Valcourt and Frank Van der Putten on SuperComm 2001 Interop Demonstration

repTIWG010314-16-010626a.doc

SuperComm 2001 Interoperability Demonstration March 15, 2001 1

Key Messages • Marketing Messages – DSL is your passport to reach the BEST in new application; on-line education, entertainment and communications. – DSL Service is easy to use, and to install – There is any-to-any interoperability in DSL – DSL availability is widespread and there are active deployments around the world. – Wow, DSL is fast, and gives you the competitive edge.

2

Participation Guidelines for SuperComm 2001 • Want to guarantee good share of showcase goes to G.shdsl, so 33% maximum of CPE kiosks will be reserved for G.shdsl. • Reference Designs can be shown in kiosk under clear plastic case. • 4 G.shdsl Chipset kiosks will be reserved with connectivity exclusively amongst themselves. • DSLAMs with multiple linecard types in one rack are preferred to save space. • CPE and DSLAMs that do both ADSL and G.shdsl will be assessed a 20% surcharge. 3

Network Architecture DSL Forum Interoperability Showcase

• ADSL architectures for the DSL Forum Interoperability Showcase – ATM-based deployment • DSLAMs High-speed interfaces – OC-3 – DS-3 – 100BT

• CPE DTE Interface – 10BT

4

ADSL Architecture DSL Forum Interoperability Showcase

• ADSL ATM-based deployment

10BaseT

ADSL ADSL CPE

ADSL ATM Transport

ADSL DSLAM w/ ADSL Linecard

5

OC-3, DS-3, 100BaseT

Aggregator / Router w/ DHCP and PPP Termination

Network Architecture DSL Forum Interoperability Showcase

• G.shdsl architectures for the DSL Forum Interoperability Showcase – The previous ADSL Network Architecture is the baseline – ATM-based deployment • Support the same network architecture as ADSL • Support the same applications as ADSL

– TDM-based deployment • Support the same network architecture as ADSL • Support the same applications as ADSL

6

G.shdsl Architecture DSL Forum Interoperability Showcase

• G.shdsl ATM-based deployment

10BaseT

shdsl G.shdsl CPE

G.shdsl ATM Transport

shdsl DSLAM w/ G.shdsl Linecard

7

OC-3, DS-3, 100BaseT

Aggregator / Router w/ DHCP and PPP Termination

G.shdsl Architecture DSL Forum Interoperability Showcase

• G.shdsl TDM-based deployment

Vendor Provided Functionality/Equipment 10BT

Router

shdsl

Router/ Bridge

G.shdsl CPE Unit

Vendor Provided Functionality/Equipment G.shdsl TDM Transport

100BT

shdsl

Router

G.shdsl CO Unit

Router/ Bridge Aggregator / Router w/ DHCP and PPP Termination

8

Qualification Requirements G.dmt-Annex A and G.lite •Test on NULL loop 15 kft 26awg • Initialization Procedure using G.994.1 • Data rate at least 384 kbit/s down and 128 kbit/s up • Error rate better than 1E-7 • E2E check with PPP or 1483 (web surf and ftp) • Any-to-Any Interoperability

G.shdsl •Test on NULL loop 15 kft 26awg • Initialization Procedure using G.994.1 • Data rate at least 384 kbit/s • Error rate better than 1E-7 • E2E check with PPP or 1483 (web surf and ftp) • Interoperability with 3 chipsets (1 can be self) 9

High Level Network Architecture DSL Forum Interoperability Showcase

t e n er t n I

POP ATM OC-3 VideoConf

Server

25 CPEs

A 10 DSLAMs D S S L H OC3 DS3 D 100BT Aggregator/ S Class C IP address for DSL network Router L

DSL Forum Booth SuperComm 2001

FTP Server STM1

w/ DHCP VoDSL and PPP Gateway termination

10

Contact Information • Trade Show Manager

• Marketing Director

– Ericka Katz, DSL Forum – [email protected] – +1.510.608.5909

– Laurie Gonzalez, DSL Forum – [email protected] – +1.770.761.9300

• Technical Lead – Scott Valcourt, UNH – [email protected] – +1.603.862.4489

• Marketing Co-Leads – – – – – –

• PR Contact – Allison Sokol, Voce Communications – [email protected] – +1.650.322.4625

11

Keith Atwell, ADTRAN [email protected] +1.256.963.8350 Everett Brooks, ADTRAN [email protected] +1.256.963.8590

This is one you don’t want to miss!

Looking forward to seeing you there… event details posted at: www.dslforum.org/private/supercomm_index.html

Thank you! Your SuperComm Planning Team 12

dslforum2001.143.1

Attachment 13: Presentation on Thurs. afternoon by Scott Harris on the Independent Testing Labs (ITL) Process

repTIWG010314-16-010626a.doc

Independent Testing Labs (ITL) Process Scott Harris, G8 Group DSL Forum, Vancouver March 2001

March 2001

dslforum2001.066

G8 - ITL Process

History, Part I - Plugfests ✔ ADSL vendors (equipment and chipset) start

testing for interoperability ✔ Plugfest model created at UNH ✔ Plugfests grew exponentially and became unproductive and unwieldy – Unless tied to a specific goal, like Supercomm staging

✔ General consensus that Plugfest model doesn’t

scale March 2001

dslforum2001.066

G8 - ITL Process

History, Part II - RSL ✔ Reference System Lab (RSL) Process – RFP written by G8 – University of New Hampshire chosen – Set of 12 spots chosen randomly • 3 DMT DSLAMS, 3 DMT CPE • 3 LITE DSLAMS, 3 LITE CPE

– Other systems to be added when first systems are tested

✔ Process from RFP is over one year old

March 2001

dslforum2001.066

G8 - ITL Process

History, Part III - Problems ✔ Multiple test houses couldn’t/wouldn’t participate

in RSL process ✔ DSL Forum does not want to certify testing houses, but would rather let the market decide ✔ RSL Testing is not going as well as hoped – significant vendor and testing delays

✔ Single site testing schedule delaying goals of

universal interoperability March 2001

dslforum2001.066

G8 - ITL Process

Solution - ITL Process ✔ Independent Test Labs process eventually

replaces Reference System Lab process ✔ Models industry testing processes like DOCSIS, Underwriters Laboratories, CE, etc. ✔ Market driven process ✔ Service providers drive the need for testing ✔ Vendors pay for testing and provide results as requested to service providers. March 2001

dslforum2001.066

G8 - ITL Process

Flowchart of ITL Process ITL Process

DSL Forum Defines Test Reqts And Report Templates

ITLs Build Test Plan(s) And Offers Services

Service Provider requires ITL testing

Vendor chooses an ITL

Vendor & ITL Schedule Testing

ITL Testing

Testing Results Document

Test Results given to Vendor (vendor decides what to do with them)

End

March 2001

dslforum2001.066

G8 - ITL Process

Market Driven Process ✔ Any Test Lab can choose to participate ✔ Test Labs must use a recommended DSL Forum

template test plan (being developed) and provide results in a specified format ✔ Test Labs doing so are “recognized” by the DSL Forum on a web site ✔ Test Labs are free to use their own IP and keep their proprietary testing procedures private ✔ Test Labs are free to set their own fee structures March 2001

dslforum2001.066

G8 - ITL Process

Market Driven Process (cont.) ✔ The market decides which Test Labs succeed and

which ones don’t ✔ Test Labs will spring up based on regional demand – Europe, U.S., APAC, etc.

✔ Vendors choose whichever Test Lab they wish,

based on location, cost, resources, etc.

March 2001

dslforum2001.066

G8 - ITL Process

Testing Results ✔ Service provider requests/requires Vendor to submit itself

to testing to win business ✔ Since testing is paid for by the Vendors, the testing results become the private property of the Vendors ✔ Vendors may choose to share testing results with Service Providers as part of a bid, contract, etc. ✔ Test results are covered by agreements between the Test Lab and the Vendor -- Results are not public info!

March 2001

dslforum2001.066

G8 - ITL Process

DSL Forum Involvement ✔ TIWG creates and maintains template test plan ✔ TIWG creates and maintains results template ✔ G8 receives nominations from Test Labs to be

“recognized” ✔ G8/Secretariat maintains a list of Independent Test Labs on the DSL Forum Public web site ✔ A simple matrix can be published on the DSL Forum web site showing only DSLAM/CPE “check marks” March 2001

dslforum2001.066

G8 - ITL Process

Template Test Plan ✔ Test plan contributions from BT and

SBC/Verizon/BellSouth ✔ Developed and reviewed in TIWG ✔ Proposed as the DSL Forum Test Plan for ITL

March 2001

dslforum2001.066

G8 - ITL Process

Test Lab Requirements ✔ Will use template test plan as minimum test plan – can do more testing, value-add testing if desired ✔ Will present results in template format ✔ Will be a voting member of DSL Forum ✔ Shall work with TIWG for continuous

improvement of test plans ✔ Test Lab is responsible for equipment purchases, maintenance, business plans, advertising, etc. – including getting DSLAMs and CPEs for testing March 2001

dslforum2001.066

G8 - ITL Process

Benefits ✔ to Service Provider: offsets/supplements need for

testing ✔ to Test Labs: offers a market in which to compete for testing business; recognition from DSL Forum ✔ to Vendors: allows testing to be done in a controlled, professional, private environment ✔ to Forum: Requires little oversight or governing. ✔ to Industry: Speeds up Interoperability! March 2001

dslforum2001.066

G8 - ITL Process

Roadmap to Plug-n-Play Ref. System Lab defined and in progress

ITL Process Service Providers and Test Labs

Retail DSL P-n-P Equipment vendors, Service Providers, Test Labs, CPE Autocfg SHDSL VDSL

present day

March 2001

dslforum2001.066

G8 - ITL Process

Retail ADSL P-n-P ✔ True “Plug-and-Play” enables mass market ✔ CPE’s qualified against most/all DSLAMs ✔ Reduces/removes Service Provider from

“touching” CPE ✔ DSL Forum “check” matrix identifies products which successfully pass tests ✔ ITL could issue testing sticker without DSL Forum March 2001

dslforum2001.066

G8 - ITL Process

Retail xDSL P-n-P ✔ Extend model/experiences gained with ADSL

with upcoming technologies: – – – – – –

Autoconfig G.SHDSL ADSL annex B ADSL annex C VDSL etc.

March 2001

dslforum2001.066

G8 - ITL Process

Thank you very much! For more information, contact: [email protected] [email protected] [email protected]

or anyone else on the G8 March 2001

dslforum2001.066

G8 - ITL Process

dslforum2001.143.1

Attachment 14: Presentation on Fri. morning by Paul Drew on the OpenVoB D1 Model Implementation Guide

repTIWG010314-16-010626a.doc

United to Deploy Interoperable Broadband Telephony

OpenVoB • Technical special interest group • Focused on accelerating VoB deployments

• Addressing service provider concerns: • Lack of VoB solutions based on open specifications • Multi-vendor, end-to-end interoperability • Lack of CPE management and provisioning strategy

• Focused on achieving multi-vendor interoperability • Utilizing existing VoB standards • Developing test plans/implementation guidelines in support of upcoming VoB interoperability events referred to as callfestsTM

• For more info…..

www.openvob.org

OpenVoB Promoters

Leveraging Existing Standards … While Filling the Gaps D1 and D5 Models

C1 Model

OpenVoB

OpenVoB

Interoperability (System, Multi-vendor)

(Voice)

IETF ITU ISC

ATM Forum

OpenVoB

Services

OpenVoB CableLabs PacketCable 1.0

Transport DSL Forum Physical (DSL, Cable)

ANSI T1

DSL

OpenDSL

(ATM. IP)

CableLabs DOCSIS 1.1

ITU G Series

CPE Management and Provisioning

Cable

Bridging the Gap Between Standards and Deployments Broadband Broadband Service Service Provider Provider

Customers Customers

• What it is … An industry group seeking to accelerate VoB interoperability based on existing standards yet focused solely on implementation • What it is NOT … Another competing standard

Backup Slides

The Market Problem Industry confusion as networks, protocols, systems, and solutions are all pulling in different directions PacketCable VoIP Class 5 Softswitch /SIP

MGCP/Call Agents

Broadband Broadband Service Service Provider Provider

VTOA - BLES

Home Distribution Service Provisioning VTOA - VoMSDN

SS7

Market adoption will lag until industry steps up to prioritize/align these forces

Why OpenVoB? • FIRST STEPS…..Create

an implementation roadmap toward integrated services linking packet and circuit networks

• OPEN SPECIFICATIONS…..Avoid

proprietary

equipment deployments • UNITED INDUSTRY….Avoid

market fragmentation

• RAPID MARKET EXPANSION…Set

stage for general mass market acceptance for derived voice service as a POTS alternative Eliminate obstacles and avoid pitfalls associated in adoption of new technologies in the past

OpenVoB Charter Accelerate Voice over Broadband Deployments

• Promote viability/market awareness of derived voice services • Jump start wide spread VoB interoperability • Establish multi-vendor testing facility to foster collaboration • Support existing VoB standards efforts

OpenVoB is NOT…. • NOT a closed group focused on promoting a specific vendor’s implementation • OpenVoB welcomes all VoB vendors and service providers interested in open specifications and accelerating VoB adoption in the marketplace

• NOT creating a new standard • OpenVoB is created to assist in the development of existing standards and work in ATM Forum, DSL Forum, PacketCable, SoftSwitch, IETF etc. • OpenVoB is a sunset organization focused on specific deliverables and near term results

OpenVoB Work Plan • Target architectural models for 2000/2001 interoperability demos • DSL Technical Working Group • D1 Model: ATM Forum VoATM (LES -CAS) with GR-303 PSTN interface • D5 Model: Softswitch Model (VoATM with IETF/ISC MGCP signaling)

• Cable Technical Working Group • C1 Model: PacketCable 1.0 with V5.2 PSTN interface

• Identify areas requiring clarification or extension of capabilities in order to accelerate deployments • Deliverables • D1 model Implementation Guide/Test Plan – 1Q01 • D5 Model Implementation Guide/Test Plan – 3Q01 • ATM and DSL Forum contributions with “lessons learned”

Milestones • May ‘00: Published OpenVoB white paper • Aug ‘00: • Denver Summit meeting – kick-off D1 Model technical work • Public launch of organization

• 4Q00: • Select/Announce Callfest location • Phoenix Summit meeting • BLES Callfest Nov 27-Dec1

• 1Q01: • BLES Callfest • Publication of D1 implementation guide

• 2Q01: • Softswitch callfest and Cable V5 callfest

Mode of Operation Different from Standards Body Work • Implementation focus; near term revenue • Non-competitive • Target only unaddressed issues • Public demonstration of interoperability • Focused promotion of Voice over Broadband

Joining OpenVoB • OpenVoB Benefits: • Participate in development of OpenVoB framework documents • Participate in CallFest VoB interoperability testing events as well joint marketing events

• Requires signing OpenVoB promoter’s agreement and annual $5K fee • Covers operational costs: web site, collateral, legal, promotional, administrative, etc. • Excludes costs associated with CallFests and marketing events (tradeshow events)

• Open to all VoB vendors and service providers • Seeking members focused on accelerating VoB deployments based on open specifications • Seeking members interested in interoperability testing based on the D1, D5, and C1 deployment models