IEEE P1735 Working Group Meeting of January 19, 2009

Meeting Info

Conference Bridge and Webex

Participants

  • Attending
    • Steven Dovich, Cadence
    • Nitin Khurana, Cadence
    • Ruchi Tyagi, Cadence
    • Karlton Lau, Xilinx
    • Dave Clemans, Synopsys
    • Dave Graubart, Synopsys
    • Parminder Gill, Synopsys
    • Premduth Vidyanandan, Xilinx
    • Michael Smith, Synopsys
    • John Shields, Mentor

  • Not Attending
    • Nick Sgoupis, CAST
    • Bin Dai, Xilinx
    • Hamid Agah, Xilinx
    • William A Hanna, Boeing
    • Meera Srinivasan, Synopsys
    • Syed Huq, Cisco
    • Jim Robinson, Synopsys
    • NSS Subramanian, Cadence
    • David Tran, Synopsys
    • Gary Delp, LSI

Agenda

  1. Determine Quorum
  2. Patent slides
  3. Approve agenda
  4. Approval of Meeting minutes from 1/12/2009
  5. Action Items Status
  6. Liaison Reports
  7. Recommended Algorithms (AES-256)
  8. License Management
  9. Key Management Issues
  10. Other Business
  11. Adjourn

Minutes

Attendance/Quorum

We have 3/4 eligible entities, and have a working quorum.

Patent Policy

The Patent slides were offered for review.

No new claims were disclosed at the call for essential patent claims.

Agenda Approval

Motion by Karlton, seconded by Dave G. Motion is approved.

Previous Minutes

Dave G moved and Karlton seconded the approval of the January 12, 2009 minutes. The motion was approved.

Action Item Review

Steven reviewed the open action items.

Liaison Reports

No report presented.

Recommended Algorithms

Karlton requested that aes256-cbc be added to the set of required algorithms. John asked about the requirements, and Karlton replied that military contracts specified use of that algorithm. John stated that he viewed reverse-engineering of the binary as a bigger risk than the algorithm choice and that DES might even be sufficient to provide balanced protection. The group recognized that the issue here is not the technical security of the cryptosystem, but the ability to support market requirements for contract terms.

The biggest unanswered question is the performance costs of aes128-cbc vs aes256-cbc. John suggested that we check on whether anyone has concerns about supporting this algorithm, and if there are no such concerns then we should add it to the list. Karlton confirmed that their requirements are for CBC mode.

%ACTION{ closed="2010-02-08" closer="Main.StevenDovich" created="2009-01-19" creator="Main.StevenDovich" due="" state="closed" uid="000053" who="Main.KarltonLau" }% Check on performance benchmarks between AES modes %ENDACTION%

License Management

Since the last meeting, Michael revised his working draft to include two use cases for authorization-only, and current-usage. These are orthogonal to the internal vs external implementation strategies.

Steven asked about the ability of the Internal scheme to handle a common IP input from more than one tool. There isn't current support in the pragmas to solve this problem, and we need some requirements and/or strategy for solving this problem. The Rights Management discussion will need to address this issue. John reported that he has encountered resistance to vendor supplied internal licensing support, and that notational support from P1735 is only the beginning of making the case for internal licensing capabilities.

John expressed a presumption that Encryption, Licensing, and Rights were largely orthogonal. In the discussion, the topic of Rights Management raised issues in need of resolution. Steven will work to address the remaining roadblocks for the donated material.

Key Management Issues

Other Business

Adjournment

Motion by Karlton, second by Michael. Approved by acclamation at 11:34 pm CDT

Approval

These minutes were approved at the February 2, 2009 meeting.

-- StevenDovich - 02 Feb 2009

Edit | Attach | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2010-02-08 - 16:03:58 - TWikiGuest
 
Copyright © 2008-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback