Jad El Cham - 2024-05-23 10:53:23
Hi everyone, I'm Jad El Cham from the RIPE NCC. This chat panel is meant for discussion ONLY. If you have questions for the speaker and you want the session chair to read it out, please write it in the Q&A window also stating your affiliation. Otherwise, you can ask questions using the microphone icon.
Please note that all chat transcripts will be archived and made available to the public at https://ripe88.ripe.net/.
The RIPE Code of Conduct: https://www.ripe.net/publications/docs/ripe-766/.
Sebastian Wiesinger - 2024-05-23 11:03:10
👏
Shane Kerr - 2024-05-23 11:45:06
But we need a routing protocol with link costs to do cool low-carbon routing! BGP fails as an internal routing protocol. 😉
Nico Braud-Santoni - 2024-05-23 11:57:14
OK, the completely normal thing. I was confused, as this had worked OotB in my testbed
Nico Braud-Santoni - 2024-05-23 11:58:12
+1 on documentation prefixes, that really ought to be the normal thing to do
Shane Kerr - 2024-05-23 11:59:46
"It's not a protocol, it's just routing." 😆
Jen Linkova - 2024-05-23 12:00:17
What do you mean "nobody using documentation prefixes"?? :) I do! :)))
Shane Kerr - 2024-05-23 12:00:27
Same!
Sebastian Wiesinger - 2024-05-23 12:03:10
Lucky persons
Venu Gopal Kakarla - 2024-05-23 12:15:58
If you want to "drive down cost", why not deploy ipv6
Siyuan Miao - 2024-05-23 12:20:30
It may still save money, the negative cache may have a lower TTL. By setting the AAAA record, the resolvers can actually cache the response and maybe honor the TTL you set?
Jad El Cham - 2024-05-23 12:22:03
Hi Siyuan, please write your question in the Q&A panel, or please wait until the end of the talk and ask your question using audio. Thank you!
Siyuan Miao - 2024-05-23 12:23:04
Ah nvm Alexander already expressed the same idea :-D
Jad El Cham - 2024-05-23 12:30:03
This session has now ended. The next session is Open Source and it will start at 14:00 (UTC+2). More info on the RIPE 88 meeting plan: https://ripe88.ripe.net/programme/meeting-plan/
