Transcript COS 420 - Tony Gauvin`s Web Site

COS 420
Day 1
Agenda
Roll Call
 Introduction
 WebCT Overview
 Syllabus Review
 Course Overview and
Introduction

INSTRUCTOR


Tony Gauvin, Assistant Professor of ECommerce
Contact info




216 Nadeau
[email protected]
(207) 834-7519 or ext 7519
WebCT (Tony Gauvin COS 125)
Instructional Philosophy


Out-Come based education
Would rather discuss than lecture


Hate grading assignments


Requires student preparation
Especially LATE assignments
Use class interaction, assignments,
quizzes and projects to determine if
outcomes are met.
COS 420 Survival Primer

This is a 400 Level course which means
the students take a greater
responsibility for success in this course

I expect



That students show a lot of initiative
That students have read the materials in
advance of the lecture/discussion
Assignments and Projects will be of high-quality
as befitting a soon to be professional
Scope of Text

Internetworking: an overview of
concepts, terminology, and technology
underlying the TCP/IP Internet protocol
suite and the architecture of an
internet.
Objectives

You will learn


Terminology (including acronyms)
Concepts and principles






– The underlying model
– Encapsulation
– End-to-end paradigm
Naming and addressing
Functions of protocols including ARP, IP, TCP,
UDP,SMTP, FTP, DHCP, and more
Layering model
Objectives Cont’



Internet architecture and routing
Applications
You will not learn


A list of vendors, hardware products,
software products, services, comparisons,
or prices
Alternative internetworking technologies
(they have all disappeared!)
Schedule Of Topics for
Semester


Introduction
Review of








– Network hardware
– Physical addressing
Internet model and concept
Internet (IP) addresses
Higher-level protocols and the layering principle
Examples of internet architecture
Routing update protocols
Application-layer protocols
Why Study TCP/IP?


The Internet is everywhere
Most applications are distributed


They use TCP/IP for communications
Vendor Independence

Before TCP/IP and the Internet

Only two sources of network protocols



Specific vendor such as IBM or Digital Equipment
Standards bodies such as the ITU (formerly known as
CCITT)
TCP/IP

None of the above
Who Built TCP/IP?







Internet Architecture Board (IAB)
Originally known as Internet Activities Board
Evolved from Internet Research Group
Forum for exchange among researchers
About a dozen members
Reorganized in 1989 and 1993
Merged into the Internet Society in 1992
Components Of The IAB
Organization

IAB (Internet Architecture Board)


Board that oversees and arbitrates
URL is


http://www.iab.org/iab
IRTF (Internet Research Task Force)


Coordinates research on TCP/IP and
internetworking
Virtually defunct
Components Of The IAB
Organization (continued)

IETF (Internet Engineering Task Force)






Coordinates protocol and Internet engineering
Headed by Internet Engineering Steering Group
(IESG)
Divided into N areas (N is 10 plus or minus a few)
Each area has a manager
Composed of working groups (volunteers)
URL is

http://www.ietf.org
ICANN

Internet Corporation for Assigned Names and
Numbers





Formed in 1998 to subsume IANA contract
Not-for-profit managed by international board
Now sets policies for addresses and domain names
Support organizations




http://www.icann.org
Address allocation (ASO)
Domain Names (DNSO)
Protocol parameter assignments (PSO)
For fun see http://www.icannwatch.org
World Wide Web Consortium




Organization to develop common
protocols for World Wide Web
Open membership
Funded by commercial members
URL is

http://w3c.org
Internet Society






Organization that promotes the use of
the Internet
Formed in 1992
Not-for-profit
Governed by a board of trustees
Members worldwide
URL is

http://www.isoc.org
Protocol Specifications And
Documents


Protocols documented in series of
reports
Documents known as Request For
Comments (RFCs)
RFCs

Series of reports that include





TCP/IP protocols
The Internet
Related technologies
Edited by IESG, but not peer-reviewed like scientific
journals
Contain:




Proposals
Surveys and measurements
Protocol standards
Jokes
RFC continued




Numbered in chronological order
Revised document reissued under new
number
Numbers ending in 99 reserved for
summary of previous 100 RFCs
Index and all RFC’s available on-line

RFC editor Web Site

http://www.rfc-editor.org/
Requirements RFCs


Host Requirements Documents
Major revision/clarification of most TCP/IP
protocols




RFC 1122 (Communication Layers)
RFC 1123 (Application & Support)
RFC 1127 (Perspective on 1122-3)
Router Requirements


Major specification of protocols used in IP
gateways (routers)
RFC 1812 (updated by RFC 2644)
Special Subsets Of RFCs

For Your Information (FYI)



Provide general information
Intended for beginners
Best Current Practices (BCP)


Engineering hints
Reviewed and approved by IESG
A Note About RFCs

RFCs span two extremes



Protocol standards
Jokes
Question: how does one know which are
standards?

Some of my favorites

A Standard for the Transmission of IP Datagrams on
Avian Carriers (RFC 1149)




http://www.blug.linux.no/rfc1149/
The Hyper Text Coffee Pot Control Protocol (RFC 2324),
The Security Flag in the IPv4 Header (RFC 3514)
The Twelve Networking Truths (RFC 1925)
The 12 Networking Truths

1.
2.
RFC 1925, by Ross Callon
It Has To Work.
No matter how hard you push and no matter what the priority, you
can't increase the speed of light.
(corollary). No matter how hard you try, you can't make a baby in much less
than 9 months. Trying to speed this up *might* make it slower, but it won't
make it happen any quicker.
3.
4.
5.
With sufficient thrust, pigs fly just fine. However, this is not necessarily
a good idea. It is hard to be sure where they are going to land, and it
could be dangerous sitting under them as they fly overhead.
Some things in life can never be fully appreciated nor understood
unless experienced firsthand. Some things in networking can never be
fully understood by someone who neither builds commercial
networking equipment nor runs an operational network.
It is always possible to aglutenate multiple separate problems into a
single complex interdependent solution. In most cases this is a bad
idea.
The 12 Networking Truths
6. It is easier to move a problem around (for example, by moving the
problem to a different part of the overall network architecture) than it
is to solve it.
(corollary). It is always possible to add another level of indirection.
7. It is always something
(corollary). Good, Fast, Cheap: Pick any two (you can't have all three).
8. It is more complicated than you think.
9. For all resources, whatever it is, you need more.
(corollary) Every networking problem always takes longer to solve than it
seems like it should.
10. One size never fits all.
11. Every old idea will be proposed again with a different name and a
different presentation, regardless of whether it works.
(corollary). See rule 6a.
12. In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
TCP/IP Standards (STD)



Set by vote of IETF
Documented in subset of RFCs
Found in Internet Official Protocol
Standards RFC and on IETF web site


Issued periodically
Current version is RFC 3600
Internet Drafts




Preliminary RFC documents
Often used by IETF working groups
Available on-line from several
repositories
Either become RFCs within six months
or disappear
Obtaining RFCs And
Internet Drafts

Available via



– Email
– FTP
– World Wide Web


IETF report contains summary of weekly
activity


http://www.ietf.org/
http://www.isoc.org/ietfreport/
RFC Editor
Summary




TCP/IP is vendor-independent
Standards set by IETF
Protocol standards found in document
series known as Request For Comments
(RFCs)
Standards found in subset of RFCs
labeled STD
For Next Week


Read 1st 3 Chapters of Text
Start on Assignment 1

Due Jan 29, 2003