Subject: STIL phone call: Thurs 5/10 Date: Tue, 08 May 2001 14:38:38 -0700 From: "Tony Taylor" To: rkapur@synopsys.com, kellerbl@us.ibm.com, lousberg@natlab.research.philips.com, paul_reuter@mentorg.com, dkay@cisco.com, Erik.Jan.Marinissen@philips.com, tww@synopsys.com, zorian@lvision.com, gmaston@synopsys.com, dsprague@us.ibm.com, peterwohl@adelphia.net, gwilder@asic.sc.ti.com To: STIL.1 & CTL working group members I am addressing this email to both working groups and the P1500 chair. I am suggesting that we use the time of the next STIL phone call to start hammering out the details of the decision that was made at TTSC last week. The next scheduled STIL phone call is as follows: Date: Thurs 5/10 Time: 10:00 to 11:00 Dial-in#: 888-232-0370 Participant code: 605208 Agenda: As most of you probably know by now, the TTSC voted to move the CTL syntax from the P1500 standard to the P1450 standard. Below is the text of the motion as I captured it last week. Before we can start making the necessary technical changes that are involved, we need to address the process issues. Here my proposed agenda for a joint meeting to discuss these process issues: 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. 5. How/when to notify the STIL reflector of what is happening? 6. How/when to notify/request specific changes to TTSC. Attachment #1: Also attached is a document that Rohit has prepared to identify some of the key technical issues that he believes will need to be addressed. Attachment #2: For your review, I have attached the PAR for 1450.1. Hope to talk with all of you on Thurs. -tony ============================================================== 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 minumum 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. ============================================================== --------------------------------------------------------------------- Name: Implications of Moving CTL to 1450.doc Implications of Moving CTL to 1450.doc Type: Winword File (application/msword) Encoding: base64 Name: 1450-1.pdf 1450-1.pdf Type: Acrobat (application/pdf) Encoding: base64