1076.6

All,
While I don't think that 1076.6 is due just yet, if we think a
revision is needed, it is probably time to start.  The current
IEEE version is 1076.6-2004, so I think it is due in 2009 (+ extensions?).

Best,
Jim

> TEAM:
>  
> It would be sad to let 1076.6 and 1364.1 to go obsolete because of no 
> reaffirmations. These standards made it possible to harmonize many 
> synthesis tools that were going in many different ways, some were very 
> "wild" I add my support to the words below from Alex and Shalom.
>  
> Shalom (Peace).
>  
> 
> */William A. (Bill) Hanna; Ph.D.EE/*
> */Technical Fellow - Electronics Design&Analysis/*
> Boeing-IDS Programs                                   Phone: (314) 232-0714
> MC S106-3060                                                Mobile: 
> (314) 302-8039
> St. Louis, MO 63166-0516    E-Mail: william.a.hanna@boeing.com  
> 
> ------------------------------------------------------------------------
> *From:* Alex Zamfirescu [mailto:alex.zamfirescu@gmail.com]
> *Sent:* Friday, February 22, 2008 4:40 AM
> *To:* Bresticker, Shalom
> *Cc:* Victor Berman; stds-dasc@server.eda.org
> *Subject:* Re: DASC Meeting Minutes
> 
> Hi Shalom:
>  
> 1364.1 is a sibling of 1076.6. Those were produced in a special way 
> after a donation to the Industry PTAB occurred and an agreement with 
> some restrictions on how these two will be published was in place.
>  
> I will not go in the history here. Most standards do not have any 
> letters from holders of related patents. However, those for which a 
> letter according to IEEE rules was requested and issued are somehow 
> special. I am not sure what happens with that letter if the standard 
> does not exist anymore (i.e. if it is not re-affirmed).
> Note that both standards I mentioned are entangled with some patented 
> ("latch inference")
> know how. With valid standards the assuring letters work for sure, with 
> non existing the "landscape" has still to be clarified. Therefore, the 
> simplest thing to do, without looking at more work in analysis, is to 
> re-affirm, and not bother about anything else.
>  
> Note that DASC should be aware of the standards which have letters 
> attached.
> IMHO, the simplest thing is to keep alive all those which have such 
> letters.
>  
> On the other hand both are also IEC standards, so the maintenance 
> according to
> DASC operating procedures, should be carried as Dual Logo standards. 
> That have some
> implications on notifications, but that is yet another problem which 
> should not concern
> most of us.
>  
> I hope you understood my quest for simplicity, and desire to "keep 
> options open."
>  
> I am glad you wrote, because at the DASC meeting today I tried to 
> explain this, and I got an action (or at least I thought I got one) to 
> clarify it in an e-mail. This was it, I hope.
>  
>  
> Best regards,
>  
> Alex Zamfirescu
> 
>  
> On 2/22/08, *Bresticker, Shalom* <shalom.bresticker@intel.com 
> <mailto:shalom.bresticker@intel.com>> wrote:
> 
>     Hi,
>      
>     I'm no longer a member of DASC, but if I were, I would not favor
>     reconfirming 1364.1. I don't think anyone actually implements it,
>     and I was never happy with its quality.
>      
>     Shalom
> 
>         ------------------------------------------------------------------------
>         *From:* owner-stds-dasc@server.eda.org
>         <mailto:owner-stds-dasc@server.eda.org>
>         [mailto:owner-stds-dasc@server.eda.org
>         <mailto:owner-stds-dasc@server.eda.org>] *On Behalf Of *Victor
>         Berman
>         *Sent:* Friday, February 22, 2008 10:27 AM
>         *To:* stds-dasc@server.eda.org <mailto:stds-dasc@server.eda.org>
>         *Subject:* DASC Meeting Minutes
> 
>          
> 
>         Dear DASC Members,
> 
>          Please find enclosed the approved minutes from our meeting in
>         December 2007 and the draft minutes from today's meeting for review.
> 
>          
> 
>         Regards,
> 
>           Victor
> 
>          
> 
>         Victor Berman
> 
>         President & CEO
> 
>         Improv Systems, Inc.
> 
>         Email: victorb@improvsys.com <mailto:victorb@improvsys.com>
> 
>         Office:   978 927 0555 x 27
> 
>         Mobile:  978 390 7704
> 
>          
> 
> 
>         -- 
>         This message has been scanned for viruses and
>         dangerous content by *MailScanner*
>         <http://www.mailscanner.info/>*, and is
>         believed to be clean. *
> 
>     *---------------------------------------------------------------------
>     Intel Israel (74) Limited
> 
>     This e-mail and any attachments may contain confidential material for
>     the sole use of the intended recipient(s). Any review or distribution
>     by others is strictly prohibited. If you are not the intended
>     recipient, please contact the sender and delete all copies.
>     *
> 
>     * *
>     *
>     -- 
>     This message has been scanned for viruses and
>     dangerous content by <http://www.mailscanner.info/>**MailScanner*
>     <http://www.mailscanner.info/>*, and is
>     believed to be clean. *
> 
> *
> 
> 
> -- 
> Alex Zamfirescu
> 650-814-7514
> alex.zamfirescu@gmail.com <mailto:alex.zamfirescu@gmail.com>
> http://alex.zamfirescu.googlepages.com
> =========
> This communication, and its attachments, may contain
> privileged, or confidential information, intended for a specific
> individual and purpose, and is protected by law. If you are not the
> intended recipient, you should delete this communication, and/or
> shred the materials and any attachments, and are hereby notified that
> any disclosure, copying or  distribution of this communication, or
> the taking of any action based on it, is strictly prohibited.
> Interception of e-mail is a crime under the  Electronic Communication
> Privacy Act, 18 U.S.C. 2510-2521 and 2701-2709. If you have
> received this transmission in error, please notify me by reply
> e-mail at alex.zamfirescu@gmail.com <mailto:alex.zamfirescu@gmail.com> 
> and destroy the original transmission
> and its attachments without reading them, or saving them to disk.
> Thank you for your cooperation in this matter.
> =========
> -- 
> This message has been scanned for viruses and
> dangerous content by <http://www.mailscanner.info/>**MailScanner* 
> <http://www.mailscanner.info/>*, and is
> believed to be clean. *
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jim Lewis
Director of Training             mailto:Jim@SynthWorks.com
SynthWorks Design Inc.           http://www.SynthWorks.com
1-503-590-4787

Expert VHDL Training for Hardware Design and Verification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.