Hi Hank, Hi all,

Thanks for your input. I am happy to hear that you see RIPE Labs as platform for leading edge technical information. And it will certainly not become a policy blog. However, RIPE Labs was not only set up for technical topics. The scope was meant to be very broad as you can see in the About RIPE Labs section:

https://labs.ripe.net/about/all-about-ripe-labs

It is basically a platform to share ideas with others in the community. Especially if policy or other developments are potentially affecting the technical community, we feel that it is important to inform our community about these matters. And RIPE Labs is a place where we can explain background information and timely topics in some more detail than on www.ripe.net or in an email.

Since its inception we have quite regularly posted non-technical articles. However, the vast majority of RIPE Labs content has always been technical in nature, and we expect this to remain the case moving forward.

I hope this responds to your concern.

Kind regards,

Mirjam Kuehne
RIPE Labs Community Builder
RIPE NCC



On 2/10/13 10:25 AM, Hank Nussbacher wrote:
At 16:44 01/10/2013 +0300, Chris Buckridge wrote:

I have viewed the RIPE Labs as a technical lab for new and leading edge
systems in the realm of networking and routing.  Using it to distribute
and discuss policy (even related to technical issues) diminishes and
dilutes the focus of the RIPE Labs.  Perhaps some other section of RIPE
would be a more appropriate venue?

-Hank

Dear colleagues,

We have published a new article on RIPE Labs, outlining the RIPE NCC's
general strategy for engaging with the institutions of the European
Union. It also looks specifically at recent legislative proposals
regarding electronic identification (eID) and network and information
security (NIS):
https://labs.ripe.net/Members/chrisb/engaging-with-eu-legislative-process

As ever, we welcome all feedback and discussion, either on the
Cooperation Working Group mailing list, or on the RIPE Labs page. We
also look forward to further discussion of these issues at the
upcoming RIPE 67 Cooperation Working Group session.

Best regards,
Chris Buckridge
External Relations Officer, RIPE NCC




Reply via email to