1. Naming

2. Names play a very important role in all computer system. A name is a string of bits or characters that used to refer to an entity – eg:- recourse such as hosts, printers, disks and files. Entities can be operated. – eg printer offers an interface containing operations for printing a document, requesting the status of a print job etc. Entity such as a n/w connection may provide operations for sending and receiving data, setting quality-of-service parameters, requesting the status etc..

3. Names denote entities in a distributed system. To operate on an entity, we access it at an access point. Access points are entities named by an address. A location-independent name for an entity E, is independent from the addresses of the access points offered by E.

4. Naming To operate an entity it is necessary to access it for which we need an access point. The name of the access point is called address. In a distributed system a typical example of an access point is a host in the n/w with its address, combination of IP address and port number. An entity may change its access point, eg when a laptop moves to another location, it is often assigned a different IP address An address is a special kind of name, it refers to an access point of an entity

5. Naming An access point is tightly associated with an entity. An entity may easily change an access point or an access point may be reassigned to a different entity. If an entity offers more than one access point, it is not clear which address to use as a reference. Eg many organization distribute their web service across several servers, if we would use the addresses of these servers as a reference, it is not clear which address should be chosen as the best one.

6. A better solution is to have a single name for the web service independent from the addresses of the different web servers Such independent name is called location independent.

7. True Identifiers Pure name: One with no meaning; just a random string used for comparison. Identifier: A name with these properties: –Each identifier refers to at most one entity –Each entity referred to by at most one identifier –An identifier always refers to the same entity (prohibits reusing an identifier) An identifier need not necessarily be a pure name, i. e., it may have content.

8. Naming A true identifier is a name that has the following properties 1) each entity is referred to by at most one identifier 2) an identifier always refers to the same entity By using identifiers it become much easier to unambiguously refer to an entity

9. If an address can be reassigned to a different entity, we cannot use an address as an identifier. Eg the use of telephone no, which are reasonably stable in the sense that a telephone no for some time refers to the same person or organization

10. Addresses and identifiers are two important types of names that are each used for very different purpose In many computer systems addresses and identifiers are represented in machine-readable form only, that is in the form of bit strings – Eg memory address, Ethernet address Another important type of name that used by humans, also referred to as human-friendly names. It is generally represented as a character string.

11. Decomposing a name into different parts A client needs to know the address of the FTP server named ftp.cs.vu.nlftp.cs.vu.nl First resolve nl to find the server NS(nl) responsible for names that end with nl. After the rest of the name is passed to the server NS(nl)

12. This server may then resolve the name vu to the server NS(vu.nl) responsible for names that end with vu.nl who can further handle the remaining name ftp.cs ftp.cs This leads to routing the name resolution request as NS(.)-> NS(nl)->NS(vu.nl)->address of ftp.cs.vu.nlftp.cs.vu.nl Where NS(.) denotes the server that can return the address of NS(nl) also called the root server NS(vu.nl) will return the actual address of the FTP server.

13. Flat Naming In many case identifiers are simply random bit strings, which we conveniently refer to as unstructured or flat names Broadcasting and Multicasting Consider a distributed system built on a n/w. In the LAN all computers are connected to a single cable. Locating an entity in such environment is simple- a message containing the identifier of the entity is broadcast to each machine and each machine is requested to check whether it has that entity. Only the machine that can offer an access point for the entity send a real message containing the address of that access point

14. This principle is used in the internet Address Resolution Protocol (ARP) to find the data-link address of a machine when given only an IP address A machine broadcast a packet on the local n/w asking who is the owner of a given IP address When the message arrives at a machine, the receiver checks whether it should listen to the requested IP address If so it sends a reply packet

15. Broadcasting become inefficient when the n/w grows. Ie too many hosts may be interrupted by request they cannot answer. One possible solution is to switch to multicasting, by which only a restricted group of hosts receives the request

16. Multicasting can also be used to locate entities in n/w. – Eg internet support network level multicasting by allowing hosts to join a specific multicast group. Such group are identified by a multicast address. When a host sends a message to a multicast address, the n/w layer provides a best-effort service to deliver that message to all group members A multicast address can be used as a general location service for multiple entities

