#ietf125 — Public Fediverse posts

IETF125 HackathonにGatherTownからリモート参加してみた
https://qiita.com/yumi-sakemi/items/ee4e7e801ccc82ba1878?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #hackathon #ietf #IETF125 #gathertown

After testing chinese payment apps at #IETF125, I discover in Arora's talk at #UndoneCS that there is an indian payment app, Aadhaar Pay https://play.google.com/store/apps/details?id=com.tcs.merchant.cags.boi&hl=ln

After testing chinese payment apps at #IETF125, I discover in Arora's talk at #UndoneCS that there is an indian payment app, Aadhaar Pay https://play.google.com/store/apps/details?id=com.tcs.merchant.cags.boi&hl=ln

The Internet Last Week

* IETF 125
https://www.ietf.org/meeting/125/
* Cuba power outage effects
https://noc.social/@cloudflareradar/116240190351546459
https://mastodon.social/@IODA/116246041272623316
https://infosec.exchange/@dougmadory/116240466331483809
https://mastodon.social/@netblocks/116240861464667713
* IoT DDoS botnets disrupted
https://www.justice.gov/usao-ak/pr/authorities-disrupt-worlds-largest-iot-ddos-botnets-responsible-record-breaking-attacks
* Unallocated IP4 /13 announced
https://infosec.exchange/@spamhaus/116250561577999852
https://bgp.he.net/net/102.224.0.0/13
https://stat.ripe.net/widget/routing-history#resource=102.224.0.0/13&starttime=2026-03-15
* CAs must perform DNSSEC validation
https://cabforum.org/2025/06/18/ballot-sc-085v2-require-validation-of-dnssec-when-present-for-caa-and-dcv-lookups/
https://infosec.exchange/@mnordhoff/116240122433847371

#IETF125 #Cuba #Botnets #Bogons #DNSSEC #X509

The Internet Last Week

* IETF 125
https://www.ietf.org/meeting/125/
* Cuba power outage effects
https://noc.social/@cloudflareradar/116240190351546459
https://mastodon.social/@IODA/116246041272623316
https://infosec.exchange/@dougmadory/116240466331483809
https://mastodon.social/@netblocks/116240861464667713
* IoT DDoS botnets disrupted
https://www.justice.gov/usao-ak/pr/authorities-disrupt-worlds-largest-iot-ddos-botnets-responsible-record-breaking-attacks
* Unallocated IP4 /13 announced
https://infosec.exchange/@spamhaus/116250561577999852
https://bgp.he.net/net/102.224.0.0/13
https://stat.ripe.net/widget/routing-history#resource=102.224.0.0/13&starttime=2026-03-15
* CAs must perform DNSSEC validation
https://cabforum.org/2025/06/18/ballot-sc-085v2-require-validation-of-dnssec-when-present-for-caa-and-dcv-lookups/
https://infosec.exchange/@mnordhoff/116240122433847371

#IETF125 #Cuba #Botnets #Bogons #DNSSEC #X509

#IETF125
For once, there was no cats on the slides:

#IETF125
For once, there was no cats on the slides:

Now, a bit of SciFi: securing communications in space (related to working groups like tiptop or dtn).

Prevent the aliens from modifying packets?

Not obvious to do with asynchronous communications (common in space).

#IETF125

Now, a bit of SciFi: securing communications in space (related to working groups like tiptop or dtn).

Prevent the aliens from modifying packets?

Not obvious to do with asynchronous communications (common in space).

#IETF125

An interesting point is that the chinese challenge is open internationaly. Foreigners are encouraged to apply. (Unlike what Russia did for GOST.)

Apparently (but the speaker refused to answer) the proposal has to be new. Do not submit ML-KEM.

#IETF125

An interesting point is that the chinese challenge is open internationaly. Foreigners are encouraged to apply. (Unlike what Russia did for GOST.)

Apparently (but the speaker refused to answer) the proposal has to be new. Do not submit ML-KEM.

#IETF125

A talk about the new chinese commercial cryptographic algorithms program at #IETF125 (ping @shaft)
"commercial" as in "no State secrets"

Current algorithms are ZUC, SM2, SM3, SM4, SM9... (All of them ISO standards.) https://en.wikipedia.org/wiki/ZUC_stream_cipher https://en.wikipedia.org/wiki/SM9_(cryptography_standard)

Some are in IANA registries (for instance for TLS) See RFC 8998

Now asking for post-quantum alternatives. (Formal announcement one year ago.) https://niccs.org.cn/niccs/index.html You can still submit a poposal!

A talk about the new chinese commercial cryptographic algorithms program at #IETF125 (ping @shaft)
"commercial" as in "no State secrets"

Current algorithms are ZUC, SM2, SM3, SM4, SM9... (All of them ISO standards.) https://en.wikipedia.org/wiki/ZUC_stream_cipher https://en.wikipedia.org/wiki/SM9_(cryptography_standard)

