Hello and welcome to CertForums.co.uk, here we host free active certification forums with links to the best free resources for Microsoft's MCSA MCSE MCDBA Cisco's CCNA CCDA and CCNP, and CompTIA's A+ Network+ i-NET+ and Security+ certifications in the UK. If you wish to post or use other advanced features you will need to register first. Registration is absolutely free and takes only a few minutes to complete so sign up today!
If you have any problems with the registration
process or your account login, please contact support
Reading about the infamous OSI model, and have come across the term "Peer Communication".
Is it simply, an appearance of what happens with all information sent across a network?
I know that for two different systems to communicate with each other, the data needs to go down through all the layers (being encapsulated a bit more each time), across the physical layer to the recipient machine, and then back up the layers (being decapsulated) to the same layer that it left on the sending machine. Is this process another way of saying peer communication, ie all comms-through-the-layers is peer communication?
I've checked Exam Cram 2 and Meyers to really no avail of the term.
It's the journey that matters, not the destination.
Aims:
70-271: Dec 2007 PASSED!
70-272: March 2008 PASSED!
ITIL v3 Foundation: June 2008
Net+: July 2008
70-270: Nov 2008
Last edited by derkit : 27-Apr-2008 at 06:54 PM.
Reason: to add in capsulation
Both models use the same network infrastructure and libraries, its the architecture and application layer protocols that define how they are used. Which machines talk to who and when...
Last edited by dmarsh26 : 27-Apr-2008 at 07:53 PM.
Thanks Harry and dmarsh for the super quick response
Harry - that's exactly what I was reading about - it seemed like it was a label for a concept, I just wanted to make sure it wasn't trying to explain something else and I wasn't getting it! phew!
It's the journey that matters, not the destination.
Aims:
70-271: Dec 2007 PASSED!
70-272: March 2008 PASSED!
ITIL v3 Foundation: June 2008
Net+: July 2008
70-270: Nov 2008
I've said it before and i'll say it again, the OSI 7 layer model is a THEORETICAL MODEL, it does not exist, nobody ever implements it, it exists to describe a theorectial architecture of how communications takes place. It provides a rough framework for people to work within, but they can and do deviate from it.
Imagine you are creating you own computer, and your own OS, and your own communications stack, how would you go about it ? I have worked on projects that have done this, and they did not reference the 7 layer model once, but they did broadly adhere to its principles, because they are sound layered architecture principals.
For example how might the same program work over serial RS232, Ethernet and other physical mediums without a layered architecture ? Reuse is obtained and higher reliability and less code to test by creating reusable modules in each layer that are interchangeable.