Hi all, On 1/16/25 17:24, Mallory Knodel via rssac-caucus wrote:
* Slide 4: Another bubble (not sure these should be bubbles) is that IP addresses identify both services and people accessing those services. Otherwise the modern problems on the following slide might be confusing.
IP addresses don't identify people. (Some people use the same device.) But I get your point, so perhaps: "IP addresses identify connected devices (services, people, ...)" ... which is vague enough to transport the idea correctly (I think). Also suggest to change "hosts" to "devices" in the green bubble of that slide. These remarks triggered my email; adding some more thoughts below while I'm at it.
* Slide 6: There are better schematics to describe this. Sorry to toot my own horn, but in my book we use the attached graphic.
Both graphics describe subdomains under a registered domain (like en.wikipedia.org) as the "subdomain zone", which is not a correct use of the technical term. (Zones are things that have NS records; the name mentioned doesn't have any.)
* Slide 9: Security, privacy, resilience-- then on the right you can describe how it's achieved but this refinement would keep the ideas simple enough to remember.
+1
* Slides 12-13 just need a conceptual rework. It's not zone vs system, it's about who maintains which records. Build on what you've described in slide 6. You could then take each party in turn to describe how they achieve their role but slide 13 is not helpful as it is.
Agree about 13, but I think the "zone vs system" comparison is useful. Best, Peter -- Like our community service? 💛 Please consider donating at https://desec.io/ deSEC e.V. Möckernstraße 74 10965 Berlin Germany Vorstandsvorsitz: Nils Wisiol Registergericht: AG Berlin (Charlottenburg) VR 37525