Re: Update on Querying IADB
thanks. but I use 127.0.0.0/8 for other stuff. Hope you don't mind. For those interested in seeing how this has evolved, and what exactly this particular accreditation database provides, our query pages have been expanded, and include a link to the full suggested DNSL data response codes. The codes we use at present include: 127.0.0.1 Listed in IADB 127.0.1.255Vouched listing ... list elided. --bill
Re: Update on Querying IADB
On Wed, 17 Mar 2004 01:48:45 PST, Anne P. Mitchell, Esq. [EMAIL PROTECTED] said: 127.3.100.3Accepts unverified sign-ups, gives chance to opt out 127.3.100.5Has opt-in confirmation mechanism 127.3.100.6Has and uses opt-in confirmation mechanism 127.3.100.10 All mailing list mail is confirmed opt-in Hmm.. this is loads of fun if you're running a Listserv that has several thousand lists defined, and not all of them have the same policies (for instance, although the vast majority of our lists are 'confirmed opt-in', we have several lists that are bulk-loaded with database extracts for captive audience lists such as all freshmen, all grad students, and so on). Also, the pricing seems a bit whacked - are you *really* expecting sites that have less than 30 customers to pay $200/month? I know a *lot* of people who have formed collectives of 10-15 people who chip in and get a 1U at a colo It's totally unclear how you can encode an individual listing - that whole stuff to the left of the @ sign thing is rather unhandy... I'll skip the estimates of the cash flow generated if the database gets big enough to be useful, but I suspect that Verisign might have competition pgp0.pgp Description: PGP signature
Re: Update on Querying IADB
Also, the pricing seems a bit whacked - are you *really* expecting sites that have less than 30 customers to pay $200/month? I know a *lot* of people who have formed collectives of 10-15 people who chip in and get a 1U at a colo They are not email service providers; if you are talking about a site which only publishes non-commercial mailing lists, they would probably fall under the newsletter publisher rate, which is $10.00/month. Anne
Re: Update on Querying IADB
The codes we use at present include: 127.0.0.1Listed in IADB Hmmm... listed in my /etc/hosts as well. Am I IADB compliant? It's interesting to see how everyone tries to reinvent LDAP on top of DNS and/or BGP instead of just using the LDAP protocol itself. Somehow the world has gotten the idea that LDAP is an addressbook protocol when, in fact, it is a fairly generic distributed hierarchical database access protocol. IMHO there are two right ways to publish these types of databases. One is to use LDAP and the other is to use an XML protocol like XML-RPC or SOAP. Overloading DNS as a generic database query protocol is just a plain bad idea. At least both LDAP and XML support the concept of a schema which defines the data being transmitted in an unambiguous way and ensures that it can be correctly parsed and decoded. --Michael Dillon
Re: Update on Querying IADB
127.3.100.3 Accepts unverified sign-ups, gives chance to opt out 127.3.100.5 Has opt-in confirmation mechanism 127.3.100.6 Has and uses opt-in confirmation mechanism 127.3.100.10 All mailing list mail is confirmed opt-in Hmm.. this is loads of fun if you're running a Listserv that has several thousand lists defined, and not all of them have the same policies (for instance, although the vast majority of our lists are 'confirmed opt-in', we have several lists that are bulk-loaded with database extracts for captive audience lists such as all freshmen, all grad students, and so on). In a case like this we would list any IPs from which *only* come confirmed lists separately, so that they would get the 127.3.100.10 listing. Otherwise we would look at the lowest common denominator and use that data code response. Also, the pricing seems a bit whacked - are you *really* expecting sites that have less than 30 customers to pay $200/month? I know a *lot* of people who have formed collectives of 10-15 people who chip in and get a 1U at a colo I've already answered this on the fly, separately, but it bears repeating. If you are talking about non-commercial mailing lists, that would probably qualify for the newsletter publisher rate, which is only $10/month. It's also critical that people understand that you are now talking about *being listed* in IADB, not about querying IADB, which is always free (We've heard from at least one list member who thought these rates being talked about were to *query* the list). It's totally unclear how you can encode an individual listing - that whole stuff to the left of the @ sign thing is rather unhandy... Are you asking about is there a data response code for individual? There *could* be, but we determined that in the scheme of things which most receiving systems care about, it doesn't matter. What matters is the type of mail they send. Anne
Re: Update on Querying IADB
[EMAIL PROTECTED] [17/03/04 17:34 +]:
The codes we use at present include:
127.0.0.1Listed in IADB
Hmmm... listed in my /etc/hosts as well.
Am I IADB compliant?
Am i missing something or isn't this a standard dns block / white list
implementation? I don't run a large public dnsbl but I do serve out dnsbl
zones for my own use.
Should dns{b|w}ls be deployed using LDAP / SOAP now?
srs
