This is the home page for the IEEE DASC: P1735:

A Study Group for developing a proposal for a working group to develop a Recommended practice for Design Intellectual Property (IP) Encryption and Rights Management


If you are on the mailing list, then you can send mail to the mailing list ip-encrypt  - at-sign- EDA spot org
If you are not and would like to be, send mail to Gary spot Delp located at ell ess eye spot commercial

Scope of Proposed Standard:

This standard specifies embeddable and encapsulating markup syntaxes for design IP encryption and rights management, together with recommendations for integration with design specification formats described in other standards. It also recommends use models for interoperable tool and hardware flows, which will include selecting encryption and encoding algorithms and encryption key management. The recommendation includes a description of the trust model assumed in the recommended use models. This standard does not specifically include any consideration of digitally encoded entertainment media. In the context of this document, the term “IP” will be used to mean Intellectual Property electronic design data.

Purpose of Proposed Standard:

The intent of this document is to enable design flows that provide interoperability between IP sources, tools, integrators, and users of the IP. There is currently no defined, independent standard for describing IP encryption markup for design information formats. Each design format which incorporates IP encryption describes their markup differently leading to confusing interpretation. Users of those standards also lack a recommended practice for inter-operable use of IP encryption.

This document provides guidelines and recommended practice for use of IP protection markup syntax and key management to enable interoperable tool flows with IP and tools from a wide array of suppliers. It includes algorithm selection for encryption and encoding. This document specifies a generic set of embeddable markup syntax suitable for IP protection and rights management of arbitrary text files. These files represent potential inputs and outputs of EDA tools that would otherwise expose IP. The generic syntax of these directives may be suitably modified for a particular file format if there are syntactic conflicts and variations may be described in recommended practices.

Need for the Project:

Working groups currently incorporating IP Encryption technologies use different descriptive language which makes shared implementation technology more difficult to produce, and the standards more difficult to interpret. Users of those standards also want further guidance on how to use the IP Encryption technologies for inter-operability.

Email archives

Valid CSS!