Datakom høsten 20021 Datakommunikasjon høsten 2002 Mandag 11. november Repitisjon.

Presentasjon om: "Datakom høsten 20021 Datakommunikasjon høsten 2002 Mandag 11. november Repitisjon."— Utskrift av presentasjonen:

1 Datakom høsten 20021 Datakommunikasjon høsten 2002 Mandag 11. november Repitisjon

2 Datakom høsten 20022 Hva skal dere lære? zHva er Internett zNettverkskort zProtokoller zAdressering zApplikasjoner zISDN zLAN zWAN zISP zASP zEthernet zARP zTCP/IP zBro zSvitsj zRuter zFW/Brannmur zDNS zSNMP zSMTP

3 Datakom høsten 20023

4 4 Tele-/datakommunikasjonsnett PSTN IN - Node Telecom Management System Tactical and Strategic Military Networks Internet LAN GSM

5 Datakom høsten 20025 Hypertext Transfer Protocol HTTP zBenyttes av WWW zProtokoll for overføring av HTML zKan overføre tekst, lyd, bilder osv. zTransaksjonsorientert klient/tjener protokoll zVanligvis mellom en Web browser (klient) og Web server (tjener) zBenytter TCP zTilstandsløs yHver transaksjon behandles separat (Keep-Alive) yEn ny TCP forbindelse for hver transaksjon yTerminerer forbindelsen når transaksjonen er komplett

6 Datakom høsten 20026 Telnet og Rlogin zInnlogging fra en maskin til en annen over nettet zBenytter seg av klient-tjener begrepet zTelnet er en standard applikasjon som er implementert i alle TCP/IP applikasjoner zRlogin kommer fra Berkley Unix og ble utviklet for pålogging mellom to Unix systemer zTelnet er mer kompleks enn Rlogin

7 Datakom høsten 20027 FTP (File Transfer Protocol) zInternett standard for filoverføring zFTP protokoll yKontroll forbindelse yServer gjør en ”passive open” på port 21 yKlient gjør en ”active open” til port 21 yData overføres fra port 20 på FTP serveren

8 Datakom høsten 20028 DNS - Domain Name System zMapper mellom hostnavn og IP-adresse (og omvendt) zBenyttes av TCP/IP applikasjoner zDistribuert, hierarkisk zBenytter både TCP og UDP som transport, port nummer 53 zEksempler yDNS QueryDNS Query yDNS ReplyDNS Reply RFC1034RFC1034, RFC1035RFC1035

9 Datakom høsten 20029 What’s a protocol? a human protocol and a computer network protocol: Hi Got the time? 2:00 TCP connection req. TCP connection reply. Get http://gaia.cs.umass.edu/index.htm time

10 Datakom høsten 200210 A Communications Model zSource yGenerates data to be transmitted zTransmitter yConverts data into transmittable signals zTransmission System yCarries data zReceiver yConverts received signal into data zDestination yTakes incoming data

11 Datakom høsten 200211 Simplified Communications Model - Diagram

12 Datakom høsten 200212 Networking zPoint to point communication not usually practical yDevices are too far apart yLarge set of devices would need impractical number of connections zSolution is a communications network

13 Datakom høsten 200213 Simplified Network Model

14 Datakom høsten 200214 WAN - Wide Area Networks zStore geografiske områder zBestår av en rekke noder zAlternative teknologier yLinesvitsjing (Circuit switching) yPakkesvitsjing (Packet switching) yFrame relay yAsynchronous Transfer Mode (ATM)

15 Datakom høsten 200215 LAN - Local Area Networks zEn eller flere bygninger zEies vanligvis av den som henger utstyr på lokalnettet zHøyere datahastigheter enn WAN yEthernet 10 eller 100 Mbit/s zTidligere kun kringasting, dvs alle kan lytte på nettet zNå mer og mer svitsjede systemer, dvs kan segmentere nettet

16 Datakom høsten 200216 Home networks Typical home network components: zADSL or cable modem zrouter/firewall zEthernet zwireless access point wireless access point wireless laptops router/ firewall cable modem to/from cable headend Ethernet (switched)

17 Datakom høsten 200217 Circuit Switching zDedikert kommunikasjonsvei mellom partene så lenge kommunikasjonen pågår. zEksempel: Telefonnettet

