Postel, J.: 1994, `Domain Name System Structure and Delegation'. RFC 1591. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network - Nesargi, Prakash (2002) (17 citations) (Correct)
....TORA [5] ZRP [6] etc. A node in an IP based network is configured with an IP address, a netmask and a default gateway (the node to which packets for destinations not having an explicit entry in the routing table are sent) In addition, the network configuration may include information about DNS [7], DHCP [1] servers, etc. Existing MANET literature bypasses the issue of node configuration by assuming that nodes in MANETs are configured apriori, before they become a part of the network, as in [8] This introduces an element of centralized control which limits the ability to spontaneously form ....
J. Postel, "Domain Name System Structure and Delegation," Network Working Group - RFC 1591, March 1994.
Services in Cellular Packet Data Networks - Uskela (1999) (1 citation) (Correct)
....level domain (WWW server of the Helsinki University of Technology) The Internet authority has chosen some top level domains, which partition the name space. The top level domains are listed in Table 6. The top level names allow two different naming hierarchies: geographical and organisational. [35] Table 6: Top level Internet Domains Domain Name Description COM Commercial Organisations EDU Educational Institutes GOV USA Government Institutions MIL USA Military Organisations NET Major Network Support centers ORG Other Organisations than above ARPA ARPAnet domain (obsolete) INT ....
J. Postel, Domain Name System Structure and Delegation, RFC 1591, March 1994, IETF
Mediating Among Diverse Data Formats: Thesis Summary - Ockerbloom (1998) (Correct)
....based on client server connections; examples from the Internet s history include FTP [B 71] Gopher [AML 93] and the World Wide Web [BLCGP92] Data on these systems resides on a particular server, which can cause bottlenecks for popular data stores. Systems like Usenet news [KL86] and DNS [Pos94] replicate and partition their data store, lessening the load on any one server. Similarly, TOM s type brokers replicate type and format information, easing loads on any given broker. 1 For simplicity, I will use the term TOM to describe both the data model and the network of software agents ....
J. Postel. Domain name system structure and delegation. Internet Request for Comments (RFC) 1591, March 1994.
A Primer On Internet and TCP/IP Tools and Utilities - Status Of (Correct)
....by the preference value. This query also returns the name of the domain s name servers and all associated IP addresses. The DNS is beyond the scope of this introduction, although more information about the concepts and structure of the DNS can be found in STD 13 RFC 1034 [19] RFC 1591 [21], and Kessler [16] The help command can be issued at the program prompt for information about NSLOOKUP s more advanced commands. TECHNICAL NOTE: There are other tools that might be available on your system or with your software for examining the DNS. Alternatives to NSLOOKUP include HOST and ....
Postel, J., "Domain Name System Structure and Delegation," USC/Information Sciences Institute, RFC 1591, March 1994.
Cryptography in OpenBSD: An Overview - de Raadt, Hallqvist, Grabowski.. (1999) (Correct)
....have a very long cycle length. ffl A PRNG is normally just an algorithm where the same initial starting values will yield the same sequence of outputs. Some applications have criteria which affect the type of PRNG which is needed. For instance, later on we will discuss IP datagram IDs and DNS [30] query IDs, both of these issues have qualities which make it extremely desirable to have a PRNG which makes efforts to avoid emitting repetitions (thus ruling out use of a true random source) Many other operating systems also have random number device drivers and other related mechanisms, but ....
J. Postel. Domain name system structure and delegation. Request for Comments (Informational) 1591, Internet Engineering Task Force, March 1994.
A Secure Active Network Environment Architecture - .. - Alexander.. (1998) (28 citations) (Correct)
....H , or 4. fQ; IPv4 version2 j IPv4 version1 g the IPv4 module (version 2) if available, otherwise the previous version of the same module by the same programmer. This naming scheme allows for any possible name discovery mechanism. For example word of mouth, directory based [45] or DNS like [46] approaches could all be used, separately or coexisting in the Active Network. The issue is subject to further research. VIII. SANE IMPLEMENTATION STATUS AND FUTURE WORK The SANE architecture is piece wise implemented and the integration of the components is now underway. The AEGIS secure ....
J. Postel, "Domain name system structure and delegation," Request for Comments (Informational) 1591, Internet Engineering Task Force, Mar. 1994.
The Design and Evaluation of an End-to-End Hando.. - Antonios Argyriou Anargyr (Correct)
No context found.
Postel, J.: 1994, `Domain Name System Structure and Delegation'. RFC 1591.
Network Working Group Federal Networking Council.. - Government Internet.. (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, USC/Information Sciences Institute, March 1994. Security Considerations Security issues are not discussed in this memo.
Network Working Group Federal Networking Council.. - Obsoletes Government.. (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, USC/Information Sciences Institute, March 1994.
Network Working Group J. Klensin Request for Comments.. - Application Techniques .. (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
Unknown - Status Of This (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
Unknown - (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
Network Working Group J. Klensin Request for Comments: 2345.. - Status Of This (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
Collecting Statistics about the Portuguese Web - Gomes, Silva (2003) (Correct)
No context found.
J. Postel. Domain name system structure and delegation. Available at URL http://www.ietf.org/rfc/rfc1591.txt?number=1591, 1994.
Network Working Group D. Eastlake Request for Comments.. - Reserved Top Level (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation",
Network Working Group G. Kessler Request for Comments: 1739.. - Status Of This (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", USC/Information Sciences Institute, RFC 1591, March 1994.
Network Working Group J. Klensin Request for Comments: 3467.. - Role Of The (Correct)
No context found.
Postel, J., "Domain Name System Structure and Delegation", RFC 1591, March 1994.
The Self-Governing Internet: Coordination by Design - Sharon Eisner Gillett (Correct)
No context found.
Postel, Jon. 1994. Domain Name System Structure and Delegation. Network Resnick, Mitchel. 1994. Turtles, Termites, and Traffic Jams: Explorations in Massively Parallel Microworlds. Cambridge, Mass.: MIT Press.
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