The purpose 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.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 "e;IP"e; will be used to mean Intellectual Property electronic design data. Electronic Design Intellectual Property is a term used in the electronic design community. It refers to a reusable collection of design specifications which represent the behavior, properties, and/or representation of the design in various media. Examples of these collections include, but are not limited to: * A unit of electronic system design * A design verification and analysis scheme (e.g., test bench) * A netlist indicating elements and the interconnection thereof to implement a function * A set of fabrication instructions * A physical layout design or chip layout * A design intent specification The term is partially derived from the common practice for the collection to be considered the intellectual property of one party. Hardware and software descriptions are encompassed by this term.
Get Involved In The Development Of This Standard
Contact the IEEE-SA Liaison Simply click here to voice your interest. Joan Woolery Learn More About Standards ParticipationAnyone can participate, there are a variety of programs and services to
facilitate the involvement of industry and the public. More Become a Member and Ballot on this StandardMembership empowers you to participate & lead in the development of
standards. Tell Me More