#ietf104 — Public Fediverse posts

Good bye, Prague. #IETF104

#IETF104 is now over, one last beer and we get back home. By, bye, Prague, see you in Montréal in july and, in the mean time, let's write drafts, comment on drafts, paint bikesheds, and save the Internet!

Don't miss the nice dashboard monitoring the current state and options of various #DNS public resolvers https://dnsprivacy.org/jenkins/job/dnsprivacy-monitoring/ #privacy #IETF104

Very good comparison of the privacy policies of #DNS resolvers providers, by Sara Dickinson https://dnsprivacy.org/wiki/display/DP/Comparison+of+policy+and+privacy+statements #privacy #IETF104

Now, last meeting of #IETF104, DPRIVE (#DNS privacy). Among other drafts, an update to RFC 7626, and recommendations for DNS privacy operators.

Long discussion about the proposed #DNS ANAME record (a long issue, related to "CNAME at apex"): having a standard way to say:
example.com. IN CNAME cloud-provider-stealing-personal-data.com.
Biggest problem is of course turning authoritative name servers into resolvers.
#IETF104

Chair, during some tense exchange: "I think you are actually in violent agreement"

Participant: "No, we are not"

#IETF104

Giovanni Moura on stage about his draft of recommendations for #DNS authoritative servers operators, specially about resiliency and resistance to attacks.

More anycast, pay more attention to routing to them...

#IETF104 #saveTheDNS #BGP

Good morning, Prague! Fifth and last day of #IETF104 https://www.ietf.org/how/meetings/104/

Today, for me, second session of DNSOP (everything #DNS) https://datatracker.ietf.org/meeting/104/materials/agenda-104-dnsop-04 and DPRIVE (DNS privacy) https://datatracker.ietf.org/meeting/104/materials/agenda-104-dprive-01

Juliana Guerra on stage about the Internet-Draft "Feminism and protocols" https://datatracker.ietf.org/doc/draft-guerra-feminism/ #IETF104

Web sites mentioned by the speaker about women and queer rights: https://genderit.org/ https://erotics.apc.org/ https://www.takebackthetech.net/ #IETF104

"gender non-conforming people" We hear things unusual at IETF. (And almost no acronyms, it does not feel like an IETF meeting.) #IETF104

Mallory Knodel on stage about "Feminist Internet". "The purpose is to dismantle patriarchy." https://feministinternet.org/ #IETF104

In this HRPC group, at least, we should have people on the fediverse, but it does not seem so. #IETF104

Now, HRPC at #IETF104 : "Human Rights and Protocol Considerations". It seems a technical glitch prevents us from starting. (I see technical people frantically trying several things.)

@pmevzek @Shaft @ResolverCN Si l'attaquant contrôle le poste de travail, c'est doublement foutu : techniquement, et aussi parce qu'on peut se dire qu'il est « légitime ».

Pour citer Eric Rescorla (M. TLS) à la réunion DoH à l'#IETF104 « si quelqu'un contrôle le réseau mais pas la machine terminale, c'est un attaquant, pour moi ».

‪Discussing how #IETF working groups can use #git and Github at #IETF104 ...‬

Heard at #IETF104: "We still don't know how many kittens died [because of the #DNSSEC key change]."

Bold proposal: no more announcements of #DNSSEC key changes. Because if we don't announce them, software vendors will do a better job at automating everything.

(I suggest to do the same for leap seconds...)

#IETF104

The bizarre effects of the last #DNSSEC key change at the #DNS root : http://www.circleid.com/posts/20190326_unexpected_effects_of_the_2018_root_zone_ksk_rollover/ (not really fully understood) #IETF104

"If you are not familiar with the subject, you may find the meeting confusing." Like all meetings, no? #IETF104

"KSK futures" meeting. Should we change (rollover) the #DNSSEC key of the #DNS root every day? Every year? From time to time when we fancy it, as it was done before?

You may read the ICANN report on the previous change : https://www.icann.org/review-2018-dnssec-ksk-rollover.pdf

#IETF104

@bagder At the same time as #IETF104?

Sorry, people, I could not live-toot about the #DoH (DNS-over-HTTPS) side meeting yesterday at #IETF104 since I was chairing it. Nothing really new and no decisions. I may blog on it in the next days, if time permits.

Good morning, Prague! Fourth day of #IETF104 https://www.ietf.org/how/meetings/104/

For me, today, the "key rollover" session (should we change the #DNSSEC key of the #DNS root zone every year, to make it an unnoticeable event?) https://datatracker.ietf.org/meeting/104/materials/agenda-104-ksk-00 and HRPC (Human Rights and Protocol Considerations) https://datatracker.ietf.org/meeting/104/materials/agenda-104-hrpc-05

"We fully [grin] trust our registrars, so we don't have a registry lock." #IETF104 #cybersecurity

Meeting of SeLoReLo (Security Lock / Registry Lock) informal group at #IETF104. If you want to know why we need domain name registry locks, see https://krebsonsecurity.com/2019/02/a-deep-dive-on-the-recent-widespread-dns-hijacking-attacks/ (warning, the title is misleading)

"Internet for Humans" "Reduced carbon footprint" Seems promising. #NGI #IETF104

Presentation of Next Generation Internet. A lot of money. Researchers, don't hesitate to ask, 20 M€ wait for you. https://www.ngi.eu/ #IETF104