From owner-freebsd-current Wed Sep 25 13:22:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07958 for current-outgoing; Wed, 25 Sep 1996 13:22:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07853; Wed, 25 Sep 1996 13:22:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA06603; Wed, 25 Sep 1996 13:19:31 -0700 From: Terry Lambert Message-Id: <199609252019.NAA06603@phaeton.artisoft.com> Subject: Re: Licensing Software To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 25 Sep 1996 13:19:30 -0700 (MST) Cc: terry@lambert.org, wollman@lcs.mit.edu, jhs@FreeBSD.org, current@FreeBSD.org, commercial@FreeBSD.org In-Reply-To: <199609252002.PAA08640@brasil.moneng.mei.com> from "Joe Greco" at Sep 25, 96 03:02:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > One of the biggest barriers to IPv6 transition? I don't think so; > > why would it be a barrier? > > One of the biggest barriers to IPv6 is the people who are going to cling > to their IPv4 IP addresses for reasons such as legacy license servers. > > (I don't know if that is true or not, but I suspect it is more true than > not)... I think that was what he was sayin'. Then IPv6 is already screwed, isn't it, and a general soloution to the problem for all systems will solve it for FreeBSD at the same time. This is a non-problem. > > Flexible renumbering in general? Yes, I'll admit it's a barrier > > to flexible renumbering. Under what circumstances would you want > > to allow a license host to "flexibly renumber"? To hide the > > licenses from Billy-Bob? It makes no sense. > > When the customer is assigned an address block out of an ISP's CIDR block > and wants to change ISP's because the old ISP is out of business? IPv6 solves this problem by making my address ranges independent of my ISP/NSP: the address range is sufficiently enlarged, I can get a range assignment of my own. > There is a definite need to be able to flexibly renumber. There's a need for a lot of things which somply aren't being addressed, or less simply, are being purposely ignored. > > de0: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:80:48:e8:1b:b1 > > ----------------------------------------------------***************** > > de0: enabling 10baseT/UTP port > > Of course, when you switch Ethernet cards, you are screwed. So: A) Either: Don't switch ethernet cards B) Or: accept that as part of the overhead associated with switching ethernet cards, and make the decision, when you make it, after taking that fact into account > Although I will tend to think that's a better solution than IP address :-) Bleah. Show me a functioning IPv6 network where the variant portion of the address can't be ignored to achieve the same effect as using IP addresses. > The PC isn't suited to this. It has no hardware to do it. And even on > machines where there is hardware to do it, node locked licenses suck. And even where they don't, you can "spoof" the hardware by trapping the user mode programs access to the kernel mode dongle driver, and lying. So even a hardware soloution -- isn't. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.