17. When computers are connects to the locally available n/w, it is dynamically assigned an IP address. In addition it joins a specific multicast group. When a process wants to locate computer A, it sends a “where is A ?” request to the multicast group. If A is connected it responds with its current IP address.

18. Forwarding Pointers Locating mobile entities is make use of forwarding pointers. When an entity moves from A to B it leaves behind in A a reference to its new location at B. A client can look up the current address by following the chain of forwarding pointers. Drawbacks All intermediate locations in a chain will have to maintain their part of the chain of forward pointers.

19. Each forwarding pointer is implemented as (client stub, server stub) pair A server stub contain either a local reference to the actual object or a local reference to a remote client stub for that object. When ever an object moves from address space A to B it leaves behind a client stub in its place in A and installs a server stub that refers to it in B

20. Figure 5-1. The principle of forwarding pointers using (client stub, server stub) pairs.

21. Figure 5-2. Redirecting a forwarding pointer by storing a shortcut in a client stub.

23. Home base Approaches Broadcasting and multicasting is difficult to implement efficiently in large scale n/ws. long forwarding chain pointers may broken. Another approach to supporting mobile entities in large-scale n/w is home location Which keeps track of the current location of an entity.

24. The home location is often chosen to be the place where an entity was created. All mobile host has a fixed IP address. All communications to that IP address is initially directed to the mobile host’s home agent. This home agent is located in the local area network corresponding to the network address contained in the mobile host’s IP address

25. Whenever the mobile host moves to another network, it requests a temporary address that it can use for communication. This care-of address is registered at the home agent. When the home agent receives a packet for the mobile host, it looks up the host’s current location. If the host is on the current local network the packet is simply forwarded. Otherwise it is tunneled to the host’s current location and sent to the care-of address.At the same time, the sender of the packet is informed of the host’s current location

26. Drawback To communicate with a mobile entity, a client first has to contact the home, which may be completely different location. The result is an increase in communication latency. A drawback of the home-based approach is the use of a fixed home location. It must be ensure that the home location always exists. Otherwise contacting the entity will become impossible. So register the home at a traditional naming service and to let a client to be relatively stable, that location can be effectively cached after it has been looked up.

27. Home-Based Approaches Figure 5-3. The principle of Mobile IP.

28. Distributed Hash tables DHT a lookup service DHT system uses an m bit identifier space to assign randomly-chosen identifiers to nodes as well as keys to specific entities. The number m bits is usually 128 or 160 depending on the hash fun. An entity with key k falls under the jurisdiction of the node with the smallest identifier id>= k. This node is referred to as the successor of k and denoted as succ(k).

29. The main issue in DHT based system is to efficiently resolve a key k to the address of succ(k) Each node p keep track of the successor succ(p+1) as well as its predecessor pred(p) In that case whenever a node p receives a request to resolve key k, it will simply forward the request to one of its two neighbors.

30. FTp[i]=SUCC(p+2 i-1 ) Q=FTp[j]<=k<FTp[j+1]

32. Hierarchical Approaches

33. In a hierarchical scheme, a network is divided into a collection of domains. There is a single top-level domain that spans the entire network. Each domain can be subdivided into multiple, smaUer subdomains. A lowest-level domain, called a leaf domain, typically corresponds to a local-area network in a computer network or a cell in a mobile telephone network.

34. To keep track of the whereabouts of an entity, each entity currently located in a domain D is represented by a location record in the directory node dir(D). A location record for entity E in the directory node N for a leaf domain D contains the entity's current address in that domain. In contrast, the directory node N' for the next higher- level domain D' that contains D, will have a location record for E containing only a pointer to N.

35. An entity may have multiple addresses, for example if it is replicated. If an entity has an address in leaf domain D 1 and D2 respectively, then the directory node of the smallest domain containing both D 1 and D 2, will have two pointers,one for each subdomain containing an address.

