Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services

• Case study of the Global Name Service • Case study of the X.500 Directory Service • Summary

What is Name Service?

• A distinct service that is used by client to obtain attributes such as the addresses of resources or objects when given their names • Name management is separated from other services

Name and Address
• Name
– A human readable string

• Identifier
– names that are interpreted only by programs.

• Address
– Bits used by machines to locate an object

• Bind
– Association between a name and an address

• Resolve
– Translate from a name to an address – Example

Attributes

• Value of a property associated with an object • DNS
– IP address

• X.500
– Person’s email address and telephone number

Uniform Resource Identifiers • URL (Uniform Resource Locator)
– Addresses of web resources – Dangling problems: a resource may be moved

• URN (Uniform Resource Name)
– Intend to solve the dangling problems – E.g. urn:ISBN:0-201-62433-8 – Urn:net.pku.edu.cn:TR2004-10 – URN lookup service: mapping from URN to URL

Uniform Resource Identifiers • URC(Uniform Resource Characteristics)
– A description of a Web resource(metadata)

Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services • Case study of the Global Name Service • Case study of the X. the administrative domain may use entirely different naming conventions .500 Directory Service • Summary Two motivations: • Unification – It is convenient to manage the resource by to use same naming schema • Integration – Separate from the special application system – Without a common name service.

General name service requirements • Scalability – Arbitrary number of names – Arbitrary number of administrative organizations • Flexibility – A long lifetime – Accommodate variations on the organization of the set of names General name service requirements (2) • High availability – Most other systems depend upon it • Fault isolation – Isolate location failures from entire service • Tolerance of mistrust – Not all clients are trusted by all components of the system .

/etc/passwd – Resolve relative to a separate context – Potentially infinite – Different context managed by different people • Alias – The reason for having aliases is to provide for transparency – www. domain name tree of DNS • E.edu. e.cn) .g.edu.pku.Name spaces • A collection of all valid names recognized by a particular service • Require a syntactic definition • E.pku. Internal structure of a name • Hierarchic structure. directory tree of a file system • E.g.g.g. flat set of numeric or symbolic identifiers.cn( xxx.

mount file system in Unix and NFS – E.domain’s name domain names Combining name spaces • Homogeneous/heterogeneous name spaces – DNS is Homogeneous – URL is heterogeneous • Merging – E.ac.Dollimore – /…/dcs. create a higher-level root context • Heterogeneity – DCE name: /…/dcs. pku.edu.edu.g.g.qmw. cs.g.uk/files/pub/reports/TR2000-99 cell files cell principals .qmw.ac.cn • Be stored in a separated server – Naming domains are in general stored in different name servers • Domains.uk/principals/Jean.g.pku.cn – E.Naming domain • A single administrative authority – A name space for which there exists a single authority – E.

Plan 9 Name resolution • Name space is partitioned in different name servers NS2 • Iterative navigation – Client controlling – E.g.g. install configuration for multiplatform • One name space per people – E.. DNS.Customizing name spaces • One file with different names – E.g.g. NFS – A local DNS sever Client Can not reply all the Request with the help Of other servers 2 1 3 NS3 NS1 Name servers A client iteratively contacts name servers NS1–NS3 in order to resolve a name . a NFS directory mounted on different machines • One name refer to different files – E.

Server controlled navigation • Non-recursive/Recursive – Recursive type is suitable to environment where there are administrative domain prohibits NS2 2 1 client 4 NS1 3 NS3 Non-recursive server-controlled client 1 5 NS3 2 4 NS1 3 NS2 Recursive server-controlled Caching tech. in name resolution • Enhance response time • Eliminate the workload of highlevel name servers • Isolate the failures of high-level name servers .

China Even geograph-souding Domain names are conventional and are completely independent of their physical location .The Domain Name System • Original Internet Naming scheme – A central master files – Download to all hosts by FTP • Domain names [1987] – Name space is partitioned both organizationally and according to geography The DNS name space Com – Commercial organizations Edu – Universities and other educational institutions Gov – US governmental agencies Mil – US military organizations Net – Major network support centres Org – Organizations not mentioned above Int – International organizations Us – united States Uk – United Kingdom Cn .

The DNS name space • A domain name including the component “. cn gov ac edu com DNS queries • Host name resolution – From URL to IP address • Mail host location – Given a domain name. tom@dcs. return a list of domain names of hosts that can accept the mail – E.ac.g.rnx.cn” must be looked up within the tree with cn as its root.uk .

g. the architecture type or operating system of a machine • Well-known services – A list of the services run by a computer – Protocol used to obtain them (UDP & TCP) DNS name servers • DNS names are divided into Zones • Zone – Include names in the domain.DNS queries …continued • Reverse resolution – From IP to URL • Host information – E. less any sub-domains – At least two name servers for the zone – Hold name servers for the sub-domains – Domain and zones are two different concepts • Each server hold zero or more Zones – Zero zone: the caching name server – Time-to-live of secondary .

edu can be satisfied using at worst two navigation steps. DNS name resolution • Iterative navigation / recursive navigation – A query involving three component domain names sunch as www.berkeley. • Example • DNS resource types .DNS name servers …continued • Servers that a name server holds – Lower-level name servers • Child name servers – high-level name servers • One or more root name servers • Parent name server • There are 13 root server in the world.

brad.ac.2.ac.5 Www.xxx.ac.brad.5 143.uk xxx.ac.uk xxx.2.2.53.xxx.5 Www.ac.uk xxx.5 143.uk xxx.xxx.xxx.uk 143.53.uk xxx.53.brad.ac.xxx.5 143.53.53.xxx.brad.53.5 143.uk xxx.5 Www.Server controlled navigation 根服务器 xxx.53.2.53.2.uk www.5 BRAD 143.brad.xxx.xxx.ac.uk 143.brad.xxx.ac.xxx.uk AC xxx.ac.xxx.5 143.5 www.ac.xxx.2.53.53.uk xxx.5 www.5 edu.uk xxx.uk 143.2.brad.uk xxx.5 www.ac.uk xxx.uk xxx.53.ac.5 143.ac.brad.ac.brad.uk xxx.xxx.ac.53.ac.5 xxx.2.5 www.53.5 143.brad.53.2.uk xxx.uk xxx.5 www.5 Www.xxx.xxx.xxx.uk 143.xxx.5 www.xxx.brad.ac.brad.xxx.53.5 143.brad.53.53.53.xxx.ac.53.ac.cn服务器 DNS performance • Replication – Zone data are replicated on at least two name servers – Master server / secondary server •Synchronize periodically • Cache – Any server is free to cache data – Time-to-live value .uk xxx.xxx.uk xxx.53.xxx.uk 143.xxx.xxx.53.2.xxx.ac.ac.uk www.ac.xxx.2.uk 143.xxx.uk xxx.ac.53.53.2.ac.edu.ac.uk 143.2.5 143.53.ac.brad.53.ac.5 www.53.5 www.xxx.5 143.53.uk xxx.brad.uk xxx.xxx.5 143.xxx.2.2.uk xxx.53.ac.uk xxx.2.uk xxx.53.53.uk xxx.ac.xxx.uk 143.uk xxx.brad.ac.xxx.xxx.ac.2.5 143.ac.53.brad.53.2.xxx.uk 143.xxx.ac.brad.5 143.xxx.ac.uk xxx.2.uk xxx.ac.brad.2.xxx.uk 143.ac.uk xxx.ac.brad.xxx.brad.5 143.xxx.xxx.uk 143.brad.53.brad.xxx.uk HIT PKU 143.53.ac.xxx.cn服务器 主机 cn服务器 hit.xxx.53.brad.xxx.uk xxx.ac.uk xxx.2.brad.2.uk xxx.2.ac.53.brad.xxx.2.2.uk 143.ac.2.uk xxx.2.5 143.2.uk xxx.ac.2.uk xxx.uk xxx.ac.5 143.5 143.53.2.uk 143.5 143.2.uk EDU AC xxx.uk xxx.53.uk xxx.2.ac.2.brad.brad.brad.uk 主服务 xxx.xxx.uk CN UK xxx.2.uk xxx.uk xxx.brad.5 143.ac.uk 143.2.brad.uk xxx.brad.2.53.uk xxx.xxx.uk xxx.5 143.5 www.53.53.53.2.ac.5 143.5 主机 143.uk xxx.ac.ac.5 143.ac.xxx.uk xxx.ac.2.2.xxx.5 143.53.uk Www.brad.uk 143.2.2.2.uk xxx.uk www.5 www.ac.53.5 xxx.uk xxx.uk xxx.2.ac.xxx.ac.uk Www.ac.xxx.ac.brad.xxx.5 143.ac.brad.ac.xxx.xxx.uk 143.ac.5 143.xxx.uk xxx.uk xxx.2.

cache and partition • Acceptable inconsistent naming data Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services • Case study of the Global Name Service • Case study of the X.500 Directory Service • Summary .DNS performance (2) • Availability & Scalability – Achieved by a combination of replication.

500 – LDAP . value> pairs • Query – Lookup by known attributes – Return interested attributes – E.Directory services • A special kind of naming service – Searching attributes • Entries – Each entry is concerned with a set of <attribute. by his name Directory services (2) • Yellow page / white page – Directory service / Conventional naming service • Directory servers and navigation – Similar to name service • Example – Active Directory Service – X.g. query one’s telephone No.

type=laser.com/services/printer57 .g. url=http://www.Directory services (2) • Different with DNS – Convenient to description – No relation with the administrative origination – Less simplicity Discovery services • A special kind of directory service • Register the services provided in a spontaneous network • General operations – Register / lookup / de-register • E.Location=room101. colour=yes.hotelDuLac. resolution=600dpi. a registered printer ResourceClass=printer.

Jini • A lookup service – Look up services. Jini service.Jini client – A service registers an object with a set of attributes – Clients query the lookup service – Clients download service object that matches query • Leases – A limited period of time during which the service can be used How to locate lookup service in Jini? • A priori • No centralized server • Multicast to a well-know IP multicast address – Lookup services listen on the receiving socket – Lookup services announce their existence – Different lookup services provide the different multicast address • Example .

Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services • Case study of the Global Name Service • Case study of the X.500 Directory Service • Summary Introduction to GNS • Designed by DEC lab [lampson 1986] • Design objectives – Millions of computer names – Billions of email addresses for users – Long life time: accommodate changes .

Peter. value name> – E. <EC/UK/AC/QMW.Introduction to GNS • Hierarchical structure • Name space –organizational structure • Two assumption: – Update is infrequent – Slow dissemination of update is acceptation Architecture of GNS • Directory tree / value tree • Directory identifier (DI) – Unique identifier of a directory • Name of an entry – <directory name.g.Smith/password> .

how to locate /uk/ac/qmw ? Well-known directories: #599 = #633/EC #642 = #633/NORTH AMERICA DI: 599 DI: 633 (WORLD) EC NORTH AMERICA DI: 642 DI: 543 UK FR DI: 574 DI: 732 US CANADA DI: 457 .Architecture of GNS (2) • Multiple name servers – Directory tree is partitioned and stored in many servers • Replication – Each partition is replicated in several servers • Cache – Inconsistency cache data is acceptable How does GNS accommodate changes? • Merge two name space by a super-root – How to it transparent to client applications? – E.g.

i. <#599/UK/AC/QMW.g. EC • Resolve name – Working root DI + relative path • Uniquely refer to a name in the merged tree – E. Peter.Working root DI • Client agent – Store the DI of working root by client agent – E.Smith> Well-known directories • A table of well-know directories – Mapping between working root DI to new absolute path • Replication – Well-know directories are replicated at each nodes – Bottleneck of consistency • Examples .. client agent stores #599 which is the DI of “/”.g. Peter. for </UK/AC/QMW.e.Smith>.

Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services • Case study of the Global Name Service • Case study of the X.500 Architecture • General purpose directory service • Directory information tree (DIT) – Partitioned and stored in different servers – Organized according to distinguished name • Service architecture – Directory user agent (DUA) – Directory service agent (DSA) .500 Directory Service • Summary X.

Search in X.500 • DIB entry – Consist of a name and a set of attributes • Attribute definition language • Search – Query by “a base name + a filter expression” – Return a list of entries Light Directory Access Protocol (LDAP) • A distributed object naming service B1 based on LDAP C A c=China st=Hubei l=Wuhan ou=Wuda B2 ou=Tsinghua dc=Dean st=Beijing l=Beijing ou=Beida dc=Dean dc=Course dc=Teacher dc=Teacher dc=Course dc=Course dc=Dean dc=Teacher .

resolve • Name space – Syntactic rules • Multiple name servers • Cache & replication • Cases – DNS – GNS: accommodating changes – X.500 Directory Service • Summary Summary • Basics of naming service – Map between name and attributes of objects – binding.500: directory service .Chapter 9: Name Services • Introduction • Name services and the Domain Name System • Directory and discovery services • Case study of the Global Name Service • Case study of the X.

ac.uk) dns0-doc.edu dcs.ac.ic.ja.ac.ac.nic.html Web server Network address 2:60:8c:2:b0:5a Socket file DNS name servers a.cdk3.uk qmw.purdue.55 8888 WebExamples/earth.ac.ac.net (root) uk purdue.qmw.qmw.dcs.ac.qmw.ac. pathname) 55.qmw.uk) ic.Composed naming domains used to access a resource from a URL URL http://www.uk (uk) co.dcs.55.html DNS lookup Resource ID (IP number.net (ac.uk) *.ac.edu) ns0.purdue. port number.uk ac.qmw.ac.uk *.ac.uk * .55.uk *.uk (dcs.uk) .ac.net:8888/WebExamples/earth.qmw.edu (purdue.ic.uk (ic.uk (qmw.com ns.edu yahoo.uk ns1.root-servers.uk alpha.uk dns0.

