Quality of service, Domain Name system services

GopinathSamydurai 26 views 63 slides May 14, 2024
Slide 1
Slide 1 of 63
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
45
Slide 46
46
Slide 47
47
Slide 48
48
Slide 49
49
Slide 50
50
Slide 51
51
Slide 52
52
Slide 53
53
Slide 54
54
Slide 55
55
Slide 56
56
Slide 57
57
Slide 58
58
Slide 59
59
Slide 60
60
Slide 61
61
Slide 62
62
Slide 63
63

About This Presentation

QoS & DNS


Slide Content

25.1
QoS,
Application Layer
Paradigms, DNS
Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.

QUALITYOFSERVICE
Qualityofservice(QoS)isaninternetworkingissue
thathasbeendiscussedmorethandefined.Wecan
informallydefinequalityofserviceassomethinga
flowseekstoattain.
Topics discussed in this section:
Flow Characteristics Flow Classes
24.23

Figure24.15Flowcharacteristics
24.24

TECHNIQUES TOIMPROVEQoS
InSection24.5wetriedtodefineQoSintermsofits
characteristics.Inthissection,wediscusssome
techniquesthatcanbeusedtoimprovethequalityof
service.Webrieflydiscussfourcommonmethods:
scheduling,trafficshaping,admissioncontrol,and
resourcereservation.
Topics discussed in this section:
Scheduling Traffic Shaping
Resource Reservation Admission Control
24.25

Figure24.16FIFOqueue
24.26

Figure24.17Priorityqueuing
24.27

Figure24.18Weightedfairqueuing
24.28

Figure24.19Leakybucket
24.29

Figure24.20Leakybucketimplementation
24.30

A leaky bucket algorithm shapes bursty
traffic into fixed-rate traffic by averaging
the data rate. It may drop the packets if
the bucket is full.
Note
24.31

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
The token bucket allows bursty traffic at
a regulated maximum rate.
Note
24.32

Figure24.21Tokenbucket
24.33

INTEGRATEDSERVICES
Twomodelshavebeendesignedtoprovidequalityof
serviceintheInternet:IntegratedServicesand
DifferentiatedServices.Wediscussthefirstmodel
here.
Topics discussed in this section:
Signaling
Flow Specification Admission
Service Classes RSVP
ProblemswithIntegratedServices
24.34

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
Integrated Services is a flow-based QoS
model designed for IP.
Note
24.35

Figure24.22Pathmessages
24.36

Figure24.23Resvmessages
24.37

Figure24.24Reservationmerging
24.38

Figure24.25Reservationstyles
24.39

DIFFERENTIATEDSERVICES
DifferentiatedServices(DSorDiffserv)was
introducedbytheIETF(InternetEngineeringTask
Force)tohandletheshortcomingsofIntegrated
Services.
Topicsdiscussed inthissection:
DSField
24.40

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
Differentiated Services is a class-based
QoS model designed for IP.
Note
24.41

Figure24.26DSfield
24.42

Figure24.27Traffic
conditioner
24.43

24-9QoSINSWITCHEDNETWORKS
LetusnowdiscussQoSasusedintwoswitched
networks:FrameRelayandATM.Thesetwonetworks
arevirtual-circuitnetworksthatneedasignaling
protocolsuchasRSVP.
Topics discussed in this section:
QoS in Frame Relay QoS in ATM
24.44

Figure24.28Relationshipbetweentrafficcontrolattributes
24.45

Figure24.29Userrate inrelationtoBcandBc +Be
24.46

Figure24.30Service
classes
24.47

