Status Reports STF 213 MTSIPT STF 236 and

  • Slides: 16
Download presentation
Status Reports (STF 213, MTS-IPT, STF 236) and Info (STF 219, STF 224) Anthony

Status Reports (STF 213, MTS-IPT, STF 236) and Info (STF 219, STF 224) Anthony Wiles MTS#36 Budapest, March 2003 MTS#36, Budapest, March 2003

STF 213 TTCN-3 Edition 2 q STF 213 Closed December 2002 Ø On time,

STF 213 TTCN-3 Edition 2 q STF 213 Closed December 2002 Ø On time, on budget q Parts 1 - 5 v 2. 2. 1 now published Ø PTCC web updated as requested by MTS#35 q Part 6 (TCI) to be approved at this meeting (Ina) q CR process being managed on an 'emergency' basis Ø All CRs, status (28. 02. 03), living list etc. on PTCC website q Need to discuss new STF - June 2003 (? ) and 2004 Ø When do we decide to hav next revision (2. 3. 1, 3. 1. 1)? q Training material (approval): Gyorgy (voluntary work) Ø New Rapporteur (Gyorgy/Sarolta? ) q TTCN-3 promotion activities? MTS#36, Budapest, March 2003 2

EP TIPHON (DTS/00065 -1, 2, 3 R 4) STF 213 and STF 224 q

EP TIPHON (DTS/00065 -1, 2, 3 R 4) STF 213 and STF 224 q STF 224: Generic approach to interoperability testing Ø Methodology • Terminology • Abstract test architectures (general model which resolves to special cases) • Test development process (using simple UML) • Testing process (also in UML) • Assumes conformance testing been done previously Ø Installed an experimental SIP-H. 323 test bed at ETSI • Voluntary equipment from various vendors • Gatekeepers, Gateways, IWF, SIP/H. 323 terminals etc. q STF 219: H. 323 -SIP Interoperability Test Scenarios Ø Several hundred test cases; Ø Now being aligned with the methodology (validated on test bed) MTS#36, Budapest, March 2003 3

MTS-IPT (General) q Kick-off meeting held in October 2002 q MTS To. R approved

MTS-IPT (General) q Kick-off meeting held in October 2002 q MTS To. R approved by Board to include these activities q Info/News/Press release Ø http: //www. etsi. org/ptcc. IPT. htm q 1 -page status input to Board#42 (MTS 36 TD 16) q Two main activities Ø SIGTRAN Ø IPv 6 MTS#36, Budapest, March 2003 4

MTS-IPT (SIGTRAN) q Lot of interest in SIGTRAN test specifications q 8 active voluntary

MTS-IPT (SIGTRAN) q Lot of interest in SIGTRAN test specifications q 8 active voluntary participants (8 companies) Ø Representatives from MTS, SPAN and IETF Ø Plus 4 observers and 1 uncommitted (3 companies) q Concentrating on M 3 UA and SCTP Ø Have draft TPs (for both) Ø Must align with SPAN's subset for SIGTRAN Ø Hope to go to TTCN-3 for ATS q Should open WI's as needed. Need 2 WIs now: Ø TSS&TP for M 3 UA (main driver GN Nettest now Navtelcom) Ø TSS&TP for SCTP (main driver Testing. Tech) q Workplan needs to be drawn up Ø STF not needed - all homework (coordinated by PTCC) MTS#36, Budapest, March 2003 5

MTS-IPT (IPv 6) STF 236 q STF 236 started work in January Ø Anthony

MTS-IPT (IPv 6) STF 236 q STF 236 started work in January Ø Anthony Wiles (PTCC), Scott Moseley Ø César Olivera, César Viho (voluntary), Frédéric Roudaut Ø Max Frey (including 5 days voluntary) Ø Steve Randall (3 days - in April for review) Ø 75 of 87 days used with 4 days not yet assigned q Major milestones Ø 14 March: 1 st Draft (OK) Ø 1 st Progress Report TD 12 Ø Mid April: 1 st proposal to EC • EC have changed date to end of April Ø 25 April: TB approval • request slight delay (start process end of April or even mid-May) MTS#36, Budapest, March 2003 6

STF 236 Identified Work Packages q Identified 7 Work packages Ø WP 1: Toolbox

STF 236 Identified Work Packages q Identified 7 Work packages Ø WP 1: Toolbox and Core Ø WP 2: Transitioning Ø WP 3: Mobility Ø WP 4: IPSec Ø WP 5: Qo. S Ø WP 6: Routing Ø WP 7: Multicast q Based on areas of common interest to Ø EC e. Europe / European industry / ETSI members Ø 3 GPP (mid/end 2004) Ø ETSI NGN (late 2004) Ø IPv 6 Forum certification scheme (2004) MTS#36, Budapest, March 2003 7

