(I prematurely fat fingered the send hot key.)

On 3/25/2008 8:11 PM, Taylor, Grant wrote:
> So based on this I'm going to say that the DNS query is 85 bytes.
> I'm also going to say that the DNS reply is 202 bytes. (I'm not
> taking in to account that we will be sending things in 64 byte
> segments on Ethernet so these numbers will possibly even be low.)

According to ISO, there are 246 country codes.

For the sake of this discussion, let's say that each country code will
send one query per second. That means that there will be 167+ kbps of
inbound DNS (query) traffic until everyone decides to update their RBL
list. That translates to 1.8+ GB of traffic a day or 54.1+ GB of
traffic a month of inbound DNS queries per day for a service that is now
defunct. It is very likely that this traffic will very slowly taper off
over a very long time.

Let's consider the reply traffic. The reply traffic will be 397+ kbps
of outbound DNS (reply) traffic. This translates to 4.2+ GB of traffic
a day or 128.8+ GB of traffic a month of outbound DNS replies per day
for a service that is now defunct.

So if we combine the inbound queries and outbound replies, ORDB will
have 564+ kbps of DNS traffic. This translates to 6.1+ GB of traffic a
day or 183+ GB of traffic a month of DNS traffic for a service that is
now defunct.

So, would you rather drop 54.1 GB of traffic a month for the next how
ever many months (open ended until everyone removes relays.ordb.org from
their config) or would you rather have 183 GB of traffic for one month.
I will even go so far as to say that you will not even have a full 183
GB of traffic because you have done something to ensure that people will
react to what you did with in a matter of days.

You play with the numbers and and see what you would want to do long
term if you were facing this amount of traffic. Just imagine what it
would be like if the rate of queries was higher than one per country
code per second...



Grant. . . .