Some are in IANA registries (for instance for TLS) See RFC 8998

Now asking for post-quantum alternatives. (Formal announcement one year ago.) https://niccs.org.cn/niccs/index.html You can still submit a poposal!

A proposal to run #BGP over #TLS. Obvious issue: we don't want to use the classical PKI (because it would create a chicken-and-egg problem for IP).

A BGP-specific PKI, with short-lived certificates including the AS number of the BGP speaker and new introducers. (Not using the RPKI.)

#IETF125

A proposal to run #BGP over #TLS. Obvious issue: we don't want to use the classical PKI (because it would create a chicken-and-egg problem for IP).

A BGP-specific PKI, with short-lived certificates including the AS number of the BGP speaker and new introducers. (Not using the RPKI.)

#IETF125

It has been a (mosty) wonderful 4 years as Security Area Director, working with and managing awesome people and making the internet work better and more securely :) #ietf #ietf125

It has been a (mosty) wonderful 4 years as Security Area Director, working with and managing awesome people and making the internet work better and more securely :) #ietf #ietf125

Among the funny questions: at what point will ML-DSA and ML-KEM no longer regarded "Post-Quantum Cryptography" but just plain "Cryptography"? Before or after IPv6 world domination?

#IETF125

Among the funny questions: at what point will ML-DSA and ML-KEM no longer regarded "Post-Quantum Cryptography" but just plain "Cryptography"? Before or after IPv6 world domination?

#IETF125

Now, SAAG meeting (Security Area Open Meeting, basically examining possible future security work).

There are many IETF working groups in the Security Area...

#IETF125

Now, SAAG meeting (Security Area Open Meeting, basically examining possible future security work).

There are many IETF working groups in the Security Area...

#IETF125

So, when an old resolver (not knowing DELEG) queries a new server for a domain which has only DELEG (and no NS records), what the answer should be? NXDOMAIN? SERVFAIL? Synthesis of some NS?

#DNS #IETF125

So, when an old resolver (not knowing DELEG) queries a new server for a domain which has only DELEG (and no NS records), what the answer should be? NXDOMAIN? SERVFAIL? Synthesis of some NS?

#DNS #IETF125

Doing some painting at #IETF125

Doing some painting at #IETF125

