RFC706 On the junk mail problem

0706 On the junk mail problem. J. Postel. November 1975. (Format: TXT=2085 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                     Jon Postel  (SRI-ARC)
Request for Comments: 706                                              Nov 1975
NIC #33861



                    On the Junk Mail Problem

In the ARPA Network Host/IMP interface protocol there is no
mechanism for the Host to selectively refuse messages. This means
that a Host which desires to receive some particular messages must
read all messages addressed to it. Such a Host could be sent many
messages by a malfunctioning Host. This would constitute a denial of
service to the normal users of this Host. Both the local users and
the network communication could suffer. The services denied are the
processor time consumed in examining the undesired messages and
rejecting them, and the loss of network thruput or increased delay
due to the unnecessary busyness of the network.

It would be useful for a Host to be able to decline messages from
sources it believes are misbehaving or are simply annoying. If the
Host/IMP interface protocol allowed the Host to say to the IMP
"refuse messages from Host X", the IMPs could discard the unwanted
messages at their earliest opportunity returning a "refused" notice
to the offending Host.

How the IMPs might do this is an open issue -- here are two
possibilities:

The destination IMP would keep a list (per local Host) of sources
to refuse (this has the disadvantage of keeping the network
busy).

The destination IMP on receiving the "refuse messages from Host
X" message forwards the message to the source IMP (the IMP local
to Host X). That IMP keeps a list (per local Host) of
destinations that are refusing messages from this source Host.

This restriction on messages might be removed by a destination Host
either by sending a "accept messages from Host X" message to the
IMP, or by resetting its Host/IMP interface.

A Host might make use of such a facility by measuring, per source,
the number of undesired messages per unit time, if this measure
exceeds a threshold then the Host could issue the "refuse messages

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

ペンギンの平均寿命

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る