37. lookup operation a client wishing to locate an entity E, issues a lookup request to the directory node of the leaf domain D in which the client resides. If the directory node does not store a location record for the entity,then the entity is currently not located in D. Consequently, the node forwards the request to its parent. Note that the parent node represents a larger domain than its child. If the parent also has no location record for E, the lookup request is forwarded to a next level higher, and so on.

39. Update operations Consider an entity E that has created a replica in leaf domain D for which it needs to insert its address. The insertion is initiated at the leaf node dir(D) of D which immediately forwards the insert request to its parent. The parent will forward the insert request as well, until it reaches a directory node M that already stores a location record for E. Node M will then store a pointer in the location record for E, referring to the child node from where the insert request was forwarded. At that point, the child node creates a location record for E, containing a pointer to the next lower-level node from where the request came. This process continues until we reach the leaf node from which the insert was initiated. The leaf node, finally, creates a record with the entity's address in the associated leaf domain.

41. Structured Naming

42. Flat names are good for machines, but are generally not very convenient for humans to use. Structured names are composed from simple human readable names

43. Name Spaces Names are commonly organized into what is called a name space. They represented as a labeled directed graph with two types of nodes. – Leaf node – Directory node A leaf node represented a named entity and has the property that it has no outgoing edges A leaf node generally stores information on the entity, such as in the case of file systems in which a leaf actually contains the complete file it is representing

44. A directory node has a number of outgoing edges, each labeled with a name. Each directory node in a naming graph is considered as yet another entity in a distributed system. A directory node store a table in which an outgoing edge is represented as a pair (edge label, node identifier) such a table is called directory table.

45. Structured Naming A general naming graph

46. In the figure has one node namely n0 which has only outgoing and of no incoming edge, such node is called root node of the naming graph. Each path in the naming graph can be referred to by the sequence of labels corresponding to the edge in that path such as. N: N refers to the first node in the path Such a sequence is called path name. If the first path name is the root of the naming graph it is called an absolute path name. Otherwise it is called relative path name.

47. Naming graphs are implemented in file system. Instead of writing edges labels to represent a path name, path name in file system are generally represented as a single string in which the labels are separated by a special character (“/”) In the figure instead of using n0 we can use /home/steen/mbox When there are several paths that lead the same node, that node can be represented by different path name Eg node n5 can be referred to by /home/steen/keys as well as /keys. All resources such as processes, hosts, I/O devices and n/w interfaces are named in the same fashion

48. Name space offer a convenient mechanism for storing and retrieving information about entities by means of names. i.e. path name should be possible to look up any information stored in the node The process of looking up a name is called name resolution Consider a path name N:. Resolution of this name starts at node N of the naming graph, where the name label1 is looked up in the directory table. Resolution then continued to looking up name label2 and so on. Assume that the named path actually exists, resolution stop at the last node referred by label n, by returning the content of the node.

49. A global name is a name that denotes the same entity, no matter where the name is used in a system. A local name is a name whose interpretation depends on where that name is being used.

50. Name Resolution Name resolution is the process by which resolvers and name servers cooperate to find data in the name space. – Remember, not a “search” To find information anywhere in the name space, a name server only needs the names and IP addresses of the name servers for the root zone (the “root name servers”)

51. Name Resolution A name server receiving a query from a resolver looks for the answer in its data first and then in its cache – If it doesn’t have the requested data and is not in the name server then other servers must be consulted

52. ping www.nominum.com. Name Resolution Example Let’s look at the resolution process step-by- step: annie.west.sprockets.com

53. What’s the IP address of www.nominum.com? Name Resolution Example The workstation annie asks its configured name server, dakota, for www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com dakota.west.sprockets.com

54. Name Resolution Example The name server dakota asks a root name server, m, for www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com m.root-servers.net dakota.west.sprockets.com What’s the IP address of www.nominum.com?

55. Name Resolution Example The root server m refers dakota to the com name servers This type of response is called a “referral” ping www.nominum.com. annie.west.sprockets.com m.root-servers.net dakota.west.sprockets.com Here’s a list of the com name servers. Ask one of them.

