2) EECC is the new European Electronic Communications Code Standards which now include IETF Internet Data Protocols and their uses under GDPR (GLOBAL DAYA PROTECTION DIRECTIVE). https://en.m.wikipedia.org/wiki/European_Electronic_Communications_Code and https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32018L1972
In order to allow existing and new IETF standards to be used in the EU, IETF standards, their use models, and the licensing controlling them must meet the hurdle of being able to be operated under GDPR as well as the grouping for EU nations. This has been brewing for 2 years now so it should not be a surprise.
As just one of many implications... For IETF protocols with patent protected or derived methods this has serious effects for the vendors using them. It also means any and all protocols derived from controlled IP that is already in place must be brought into compliance with this new set of hurdles.
This dual head-butt to the radically complicated the idea of patent derivatives in IETF protocols, and for those already in peoduction, their licensing must meet these new tests.
Already deployed IETF protocols will have to be revised under co-copyright standings and this creates a huge problem for VENDORS like apple ios, Google android, Microsoft networking, virtual computing, and many others as well.
There are serious reasons pending why IETF needs to reopen the IPR group to address these issues, and ongoing ones as well in global Internet compliance.
//Todd glassey
-------- Original Message --------
On Sep 23, 2020, 21:50, Michael Richardson < mcr@xxxxxxxxxxxx> wrote:
please post an ID revising our process.
I have no idea about what the SCHREMS2 ruling means, I just know that "RAND"
is a useless kind of license for open source.--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
