?
Solved

what is a protocol

Posted on 2016-10-20
7
Medium Priority
?
51 Views
Last Modified: 2016-11-17
.
0
Comment
Question by:rgb192
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 41853088
A protocol is a specific method for a network connection such as http, ftp, smtp, etc.  The actual details of a protocol are in the binary code implemented in the driver software.  This article https://en.wikipedia.org/wiki/Internet_protocol_suite lists most of the Internet protocols in use.  From a user viewpoint, all you usually need is to make sure your software is using the same protocol as the site you're trying to connect to.
1
 
LVL 9

Expert Comment

by:Antzs
ID: 41853152
Protocol is a certain way of communication in between devices.  The devices communicating with each other need to be talking in the same language.
0
 
LVL 11

Expert Comment

by:Scott Silva
ID: 41854193
Are we doing your homework?  Just wondering...
1
Four New Appliances. Same Industry-leading Speeds.

But don't take it from us.  The Firebox M370 is Miercom tested and Miercom approved, outperforming its competitors for stateless and stateful traffic throughput scenarios.  Learn more about the M370, M470, M570 and M670 and find the right solution for your organization today!

 

Author Comment

by:rgb192
ID: 41861085
"Are we doing your homework?  Just wondering..."

No, I graduated high school over a decade ago.
Perhaps I should have expanded more on the question - I want to know what exactly a Protocol is comprised of and how they're built -i.e. Assembly/Machine Code?

What is a Protocol, exactly?
0
 
LVL 83

Assisted Solution

by:Dave Baldwin
Dave Baldwin earned 1000 total points
ID: 41861115
"Protocol" is a general word for things in networks in particular that have to work a certain way.  However, there is no 'exactly' because each one is different.  Most networking software over the years has been written in C because that is easier than Assembly language to maintain and it is also easier to re-compile on another machine.  Some low level parts may require Assembly language but those are usually in the drivers for a specific machine.

This is the best description I can give you: https://en.wikipedia.org/wiki/Internet_protocol_suite   There is no 'exact' answer because 'protocol' is a general purpose category, not a specific thing.
0
 
LVL 27

Accepted Solution

by:
tliotta earned 1000 total points
ID: 41866532
A protocol is really just a set of rules. A network protocol is a set of rules that say what signals can be sent over a wire (or broadcast by radio or whatever) and what to do when a particular signal is received.

A protocol might be HTTP (HyperText Transfer Protocol). A given set of signals sent across a network will tell some remote system to send back a document in an agreed upon format so it can be displayed on the local screen.

That protocol might (unlikely) be written in assembler for some systems, but it's far more likely to be written in a language such as C. An assembler will be different for different types of systems, making it necessary to write significant sections (or even all) of the protocol code from scratch for each system. And when a new generation of a system is built, all of the protocols could need to be rewritten, possibly from scratch, making it difficult to get a new system to work for customers.

But a language such as C can be written with portability in mind. Properly written C modules can be relatively easy to get to work on almost any new system.

In short, protocols are just rules. "When 'y' comes across the network, do 'Y'." You can find documents called RFCs (
Request for Comments) on the internet. Each one is for a proposed set of rules for a particular protocol (as well as some other things). If a given RFC is accepted and implemented by enough people, it essentially becomes a 'standard'. Then anyone can use that RFC or standard to write programming to implement that protocol. The programmer may use any language, even an assembler.

If you want to build a computer at home and write the protocols yourself, you're free to do so in any way you wish. And as long as your code implements the rules according to the specifications in the RFCs, you can communicate with any other system on the same network or across the internet.
0
 

Author Closing Comment

by:rgb192
ID: 41891405
data rich answers thanks
0

Featured Post

Supports up to 4K resolution!

The VS192 2-Port 4K DisplayPort Splitter is perfect for anyone who needs to send one source of DisplayPort high definition video to two or four DisplayPort displays. The VS192 can split and also expand DisplayPort audio/video signal on two or four DisplayPort monitors.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Quality of Service (QoS) options are nearly endless when it comes to networks today. This article is merely one example of how it can be handled in a hub-n-spoke design using a 3-tier configuration.
As companies replace their old PBX phone systems with Unified IP Communications, many are finding out that legacy applications such as fax do not work well with VoIP. Fortunately, Cloud Faxing provides a cost-effective alternative that works over an…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question