From: Dave Taht <dave.taht@gmail.com>
To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: Open-source software vs. the proposed Cyber Resilience Act
Date: Mon, 14 Nov 2022 02:23:51 -0800 [thread overview]
Message-ID: <CAA93jw7tLRDVWcV__QBCLOvG_Zmon4HkGi8tLRTpH-4K2Wr3iQ@mail.gmail.com> (raw)
In-Reply-To: <4F5A7CAD-54E4-4BCF-924D-F54172A1C34F@nlnetlabs.nl>
---------- Forwarded message ---------
From: Alex Band <alex@nlnetlabs.nl>
Date: Mon, Nov 14, 2022 at 1:56 AM
Subject: Open-source software vs. the proposed Cyber Resilience Act
To: North American Network Operators' Group <nanog@nanog.org>
The NLnet Labs foundation is closely following a legislative proposal by the
European Commission called the Cyber Resilience Act (CRA), affecting almost
all hardware and software offered on the European market.
In the nearby future, manufacturers of toasters, ice cream makers and
(open-source) software will have something in common: to make their products
available on the European market, they will need to affirm their compliance
with EU product legislation by affixing the CE marking.
We have published background information and our views here:
https://blog.nlnetlabs.nl/open-source-software-vs-the-cyber-resilience-act/
The current proposal would require developers of open-source software deemed
both ‘critical’ and a ‘commercial activity’ to jump through elaborate and
potentially costly compliance hoops to make their software available in the
EU. What defines a 'critical product' and a 'commercial activity' is key for
this discussion.
Please get in touch with us if you have concerns or this affects you. Maarten
Aertsen <maarten@nlnetlabs.nl> is spearheading this initiative.
Kind regards,
Alex Band
NLnet Labs
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-11-14 10:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4F5A7CAD-54E4-4BCF-924D-F54172A1C34F@nlnetlabs.nl>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7tLRDVWcV__QBCLOvG_Zmon4HkGi8tLRTpH-4K2Wr3iQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=openwrt-devel@lists.openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox