[Asrg] Round one modifications to DNSBL BCP draft.

[Chris Lewis]

Douglas Otis wrote:
> On Mar 31, 2008, at 7:04 AM, Chris Lewis wrote:
> 
>> As a FYI, I'm preparing a revision 2 which I will publish here  
>> shortly.
> 
> Will information be added related to warnings regarding network  
> provider associated address space about to be list?   In many cases,
> only the network provider can be identified as being associated with  
> the address space in question.

No:

a) No (or very few) existing DNSBLs do it, the intent is that the BCP 
describes the practise of most DNSBLs to garner the best acceptance of 
the BCP.

b) MUST or even SHOULD prior warning in a general sense, would just 
about cripple most DNSBLs effectiveness (especially automated ones 
related to bots and vulnerabilities) to the point of not being worth 
doing at all.  At best, it can be a MAY, appropriate to a small number 
of DNSBLs.  I wouldn't even RECOMMEND it.

[I can think of several more, but the above two are sufficient.  Other 
than to point out emailing, say, Turkish Telecom, with a few bazillion 
"this IP is hacked" notifications wouldn't be very productive.]

> Will there be any recommendation  
> regarding the notification of listings?

[Assuming post-listing] No - same reason as (a) above and probably more.

> Will there be any mention of  
> interacting with network providers to determine the nature of access  
> given their advertised address space?  If not, why not?

I don't see this as particularly relevant except to a very narrow set of 
DNSBLs (eg: PBL and some DULs), and as such doesn't seem worth mentioning.