Conversation

Notices

1. Embed this notice
   Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 07:42:55 JST Stéphane Bortzmeyer

   Good morning, Brisbane! First "real" day of #IETF119. https://www.ietf.org/how/meetings/119/

   We start with the new "all dispatch" session: new job which does not know where it fits and has to be dispatched somewhere in the large IETF.

   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 07:42:53 JST Stéphane Bortzmeyer

     in reply to

     SSH v3 = SSH over HTTP

     One of the reasons is that SSH is too easily blocked by firewalls (port blocking or DPI+RST). (And the new IP is HTTP, as you know.)

     #IETF119

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 07:42:54 JST Stéphane Bortzmeyer

     in reply to

     Let's follow the agenda https://datatracker.ietf.org/meeting/119/materials/agenda-119-alldispatch-05

     First, #SSH v3

     (I hear people chat and laugh during the reminder of the Code of Conduct.)

     #IETF119

   • Embed this notice
     John Shaft (shaft@piaille.fr)'s status on Monday, 18-Mar-2024 07:44:09 JST John Shaft

     in reply to

     @bortzmeyer 😩

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 18-Mar-2024 07:44:58 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • John Shaft
     @shaft @bortzmeyer "DoH!" on dit ^^
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 07:48:49 JST Stéphane Bortzmeyer

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • John Shaft

     @lanodan @shaft Là, il en est à faire tourner SSH sur HTTP/3 sur QUIC sur HTTP/2 (pour les réseaux qui bloquent UDP et donc QUIC).

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Eragon (eragon@pl.eragon.re)'s status on Monday, 18-Mar-2024 07:52:04 JST Eragon

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • John Shaft

     @bortzmeyer @lanodan @shaft Et t'a encore des profs pour venir me dire que le modèle OSI a 7 couches et seulement 7 couches…
     WTF, le nombre des trucs imbriqué les uns dans les autres…

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 18-Mar-2024 07:54:06 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Eragon
     • John Shaft
     @eragon @bortzmeyer @shaft Ouais, l'éducation encore à OSI c'est assez typique…
     Faudrait passer à TCP/IP enfin. (Et tant qu'a faire IPv6 hein)
   • Embed this notice
     Lord (lord@pleroma.lord.re)'s status on Monday, 18-Mar-2024 07:58:23 JST Lord

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • John Shaft

     @bortzmeyer @lanodan @shaft Après le modèle OSI, il y a le modèle TCP/IP, mais finalement on va simplifier en modèle IP/HTTP.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 07:59:08 JST Stéphane Bortzmeyer

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • Eragon
     • John Shaft

     @eragon @shaft @lanodan Comme je dis toujours en cours, le modèle en couches n'a qu'une seule utilité : découper le cours en chapitres. Mais ce modèle n'a aucun rapport avec la réalité.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 18-Mar-2024 08:05:19 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Eragon
     • John Shaft
     @bortzmeyer @eragon @shaft C'est bien pour un court d'histoire sur X.25 et autres trucs qui je crois était lié a OSI.
     Forcément derrière ça colle pas sur TCP/IP et ses encapsulations diverses, pour moi ça tient d'expliquer Unix et ses pipes via des notions qui viennent d'OS rigides.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 08:19:23 JST Stéphane Bortzmeyer

     in reply to

     Now, happy eveyballs (updating RFC 8305) https://datatracker.ietf.org/doc/draft-pauly-v6ops-happy-eyeballs-v3/ One problem of happy eyeballs is that it hides problems (on purpose, but it does not help to solve the problems) so reporting is an issue.
     Other issues: IPv6-only networks (more and more common) and choices QUIC vs. TCP (not just v4 vs v6).

     So, the new algorithm prefers ECH then SVCB/HTTPS.

     #IETF119

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 08:19:25 JST Stéphane Bortzmeyer

     in reply to

     The proposal does not seem consensual (for instance, HTTP is hop-by-hop while SSH is end-to-end). Instead using WebTransport? Or MASQUE?

     #IETF119

   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:30:29 JST Stéphane Bortzmeyer

     in reply to

     Now, "Unichars", "Unicode Character Repertoire Subsets" Defining subsets of Unicode useful for some applications (for instance, I-JSON, the subset of JSON that is used at the IETF)

     "Old people in the room will remember what 'control characters' are."

     For instance, "Unicode scalars" are Unicode code points without the awful surrogates of UTF-16.

     https://datatracker.ietf.org/doc/draft-bray-unichars/

     #IETF119

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:30:31 JST Stéphane Bortzmeyer

     in reply to

     Human Rights Privacy through Deterministic Hashed Based Elision
     https://datatracker.ietf.org/doc/draft-appelcline-hashed-elision/

     Once data is sent, you can do nothing, it will be redistributed, correlated, etc.

     (He has a solution but, frankly, I did not really understand it.)

     #IETF119

   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:30:32 JST Stéphane Bortzmeyer

     in reply to

     "The problem existed for the last 35 years"

     Wrong-Recipient URL for Handling Misdirected Emails

     https://datatracker.ietf.org/doc/draft-dweekly-wrong-recipient/

     Proposal: report the wrong recipient via a HTTP POST to an URL indicated in the header of email.

     #IETF119

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 18-Mar-2024 09:32:19 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @bortzmeyer
     > "Old people in the room will remember what 'control characters' are."
     
     Eh? I guess it's called differently for unicode? (properties?)
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:34:56 JST Stéphane Bortzmeyer

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan No, it's called control characters but people born after the disuse of text terminals don't know what they are about.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:50:54 JST Stéphane Bortzmeyer

     in reply to

     Modern Network Unicode (moving after RFC 5198, which defines the use of Unicode in IETF protcols when they need "plain text")

     https://datatracker.ietf.org/doc/draft-bormann-dispatch-modern-network-unicode/

     "Plain text is no longer enough, data has structure."

     #IETF119

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Stéphane Bortzmeyer (bortzmeyer@mastodon.gougere.fr)'s status on Monday, 18-Mar-2024 09:50:55 JST Stéphane Bortzmeyer

     in reply to

     The problem is that IETF already has a framework for that, PRECIS. Why not using it? (One possible reason is that nobody knows and uses PRECIS.)

     #IETF119