IEEE P1735-D7-2014 pdf free
IEEE P1735-D7-2014 pdf free.IEEE P1735 TM/D7 Draft Recommended Practice for Encryption and Management of Electronic Design Intellectual Property (IP).
The intent of this document is to enable design flows that provide interoperability among IP authors, tool providers. integrators. and users of the lP. The resulting flow identified aids lP authors in providing lP that can be processed by tools without sharing protected information with IP users. Furthermore, this flow can support an integrated licensing scheme, enabling the lP authors to specify compile.time licenses. An integrated rights management scheme is also an element of the flow, which helps IP authors to control tool behavior including. hut 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 design information formats. Each design format that incorporates IP encryption describes their markup differently leading to confusing interpretation. Users of thosc standards also lack a recommended practice for interoperable usc of IP encryption.
For the lP author, the digital envelope containing the rights, key, and data blocks is the main focus. This envelope contains the source, encrypted with a symmetric cipher using a one-time session key. The session key 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 each supported 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 the tool vendor finds the blocks with their public keys, each block is decrypted with their private key. thus extracting the data key. licensing requirements, and rights constraints. If required, the tool then checks for the presence of a valid license and, if successful, decrypts the source using the data key and obeying the rights constraints. Output files from the tool may he encrypted for use in downstream tools, provided such action is granted in the IP rights.
A standard defined with all these IP author and tool vendor features would make the overall flow transparent for the IP user. Therefore, 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 also specifies a subset of markup syntax for IIDL. formats that could adapted to other file formats. These files represent potential inputs and outputs of tools that would otherwise expose lP. The generic syntax of these directives may be suitably modified for a particular file format if there are syntactic conflicts and variations which may be described in recommended practices.
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 product of exchange is accurately described, and that the tenns of the transaction will be fiuirly observed.
As a form of intellectual property (IP), electronic design data is a virtual object and is susceptible to the evolving social conventions of respect for ownership rights. Despite UflCVCfl acceptance of their rights to control the use of IP, those who produce such property frequently want to monetize their investment and receive compensation for their investment in its creation. Risk premiums to compensate for loss are not commonly itemized, but can be assumed as a factor in compensation demands. The inverse of a risk premium is the tmst discount, which is most commonly reflected in a greater willingness to market the IP as the strength of the trust model improves. This concept of the trust model is explained in more detail in Clause 4.Trade secret protection is usually impractical as the security and reliability of the protection decreases with each new transaction, It also requires a degree of confidence in the integrity of the receiving party that is an unwise assumption if the objective is to preserve the financial value of the IP.
Since party integrity is a concern, the other forms of legal protection need to be accompanied by technical security to help enforce the terms of the transaction. The recommended practices described by this standard assist in the construction and maintenance of technical security consistent with the intent of the contracted terms of the transaction.
Each command description (syntax) consists of a command keyword followed by one or more parameters. The meta-syntax for the description of the syntax rules uses the conventions shown in Table 1.IEEE P1735-D7 pdf download.
