Re: example.com

[Edward Lewis <edlewis@arin.net>]

At 14:04 -0700 4/30/03, Randy Bush wrote:
>people cut and paste from examples.  what if queries are generated
>to foo.x?  how did 192.0.2.0/24 become glowing slag?

If the IESG wants to worry about what names are in the domain name 
examples, go ahead.  I was just throwing out some reasons why I think 
that time is better spent on other issues.

The reason I stick to "example.com." or "example." is that if I were 
to say, use "slashdot.net." in an RFC, I might be slashdot-ting them. 
I try to stick to examples that, if abused, hurt only me and not an 
innocent bystander.

I, for one, am not concerned about an RFC inducing folks to hit the 
root servers with bogus domain names.  Popular commercial code is 
more efficient at doing this than the RFCs.

I will abide by using "example." because I think it is wise to use 
safe examples.  But, since you asked, I would say that the time 
commitment to strictly enforce this is time that is in the 
'diminishing returns' category.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                            +1-703-227-9854
ARIN Research Engineer

It's true, my last college class really was "Introduction to Ada."
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.