Relationshipofserviceclasses tothetotalcapacityof thenetwork
24.48

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
ApplicationLayer
•Theapplicationlayerprovidesservicestotheuser.
•Communicationisprovidedusingalogicalconnection,which
meansthatthetwoapplicationlayersassumethatthereisan
imaginarydirectconnectionthroughwhichtheycansendand
receivethemessages.
•ApplicationLayerprovidesafacilitybywhichuserscanforward
severalemailsanditalsoprovidesastoragefacility.
•Thislayerallowsuserstoaccess,retrieveandmanagefilesina
remotecomputer.
•Itallowsuserstologonasaremotehost.
5/14/2024 Dr. Shivashankar, E&CE, RRIT 28

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
ProvidingServices
•TheInternetwasoriginallydesignedforthesamepurpose:toprovideservice
tousersaroundtheworld.
•Newprotocolscanbeaddedorsomeprotocolscanberemovedorreplaced
bytheInternetauthorities.
•Sincetheapplicationlayeristheonlylayerthatprovidesservicestothe
Internetuser,itallowsnewapplicationprotocolstobeeasilyaddedtothe
Internet.
StandardApplication-LayerProtocols
•Thereareseveralapplication-layerprotocolsthathavebeenstandardizedand
documentedbytheInternetauthority.
•Eachstandardprotocolisapairofcomputerprogramsthatinteractwiththe
userandthetransportlayertoprovideaspecificservicetotheuser.
•Ex:Telnet,FTP,TFTP,SMTP,SNMP,DNS,DHCP.
NonstandardApplication-LayerProtocols
•Aprogrammercancreateanonstandardapplication-layerprogram.
•Itisthecreationofanonstandard(proprietary)protocol,whichdoesnoteven
needtheapprovaloftheInternetauthoritiesifprivatelyused.
5/14/2024 Dr. Shivashankar, E&CE, RRIT 29

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
Application-Layer Paradigms
TwoparadigmshavebeendevelopedduringthelifetimeoftheInternet:
1.theclient-serverparadigm
2.thepeer-to-peerparadigm.
TraditionalParadigm:Client-Server
•Thetraditionalparadigmiscalledtheclient-serverparadigm.
•Serviceproviderisanapplicationprogram,calledtheserverprocess;itrunscontinuously,waiting
foranotherapplicationprogram,calledtheclientprocess,tomakeaconnectionthroughthe
Internetandaskforservice.
•Theserverprocessmustberunningallthetime;theclientprocessisstartedwhentheclient
needstoreceiveservice.
•Severaltraditionalservicesarestillusingthisparadigm,includingtheWorldWideWeb(WWW)
anditsvehicleHyperTextTransferProtocol(HTTP),filetransferproto-col(FTP),secureshell(SSH),
e-mail,andsoon.
5/14/2024 Dr. Shivashankar, E&CE, RRIT 30
Figure25.2Exampleofaclient-
serverparadigm

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
Peer-to-Peer
•Anewparadigm,calledthepeer-to-peerparadigm(P2Pparadigm)hasemergedto
respondtotheneedsofsomenewapplications.
•Inthisparadigm,thereisnoneedforaserverprocesstoberunningallthetimeand
waitingfortheclientprocessestoconnect.
•Theresponsibilityissharedbetweenpeers.
•AcomputerconnectedtotheInternetcanprovideserviceatonetimeandreceive
serviceatanothertime.
•Acomputercanevenprovideandreceiveservicesatthesametime.
•Therearesomenewapplications,suchasBitTorrent,Skype,IPTV,andInternet
telephony.
5/14/2024 Dr. Shivashankar, E&CE, RRIT 31
Figure25.3Exampleofapeer-
to-peerparadigm

McGraw-Hill ©The McGraw-Hill Companies, Inc., 2000
Mixed Paradigm
•Anapplicationmaychoosetouseamixtureofthetwo
paradigmsbycombiningtheadvantagesofboth.
•Forexample,alight-loadclient-servercommunicationcanbe
usedtofindtheaddressofthepeerthatcanofferaservice.
•Whentheaddressofthepeerisfound,theactualservicecanbe
receivedfromthepeerbyusingthepeer-to-peerparadigm.
5/14/2024 Dr. Shivashankar, E&CE, RRIT 32

25.33
Figure 25.1 Example of using the DNS service
server
Typo in textbook

25.34
25-1 NAME SPACE
Tobeunambiguous,thenamesassignedtomachines
mustbecarefullyselectedfromanamespacewith
completecontroloverthebindingbetweenthenames
andIPaddresses.
Flat Name Space: hard to manage for large-scale system
Hierarchical Name Space: name has several parts
Topics discussed in this section:

25.35
25-2 DOMAIN NAME SPACE
Tohaveahierarchicalnamespace,adomainname
spacewasdesigned.Inthisdesignthenamesare
definedinaninverted-treestructurewiththerootat
thetop.Thetreecanhaveonly128levels:level0
(root)tolevel127.
Label
Domain Name
Domain
Topics discussed in this section:

25.36
Figure 25.2 Domain name space
root

25.37
Figure 25.3 Domain names and labels

25.38
Figure 25.5 Domains: subtree of the domain name space

25.39
25-3 DISTRIBUTION OF NAME SPACE
Theinformationcontainedinthedomainnamespace
mustbestored.However,itisveryinefficientandalso
unreliabletohavejustonecomputerstoresuchahuge
amountofinformation.Inthissection,wediscussthe
distributionofthedomainnamespace.
Hierarchy of Name Servers
Zone
Root Server
Primary and Secondary Servers
Topics discussed in this section:

25.40
Figure 25.6 Hierarchy of name servers

