Paul Mockapetris. Domain names - implementation and specification, 1987. Internet Engineering Task Force, RFC 1035.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....unique host that provides them is on line, and this does not satisfy our requirements about check out. The choice (2) suits better our requirements, but it needs more machinery to compose conflicts among different versions of configuration items. The situation is similar to the Domain Name System [9], in which the data regarding associations between IP numbers and host names are replicated on several DNS servers. DNS servers do not rely on one large centralized name repository. Instead, each DNS server records some associations known with certainty (au thoritative associations) and some ....

P. Mockapetris. Rfc 1035 (standard: Std 13) domain names--implementation and specification. Technical report, Internet Engineering Task Force, November 1987.

....between two servers interacting for other purposes (i.e. a query) Note that the set of replicas for a given node eventually need to be made consistent (i.e. the owner should be informed) but there is no requirement that this be immediate. 6 Related Work 6. 1 Distributed Directories DNS DNS [29, 30] can be considered to be one of the cornerstones of the Internet and is possibly the most widely deployed directory service, ever. The design of DNS was a careful compromise 21 between functionality, scalability, and implementability [31] years of experience with DNS has shown that the ....

P. V. Mockapetris. Domain names - implementation and specication. Request for Comments 1035, Internet Engineering Task Force, November 1987.

....between two servers interacting for other purposes (i.e. a query) Note that the set of replicas for a given node eventually need to be made consistent (i.e. the owner should be informed) but there is no requirement that this be immediate. 6 Related Work 6. 1 Distributed Directories DNS DNS [29, 30] can be considered to be one of the cornerstones of the Internet and is possibly the most widely deployed directory service, ever. The design of DNS was a careful compromise 21 between functionality, scalability, and implementability [31] years of experience with DNS has shown that the ....

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comments 1034, Internet Engineering Task Force, November 1987.

....and memory requirements when CNs have several correspondents in the same mobile network. We therefore propose a solution based on multicast routing protocols for delivering network scope Binding Updates. The mobile network has a permanent multicast address which the MNG registers in the DNS [7, 8]. The MNG sends periodic Binding Updates containing a binding between its MNG prefix and its MNG coa to the multicast address. CNs join the multicast group using IPv6 multicast mechanisms. The Binding Update instructs CNs to add an entry in their binding cache. Before sending a datagram, the CN ....

P. Mockapetris. Domain Names - Implementation and Specification. Request for Comments 1035, Internet Engineering Task Force (IETF), November 1987.

....and memory requirements when CNs have several correspondents in the same mobile network. We therefore propose a solution based on multicast routing protocols for delivering network scope Binding Updates. The mobile network has a permanent multicast address which the MNG registers in the DNS [7, 8]. The MNG sends periodic Binding Updates containing a binding between its MNG prefix and its MNG coa to the multicast address. CNs join the multicast group using IPv6 multicast mechanisms. The Binding Update instructs CNs to add an entry in their binding cache. Before sending a datagram, the CN ....

P. Mockapetris. Domain Names - Concepts and Facilities. Request for Comments 1034, Internet Engineering Task Force (IETF), November 1987.

