 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Nicolas Alvarez wrote:
> How is that a "current" event?
How about Dr Jarvik.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
> Invisible wrote:
>> Right. My point was that if companies are just left to their own
>> devices, they will all invent and deploy incompatible technologies.
>
> Not really. One network will be bigger, and others will make their stuff
> compatible so they can connect to the network. Or you build interface
> converters.
Or you have the network equivilent of "format wars" while the few
biggest networks try to out-grow each other and win the game...
> Wow, good thing the internet uses ethernet everywhere, and we never had
> these dial-up modems, ADSL, or cable modems to deal with.
Fortunately, somebody invented IP. Before that happened, it was crazy
out there...
>> For something like washing machines, the fact that one machine is
>> "incompatible" with another is largely irrelevant. For anything which
>> could be described as a "network", compatibility is usually a Big Deal.
>
> Which is exactly why the companies tend not to deploy incompatible
> technologies, once a sufficiently good technology has proven itself.
Really? How would company X know that company Y is using a given technology?
> The main reason the telephone networks in the USA were monopolies is
> they were analog, and you had to carefully design the routing so that
> long distance calls didn't go thru so many switches that you lost all
> quality.
Similar constraints probably apply to things like water or electricity
distribution.
>> The other problem is assigned numbers. Can you imagine if there were
>> three different postal services, each of which assigns completely
>> different postcodes to the same addresses?
>
> FedEx and UPS and GPS driving directions and such all use the postal
> address. Why wouldn't they? Why would UPS go to the trouble of making up
> their own sets of addresses?
Yeah, because the postal address already existed in the first place. If
the post office hadn't existed first...
>> Even if the format of a
>> postcode is standardised, you still need a single entity to assign them.
>
> Because ethernet MAC addresses and worldwide telephone numbers are all
> managed by the same entity.
?
>> (Still, I guess it's plausible that you could have a single entity in
>> charge of *planning* a service, and have the service actually
>> *performed* by several independant companies...)
>
> Hey, welcome to Bellcore. Have a nice visit.
Um... OK?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Similar arguments go for things like power distribution, or rail
>> networks.
>
> Rail networks aren't a monopoly. They didn't even have compatible rails
> for a long time, since it wasn't really that much of a problem to switch
> cars.
In which country?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott wrote:
> When I was a child my computer had booted before the picture came on :-)
Heh. Makes me chuckle when I think about how many seconds it takes for a
C64 to bootstrap.
About 0.2.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> Or you have the network equivilent of "format wars" while the few
> biggest networks try to out-grow each other and win the game...
Yep. But again that's going to win/lose on lots of features, one of which is
how well the formats match what people want at the time.
The sad part is when a format gets entrenched and then people change how the
work to a way that the entrenched mechanisms don't support well.
> Fortunately, somebody invented IP. Before that happened, it was crazy
> out there...
Not especially. And IP didn't win. IP addresses a very small part of the
networking stack. X.25 was around first, and had nationwide networks
interconnected before IP was around. There was ISDN, SNA, and DecNet, and
that was pretty much it.
Now there's SONET and ATM, which is what carries most IP traffic.
> Really? How would company X know that company Y is using a given
> technology?
I'm pretty sure it's not hard to figure out what technology your
competition in network services is using. You think it's difficult to figure
out what coding an iPhone uses over the air, for example?
> Similar constraints probably apply to things like water or electricity
> distribution.
Yes. Around here at least, it's space underneath the roads to actually run
the pipes. Indeed, a huge amount of network monopoly power comes from
having access to the land to run the network. That's why telegraph
companies were all owned by railroads.
> Yeah, because the postal address already existed in the first place. If
> the post office hadn't existed first...
Exactly, yes. But not because the post office was a monopoly.
>>> Even if the format of a
>>> postcode is standardised, you still need a single entity to assign them.
>>
>> Because ethernet MAC addresses and worldwide telephone numbers are all
>> managed by the same entity.
>
> ?
Why would post codes need a monopoly if phone numbers, IP addresses, and MAC
addresses don't?
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
>>> Similar arguments go for things like power distribution, or rail
>>> networks.
>>
>> Rail networks aren't a monopoly. They didn't even have compatible
>> rails for a long time, since it wasn't really that much of a problem
>> to switch cars.
>
> In which country?
The USA.
Anyone who builds a large network after there's already a clear winner
somewhere else is likely to adopt the same standards, or at least recognise
that there's going to be a need for standards.
Did the UK have analog cell phones, out of curiousity?
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> scott wrote:
>
>> When I was a child my computer had booted before the picture came on :-)
>
> Heh. Makes me chuckle when I think about how many seconds it takes for a
> C64 to bootstrap.
>
> About 0.2.
Yeah, it astounded a friend of mine who was a VAX-head when I hit the reset
switch on the back of a Kaypro CP/M machine. "Was that an interrupt? That
was quick." "No, that was a cold boot."
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 <voi### [at] dev null> wrote:
> Heh. Makes me chuckle when I think about how many seconds it takes for a
> C64 to bootstrap.
> About 0.2.
Yeah, with all that hardware it has to initialize and the boot loaders it
has to load from hard disks, it's a miracle.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Or you have the network equivilent of "format wars" while the few
>> biggest networks try to out-grow each other and win the game...
>
> Yep. But again that's going to win/lose on lots of features, one of
> which is how well the formats match what people want at the time.
>
> The sad part is when a format gets entrenched and then people change how
> the work to a way that the entrenched mechanisms don't support well.
The sad part is that the format that wins is usually the least
technically sophisticated.
>> Fortunately, somebody invented IP. Before that happened, it was crazy
>> out there...
>
> Not especially. And IP didn't win. IP addresses a very small part of the
> networking stack.
What IP does is provide a single language for networking. Any networking
technology that has a standardised way of carrying IP can potentially be
interconnected with any other such technology.
IP over Avian Carrier, anyone?
From what little I remember, before that we had IPX and SPX and
AppleTalk and Ethernet and Token Ring and none of it worked together.
>> Really? How would company X know that company Y is using a given
>> technology?
>
> I'm pretty sure it's not hard to figure out what technology your
> competition in network services is using. You think it's difficult to
> figure out what coding an iPhone uses over the air, for example?
Er, YES. (?!)
>> Similar constraints probably apply to things like water or electricity
>> distribution.
>
> Yes. Around here at least, it's space underneath the roads to actually
> run the pipes.
Yeah, that wouldn't surprise me...
And besides, why waste time and energy laying a dozen sets of cables
when one will do?
>> Yeah, because the postal address already existed in the first place.
>> If the post office hadn't existed first...
>
> Exactly, yes. But not because the post office was a monopoly.
So if the post office hadn't been a monopoly, and there had been a dozen
different postal companies all start at the same time, they would have
all used the same postcodes?
> Why would post codes need a monopoly if phone numbers, IP addresses, and
> MAC addresses don't?
Are you telling me that IP addresses don't involve a monopoly?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
> Did the UK have analog cell phones, out of curiousity?
Uh... I *think* so. For a while, at least. But back then, only rich
playboy execs could afford them. (And they were *huge* anyway...)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Thu, 13 May 2010 20:09:00 +0100, Orchid XP v8 wrote:
> The sad part is that the format that wins is usually the least
> technically sophisticated.
Actually, that's quite pragmatic more than sad; often you find that the
requirements come down to the lowest common denominator. Implementing
things that are more esoteric tend to not happen because they aren't
likely to be widely utilized.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> What IP does is provide a single language for networking.
So does every network. And the IP stack doesn't support all sorts of stuff
that other networks do. You're just expressing a tautology.
> Any networking
> technology that has a standardised way of carrying IP can potentially be
> interconnected with any other such technology.
And any networking technology that has a standardized way of carrying SONET
can be interconnected with any other such technology. Any networking
technology that has a standardized way of carrying ISDN can be
interconnected with any other such technology. Any networking ... X.25 ...
Etc etc etc.
> From what little I remember, before that we had IPX and SPX and
> AppleTalk and Ethernet and Token Ring and none of it worked together.
Yet, at the same time we had X.25, voice dialing over *analog connections*
using *human beings* as routers worked just fine worldwide.
Something which IP still doesn't support well. Along with roaming. And
address portability.
> And besides, why waste time and energy laying a dozen sets of cables
> when one will do?
Money. Why waste time and energy with multiple search engines?
> So if the post office hadn't been a monopoly, and there had been a dozen
> different postal companies all start at the same time, they would have
> all used the same postcodes?
No. But over a fairly short time, that would have sorted itself out.
>> Why would post codes need a monopoly if phone numbers, IP addresses,
>> and MAC addresses don't?
>
> Are you telling me that IP addresses don't involve a monopoly?
Yes. Who served the IP address to your machine? Time Warner San Diego? I
doubt it.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> The sad part is that the format that wins is usually the least
> technically sophisticated.
Oh, and this is also wrong. It's just that the technology that gets picked
isn't always emphasizing the qualities you want.
GSM is inferior technologically to CDMA. But what people *want* is that SIM
card, and the ability to roam easily, so enforcing a standard with a lower
technological quality earlier is better than waiting for the best invention
before standardizing.
If you're talking about the VCR tapes, VHS was technically superior in
recording time, while BetaMax was technically superior in picture quality.
Niether was inferior to the other per se.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Orchid XP v8 <voi### [at] dev null> wrote:
>> Heh. Makes me chuckle when I think about how many seconds it takes for a
>> C64 to bootstrap.
>
>> About 0.2.
>
> Yeah, with all that hardware it has to initialize and the boot loaders it
> has to load from hard disks, it's a miracle.
What, that it takes as long as 200 ms, and not 20 ms? ;-)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> The sad part is that the format that wins is usually the least
>> technically sophisticated.
>
> Actually, that's quite pragmatic more than sad; often you find that the
> requirements come down to the lowest common denominator. Implementing
> things that are more esoteric tend to not happen because they aren't
> likely to be widely utilized.
I'm thinking about things like VHS vs Betamax. One has automatic
tracking, the other needlessly forces you to do it manually. Guess which
one won?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> What IP does is provide a single language for networking.
>
> So does every network. And the IP stack doesn't support all sorts of
> stuff that other networks do. You're just expressing a tautology.
>
>> Any networking technology that has a standardised way of carrying IP
>> can potentially be interconnected with any other such technology.
>
> And any networking technology that has a standardized way of carrying
> SONET can be interconnected with any other such technology. Any
> networking technology that has a standardized way of carrying ISDN can
> be interconnected with any other such technology. Any networking ...
> X.25 ... Etc etc etc.
Take token ring, for example. Token ring is inherantly designed around
the idea that you will only be connecting, say, maybe 100 nodes
together. Nodes are referred to by their position in the ring; add a new
node and all the addresses change. You can't even connect a token ring
to another token ring, never mind any other type of technology. It
doesn't work.
IP is different. It's designed to work for large networks.
>> So if the post office hadn't been a monopoly, and there had been a
>> dozen different postal companies all start at the same time, they
>> would have all used the same postcodes?
>
> No. But over a fairly short time, that would have sorted itself out.
Oh yeah? You recon??
>>> Why would post codes need a monopoly if phone numbers, IP addresses,
>>> and MAC addresses don't?
>>
>> Are you telling me that IP addresses don't involve a monopoly?
>
> Yes. Who served the IP address to your machine? Time Warner San Diego?
> I doubt it.
AFAIK, IP addresses are assigned by a central allocation agency.
Sure, you don't usually talk to them directly; usually you use one of
the IP addresses from the block assigned to your ISP. But my point is,
you can't just pick a random number out of the air and try to use that
as your IP address. It won't work.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> The sad part is that the format that wins is usually the least
>> technically sophisticated.
>
> Oh, and this is also wrong. It's just that the technology that gets
> picked isn't always emphasizing the qualities you want.
You mean qualities like cheapness, design simplicity, ability to force
people to pay more money for it, that kinda thing?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 5/14/2010 3:08 AM, Invisible wrote:
>
> I'm thinking about things like VHS vs Betamax. One has automatic
> tracking, the other needlessly forces you to do it manually. Guess which
> one won?
Would it not be easier to implement manual tracking at a slight
inconvenience to the user?
Of course, that's not why beta lost out. We all know the real reason
why... (hint: it's the reason the internet got so popular...)
--
~Mike
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 5/13/2010 1:57 PM, Darren New wrote:
> Yeah, it astounded a friend of mine who was a VAX-head when I hit the
> reset switch on the back of a Kaypro CP/M machine. "Was that an
> interrupt? That was quick." "No, that was a cold boot."
Your Kaypro had a reset switch? Ours only had a power switch. I didn't
do much with it at the time, but I do remember fondly a game that came
on it called Ladder, The game was entirely in text mode.
A friend of mine and I both wrote independent copies of the game on our
respective PC platforms. His was a Tandy1000 mine was a PC-XT clone.
Interestingly, his had a couple problems:
He double-buffered the screen, which was fine on the Tandy, but due to
the design of the CGA on the XT, when the program flipped pages it would
cause interminable snow.
With my version I only erased what changed and redrew it. Flicker wasn't
apparent. His would keep an empty copy of the background, then draw the
characters on it.
The collision detection on his version had a minor bug: if you
approached a block at the correct angle, it would fail to detect it and
your character would become stuck in that block. Mine didn't do that.
In other ways, his was vastly superior to mine. He had actually coded
enemies. Mine was more of a puzzle you had to work through.
I wish I still had program... was written entirely in QuickBasic.
--
~Mike
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 09:08:42 +0100, Invisible wrote:
>>> The sad part is that the format that wins is usually the least
>>> technically sophisticated.
>>
>> Actually, that's quite pragmatic more than sad; often you find that the
>> requirements come down to the lowest common denominator. Implementing
>> things that are more esoteric tend to not happen because they aren't
>> likely to be widely utilized.
>
> I'm thinking about things like VHS vs Betamax. One has automatic
> tracking, the other needlessly forces you to do it manually. Guess which
> one won?
The one that had the largest adoption by the consuming public.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> I'm thinking about things like VHS vs Betamax. One has automatic
> tracking, the other needlessly forces you to do it manually. Guess which
> one won?
VHS, because it actually had the playing time people wanted.
Guess what? People use wireless instead of wired ethernet, even tho wired
ethernet is at least twice as fast and possible 20x depending on which kind
of wire you use. Don't you hate when these crappy products like wireless
networking win out over real speed?
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> IP is different. It's designed to work for large networks.
And SONET and ATM and X.25 and ISDN aren't? Do you even know what those
networks are?
Here's a hint: When you phone America from the UK, your voice is not
traveling over IP. Heck, the busy signal isn't traveling over IP either.
>> No. But over a fairly short time, that would have sorted itself out.
> Oh yeah? You recon??
Just like pretty much every other group of competing networking technologies.
> Sure, you don't usually talk to them directly; usually you use one of
> the IP addresses from the block assigned to your ISP.
Ding ding! Guess what? They aren't assigned centrally. Your ISP assined you
yours, mine assigned me mine.
> But my point is,
> you can't just pick a random number out of the air and try to use that
> as your IP address. It won't work.
That's a different statement from "they're assigned centrally."
And yes, actually, you can. You'll break other people, but it'll work if you
do it right.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
> Invisible wrote:
>> IP is different. It's designed to work for large networks.
>
> And SONET and ATM and X.25 and ISDN aren't? Do you even know what those
> networks are?
Last time I checked, ISDN is point-to-point only (i.e., the smallest
possible kind of network). I was under the impression that ATM is as
well, but I haven't actually used ATM.
> Here's a hint: When you phone America from the UK, your voice is not
> traveling over IP. Heck, the busy signal isn't traveling over IP either.
I try to avoid phoning America. It's almost impossible to hear what the
other person is saying. (Why this would be the case in a digital system
is beyond me...)
>> Sure, you don't usually talk to them directly; usually you use one of
>> the IP addresses from the block assigned to your ISP.
>
> Ding ding! Guess what? They aren't assigned centrally. Your ISP assined
> you yours, mine assigned me mine.
And where does the ISP get their IP block from?
Yeah, exactly: They're assigned centrally.
>> But my point is,
>> you can't just pick a random number out of the air and try to use that
>> as your IP address. It won't work.
>
> That's a different statement from "they're assigned centrally."
>
> And yes, actually, you can. You'll break other people, but it'll work if
> you do it right.
If I just pick an IP address at random, it won't even route correctly.
Oh, sure, if I'm building a *private* network not connected to anything
else, I can use whatever addresses I want. (Hell, I don't even have to
use IP.) But then everybody on *that* network needs centrally-assigned
addresses...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Mike Raiford wrote:
> Your Kaypro had a reset switch? Ours only had a power switch.
The Dell PCs I have at work don't even have a power switch.
If one of them crashes, you have to unplug it from the wall to turn it
off...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> Last time I checked, ISDN is point-to-point only
So is TCP. It's connection-oriented, except for the D-channel, which is
datagram oriented.
> (i.e., the smallest possible kind of network).
Yet, oddly enough, orders of magnitude bigger than IP.
> I was under the impression that ATM is as
> well, but I haven't actually used ATM.
Tell me what you mean by "point to point" if you think IP isn't.
>>> Sure, you don't usually talk to them directly; usually you use one of
>>> the IP addresses from the block assigned to your ISP.
>>
>> Ding ding! Guess what? They aren't assigned centrally. Your ISP
>> assined you yours, mine assigned me mine.
>
> And where does the ISP get their IP block from?
>
> Yeah, exactly: They're assigned centrally.
Nope. They're assigned heirarchically. That's completely different.
> If I just pick an IP address at random, it won't even route correctly.
Of course you have to adjust the routing.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 12:38:52 -0700, Darren New wrote:
> Tell me what you mean by "point to point" if you think IP isn't.
Arguably, IP multicast (or broadcast for that matter) isn't point-to-
point.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Arguably, IP multicast (or broadcast for that matter) isn't point-to-
> point.
Except that only works on a LAN. Otherwise, it's the routers duplicating the
packets to every output. I.e., the same as conference calling.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 13:10:32 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Arguably, IP multicast (or broadcast for that matter) isn't point-to-
>> point.
>
> Except that only works on a LAN. Otherwise, it's the routers duplicating
> the packets to every output. I.e., the same as conference calling.
Depends on how the router implements forwarding for multicast - ISTR that
some routers can be configured to forward multicast traffic up to a
specified TTL, but what's forwarded is still multicast traffic.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 5/14/2010 1:12 AM, Invisible wrote:
>> Yes. Who served the IP address to your machine? Time Warner San Diego?
>> I doubt it.
>
> AFAIK, IP addresses are assigned by a central allocation agency.
>
> Sure, you don't usually talk to them directly; usually you use one of
> the IP addresses from the block assigned to your ISP. But my point is,
> you can't just pick a random number out of the air and try to use that
> as your IP address. It won't work.
Mind, in principle, IPV6 could have each "device" us its own IP, kind of
like routing to you via MAC address. But.. In a practical sense, its
still the same DNS system being used for it.
--
void main () {
If Schrödingers_cat is alive or version > 98 {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le 14/05/2010 18:37, Darren New nous fit lire :
> Invisible wrote:
>> IP is different. It's designed to work for large networks.
>
> And SONET and ATM and X.25 and ISDN aren't? Do you even know what those
> networks are?
I'm feeling fear... I know them all...
SDH should be cited with SONET if you go that way!
IP is not designed for large networks of today.
It has been designed for hierarchy of networks.
Getting ride of classes was just one way to avoid doomsday for a time.
Address allocation was always done by delegation along the hierarchical
path...
Then came NAT... but it won't stand long either.
>> Sure, you don't usually talk to them directly; usually you use one of
>> the IP addresses from the block assigned to your ISP.
>
> Ding ding! Guess what? They aren't assigned centrally. Your ISP assined
> you yours, mine assigned me mine.
>
Rejoice, the end of IPv4 addresses is coming... less than 1 year of
available blocs for some continents... 2 years for the lucky ones!
Get your visa & mastercard ready to pay for a routable ipv4 if ipv6 does
not happens transparently for joe-user and you want a public server!
>> But my point is,
>> you can't just pick a random number out of the air and try to use that
>> as your IP address. It won't work.
>
> That's a different statement from "they're assigned centrally."
>
> And yes, actually, you can. You'll break other people, but it'll work if
> you do it right.
>
What is worst with IP: every interface of a system need one, not the
system itself, but every interface! You do not try to reach a system,
but a door to that system... and the same door number can be reused by
others... lame!
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 13:53:14 -0700, Patrick Elliott wrote:
> On 5/14/2010 1:12 AM, Invisible wrote:
>>> Yes. Who served the IP address to your machine? Time Warner San Diego?
>>> I doubt it.
>>
>> AFAIK, IP addresses are assigned by a central allocation agency.
>>
>> Sure, you don't usually talk to them directly; usually you use one of
>> the IP addresses from the block assigned to your ISP. But my point is,
>> you can't just pick a random number out of the air and try to use that
>> as your IP address. It won't work.
> Mind, in principle, IPV6 could have each "device" us its own IP, kind of
> like routing to you via MAC address. But.. In a practical sense, its
> still the same DNS system being used for it.
That's one of the nice features of IPv6 (taken from IPX, actually, from
what I've read, that essentially did the same thing).
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Depends on how the router implements forwarding for multicast - ISTR that
> some routers can be configured to forward multicast traffic up to a
> specified TTL, but what's forwarded is still multicast traffic.
Yes. And if you have a router with three ethernet connections plugged into
it, it's going to duplicate each multicast packet onto each ethernet
connection. Otherwise it isn't multicast.
The whole multicast protocol is nothing more than telling each router on the
path which outputs it needs to duplicate packets on to, so you *don't* get
multicast going onto network segments where nobody is listening for them.
Of course when it's duplicated it's still a multicast packet. That's defined
by the source address, and on any given segment that supports broadcast it
is treated as a broadcast packet. It's still point-to-point between routers.
I.e., it's still point to point if you treat "all the people listening to
the same broadcast address on the same network segment" as one point of the
multicast transmission.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Depends on how the router implements forwarding for multicast
Or, to phrase it differently, multicast is somewhat more point-to-point than
a telephone party line is.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 15:36:09 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Depends on how the router implements forwarding for multicast
>
> Or, to phrase it differently, multicast is somewhat more point-to-point
> than a telephone party line is.
Not really, a party line is many-to-many, but multicast is one-to-many.
The routers act as repeaters, but still operate a multicast "domain" (if
you will) within their local network, as long as there's a client that
has registered with the router to listen in on the multicast.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 15:30:22 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Depends on how the router implements forwarding for multicast - ISTR
>> that some routers can be configured to forward multicast traffic up to
>> a specified TTL, but what's forwarded is still multicast traffic.
>
> Yes. And if you have a router with three ethernet connections plugged
> into it, it's going to duplicate each multicast packet onto each
> ethernet connection. Otherwise it isn't multicast.
Assuming the switch isn't multicast aware. I wouldn't be surprised if
some were these days (but I haven't looked at it recently).
> The whole multicast protocol is nothing more than telling each router on
> the path which outputs it needs to duplicate packets on to, so you
> *don't* get multicast going onto network segments where nobody is
> listening for them.
Right.
> Of course when it's duplicated it's still a multicast packet. That's
> defined by the source address, and on any given segment that supports
> broadcast it is treated as a broadcast packet. It's still point-to-point
> between routers. I.e., it's still point to point if you treat "all the
> people listening to the same broadcast address on the same network
> segment" as one point of the multicast transmission.
It's more like multiple people listening to a radio station - the data is
only transmitted once per subnet. The difference between, for example,
using unicast to push an image down to 15 workstations on a subnet and
using multicast to push an image down to 15 workstations on a subnet is a
significant reduction in overall network traffic.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 05/12/10 23:50, Stephen wrote:
> On 13/05/2010 7:34 AM, Neeum Zawan wrote:
>> On 05/11/10 05:45, Mike Raiford wrote:
>>>>> Or Carl Sagan, for that matter.
>>>>
>>>> Who?
>>>>
>>>
>>> Inventor of the communications satellite, physicist, cosmologist ... and
>>> sci-fi writer....
>>
>> Communications Satellite?
>>
>> Methinks you have two writers mixed up.
>>
>> And he sucked as a sci-fi writer.
>>
> Sir Arthur would agree. ;-)
I'm sure he'd be a bit more elegant in the phrasing.
--
All hope abandon, ye who enter messages here.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Assuming the switch isn't multicast aware. I wouldn't be surprised if
> some were these days (but I haven't looked at it recently).
Um, no. Even so.
If you have one cable coming into the university campus, and a network for
each building, the router is going to have to send the packets to each
building, duplicating the packets, regardless of how "aware" anyone is.
> It's more like multiple people listening to a radio station - the data is
> only transmitted once per subnet.
Right. But you have to duplicate it for each subnet, which is the "party
line" equivalent.
> The difference between, for example,
> using unicast to push an image down to 15 workstations on a subnet and
> using multicast to push an image down to 15 workstations on a subnet is a
> significant reduction in overall network traffic.
Only for that one subnet.
It's better than a unicast stream to each destination, yes. That doesn't
mean IP isn't point-to-point, if you factor in the broadcast address as
meaning "one subnet is the point."
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Not really, a party line is many-to-many,
Er, not really, no. A party line is one switch to many phones.
> The routers act as repeaters, but still operate a multicast "domain" (if
> you will) within their local network, as long as there's a client that
> has registered with the router to listen in on the multicast.
Yes, I know how it works. Now we're just arguing over analogies.
My point is that it's *not* like a radio broadcast. It's point-to-point
between routers. The only place you're saving bandwidth is on subnets.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le_Forgeron wrote:
> Rejoice, the end of IPv4 addresses is coming... less than 1 year of
> available blocs for some continents... 2 years for the lucky ones!
>
> Get your visa & mastercard ready to pay for a routable ipv4 if ipv6 does
> not happens transparently for joe-user and you want a public server!
That's why I spent the last few days adding IPv6 support to some C++ code
that uses BSD sockets directly :/
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Nicolas Alvarez wrote:
> That's why I spent the last few days adding IPv6 support to some C++ code
> that uses BSD sockets directly :/
Oh, I have joy at work. The resolver on the work box I'm supposed to be
programming is happy to return IPv6 addresses for names in /etc/hosts, even
tho there's no IPv6 in the network stack. It's really quite the PITA.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Not really, a party line is many-to-many, but multicast is one-to-many.
If someone in a multicast domain sends a multicast packet, it'll go to
everyone on the LAN and downstream from there.
But the real answer is that IP multicast doesn't describe how to route the
packet other than point to point. IP multicast is between routers. The
mechanism for getting from the last router to the individual host clients
isn't specified and depends on the underlying technology. If the underlying
network between client machines on the subnet doesn't do true broadcasting,
you're going to wind up repeating the packet on the subnets too.
So it's not really a valid comparison. IP broadcast only works when the
underlying network supports it, so it's still point to point.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Last time I checked, ISDN is point-to-point only
>
> So is TCP. It's connection-oriented, except for the D-channel, which is
> datagram oriented.
My point being, ISDN lets you put a cable between two nodes. If you want
to talk to a different node, you have to plug in a different cable.
>>>> Sure, you don't usually talk to them directly; usually you use one
>>>> of the IP addresses from the block assigned to your ISP.
>>>
>>> Ding ding! Guess what? They aren't assigned centrally. Your ISP
>>> assined you yours, mine assigned me mine.
>>
>> And where does the ISP get their IP block from?
>>
>> Yeah, exactly: They're assigned centrally.
>
> Nope. They're assigned heirarchically. That's completely different.
I don't see how...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
>>> Last time I checked, ISDN is point-to-point only
>>
>> So is TCP. It's connection-oriented, except for the D-channel, which
>> is datagram oriented.
>
> My point being, ISDN lets you put a cable between two nodes. If you want
> to talk to a different node, you have to plug in a different cable.
So there's only one possible ISP you can use over ISDN? There's only one
person you can call on ISDN?
Since one of the nodes on the cable is a switch connected to a world-wide
network, I don't really see your point. Every network that's just a wire
works this way. IP over CAT5 ethernet only lets you talk between two nodes,
and if you want to use a different node, you have to move a wire. That's why
there's such a concept as a default route.
>>> Yeah, exactly: They're assigned centrally.
>> Nope. They're assigned heirarchically. That's completely different.
> I don't see how...
Can't really help you with the english, there.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 20:00:11 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Assuming the switch isn't multicast aware. I wouldn't be surprised if
>> some were these days (but I haven't looked at it recently).
>
> Um, no. Even so.
>
> If you have one cable coming into the university campus, and a network
> for each building, the router is going to have to send the packets to
> each building, duplicating the packets, regardless of how "aware" anyone
> is.
Yes, but that's not a 1:1 transmission (compared to the receiving
clients).
>> The difference between, for example,
>> using unicast to push an image down to 15 workstations on a subnet and
>> using multicast to push an image down to 15 workstations on a subnet is
>> a significant reduction in overall network traffic.
>
> Only for that one subnet.
The router is part of the subnet, though. It retransmits upstream if the
TTL hasn't expired (and it's configured to do so).
> It's better than a unicast stream to each destination, yes. That doesn't
> mean IP isn't point-to-point, if you factor in the broadcast address as
> meaning "one subnet is the point."
That's a bit like saying shouting is point-to-point, though, because the
target "point" is a group.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Fri, 14 May 2010 20:01:35 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Not really, a party line is many-to-many,
>
> Er, not really, no. A party line is one switch to many phones.
>
>> The routers act as repeaters, but still operate a multicast "domain"
>> (if you will) within their local network, as long as there's a client
>> that has registered with the router to listen in on the multicast.
>
> Yes, I know how it works. Now we're just arguing over analogies.
We tend to do that. ;-)
> My point is that it's *not* like a radio broadcast. It's point-to-point
> between routers. The only place you're saving bandwidth is on subnets.
Which is kinda the important point.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
>> If you have one cable coming into the university campus, and a network
>> for each building, the router is going to have to send the packets to
>> each building, duplicating the packets, regardless of how "aware" anyone
>> is.
>
> Yes, but that's not a 1:1 transmission (compared to the receiving
> clients).
I don't know what you mean.
For one thing, modern ethernet (the kind that goes over CAT5 instead of
coax) is indeed 1:1 on every part of the network. Nothing I send from my
computer to yours does not go through the router.
You need to duplicate the packets at least once per physical wire. Same as
any network. IP doesn't force you to duplicate anything less.
Granted, if you're broadcasting from one point, the broadcaster only has to
send one packet per physical connection regardless of the number of
recipients. But that's the same with ISDN and all those technologies too.
You call into a conference bridge and the bridge duplicates the data as
necessary. You're not sending out the same data once for each receiver there
either.
>>> The difference between, for example,
>>> using unicast to push an image down to 15 workstations on a subnet and
>>> using multicast to push an image down to 15 workstations on a subnet is
>>> a significant reduction in overall network traffic.
>> Only for that one subnet.
>
> The router is part of the subnet, though. It retransmits upstream if the
> TTL hasn't expired (and it's configured to do so).
Firstly, if your subnet isn't broadcast, it doesn't save you any bandwidth.
The router still needs to duplicate all the packets. If your subnet *does*
support broadcast (like coax ethernet, or alohanet, or something like that)
then sure, you can broadcast to everyone, but that's because *any*
transmission goes to everyone, taking up your bandwidth even if it's not
addressed to you.
>> It's better than a unicast stream to each destination, yes. That doesn't
>> mean IP isn't point-to-point, if you factor in the broadcast address as
>> meaning "one subnet is the point."
>
> That's a bit like saying shouting is point-to-point, though, because the
> target "point" is a group.
Broadcast networks tend to be very small, and they tend to not allow two
conversations at once. You're not saving bandwidth by broadcasting. You're
just using it more efficiently. A targeted communication on a broadcast
network still takes up everyone's bandwidth. They just ignore it. Multicast
on a broadcast network isn't saving bandwidth as much as it's not wasting
bandwidth.
Wireless is about the only common broadcast IP-based network still around,
tho, exactly because it's so bandwidth-inefficient and impossible to squelch
when something goes wrong.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
>> My point is that it's *not* like a radio broadcast. It's point-to-point
>> between routers. The only place you're saving bandwidth is on subnets.
>
> Which is kinda the important point.
Except even there, you're only saving bandwidth on broadcast networks, and
on broadcast networks, everyone shares the same bandwidth, so even TCP
packets go to everyone on the subnet.
The whole point of using multicast instead of broadcast is what it does
between routers, not what it does on a subnet.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Le 15/05/2010 22:02, Darren New nous fit lire :
> Jim Henderson wrote:
>>> If you have one cable coming into the university campus, and a network
>>> for each building, the router is going to have to send the packets to
>>> each building, duplicating the packets, regardless of how "aware" anyone
>>> is.
>>
>> Yes, but that's not a 1:1 transmission (compared to the receiving
>> clients).
>>>> The difference between, for example,
>>>> using unicast to push an image down to 15 workstations on a subnet and
>>>> using multicast to push an image down to 15 workstations on a subnet is
>>>> a significant reduction in overall network traffic.
>>> Only for that one subnet.
>>
>> The router is part of the subnet, though. It retransmits upstream if
>> the TTL hasn't expired (and it's configured to do so).
>
> Firstly, if your subnet isn't broadcast, it doesn't save you any
> bandwidth. The router still needs to duplicate all the packets. If your
> subnet *does* support broadcast (like coax ethernet, or alohanet, or
> something like that) then sure, you can broadcast to everyone, but
> that's because *any* transmission goes to everyone, taking up your
> bandwidth even if it's not addressed to you.
>
[snip]
> Broadcast networks tend to be very small, and they tend to not allow two
> conversations at once. You're not saving bandwidth by broadcasting.
> You're just using it more efficiently. A targeted communication on a
> broadcast network still takes up everyone's bandwidth. They just ignore
> it. Multicast on a broadcast network isn't saving bandwidth as much as
> it's not wasting bandwidth.
>
> Wireless is about the only common broadcast IP-based network still
> around, tho, exactly because it's so bandwidth-inefficient and
> impossible to squelch when something goes wrong.
>
And then came in play the (G)MPLS system(s), allowing to reserve
bandwidth, having "routers" to perform split/duplication of data, and
putting in place minimalist-covering trees for optimal diffusion (and
even worse: you can have 1:1 protection, or even 1+1 !) adapting in
nearly realtime to the destinations interested in the "channel" and
reacting to the network events too.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 10-5-2010 10:12, Invisible wrote:
>> Or Carl Sagan, for that matter.
>
> Who?
See also Pioneer WIP in p.b.i
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>>>> Last time I checked, ISDN is point-to-point only
>>>
>>> So is TCP. It's connection-oriented, except for the D-channel, which
>>> is datagram oriented.
>>
>> My point being, ISDN lets you put a cable between two nodes. If you
>> want to talk to a different node, you have to plug in a different cable.
>
> So there's only one possible ISP you can use over ISDN? There's only one
> person you can call on ISDN?
>
> Since one of the nodes on the cable is a switch connected to a
> world-wide network, I don't really see your point.
My point is that ISDN is a point-to-point system, so it doesn't have a
concept of network addresses. When there are only 2 nodes in the system,
you don't need addresses; if machine A talks, it can only be talking to
machine B.
Having a global network without addresses doesn't really work.
And that's kind of my point: All the other network systems were designed
for networks that are "small", where it's feasible to keep track of all
the addresses by hand. None of them really supported having several
networks connected together, managed independently.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |