1 / 26

Name Services

Name Services. Vidya Satyanarayanan. Why do we need Name Services?. Requirements for name spaces. Allow simple but meaningful names to be used Potentially infinite number of names Structured to allow similar subnames without clashes to group related names

joseph-carroll
Télécharger la présentation

Name Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Name Services Vidya Satyanarayanan

  2. Why do we need Name Services?

  3. Requirements for name spaces • Allow simple but meaningful names to be used • Potentially infinite number of names • Structured • to allow similar subnames without clashes • to group related names • Allow re-structuring of name trees • for some types of change, old programs should continue to work • Management of trust

  4. URL http://www.cdk3.net:8888/WebExamples/earth.html DNS lookup Resource ID (IP number, port number, pathname) 138.37.88.61 8888 WebExamples/earth.html ARP lookup (Ethernet) Network address file 2:60:8c:2:b0:5a Socket Web server Composed naming domains used to access a resource from a URL

  5. URI Uniform Resource Identifiers (URI) offer a general solution for any type of resource. There two main classes: URL Uniform Resource Locator • typed by the protocol field (http, ftp, nfs, etc.) • resources cannot be moved between domains URN Uniform Resource Name • Solves the dangling problem of URL. • Given URN it return the URL. • requires a universal resource name lookup service - a DNS-like system for all resources • Format of URN: urn:<nameSpace>:<name-within-namespace> • e.g. urn:ISBN:021-61918-0

  6. NS2 2 Name 1 NS1 servers Client 3 NS3 A client iteratively contacts name servers NS1–NS3 in order to resolve a name Name Resolution: Navigation methods Iterative navigation Used in: DNS: Client presents entire name to servers, starting at a local server, NS1. If NS1 has the requested name, it is resolved, else NS1 suggests contacting NS2 (a server for a domain that includes the requested name). NFS: Client segments pathnames (into 'simple names') and presents them one at a time to a server together with the filehandle of the directory that contains the simple name.

  7. NS2 NS2 2 2 4 3 1 1 NS1 NS1 client client 3 5 4 NS3 NS3 Recursive Non-recursive server-controlled server-controlled Non-recursive and recursive server-controlled navigation A name server NS1 communicates with other name servers on behalf of a client DNS offers recursive navigation as an option, but iterative is the standard technique. Recursive navigation must be used in domains that limit client access to their DNS information for security reasons.

  8. DNS - The Internet Domain Name System • A distributed naming database • Name structure reflects administrative structure of the Internet • Rapidly resolves domain names to IP addresses • exploits caching heavily • typical query time ~100 milliseconds • Scales to millions of computers • partitioned database • caching • Resilient to failure of a server • replication

  9. a.root-servers.net (root) uk purdue.edu ns1.nic.uk yahoo.com .... (uk) ns.purdue.edu (purdue.edu) co.uk ac.uk... ns0.ja.net (ac.uk) * .purdue.edu ic.ac.uk qmw.ac.uk... alpha.qmw.ac.uk dns0.dcs.qmw.ac.uk dns0-doc.ic.ac.uk (qmw.ac.uk) (dcs.qmw.ac.uk) (ic.ac.uk) dcs.qmw.ac.uk *.dcs.qmw.ac.uk *.ic.ac.uk *.qmw.ac.uk DNS name servers Note: Name server names are in italics, and the corresponding domains are in parentheses.Arrows denote name server entries authoritative path to lookup: jeans-pc.dcs.qmw.ac.uk

  10. DNS server functions and configuration • Main function is to resolve domain names for computers, i.e. to get their IP addresses (Host name resolution) • caches the results of previous searches until they pass their 'time to live' • Other functions: • get mail host for a domain • reverse resolution - get domain name from IP address • Host information - type of hardware and OS • Well-known services - a list of well-known services offered by a host • Other attributes can be included (optional)

  11. DNS resource records Record type Meaning Main contents A A computer address IP number NS An authoritative name server Domain name for server CNAME The canonical name for an alias Domain name for alias SOA Marks the start of data for a zone Parameters governing the zone WKS A well-known service description List of service names and protocols PTR Domain name pointer (reverse Domain name lookups) HINFO Host information Machine architecture and operating system MX Mail exchange List of < TXT Text string Arbitrary text

  12. DNS issues • Name tables change infrequently, but when they do, caching can result in the delivery of stale data. • Clients are responsible for detecting this and recovering • Its design makes changes to the structure of the name space difficult. For example: • merging previously separate domain trees under a new root • moving sub trees to a different part of the structure (e.g. if Scotland became a separate country, its domains should all be moved to a new country-level domain.

  13. Directory and discovery services • Directory service:- 'yellow pages' for the resources in a network • Retrieves the set of names that satisfy a given description • e.g. X.500, LDAP, MS Active Directory Services • (DNS holds some descriptive data, but: • the data is very incomplete • DNS isn't organised to search it) • Discovery service:- a directory service that also: • is automatically updated as the network configuration changes • meets the needs of clients in spontaneous networks (Section 2.2.3) • discovers services required by a client (who may be mobile) within the current scope, for example, to find the most suitable printing service for image files after arriving at a hotel. • Examples of discovery services: Jini discovery service, the 'service location protocol', the 'simple service discovery protocol' (part of UPnP), the 'secure discovery service'.

  14. Music service Alarm gateway service Internet Hotel wireless network Discovery service Camera TV/PC Guest's Laptop PDA devices Revision: Spontaneous networks • Easy connection of guest's devices • wireless network • automatic configuration • Easy integration with local services • discovery of services relevant to guest's needs

  15. admin Printing 1. ‘finance’ service Mobile client lookup service? admin Client Lookup service Network 2. Here I am: ..... 4. Use printing admin, finance service Lookup 3. Request service Corporate Printing printing & receive proxy service infoservice finance Service discovery in Jini • Jini services register their interfaces and descriptions with the Jini lookup servicesin their scope • Clients find the Jini lookup services in their scope by IP multicast • Jini lookup service searches by attribute or by interface type

  16. Case Study of Global Name Service • Designed and implemented to provide facilities for resource location, mail addressing and authentication. • GNS manages a naming database, composed of a tree of directories holding names and values. • Each directory is assigned an integer which serves as the unique directory identifier (DI). • The values stored at the leaves of the directory tree are organized into value trees. • Names in GNS has 2 parts: <directory name, value name>.

  17. DI: 599 (EC) UK FR DI: 543 DI: 574 AC DI: 437 QMW DI: 322 Peter.Smith password mailboxes Alpha Beta Gamma GNS directory tree and value tree for user Peter.Smith

  18. DI: 633 (WORLD) Well-known directories: #599 = #633/EC NORTH AMERICA EC #642 = #633/NORTH AMERICA DI: 599 DI: 642 CANADA US UK FR DI: 543 DI: 574 DI: 732 Accommodating the change of structure • Integrating 2 separate GNS – • Integrate the database rooted at the EC directory and another directory rooted at NORTH AMERICA. • When the client refers to the name </UK/AC/QMW, Peter.Smith> with EC as the root, will it still be valid? • <#599/UK/AC/QMW,Peter.Smith> will work.

  19. DI: 633 (WORLD) Well-known directories: #599 = #633/EC EC NORTH AMERICA #642 = #633/NORTH AMERICA DI: 599 DI: 642 US US CANADA UK FR DI: 457 DI: 543 DI: 574 DI: 732 #633/EC/US Restructuring the directory • Suppose US becomes part of the EC, then names beginning WORLD/NORTH AMERICA/US will no longer work. • So we insert a “symbolic link” in place of the original US entry which acts as a redirection to the US directory in its new location.

  20. Summary of GNS • GNS addresses the needs for scalability and re-configurability. • The solution adopted for merging & moving directory trees has a lot of overload.

  21. X.500 Directory Service • Satisfies the descriptive queries, designed to discover the names and attributes of other users or system resources. • Range of Queries – • White pages: e.g. access to obtain a user’s electronic mail address. • Yellow pages: e.g. obtaining the names of all the garages specializing in the repair of a car. • The data stored is organized in a tree structure with named nodes. • Supports wide range of attributes,that are stored at each node • Access both by name and by searching with required attributes. • The name tree is called the Directory Information Tree (DIT) and the entire directory structure including the data is called the Directory Information Base (DIB).

  22. Servers – Directory Service Agents (DSA). Clients – Directory User Agents (DUA). DUA DSA DSA DSA DUA DSA DSA DUA DSA

  23. X.500 Service (root) ... France (country) Great Britain (country) Greece (country) ... ... BT Plc (organization) University of Gormenghast (organization) ... Computing Service (organizationalUnit) ... Department of Computer Science (organizationalUnit) Engineering Department (organizationalUnit) ... Departmental Staff (organizationalUnit) ... ely (applicationProcess) Research Students (organizationalUnit) ... ... ... Alice Flintstone (person) Pat King (person) James Healey (person) Janet Papworth (person) ... Relation between DIB entries and OOPs

  24. Methods to access the directory • read: An absolute or relative name for an entry is given, together with the attributes to be read. • search: • This is an attribute based access request. A base name and a filter expression is specified as arguments. • Returns a list of names (Domain Names) for all the entries below the base node for which the filter evaluates to TRUE. • Searching is very costly when it is applied to a large portions of directory tree.

  25. Administration and updating of the DIB • Interface includes operations for adding, deleting and modifying entries. • Relies on extensive use of replication and caching technologies. LDAP – Lightweight directory Access Protocol The Standard interface to X.500 uses LDAP. The DUA accesses X.500 directory services directly over TCP/IP. Replaces the ASN.1 encoding with textual encoding. LDAP can be used as an interface to any Directory Service if it obeys the LDAP specification. LDAP provides secure access to directory data through authentication.

  26. Summary Name services: • refer the binding of resource names to addresses (and other attributes) • Names are resolved to give addresses and other attributes • Goals : • Scalability (size of database, access traffic (hits/second), update traffic) • Reliability • Trust management (authority of servers) • Issues • exploitation of replication and caching to achieve scalability without compromising the distribution of updates • navigation methods Directory and discovery services: • 'yellow pages' retrieval by attributes • dynamic resource registration and discovery

More Related