Discussion Locked

Protocol's; What are they

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have taken TCP\IP as my MCSE elective, and read
the Sybex's CCNA(Cisco Certified Network Associate), and researched many online RFC's and followed links that have been provided by Tech Republic, and still would like to get my hand on a protocol!What are they really; C+ scripts, software drivers? As a Net. Admin., I really need a "visual" in order to lockdown a Domain. Thanks

17 replies

by sridharpandu

When bush went was in Korea a few days ago he met up with the South Korean President Kim Dae jung they could have conversed if either Bush knew Korean or Kim knew English. So how did they establish a handshake and get to understand each other ? by using an interpreter who established the required protocol for Bush and Kim to understand each other.

Unfortunately the same problem exists in todays networked world, too many different dialects of technology. And establishing a handshake is almost impossible. Handshake between two different computing systems are possible only if the underlying protocol that carries the messages is one and the same. Today the most popular protocol is the TCP/IP which stands for Transfer Control Protocol / Internet Protocol. This ensures that all computers speak the same language and the handshake between machines can be easily established.

Some old protocols like SNA (IBM mainframes) and IPX (Netware) are still in use and to communicate with them you need a gateway which does the translation of TCP/IP to the destinationprotocol and vice versa thus performing the role of an interpreter

Visualising this mechanism is slightly difficult.

(PS- The HTTP protocol used for the internet is built over the TCP/IP protocol. )

Hope this helps.

by shanghai sam

Thank you for responding so quickly. I liked the comparison with the Prez's trip. However: If language was my goal, I could see and learn to speak any foreign language. Protocols on the other hand are explained medifourse to me so far. Can we trust Kim Dae Jung's interpreters? Could we have used a better distribution layer connection to Enron.

by shanghai sam

Protocols are neither scripts or drivers. Although, you could implement them in a script, and they install like a driver.

Protocols are sets of standard proceedures for clear communications between devices.

Following on the first answer, in Diplomacy Protocol is the sequence of events that are part of the diplomatic meetings and events.

It is a breach of protocol for a US clerk to speak directly to the Korean ambassador, without first going through the Korean clerk, and the entire chain of command up to the ambassador.

Computer protocols work the same way. They are composed of the commands and sequences of commands for the specific interface.

Another way to look at protocols is that the protocol is a definition of sentencestructure in a pass/fail class.
If you don't structure the sentence exactly right, with no mis-spellings, you fail the class.
The only way to pass is to structure your sentence perfectly.

You can think of each different protocol as a different language.

The structure that you need to use when writing your C+ scripts is a form of protocol. As are the sequence of commands that are implemented in a device driver.

So, basically, a protocol is a standard operating proceedure.

From theAmerican Heritage Dictionary;

pro?to?col n. 1.a. The forms of ceremony and etiquette observed by diplomats and heads of state. b. A code of correct conduct. 2. The first copy of a treaty or other such document before its ratification. 3. A preliminary draft or record of a transaction. 4. The plan for a course of medical treatment or for a scientific experiment. 5. Computer Science. A standard procedure for regulating data transmission between computers.

Hope this helps. Chas

by shanghai sam

WOW! Thank you very much on the detailed answer. This is truely more than what I could of ever expected.

by shanghai sam

Networking protocols are a commonly defined method whereby two or more computers communicate in a predefined method. For a breakdown of the TCP/IP protocol suite look here:

http://www.protocols.com/pbook/tcpip.htm

Some, like ARP and FTP, haveexecutable equivalent operating system execuatbles to invoke a process to perform communication with user-visible results. Others like IMAP and IGMP merely define composition of datagrams so the receiving entity can receive and decode the data. If you want to know how the information moves down the OSI layers, you would have to review the operating system source code. You might get a better understanding of the OSI model from Upgrading and Repairing Computers (1996 edition, ISBN 0-7897-0181-2), Chapter 3, "The OSI Model: Bringing Order to Chaos". There might be a similar chapter in more current versions of the book, but I don't have one.

by isys

I am reposting this because the above posting did not attribute the comments to me.

Networking protocols are a commonly defined method whereby two or more computers communicate in a predefined method. For a breakdown of the TCP/IP protocol suite look here:

http://www.protocols.com/pbook/tcpip.htm

Some, like ARP and FTP, have executable equivalent operating system execuatbles to invoke a process to perform communication with user-visible results. Others like IMAP and IGMP merely define composition of datagrams so the receiving entity can receive and decode the data. If you want to know how the information moves down the OSI layers, you would have to review the operating system source code. You might get a better understanding of the OSI model from Upgrading and Repairing Computers (1996 edition, ISBN 0-7897-0181-2), Chapter 3, "The OSI Model: Bringing Order to Chaos". There might be a similar chapter in more current versions of the book, but I don't have one.

by mm212

All of the above are excellent answers, but I'd add one thing:

You have Microsoft OSs, you have several versions of Unix and subsets of it. You have MacIntosh OSs. How can all of these computers talk to one another? Just like the Bush in Korea answer above (I LIKE that analogy!) all of these computers speak a different native tongue. The only way they can communicate is to have a way of communicating layed out in advance.

Think of a protocol as an interpreter that each computer speaks to,which translates it into the "Universal" language. The other computers hear the "Universal" language, their interpreter translates it into their own language and we now have a dialog.

Hope this helps more than it confuses!

by xanderoth

Ok, i know its getting old now- but to further illustrate on the interpreter analogy...

You are right about not being able to trust the interpretor. Protocol requires that layer to communicate, but whether what Bush heard was what the Korean President was saying was debateable.

Therefore Protocol also dictates that the message be first analyzed for integrity. The translator has several aides to ensure he heard the entire message and that his conversion of the language from Korean to English is correct. The message is then passed along.

Protocol also dictates that the message is acknowledged. Thus President Bush would either respond or at least acknowledge the words of the Korean President according to Protocol, though we cancall it common curtesy. His respone would be then handled the same way, according to Protocol.

by timwalsh

Your drive for the need of a "visual" of a protocol in order to lock down a domain, is akin to the need to understand the minutae of the source code in order to use Windows. It's really not necessary.
A protocol is no one "thing" that you can get a visual on. If you have researched the various RFCs, that is the closest to a "visual" you will get. As to your question of "can we trust the interpretor," the answer is that while the accuracy human interpretation of human language is subject to the vageries of individual human interpretors, network protocols are layed out in the various RFCs. The ultimate penalty for a network hardware manufacturer /software publisher not following the protocols are that their product can't play on any networks or on the internet. Period.

by rkelly

Just as an extention of what's already gone above here's another analogy.

As perviously stated all the machines need to be talking the same language (i.e protocol) but ALL network protocols just talk in 1s and 0s. The protocol tells the networkeddevice which language is being used AND defines which type of response it expects, just like a diplomatic protocol.

This discussion is closed to new replies.