• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Software and IPv6
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Software and IPv6


  • Subject: Re: Software and IPv6
  • From: Ragnar Sundblad <email@hidden>
  • Date: Wed, 7 Jun 2006 11:29:45 +0200


On 7 jun 2006, at 01.40, Michael Bartosh wrote:


On Jun 6, 2006, at 11:25 PM, Ragnar Sundblad wrote:

Other than QA, are there any development issues that would
prevent people from making their software IPv6 ready?

Well, since there are so many programs out there that work perfectly well with ipv6, it is hard to think of any real show stoppers.

I can think of two major examples.

In certain circumstances, an IPv6 address can get embedded in a user's
AuthAuthorty. In most cases, IPv6 is not actually routed by most of my
customers (including a great many fortune 1000 companies), and if the
Password Server is on another subnet, users can't authenticate.

Ok, that sounds like an unfortunate bug, but that doesn't really have to do anything with preventing people from creating ipv6 ready software, has it?

In Panther, ipfw didn't understand IPv6. So 6 connections could get
around any firewall rules.

That may be right, maybe the ipfw stuff lagged in ipv6 support. Well, since "firewalling" is the opposite of networking, it is maybe just natural that they don't follow. Just don't use that kind of destruction software and you will be a happy camper.

Both of these are mostly fixed now, but this illustrates a trend of 6 not being taken into account by developers.

Trend? There were two issues, were the first is a potential problem for everyone that could have working ipv4 but not v6 to their password server (which is in many, to not say the most, places on the internet) and therefore is an obvious bug, which you btw say is fixed now, and the other is just a single example of a piece of software that lagged ipv6 support, which incidentally is the kind of software that is made and used for destroying connectivity, not for supporting it.

There are a zillion things that Just Work and does so well, on
most OSes. Where did those go in that trend analysis?

So unless the networking personnel I'm working with are actually using 6 I always make sure it's turned off on the Mac.

Well, I think it is very uncommon to turn it off, and those machines still work for people. I'd recommend not to turn it off.

Maybe your turning it off is why you fell that it doesn't work?
It does, just use it and hope to forget about it.

/ragge

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Software and IPv6
      • From: Michael Bartosh <email@hidden>
References: 
 >Re: Software and IPv6 (From: Ragnar Sundblad <email@hidden>)
 >Re: Software and IPv6 (From: Michael Bartosh <email@hidden>)

  • Prev by Date: Re: Software and IPv6
  • Next by Date: Compile/Install/Launch DSS
  • Previous by thread: Re: Software and IPv6
  • Next by thread: Re: Software and IPv6
  • Index(es):
    • Date
    • Thread