Reading through all the "new posts" on this thread: well, first of all, till first 15-16 posts, it wasn't even clear whether this query was for audio application. So there was no question of an attempt to take it south. I was merely trying to help and just kept addressing questions that kept coming in...
Anyway, here goes...
It would be nice to get a reference to this.
I have a very basic understanding of the TCP IP protocol/stack and nothing I know of says of this specifically.
Especially this part.
Nikhil, in a previous post you apparently admitted you understand TCP/IP "works". So a bit surprised to see this demand of "reference". Anyway, you can always look up IETF site for all things Internet. If you do need reference line-wise and interpretation wise, then you will either have to wait till I can find enough spare time to highlight specific parts from the protocol's official specification for your reference or you'll have to hire me. I can assure you if hired, I'll do it pretty quickly
Alternatively, there is this thing called Google. I am sure you would rather type in Google TCP/IP specification. The pages it throws up will answer many more questions than this alone.
Could you guys clarify the crosstalk thing? I am under the impression that it is about interference between pairs in one cable, and not about external interference from other cables or sources.
Thad, when a cable reject/eliminates interference it just rejects it. It doesn't know whether the interference is from the wires rolling next to them, or from elsewhere. If the interference is weak enough to be contained by its shield, it remain unaffected, regardless of the origin of the interference.
I sort-of wish you'd put that in the first post! it is not wise. I don't know if best-practice recommendations have changed, but I suspect (Ranjeet and Arun will tell us) that they would still be to separate electricity and data runs, avoid fittings such as fluorescent lights, and when electricity and data must cross, do so at right angles.
It's been done to several steps further, Thad. You can actually send data packets through mains.
Look up "Powerline Adapters" or PowerPacket Technology. TCP/IP protocols are so robust they work even if directly mains lines are used as physical medium forget noise, interference, shielding
This page is a goor start-point.
I don't mind a good discussion but some of the questions asked (in the context of my original post) were to put it mildly .... condescending.
I am very surprised with this. Way too many times at this forum to keep a count, people have been asked - have you tried it?. Have you heard it? Do you own it? As if not owning, hot having heard or not having tried something was a disqualification from posting based on established academic knowledge and knowledge earned through indirect experiences. People have gone to lengths of declaring comments that were not based on personal experience as "unsubstantiated". I am really really surprised to read this appears condescending in this thread. May be it's time to have some clear understanding of what's condescending and what isn't. Because such things can't be condescending or non-condescending based on which thread it appears in, or where it comes from.
At this stage, I'm wondering if the CAT-7 shielding would be effective in a mains duct. I'm not sure that that is the kind of thing it would be designed to protect against. I'm hoping that Asliarun or Ranjeet is going to offer something on that.
Thad, what's the point going in for CAT7 if it has to be laid alongside mains cables? Definitely, if someone spends on shielded cables, he would be wise to keep it as far away from major sources of interference such as electrical lines. But that's just my 2 paise! Others might say, whats shielding good for, what am I paying for if I have to prepare another conduit.