56. Name Resolution Example The name server dakota asks a com name server, f, for www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com m.root-servers.net dakota.west.sprockets.com What’s the IP address of www.nominum.com? f.gtld-servers.net

57. Name Resolution Example The com name server f refers dakota to the nominum.com name servers ping www.nominum.com. annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com Here’s a list of the nominum.com name servers. Ask one of them.

58. Name Resolution Example The name server dakota asks a nominum.com name server, ns1.sanjose, for www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net What’s the IP address of www.nominum.com?

59. Name Resolution Example The nominum.com name server ns1.sanjose responds with www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net Here’s the IP address for www.nominum.com

60. Name Resolution Example The name server dakota responds to annie with www.nominum.com’s address ping www.nominum.com. annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net

61. ping ftp.nominum.com. Resolution Process (Caching) After the previous query, the name server dakota now knows: – The names and IP addresses of the com name servers – The names and IP addresses of the nominum.com name servers – The IP address of www.nominum.com Let’s look at the resolution process again annie.west.sprockets.com

62. ping ftp.nominum.com. What’s the IP address of ftp.nominum.com? Resolution Process (Caching) The workstation annie asks its configured name server, dakota, for ftp.nominum.com’s address annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net

63. ping ftp.nominum.com. What’s the IP address of ftp.nominum.com? Resolution Process (Caching) dakota has cached an NS record indicating ns1.sanjose is an nominum.com name server, so it asks it for ftp.nominum.com’s address annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net

64. ping ftp.nominum.com. Here’s the IP address for ftp.nominum.com Resolution Process (Caching) The nominum.com name server ns1.sanjose responds with ftp.nominum.com’s address annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net

65. ping ftp.nominum.com. Here’s the IP address for ftp.nominum.com Resolution Process (Caching) The name server dakota responds to annie with ftp.nominum.com’s address annie.west.sprockets.com f.gtld-servers.net m.root-servers.net dakota.west.sprockets.com ns1.sanjose.nominum.net

66. Name resolution can take place only if we know how and where to start. Knowing how and where to start name resolution is generally referred as a closure mechanism. It deals with selecting initial node, which name resolution start. Eg consider the string representation of a file name such as /home/steen/mbox To resolve this name, necessary to access to the directory table of the root node Closure Mechanism

67. In this case it would have been necessary to have access to the root node. so resolving a file name requires, some mechanism has already been implemented by which the resolution process can start.

68. An alias is another name for the same entity. In terms of naming graphs, there are basically 2 ways to implement an alias. First approach is to simply allow multiple absolute path names to refer to the same node in a naming graph. This approach is shown below Linking and Mounting

70. In which node n5 can be referred to by 2 different path name /keys and /home/steen/keys are called hard links to node n5. The second approach is to represent an entity by a leaf node say N, but instead of storing the address, the node stores an absolute path name. When first resolving an absolute path name that leads to N, name resolution will return the path name stored in N at which point it can continue with resolving that new path name. This principle corresponds to the use of symbolic links

71. The concept of a symbolic link explained in a naming graph.

72. In this example the path name /home/steen/keys where refers to a node containing the absolute path name /keys is symbolic link to node n5 Mounting Name resolution can also be used to merge different name spaces in a transparent way. In terms of our naming model a mounted file system corresponds to letting a directory node store the identifier of a directory node from different name space. The directory node storing the node identifier is called mount point.

73. The directory node in the foreign name space is called a mounting point. Normally the mounting point is the root of a name space. A directory node that acts as a mount point and stores all the necessary information for identifying and accessing the mounting point in the foreign name space.

74. Linking and Mounting root output file personal file A B C D root others users Student faculty root network file clients bob tom john ken ClientServer 1Server 2 Mounting point Linking: allow multiple absolute path names to refer to the same node Mounting: allow a node to refer to a node from a different name space

75. Implementation of a Name Space A name space forms the heart of a naming service. ie a service that allows users and processes to add, remove and lookup names A naming service is implemented by name servers. If a distributed system is restricted to a local area n/w it is often feasible to implement a naming service by means of only a single name server In large scale distributed system with many entities spread across a large geographical area, it is necessary to distribute the implementation of a name space over multiple name server.

