Meeting 21 Minutes

Teleconference, April 24th, 2006
A quorum of 13 out of 16 voting members present. Attendance indicated on the roster web page.

1. Call to order

Meeting was called to order at 09:00 PST/17:00 GMT.

2. Approval of minutes from meeting 20

Darren Galpin moves to approve the minutes as posted.
Matan seconds.
No objections/abstainers. The motion to approve the minutes was carried.

3. Announcing the standard approval

First Item is the happy announcement of the standards approval. As you probably know the IEEE standards board have finally approved our draft and now 1647 is an official standard and no longer a need for the letter p in front of it which standards for provisional as now we have an official standards in the works. The actual standard manual is going to be published by the IEEE probably in the June timeframe.

Now that the standard is approved, the working group will have access to the text (which is really our latest draft) for our work, but we will not be able to share that with others essentially for commercial reasons.

4. Proposal for seeking maintenance and enhancement PAR

Typically, the working group or a subset of the working group remains in place to watch over the standard as it is being used to address errors or typos or inconsistencies which may have found their way into the official standard. This calls for a PAR for the maintenance of the standard.

In addition to that you may recall the e-language that we have captured in the standard is really the form that it was in late 2002 so we are missing some more modern additions to the language - some things such as sequences for instance and all the other support that goes with eRM. Another area that's developed since is method ports and transaction level communication with external simulators which is growing in importance today but wasn't in place when we started. Including these features in a revision of the standard is another reason to seek a revision PAR.

So we should request an authorization for a follow on project and specify these two components in the scope, one will be the maintenance of the existing one and the second one will be for the addition of features that are currently being used but are not in the standard.

Yaron will produce a draft PAR and post it on the web site and we'll open up a two week comment period intended for the members of the working group to suggest changes to the PAR as posted. We'll hold e-mail discussion possibly followed by a discussion next meeting. Once consensus is reached, the PAR will be forwarded to IEEE NesCom.

Andy : will you be mailing out a message when that PAR is posted or shall we just check at the end of the week?

Yaron : I'll e-mail out a reminder to everybody and announce the comments period open

Matan : what kind of comments do you expect to give on this PAR , do we need to get into detail about what things need revision or addition etc.

Yaron : the PAR scope should not be very specific because eventually when you get to the approval of the standard people are going to hold you accountable for the details that you specified. So if we specify three items and we have only added two then they'll say that you've not completed the work. We should ask for a broad license and not be too specific. Most comments are expected to be various objections to the wording used.

5. Other Business

Proposing a festive get together in the bay area for WG members that are local in the San Jose area. Details will be provided through the reflector.

Second point : There's going to be some update to the web site - the web sites a bit outdated at this point. Firstly there's a historical list of participants which will have to be reduced to only people who actively participate. Finally we need to create a compatibility section for people who are using the standard and are wondering what the difference is between the standard and the existing tool out there. This is something that is initially going to be very sparse but as we collect more information we can populate.

The 3rd item is just a note that we'll have to run elections in the June time frame.

Final discussion on rollcall procedure - it was established when it was a big committee and some 30+ callers in every call and at that point it was impractical to collect names - hence the e-mail procedure.

It is decided to continue using the rollcall e-mail system, but introduce callers as meetings are called to order.

Serrie is commended for her willingness to take such detailed minutes.

6. Patent policy

The chair has issued a call for essential patents, in compliance with current IEEE/SA PatCom guidelines. The WG members are advised to review the call for essential patents and the patent related slide presentation posted on the web site .

7. Next meeting

Please remember to send in your e-mail to rollcall@ieee1647.org so that your attendance on this call is registered.

• Please DON'T send these e-mails to the reflector
• Use the e-mail address you registered with

The next meeting is tentatively set to Monday May 29th at 09:00 AM Pacific time, 17:00 UTC. The date may change according to circumstances.

8. Adjourn

IEEE/SA home
IEEE Standards Association

DASC Home
Design Automation Standards Committee

VLSG Home
Verification Language Study Group

The 1647 PAR
Project Authorization Form

(Updated Wed Oct 11 16:19:33 PDT 2006)