18 Datakom høsten 200218 Circuit Switching: FDMA and TDMA Frequency Division Multiplexing Access frequency time Time Division Multiplexing Access frequency time 4 users Example:

19 Datakom høsten 200219 Packet Switching zDatapakker sendes enkeltvis zDatapakkene behøver ikke ta samme vei gjennom nettet zDatapakkene sendes fra node til node mellom avsender og mottaker zBrukes mellom datamaskiner zEksempel: Datapak basert på X.25

20 Datakom høsten 200220 Pakkesvitsjing A B C 10 Mbs Ethernet 1.5 Mbs 45 Mbs D E statistical multiplexing queue of packets waiting for output link

21 Datakom høsten 200221 Asynchronous Transfer Mode zATM zLittle overhead for error control zFixed packet (called cell) length zAnything from 10Mbps to Gbps zConstant data rate using packet switching technique

22 Datakom høsten 200222 Integrated Services Digital Network zISDN zLaget for å erstatte PSTN, dvs analog telefoni zPrøveprosjekt i Norge høsten 1989 zBle først populært når det kunne benyttes for å koble seg mot Internett

23 Datakom høsten 200223 ISDN kanaler Grunnaksess (Basic Access): 2 B-kanaler 1 D-kanal Utvidet aksess (Primary rate Access): 30 B-kanaler 1 D-kanal

24 Datakom høsten 200224 ADSL – Assymetric Digital Subscriber Line  Telenor tilbyr (h astighet inn/ut): y384 / 128 Kb/s laste ned lyd og bilde, samt gjøre flere ting på en gang y 704 / 128 Kb/s laste ned filmklipp, programvare og andre store filer y 1024 / 256 Kb/s laste ned og sende ut store filer raskt og effektivt

25 Datakom høsten 200225 Internet protocol stack zapplication: supporting network applications yftp, smtp, http ztransport: host-host data transfer ytcp, udp znetwork: routing of datagrams from source to destination yip, routing protocols zlink: data transfer between neighboring network elements yppp, ethernet zphysical: bits “on the wire” application transport network link physical

26 Datakom høsten 200226 Internetworking Protocols

27 Datakom høsten 200227 Kommunikasjonslagene (referert til OSI) ApplicationPresentationSession Ethernet IP ARP ICMP TCPUDP NetworkTransportData LinkPhysicalApplicationTransportNetworkData Link PPP FTPHTTP DNS OSI Internet-TCP/IP SMTP

28 Datakom høsten 200228 Sikkerhet zAutentisering (identifikasjon) zAksesskontroll (aksess til ressurser) zKonfidensialitet (informasjon holdes hemmelig) zIntegritetstjeneste (data skal være korrekte) zTilgjengelighet (informasjonen skal være tilgjengelig for de som er autorisert) zCIA – Confidentiality Integrity Availability

29 Datakom høsten 200229 Symmetrisk kryptering Cleartext Cleartext Encryption Algorithm Ciphertext Ciphertext EncipherDecipher Secret Key

30 Datakom høsten 200230 Asymmetrisk kryptering One Key to Encipher Another Key to Encipher Cleartext Cleartext Encryption Algorithm Ciphertext Ciphertext EncipherDecipher

31 Datakom høsten 200231 IPSec – IP Security zSikkerhetsmekanisme for beskyttelse av VPN zVPN – Virtual Private Network zVPN over Internett yMellom avdelingskontorer yMellom hjemmekontor og jobb yMellom leverandør og kunde

32 Datakom høsten 200232 IPSec sikkerhetstjenester zKonfidensialitet yInformasjonen krypteres zIntegritet yEn veis hash funksjon zAutentisering yMAC (hash + hemmelighet) yDigital signatur

33 Datakom høsten 200233 PING ping 193.69.136.8 Pinging 193.69.136.8 with 32 bytes of data: Reply from 193.69.136.8: bytes=32 time=81ms TTL=127 Reply from 193.69.136.8: bytes=32 time=48ms TTL=127 Reply from 193.69.136.8: bytes=32 time=50ms TTL=127 Reply from 193.69.136.8: bytes=32 time=49ms TTL=127 Ping statistics for 193.69.136.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 81ms, Average = 57ms

34 Datakom høsten 200234 Informasjon om IP på maskin ipconfig -all Ethernet adapter Local Area Connection: Connection-specific DNS Suffix. : halden.scandpower.no Description........... : 3Com EtherLink XL 10/100 PCI or Complete PC Management NIC (3C905C-TX) Physical Address......... : 00-50-DA-DD-2E-5E DHCP Enabled........... : No IP Address............ : 193.69.136.78 Subnet Mask........... : 255.255.255.0 Default Gateway......... : 193.69.136.54 DNS Servers........... : 193.69.136.53

35 Datakom høsten 200235 ARP - Address Resolution Protocol (IP til MAC adresse) arp -a Interface: 193.69.136.78 on Interface 0x2 Internet Address Physical Address Type 193.69.136.34 00-60-b0-3d-82-74 dynamic 193.69.136.54 00-10-5a-66-21-78 dynamic 193.69.136.60 00-50-da-4f-31-8c dynamic 193.69.136.61 00-60-97-17-2a-48 dynamic 193.69.136.91 00-60-08-49-2a-fe dynamic 193.69.136.115 08-00-09-70-2c-8e dynamic 193.69.136.133 08-00-09-87-fe-29 dynamic

36 Datakom høsten 200236 Traceroute Address: Time: Seq: Results: 192.168.1.1 <10ms 1 56 bytes received. 80.212.232.0 16ms 2 56 bytes received. 146.172.167.65 16ms 3 56 bytes received. 146.172.202.57 31ms 4 168 bytes received. 146.172.202.37 16ms 5 168 bytes received. 146.172.250.229 16ms 6 168 bytes received. 146.172.248.66 31ms 7 56 bytes received. 193.156.90.3 16ms 8 56 bytes received. 193.75.3.62 15ms 9 56 bytes received. www.vg.no [193.69.165.20] 31ms 9 52 bytes received.

37 Datakom høsten 200237 Standards zRequired to allow for interoperability between equipment zAdvantages yEnsures a large market for equipment and software yAllows products from different vendors to communicate zDisadvantages yFreeze technology yMay be multiple standards for the same thing

38 Datakom høsten 200238 Standards Organizations zInternet Society yInternet Architecture Board (IAB) yInternet Engineering Task Force (IETF) yInternet Engineering Steering Group (IESG) zISO - International Standard for Organization yJTC – Joint Technical Committee zITU-T (tidligere CCITT) yITU- International Telecommunication Union y14 study groups zATM forum

39 Datakom høsten 200239 Network applications: some jargon Process: program running within a host. zwithin same host, two processes communicate using interprocess communication (defined by OS). zprocesses running in different hosts communicate with an application-layer protocol z user agent: software process, interfacing with user “above” and network “below”. yimplements application-level protocol yWeb: browser yE-mail: mail reader ystreaming audio/video: media player

40 Datakom høsten 200240 Client-server paradigm Typical network app has two pieces: client and server application transport network data link physical application transport network data link physical Client: zinitiates contact with server (“speaks first”) ztypically requests service from server, zWeb: client implemented in browser; e-mail: in mail reader request reply Server: zprovides requested service to client ze.g., Web server sends requested Web page, mail server delivers e-mail

41 Datakom høsten 200241 Application-layer protocols (cont). API: application programming interface zdefines interface between application and transport layers zsocket: Internet API ytwo processes communicate by sending data into socket, reading data out of socket Q: how does a process “identify” the other process with which it wants to communicate? yIP address of host running other process y“port number” - allows receiving host to determine to which local process the message should be delivered

42 Datakom høsten 200242 What transport service does an app need? Data loss zsome apps (e.g., audio) can tolerate some loss zother apps (e.g., file transfer, telnet) require 100% reliable data transfer Timing z some apps (e.g., Internet telephony, interactive games) require low delay to be “effective” Bandwidth zsome apps (e.g., multimedia) require minimum amount of bandwidth to be “effective” zother apps (“elastic apps”) make use of whatever bandwidth they get

43 Datakom høsten 200243 Transport service requirements of common apps Application file transfer e-mail Web documents real-time audio/video stored audio/video interactive games financial apps Data loss no loss loss-tolerant no loss Bandwidth elastic audio: 5Kb-1Mb video:10Kb-5Mb same as above few Kbps up elastic Time Sensitive no yes, 100’s msec yes, few secs yes, 100’s msec yes and no

