nanog mailing list archives

Re: Anyone still maintaining altdb.net?


From: Bret Palsson <bret () getjive com>
Date: Wed, 20 Apr 2011 09:51:30 -0600

Really... Please provide support? Below is the response I got on April 11. I don't need a tutorial on how to use the 
service...

"#ERROR: New maintainers must be added by a DB administrator.
Forwarding new request to db-admin () altdb net"

If it takes weeks for a maintainer record to be added, the service really isn't helping people which is why I offered 
to be part of that service a volunteer.

Frankly I am shocked you would make such comments as: 
There is infact more than 1 person volunteering for AltDB, but from what 
I can see of this April 11th email, it falls into the "please provide 
support" category. :)


I really was requesting: Please do what you signed up to do and add my object. If you need more people to help with 
this process, I'm available and would be more than happy to help out, as I do in every position I volunteer in.

I've waited 9 days which isn't a lot compared to others I've talked with who have waited many weeks or have had no 
response at all. 

I also realize people have lives and can't do things on demand when they are a volunteer. However for a service to be a 
service responsibility must lie with someone. If no one takes responsibility the service becomes unusable and actually 
becomes a disservice. 

I appreciate Jon Lewis's response it was much more helpful to know of other free services that I can support vs. the 
non-helpful response I got from you.

I only posted to nanog about altdb.net becaus altdb was created by nanog members. I like to support nanog and the 
services the community provides.
 

---- Actual results below -----
Your transaction has been processed by the
IRRd routing registry system.

Diagnostic output:

------------------------------------------------------------

The submission contained the following mail headers:

- From: routing () getjive com
- Subject: Please add mntner object.
- Date: Wed, 20 Apr 2011 08:24:09 -0600
- Msg-Id: <E5E09659-1601-4C54-9310-8DCA471729B6 () getjive com>


ADD FAILED: [mntner] MAINT-JIVE
mntner:     MAINT-JIVE
descr:      Jive Communications, Inc.
admin-c:    BEP7-ARIN
tech-c:     BEP7-ARIN
upd-to:     routing () getjive com
mnt-nfy:    routing () getjive com
auth:       CRYPT-PW jiCdjGQviTmYo
mnt-by:     MAINT-JIVE
changed:    routing () getjive com 20110411
source:     ALTDB
#ERROR: New maintainers must be added by a DB administrator.
Forwarding new request to db-admin () altdb net



On Apr 20, 2011, at 9:05 AM, Richard A Steenbergen wrote:

On Wed, Apr 20, 2011 at 10:30:44AM -0400, Jon Lewis wrote:
On Wed, 20 Apr 2011, Bret Palsson wrote:

I submitted my objects April 11. the mtrner object needs to be 
created by the db-admin. I realize this is a volunteer thing. Could 
I help out or could the people that are helping out look at adding 
my record? I need to setup some peering relationships. I'd prefer to 
support open communities rather than paying and am willing to help 
out if need be.

If you're just getting started, it might make sense to look at another db. 
IIRC, RIPE's routing registry is free to use, supports md5crypt and 
PGP/GPG auth, and isn't a volunteer one-man show.

One of the premises of AltDB is that no support is provided. For 
example, a lot of people send email asking "how do I use this", and the 
unfortunate answer has to be "sorry we can't help you". If you need 
support, then by all means pay the money to someone like RADB and let 
them help walk you through the process. Of course after the initial 
mntner creation everything is pretty much automated anyways, so if you 
know what you're doing AltDB provides a free method to maintain your IRR 
entries with very little sacrificied over a commercial solution.

There is infact more than 1 person volunteering for AltDB, but from what 
I can see of this April 11th email, it falls into the "please provide 
support" category. :)

-- 
Richard A Steenbergen <ras () e-gerbil net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)



Current thread: