Posts Tagged #ietf121

2024-11-08 bortzmeyer ┃ 1#️ ┃ RE: bortzmeyer

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

2024-11-08 bortzmeyer ┃ 1πŸ”— 2#️

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

2024-11-08 bortzmeyer ┃ edited ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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

2024-11-08 bortzmeyer ┃ edited ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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?
[…]

2024-11-08 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

"Data is messy"
You can say that for every project in social sciences…
[…]

2024-11-08 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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 […]

2024-11-08 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

Justus Baron present on the geography of standardization.
Role of the "global south" in standard setting, etc, remote vs. physical meetings.
[…]

2024-11-08 bortzmeyer ┃ edited ┃ 1πŸ”— 2#️ 2πŸ’¬ ┃ RE: bortzmeyer

OK, start of the proposed research group (like a working group but for the #IRTF) RASP datatracker.ietf.org/meeting/1…
#IETF121

2024-11-08 bortzmeyer ┃ 1πŸ”— 2#️

#vΓ©lotaf Γ  Dublin (mais pas pour moi, je vais Γ  l'#IETF121 Γ  pied).

2024-11-08 bortzmeyer ┃ 2πŸ”— 1#️ 1πŸ’¬

Good morning, Dublin! Seventh and last day of #IETF121 ietf.org/meeting/121/
Today, for me, RASP meeting (auto-study of IETF).
[…]

2024-11-07 bortzmeyer ┃ 4#️ 1πŸ‘€ ┃ RE: bortzmeyer

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 […]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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

2024-11-07 bortzmeyer ┃ 2#️ 1πŸ’¬ ┃ RE: bortzmeyer

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

2024-11-07 bortzmeyer ┃ 1πŸ”— 2#️ 1πŸ’¬ ┃ RE: bortzmeyer

Now, DNSOP, "new work for consideration" session, we want to add funny things to the #DNS
datatracker.ietf.org/meeting/1…
[…]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

IP works fine, UDP also, TCP no. For QUIC, careeful settings can make it work.
Avoid DNS.
[…]

2024-11-07 bortzmeyer ┃ edited ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

Now, use cases and scenarios for IP in space.
% ping mars
[…]

2024-11-07 bortzmeyer ┃ edited ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

"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 […]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

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. […]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

% ping moon
2.6 s
#IETF121

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

"OK, you have ten minutes for your talk on lunar IP networking"
Ten minutes to go to the moon and back?
[…]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

"Initial deployment: lunar networking" (not really deep space)
Anyway, will my employer pay the bill for my experiments on the ground?
[…]

2024-11-07 bortzmeyer ┃ 1πŸ”— 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

Now, deep space meeting. To go boldly where IETF never went before.
#IETF121

2024-11-07 bortzmeyer ┃ 2#️ 1πŸ’¬ ┃ RE: bortzmeyer

Now, discussion about a mechanism for a smooth key rollover / replacement in #OpenPGP .
For instance, should we add a reference in the format to "preferred key server to fetch the new […]

2024-11-07 bortzmeyer ┃ 1#️

Show of hands at #IETF121: "People are vigourously without an opinion".

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ‘€ 1πŸ’¬ ┃ RE: bortzmeyer

Most of the issues seem to be about combining PQ and traditional keys/signatures (because we cannot be sure of either technique: we need to combine them, which is difficult).
Ping […]

2024-11-07 bortzmeyer ┃ edited ┃ 1πŸ”— 3#️ 1πŸ’¬ ┃ RE: bortzmeyer

What about a bit of post-quantum cryptography in #OpenPGP? datatracker.ietf.org/doc/draft… (inline with the NIST standards published in August, ML-KEM - ex-Kyber - and ML-DSA - […]

2024-11-07 bortzmeyer ┃ 1πŸ”— 2#️ 1πŸ’¬ ┃ RE: bortzmeyer

Now, #OpenPGP working group. Lots of stuff on the agenda: datatracker.ietf.org/meeting/1…
Reminder: OpenPGP has a new standard, RFC 9580, published this summer.
[…]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

5G alllows "slicing" (a virtual network built over 5G, with specific charcacteristics, typically if you pay for them). The interaction with IETF protocols is in the recent RFC 9543 - TEAS […]

2024-11-07 bortzmeyer ┃ 1#️ 1πŸ’¬ ┃ RE: bortzmeyer

In 5G, all the data is transported over GTP, which is itself encapsulated in IP. So a packet is made of data / GTP header / IP header/ L2 header.
#IETF121

────

Next page (30-60)

────

πŸ”Ž Posts by hashtag

────

πŸ“‘ Local feed

πŸ•οΈ Communities

πŸ”₯ Hashtags

πŸ”Ž Search posts

πŸ”‘ Sign in

πŸ“Š Status

πŸ›Ÿ Help