IEEE 1735:2014 pdf free download – IEEE Recommended Practice for Encryption and Management of Electronic Design Intellectual Property (Ip)
1.2 Purpose, value, and approach
The intent of this document is to enable design flows that provide interoperability among IP authors, toolproviders,integrators, and users of the IP.The resulting flow identified aids IP authors in providing lP thatcan be processed by tools without sharing protected information with IP users.Furthermore, this flow cansupport an integrated licensing scheme,enabling the lP authors to specify compile-time licenses.Anintegrated rights management scheme is also an element of the flow, which helps IP authors to control toolbehavior including, but not limited to, IP visibility, allowed tool versions, and output file encryption.
There is currently no defined，independent standard for describing IP encryption markup for designinformation formats. Each design format that incorporates lP encryption describes their markup differently,leading to confusing interpretation.Users of those standards also lack a recommended practice forinteroperable use of IP encryption.
For the IP author, the digital envelope containing the rights, key, and data blocks is the main focus. Thisenvelope contains the source, encrypted with a symmetric cipher using a one-time session key. The sessionkey is encrypted with a tool vendor public key for each supported vendor arranged in a series of key blocks.The license constraints and rights constraints are similarly encrypted with a tool vendor public key for eachsupported vendor arranged in a series of rights blocks.
The tool vendor supporting the standard can then parse and process the envelope and its contents. When thetool vendor finds the blocks with their public keys, each block is decrypted with their private key, thusextracting the data key, licensing requirements, and rights constraints. If required, the tool then checks forthe presence of a valid license and, if successful, decrypts the source using the data key and obeying therights constraints. Output files from the tool may be encrypted for use in downstream tools,provided suchaction is granted in the IP rights.
A standard defined with all these IP author and tool vendor features would make the overall flow transparentfor the IP user.Therefore,this document provides guidelines and recommended practice for use of IPprotection markup syntax and key management to enable interoperable tool flows with IP and tools from awide array of suppliers. It includes algorithm selection for encryption and encoding.
This document also specifies a subset of markup syntax for hardware description language(HDL) formatsthat could adapted to other file formats. These files represent potential inputs and outputs of tools that wouldotherwise expose IP.The generic syntax of these directives may be suitably modified for a particular fileformat if there are syntactic conflicts and variations that may be described in recommended practices.
1.3 Key characteristics of this standard
The marketplace for electronic design data depends on trust between the parties to the transactions.Exchanges require a confidence between the parties that they represent legitimate interests, that the productof exchange is accurately described, and that the terms of the transaction will be fairly observed.
As a form of intellectual property, electronic design data is a virtual object and is susceptible to the evolvingsocial conventions of respect for ownership rights. Despite uneven acceptance of their rights to control theuse of lP,those who produce such property frequently want to monetize their investment and receivecompensation for their investment in its creation.Risk premiums to compensate for loss are not commonlyitemized, but can be assumed as a factor in compensation demands.The inverse of a risk premium is thetrust discount, which is most commonly reflected in a greater willingness to market the IP as the strength ofthe trust model improves. This concept of the trust model is explained in more detail in Clause 4.