BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//conference.wireshark.org//sf26eu//talk//AHJB7N
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-sf26eu-AHJB7N@conference.wireshark.org
DTSTART;TZID=CET:20261104T113000
DTEND;TZID=CET:20261104T123000
DESCRIPTION:_The packet stories are back with a few new cases from my work 
 as an independent troubleshooter!_\n\n**_To be the network or not to be th
 e network\, that's the question!_**\n\nThis is a question we face a lot. T
 he network is blamed by default\, but is it really the network. During thi
 s session a couple of real life cases will be presented. What was the prob
 lem\, how was it analyzed\, what can we learn about the process and off co
 urse the answer to the question: was it the network?
DTSTAMP:20260922T091936Z
LOCATION:Room 2
SUMMARY:Packet stories #2 - Sake Blok
URL:https://conference.wireshark.org/sf26eu/talk/AHJB7N/
END:VEVENT
END:VCALENDAR