76. To efficiently implement a name space for a large-scale, it is usually organized hierarchically and may be partitioned into logical layers: Global layer Administrational Layer Managerial layer

77. Global layer: formed by the highest-level nodes, e.g., root and other directory nodes logically close to the root. The directory tables in these nodes are rarely changed.

78. administrational layer: formed by the directory nodes managed within single organization. The nodes in this layer are relatively stable although less stable than those in global layers.

79. managerial layer: formed by the nodes that may change regularly, e.g., nodes representing hosts in the LAN. The nodes in this layer are also maintained by end users of a DS.

80. Structured Naming Implementation of a Name Space An example partitioning of the DNS name space, including Internet- accessible files, into three layers.

81. The fig shows an example of the partitioning of part of the DNS name space including the names of files within an organization that can be accessed through the internet. The name space is divided into non overlapping parts called zones. A zone is a part of the name space that is implemented by a separate name server. If a name server fails, a large part of the name space will be unreachable because name resolution cannot proceed beyond the falling server

82. Name Space Distribution A comparison between name servers for implementing nodes from a large-scale name space partitioned into a global layer, as an administrational layer, and a managerial layer. ItemGlobalAdministrationalManagerial Geographical scale of networkWorldwideOrganizationDepartment Total number of nodesFewMany Vast numbers Responsiveness to lookupsSecondsMillisecondsImmediate Update propagationLazyImmediate Number of replicasManyNone or fewNone Is client-side caching applied?Yes Sometimes

83. Domain Name System One of the largest distributed naming service is used today is the internet DNS.DNS is used for looking up IP addresses of hosts and mail servers. DNS Name Space The DNS name space is hierarchically organized as a rooted tree.A label has a maximum length of 63 characters the length of a complete path name is restricted to 255 characters.

84. The string representation of a path name consists of listing its labels, starting with rightmost one, and separating the labels by a dot The root is represented by a dot. eg the path name root: is represented by the string flits.cs.vu.nl which includes the rightmost dot to indicate the root node

85. Each node in the DNS name space has exactly one incoming edge, the label attached to a node’s incoming edge is also used as the name for that node A sub tree is called a domain. A path name to its root node is called domain name. The content of a node is formed by a collection of resource records.There are different types of resource records The major ones are shown below

86. The DNS Name Space The most important types of resource records forming the contents of nodes in the DNS name space. Type of record Associated entity Description SOAZoneHolds information on the represented zone AHostContains an IP address of the host this node represents MXDomain Refers to a mail server to handle mail addressed to this node SRVDomainRefers to a server handling a specific service NSZone Refers to a name server that implements the represented zone CNAMENode Symbolic link with the primary name of the represented node PTRHostContains the canonical name of a host HINFOHostHolds information on the host this node represents TXTAny kindContains any entity-specific information considered useful

87. Domain Name System An SOA (start of authority) – resource record contain information such as an e- mail address of the system administrator responsible for the represented zone, the name of the host where data on the zone can be fetched and so on. An A(address) record – represents a particular host in the internet – The A record contains an IP address for that host to allow communication

88. Domain Name System MX (mail exchange) – record which is representing a mail server. – That mail server will handle all incoming mail addressed to users in the domain SRV record – the server itself identified by means of a name along with the name of a protocol. – An important advantage of SRV record is that client need no longer know the DNS name of the host providing a specific service

89. Domain Name System Nodes that represent a zone contain one or more NS(name server) records. Each node in the name space can store an NS record referring to the name server that implements. DNS distinguishes aliases from what are called canonical names. Each host is assumed to have a canonical, or primary name.

90. Domain Name System An alias is implemented by means of node storing a CNAME record containing the canonical name of a host. DNS maintains a inverse mapping of IP addresses to host names by means of PTR (pointer) records. To accommodate the lookups of host names when given only an IP address. DNS maintains a domain named in-addr.arpa, which contains nodes that represent internet hosts and which are named by the IP address of the represented host. Eg- host www.cs.vu.nl has IP address 130.37.20.20www.cs.vu.nl DNS creates a node named 20.20.37.130.in-addr.arpa, which is used to store the canonical name of that host

