RIPE 82

Daily Archives

Nathalie Trenaman - 17-05-2021 16:00:08
Hi everyone, I'm Nathalie from the RIPE NCC. This chat panel is meant for discussion ONLY.  If you have questions for the speaker and you want the session chair to read it out, please write it in the Q&A window also stating your affiliation. Otherwise, you can ask questions using the microphone icon.         
Please note that all chat transcripts will be archived and made available to the public on https://ripe82.ripe.net/.

Jan Žorž - 17-05-2021 16:02:15
finally flow label is being used for something :)

Marco Hogewoning - 17-05-2021 16:03:12
what do you use as doorstop?

Marco Hogewoning - 17-05-2021 16:03:18
:D

Marco Hogewoning - 17-05-2021 16:03:29
(onbly joking ppl, only joking)

Elmar K. Bins - 17-05-2021 16:03:48
(what? My 7204VXR doorstop could use an upgrade...)

Marco Hogewoning - 17-05-2021 16:04:09
yes, get IPv6

Éric Vyncke - 17-05-2021 16:05:05
Not too many participants using https://en.gravatar.com/

Blake Willis - 17-05-2021 16:06:40
we have l2 pseudowire flow aware transport in the lab, rolling out soon. https://www.juniper.net/documentation/us/en/software/junos/vpn-l2/topics/concept/vpns-fat-flow-labels-overview.html

Elmar K. Bins - 17-05-2021 16:07:18
I like that the title is "X11 is broken"...

Rob Evans - 17-05-2021 16:09:19
xhost +

Shane Kerr - 17-05-2021 16:23:45
I can't decide if things are going well or badly when eBPF comes to the discussion. :-D

Jim Reid - 17-05-2021 16:23:53
Is X-windows still a thing these days? :-)

Blake Willis - 17-05-2021 16:23:54
both

Kurt Kayser - 17-05-2021 16:24:12
KISS - keep it simple straight..

Andrea Togni - 17-05-2021 16:24:37
Exactly hahahaeBPF can both save and ruin you :joy:

Shane Kerr - 17-05-2021 16:26:17
Now _that_ is a graph.

Shane Kerr - 17-05-2021 16:26:28
Nice.

Ivan Beveridge - 17-05-2021 16:28:51
Shane: IMHO, using eBPF seems a beneficial way to test, and perhaps a useful way to achieve the intended resolution without waiting for "fixing in code". It would seem to be useful to have a proper fix in code, though.

Daniel Karrenberg - 17-05-2021 16:31:37
👏🏻

Shane Kerr - 17-05-2021 16:31:43
Yeah, change to the kernel would be best, but take a while. :-D

Blake Willis - 17-05-2021 16:32:37
rhalina selective audio dropouts over your multipath fabric, turn on flow label :-)

Kurt Kayser - 17-05-2021 16:32:54
it worked when she touched the mike

Simon Leinen - 17-05-2021 16:33:08
Nice talk, thanks!

Sebastian Becker - 17-05-2021 16:33:22
Thank you, Sascha!

Alexander Azimov - 17-05-2021 16:36:07
You are welcome. But I really looking for volunteers for the IETF activity. :)

Dmitry Kohmanyuk - 17-05-2021 16:37:22
maybe the kernel patch is better start :)

Farzaneh Badiei - 17-05-2021 16:41:32
that was the neon cat I think. great art :)

Ondřej Caletka - 17-05-2021 16:42:01
https://labs.ripe.net/author/cteusche/bgp-meets-cat/

Farzaneh Badiei - 17-05-2021 16:42:43
Thank you!