DELEG working group (changing completely the #DNS delegation). Last big issue: how should a new server reply to an old client, when the server has only DELEG records and no NS records?

#IETF125

DELEG working group (changing completely the #DNS delegation). Last big issue: how should a new server reply to an old client, when the server has only DELEG records and no NS records?

#IETF125

Good morning, Shenzhen:! Seventh and last day of #IETF125 https://www.ietf.org/meeting/125/

Today, we are going to break/save/restore the #DNS with the new delegation system, DELEG. Also, security area general meeting.

Good morning, Shenzhen:! Seventh and last day of #IETF125 https://www.ietf.org/meeting/125/

Today, we are going to break/save/restore the #DNS with the new delegation system, DELEG. Also, security area general meeting.

And so the fun begins… Air Canada delays my return flight home today from #IETF125 in Tokyo by an hour…

——

Your flight AC4 to Vancouver is delayed because a mechanical issue on an earlier flight caused the scheduled aircraft to arrive late. It will now depart at 18:35. We apologize and are working to get you on your way.

And so the fun begins… Air Canada delays my return flight home today from #IETF125 in Tokyo by an hour…

——

Your flight AC4 to Vancouver is delayed because a mechanical issue on an earlier flight caused the scheduled aircraft to arrive late. It will now depart at 18:35. We apologize and are working to get you on your way.

And now, at last, AI in the dnsop working group. "DNS for AI Discovery"

https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/ https://datatracker.ietf.org/doc/draft-mozley-aidiscovery/ (5 or 6 very similar drafts, often from China)

_agents.ietf.org soon! More seriously, this is a limited (and rightly so) proposal to use DNS just for naming AI agents.

#IETF125

And now, at last, AI in the dnsop working group. "DNS for AI Discovery"

https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/ https://datatracker.ietf.org/doc/draft-mozley-aidiscovery/ (5 or 6 very similar drafts, often from China)

_agents.ietf.org soon! More seriously, this is a limited (and rightly so) proposal to use DNS just for naming AI agents.

#IETF125

"We broke LG washing machines with DNS compression change in Knot Resolver"

#InternetOfShit

#IETF125

"We broke LG washing machines with DNS compression change in Knot Resolver"

#InternetOfShit

#IETF125

Another funny question. After Cisco broke because Cloudflare changed the order of DNS records in the answer (which is perfectly legitimate), should we mandate a specific order in #DNS?

#IETF125

Another funny question. After Cisco broke because Cloudflare changed the order of DNS records in the answer (which is perfectly legitimate), should we mandate a specific order in #DNS?

#IETF125

After a lively discussion on solutions to depend less on the #DNS root (obviously no consensus, despite a tendency to deny there is a problem to solve), another hot question: DNS #censorship and the need to be transparent about it. https://datatracker.ietf.org/doc/draft-nottingham-dnsop-censorship-transparency/

What to display to the end user? (Not anything got from the resolver: security issues.) Lumen Database entry?

#IETF125

After a lively discussion on solutions to depend less on the #DNS root (obviously no consensus, despite a tendency to deny there is a problem to solve), another hot question: DNS #censorship and the need to be transparent about it. https://datatracker.ietf.org/doc/draft-nottingham-dnsop-censorship-transparency/

What to display to the end user? (Not anything got from the resolver: security issues.) Lumen Database entry?

#IETF125

It seems we have now the mandatory very-long-thread-with-a-lot-of-rant on the #IETF125 mailing list about https://datatracker.ietf.org/doc/draft-rescorla-anonymous-network/ and the possibility that it prevents us going to China (and may be other countries).

#privacy

It seems we have now the mandatory very-long-thread-with-a-lot-of-rant on the #IETF125 mailing list about https://datatracker.ietf.org/doc/draft-rescorla-anonymous-network/ and the possibility that it prevents us going to China (and may be other countries).

#privacy

Now, dnsop working group (real-time transcript said "Dina Zop") because the #DNS loves you and we love it, too.

First, a lot of stuff about various ways to be less technically dependent on the root (local caching, local root as in RFC 8806, etc).

RFC 8806, the resolver behaves as if it were authoritative for the root. RootCache is more resolver-traditional.

#IETF125

Now, dnsop working group (real-time transcript said "Dina Zop") because the #DNS loves you and we love it, too.

First, a lot of stuff about various ways to be less technically dependent on the root (local caching, local root as in RFC 8806, etc).

RFC 8806, the resolver behaves as if it were authoritative for the root. RootCache is more resolver-traditional.

#IETF125

Among the questions: will the LLMs be required to log in Meetecho? Will they have to pay a fee for attending? Are they eligible for NomCom?

#IETF125

Among the questions: will the LLMs be required to log in Meetecho? Will they have to pay a fee for attending? Are they eligible for NomCom?

#IETF125

Thinking about writing an April Fools RFC about the future "AI-only IETF", where everything, writing drafts, implementing them at the hackathon, reviewing them and trolling on the mailing lists about cookies will be done by LLMs.

#IETF125

Thinking about writing an April Fools RFC about the future "AI-only IETF", where everything, writing drafts, implementing them at the hackathon, reviewing them and trolling on the mailing lists about cookies will be done by LLMs.

#IETF125

Beginning of the Internet in China:

#IETF125

Beginning of the Internet in China:

#IETF125

Interesting questions about student participation in the IETF. The delays are not the same (a RFC can easily take longer than a master thesis).

#IETF125

Interesting questions about student participation in the IETF. The delays are not the same (a RFC can easily take longer than a master thesis).

#IETF125

Testimony from Tsinghua university at IETF. Worked on 4over6 (softwires, BEHAVE working group), SAVI (source IP address validation, currently the SAVNET working group, with extensions to routing protocols), and now AI (LLM agents running wild on the network)

Mentioned in 22 RFCs (not many universities have this score)

"IETF: the heaven for contribution to the Internet"

#IETF125

Testimony from Tsinghua university at IETF. Worked on 4over6 (softwires, BEHAVE working group), SAVI (source IP address validation, currently the SAVNET working group, with extensions to routing protocols), and now AI (LLM agents running wild on the network)

Mentioned in 22 RFCs (not many universities have this score)

"IETF: the heaven for contribution to the Internet"

#IETF125

Expect a lot of AI in #DNS (there were many side meetings at #IETF125 about AI)

Expect a lot of AI in #DNS (there were many side meetings at #IETF125 about AI)

The research arm of CNNIC is the National Engineering Laboratory. Working on many things, including of course a lot of AI (and drone identification.

#IETF125

The research arm of CNNIC is the National Engineering Laboratory. Working on many things, including of course a lot of AI (and drone identification.

#IETF125

CNNIC https://cnnic.cn/ is both the registry of ;cn (and other Chinese TLD, for instance in Unicode), the registry of some ICANN TLDs and the NIR (National Internet registry, for IP addresses).

#IETF125

CNNIC https://cnnic.cn/ is both the registry of ;cn (and other Chinese TLD, for instance in Unicode), the registry of some ICANN TLDs and the NIR (National Internet registry, for IP addresses).

#IETF125

Now, "host speaker", CNNIC (.cn registry) will talk about "Innovation and development of Internet infrastructure resources technology".

And there is a nice lunch box.

#IETF125