Re: IEEE 1364-2005 Encryption draft with consensus changes

From: Shalom Bresticker (Shalom.Bresticker@freescale.com)
Date: Tue Jan 18 2005 - 07:41:05 PST

  • Next message: Shalom.Bresticker@freescale.com: "Re: IEEE 1364-2005 Encryption draft with consensus changes"

    Thanks for the quick reply.

    Responses:

    "Steven J. Dovich" wrote:

    > > I had to go down to 7.6 pt font size to get it on one line, instead of the
    > > regular 10 pt size.
    > >
    > > It would help if some of the strings in the line could be shortened or if
    > > the optional exit or match arguments could be omitted.
    >
    > We could certainly shorten strings, and the exit argument could be omitted.
    > The match argument is more critical to answer some of the licensing security
    > concerns that have been expressed.

    Omitting 'exit' shortens it enough so that 9.0 pt is OK, which is a reasonable
    size.
    If you can shorten the strings, then we might be able to get in 'feature' as well.

    I guess it is the same length in the second part of the example, showing the
    code after encryption?
    You will have to provide me a new version of the encoded text.

    > > In looking at this, though, I found the following syntax in 28.3.29
    > > (now 28.4.29):
    > >
    > > runtime_license=(library=<string>, entry=<string>, feature=<string>, [ exit=<
    > > string>,] [ match=<number> ] )
    > >
    > > Two problems I see here:
    > >
    > > 1. The syntax says that the 'feature' argument is required, but it does not a
    > > ppear in the example.
    >
    > An uncaught error on my part, and one that makes the current layout
    > problem worse...
    >
    > > 2. The argument shows feature=<string> and 'exit=<string>' ending with commas
    > > even if not followed by anything.
    > > Should it have been
    > >
    > > runtime_license = ( library = <string> , entry = <string>, feature = <string>
    > > [ , exit = <string> , ] [ , match = <number> ] )
    > >
    > > with the comma appearing only if the following optional argument appears
    > > (with spaces to show that white space is permitted) ?
    >
    > Yes, except for the extra comma. I think we intend:
    >
    > runtime_license = ( library = <string> , entry = <string>, feature = <string>
    > [ , exit = <string> ] [ , match = <number> ] )

    Right. The extra comma was my mistake.
    I will fix the syntax according to this.

    > One more item for tomorrow's meeting. Is there a preference for
    > either new Mantis items for some of these issues, or for appending
    > BugNotes to the existing 314 item?
    >
    > /sjd

    Personally, I would prefer appending them to 314, but the WG might have other
    preferences.

    Thanks,
    Shalom 

    --
Shalom Bresticker                        Shalom.Bresticker @freescale.com
Design & Verification Methodology                    Tel: +972 9  9522268
Freescale Semiconductor Israel, Ltd.                 Fax: +972 9  9522890
POB 2208, Herzlia 46120, ISRAEL                     Cell: +972 50 5441478

    [ ]Freescale Internal Use Only      [ ]Freescale Confidential Proprietary

    This archive was generated by hypermail 2.1.4 : Tue Jan 18 2005 - 07:24:33 PST and
    sponsored by Boyd Technology, Inc.