Here I am: .. finance 3.. host > pairs Arbitrary text Service discovery in Jini admin Printing Client 1.. ‘finance’ lookup service? service admin Lookup service 4.. Use printing service Network Client 2. Request Corporate infoservice Printing service finance printing Lookup service . admin.DNS resource records Record type Meaning A NS CNAME SOA WKS PTR HINFO MX TXT A computer address An authoritative name server The canonical name for an alias Main contents IP number Domain name for server Domain name for alias Marks the start of data for a zone Parameters governing the zone A well-known service description List of service names and protocols Domain name pointer (reverse lookups) Host information Mail exchange Text string Domain name Machine architecture and operating system List of < preference.

Smith DI: 599 (EC) DI: 543 UK FR DI: 574 DI: 437 AC DI: 322 QMW Peter.Smith mailboxes password Alpha Beta Gamma Merging trees under a new root DI: 633 (WORLD) Well-known directories: #599 = #633/EC #642 = #633/NORTH AMERICA EC NORTH AMERICA DI: 599 DI: 642 DI: 543 UK FR US DI: 574 DI: 732 CANADA DI: 457 .GNS directory tree and value tree for user Peter.

Restructuring the directory DI: 633 (WORLD) Well-known directories: #599 = #633/EC #642 = #633/NORTH AMERICA DI: 599 US DI: 574 EC NORTH AMERICA DI: 642 DI: 543 UK FR US DI: 732 CANADA DI: 457 #633/EC/US X.500 Service Architecture DUA DSA DSA DSA DUA DSA DUA DSA DSA .

.ac. Flintstone surname Flintstone telephoneNumber +44 986 33 4604 uid alf mail alf@dcs.. France (country) Great Britain (country) Greece (country). Departmental Staff (organizationalUnit) ely (applicationProcess) Research Students (organizationalUnit) . .500 Service (root) . Department of Computer Science.....uk roomNumber Z42 userClass Research Fellow . .Flintstone Alice Flintstone A. University of Gormenghast.ac.500 directory information tree X....gormenghast...Flintstone Alice.Flintstone@dcs. BT Plc (organization) University of Gormenghast (organization) . Alice Flintstone (person) ... Departmental Staff..Part of X. An X. .uk Alice.... Pat King (person) James Healey (person) Janet Papworth (person) ..... . Computing Service (organizationalUnit) Department of Computer Science (organizationalUnit) Engineering Department (organizationalUnit) .500 DIB entry info Alice Flintstone.L.. GB commonName Alice.gormenghast.