DNS: Root name servers
b USC-ISI Marina del Rey, CA
l ICANN Los Angeles, CA
e NASA Mt View, CA
f Internet Software C. PaloAlto, CA
(and 17 other locations)
i Autonomica, Stockholm (plus 3 other
locations)
k RIPE London (also Amsterdam, Frankfurt)
m WIDE Tokyo
a Verisign, Dulles, VA
c Cogent, Herndon, VA (also Los Angeles)
d U Maryland College Park, MD
g US DoD Vienna, VA
h ARL Aberdeen, MD
j Verisign, ( 11 locations)
13 root name
servers
worldwide

TLD and Authoritative Servers
Top-level domain (TLD) servers:responsible for
com, org, net, edu, etc, and all top-level country
domains uk, fr, ca, jp.
Network solutions maintains servers for com TLD
Educause for edu TLD
Authoritative DNS servers:organization’s DNS
servers, providing authoritative hostname to IP
mappings for organization’s servers (e.g., Web
and mail).
Can be maintained by organization or service
provider (paid by the organization)

25.43
Figure 25.7 Zones and domains

25.44
Two types of DNS server: A primary server
loads all information from the disk file; the
secondary server loads all information from
the primary server. Reason: redundancy
When the secondary downloads
information from the primary, it is called zone
transfer.
Note

25.45
25-4 DNS IN THE INTERNET
DNSisaprotocolthatcanbeusedindifferent
platforms.IntheInternet,thedomainnamespace
(tree)isdividedintothreedifferentsections:generic
domains,countrydomains,andtheinversedomain.
Generic Domains
Country Domains
Inverse Domain
Topics discussed in this section:

25.46
Unix: nslookup, dig
Windows: nslookup
DNS Query Commands

25.47
Figure 25.8 DNS IN THE INTERNET

25.48
Figure 25.9 Generic domains

25.49
Table 25.1 Generic domain labels

25.50
Figure 25.10 Country domains

25.51
25-5 RESOLUTION
Mappinganametoanaddressoranaddresstoa
nameiscalledname-addressresolution.
Resolver
Mapping Names to Addresses
Mapping Addresses to Names
Recursive Resolution
Caching
Topics discussed in this section:

25.52
Figure 25.12 Recursive resolution

25.53
Figure 25.13 Iterative resolution

25.54
Caching: Main Reason for the Efficiency of DNS
All DNS servers cache prior query results
Normal DNS query will not go through the
full steps of recursive/iterative resolution

25.55
25-6 DNS MESSAGES
DNShastwotypesofmessages:queryandresponse.
Bothtypeshavethesameformat.Thequerymessage
consistsofaheaderandquestionrecords;the
responsemessageconsistsofaheader,question
records,answerrecords,authoritativerecords,and
additionalrecords.
Header
Topics discussed in this section:

25.56
Figure 25.14 Query and response messages

25.57
Figure 25.15 Header format

25.58
25-7 TYPES OF RECORDS
AswesawinSection25.6,twotypesofrecordsare
usedinDNS.Thequestionrecordsareusedinthe
questionsectionofthequeryandresponsemessages.
Theresourcerecordsareusedintheanswer,
authoritative,andadditionalinformationsectionsof
theresponsemessage.
Question Record
Resource Record
Topics discussed in this section:

DNS records
DNS:distributed db storing Resource Records (RR)
Type=NS
nameis domain (e.g.
foo.com)
valueis name of
authoritative DNS server
for this domain
RR format: (name, value, type, ttl)
Type=A
nameis hostname
valueis IP address
Type=CNAME
nameis alias name for some
“canonical” (the real) name
www.ibm.com is really
servereast.backup2.ibm.com
valueis canonical name
Type=MX
valueis name of mailserver
associated with name
25.59

DNS protocol, messages
DNS protocol :queryand replymessages, both with
same message format
msg header
identification:16 bit # for
query, reply to query
uses same #
flags:
query or reply
recursion desired
recursion available
reply is authoritative
25.60

DNS protocol, messages (UDP 53)
Name, type fields
for a query
RRs in
response
to query
records for
authoritative servers
additional “helpful”
info that may be used
Let’s check a web example using Wireshark!
(MX record: nslookup –type=MX cs.ucf.edu or
dig mx cs.ucf.edu)
25.61

Inserting records into DNS
Example: just created startup “netwar”
Register name netwar.com at a registrar(e.g., Network
Solutions)
Need to provide registrar with names and IP addresses of your
authoritative name server (primary and secondary)
Registrar inserts two RRs into the com TLD server:
(netwar.com, dns1.netwar.com, NS)
(dns1.netwar.com, 212.212.212.1, A)
Put in authoritative server dns1.netwar.com
Type A record for www.netwar.com
Type CName for netwar.com (alias)
Type MX record for netwar.com (email)
Type A record for the email server
How do people get the IP address of your Web site?
25.62

25.63
DNS can use the services of UDP or TCP
using the well-known port 53.
Note