All of lore.kernel.org
 help / color / mirror / Atom feed
From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Knowledge of Protocols
Date: Fri, 10 Jul 2015 08:54:58 +0530	[thread overview]
Message-ID: <874mlcpud1.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <277293065.1356584.1436464575919.JavaMail.yahoo@mail.yahoo.com>


>>>>> [2015-07-09T23:26:15+0530]: "Mohit ." (Mohit):
,----[ Mohit ]
| I have just finished C & linux application programming with a tinge of socket programming.
| I would like to know what do statements like the following mean
|    
| - "Have knowledge of Protocols such as TCP/IP, IPSec, IPV6 or SSL"   
| 
| 
| Does it mean to have a theoretical view of the facets which constitute the protocol which can be done by reading RFC or does it also mean to have implementation knowledge (code understanding) as well. I am not very clear about this statement which is generally used quite often.
| Secondly, it the latter understanding is correct (Theory - RFC + Implementation - Code) then where to look for the code which deals with a particular protocol ?
`----
rfc's etc come in play once you start digging into internals of said
protocols. humble suggestion would be to start in a top->down
manner. first as a user of these, and then go 'down the stack' (so to
speak) if it strikes your fancy. 

if you don't know it already, richard-steven's networking books would
serve as an indispensable guide on your journey.

have fun !

-- 
kind regards
anupam

      parent reply	other threads:[~2015-07-10  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 17:56 Knowledge of Protocols Mohit .
2015-07-09 18:34 ` Valdis.Kletnieks at vt.edu
2015-07-10  3:24 ` Anupam Kapoor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874mlcpud1.fsf@fatcat.parallelwireless \
    --to=anupam.kapoor@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.