#ietf123 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ietf123, aggregated by home.social.
-
#IETF123 Bad Attitude Pecha Kucha -- Let's talk about problems: The image of #DNSSEC
by Barbara from #deSEC (@ItsAutomatic )
https://youtu.be/7mQ5x7Jpj4I?feature=sharedI am definitely on the "best shot at #DNS security so far" side…
-
#IETF123 Bad Attitude Pecha Kucha -- Let's talk about problems: The image of #DNSSEC
by Barbara from #deSEC (@ItsAutomatic )
https://youtu.be/7mQ5x7Jpj4I?feature=sharedI am definitely on the "best shot at #DNS security so far" side…
-
#IETF123 Bad Attitude Pecha Kucha -- Let's talk about problems: The image of #DNSSEC
by Barbara from #deSEC (@ItsAutomatic )
https://youtu.be/7mQ5x7Jpj4I?feature=sharedI am definitely on the "best shot at #DNS security so far" side…
-
In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html
-
In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html
-
In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html
-
In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html
-
In july 2025, there was the #IETF meeting, the 123th, in Madrid. Before the meeting, there was the now traditional hackathon. I worked on the future protocol #RPP (RESTful Provisioning Protocol), which may be the successor of #EPP. https://www.bortzmeyer.org/hackathon-ietf-123.html
-
The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/
-
The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/
-
The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/
-
The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/
-
The #IETF123 @irtf Open Session featured Haarika Manda and Hendrick Chech presenting their ANRP-winning research on Internet access inequities and LEO satellite network measurements and analysis. Watch the full presentations: https://www.ietf.org/blog/ietf123-anrp/
-
#ietf123 oauth wg session Brian Campbell about SD-JWT VC
Some subtle jokes included ;-)
Some not so subtlehttps://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-10
-
#ietf123 oauth wg session Brian Campbell about SD-JWT VC
Some subtle jokes included ;-)
Some not so subtlehttps://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-10
-
#ietf123 oauth wg session Brian Campbell about SD-JWT VC
Some subtle jokes included ;-)
Some not so subtlehttps://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-10
-
#ietf123 oauth wg session Brian Campbell about SD-JWT VC
Some subtle jokes included ;-)
Some not so subtlehttps://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-10
-
Ducks before heading off to the airport 🦆 :) #ietf123
-
Ducks before heading off to the airport 🦆 :) #ietf123
-
Ducks before heading off to the airport 🦆 :) #ietf123
-
Ducks before heading off to the airport 🦆 :) #ietf123
-
Do I want to know why there is an ambulance outside #ietf123 ?
-
Do I want to know why there is an ambulance outside #ietf123 ?
-
Do I want to know why there is an ambulance outside #ietf123 ?
-
Do I want to know why there is an ambulance outside #ietf123 ?
-
This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols
-
This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols
-
This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols
-
This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols
-
This week the Internet Engineering Task Force (IETF) — made up of protocol engineers from companies and organizations around the world — met in Madrid and online at #IETF123. CDT has been playing an active role in the proceedings, focusing on privacy and censorship-resistance in Internet protocols
-
The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/
-
The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/
-
The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/
-
The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/
-
The #IETF123 meeting is wrapping up! 1700+ participants around the world came together—in Madrid & online—to work on emerging Internet technologies and issues. Thanks to host Ericsson and to all the meeting sponsors for their support. On demand recordings let you watch any of the 100+ sessions you may have missed: https://ietf.org/live/
-
Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"
Just by sending the results of a resolution to your friends.
Implemented in Unbound at the IETf hackathon
-
Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"
Just by sending the results of a resolution to your friends.
Implemented in Unbound at the IETf hackathon
-
Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"
Just by sending the results of a resolution to your friends.
Implemented in Unbound at the IETf hackathon
-
Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"
Just by sending the results of a resolution to your friends.
Implemented in Unbound at the IETf hackathon
-
Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"
Just by sending the results of a resolution to your friends.
Implemented in Unbound at the IETf hackathon
-
Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).
Zone cut to nowhere:
internal.example.com. IN NS .
-
Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).
Zone cut to nowhere:
internal.example.com. IN NS .
-
Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).
Zone cut to nowhere:
internal.example.com. IN NS .
-
Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).
Zone cut to nowhere:
internal.example.com. IN NS .
-
Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).
Zone cut to nowhere:
internal.example.com. IN NS .
-
Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)
-
Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)
-
Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)
-
Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)
-
Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)
-
#IETF123 in Madrid has been great! I ran an open side-meeting and had many conversations about bringing atproto as work. really appreciate the community for being welcoming and receptive.
-
#IETF123 in Madrid has been great! I ran an open side-meeting and had many conversations about bringing atproto as work. really appreciate the community for being welcoming and receptive.
-
#IETF123 in Madrid has been great! I ran an open side-meeting and had many conversations about bringing atproto as work. really appreciate the community for being welcoming and receptive.
-
#IETF123 in Madrid has been great! I ran an open side-meeting and had many conversations about bringing atproto as work. really appreciate the community for being welcoming and receptive.
-
DNSOP working group: a lot of small (and somestimes not so small) changes to #DNS https://datatracker.ietf.org/meeting/123/materials/agenda-123-dnsop-01
First: persistent references to services you authorize (such as CAA, wallets or also what Bluesky is doing). Related but not identical to TXT-based validation with a cookie/nonce/token in it.
