NOTICE: August 08, 2016 Si2 EMAIL REFLECTOR MAIL IS BEING REJECTED BY SOME COMPANIES
NOTE: Si2 External IP Address Changes
* Recently, Si2 switched network service providers and subsequently, all of its external IP addresses.
* Email reflectors are used by our many Production and Open Standards collaborative research/development working groups.
* If your company uses access control lists to manage email traffic, and you send emails via the Si2 reflector list system, then the following information will be relevant to you.
CONTACT YOUR IT DEPARTMENT TO VERIFY YOUR CURRENT OR FUTURE STATUS:
After the Si2 IP changes, reflector list messages that previously appeared as email coming from 184.108.40.206 will now show as email coming from 220.127.116.11. Any access control lists that reference the old Si2 IP (18.104.22.168), will need to be updated to the new Si2 IP (22.214.171.124) in order to restore previous functionality. Additionally, make sure that your company IT has Si2 white listed!
Low Power Coalition Technical Steering Group(LPC TSG)
Request for CPF Validation Test Cases
The CPF Validation program is initiated by the Low Power Coalition Technical
Steering Group (LPCTSG). The LPCTSG has two different objectives:
1) Provide an arbiter of correctness for CPF files.
2) Provide test cases that CPF supporting tool developers can use to validate
To LPC members:
The Si2 Low Power Coalition requests the following of all LPC members:
a) Try running the beta CPF 1.1 reference parser on
any CPF 1.1. sample files you might have, and report and
provide examples to (how to contribute) of any cases
where a file you believe to be correct reports an error, or a file you believe
to be erroneous does not.
b) Contribute any CPF 1.0/1.1 files (real or toy cases, correct or erroneous)
that you can toward a suite of valid and invalid CPF files.
(how to contribute). Where possible,
accompanying Verilog files may be helpful toward developer deeper
To the CPF community:
The Si2 Low Power Coalition solicits contributions of CPF 1.0/1.1
files (real or toy cases, correct or erroneous) toward a suite of valid
and invalid CPF files (how to contribute). Where possible, accompanying Verilog files
may be helpful toward developer deeper checking capabilities.
Contribute CPF 1.0/1.1 Test Cases
Package your CPF test cases as a tar.gz. Include
a Readme file which describes
the CPF version (1.0/1.1), any instructions, version of parser to use, expected results, etc.
Email your package to: