<font color="#3333ff"><font face="verdana,sans-serif">Yes, when I read back the whole thread, I made too many assumptions and as you said "over simplified" the explanation, thus ended up messing up the whole theory and protocol. I apologise. <br clear="all">
</font></font><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><br>-GGR<br>--</span><div><div><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Rajiv G Gunja</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">
<span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Blog: <a href="http://ossrocks.blogspot.com" target="_blank">http://ossrocks.blogspot.com</a></span><br>
<br><br><div class="gmail_quote">On Thu, Sep 15, 2011 at 18:43, Bryan J Smith <span dir="ltr"><<a href="mailto:b.j.smith@ieee.org">b.j.smith@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
That's not all you wrote, let alone there are still context issues where you went deeper than you should.<br>
<br>
That's why I "stepped back" from the get go. And then I saw exactly what I figured would happen.<br>
<br>
More absolutes, more assumptions, few, accurate statements.<br><font color="#888888">
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br></font><div class="gmail_quote"><div class="im">Rajiv Gunja <<a href="mailto:opn.src.rocks@gmail.com" target="_blank">opn.src.rocks@gmail.com</a>> wrote:</div>
<div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<font color="#3333ff"><font face="verdana,sans-serif">Ok Mr Bryan the IEEE guru</font></font><font color="#3333ff"><font face="verdana,sans-serif">, please read what I wrote. <br clear="all"></font></font><div><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><br>
</span></div><div><font color="#3333ff" face="verdana, sans-serif">----</font></div><div><font color="#3333ff" face="verdana, sans-serif"><span style="font-size:13px;background-color:rgb(255, 255, 255)">Network driver does not care if the packet is from a telnet application or KDE application or VNC or java program, its function is to deliver the said data to the end client and guarantee (tcp)that the packet reaches the destination without corruption.</span></font></div>
<div><font color="#3333ff" face="verdana, sans-serif"><span style="font-size:13px;background-color:rgb(255, 255, 255)">----</span></font></div><div><font color="#3333ff" face="verdana, sans-serif"><span style="font-size:13px;background-color:rgb(255, 255, 255)"><br>
</span></font></div><div><font color="#3333ff" face="verdana, sans-serif"><span style="font-size:13px;background-color:rgb(255, 255, 255)">In that above statement, am I talking about UDP or stateless packet?</span></font></div>
<div><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><br></span></div><div><font color="#3333ff" face="verdana, sans-serif">-GGR</font></div><div><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><br>
--</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif"><span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Rajiv G Gunja</span><br style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">
<span style="color:rgb(51, 51, 255);font-family:verdana,sans-serif">Blog: <a href="http://ossrocks.blogspot.com" target="_blank">http://ossrocks.blogspot.com</a></span><br>
<br><br><div class="gmail_quote">On Thu, Sep 15, 2011 at 17:28, Bryan J Smith <span dir="ltr"><<a href="mailto:b.j.smith@ieee.org" target="_blank">b.j.smith@ieee.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanx, I was hoping I'd find someone who agreed.<br>
<br>
There are so many, common solutions aspects of exchange that do not. Ping is a type of ICMP (IP protocol 1). The type is contained in the header of the IP packet (layer 3) itself, and does not use a transport. There are several others involved with PXEBoot'ing, which is very, very important when you're trying to netboot systems. And I can state countless other, "real world" examples too. And that's before I dive into security aspects.<br>
<br>
Understand I dove into this because I run into individuals at clients that not only think _exactly_ like this, but that one individual will undermine my trying to help the rest of their team. It's one thing to get the dumb stare like many do when we walk into Radio Shack, that's understandable as I don't expect everyone to know everything, but only where their experience has been. But it's not about not following, it's about _undermining_ the knowledge some someone is trying to share it, and help you.<br>
<br>
I've been involved with everything from IEEE subcomittees to government installations to 5 figures of nodes in computing and trading grids. There is nothing more destructive than people talking where they don't have experience, and stating incorrect information. It starts with over-simplification, but that's usually not bad. Most people do web, maybe remote shells, and you're talking TCP segments passing back and forth between source and destination ports. But I saw where it was going, and my assumptions proved right. They quickly became factually incorrect.<br>
<br>
You don't have to be doing real-time, Infiniband and other exchanges to not have transports using ports. There are many, common IP protocols and framing exchange, even some higher-level applications, that do not use transports with ports. As I used as an example above, troubleshooting PXEboot is one area where you really need to be familiar with this, especially. But I could dive into many other, real world cases.<br>
<div><br>
<br>
<br>
<br>
----- Original Message -----<br>
From: Joel J. <<a href="mailto:tcepsa@gmail.com" target="_blank">tcepsa@gmail.com</a>><br>
</div><div><div></div><div>Sent: Thursday, September 15, 2011 5:11 PM<br>
<br>
GGR> Yes, every application that talks over the network or within the<br>
OS itself has a port, it may be a temporary port, but it is<br>
GGR> present. In fact when 1 app talks to another app within the same<br>
server/pc, a port is opened for communication. It may not be<br>
GGR> seen on the network, but it is still present.<br>
<br>
I'm going to have to go with Brian on this one. For example, I<br>
present the humble ping application. It communicates with another<br>
computer across a network, yet does not use a port.<br>
</div></div></blockquote></div><br></div>
</blockquote></div></div></div></blockquote></div><br></div></div>