This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
- Previous message (by thread): [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
- Next message (by thread): [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Uros Gaber
uros at ub330.net
Thu May 14 15:01:10 CEST 2020
Hi all, as a developer I can say with some confidence, that a big hurdle is to use hostname instead of IPs, it's way simpler to use IP during development than to use hostname where you have to configure DNS record to do so. And this has the underlying problem in large development setups where the single developer or the single developer group can not (due to internal rules) simply change / configure DNS records. Re, Uros On Thu, May 14, 2020 at 2:37 PM Wilhelm Boeddinghaus <wilhelm at boeddinghaus.de> wrote: > > Hi folks, > > my DSL line broke, and it is still offline :-( > > Thanks for listening and asking quesions. > > I try to answer the questions below. > > App Developers try to avoid IPv6, I know. We cannot force them to use IPv6. But we have to force them to use libraries that work with IPv6 and IPv4, not some old stuff useing IPv4 only. Then there is golden rule: no IP addresses in code or config files, use names > > I they at least stay to this, there is hope. You can then enable IPv6 later without recoding the app. > > > SLAAC and DHCPv6 > > SLAAC (the RA) triggers DHCP, we need both. DHCPv6 is the excuse to stay in the old IPv4 network design. Large L2 networks (broadcast and failure domain) with VRRP (HSRP) and Dualstack. I would rather try to get rid of DHCPv6. > > I think we will have no DHCPv6 on Android (you refer that, don`t you) in the near future, so we have to use SLAAC to get IPv6 addresses to those devices. And don't forget, there is no default route in DHCPv6. > > Best, > > Wilhelm > > Am 14.05.2020 um 13:58 schrieb Jetten Raymond: > > Hello All, > > > > Thank you all for watching the IPv6 WG virtually, > > > > at the latest minutes of Wilhelms presentation Q&A his dsl connection unfortunately went down, > > > > there were still some questions in the buffer, could you Wilhelm comment yet on these ? > > > > > > > > Any tips to get app developers on board to develop IPv6 enabled apps? It’s not uncommon for companies to exclude IPv6 from minimum viable product as its “too hard” > > > > > > > > > > > > Could disabling SLAAC and better DHCPv6 support (eg in mobile devices) help the deployment? It would help with some migrations from IPv4 to IPv6 I think. (Mark Scholten / asking for myself) > > > > > > Rgds, > > > > Ray > > > > > For Internal Use Only
- Previous message (by thread): [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
- Next message (by thread): [ipv6-wg] RIPE 80 IPv6 wg session Wilhelms DSL broke, some unanswered questions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]