 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> 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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Sat, 15 May 2010 13:02:58 -0700, Darren New wrote:
> 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.
It's not one sender to one receiver. It's one sender to many receivers.
> 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.
Not necessarily true if it's a local subnet. But even if it is across
routers, so what? The router is just setting up a multicast domain for
the downstream network, which may include another router that does the
same thing.
> 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.
True.
> 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.
That's also the point; the amount of traffic sent by the sender is
significantly reduced; the switches also typically have logic so they
don't have to fill their buffers with multiple copies of the same data
(for those that have a buffer).
> 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.
I think there may be a conflation of "broadcast" and "multicast" here.
> 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.
Small relative to the size of the Internet, sure. Small relative to the
size of a given network, maybe not so much.
That last sentence is just semantics, though.
> 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.
I assume you're talking about 802.11 networks; some wireless networking
technologies implement CSMA-CA while others do CSMA-CD; the latter is
much more efficient but requires hardware that is capable of listening;
in a spread-spectrum implementation (which most 802.11 networks are),
CSMA-CA is more common but the DSS implementations mean that there's much
less chance of a collision (that's part of the point of that type of
implementation).
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> On Sat, 15 May 2010 13:02:58 -0700, Darren New wrote:
>
>> 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.
>
> It's not one sender to one receiver. It's one sender to many receivers.
Right. The question isn't how many senders and receivers there are. The
question is whether you're duplicating packets.
>> 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.
>
> Not necessarily true if it's a local subnet.
Uh, yes. There's nothing that's going to go over this cat5 wire that doesn't
go to the other end of the wire. If your PC is plugged into your
router/switch, and your other PC is plugged into your router/switch, then
talking between the PCs goes thru the router/switch.
The only difference would be if you have (a) only two PCs on the network, at
which point multicast is irrelevant, or (b) you have a hub, at which point
the hub is still duplicating packets for every wire, except it's doing it
indiscriminately.
> But even if it is across
> routers, so what? The router is just setting up a multicast domain for
> the downstream network, which may include another router that does the
> same thing.
I think at this point you may have forgotten why we're discussing this.
The contention was that things like ATM and ISDN are "point to point" while
IP somehow isn't. My contention is that any network physically wired
anything close to what ATM and ISDN does is also point to point, and that
most IP networks other than wireless are of the same sort of topology as ATM
and ISDN. (And maybe wireless, too. I don't know enough to know whether one
node can send to the other without the AP repeating it.)
>> 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.
>
> True.
That's my point. IP is still point-to-point, by necessity, when you don't
have a broadcast network.
When you *do* have a broadcast network, unless you do something really funky
(unlike, say, coax ethernet), all the nodes can be conceptually treated as
one node, because they can't talk at the same time, they all see the same
data, they don't get all the bandwidth to themselves, etc. And that hasn't
anything to do with IP. IP multicast doesn't route packets to a specific
machine. It routes them to a specific broadcast subnet, if there is one. If
I'm on a segment with someone receiving multicast, I have no way *not* to
receive that, and it can saturate my bandwidth even tho I'm uninterested.
>> 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.
>
> That's also the point; the amount of traffic sent by the sender is
> significantly reduced;
When I'm on a conference call via ISDN, I'm only sending one copy of each
byte. I'm not the one doing the duplication. The ISDN router (known as the
conference bridge) is doing the duplication, just like in IP.
> the switches also typically have logic so they
> don't have to fill their buffers with multiple copies of the same data
> (for those that have a buffer).
True, but now we're talking about something far below the level of IP.
>> 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.
>
> I think there may be a conflation of "broadcast" and "multicast" here.
Nope. I'm saying there are two physical networking possibilities: broadcast,
and unicast. Either everyone gets the signal on a broadcast network, or only
one person gets the signal on a unicast network. Coax ethernet is
broadcast. CAT5 ethernet is unicast.
The only place that multicast saves bandwidth is on a unicast network (like
between routers) where nobody downstream of the receiver wants to receive
the data. If you have a separate wire to each PC with bandwidth dedicated to
that PC, multicast is 1:1 on any given segment of the network.
>
>> 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.
>
> Small relative to the size of the Internet, sure. Small relative to the
> size of a given network, maybe not so much.
>
> That last sentence is just semantics, though.
By that I mean that multicast on a broadcast network doesn't needlessly send
the same packet multiple times. But neither does something like ATM or ISDN.
>> 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.
>
> I assume you're talking about 802.11 networks;
Yes, the kind that carry IP via broadcast. Something like IP over CDMA or
GSM is much closer to having a wired connection than a broadcast connection,
since nearby nodes aren't listening to you.
> some wireless networking
> technologies implement CSMA-CA while others do CSMA-CD; the latter is
> much more efficient but requires hardware that is capable of listening;
> in a spread-spectrum implementation (which most 802.11 networks are),
> CSMA-CA is more common but the DSS implementations mean that there's much
> less chance of a collision (that's part of the point of that type of
> implementation).
Sure. But if I have a 10Mbps coax, or a 54Mbps 802.11g, I'm sharing that
with everyone else on that network. If I can hear everything coming out of
the router and I have to wait for everyone else to stop transmitting before
I can, then having multicast not transmit duplicates isn't "saving"
bandwidth. It's taking up my bandwidth whether I'm listening to it or not.
If I have a 9Mbps stream coming in, my coax ethernet network is going to be
slow whether I'm watching video or not. What it *does* do is not send it
twice when everyone interested has already heard it. That's what I was
talking about.
However, I strongly suspect that none of this discussion has anything to do
with whatever Andrew meant when he said IP isn't 1:1 like ISDN 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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> Small relative to the size of the Internet, sure. Small relative to the
> size of a given network, maybe not so much.
I meant small physically. Rarely does a broadcast network extend over more
than (say) one building. Not if you're talking about a 2-way broadcast.
Maybe cable IP systems? I don't know how they work on the cable, whether
it's closer to TDMA or closer to CDMA or what. Clearly it's not isochronous,
so you get the bandwidth you ask for if it's available. Thinking on it, I'm
guessing at least the cable network for the local neighborhood is probably
one big broadcast tree, so yea, bigger than I was thinking.
--
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:
> My point is that ISDN is a point-to-point system, so it doesn't have a
> concept of network addresses.
WTF? What are you smoking? And can I have some?
http://en.wikipedia.org/wiki/ISDN
> Having a global network without addresses doesn't really work.
You *have* heard of phone numbers, haven't you?
> 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.
So, when you make a phone call to someone in the USA, you think there's one
group of people managing the undersea cable, the wire going into your
building, and the cell phone towers talking to the cell phone in the USA?
When you see a phone number that starts +1 or +43 or something like that,
what do you think that means?
--
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 Mon, 17 May 2010 10:12:20 -0700, Darren New wrote:
> Jim Henderson wrote:
>> Small relative to the size of the Internet, sure. Small relative to
>> the size of a given network, maybe not so much.
>
> I meant small physically. Rarely does a broadcast network extend over
> more than (say) one building. Not if you're talking about a 2-way
> broadcast.
What do you mean by "2-way broadcast"?
> Maybe cable IP systems? I don't know how they work on the cable, whether
> it's closer to TDMA or closer to CDMA or what. Clearly it's not
> isochronous, so you get the bandwidth you ask for if it's available.
> Thinking on it, I'm guessing at least the cable network for the local
> neighborhood is probably one big broadcast tree, so yea, bigger than I
> was thinking.
Yes, but from a standpoint of multicast, there again, you get some
savings (and increased scalability). I imagine (but don't know for sure)
that cable uses some sort of multicast scheme (though probably not
multicast over IP) so there isn't a bottleneck at the transmitting end of
things; all people who are watching channel 657 are likely part of a
multicast group of some sort, otherwise you'd hit xmit bandwidth
limitations when a large number of people start watching TV all at once.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 10:07:52 -0700, Darren New wrote:
> Jim Henderson wrote:
>> On Sat, 15 May 2010 13:02:58 -0700, Darren New wrote:
>>
>>> 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.
>>
>> It's not one sender to one receiver. It's one sender to many
>> receivers.
>
> Right. The question isn't how many senders and receivers there are. The
> question is whether you're duplicating packets.
Yes, and you would duplicate packets when repeating to a different
subnet, sure. That doesn't mean the bandwidth savings disappear when you
introduce a router to the picture.
>>> 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.
>>
>> Not necessarily true if it's a local subnet.
>
> Uh, yes. There's nothing that's going to go over this cat5 wire that
> doesn't go to the other end of the wire. If your PC is plugged into your
> router/switch, and your other PC is plugged into your router/switch,
> then talking between the PCs goes thru the router/switch.
Yes, true.
> The only difference would be if you have (a) only two PCs on the
> network, at which point multicast is irrelevant, or (b) you have a hub,
> at which point the hub is still duplicating packets for every wire,
> except it's doing it indiscriminately.
True in both cases.
>> But even if it is across
>> routers, so what? The router is just setting up a multicast domain for
>> the downstream network, which may include another router that does the
>> same thing.
>
> I think at this point you may have forgotten why we're discussing this.
Perhaps, or perhaps the discussion mutated. :-)
> The contention was that things like ATM and ISDN are "point to point"
> while IP somehow isn't. My contention is that any network physically
> wired anything close to what ATM and ISDN does is also point to point,
> and that most IP networks other than wireless are of the same sort of
> topology as ATM and ISDN. (And maybe wireless, too. I don't know enough
> to know whether one node can send to the other without the AP repeating
> it.)
I was simply pointing out that multicast (in particular) isn't
necessarily point-to-point from an IP standpoint. I think you may be
talking at a lower level in the OSI stack than IP that it is, and I
couldn't disagree with that, certainly.
>>> 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.
>>
>> True.
>
> That's my point. IP is still point-to-point, by necessity, when you
> don't have a broadcast network.
This is where I think you're talking at the physical or network layer,
not the transport layer.
> When you *do* have a broadcast network, unless you do something really
> funky (unlike, say, coax ethernet), all the nodes can be conceptually
> treated as one node, because they can't talk at the same time, they all
> see the same data, they don't get all the bandwidth to themselves, etc.
> And that hasn't anything to do with IP. IP multicast doesn't route
> packets to a specific machine. It routes them to a specific broadcast
> subnet, if there is one. If I'm on a segment with someone receiving
> multicast, I have no way *not* to receive that, and it can saturate my
> bandwidth even tho I'm uninterested.
That's not how multicast works, to my understanding. You subscribe to
the multicast - unless the switch (a) isn't a switch, or (b) isn't
multicast aware, you're right; but if you are on a segment with someone
who receives a multicast and the network hardware understands which ports
to send the multicast data to, then no, you don't see the packets because
you're not subscribed to the multicast.
> When I'm on a conference call via ISDN, I'm only sending one copy of
> each byte. I'm not the one doing the duplication.
Right.
> The ISDN router (known
> as the conference bridge) is doing the duplication, just like in IP.
Depends on whether you're talking unicast to *each* destination node or
multicast IP. Therein lies the difference (and the bandwidth savings).
In a multicast scenario, at the transport layer, the switch isn't
"duplicating" the packet, it's forwarding it (which may be a semantic
debate).
>> the switches also typically have logic so they don't have to fill their
>> buffers with multiple copies of the same data (for those that have a
>> buffer).
>
> True, but now we're talking about something far below the level of IP.
Not in a Layer3 switch we're not. ;-)
>>> 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.
>>
>> I think there may be a conflation of "broadcast" and "multicast" here.
>
> Nope. I'm saying there are two physical networking possibilities:
> broadcast, and unicast. Either everyone gets the signal on a broadcast
> network, or only one person gets the signal on a unicast network. Coax
> ethernet is broadcast. CAT5 ethernet is unicast.
Yes, physical layer (or network layer), not transport layer. It feels
like you're conflating the two.
> The only place that multicast saves bandwidth is on a unicast network
> (like between routers) where nobody downstream of the receiver wants to
> receive the data. If you have a separate wire to each PC with bandwidth
> dedicated to that PC, multicast is 1:1 on any given segment of the
> network.
The destination "1" is a single multicast address that the specific
targets subscribe to - that's what makes it not 1:1, but 1:many.
>>> 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.
>>
>> Small relative to the size of the Internet, sure. Small relative to
>> the size of a given network, maybe not so much.
>>
>> That last sentence is just semantics, though.
>
> By that I mean that multicast on a broadcast network doesn't needlessly
> send the same packet multiple times. But neither does something like ATM
> or ISDN.
There again, though, mixing up physical/network layer with transport
layer.
>>> 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.
>>
>> I assume you're talking about 802.11 networks;
>
> Yes, the kind that carry IP via broadcast. Something like IP over CDMA
> or GSM is much closer to having a wired connection than a broadcast
> connection, since nearby nodes aren't listening to you.
Well, if it's DSS then that's true, but otherwise, the other nodes can
cause interference with you, so if they're doing CSMA-CD, then they are
listening to you, if only to see if the channel is clear to transmit.
>> some wireless networking
>> technologies implement CSMA-CA while others do CSMA-CD; the latter is
>> much more efficient but requires hardware that is capable of listening;
>> in a spread-spectrum implementation (which most 802.11 networks are),
>> CSMA-CA is more common but the DSS implementations mean that there's
>> much less chance of a collision (that's part of the point of that type
>> of implementation).
>
> Sure. But if I have a 10Mbps coax, or a 54Mbps 802.11g, I'm sharing that
> with everyone else on that network. If I can hear everything coming out
> of the router and I have to wait for everyone else to stop transmitting
> before I can, then having multicast not transmit duplicates isn't
> "saving" bandwidth. It's taking up my bandwidth whether I'm listening to
> it or not. If I have a 9Mbps stream coming in, my coax ethernet network
> is going to be slow whether I'm watching video or not. What it *does* do
> is not send it twice when everyone interested has already heard it.
> That's what I was talking about.
Not with multicast IP; again, if you don't subscribe to it, you don't
receive it, at least that's my understanding (http://
www.multicasttech.com/faq/ provides a good explanation).
> However, I strongly suspect that none of this discussion has anything to
> do with whatever Andrew meant when he said IP isn't 1:1 like ISDN is.
Well, quite possibly, unless he was talking about multicast as a reason.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> My point is that ISDN is a point-to-point system, so it doesn't have a
>> concept of network addresses.
>
> WTF? What are you smoking? And can I have some?
>
> http://en.wikipedia.org/wiki/ISDN
So... it's a large page of jargon that I don't really understand. What
specifically am I looking at?
>> Having a global network without addresses doesn't really work.
>
> You *have* heard of phone numbers, haven't you?
Relevance?
>> 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.
>
> So, when you make a phone call to someone in the USA, you think there's
> one group of people managing the undersea cable, the wire going into
> your building, and the cell phone towers talking to the cell phone in
> the USA?
All of the other *computer* network systems were designed for small
networks. Sheesh...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> I was simply pointing out that multicast (in particular) isn't
> necessarily point-to-point from an IP standpoint.
Sure. And it's not point-to-point from an ISDN or even POTS perspective
either. Dialing into a conference bridge is the equivalent of putting the
destination address as the multicast address in IP. It's lower-layer
technology that actually does the multicasting, not IP itself.
>>>> 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.
>>> True.
>> That's my point. IP is still point-to-point, by necessity, when you
>> don't have a broadcast network.
>
> This is where I think you're talking at the physical or network layer,
> not the transport layer.
The transport layer isn't involved in multicast in IP, per se. Multicast
transport layer is just UDP. The messages maintaining the spanning three
modify things in the network layer.
> and the network hardware understands which ports
> to send the multicast data to,
Then it's not broadcast, and the switch is duplicating the data once for
each subscriber. That's what I'm saying. *If* there's any bandwidth savings
(i.e., more than one NIC reads the same packet), it's because every NIC in
the broadcast area is reading the same packet and some of them are throwing
it away.
>> The ISDN router (known
>> as the conference bridge) is doing the duplication, just like in IP.
>
> Depends on whether you're talking unicast to *each* destination node or
> multicast IP. Therein lies the difference (and the bandwidth savings).
> In a multicast scenario, at the transport layer, the switch isn't
> "duplicating" the packet, it's forwarding it (which may be a semantic
> debate).
It's duplicating it for each outward link the packet goes over. If you have
a router with someone upstream sending a multicast session and three routers
downstream receiving it, how much bandwidth, total, is that taking up?
>>> the switches also typically have logic so they don't have to fill their
>>> buffers with multiple copies of the same data (for those that have a
>>> buffer).
>> True, but now we're talking about something far below the level of IP.
>
> Not in a Layer3 switch we're not. ;-)
I'm pretty sure IP says nothing about how you implement copying a packet
from one NIC to another. :-)
> Yes, physical layer (or network layer), not transport layer. It feels
> like you're conflating the two.
No. I'm pointing out that talking about the bandwidth savings, or "point to
point" ness of IP implicitly is talking about the network and physical
layers. Multicast *is* point to point, *unless* you're on a physical
broadcast network. Multicast is point-to-point between any two elements of
the network where there's a non-broadcast cable between them.
>> The only place that multicast saves bandwidth is on a unicast network
>> (like between routers) where nobody downstream of the receiver wants to
>> receive the data. If you have a separate wire to each PC with bandwidth
>> dedicated to that PC, multicast is 1:1 on any given segment of the
>> network.
>
> The destination "1" is a single multicast address that the specific
> targets subscribe to - that's what makes it not 1:1, but 1:many.
Yes. And 858-102-1137 is a single multicast address that hosts a conference
bridge. Is that not 1:many, if many phones call into that address?
> There again, though, mixing up physical/network layer with transport
> layer.
Only because I'm trying to understand in what possible sense IP is 1:many
and ISDN isn't. Sure, if a conference bridge is 1:many then so is an IP
multicast. But I don't think you can say an IP multicast is 1:many and an
ISDN conference bridge is 1:1, because it's doing the identical thing in the
identical way.
>> Yes, the kind that carry IP via broadcast. Something like IP over CDMA
>> or GSM is much closer to having a wired connection than a broadcast
>> connection, since nearby nodes aren't listening to you.
>
> Well, if it's DSS then that's true, but otherwise, the other nodes can
> cause interference with you, so if they're doing CSMA-CD, then they are
> listening to you, if only to see if the channel is clear to transmit.
I said CDMA, not CSMA. I'm not sure what DSS is here, but in CDMA everyone
talks at the same time, and in GSM (afaik) nobody talks at the same time, so
there's no interference (of the type we're talking about) in either one.
> Not with multicast IP; again, if you don't subscribe to it, you don't
> receive it, at least that's my understanding (http://
> www.multicasttech.com/faq/ provides a good explanation).
If you're on a broadcast network, you have no choice but to receive it. If
you're on a network where each connection is 1:1, then it's the same as an
ISDN conference bridge.
>> However, I strongly suspect that none of this discussion has anything to
>> do with whatever Andrew meant when he said IP isn't 1:1 like ISDN is.
>
> Well, quite possibly, unless he was talking about multicast as a reason.
I don't think so...
--
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:
> What do you mean by "2-way broadcast"?
Well, FM radio would be a one-way broadcast. Coax ethernet would be a
two-way broadcast.
> Yes, but from a standpoint of multicast, there again, you get some
> savings (and increased scalability). I imagine (but don't know for sure)
> that cable uses some sort of multicast scheme
Well, look, there really isn't something that's a multicast physical layer.
Either the bandwidth is scaled per user, or it isn't. If we're all talking
at the same frequency on a coax cable (say like old ethernet) and I'm
transmiting, it's a broadcast, regardless of the destination address.
AFAIK, cable systems run fiber to a box in each neighborhood, and then have
a tree of cables coming out from there, all carrying the same signal.
> all people who are watching channel 657 are likely part of a
> multicast group of some sort,
Sure. And all people watching channel 657 are also receiving channel 652.
They're just not tuning it. Just like FM radio. (And I was talking about IP
over cable, actually, not TV 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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
>>> My point is that ISDN is a point-to-point system, so it doesn't have
>>> a concept of network addresses.
>>
>> WTF? What are you smoking? And can I have some?
>>
>> http://en.wikipedia.org/wiki/ISDN
>
> So... it's a large page of jargon that I don't really understand. What
> specifically am I looking at?
The part that describes ISDN as a global network?
>>> Having a global network without addresses doesn't really work.
>> You *have* heard of phone numbers, haven't you?
> Relevance?
> Having a global network without addresses doesn't really work.
That's the relevance. Do you even *know* what ISDN is? Do you understand
that it's a global network? Do you understand how everyone *except* IP
addresses global networks, specifically because of the sorts of problems you
see with IPv4 address spaces, NATs, routing table overflows, etc etc etc?
>>> 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.
>>
>> So, when you make a phone call to someone in the USA, you think
>> there's one group of people managing the undersea cable, the wire
>> going into your building, and the cell phone towers talking to the
>> cell phone in the USA?
>
> All of the other *computer* network systems were designed for small
> networks. Sheesh...
Uh, no. Really, not. X.25. ATM. ISDN. SONET. They're all world-wide
networks-of-networks, just like IP. Indeed, IP runs over top of all these
networks once you get outside your own building. (Granted, X.25 is probably
not much used any more, but it was basically what IP wound up replacing, and
again was the substrate carrier for a lot of IP data before SONET got cheap
enough to dedicate a fiber to something as trickling slow as IP traffic.)
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> All of the other *computer* network systems were designed for small
>> networks. Sheesh...
>
> Uh, no. Really, not. X.25. ATM. ISDN. SONET. They're all world-wide
> networks-of-networks, just like IP. Indeed, IP runs over top of all
> these networks once you get outside your own building. (Granted, X.25 is
> probably not much used any more, but it was basically what IP wound up
> replacing, and again was the substrate carrier for a lot of IP data
> before SONET got cheap enough to dedicate a fiber to something as
> trickling slow as IP traffic.)
Interesting. Because from what I've seen, all the earlier technologies
allow you to connect together maybe a few dozen nodes, and then stop
working after you try to scale much beyond that. They all use their own
perculiar addressing scheme, and there's no way of referring to a node
that isn't on the local network.
To me, it seems that the major contribution of IP is that it gives you
an addressing system which is independent of the underlying transport
technology, and has routable addresses (and definite rules for how to
use them). I haven't seen anything else that does that.
Oh, and then people whine that it doesn't map cleanly to the ISO/OSI
7-layer model. Oh well...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 20:37:18 +0100, Orchid XP v8 wrote:
> I haven't seen anything else that does that.
IPX/SPX did that. DECNET, AFAIK, did that.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 12:15:13 -0700, Darren New wrote:
> Jim Henderson wrote:
>> What do you mean by "2-way broadcast"?
>
> Well, FM radio would be a one-way broadcast. Coax ethernet would be a
> two-way broadcast.
OIC what you're saying, that the filtering is applied by the receiving
end (either filtered by software or hardware).
>> Yes, but from a standpoint of multicast, there again, you get some
>> savings (and increased scalability). I imagine (but don't know for
>> sure) that cable uses some sort of multicast scheme
>
> Well, look, there really isn't something that's a multicast physical
> layer.
Maybe Sirius radio? Dunno, you might be right on that.
> Either the bandwidth is scaled per user, or it isn't. If we're
> all talking at the same frequency on a coax cable (say like old
> ethernet) and I'm transmiting, it's a broadcast, regardless of the
> destination address.
>
> AFAIK, cable systems run fiber to a box in each neighborhood, and then
> have a tree of cables coming out from there, all carrying the same
> signal.
Would have to find someone who works for a cableco to confirm,
obviously. (Or a good article describing the technology)
>> all people who are watching channel 657 are likely part of a multicast
>> group of some sort,
>
> Sure. And all people watching channel 657 are also receiving channel
> 652. They're just not tuning it. Just like FM radio. (And I was talking
> about IP over cable, actually, not TV per se. :-)
That implies a pretty enormous total bandwidth on the coax cable coming
into your house, then. If you figure 40 SD channels and 40 HD channels,
for example, that several megabits of digital broadcast being sent out to
be filtered.
I was using cable TV as an example because it's data being sent over a
network. Data is data is data is data, after all. :-)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 11:58:34 -0700, Darren New wrote:
> Jim Henderson wrote:
>> I was simply pointing out that multicast (in particular) isn't
>> necessarily point-to-point from an IP standpoint.
>
> Sure. And it's not point-to-point from an ISDN or even POTS perspective
> either. Dialing into a conference bridge is the equivalent of putting
> the destination address as the multicast address in IP. It's lower-layer
> technology that actually does the multicasting, not IP itself.
Arguably, it would be a technology - not a protocol - implementation.
>>>>> 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.
>>>> True.
>>> That's my point. IP is still point-to-point, by necessity, when you
>>> don't have a broadcast network.
>>
>> This is where I think you're talking at the physical or network layer,
>> not the transport layer.
>
> The transport layer isn't involved in multicast in IP, per se. Multicast
> transport layer is just UDP. The messages maintaining the spanning three
> modify things in the network layer.
I may need to read more on this.
>> and the network hardware understands which ports to send the multicast
>> data to,
>
> Then it's not broadcast, and the switch is duplicating the data once for
> each subscriber. That's what I'm saying. *If* there's any bandwidth
> savings (i.e., more than one NIC reads the same packet), it's because
> every NIC in the broadcast area is reading the same packet and some of
> them are throwing it away.
But that isn't the case, necessarily. The switch is allowing the packet
to get to those subscribers who've requested it. Whether that's
duplication or filtering is really just semantics.
>>> The ISDN router (known
>>> as the conference bridge) is doing the duplication, just like in IP.
>>
>> Depends on whether you're talking unicast to *each* destination node or
>> multicast IP. Therein lies the difference (and the bandwidth savings).
>> In a multicast scenario, at the transport layer, the switch isn't
>> "duplicating" the packet, it's forwarding it (which may be a semantic
>> debate).
>
> It's duplicating it for each outward link the packet goes over. If you
> have a router with someone upstream sending a multicast session and
> three routers downstream receiving it, how much bandwidth, total, is
> that taking up?
That depends on a lot of different factors. If there's 10 stations at
the far end of the third router hop, the amount of bandwidth between
routers is still a constant 1:1; the initial sender isn't sending the
data 10 times, it's sending it once - and that doesn't matter if there's
10 targets at the end of the 3rd router, or 10 at the end of router 3, 50
between router 2&3, and 100 between router 1&2.
>>>> the switches also typically have logic so they don't have to fill
>>>> their buffers with multiple copies of the same data (for those that
>>>> have a buffer).
>>> True, but now we're talking about something far below the level of IP.
>>
>> Not in a Layer3 switch we're not. ;-)
>
> I'm pretty sure IP says nothing about how you implement copying a packet
> from one NIC to another. :-)
That's because the switch provides the implementation details; the
protocol doesn't implement itself.
>> Yes, physical layer (or network layer), not transport layer. It feels
>> like you're conflating the two.
>
> No. I'm pointing out that talking about the bandwidth savings, or "point
> to point" ness of IP implicitly is talking about the network and
> physical layers. Multicast *is* point to point, *unless* you're on a
> physical broadcast network. Multicast is point-to-point between any two
> elements of the network where there's a non-broadcast cable between
> them.
I think that made sense to me.
>>> The only place that multicast saves bandwidth is on a unicast network
>>> (like between routers) where nobody downstream of the receiver wants
>>> to receive the data. If you have a separate wire to each PC with
>>> bandwidth dedicated to that PC, multicast is 1:1 on any given segment
>>> of the network.
>>
>> The destination "1" is a single multicast address that the specific
>> targets subscribe to - that's what makes it not 1:1, but 1:many.
>
> Yes. And 858-102-1137 is a single multicast address that hosts a
> conference bridge. Is that not 1:many, if many phones call into that
> address?
It is, sure. Each phone is a "subscriber" to the bridge. The "data"
isn't sent to phones that aren't subscribers.
>> There again, though, mixing up physical/network layer with transport
>> layer.
>
> Only because I'm trying to understand in what possible sense IP is
> 1:many and ISDN isn't. Sure, if a conference bridge is 1:many then so is
> an IP multicast. But I don't think you can say an IP multicast is 1:many
> and an ISDN conference bridge is 1:1, because it's doing the identical
> thing in the identical way.
I don't think I was saying that. I haven't commented on ISDN, only on IP
multicast.
>>> Yes, the kind that carry IP via broadcast. Something like IP over CDMA
>>> or GSM is much closer to having a wired connection than a broadcast
>>> connection, since nearby nodes aren't listening to you.
>>
>> Well, if it's DSS then that's true, but otherwise, the other nodes can
>> cause interference with you, so if they're doing CSMA-CD, then they are
>> listening to you, if only to see if the channel is clear to transmit.
>
> I said CDMA, not CSMA. I'm not sure what DSS is here, but in CDMA
> everyone talks at the same time, and in GSM (afaik) nobody talks at the
> same time, so there's no interference (of the type we're talking about)
> in either one.
Oh, right, I missed that (I'm used to talking strictly in terms of CSMA).
>> Not with multicast IP; again, if you don't subscribe to it, you don't
>> receive it, at least that's my understanding (http://
>> www.multicasttech.com/faq/ provides a good explanation).
>
> If you're on a broadcast network, you have no choice but to receive it.
True, because you see everything, addressed to your or not. That's why
hubs are used for sniffing, generally.
> If you're on a network where each connection is 1:1, then it's the same
> as an ISDN conference bridge.
I think that's a matter of semantics.
>>> However, I strongly suspect that none of this discussion has anything
>>> to do with whatever Andrew meant when he said IP isn't 1:1 like ISDN
>>> is.
>>
>> Well, quite possibly, unless he was talking about multicast as a
>> reason.
>
> I don't think so...
In which case the discussion has been an 'evolution'. ;-)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> On Mon, 17 May 2010 12:15:13 -0700, Darren New wrote:
>
>> Jim Henderson wrote:
>>> What do you mean by "2-way broadcast"?
>> Well, FM radio would be a one-way broadcast. Coax ethernet would be a
>> two-way broadcast.
>
> OIC what you're saying, that the filtering is applied by the receiving
> end (either filtered by software or hardware).
Right.
>> Well, look, there really isn't something that's a multicast physical
>> layer.
>
> Maybe Sirius radio? Dunno, you might be right on that.
Different frequencies, sure. I'd more likely call that lots of independent
networks.
> Would have to find someone who works for a cableco to confirm,
> obviously. (Or a good article describing the technology)
Yeah.
>>> all people who are watching channel 657 are likely part of a multicast
>>> group of some sort,
>> Sure. And all people watching channel 657 are also receiving channel
>> 652. They're just not tuning it. Just like FM radio. (And I was talking
>> about IP over cable, actually, not TV per se. :-)
>
> That implies a pretty enormous total bandwidth on the coax cable coming
> into your house, then. If you figure 40 SD channels and 40 HD channels,
> for example, that several megabits of digital broadcast being sent out to
> be filtered.
Yep. A cable can carry huge amounts of data, depending on its length. The
closer the fiber hubs out to the houses, the more channels you can carry.
> I was using cable TV as an example because it's data being sent over a
> network. Data is data is data is data, after all. :-)
Exactly.
--
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:
> 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.
Nope. If you're on a party line and I'm not, and I call you, I have one
person on my end and you have every party on your end. Exactly like going
thru a router with one connection that's CAT5 and the other connection
that's coax ethernet. If you connect two party lines thru the switch, then
anyone on either side can hear everyone, just like having a switch with two
ports and a broadcast network on each side.
--
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:
> Interesting. Because from what I've seen, all the earlier technologies
> allow you to connect together maybe a few dozen nodes, and then stop
> working after you try to scale much beyond that.
Um, you *are* aware that we had a global telephone network *before* we had
computers, right?
> They all use their own
> perculiar addressing scheme, and there's no way of referring to a node
> that isn't on the local network.
Tell me. When you (or your boss) needs to talk to someone in America, how
do they do it? What steps do they follow?
> To me, it seems that the major contribution of IP is that it gives you
> an addressing system which is independent of the underlying transport
> technology, and has routable addresses (and definite rules for how to
> use them). I haven't seen anything else that does that.
You ... haven't picked up a phone lately?
> Oh, and then people whine that it doesn't map cleanly to the ISO/OSI
> 7-layer model. Oh well...
Exactly. It doesn't map cleanly to the global network that was already
around for decades before IP was even conceived. It is difficult to manage
and debug and route compared to the world-wide telephone network everyone
takes for granted. And they're running out of addresses (actually, probably
already ran out of addresses) long before every person has an address, let
alone every piece of communications equipment.
--
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:
> Arguably, it would be a technology - not a protocol - implementation.
Yeah, basically.
> I may need to read more on this.
Yep. There's (IIRC) ICMP messages to control the routing (via expressing
interest), and just UDP with multicast destination addresses to deliver the
data.
> But that isn't the case, necessarily. The switch is allowing the packet
> to get to those subscribers who've requested it. Whether that's
> duplication or filtering is really just semantics.
Sure. As is "1:1" vs "1:many" when every pair of receivers had an
independent connection, which was my point. :-)
> That depends on a lot of different factors. If there's 10 stations at
> the far end of the third router hop, the amount of bandwidth between
> routers is still a constant 1:1;
Yep. And if there's 10 people on the conference call, my phone is only
sending my voice once. I completely agree with you. I'm simply stating that
ISDN and all those other network technologies work the same way, so IP
multicast isn't a distinguishing feature.
>>>> True, but now we're talking about something far below the level of IP.
>>> Not in a Layer3 switch we're not. ;-)
>> I'm pretty sure IP says nothing about how you implement copying a packet
>> from one NIC to another. :-)
>
> That's because the switch provides the implementation details; the
> protocol doesn't implement itself.
Hmmm. You seem to be disagreeing with yourself. Unless you were joking and
saying a layer 3 switch is only a little below IP and not far below.
> I think that made sense to me.
That's all I've been trying to express. IP multicast is equivalent to ISDN
conference bridge, where the bridge serves as the router doing the routing
to multiple outgoing segments.
>>> The destination "1" is a single multicast address that the specific
>>> targets subscribe to - that's what makes it not 1:1, but 1:many.
>> Yes. And 858-102-1137 is a single multicast address that hosts a
>> conference bridge. Is that not 1:many, if many phones call into that
>> address?
>
> It is, sure. Each phone is a "subscriber" to the bridge. The "data"
> isn't sent to phones that aren't subscribers.
OK. That was what I was trying to express. Saying IP multicast is 1:many and
ISDN conference bridge isn't is not a reasonable comparison.
> I don't think I was saying that. I haven't commented on ISDN, only on IP
> multicast.
Fair enough. That's where this came up, and why I'm talking about layers
below IP. Otherwise, I think we both understand how IP handles multicast.
>>> Not with multicast IP; again, if you don't subscribe to it, you don't
>>> receive it, at least that's my understanding (http://
>>> www.multicasttech.com/faq/ provides a good explanation).
>> If you're on a broadcast network, you have no choice but to receive it.
>
> True, because you see everything, addressed to your or not. That's why
> hubs are used for sniffing, generally.
Exactly my point. That's why I said multicast in that case doesn't "save"
bandwidth.
>>> Well, quite possibly, unless he was talking about multicast as a
>>> reason.
>> I don't think so...
>
> In which case the discussion has been an 'evolution'. ;-)
From his other message, I think he doesn't realize that an ISDN connection
has an address at all, or something.
--
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 Mon, 17 May 2010 14:55:37 -0700, Darren New wrote:
> If you're on a party line and I'm not, and I call you
Then you get a busy signal. ;-)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 15:05:04 -0700, Darren New wrote:
> Exactly my point. That's why I said multicast in that case doesn't
> "save" bandwidth.
Bottom line, we're both in violent agreement again without realising
it. ;-)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Mon, 17 May 2010 14:53:24 -0700, Darren New wrote:
> Yep. A cable can carry huge amounts of data, depending on its length.
> The closer the fiber hubs out to the houses, the more channels you can
> carry.
It's not just a function of the cable length, though; encoding the data,
attenuation, other forms of interference, etc - but that's all outside
the scope of discussion. :-)
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 17/05/2010 11:29 PM, Jim Henderson wrote:
> On Mon, 17 May 2010 14:55:37 -0700, Darren New wrote:
>
>> If you're on a party line and I'm not, and I call you
>
> Then you get a busy signal. ;-)
>
Are you allowed to use real life examples, here?
Do you still have party lines in 2010?
--
Best Regards,
Stephen
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Interesting. Because from what I've seen, all the earlier technologies
>> allow you to connect together maybe a few dozen nodes, and then stop
>> working after you try to scale much beyond that.
>
> Um, you *are* aware that we had a global telephone network *before* we
> had computers, right?
And, for the 17th time, you *are* aware that I'm talking about earlier
_computer_ network technologies, right?
My point, which you seem determined to ignore, is that everybody who
designed a way to connect computers together designed it to only handle
a small handful of computers. It seems to me that it wasn't until IP
came along that you could connect very large collections of computers
together.
>> Oh, and then people whine that it doesn't map cleanly to the ISO/OSI
>> 7-layer model. Oh well...
>
> Exactly. It doesn't map cleanly to the global network that was already
> around for decades before IP was even conceived. It is difficult to
> manage and debug and route compared to the world-wide telephone network
> everyone takes for granted.
I'm fairly sure the telephone network connects vastly fewer nodes. It
was also originally analogue, not digital. Not to mention being managed
by a very small number of companies. But anyway...
> And they're running out of addresses
> (actually, probably already ran out of addresses) long before every
> person has an address, let alone every piece of communications equipment.
Isn't that why IPv6 was invented?
BTW, how come nobody uses that yet? And does it replace just the IP
layer, or the entire protocol stack?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Tue, 18 May 2010 09:19:54 +0100, Invisible wrote:
> And, for the 17th time, you *are* aware that I'm talking about earlier
> _computer_ network technologies, right?
It's all telecommunications, which is what I think Darren is saying.
> I'm fairly sure the telephone network connects vastly fewer nodes. It
> was also originally analogue, not digital. Not to mention being managed
> by a very small number of companies. But anyway...
IP address blocks are managed by IANA - a single organisation. IANA does
delegate some administrative tasks, but overall they handle the larger
picture.
>> And they're running out of addresses
>> (actually, probably already ran out of addresses) long before every
>> person has an address, let alone every piece of communications
>> equipment.
>
> Isn't that why IPv6 was invented?
Yes.
> BTW, how come nobody uses that yet? And does it replace just the IP
> layer, or the entire protocol stack?
Some people do use it. IPv6 runs at the same OSI level as IPv4, so yes,
it's a direct replacement.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> And, for the 17th time, you *are* aware that I'm talking about earlier
>> _computer_ network technologies, right?
>
> It's all telecommunications, which is what I think Darren is saying.
And what I'm saying is that it just seems that whenever somebody sat
down and designed a system for making computers talk to each other, they
invisiged a LAN with a quite limited number of nodes.
> IP address blocks are managed by IANA - a single organisation. IANA does
> delegate some administrative tasks, but overall they handle the larger
> picture.
That's roughly what I figured.
>> BTW, how come nobody uses that yet? And does it replace just the IP
>> layer, or the entire protocol stack?
>
> Some people do use it. IPv6 runs at the same OSI level as IPv4, so yes,
> it's a direct replacement.
I mean, for example, does TCP work differently with IPv6, or is it the
exact same protocol just running over a different carrier?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Stephen wrote:
> Do you still have party lines in 2010?
The last party line was shut down in the late 1980s in the USA, if I recall
properly. It was surprisingly recent.
--
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:
> And, for the 17th time, you *are* aware that I'm talking about earlier
> _computer_ network technologies, right?
And what makes you think ISDN isn't a computer network technology?
From the very first sentence in the wikipedia page you claimed was too complex:
"""
Integrated Services Digital Network (ISDN) is a set of communications
standards for simultaneous digital transmission of voice, video, data, and
other network services over the traditional circuits of the public switched
telephone network.
"""
What do you think "Integrated Services" means?
> My point, which you seem determined to ignore, is that everybody who
> designed a way to connect computers together designed it to only handle
> a small handful of computers.
Uh, no. How many computers do you think ISDN can connect together?
Or perhaps you mean http://en.wikipedia.org/wiki/X.25
> It seems to me that it wasn't until IP
> came along that you could connect very large collections of computers
> together.
You are mistaken. People were connecting together large numbers of computers
long before IP was around.
> I'm fairly sure the telephone network connects vastly fewer nodes.
You are incorrect. Indeed, in 1999, there was more *fax* traffic than
internet traffic, let alone voice and data. Ten years later, probably less
so. But you're talking about "earlier" networks.
Just the number of telephones exceeded the number of IP addresses just a
couple of years ago. And that's not even counting the fact that IP allocates
multiple IP addresses to each router in the network and the PSTN doesn't
allocate phone numbers to the switches at all. If you actually allocated an
address to every endpoint like you do in IP, you'd have an order of
magnitude more addresses in the PSTN than you do in IP.
> It was also originally analogue, not digital.
Yes, but irrelevant once you invent the modem. All underlying network
technology is analog until it gets to a modem.
> Not to mention being managed
> by a very small number of companies.
Not particularly. Certainly not nowadays.
>> And they're running out of addresses (actually, probably already ran
>> out of addresses) long before every person has an address, let alone
>> every piece of communications equipment.
>
> Isn't that why IPv6 was invented?
In part.
> BTW, how come nobody uses that yet?
Because they stupidly didn't design in any backward compatibility, so an
IPv4 machine can't talk to an IPv6 machine and vice versa.
--
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:
> On Tue, 18 May 2010 09:19:54 +0100, Invisible wrote:
>
>> And, for the 17th time, you *are* aware that I'm talking about earlier
>> _computer_ network technologies, right?
>
> It's all telecommunications, which is what I think Darren is saying.
No. ISDN is a computer networking technology. It really is. When you swipe
your credit card, it uses the D channel of ISDN to deliver the numbers to
your bank and get the auth back. It's digital. It's computer. It happens to
be common that you take those bytes and run them thru a DAC to a speaker.
That doesn't mean your phone isn't a computer.
> IP address blocks are managed by IANA - a single organisation. IANA does
> delegate some administrative tasks, but overall they handle the larger
> picture.
And telco numbers are managed by ISO, and then each country, then each
company, then each local office, because the telco has *way* too many phone
numbers and crosses *way* too many administrative domains to make it
reasonable to only have two levels of network allocation.
IANA allocates blocks to Tier 1 providers. Then *they* split up the blocks
smaller and smaller. IANA has no say in what /24 you wind up getting on your
individual cable modem.
> Some people do use it. IPv6 runs at the same OSI level as IPv4, so yes,
> it's a direct replacement.
And that's the problem. It's a replacement, not an upgrade.
--
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:
> And what I'm saying is that it just seems that whenever somebody sat
> down and designed a system for making computers talk to each other, they
> invisiged a LAN with a quite limited number of nodes.
And yet I've given you half a dozen examples to the contrary. I give up.
>> IP address blocks are managed by IANA - a single organisation. IANA
>> does delegate some administrative tasks, but overall they handle the
>> larger picture.
>
> That's roughly what I figured.
They handle the top-level allocations of blocks for people who connect to
the primary backbone. Your ISP isn't one of them.
--
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 Tue, 18 May 2010 16:46:34 +0100, Invisible wrote:
>>> And, for the 17th time, you *are* aware that I'm talking about earlier
>>> _computer_ network technologies, right?
>>
>> It's all telecommunications, which is what I think Darren is saying.
>
> And what I'm saying is that it just seems that whenever somebody sat
> down and designed a system for making computers talk to each other, they
> invisiged a LAN with a quite limited number of nodes.
Have you read up on IPX? Used in some of the first PC networks, and it
was designed with multiple networks in mind and routing.
I've actually talked with one the guys who came up with that stuff.
"Limited" wasn't part of the equation, in fact, quite the opposite.
The fact that IPv6 uses the MAC address of the NIC as part of its address
is something they "borrowed" from IPX, in fact.
>>> BTW, how come nobody uses that yet? And does it replace just the IP
>>> layer, or the entire protocol stack?
>>
>> Some people do use it. IPv6 runs at the same OSI level as IPv4, so
>> yes, it's a direct replacement.
>
> I mean, for example, does TCP work differently with IPv6, or is it the
> exact same protocol just running over a different carrier?
I imagine Google could answer that question for you; I don't know off the
top of my head.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Tue, 18 May 2010 09:09:06 -0700, Darren New wrote:
>> It's all telecommunications, which is what I think Darren is saying.
>
> No. ISDN is a computer networking technology. It really is.
Yes, but it's all about getting information from point A to point B,
which is essentially what telecommunications is all about.
>> IP address blocks are managed by IANA - a single organisation. IANA
>> does delegate some administrative tasks, but overall they handle the
>> larger picture.
>
> And telco numbers are managed by ISO, and then each country, then each
> company, then each local office, because the telco has *way* too many
> phone numbers and crosses *way* too many administrative domains to make
> it reasonable to only have two levels of network allocation.
>
> IANA allocates blocks to Tier 1 providers. Then *they* split up the
> blocks smaller and smaller. IANA has no say in what /24 you wind up
> getting on your individual cable modem.
Much like the telephone system. ISO has no say about what my cell phone
number is. :-)
>> Some people do use it. IPv6 runs at the same OSI level as IPv4, so
>> yes, it's a direct replacement.
>
> And that's the problem. It's a replacement, not an upgrade.
Yep, though there are ways of tunneling IPv4 through IPv6 and vice-versa.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Jim Henderson wrote:
> On Tue, 18 May 2010 09:09:06 -0700, Darren New wrote:
>
>>> It's all telecommunications, which is what I think Darren is saying.
>> No. ISDN is a computer networking technology. It really is.
>
> Yes, but it's all about getting information from point A to point B,
> which is essentially what telecommunications is all about.
It's what all electronic networking is about. (Physical networking is about
getting "stuff" from A to B.)
In what sense is IP not telecommunications?
>> IANA allocates blocks to Tier 1 providers. Then *they* split up the
>> blocks smaller and smaller. IANA has no say in what /24 you wind up
>> getting on your individual cable modem.
>
> Much like the telephone system. ISO has no say about what my cell phone
> number is. :-)
Yes. I'm agreeing with that, unlike Andrew's contention that it's all
centralized.
> Yep, though there are ways of tunneling IPv4 through IPv6 and vice-versa.
Unfortunately, they require someone to provide you a server, so most such
servers aren't open to the public.
--
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 Tue, 18 May 2010 09:51:30 -0700, Darren New wrote:
> Jim Henderson wrote:
>> On Tue, 18 May 2010 09:09:06 -0700, Darren New wrote:
>>
>>>> It's all telecommunications, which is what I think Darren is saying.
>>> No. ISDN is a computer networking technology. It really is.
>>
>> Yes, but it's all about getting information from point A to point B,
>> which is essentially what telecommunications is all about.
>
> It's what all electronic networking is about. (Physical networking is
> about getting "stuff" from A to B.)
>
> In what sense is IP not telecommunications?
I didn't say it wasn't. I'm agreeing with you.
>>> IANA allocates blocks to Tier 1 providers. Then *they* split up the
>>> blocks smaller and smaller. IANA has no say in what /24 you wind up
>>> getting on your individual cable modem.
>>
>> Much like the telephone system. ISO has no say about what my cell
>> phone number is. :-)
>
> Yes. I'm agreeing with that, unlike Andrew's contention that it's all
> centralized.
We're doing it again. Violent agreement. :-)
>> Yep, though there are ways of tunneling IPv4 through IPv6 and
>> vice-versa.
>
> Unfortunately, they require someone to provide you a server, so most
> such servers aren't open to the public.
True, at least at this point.
Jim
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> And, for the 17th time, you *are* aware that I'm talking about earlier
>> _computer_ network technologies, right?
>
> And what makes you think ISDN isn't a computer network technology?
You don't use ISDN to network all the computers in the building
together. You use ISDN to connect one computer in your building to one
computer in some other building. If it weren't for higher-level
protocols, you wouldn't be able to use this for anything other than
letting those two solitary nodes converse.
>> My point, which you seem determined to ignore, is that everybody who
>> designed a way to connect computers together designed it to only
>> handle a small handful of computers.
>
> Uh, no. How many computers do you think ISDN can connect together?
2, AFAIK.
>> It seems to me that it wasn't until IP
>> came along that you could connect very large collections of computers
>> together.
>
> You are mistaken.
Oh well. I guess that's the problem with being *alive*. :-(
> People were connecting together large numbers of
> computers long before IP was around.
Interesting. As I say, all the technologies I've seen support only small
numbers of nodes.
>> I'm fairly sure the telephone network connects vastly fewer nodes.
>
> You are incorrect. Indeed, in 1999, there was more *fax* traffic than
> internet traffic, let alone voice and data. Ten years later, probably
> less so. But you're talking about "earlier" networks.
That makes no sense at all. There are people who don't even own a
telephone, but have multiple computers connected to the Internet. And
nobody uses fax anymore. What the hell...?
>> BTW, how come nobody uses that yet?
>
> Because they stupidly didn't design in any backward compatibility, so an
> IPv4 machine can't talk to an IPv6 machine and vice versa.
Now do you mean they didn't design IPv4 to be easily extensible, or they
didn't design IPv6 to be backwards-compatible?
And WTF happened to IPv5 anyway?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 18/05/2010 4:54 PM, Darren New wrote:
> Stephen wrote:
>> Do you still have party lines in 2010?
>
> The last party line was shut down in the late 1980s in the USA, if I
> recall properly. It was surprisingly recent.
>
I think that it was a bit earlier than that in the UK but we are much
more closely packed.
--
Best Regards,
Stephen
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Stephen wrote:
> I think that it was a bit earlier than that in the UK but we are much
> more closely packed.
I'm not sure of the history, but a lot of times, things will go a lot longer
where they were invented.
For example, in the USA, we had 96%+ landline penetration in residences in
1980 or so. South Korea had essentially none. Forward to 2005, and we have
like 20% of the population having cell phones and 80%+ of south koreans
having cell phones.
I.e., I wouldn't be surprised that by the time the UK had widespread
residential phone service, the technology was cheap enough that party lines
didn't really make sense.
--
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:
> You don't use ISDN to network all the computers in the building
> together.
You don't use IP to network all the computers in your building together
either. You have one wire from your computer to the switch. You then run
wires between switches.
> You use ISDN to connect one computer in your building to one
> computer in some other building.
You're being kind of silly here, you know that?
I guess you can only connect a modem to one other computer, too, right?
When the other computer in some other building is connected to a worldwide
network of switching fabric, what do you think happens?
> If it weren't for higher-level
> protocols, you wouldn't be able to use this for anything other than
> letting those two solitary nodes converse.
Higher-level protocols like dialing the phone? You know, you can't even
connect two ISDN machines together. You *need* a switch in between, even if
the two machines are sitting in the same room.
>>> My point, which you seem determined to ignore, is that everybody who
>>> designed a way to connect computers together designed it to only
>>> handle a small handful of computers.
>>
>> Uh, no. How many computers do you think ISDN can connect together?
>
> 2, AFAIK.
So that explains, for example, BRI having two high-speed channels and 8
source addresses on the D channel, right?
Tell me, how many people can you talk to on your phone?
>>> It seems to me that it wasn't until IP
>>> came along that you could connect very large collections of computers
>>> together.
>>
>> You are mistaken.
>
> Oh well. I guess that's the problem with being *alive*. :-(
It is, in part, part of the problem of people showing you where to read up
on the subject and you saying "that would take too long."
>> People were connecting together large numbers of computers long before
>> IP was around.
>
> Interesting. As I say, all the technologies I've seen support only small
> numbers of nodes.
TELEPHONES! Jeez, dude. How many nodes do you think is typical for one
switch in, say, downtown London? Hint: I'd guess somewhere between 500,000
and 1,000,000 subscribers per switch.
Interesting, perhaps, because you're not really thinking things through.
Given that IP isn't a physical networking technology, how do you think IP
gets all over the world if there isn't any network technology capable of
connecting to things all over the world?
>>> I'm fairly sure the telephone network connects vastly fewer nodes.
>>
>> You are incorrect. Indeed, in 1999, there was more *fax* traffic than
>> internet traffic, let alone voice and data. Ten years later, probably
>> less so. But you're talking about "earlier" networks.
>
> That makes no sense at all. There are people who don't even own a
> telephone, but have multiple computers connected to the Internet. And
> nobody uses fax anymore. What the hell...?
Clearly nobody uses fax any more.
> Now do you mean they didn't design IPv4 to be easily extensible, or they
> didn't design IPv6 to be backwards-compatible?
The latter.
> And WTF happened to IPv5 anyway?
It was allocated to an experimental realtime protocol that didn't get deployed.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
> When the other computer in some other building is connected to a
> worldwide network of switching fabric, what do you think happens?
You use ISDN to transport some higher-level protocol that knows how to
do routing?
>>> You are mistaken.
>>
>> Oh well. I guess that's the problem with being *alive*. :-(
>
> It is, in part, part of the problem of people showing you where to read
> up on the subject and you saying "that would take too long."
Or maybe a result of thinking that just because you've been using
something for 10 years, you actually know something about it...
>> And WTF happened to IPv5 anyway?
>
> It was allocated to an experimental realtime protocol that didn't get
> deployed.
Now *that* at least makes sense...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> You use ISDN to transport some higher-level protocol that knows how to
> do routing?
ISDN already knows how to do the routing. As does ATM and X.25. You don't
need to layer anything on top of it to route packets or connections.
> Or maybe a result of thinking that just because you've been using
> something for 10 years, you actually know something about it...
I dunno. I've been using my lymph system for a lot longer than that and I
know virtually nothing about 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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 18/05/2010 9:11 PM, Darren New wrote:
> Stephen wrote:
>> I think that it was a bit earlier than that in the UK but we are much
>> more closely packed.
>
> I'm not sure of the history, but a lot of times, things will go a lot
> longer where they were invented.
>
> For example, in the USA, we had 96%+ landline penetration in residences
> in 1980 or so. South Korea had essentially none. Forward to 2005, and we
> have like 20% of the population having cell phones and 80%+ of south
> koreans having cell phones.
>
Crikey!
http://en.wikipedia.org/wiki/List_of_countries_by_number_of_mobile_phones_in_use
In the UK everyone has almost one and a quarter mobile phones each (2008).
South Korea - 97.24% 2009
United States - 91.0% Dec. 2009
> I.e., I wouldn't be surprised that by the time the UK had widespread
> residential phone service, the technology was cheap enough that party
> lines didn't really make sense.
>
You are probably right, I missed the transition tho’.
Although I tend to think that it was not cost but capacity in GB (as it
was known then). Remember* there was no profit requirement with the GPO
but a mater of “national pride”.
* You won’t remember of course as there was no reason for you to take
notice. :-)
--
Best Regards,
Stephen
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> You use ISDN to transport some higher-level protocol that knows how to
>> do routing?
>
> ISDN already knows how to do the routing. As does ATM and X.25. You
> don't need to layer anything on top of it to route packets or connections.
Well that's news to me...
>> Or maybe a result of thinking that just because you've been using
>> something for 10 years, you actually know something about it...
>
> I dunno. I've been using my lymph system for a lot longer than that and
> I know virtually nothing about it.
Ah, but do you have qualifications about it? Did you get an A* in your
Lymph System Utilisation finals?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |