Re: [44net] whois/rwhois

(Please trim inclusions from previous messages) _______________________________________________ whois/rwhois listing, including an email address, of the responsible contact for an allocation should be mandatory and available publicly. If the net manager has "I can't stand hitting delete on SPAM" disorder, they can setup an email address specifically for this function (and check it daily) using something like a free gmail account, which has pretty good SPAM filtering in the first place. ______________________________________________________________________ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 On Thu, Feb 7, 2013 at 3:31 AM, Antonio Querubin <tony(a)lavanauts.org> wrote: (Please trim inclusions from previous messages) _______________________________________________ On Wed, 6 Feb 2013, Tim Osburn wrote: My thoughts are people probably should not be announcing BGP prefixes on the Internet if they have a issue of not giving out their contact info. I believe the initial intent of rwhois with regard to AMPRNet is only for people who are announcing prefixes via BGP. Not the small "sub" assignments within said announced BGP prefixes. Actually that's an RIR requirement regardless of whether the address space is even routed publicly. BGP has nothing to do with it - only that the prefix is shorter than a /29 - and the LIR has a choice of either SWIPing the assignment or putting it in rwhois. Moreover, net-44 is a legacy resource which I don't think is legally governed by any specific RIR policies (ie. I don't think we've signed on to any legacy RSAs). However, a (r)whois lookup facility would not be a bad idea. Antonio Querubin e-mail: tony(a)lavanauts.org xmpp: antonioquerubin(a)gmail.com _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html