-=> Michiel van der Vlist wrote to Tony Langdon <=-   
      
    MvV> For starters: 30% of the nodes in my list of IPv6 capable nodes still   
    MvV> connect via a tunnel. Setting uo a tunnel certainly requires taking   
    MvV> active steps.   
      
   True.   
      
    TL> IPv6 may not be automatically enabled in some Fido software (that   
    TL> supports it). Network wise, it depends on your ISP.  Mine enables IPv6   
    TL> by default and all of the routers they provide support IPv6 out of the   
    TL> box, so at the network level it should "just work".   
      
    MvV> Your ISp is a pioneer. Many ISPs around the world are still dragging   
    MvV> their feet. So " just work" is still the exception rather than te rule.   
      
   Yes, now you know why I chose them!  :-)   
      
    MvV> I have native Dual Stack now for over a year, but my ISP is also one of   
    MvV> the slow ones. Plus that now their policy is to go DS -Light. New   
    MvV> customers get DS-Light. On request they can be converted ti IPv4 only.   
    MvV> That is another spoke in the whell of "just work".   
      
   I've just got to 7 years of native dual stack here.   
      
    MvV>> Same here. Plus that when adding new links and having to make a   
    MvV>> choice, I prefer to link to the IPv6 capable node over linking   
    MvV>> to the IPv4 only node.   
      
    TL> Me too, I think around 50% of my upstream links have IPv6 here.   
      
    MvV> Same here, around 50%. In future, I may even drop some IPv4 only links   
    MvV> to up the percentage. ;-)   
      
   That's not an option, the IPv4 uplinks are sole providers for othernets. :)    
   While I'm a big supporter of IPv6, it's not the hill I choose to die on. :)   
      
      
   ... Real knowledge is to know the extent of ones ignorance.   
   === MultiMail/Win32 v0.49   
   --- SBBSecho 3.03-Linux   
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)