home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Education Sampler 1992 [NeXTSTEP]
/
Education_1992_Sampler.iso
/
NeXT
/
Misc
/
HigherEducationMailbox.mbox
/
Archives_provide_val_.attach
/
May_91
/
network.418
< prev
next >
Wrap
Text File
|
1991-05-21
|
7KB
|
200 lines
{\rtf0\ansi{\fonttbl\f0\fnil Times-Roman;\f3\fswiss Helvetica;\f2\fmodern Ohlfs;}
\paperw13660
\paperh13360
\margl0
\margr340
{\colortbl\red0\green0\blue0;}
\pard\tx720\tx6120\f0\b0\i0\ul0\fs28\li360 Q: What is an Ethernet Address?\
Q: What is an IP Address?\
Q: General Questions about the Internet, TCP/IP?\
Q: What else can I read about the Internet?\
\f3\b\fs36 \
\qc
\pard\tx1152\tx2304\tx3456\tx4608\tx5760\tx6912\tx8064\tx9216\tx10368\tx11520\fc0 Introduction to Networking\
\pard\tx720\tx6120\qc\li360 on the NeXT Computer\
\ql \
\fs24 \
\pard\tx720\tx1440\tx2160\tx2860\fs32\li360 • Ethernet Address
\fs36 \
\b0\fs32 • Six bytes (48 bits)\
• Hardware address, unique for each machine\
• Typical notation is hex, using colons (:) to separate bytes; e.g. 0:0:f:0:23:c0\
• Typically, on the NeXT computer, eliminate leading zeros\
• 0:0:f:0:23:c0 OK\
\
\pard\tx720\tx1440\li360 \
\b • IP Address
\fs36 \
\b0\fs32 • IP = Internet Protocol\
• Four bytes\
• Software address, used by networking protocols\
\fi-360\li720 • Typical notation is hex or decimal, using dots (.) to separate bytes (though sometimes not); e.g. (all these are the
\b same
\b0 address!):\
\fi0\li360 \
\pard\tx720\tx1440\tx2160\f2\fs20\li360 • 193.18.2.147\
• c1.12.2.93\
• c1.12.02.93\
• C1.12.02.93\
• c1120293\
• 0xC1120293\
\f3\fs32 \
\pard\tx720\tx1440\li360 • Three (well, four) classes of addresses\
\
\pard\tx1080\tx2160\tx3960\tx5760\tx7200\f0\b\fs28\li360 Network High-Order Bits in Bits in\
Class Bits Network Part Host Part\
\b0 A 0 8 24\
B 10 16 16\
C 110 24 8\
D 1110 EXPERIMENTAL MULTICAST\
\
\pard\tx720\tx1440\f3\fs32\li360 • Ranges of network numbers:\
\b \
\pard\tx720\tx2160\tx3620\f0\li360 Class Hex Decimal\
\b0 A 01–7E 1–126\
B 80–BF 128–191\
C C0–DF 192–223\
D E0–FE 224–254\
\f3 \
\pard\tx720\tx1440\li360 • Three special network numbers\
\pard\tx720\tx1440\tx2160\li360 • 7F, 127: Loopback address (127.1, 127.0.0.1)
\pard\tx720\tx1440\li360 \
• 00, 0: Broadcast\
• FF, 255: Broadcast\
\
\
\b • Protocols\
\
\b0 • IP — Internet Protocol\
• Host-to-host addressing\
• Routing\
• Packet forwarding, fragmentation, reassembly\
• UDP — User Datagram Protocol\
• Unreliable (i.e., does not guarantee delivery)\
• Simple\
• Peer-to-peer addressing, optional checksums\
• TCP — Transmission Control Protocol\
• Reliable (i.e., in order, unduplicated)\
• Flow control\
• Out-of-band indication of urgent data\
• ICMP — Internet Control Message Protocol\
• XNS — Xerox Network Systems [not supported]\
\f0\fc0 \
\pard\tx720\tx6120\li360\fc0 The reader is referred to RFC1177, for additional questions and answers about the Internet. The following text, taken from RFC1177, explains how to get RFCs and what they are.\
\pard\tx1152\tx2304\tx3456\tx4608\tx5760\tx6912\tx8064\tx9216\tx10368\tx10820\fc0 \
\pard\tx1152\tx2304\tx3456\tx4608\tx5760\tx6912\tx8064\tx9216\tx10368\tx11520\li360\fc0 What is an RFC?\
\
The Request for Comments documents (RFCs) are working notes of the\
Internet research and development community. A document in this\
series may be on essentially any topic related to computer\
communication, and may be anything from a meeting report to the\
specification of a standard. Submissions for Requests for\
Comments may be sent to the RFC Editor, Jon Postel\
(POSTEL@ISI.EDU).\
\
Most RFCs are the descriptions of network protocols or services,\
often giving detailed procedures and formats providing the\
information necessary for creating implementations. Other RFCs\
report on the results of policy studies or summarize the work of\
technical committees or workshops.\
\
While RFCs are not refereed publications, they do receive\
technical review from either the task forces, individual technical\
experts, or the RFC Editor, as appropriate. Currently, most\
standards are published as RFCs, but not all RFCs specify\
standards.\
\
Anyone can submit a document for publication as an RFC.\
Submissions must be made via electronic mail to the RFC Editor.\
RFCs are distributed online by being stored as public access\
files, and a short message is sent to the distribution list\
indicating the availability of the memo. Requests to be added to\
this distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL.\
\
The online files are copied by interested people and printed or\
displayed at their sites on their equipment. (An RFC may also be\
returned via electronic mail in response to an electronic mail\
query.) This means that the format of the online files must meet\
the constraints of a wide variety of printing and display\
equipment.\
\
Once a document is assigned an RFC number and published, that RFC\
is never revised or re-issued with the same number. There is\
never a question of having the most recent version of a particular\
RFC. However, a protocol (such as File Transfer Protocol (FTP))\
may be improved and re-documented many times in several different\
RFCs. It is important to verify that you have the most recent RFC\
on a particular protocol. The "IAB Official Protocol Standards"\
[2] memo is the reference for determining the correct RFC to refer\
to for the current specification of each protocol.\
\
How do I obtain RFCs?\
\
RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname\
RFC:RFCnnnn.TXT or RFC:RFCnnnn.PS (where "nnnn" refers to the\
number of the RFC). Login with FTP, username "anonymous" and\
password "guest". The NIC also provides an automatic mail service\
for those sites which cannot use FTP. Address the request to\
SERVICE@NIC.DDN.MIL and in the subject field of the message\
indicate the RFC number, as in "Subject: RFC nnnn" (or "Subject:\
RFC nnnn.PS" for PostScript RFCs).\
\
RFCs can also be obtained via FTP from NIS.NSF.NET. Using FTP,\
login with username "anonymous" and password "guest"; then connect\
to the RFC directory ("cd RFC"). The file name is of the form\
RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC). The\
NIS also provides an automatic mail service for those sites which\
cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and\
leave the subject field of the message blank. The first line of\
the text of the message must be "SEND RFCnnnn.TXT-1", where nnnn\
is replaced by the RFC number.\
\
Requests for special distribution should be addressed to either\
the author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless\
specifically noted otherwise on the RFC itself, all RFCs are for\
unlimited distribution.\
\
Which RFCs are Standards?\
\
See "IAB Official Protocol Standards" (currently, RFC 1140) [2].\
\
\
\pard\tx360\fs28\li360 QA418\
\
Valid for 1.0\
Valid for 2.0\
\