STF 236 Contents q Introduction/background Ø Interested players: IETF, EC, 3 GPP, ETSI TBs,

STF 236 Contents q Introduction/background Ø Interested players: IETF, EC, 3 GPP, ETSI TBs, IPv 6 Forum etc. q Basic concepts q Description of each workpackage Ø 1 st shot at resource estimate (need to revise) Ø In region of 270 man-months total (!) Ø Can PIck-'n-Mix q Lot of data! see annexes: Ø Tables, data, lists of RFCs, 3 GPP, priorities, existing test suites etc. for each package Ø Proposal for e. Europe 2005 - to do Ø To. R etc. for individual STFs not done (suggest to wait) MTS#36, Budapest, March 2003 8

STF 236 Basic Concepts q Toolbox is a key concept Ø TTCN-3 toolkit •

STF 236 Basic Concepts q Toolbox is a key concept Ø TTCN-3 toolkit • Max will talk about this Ø Core IPv 6 protocol q Other test suites based on toolbox Ø Core part Ø Specific part q Savings Ø Good SW engineering approach Ø 20% per test suite Ø Easier maintenance Ø Adaptability/Extensibility (3 GPP, SMEs, NGN etc. ) MTS#36, Budapest, March 2003 9

STF 236 Basic Tasks - Core (9. 2. 3) q Methodology q Toolbox Ø

STF 236 Basic Tasks - Core (9. 2. 3) q Methodology q Toolbox Ø Core protocol mechanisms Ø Patterns Ø Switches Ø User guide q Integration of TTCN-2/3 q Core protocol test suite (conformance/Io. P) Ø Needed? Already out there with TAHI, UNH etc. Ø But we need enough on which to build other WP test suites MTS#36, Budapest, March 2003 10

STF 236 Basic Tasks - Other Packages q Specification of Minimum Requirements Ø Minimum

STF 236 Basic Tasks - Other Packages q Specification of Minimum Requirements Ø Minimum RFCs Ø Minimum reqs - like PICS q Definition of Test Architecture and Methods q Engineering approach Ø Use of toolbox q TPs (Reuse? ) q Test Suites Ø Both Conformance and Interop test specifications Ø Reusibility (Io. P assumes test specs already exist) q Validation (voluntary? ) MTS#36, Budapest, March 2003 11

STF 236 Tool Support q TTCN-3 will be used q Both for Conformance and

STF 236 Tool Support q TTCN-3 will be used q Both for Conformance and Interop tests Ø In IPv 6 Forum the Io. P tests are automated q Existence of tool support will be essential Ø Additional package? Ø Voluntary? Ø Other project (e. g. , IST 6 TIPI)? MTS#36, Budapest, March 2003 12

STF 236 Timelines q Funding from EU not likely before Sept/October 2003 q No

STF 236 Timelines q Funding from EU not likely before Sept/October 2003 q No funding from ETSI likely in 2003 q If we wish to start earlier Ø Will need to be on a voluntary basis q Work anticipated to span 2004 - 2006 MTS#36, Budapest, March 2003 13

STF 236 Cost sharing issues q The commission only funds 50% q ETSI STF

STF 236 Cost sharing issues q The commission only funds 50% q ETSI STF budget (FWP/PTCC) is not large q Will require some voluntary activity q Other projects Ø TIPI (but also only 50%) Ø May be possibility for 100% but the situation is unclear MTS#36, Budapest, March 2003 14

STF 236 What next - short term q Week 14 - 16 Ø Anthony

STF 236 What next - short term q Week 14 - 16 Ø Anthony finish TR Ø Use of English etc. needs a thorough rationalisation (AW) Ø Draft proposal for EC if possible q Week 17 Ø Anthony, Steve, Scott Ø Need decision from MTS on which packages and where to place them (which projects)!! Ø Finalise proposal for EC • 3 -4 pages to Gavin for the Commission Ø To. Rs for phase 1 packages (? ) q Approval of TR can begin after that (from week 18) MTS#36, Budapest, March 2003 15

STF 236 What next - longer term q Anthony (PTCC) can continue with proposal

STF 236 What next - longer term q Anthony (PTCC) can continue with proposal Ø But not alone! Ø Need support from MTS q Full technical annex Ø Based on data from the TR Ø Partners!!! Ø Resource plan (voluntary vs. funded) Ø etc. q Completed by September? MTS#36, Budapest, March 2003 16