Alexander Azimov - 17-05-2021 16:45:29
Patch to kernel should be accompanied with a proper document (so the bug won't be carried to another OS or transport). And unfortunately even if it is accepted it won't instantly resolve the issue during uploads over IPv6.

Shane Kerr - 17-05-2021 16:45:54
Important to have unique capitalization for every product. It's sort of a checksum built-into the name.

Dmitry Kohmanyuk - 17-05-2021 16:46:20
SoMeNaMeSaReSpEcIaL

Shane Kerr - 17-05-2021 16:46:20
Hence Apple vs OS X vs macOS.

Blake Willis - 17-05-2021 16:46:32
Juniper JunOS OS

Peter Magnusson - 17-05-2021 16:47:16
ripe-STAT

Daniel Karrenberg - 17-05-2021 16:47:28
👏🏻

Dmitry Kohmanyuk - 17-05-2021 16:47:32
and IOS vs iOS

Robert Kisteleki - 17-05-2021 16:47:34
>><<

Nigel Hickson - 17-05-2021 16:47:43
Thank you

Sebastian Becker - 17-05-2021 16:47:44
:clap:

James Kennedy - 17-05-2021 16:47:45
:clap:

Daniel Karrenberg - 17-05-2021 16:51:21
RIPEstat of course is an essential service :wink:

Chris Buckridge - 17-05-2021 16:51:36
shhh @Daniel!

Chris Buckridge - 17-05-2021 16:51:42
:wink:

Dmitry Kohmanyuk - 17-05-2021 16:52:19
I thought RIPE Atlas was..

Daniel Karrenberg - 17-05-2021 16:52:25
yeah, don't tell the governments! :wink::face_with_finger_covering_closed_lips:

Jan Žorž - 17-05-2021 16:53:12
scary...

Farzaneh Badiei - 17-05-2021 16:53:36
I'd like to know how they justify NIS2. did they empirically measure the effect of NIS1? or is this just a political game.

Blake Willis - 17-05-2021 16:54:11
please be sure to address questions to the speaker in the question tool

Dmitry Kohmanyuk - 17-05-2021 16:54:33
its a multistakeholder q&a here

Kurt Kayser - 17-05-2021 16:54:43
This is very essential work for the future of our Internet. Great job!

Brian Nisbet - 17-05-2021 16:54:49
Farzaneh, I very much doubt there's any justification other than "we must protect all the things!" See the encryption conversation.

Stephen Farrell - 17-05-2021 16:55:48
anyone know the timeline for NIS2 from now?

Daniel Karrenberg - 17-05-2021 16:56:10
@stephen: marco lnows, ask him

Nathalie Trenaman - 17-05-2021 16:56:16
Farzaneh and Stephen: you can ask this question in the Q&A section if you wish to ask Marco

Stephen Farrell - 17-05-2021 16:56:26
suspect he may already have too many questions for this slot:-)

Farzaneh Badiei - 17-05-2021 16:56:36
but you need to know how effective your protection is. it's like their arguments when it comes to child online protection. did removal of content or snooping on conversation make the kids safer...

Chris Buckridge - 17-05-2021 16:56:47
@Stephen, this is a pretty jargon-y description, but...

Chris Buckridge - 17-05-2021 16:56:51
European Parliament’s ITRE Committee (Industry, Research and Energy) timeline for NIS 2 Directive is the following :
 
First exchange of views: 13 April
Draft Report published: 3 May
Consideration of Draft Report: 26 May
Deadline for amendments : 2 June at 12:00 pm (4 June for critical entities)
Vote in ITRE: probably October 14

Nigel Hickson - 17-05-2021 16:57:11
Really useful, thanks. Understand that the Council will only adopt a "progress report" this summer, so a long way to go yet.

Chris Buckridge - 17-05-2021 16:57:12
(and of course, line breaks don't translate to the chat...)

Stephen Farrell - 17-05-2021 16:57:22
@chris: thanks, works for me (sadly, I guess:-)

Petra Zeidler - 17-05-2021 16:57:35
one can see that many parties have neglected security for the bottom line. Doesn't help to hit entities that aren't aiming for a bottom line though. It hardly can be the goal to have no root servers in the EU.

Chris Buckridge - 17-05-2021 16:58:02
and that is the ITRE Committee (Parliament) timeline, which will align with timelines for other entities (Council, the Commission)

Blake Willis - 17-05-2021 16:58:40
just put them all in Britain, Iceland, Belarus, Moldova, & Albania

Stephen Farrell - 17-05-2021 16:59:01
one of the fails (I thought) with NIS1 was that if failed to take into account open-source, (considering all evaluation as a pair-for commercial consultation for profit) - anyone know if NIS2 does any better? (sorry for the basic questions but I fall asleep if I think about NIS for more than a few minutes;-)

Carsten Schiefner - 17-05-2021 17:00:33
Thanks, Marcvo!

Jim Reid - 17-05-2021 17:01:22
Stephen, it's up to national govts/regulators to decide how they apply the NIS directives and who is and isn't an OES.

Hisham Ibrahim - 17-05-2021 17:01:35
the ripe labs article Marco mentioned https://labs.ripe.net/author/athina/caught-in-the-middle-regulatory-impact-and-our-mission-as-the-ripe-ncc/

Daniel Karrenberg - 17-05-2021 17:01:37
👏🏻

Nigel Hickson - 17-05-2021 17:01:46
@Blake - NIS2 is extra-territorial in scope (like GDPR) so "stuff" in UK would be covered if providing services into EU.

Maxim Burtikov - 17-05-2021 17:02:01
👏🏻

Brian Nisbet - 17-05-2021 17:02:07
:clap:

Chris Buckridge - 17-05-2021 17:02:12
@Jim, though the lessening of that flexibility for national regulators is one of the key shifts in NIS 2

Mick Begley - 17-05-2021 17:02:30
:clap:

Nathalie Trenaman - 17-05-2021 17:02:44
This session has now ended. The next session is the SCION BOF and it will start at 17:30 UTC+2 . More info on the RIPE 82 meeting plan: https://ripe82.ripe.net/programme/meeting-plan/