Today, for me, decentralization (DIN research group), privacy (PEAR research group) and both plenaries, the technical one on #privacy, and the administrative one with probably a heated discussion about the recent resignation of the #RFC editor and what to do next.
A typical problem of mesh networks is compensation: why giving network capacity gratis?
Their solution measures a lot of things (such as the amount of bytes) and put it in an #Ethereum blockchain. ("We tried HyperLedger but Ethereum works.")
And yet another presentation by a guy who thinks that adding "blockchain" to any system makes it decentralized. (And who clouds issues by spending a lot of time on unimportant technical details.) #IETF105
Some slides titles at #IETF105 are surprising:
IoT devices are doing end-to-end encryption but the ends are the device and the company. The user is not in it.
Proposal: a debug mode allowing the user to dump the traffic of his smart gadgets in cleartext.
"If data exists, it's available to governments." #IETF105
Statistics for #IETF105 : 1079 participants onsite (from 48 countries) 147 beginners.
Hackathon : 280 onsite (biggest IETF hackathon), 42 projects.
Mais c'est pas fini ?
Bon boulot !
@Clailou Ah non, il n'est que 18h40 ici. On a encore toute la discussion sur la crise du RFC editor.
But of course, it will depend on the new RFC editor. The current one stepped down, following an internal crisis, and will leave at the end of 2019. (Standing ovation for Heather.)
@bortzmeyer Oh wow, Heather is leaving the RFC Editor position??
@darius Unfortunately, yes, she resigned because of problems that we are going to discuss now.
@bortzmeyer I'm greatly appreciating your live blog, I'll try to keep an eye out for minutes too
@darius Good luck for following all the discussion :-}
@bortzmeyer I think I'm getting a handle on it! Thank goodness for mailing list archives
Some remarks that seem common in the discussion about the #RFC editor crisis: the RFC editor model (RFC 6635) is too complicated, IETF particicipants were not informed of what was happening, and of the crisis (this changed this morning with the message "RSOC apology"), misunderstandings were many...
@bortzmeyer that would be a great idea,
AND I would start at the biggest "IOT" of all : the smartphone !!
indeed : in recent android phones, it's impossible to know what https queries apps are doing : biggest apps are doing SSL Certificate Pinning, therefore not allowing even a home-made (and system-accepted) CA :(
@pmevzek In what way is it more realistic? Corporations will refuse that as well.
(Otherwise, I agree: really solving the problem will require ending capitalism.)
@bortzmeyer Because at least there is the possibility of "the market to decide". Users *may* have a choice between device A working that way, and device B not that way. At least some of them can choose A, as some companies may see the way to profit from that case and why interoperability could help. Of course, it is known that users do not base their buying choice on security/privacy features first. And interoperability is both difficult on technical and non technical aspects.
Vive les gougères ! mnt-by: @yapret @papaeng89