Concepten van computernetwerken

2003-2004 - Information management2Groep T Leuven – Information department2/15

OSI Model

2003-2004 - Information management3Groep T Leuven – Information department3/15

Protocol Overview

2003-2004 - Information management4Groep T Leuven – Information department4/15

Netwerk-protocollen

ApplicationApplication

PresentationPresentation

SessionSession

TransportTransport

NetworkNetwork

Data-linkData-link

PhysicalPhysical

ApplicationApplication

TransportTransport

InternetInternet

Network InterfaceNetwork Interface

OSI Model Internet Protocol Suite

2003-2004 - Information management5Groep T Leuven – Information department5/15

Netwerk-protocollen

Network Interface

Internet

Transport

Application

ICMPICMP

TCPTCP UDPUDP

IPIP

HTTP, HTTPS, SMTP, POP, LDAP

FTP, TELNETBGP, NTP, NNTP

HTTP, HTTPS, SMTP, POP, LDAP

FTP, TELNETBGP, NTP, NNTP

DNSDHCP, RADIUS, SNMP

RIPRealAudio, CU-SeeMe

NetMeeting

DNSDHCP, RADIUS, SNMP

RIPRealAudio, CU-SeeMe

NetMeeting

ARPARP

PPPEthernet, PSTN, ISDN, Frame Relay, ATM

PPPEthernet, PSTN, ISDN, Frame Relay, ATM

2003-2004 - Information management6Groep T Leuven – Information department6/15

Hosts en routers

2003-2004 - Information management7Groep T Leuven – Information department7/15

Protocollen en interfaces

2003-2004 - Information management8Groep T Leuven – Information department8/15

Encapsulatie

User data

User dataApp.

header

Application dataTCP

header

Application dataTCP

headerIP

header

Application dataTCP

headerIP

headerEthernet

headerEthernet

trailer

TCP segment

IP datagram

Ethernet Frame

2003-2004 - Information management9Groep T Leuven – Information department9/15

Demultiplexing

2003-2004 - Information management10Groep T Leuven – Information department10/15

TCP/IP en standaardisatie

• Internet Architecture Board• Internet Research Task Force• Internet Engineering Task Force• Internet Engineering Steering Group

2003-2004 - Information management11Groep T Leuven – Information department11/15

RFC’s : Request for comment• Werkdocumenten voor de Internet Community• Standaarden worden gepubliceerd in RFC’s• Vijf classificaties:

– Required, recommended, directional, informational, and obsolete

• Ontwikkeld op basis van consensus

2003-2004 - Information management12Groep T Leuven – Information department12/15

RFC’s : Example

2328 OSPF Version 2. J. Moy. April 1998. (Format: TXT=447367 bytes)

(Obsoletes RFC2178) (Also STDO054) (Status: STANDARD)

2178 J..Moy, .OSPF yersion 2., 07/22/1997. (Pages=211) (Format=.txt)

(Obsoletes RFC1583)

1583 J. Moy, nosPF Version 2., 03/23/1994. (Pages=212)

(Format=.txt, :ps) (Obsoletes RFC1247) (Obsoleted by RFC2178)

1247 J. Moy, .OSPF Version 2n, 08/08/1991. (Pages=189)

(Format=.txt, .ps) (Obsoletes RFCl131) (Obsoleted by RFC1583)

1131 J. Moy, nosPF specificationn, 10/01/1989. (Pages=107)

(Format=.txt, .ps) (Obsoleted by RFC1247)

2003-2004 - Information management13Groep T Leuven – Information department13/15

RFC’s : ExampleMailer software MUST be able to send and receive messages of at

least 64K bytes in length (including header), and a much larger

maximum size is highly desirable.

Host software MUST handle hostnames of up to 63 characters and

SHOULD handle hostnames of up to 255 characters.

2003-2004 - Information management14Groep T Leuven – Information department14/15

Oefening

2003-2004 - Information management15Groep T Leuven – Information department15/15

Oefening• Download + bekijk rfc-index.txt• Download + lees RFC 1812 of RFC 1123• Download RFC 1918