91. Domain Name System The last 2 record types are HINFO records and TXT records An HINFO (host info) record – It is used to store additional information on a host such as its machine type and operating system. TXT records – are used for any other kind of data that a user finds useful to store about the entity represented by the node.

92. Domain Name System DNS implementation DNS name space can be divided into a global layer and an administrational layer as show in figure. The managerial layer, which is generally formed by local file system is formally not part of DNS.Each zone is implemented by a name server. Updates for a zone are normally handled by the primary name server.Updates take place by modifying the DNS database local to the primary server.

93. Domain Name System DNS implementation Secondary name servers do not access the database directly, but instead request the primary server to transfer its content. A DNS database is implemented as a small collection of files of which contains all the resource records for all the nodes in a particular zone. This approach allows nodes to be simply identified by means of their domain name

94. DNS Implementation (1) DNS database for the zone cs.vu.nl.

95. The fig shows a small part of the file that contains most of the information for the cs.vu.nl domain The file shows the contents of several nodes that are part of the cs.vu.nl domain, where each node is identified by means of its domain name

96. ATTRIBUTE-BASED NAMING (Directory Services) As more information is being made available it becomes important to effectively search for entities. This approach requires that a user can provide merely a description of what he is looking for. There are many ways in which descriptions can be provided, but a popular one in distributed systems is to describe an entity in terms of (attribute, value) pairs, generally referred to as attribute-based naming. In this approach, an entity is assumed to have an associated collection of attributes. Each attribute says something about that entity.

97. Directory Services Attribute-based naming systems are also known as directory services, whereas systems that support structured naming are generally called naming systems. With directory services, entities have a set of associated attributes that can be used for searching. In some cases, the choice of attributes can be relatively simple., For example, in an e-mail system, messages can be tagged with attributes for the sender, recipient, subject, and so on.

98. Resource Description Framework (RDF). Research has been conducted on unifying the ways that resources can be described. In the context of distributed systems, one particularly relevant development is the resource description framework (RDF). Fundamental to the RDF model is that resources are described as triplets consisting of a subject, a predicate, and an object. For example, (Person, name,Alice) describes a resource Person whose name is Alice. In RDF, each subject,predicate, or object can be a resource itself. This means that Alice may be implemented as reference to a file that can be subsequently retrieved

99. Hierarchical Implementations: LDAP A common approach to tackling distributed directory services is to combine structured naming with attribute-based naming. LDAP - Lightweight Directory Access Protocol An LDAP directory service consists of a number of records, usually referred to as directory entries. Each record is made up of a collection of (attribute, value) pairs, where each attribute has an associated type. A distinction is made between single-valued attributes and multiple-valued attributes.

101. The attributes Country, Organization, and Organizational Unit could be used to form the globally unique name. The collection of all directory entries in an LDAP directory service is called a directory information base (DIB). An important aspect of a DIB is that each record is uniquely named so that it can be looked up. Such a globally unique name appears as a sequence of naming attributes in each record. Each naming attribute is called a relative distinguished name, or RDN for short.

102. As in DNS, the use of globally unique names by listing RDNs in sequence, leads to a hierarchy of the collection of directory entries, which is referred to as a directory information tree (DIT). A DIT essentially forms the naming graph of an LDAP directory service in which each node represents a directory entry.

103. Figure 5-23. (a) Part of a directory information tree. (b) Two directory entries having Host.Name as RDN.

104. Implementing an LDAP directory service proceeds in much the same way as implementing a naming service such as DNS, except that LDAP supports more lookup operations. When dealing with a large-scale directory, the DIT is usually partitioned and distributed across several servers, known as directory service agents (DSA). Clients are represented by what are called directory user agents, or simply DUAs. A DUA is similar to a name resolver in structured-naming services. A DUA exchanges information with a DSA according to a standardized access protocol.