Proposal for OCP Specification - OCP-IP
Proposal for OCP Specification - OCP-IP
Proposal for OCP Specification - OCP-IP
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>OCP</strong>-<strong>IP</strong><br />
General Steering Committee Meeting<br />
Santa Clara, CA<br />
October 4, 2002<br />
Attendees:<br />
Ian Mackintosh – <strong>OCP</strong>-<strong>IP</strong> President<br />
Anssi Haverinen - Nokia<br />
Drew Wingard – Sonics<br />
Mau Truong – UMC<br />
Joe Basquez – VitalCom<br />
Rich Baek – VTM<br />
Reen Presnell – VTM<br />
Barbara Oshiro – VTM<br />
Jason Hewett – VTM<br />
Teleconference:<br />
Pete Cumming – TI<br />
Agenda:<br />
*Introductions/Agenda Review (Ian)<br />
*Next GSC Meeting (Ian)<br />
*SLD Study Group Update (Anssi)<br />
*Technical Vision WG Update (Drew)<br />
*Functional Verification WG Update (Pete)<br />
*<strong>Specification</strong> Enhancements – Feedback, Comments, Timelines, and Support<br />
Implications? (Drew)<br />
*WG Long-Term Activity/Priorities (Drew)<br />
*VSIA <strong>Proposal</strong>/Update (Ian)<br />
*Action Item Review (VTM/Ian)<br />
*Foundation Documents/Legal/Financial (Ian)<br />
*PR Update (Scott)<br />
*Collateral Review – CD/Lite Training/Press Clippings (VTM)<br />
*Short-Term Recruiting (Joe)<br />
*Long-Term Recruiting (VTM)<br />
*Administrative Update (VTM)<br />
Meeting began at 9:13 a.m. PDT.<br />
Action Item Review:<br />
AI: Ian will talk to Qualis, and others, about the value of sponsor membership so<br />
they can join the WGs.<br />
AI: Scott/Ian to shift focus of newsletters and press releases to adoption stories.<br />
<strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED
AI: VTM to create a homepage link to adoption stories.<br />
AI: Pete to review membership list and tell Ian who to invite as Sponsors.<br />
(Comments: Advise that upgrade comes as a result of contributions --- trading work<br />
<strong>for</strong> sponsor membership).<br />
AI: VTM to post a notification in members only area that members providing<br />
support to WGs may receive free upgrade to Sponsor level membership.<br />
AI: Scott to look into tech-online Web postings.<br />
AI: Have the membership roster page link to the <strong>OCP</strong> products page <strong>for</strong> that<br />
member.<br />
AI: VTM to survey <strong>OCP</strong> members to see if there are any <strong>OCP</strong> products that they<br />
would like to feature.<br />
AI: Call key member contacts and make them aware of the 2003 specification<br />
revision and ask if they and their customers are ready <strong>for</strong> it.<br />
AI: January GSC meeting should open the issue of how to propel <strong>OCP</strong>-<strong>IP</strong> to the<br />
next level.<br />
AI: Ian to develop a program on the deliverables that support the 2003 specification.<br />
AI: Drew to talk to FSA <strong>IP</strong> Forum and tell them who we are.<br />
AI: VTM to get collateral and presence at the VSIA booth <strong>for</strong> DesignCon.<br />
AI: Drew committed to provide die photographs to use in future newsletter<br />
graphics.<br />
AI: Add electronic packets page to Web site, so prospects can download them.<br />
Introductions:<br />
Ian begins the meeting by introducing Mau Truong as the new UMC representative. At<br />
this time, the agenda is reviewed by the GSC members.<br />
Next GSC Meeting:<br />
Anssi suggested that we hold the next GSC meeting sometime during the beginning of<br />
November in New York. Pete cannot be in the US during the beginning of November but<br />
suggested the 13 th or 14 th . GSC discussed the possibility of moving GSC meetings to<br />
each quarter, rather than every six weeks. GSC decided to make their next meeting<br />
November 14, 2002 in Boston, Massachusetts.<br />
SLD Study Group Update:<br />
Anssi said that the first SLD Study Group meeting since the last GSC meeting was held<br />
yesterday, 10/3/02. The group has made some progress – the press release is in approval<br />
<strong>for</strong> 10/15 release. They will have white paper ready 10/14, making lite because API is<br />
being left out. The API is due at the beginning of January. The current version of API is<br />
in use in Nokia so far.<br />
Anssi needs some of Max’s time. They need one picture that he promised to draw <strong>for</strong> the<br />
introduction section and also a review of the whole paper from the TI prospective. Anssi<br />
emailed Max yesterday.<br />
Franck needs to do a review; however Pete cannot commit Franck at this time. He is very<br />
busy.<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 2 of 7
The white paper will be posted on the Synopsys and <strong>OCP</strong>-<strong>IP</strong> Web sites. <strong>OCP</strong>-<strong>IP</strong> will<br />
carry “Golden Copy.”<br />
The models and the API code itself would be stored and owned by <strong>OCP</strong>-<strong>IP</strong>.<br />
Sonics is a bit concerned about the contribution to OSCI. It would look more peer-topeer<br />
if we note that Synopsys is contributing to <strong>OCP</strong>-<strong>IP</strong> as well.<br />
GSC requests that Scott work into the press release the contribution from OSCI to <strong>OCP</strong>-<br />
<strong>IP</strong>. Scott replies that the press release is set in stone.<br />
When should we expect to have a WG? Anssi thinks that the WG should begin after they<br />
release the first API. This issue was deferred until the January GSC meeting.<br />
Technical Vision WG Update:<br />
The Technical Vision WG has not met since last GSC meeting. They have focused all of<br />
their attention on the specification revision. Drew will work on the summary document.<br />
Further discussion of this issue was deferred until the November meeting.<br />
Functional Verification WG Update:<br />
The Functional Verification WG has met about five times. WG is making progress on<br />
property checking.<br />
Qualis presented their DVC in one of these meetings. We need to communicate with<br />
Valiosys and Qualis on how to move <strong>for</strong>ward. Should we invite them to the GSC every<br />
six weeks and/or have them join the WG? GSC expressed interest in involving other<br />
members in WGs.<br />
Ian said that he would determine whether each member company could have more than<br />
one representative in the WGs. The Technical Vision WG would decide what they want.<br />
Pete wondered if we are talking to the right people about joining the WGs.<br />
AI: Ian will talk to Qualis, and others, about the value of Sponsor membership so<br />
they can join the WGs.<br />
GSC has a discussion on adoption. We need to begin presenting adoption stories in the<br />
newsletter.<br />
AI: Scott/Ian to shift focus of newsletters and press releases to adoption stories.<br />
AI: VTM to create a homepage link to adoption stories.<br />
AI: Pete to review membership list and tell Ian who to invite as Sponsors.<br />
(Comments: Advise that upgrade comes as a result of contributions --- trading work<br />
<strong>for</strong> sponsor membership).<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 3 of 7
AI: VTM to post a notification in members only area that members providing<br />
support to WGs may receive free upgrade to Sponsor level membership.<br />
AI: Scott to look into tech-online Web postings.<br />
AI: Have the membership roster page link to the <strong>OCP</strong> products page <strong>for</strong> that<br />
member.<br />
AI: VTM to survey <strong>OCP</strong> members to see if there are any <strong>OCP</strong> products that they<br />
would like to feature.<br />
AI: Drew to clarify with David Courtright if sufficient review has been done within<br />
M<strong>IP</strong>S on enhancement proposals.<br />
We will now have the 2003 specification – do we want the Functional Verification WG<br />
to start working on verifying that they are using 2003 version?<br />
Who is going to make sure that the 2003 release is used in the new products? We should<br />
in<strong>for</strong>m our members that 2003 is coming out so they can start thinking about aligning<br />
their new products.<br />
Matrix – list tools and <strong>IP</strong> that support <strong>OCP</strong> that we know about, then rank how important<br />
it is <strong>for</strong> them to be on the 2003 release, and then go out and make it happen.<br />
AI: Call key member contacts and make them aware of the 2003 specification<br />
revision and ask if they and their customers are ready <strong>for</strong> it.<br />
We need to think about the vision <strong>for</strong> <strong>OCP</strong>-<strong>IP</strong>. How do we get to the next level? This is<br />
something that the GSC should discuss at January meeting.<br />
AI: January GSC meeting should open the issue of how to propel <strong>OCP</strong>-<strong>IP</strong> to the<br />
next level.<br />
<strong>Specification</strong> Enhancements:<br />
<strong>Specification</strong> WG is passed the feedback period. TI needs to get their feedback in; they<br />
will send to the reflector Monday.<br />
The biggest drawback is in the drafting stage; Sonics will get out the first draft. It<br />
appears that the specification will be issued at the end of January.<br />
We should have first draft <strong>for</strong> member review at the end of the year.<br />
AI: Ian to develop a program on the deliverables that support the 2003 specification.<br />
Long-term activity discussion postponed until next month.<br />
Joe arrived.<br />
VSIA proposal outline:<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 4 of 7
Ian has been working with Larry Cook. He proposed discussing what they have in<br />
common (aligning them); he has no issue with giving VSIA members individual<br />
membership. VSIA had a board meeting a few weeks ago, during dinner – they decided<br />
that they wanted to entertain the idea of merging the two organizations.<br />
Motorola, Alcatel, and Mentor appeared to be in favor of this possible merger. Infineon<br />
and ARM were silent during the discussion.<br />
Foils were presented by Ian outlining Larry Cook’s proposal.<br />
What about a situation where <strong>OCP</strong>-<strong>IP</strong> becomes a recognized “user group”? <strong>OCP</strong>-<strong>IP</strong>’s<br />
money, operation, and voting would all be separate. They will give VCI to <strong>OCP</strong>-<strong>IP</strong> and<br />
have a membership fee scheme <strong>for</strong> exclusive and combined membership alternates.<br />
VSIA would promote new structural vision.<br />
What about other <strong>OCP</strong>-<strong>IP</strong> actions like the XML issue Pete is working on with Beach?<br />
We are separate so we would determine our WG members.<br />
What does it mean to be a VSIA user group? Ian offered that the principle is beneficial,<br />
but the details concern us. Ian needs to know about what they don’t like, what they are<br />
concerned about.<br />
Drew expressed concerned about losing control of the specification.<br />
Some things we want to ensure <strong>OCP</strong> retains are as follows:<br />
• Operational autonomy and control of the specification.<br />
• No subrogation to their voting process.<br />
• Concerned of VSIA continuing to accept <strong>OCP</strong> specification versions.<br />
• Irregardless of VSIA’s future, <strong>OCP</strong>-<strong>IP</strong> is structurally, legal, and financially intact.<br />
• We would like the focus to be on adoption of <strong>OCP</strong> and not the group.<br />
• VSIA members have the right to use <strong>OCP</strong> and that is all. We do not want <strong>OCP</strong> to be<br />
a standard that VSIA approves.<br />
• The VSIA Board of Directors should vote, so as to give the approval power of On<br />
Chip Interface standard to <strong>OCP</strong>-<strong>IP</strong> until they feel we need to go separate ways. They<br />
would aggregate the space to us and endorse us in the process and have no<br />
mechanism <strong>for</strong> approval process in VSIA.<br />
• <strong>OCP</strong>-<strong>IP</strong> should provide advanced notification of specification enhancements. The<br />
extension of preliminary copies would only be to members of VSIA and individual<br />
members of <strong>OCP</strong>-<strong>IP</strong>.<br />
• VSIA needs to investigate the legal complications of “donating” VCI to <strong>OCP</strong>-<strong>IP</strong>.<br />
• Should VSIA come back with a big demand on supporting the VCI specification,<br />
which should serve as a red flag.<br />
• We should incorporate the VSIA logo into membership foils.<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 5 of 7
• We should have VSIA appoint a <strong>for</strong>mal liaison to stay abreast of our ef<strong>for</strong>ts – it<br />
would be the liaison’s job to in<strong>for</strong>m impacted WGs, etc. This liaison has to be<br />
individual member of <strong>OCP</strong>-<strong>IP</strong>.<br />
Pete dropped off the line.<br />
AI Review:<br />
VTM edits made on AI list.<br />
AI: Drew to clarify with David Courtright if sufficient review has been done within<br />
M<strong>IP</strong>S on enhancement proposals.<br />
Foundation Documents/Legal/Financial:<br />
GSC discussed foundation document sign-off. Ian in<strong>for</strong>med other GSC members of the<br />
membership intent of Toshiba, ST, and Flextronics. No one had any issues with these<br />
companies.<br />
Scott joined.<br />
MWG/PR update:<br />
MWG members have been very active and a lot of progress has been made.<br />
New press releases that are <strong>for</strong>thcoming are as follows: Broadcom, Amphion, and Tower<br />
Semiconductor. Synopsys/System C is under approval. They are still targeting October<br />
15, 2002 because it aligns with the Synopsys event. Synopsys will put the release on the<br />
wire and distribute to press through email.<br />
Call <strong>for</strong> articles and papers is presented by Scott Seiden.<br />
We are still looking <strong>for</strong> an author <strong>for</strong> VCI-to-<strong>OCP</strong> article. DesignCon and Electronic<br />
Design paper submissions are still TBD. Ian offered that VSIA has a strong presence at<br />
DesignCon and any VSIA collaboration might allow <strong>OCP</strong> to be presented through VSIA<br />
ef<strong>for</strong>ts.<br />
FSA Update<br />
We gave away about 500 Lego-style stress blocks. Also, we talked with about 15<br />
contacts that we will follow up with. FSA had 2,500 pre-registrations.<br />
It seems that putting an article in their publication is a definite possibility. Scott will<br />
work with them on these and other issues. Ian is entertaining the idea of hosting an<br />
annual event around the FSA conference time.<br />
AI: Drew to talk to FSA <strong>IP</strong> Forum and tell them who we are.<br />
AI: VTM to get collateral and presence at the VSIA booth <strong>for</strong> DesignCon.<br />
VCX<br />
Andy Travis has some great ideas and tools. We need to stay abreast of this situation, so<br />
we can track progress.<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 6 of 7
Scott dropped off the line.<br />
Lunch<br />
Reen joins.<br />
Collateral Review:<br />
Web site CD is reviewed by GSC.<br />
Lite Training presentation is reviewed by GSC.<br />
Press Clippings Booklet presented to GSC.<br />
Newsletter is presented to GSC. Drew has more die photo pictures that he will <strong>for</strong>ward<br />
to us.<br />
AI: Drew committed to provide die photographs to use in future newsletter<br />
graphics.<br />
Short-Term Recruiting:<br />
GSC reviews Joe’s foils.<br />
Ian gave a quick update of some of the “hot list” companies listed in red on the shortterm<br />
recruiting foils.<br />
Long-Term Recruiting:<br />
GSC reviews foils presented by VTM.<br />
AI: Add electronic packets page to Web site, so prospects can download them.<br />
Administrative Update:<br />
VTM gave an administrative update.<br />
Meeting ended at 2:30 p.m. PDT.<br />
10/10/2002 <strong>OCP</strong>-<strong>IP</strong> CONFIDENTIAL – NOT TO BE DUPLICATED 7 of 7