home.social

#ietf121 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ietf121, aggregated by home.social.

fetched live
  1. A Sustainable Internet: How to get there from here. After a successful side meeting during the #IETF121 meeting, the new Sustainability and the Internet (SUSTAIN) Proposed Research Group will have its first meeting during #IETF122 Bangkok. Learn more: ietf.org/blog/sustain-rg/

  2. A Sustainable Internet: How to get there from here. After a successful side meeting during the #IETF121 meeting, the new Sustainability and the Internet (SUSTAIN) Proposed Research Group will have its first meeting during #IETF122 Bangkok. Learn more: ietf.org/blog/sustain-rg/

  3. 🕗 Roughtime is a draft protocol aimed at providing a secure way for any device to obtain time and to prove if a server has provided false time to that device. Read about the outcomes from the #Roughtime hackathon held at #IETF121

    labs.ripe.net/author/robert-al

  4. 🕗 Roughtime is a draft protocol aimed at providing a secure way for any device to obtain time and to prove if a server has provided false time to that device. Read about the outcomes from the #Roughtime hackathon held at #IETF121

    labs.ripe.net/author/robert-al

  5. 自前のMedia over QUICの実装をIETF 121のハッカソンへ持ち込んだ話 - NTT Communications Engineers' Blog : 👀
    ---
    engineers.ntt.com/entry/202412

    #mediaoverquic #moq #quic #ietf #ietf121 #webrtc

  6. Thanks to #IETF121 Dublin meeting host Cisco and all sponsors, including Akamai, Huawei, Ericsson & Meta, without whom IETF meetings like the one last week would not be possible. Catch up on all the sessions held 2-8 November at: ietf.org/live

  7. Thanks to #IETF121 Dublin meeting host Cisco and all sponsors, including Akamai, Huawei, Ericsson & Meta, without whom IETF meetings like the one last week would not be possible. Catch up on all the sessions held 2-8 November at: ietf.org/live

  8. Interesting thread about the recent #IETF121 meeting, reflecting on the mix of technology, people, and politics that connects the Internet standards, research, and open source communities social.finkhaeuser.de/@jens/11

  9. Interesting thread about the recent #IETF121 meeting, reflecting on the mix of technology, people, and politics that connects the Internet standards, research, and open source communities social.finkhaeuser.de/@jens/11

  10. End of #IETF121 and end of this long live-tooting. Fly safe back home and have a beer.

  11. End of #IETF121 and end of this long live-tooting. Fly safe back home and have a beer.

  12. An Internet-Draft which talks a lot about Bluesky (boasting that it allows you to have your own domain name) and not mentioning the fediverse :-( datatracker.ietf.org/doc/draft

    #DNS #IETF121

  13. An Internet-Draft which talks a lot about Bluesky (boasting that it allows you to have your own domain name) and not mentioning the fediverse :-( datatracker.ietf.org/doc/draft

    #DNS #IETF121

  14. "It sometimes takes a creative detour" (= hallucination).

    #IETF121

  15. "It sometimes takes a creative detour" (= hallucination).

    #IETF121

  16. Now, a talk about generating automatically reports of IETF meetings (in LaTeX!) with AI…

    May be this live-tooting will be done by an AI at the next IETF meeting?

    #IETF121

  17. Now, a talk about generating automatically reports of IETF meetings (in LaTeX!) with AI…

    May be this live-tooting will be done by an AI at the next IETF meeting?

    #IETF121

  18. "Data is messy"

    You can say that for every project in social sciences…

    #IETF121

  19. "Data is messy"

    You can say that for every project in social sciences…

    #IETF121

  20. Gender participation statistics: the speaker's research use the first name to infer gender, which is brittle.
    (IETF does ask the participants their gender. But it is no made available to researchers.)

    #IETF121

  21. Gender participation statistics: the speaker's research use the first name to infer gender, which is brittle.
    (IETF does ask the participants their gender. But it is no made available to researchers.)

    #IETF121

  22. Justus Baron present on the geography of standardization.

    Role of the "global south" in standard setting, etc, remote vs. physical meetings.

    Distance and borders matter!

    The speaker worked on IETF and 3GPP, with data from meeting attendance..

    #IETF121

  23. Justus Baron present on the geography of standardization.

    Role of the "global south" in standard setting, etc, remote vs. physical meetings.

    Distance and borders matter!

    The speaker worked on IETF and 3GPP, with data from meeting attendance..

    #IETF121

  24. Good morning, Dublin! Seventh and last day of #IETF121 ietf.org/meeting/121/

    Today, for me, RASP meeting (auto-study of IETF).

    We'll continue to go deeper in details:

  25. Good morning, Dublin! Seventh and last day of #IETF121 ietf.org/meeting/121/

    Today, for me, RASP meeting (auto-study of IETF).

    We'll continue to go deeper in details:

  26. Many people who do a lot of international travel have a favorite comfy outfit that they like to wear while in transit. I know I do!

    Safe travels, y'all. #IETF121

  27. Many people who do a lot of international travel have a favorite comfy outfit that they like to wear while in transit. I know I do!

    Safe travels, y'all. #IETF121

  28. Today is the final day of #IETF121 and we have a full agenda of IRTF research group meetings. First up, at 09:30 UTC is the Quantum Internet Research Group with discussion of routing, addressing, and other control plane questions for quantum entangled networks, and operational experience with quantum testbeds datatracker.ietf.org/meeting/1 1/7

  29. Today is the final day of #IETF121 and we have a full agenda of IRTF research group meetings. First up, at 09:30 UTC is the Quantum Internet Research Group with discussion of routing, addressing, and other control plane questions for quantum entangled networks, and operational experience with quantum testbeds datatracker.ietf.org/meeting/1 1/7

  30. View from the #iesg at the slightly over provisioned full theatre room at #ietf121

  31. Proposal to add hard numerical limits to the #DNS parameters, in order to limit DoS attacks like #KeyTrap, Infinite or #Tsuname

    For instance, max. number of NS records : 13, max. number of DNSSEC keys: 6, max. length of the CNAME chain: 1 (3 for the sissies), etc.

    #IETF121

    @x_cli

  32. Proposal to add hard numerical limits to the #DNS parameters, in order to limit DoS attacks like #KeyTrap, Infinite or #Tsuname

    For instance, max. number of NS records : 13, max. number of DNSSEC keys: 6, max. length of the CNAME chain: 1 (3 for the sissies), etc.

    #IETF121

    @x_cli

  33. Kim Davies present the .internal TLD (reserved by ICANN so no risk of it being delegated). A new draft published to document it.

    #IETF121

  34. Kim Davies present the .internal TLD (reserved by ICANN so no risk of it being delegated). A new draft published to document it.

    #IETF121

  35. The talk about how #Bluesky and its proprietary AT protocol could use domain names as social media identifiers does not start: no sound. (The joy of remote presentations.)

    #IETF121

  36. The talk about how #Bluesky and its proprietary AT protocol could use domain names as social media identifiers does not start: no sound. (The joy of remote presentations.)

    #IETF121

  37. Funny discussion about the working group charter "Should the scope include Mars?" (or limit ourselves to the Moon).

    #IETF121

  38. Funny discussion about the working group charter "Should the scope include Mars?" (or limit ourselves to the Moon).

    #IETF121

  39. IP works fine, UDP also, TCP no. For QUIC, careeful settings can make it work.

    Avoid DNS.

    HTTP works but some headers create problms (Expires…)

    In any case, store and forwarding will be necessary.

    #IETF121

  40. IP works fine, UDP also, TCP no. For QUIC, careeful settings can make it work.

    Avoid DNS.

    HTTP works but some headers create problms (Expires…)

    In any case, store and forwarding will be necessary.

    #IETF121

  41. Now, use cases and scenarios for IP in space.

    % ping mars
    16 mn

    [A few months later]

    % ping mars
    90 mn

    And of course, intermittence.

    (See RFC 4838.)

    #IETF121

  42. "Moon mobile provider requirements" You want to install a 5G network on the Moon? (And have a lot of customers.)

    The speaker's company plans it for 2030. (Very little technical details.)

    #IETF121

  43. For space networking, we have IP (the goal of the BoF) and, already the alternative DTN Bundle (RFC 9171).

    The talk focus on IP. Planned for the Lunar Gateway moon-orbiting space station.

    #IETF121