Episode Info

Episode Info: Episode 14 You may not know it but if you got a new Android phone with your recent T-Mobile contract, you’re running IPv6… natively… most of the time. T-Mobile’s transition solution still needs to accommodate v4 websites and apps that don’t play by the IP rules but over 50% of data flow is happening over native IPv6. In this episode of the IPv6 show I talk with Cameron Byrne about the path he took T-Mobile on to reach IPv6 nirvana and what he learned along the way. Cameron is a Member of the Technical Staff and is Director of Technology at T-Mobile US. He’s been with T-Mobile for 8 years, and is responsible for their end-to-end IP network architecture. Cameron is also the co-author of the IPv6 transition mechanism 464XLAT, which he used in T-Mobile’s transition to IPv6. All the “smart” guys in the room said dual stack was the way to go but Cameron had other ideas. In a mobile environment it was too costly and didn’t make technical sense. So knowing the endgame was IPv6, he set out to find a solution based on a native IPv6 network. The strategy had to be refined along the way, especially for the last 1%. Although it was out of T-Mobile’s control, in the end it was their problem that Skype, Netflix and Spotify didn’t work so further refinement was necessary that led to the 464XLAT translation mechanism.

Episode Info: Episode 14 You may not know it but if you got a new Android phone with your recent T-Mobile contract, you’re running IPv6… natively… most of the time. T-Mobile’s transition solution still needs to accommodate v4 websites and apps that don’t play by the IP rules but over 50% of data flow is happening over native IPv6. In this episode of the IPv6 show I talk with Cameron Byrne about the path he took T-Mobile on to reach IPv6 nirvana and what he learned along the way. Cameron is a Member of the Technical Staff and is Director of Technology at T-Mobile US. He’s been with T-Mobile for 8 years, and is responsible for their end-to-end IP network architecture. Cameron is also the co-author of the IPv6 transition mechanism 464XLAT, which he used in T-Mobile’s transition to IPv6. All the “smart” guys in the room said dual stack was the way to go but Cameron had other ideas. In a mobile environment it was too costly and didn’t make technical sense. So knowing the endgame was IPv6, he set out to find a solution based on a native IPv6 network. The strategy had to be refined along the way, especially for the last 1%. Although it was out of T-Mobile’s control, in the end it was their problem that Skype, Netflix and Spotify didn’t work so further refinement was necessary that led to the 464XLAT translation mechanism. Episode 14 You may not know it but if you got a new Android phone with your recent T-Mobile contract, you’re running IPv6… natively… most of the time. T-Mobile’s transition solution still needs to accommodate v4 websites and apps that don’t play by the IP rules but over 50% of data flow is happening over native IPv6. In this episode of the IPv6 show I talk with Cameron Byrne about the path he took T-Mobile on to reach IPv6 nirvana and what he learned along the way. Cameron is a Member of the Technical Staff and is Director of Technology at T-Mobile US. He’s been with T-Mobile for 8 years, and is responsible for their end-to-end IP network architecture. Cameron is also the co-author of the IPv6 transition mechanism 464XLAT, which he used in T-Mobile’s transition to IPv6. All the “smart” guys in the room said dual stack was the way to go but Cameron had other ideas. In a mobile environment it was too costly and didn’t make technical sense. So knowing the endgame was IPv6, he set out to find a solution based on a native IPv6 network. The strategy had to be refined along the way, especially for the last 1%. Although it was out of T-Mobile’s control, in the end it was their problem that Skype, Netflix and Spotify didn’t work so further refinement was necessary that led to the 464XLAT translation mechanism. Read less

Discover more stories like this. Like Stitcher On Facebook