KANTOR, B., AND LAPSLEY, P. Network news transfer protocol. RFC 977, Network Working Group, Feb. 1986. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
An Adaptive Quality Of Service Aware Middleware For Replicated .. - Krishnamurthy (2002) (2 citations) (Correct)
....replicated state. In order for the responses to be meaningful to the clients, it is important to bound the degree of inconsistency when the replicated information is time varying. Traditionally, replicated systems provide either strong consistency (e.g. 55, 63, 67] or weak consistency (e.g. [77, 37, 21]) guarantees for replicated data. Strong replica consistency requires that at the end of each method execution by a replicated object, all the replicas of the object have the same state. Weak consistency specifies that the replicated state will eventually converge, but does not provide any ....
....algorithms mainly target applications for which the probability of occurrence of these conflicts is rather small. 66 Although optimistic replication algorithms have been studied for a long time, their use has become more popular with the growth of the Internet and mobile computing. Usenet [37], the Internet bulletin board system, is one of the well known replicated services that is based on optimistic replication. Each server replicates all the news articles so that a user can read any article from the closest server. The postings are propagated among the servers by periodic flooding. ....
[Article contains additional citation context not shown here]
B. Kantor and P. Rapsey. Network News Transfer Protocol. RFC977, Feb 1986. http://www. cis.ohio-state.edu/htbin/rfc/rfc977.html.
M/TCP: The Multicast-extension to Transmission.. - Visoottiviseth.. (2001) (Correct)
....of M TCP in order to supports them. The features of M TCP are, 1) M TCP can be applied to those applications that a sender triggers data transfer (senderinitiated) for example, File Transfer Protocol (FTP) 5] Simple Mail Transfer Protocol (SMTP) 6] and Network News Transfer Protocol (NNTP) [7], 2) it requires only implementation on the sender. Receivers will receive the packets as the unicast packets. Therefore, there is no need to modify both receiver s protocol stacks and their applications. In this paper, we provide the details of M TCP, and show how M TCP can be widely deployed ....
Kantor, B and P. Lapsley, "Network News Transfer Protocol", RFC 977, Febuary 1986.
An Architecture for Intentional Name Resolution.. - Adjie-Winoto.. (Correct)
....is ################. To include it in the header to describe the source and destination of a message, the name specifier has a wire representation as shown in Figure 2. This string based representation was chosen to be readable to assist with debugging, in the spirit of SMTP [35] HTTP [16] NNTP [23], etc. Levels of nesting are indicated by the use of brackets (# and #) and at root city service whitehouse building wing room west oval office camera picture data type 640x480 resolution accessibility public Figure 1: A graphical view of an example name specifier. The hollow ....
KANTOR,B.ARE LAPSLEY,P.Network News Transfer Protocol, Feb. 1986. RFC-977.
Empirically-Derived Analytic Models of Wide-Area TCP Connections: .. - Paxson (1994) (136 citations) (Correct)
....indistinct, since the remote peer may have some but not all of the offered articles. The first mode is easy to detect. If upon initially being contacted a responder peer is unable to communicate with the originating peer, it sends a message with response code 400 ( service discontinued ) as per [RFC977] When the originating peer then replies with QUIT followed by a carriagereturn and a line feed, it will send a total of 6 bytes during the connection. Indeed, we find large spikes of 6 originator bytes in the nntp datasets, as did the authors of [DJCME92] Thus we can recognize a connection in ....
B. Kantor and P. Lapsley, "Network News Transfer Protocol", RFC 977, Network Information Center, SRI International, Menlo Park, CA, 1986.
An Architecture for Intentional Name Resolution.. - Adjie-Winoto.. (1999) (Correct)
....is province=ontario. To include it in the header to describe the source and destination of a message, the name specifier has a wire representation as shown in Figure 2. This string based representation was chosen to be readable to assist with debugging, in the spirit of SMTP [35] HTTP [16] NNTP [23], etc. Levels of nesting are indicated by the use of brackets ( and ] and at root city service whitehouse building wing room west oval office camera picture data type 640x480 resolution accessibility public Figure 1: A graphical view of an example name specifier. The hollow ....
KANTOR, B. ARE LAPSLEY, P. Network News Transfer Protocol, Feb. 1986. RFC-977.
Three problems with Internetworking in cellular networks - Larzon (Correct)
....such as IP, TCP, UDP and RTP. While it is possible to achieve a high compression ratio for combinations of these protocols, there are many examples of application specific protocols that could be compressed as well. Examples include AFS [25] HTTP [19] IMAP [11] Java RMI [36] NFS [38] NTP [30], RPC [35] RTSP [51] SDP [24] SNMP [45] various protocols used by networked games (e.g. QNP [47] tunneling protocols (e.g. PPTP [23] protocols used by messaging software (e.g. ICQ [27] AIM [2] and the IMPP work within the IETF [26] and many more. Within a cellular network, it is ....
....TCP packets [28] Most of these algorithms focus on network and transport layer protocols. However, there are many examples of application specific protocols that could be compressed to save valuable wireless bandwidth. Examples include AFS [25] HTTP [19] IMAP [11] Java RMI [36] NFS [38] NTP [30], RPC [35] RTSP [51] SDP [24] SNMP [45] various protocols used by networked games (e.g. QNP [47] tunneling protocols (e.g. PPTP [23] protocols used by messaging software (e.g. ICQ [27] AIM [2] and the IMPP work within the IETF [26] and many more. Standardization of new algorithms ....
Brian Kantor and Phil Lapsley. Network news transfer protocol. Request For Comments RFC 977, IETF, February 1986.
Network Support for Group Communication - Levine (1999) (Correct)
....because an existing multicast group is used to send data regardless of the intended receivers. Further advantages and disadvantages or 90 addressing and filtering are discussed throughout this paper. 4.2. 4 USENET News Distribution The USENET network of NNTP (Network News Transport Protocol) [22] servers is one of the most popular large scale services on the Internet and a classic example of the pure filtering approach. In USENET, users can post articles containing text and mimeencode multimedia content to categorized newsgroups, which are partitions of specific topics. Once an article ....
....stock is volatile) If the clients wanted a continuous update of a stock s value for a long period after it first becomes volatile, then we can re classify the application s data flows as long duration. An example long duration application is USENET newsreaders and news distribution (i.e. NNTP [22]) USENET data lacks the real time requirements of stock market data, but we can classify it as long duration, because the data flows (the articles; or at a higher level, 100 the newsgroups) are relatively long. In other words, a summary description of the article s content (perhaps the subject ....
Brian Kantor and Phil Lapsley. Network news transfer protocol. Request for Comments 977, Feb 1986.
UsenetDHT: A Low Overhead Usenet Server - Emil Sit Frank (2004) (1 citation) (Correct)
No context found.
KANTOR, B., AND LAPSLEY, P. Network news transfer protocol. RFC 977, Network Working Group, Feb. 1986.
A Network Measurement Architecture for Adaptive - Applications Mark Stemm (2000) (Correct)
No context found.
B. Kantor and P. Lapsley, Network News Transfer Protocol (NNTP), UC San Diego, Feb 1986, RFC-977.
F2F: reliable storage in open networks - Jinyang Li Frank (2006) (1 citation) (Correct)
No context found.
B. Kantor and P. Lapsley. Network news transfer protocol. RFC 977, Network Working Group, Feb. 1986.
Measuring an IP Network in situ - Burch (2005) (Correct)
No context found.
B. Kantor and P. Lapsley. Network news transfer protocol. RFC 977, Feb. 1986.
Unknown - (Correct)
No context found.
B. Kantor and P. Lapsley. Network News Transfer Protocol. RFC 977, UC San Diego and UC Berkeley, February 1986.
Data Webs for Earth Science Data - Asvin Ananthanarayan Rajiv (Correct)
No context found.
Brian Kantor and Phil Lapsley, Network News Transfer Protocol, February 1986.
Unknown - Status Of This (Correct)
No context found.
Kantor, B. and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
UsenetDHT: A Low Overhead Usenet Server - Emil Sit Frank (2004) (1 citation) (Correct)
No context found.
KANTOR, B., AND LAPSLEY, P. Network news transfer protocol. RFC 977, Network Working Group, Feb. 1986.
A Pseudonymous Communications Infrastructure For The Internet - Goldberg (2000) (11 citations) (Correct)
No context found.
Brian Kantor and Phil Lapsley. Network News Transfer Protocol, February 1986. RFC 977.
Network Working Group H. Alvestrand Request for Comments.. - Status Of This (Correct)
No context found.
Kantor, B. and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
Unknown - (Correct)
No context found.
Kantor, B. and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
An Adaptive Quality of Service Aware Middleware for.. - Krishnamurthy.. (2002) (2 citations) (Correct)
No context found.
B. Kantor and P. Rapsey. Network News Transfer Protocol. RFC977, Feb 1986. http://www.cis.ohio-state. edu/htbin/rfc/rfc977.html.
Data-Aware Multicast - Ebastien Baehni Patrick (2004) (3 citations) (Correct)
No context found.
B. Kantor and P. Lapsley. Network News Transfer Protocol, Request for Comments, 1986.
Data-Aware Multicast - Baehni Th Eugster (2004) (3 citations) (Correct)
No context found.
B. Kantor and P. Lapsley. Network News Transfer Protocol, Request for Comments, 1986.
Unknown - (Correct)
No context found.
Kantor, B., and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
Network Working Group S. Barber Request for Comments: 2980.. - Status Of This (Correct)
No context found.
Kantor, B and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
Xml Media Types - Murata, Laurent, Kohn (2001) (13 citations) (Correct)
No context found.
Kantor, B. and P. Lapsley, "Network News Transfer Protocol", RFC 977, February 1986.
Clustering Web Accelerators - Feenan, Fry, Lei (2002) (Correct)
No context found.
Kantor, B and P. Lapsley, RFC 977, "Network News Transfer Protocol".
First 50 documents Next 50
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