44 Datakom høsten 200244 Internet transport protocols services TCP service: zconnection-oriented: setup required between client, server zreliable transport between sending and receiving process zflow control: sender won’t overwhelm receiver zcongestion control: throttle sender when network overloaded zdoes not providing: timing, minimum bandwidth guarantees UDP service: z unreliable data transfer between sending and receiving process z does not provide: connection setup, reliability, flow control, congestion control, timing, or bandwidth guarantee

45 Datakom høsten 200245 Internet apps: application, transport protocols Application e-mail remote terminal access Web file transfer streaming multimedia remote file server Internet telephony Application layer protocol smtp [RFC 821] telnet [RFC 854] http [RFC 2068] ftp [RFC 959] proprietary (e.g. RealNetworks) NSF proprietary (e.g., Vocaltec) Underlying transport protocol TCP TCP or UDP typically UDP

46 Datakom høsten 200246 ftp: the file transfer protocol ztransfer file to/from remote host zclient/server model yclient: side that initiates transfer (either to/from remote) yserver: remote host zftp: RFC 959 zftp server: port 21 file transfer FTP server FTP user interface FTP client local file system remote file system user at host

47 Datakom høsten 200247 ftp: separate control, data connections zftp client contacts ftp server at port 21, specifying TCP as transport protocol ztwo parallel TCP connections opened: ycontrol: exchange commands, responses between client, server. “out of band control” ydata: file data to/from server zftp server maintains “state”: current directory, earlier authentication FTP client FTP server TCP control connection port 21 TCP data connection port 20

48 Datakom høsten 200248 ftp commands, responses Sample commands: zsent as ASCII text over control channel  USER username  PASS password  LIST return list of file in current directory  RETR filename retrieves (gets) file  STOR filename stores (puts) file onto remote host Sample return codes z status code and phrase (as in http) z331 Username OK, password required z125 data connection already open; transfer starting z425 Can’t open data connection z452 Error writing file

49 Datakom høsten 200249 DNS: Domain Name System People: many identifiers: ySSN, name, passport # Internet hosts, routers: yIP address (32 bit) - used for addressing datagrams y“name”, e.g., gaia.cs.umass.edu - used by humans Q: map between IP addresses and name ? Domain Name System: z distributed database implemented in hierarchy of many name servers z application-layer protocol host, routers, name servers to communicate to resolve names (address/name translation) ynote: core Internet function, implemented as application- layer protocol ycomplexity at network’s “edge”

50 Datakom høsten 200250 DNS name servers zno server has all name-to- IP address mappings local name servers: yeach ISP, company has local (default) name server yhost DNS query first goes to local name server authoritative name server: yfor a host: stores that host’s IP address, name ycan perform name/address translation for that host’s name Why not centralize DNS? z single point of failure z traffic volume z distant centralized database z maintenance doesn’t scale!

51 Datakom høsten 200251 DNS: Root name servers zcontacted by local name server that can not resolve name zroot name server: ycontacts authoritative name server if name mapping not known ygets mapping yreturns mapping to local name server b USC-ISI Marina del Rey, CA l ICANN Marina del Rey, CA e NASA Mt View, CA f Internet Software C. Palo Alto, CA i NORDUnet Stockholm k RIPE London m WIDE Tokyo a NSI Herndon, VA c PSInet Herndon, VA d U Maryland College Park, MD g DISA Vienna, VA h ARL Aberdeen, MD j NSI (TBD) Herndon, VA 13 root name servers worldwide

52 Datakom høsten 200252 Simple DNS example host surf.eurecom.fr wants IP address of gaia.cs.umass.edu 1. contacts its local DNS server, dns.eurecom.fr 2. dns.eurecom.fr contacts root name server, if necessary 3. root name server contacts authoritative name server, dns.umass.edu, if necessary requesting host surf.eurecom.fr gaia.cs.umass.edu root name server authorititive name server dns.umass.edu local name server dns.eurecom.fr 1 2 3 4 5 6

53 Datakom høsten 200253 DNS example Root name server: zmay not know authoritative name server zmay know intermediate name server: who to contact to find authoritative name server requesting host surf.eurecom.fr gaia.cs.umass.edu root name server local name server dns.eurecom.fr 1 2 3 4 5 6 authoritative name server dns.cs.umass.edu intermediate name server dns.umass.edu 7 8

54 Datakom høsten 200254 DNS: iterated queries recursive query: zputs burden of name resolution on contacted name server zheavy load? iterated query: zcontacted server replies with name of server to contact z“I don’t know this name, but ask this server” requesting host surf.eurecom.fr gaia.cs.umass.edu root name server local name server dns.eurecom.fr 1 2 3 4 5 6 authoritative name server dns.cs.umass.edu intermediate name server dns.umass.edu 7 8 iterated query

55 Datakom høsten 200255 DNS: caching and updating records zonce (any) name server learns mapping, it caches mapping ycache entries timeout (disappear) after some time zupdate/notify mechanisms under design by IETF yRFC 2136 yhttp://www.ietf.org/html.charters/dnsind-charter.html

56 Datakom høsten 200256 DNS records DNS: distributed db storing resource records (RR) z Type=NS  name is domain (e.g. foo.com)  value is IP address of authoritative name server for this domain RR format: (name, value, type,ttl) zType=A  name is hostname  value is IP address zType=CNAME  name is alias name for some “cannonical” (the real) name www.ibm.com is really servereast.backup2.ibm.com  value is cannonical name zType=MX  value is name of mailserver associated with name

57 Datakom høsten 200257 The Web: the http protocol http: hypertext transfer protocol zWeb’s application layer protocol zclient/server model yclient: browser that requests, receives, “displays” Web objects yserver: Web server sends objects in response to requests zhttp1.0: RFC 1945 zhttp1.1: RFC 2068 PC running Explorer Server running NCSA Web server Mac running Navigator http request http response

58 Datakom høsten 200258 Hypertext Transfer Protocol HTTP zBenyttes av WWW zProtokoll for overføring av HTML zKan overføre tekst, lyd, bilder osv. zTransaksjonsorienter klient/tjener protokoll zVanligvis mellom en Web browser (klient) og Web server (tjener) zBenytter TCP zTilstandsløs yHver transaksjon behandles separat yEn ny TCP forbindelse for hver transaksjon yTerminerer forbindelsen når transaksjonen er komplett

59 59 SNMP – Simple Network Management Protocol Request Response Unsolicited trap ManagerAgent Network Management Station Network Management ProtocolManaged Node (Management Information)

60 60 SNMP protokollen ManagerAgent GetRequest, GetNextRequest, SetRequest GetResponse Trap Port 161 Port 162

61 61 SNMP innkapsling LLC/MAC header IP header UDP header SNMP melding LLC/MAC trailer Data Link nivåNettverks- nivå Transport- nivå Applikasjons- nivå SNMP innkapsling:

62 62 SNMPv1 melding En SNMPv1 melding består av 3 deler: Versjons nummer Community string En av de 5 SNMP PDUene

63 Datakom høsten 200263 Internet Mail zUser agent, dvs Outlook, Eudora, Pegasus osv zMail transfer Agent, dvs Microsoft Exchange, Sendmail zSMTP - Simple Mail Transfer Protocol yTCP/IP yKun sending av tekst zMIME - Multi-purpose Internet Mail Extension ySending av bilder, video osv zPOP 3 - Post Office Protocol ver 3 zIMAP - Internet Message Access Protocol zMX-records (Mail Exchange records) Del an DNS (Domain Name System)

64 Datakom høsten 200264 SMTP Mail Flyt

65 Datakom høsten 200265 User Agent (mail program) zLese og sende mail zOpsjoner: yVideresending til andre ySvarsfunksjon yFiltrering av innkommende mail til ulike mail bokser ySignatur fil yAdresslister, aliases

66 Datakom høsten 200266 Mail Transfer Agent (MTA) zAnsvarlig for å sende mailen gjennom nettet zBaseres på SMTP (Simple Mail Transfer Protocol) zSMTP er en enkel ASCII protokoll zBenytter TCP og port 25 for å opprette en forbindelse mellom to MTA-er

67 Datakom høsten 200267 Sammensetning av en mail zEnvelopes yBrukes av Message Transfer Agent zHeaders yBrukes av User Agent zBody yInnholdet i mailen (tekst og vedlegg)

68 Datakom høsten 200268 Envelopes - eksempel Received: from sara.halden.scandpower.no ([193.69.136.35]) by Received: from sara.halden.scandpower.no ([193.69.136.35]) by janis.halden.scandpower.no with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RCM02KCM; Mon, 20 Aug 2001 12:41:19 +0200 Received: from fw.scandpower.no (mail.hrp.no [158.36.61.51]) by sara.halden.scandpower.no (8.9.3/8.9.3) with SMTP id MAA12382 for ; Mon, 20 Aug 2001 12:43:02 +0200 Received: from mail.hrp.no ([158.36.61.51]) by fw.scandpower.no via smtpd (for sara.halden.scandpower.com [193.69.136.35]) with SMTP; 20 Aug 2001 10:44:06 UT Received: from pcthorbjornb (pc-thorbjornb.hrp.no [158.36.44.62]) by mail.hrp.no (8.10.1/8.9.0) with SMTP id f7KAlXK14155; Mon, 20 Aug 2001 12:47:33 +0200 (METDST)

69 Datakom høsten 200269 Header - eksempel zMessage-ID: zFrom: Per Hansen zTo: Bjorn-Arild.Kydland@scandpower.no Bjorn-Arild.Kydland@scandpower.no zSubject: E-mail security

70 Datakom høsten 200270 SMTP-kommandoer (RFC 821) zHELO zMAIL FROM: zRCPT TO: zDATA z. zQUIT

71 Datakom høsten 200271 MX-records zBrukes for å fortelle omverdenen om hvem som er mail server zDel av DNS (Domain Name System) zMX-recorden for en domene forteller i prioritert rekkefølge hvor mailen skal sendes

72 Datakom høsten 200272 MX-record eksempel zMX-record for scandpower.no 1. prioritet: bill.halden.scandpower.no 2. prioritet: mail.globalone.no  Mail leveres til mail.globalone.no hvis mailserver bill er nede eller forbindelsen til Internett er nede

73 Datakom høsten 200273 POP 3 zPost Office Protocol number 3 zProtokoll for å hente mail fra mail server til en mail klient (f.eks Outlook eller Eudora) zBruker TCP og port 110 zBaserer seg på enkle ASCII kommandoer

74 Datakom høsten 200274 POP3 kommandoer zUSER username zPASS password zSTAT [gir antall uleste meldinger] zLIST (n) 8gir størrelse på melding n] zRETR n [hent melding nr n] zDELE n [slett melding nr n] zQUIT

75 Datakom høsten 200275 Internet Message Access Protocol - IMAP zMail klient zTilsvarende som POP3, men all behandling av mail foregår på mailserveren zPOP3 henter mailen ned til User Agent

76 Datakom høsten 200276 MIME – Multipurpose Internet Mail Extension zUtvidelse av SMTP for å kunne overføre filer som ikke er 7-bit ASCII zMIME informasjon i mail: yMIME-Version yContent-Type yContent-Transfer-Encoding y(Content-Description) y(Content-ID)

77 Datakom høsten 200277 MIME – Content Type zText zImage zAudio zApplication (Word, Postscript, ) zMultipart (Mixed, alternative)

78 Datakom høsten 200278 MIME – Content-transfer encoding zForteller hvordan innholdet av mailen er kodet z Fem forskjellige kode formater er definert y7 bits ASCII yQuoted Printable ybase64 y8 bits som inneholder linjer ybinær koding, 8 bit data uten linjer

79 Datakom høsten 200279 Quoted Printable z7 bit ASCII med alle karakterer 127 kodes som likhetstegn + verdien av tegnet som to hexadecimale tegn zeks. bokstaven ”å” kodes som =E5 zKarakteresettet ISO-8859 gir å=229 desimalt 229=11100101 z1110=E z1110=5 z”å” kodes som =E5

80 Datakom høsten 200280 Base 64 Encoding

81 Datakom høsten 200281 Base 64 encoding zTre bytes med data kodes som fire 6 bits karakterer zOrginale data: Hi! H i ! 01001000 01101001 00100001 (24 bit) 010010 000110 100100 100001 00010010 00000110 00100100 00100001 S G k h zDatamengden øker med 25%

82 Datakom høsten 200282 MIME - eksempel zMIME-Version: 1.0 zX-Mailer: Internet Mail Service (5.5.2653.19) zContent-Type: text/plain; zcharset="iso-8859-1" zContent-Transfer-Encoding: quoted-printable

83 Datakom høsten 200283 MIME eks. Word fil som vedlegg MIME-Version: 1.0 Content-Type: multipart/mixed; Content-Type: text/plain; charset="iso-8859-1" Content-Type: application/msword; Content-Transfer-Encoding: base64