....3.29: KangaDirectory store and rebuild Kanga endpoints. Its class definition is shown in figure 3.30. By instantiating TiggerDirectory with a different class, you would be able to build a name service that stored simple (name,IP address) mappings similar to The Domain Name System (DNS) MC94, Moc87, Moc87] char getComment( char getKey( setKey(char ) KangaAddr getAddr( KangaDirectoryEntry addr : KangaAddr KangaDirectoryEntry(KangaDirectoryEntry ) KangaDirectoryEntry(KangaAddr ,char ) KangaDirectoryEntry operator= KangaDirectoryEntry ) about,key : char Figure 3.30: ....

....KangaDirectory store and rebuild Kanga endpoints. Its class definition is shown in figure 3.30. By instantiating TiggerDirectory with a different class, you would be able to build a name service that stored simple (name,IP address) mappings similar to The Domain Name System (DNS) MC94, Moc87, Moc87] char getComment( char getKey( setKey(char ) KangaAddr getAddr( KangaDirectoryEntry addr : KangaAddr KangaDirectoryEntry(KangaDirectoryEntry ) KangaDirectoryEntry(KangaAddr ,char ) KangaDirectoryEntry operator= KangaDirectoryEntry ) about,key : char Figure 3.30: Class ....

P. Mockapetris. Domain names - implementation and specification. Request for Comments (Standard) RFC 1035, Internet Engineering Task Force, November 1987. Obsoletes RFC0973; Updated by RFC1348.

....SLPv2 if it is not reduced. 6 Related Work Our early work on mSLP was presented as an Internet Draft in Interaction of SLP Directory Agents for Reliability and Scalability [14] The fully meshed peer relationship is used in IBGP [13] Redundancy is a basic method to ensure reliability, the DNS [11, 12] primary and secondary server architecture is a good example of this. 7 Conclusion In this paper we presented mSLP Mesh enhanced Service Location Protocol. It enhances SLP with a fully meshed peering DA architecture. mSLP can provide a reliable directory service for an SLP system. It can also ....

P. V. Mockapetris. Domain names - implementation and specification. Request for Comments 1035, Internet Engineering Task Force, November 1987.

....SLPv2 if it is not reduced. 6 Related Work Our early work on mSLP was presented as an Internet Draft in Interaction of SLP Directory Agents for Reliability and Scalability [14] The fully meshed peer relationship is used in IBGP [13] Redundancy is a basic method to ensure reliability, the DNS [11, 12] primary and secondary server architecture is a good example of this. 7 Conclusion In this paper we presented mSLP Mesh enhanced Service Location Protocol. It enhances SLP with a fully meshed peering DA architecture. mSLP can provide a reliable directory service for an SLP system. It can also ....

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comments 1034, Internet Engineering Task Force, November 1987.

....of the certificate within the tree. The authentication of a certificate requires the acquisition of all certificates and associated revocation state information within the certification path. The Secure DNS (DNSSec) Gal96, EK99] system leverages the vast installed base of the Domain Name System [Moc87] to support certificate distribution. DNS name servers perform CA functions, and the root server ( is the trusted point for all verifiers. Certification paths mirror DNS name resolution, where the path is constructed from the root to the certificate holder. Many of the proposed PKI ....

P. Mockapetris. Domain Names - Concepts and Facilities. RFC 1034, Internet Engineering Task Force, November 1987.

....separately, by a process of delegation from above. In this scenario, the URN resolution process consists of finding the server which is authoritative for the URN, and then sending it the full Path URN using the HTTP protocol. The delegation process is achieved using the Domain Name System[25, 26]. All Path URN related DNS entries would be rooted under the domain name path.int. 4.3 The dns URN scheme In this scheme[4] the Element ID component of the URN is separated into two, a naming authority and a resource identifier, e.g. dns:shells.unix.computing.subjects:zsh The naming authorities ....

P. Mockapetris. Domain names - implementation and specification. Request For Comments (Standard) RFC 1035, Internet Engineering Task Force, November 1987. !URL: ftp://ds.internic.net/rfc/rfc1035.txt ?.

....separately, by a process of delegation from above. In this scenario, the URN resolution process consists of finding the server which is authoritative for the URN, and then sending it the full Path URN using the HTTP protocol. The delegation process is achieved using the Domain Name System[25, 26]. All Path URN related DNS entries would be rooted under the domain name path.int. 4.3 The dns URN scheme In this scheme[4] the Element ID component of the URN is separated into two, a naming authority and a resource identifier, e.g. dns:shells.unix.computing.subjects:zsh The naming authorities ....

P. Mockapetris. Domain names - concepts and facilities. Request for Comments (Standard) RFC 1034, Internet Engineering Task Force, November 1987. !URL: ftp://ds.internic.net/rfc/rfc1034.txt ?.

....resources not found in the whole network need to be installed. A distributed database should be used so that a system can obtain information about the resources its peers have. Again, distributed system databases are not rare in existing systems. Servers that provide Domain Name Service (DNS) 7][8] are actually distributed system databases. Now we have established that a distributed system level database specialized in the handling of information about language environments is needed for a truly multilingual system. Hereafter, we will call this database MLDB. Note that, besides passive ....

P. Mockapetris. Domain names - implementation and specification. Request for Comments (Standard) RFC 1035, Internet Engineering Task Force, November 1987. Obsoletes RFC0973; Updated by RFC1348.

....resources not found in the whole network need to be installed. A distributed database should be used so that a system can obtain information about the resources its peers have. Again, distributed system databases are not rare in existing systems. Servers that provide Domain Name Service (DNS) [7][8] are actually distributed system databases. Now we have established that a distributed system level database specialized in the handling of information about language environments is needed for a truly multilingual system. Hereafter, we will call this database MLDB. Note that, besides passive ....

P. Mockapetris. Domain names - concepts and facilities. Request for Comments (Standard) RFC 1034, Internet Engineering Task Force, November 1987. Obsoletes RFC0973; Updated by RFC1101.

....DNS delegations edge information becomes too great to efficiently process on a single machine. A classic, but perhaps extreme, example of this problem was the list of Internet hosts, which was used to distribute Internet naming and addressing information before the Domain Name Service (DNS [22, 23]) was developed. As the number of machines connected to the Internet increased, this began to suffer from the twin problems of ever increasing size, and ever increasing demand. The DNS provides a distributed alternative to the old centralised list of Internet hosts. This is done by allowing ....

P. Mockapetris. Domain names - implementation and specification. Request For Comments (Standard) RFC 1035, Internet Engineering Task Force, November 1987. !URL: ftp://ds.internic.net/rfc/rfc1035.txt ?.

No context found.

Paul Mockapetris. Domain names - implementation and specification, 1987. Internet Engineering Task Force, RFC 1035.

No context found.

Paul Mockapetris. Domain names - concepts and facilities, 1987. Internet Engineering Task Force, RFC 1034.

No context found.

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comments 1034, Internet Engineering Task Force, November 1987.

No context found.

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comments 1034, Internet Engineering Task Force, November 1987.

No context found.

Paul Mockapetris. Domain names - implementation and specification, 1987. Internet Engineering Task Force, RFC 1035.

No context found.

Paul Mockapetris. Domain names - concepts and facilities, 1987. Internet Engineering Task Force, RFC 1034.

No context found.

P. Mockapetris. Rfc 1035 (standard: Std 13) domain names--implementation and specification. Technical report, Internet Engineering Task Force, November 1987.

No context found.

P. Mockapetris. Rfc 1035 (standard: Std 13) domain names-- implementation and specification. Technical report, Internet Engineering Task Force, November 1987.

No context found.

P. Mockapetris. Domain names - implementation and specification. Request for Comments (Standard) RFC 1035, Internet Engineering Task Force, November 1987.

No context found.

P. V. Mockapetris. Domain Names -- implementation and specification, RFC 1035, Internet Engineering Task Force, November, 1987.

No context found.

P. V. Mockapetris. Domain Names -- concepts and facilities, RFC 1034, Internet Engineering Task Force, November, 1987.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC