Phone Conference P1450.1 & CTL Working Doc Subgroup Thurs May 10, 10:00 am PST --------------------------------------------- Attendees: ---------- Tony Taylor Peter Wohl Doug Sprague Greg Maston Rohit Kapur Agenda ------ In light of the recent decision of TTSC to merge CTL into the P1450.x work, we used this meeting to discuss the process issues involved. Information about the TTSC motion is attached. 1. General discussion of the motion for everyone's clarification. 2. Initial "gut" reaction of the impact of this decision on the standards work currently in place - both STIL (1450.1) and CTL. a) schedule impact b) technical impact c) user impact if schedule or syntax changes 3. Discuss (and decide) on how to working groups should proceed, given this new direction. a) maintain separate working groups for CTL, STIL, TRC? b) combined working groups c) separate working groups with strong interaction 4. Discuss any changes or additional PARs required. Discussion: ---------- 1. There was general agreement in the combining of these two efforts. Two issues immediately were raised: a) We don't want to slow down the efforts currently underway by either the P1450.1 team or the CTL team. b) The CTL part of the standard will need to be balloted at pretty much the same time as P1500. c) The 1450.1 must be balloted before (or at same time as) CTL. 2. Rohit - Expressed concern that moving CTL out of the Environment block will cause many aspects of the CTL syntax to be revisited. This led to the question (still to be resolved) as to whether CTL can remain in the Environment block as part of STIL. 3. Rohit - Expressed concern that the 1450.1 working group has not supported some syntactical aspects of CTL - i.e., the named file referenced identifiers, the user defined parameters. These things need to be explicitly defined for full automation of the core interchange objective. 4. We jumped right into the heart of the issue with a discussion and vote on whether CTL should be included in the 1450.1 standard or in a new 1450.6 standard (i.e., the next un-assigned dot number). The discussion recognized that as written, the PAR for 1450.1 could be interpreted to include CTL. It was also recognized that the IEEE will package several standard documents (in this case dots of the same standard) into a single package. After discussion, the vote was taken with the following result. Note: Since we didn't have all the CTL working group members present, we will need their votes also before making the final decision. 5 votes = Make CTL a new standard, numbered 1450.6 0 votes = Include CTL in 1450.1 5. A new PAR is required to request to be submitted to IEEE. Rohit is to prepare a draft of the PAR for review. Action Items: ------------ 1. Rohit & Tony - Can CTL remain in the Environment block? Review the CTL syntax and propose how the syntax should be changed as a result of moving into STIL. 2. Tony - Contact IEEE editor about the packaging of several standards into a single package. 3. Rohit - Prepare PAR for P1450.6. 4. Greg - Publish these minutes on the STIL web site, and in addition, prepare a general announcement about this decision. 5. Rohit - Discuss this CTL-STIL merge with the rest of the CTL working group and get their input and vote on the 1450.1 vs. 1450.6 motion. ============================================================== TTSC Meeting on Tuesday 5/1/2001: The meeting today with regard to the separation of CTL from P1500 was attended by the following: Adam Cron, Brion Keller, Maurice Lousberg, Gordon Robinson, Tom Williams, Yervant Zorian, Paolo, Tony Taylor, Erik-Jan Marinessen, Rohit Kapur. After about 1hr 45min discussion, the following motion was made: "Motion to pull the CTL syntax and semantic definitions out of the P1500 standard, while keeping the information model and guaranteeing co-operation of the two working groups". The vote was 4:0 in favor of the motion. The voting was done by the members of the TTSC as sponsors of the P1500 standard: Yervant Zorian, Adam Cron, Gordon Robinson, Tom Williams. There was discussion as to the best home for the CTL syntax and semantic definitions. The options considered were: a) separate dot to P1500 - this was specifically disallowed by the wording of the motion above. The reason for disallowing of this option was to maintain a single document for P1500 that contains ALL information necessary for defining plug-and-play cores including all details of the wrapper and information model. The P1500 standard will reference both STIL (1450) and the standard containing CTL. b) 1450.1 - to be combined with the current design extensions to STIL. This was deemed to be an appropriate place since the PAR for this effort already calls for support of the P1500 embedded core work. The exact wording of the 1450.1 PAR should be reviewed if this avenue is decided upon. c) 1450.x - a new dot standard to 1450. This would have minimum impact to the existing structure of the working groups and the documents. The down side is that the CTL user would need to reference 3 separate documents (1450, 1450.1, 1450.x). The CTL and P1450.1 working groups are tasked with jointly reviewing the above options and proposing to TTSC their desired solution and justification. ==============================================================