IETF125 HackathonにGatherTownからリモート参加してみた - Qiita

IETF125 HackathonにGatherTownからリモート参加してみた はじめに こんにちは!暗号のおねぇさんことGMOコネクト(GMOインターネットグループ エキスパート)の酒見です。 IETF125(2026年3月、深圳・中国)のHackathonに、今回...

Qiita
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
BOI BHIM AADHAR – Applications sur Google Play

BOI BHIM AADHAR is a payment interface for Merchant using AADHAR authentication.

IETF 125 Shenzhen

Information about the IETF 125 Shenzhen meeting on 14-20 March 2026.

IETF
Back home #IETF125
Hi from Hong Kong  #IETF125
#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

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!

ZUC stream cipher - Wikipedia

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