- NANOG - lists.nanog.org

RE: djbdns: An alternative to BIND
by Malayter, Christopher 11 Apr '05

11 Apr '05

Good Evening, As an FYI the mailing list administrators have been contacting users individually letting them know they have been off-topic. We're not connecting this with any warnings etc.. We have been working through the day to get the off-topic posts down in volume on a case-by-case basis. This has been done to allow the operational aspect of the thread to continue, while attempting to remove the personal attacks. Please, if you have a complaint and you would like the list administrators to attend to it please direct it to nanog-admin(a)merit.edu. Regards, Chris Malayter Nanog List Administration Team TDS Telecom - Network Services Data Network Engineering chris.malayter(a)tdstelecom.com Phone: (608) 664-4878 FAX: (608) 664-4644 -----Original Message----- From: Jim Popovitch [mailto:jimpop@yahoo.com] Sent: Monday, April 11, 2005 5:32 PM To: Dean Anderson Cc: Kevin Oberman; william(at)elan.net; nanog(a)merit.org Subject: Re: djbdns: An alternative to BIND On Mon, 2005-04-11 at 17:30 -0400, Dean Anderson wrote: > As long as we are getting history out, It was moving towards death as > a _result_ of Vixie involvment from 1987-1994. I knocked heads with > Vixie around 1989/91 several times "knocked" implies past tense. I'd say that you are still exhibiting that behavior. Give it a break guys, even I'm tiring of this. Moderators??? -Jim P.

1 0

Re: djbdns: An alternative to BIND
by Dean Anderson 11 Apr '05

11 Apr '05

On Mon, 11 Apr 2005, Thor Lancelot Simon wrote: > On Mon, Apr 11, 2005 at 03:03:37AM -0400, Dean Anderson wrote: > > > > Several previous security vulnerabilities in BIND is one strike against. > > You know perfectly well that BIND9 isn't the same code as BIND4 or BIND8; > it's a complete rewrite. It has as much in common with BIND8 as djbdns > does. You might just as reasonably claim that security vulnerabilities > in BIND4 constituted "previous security vulnerabilities in djbdns". It has in common some of the same people who worked on BIND4 and BIND8. Possibly some of the problems of BIND4/8 were systemic. Djbdns, by contrast, has no previous security vulnerabities. This is hardly news, and most consider it to be a valid point. > > These might be fixed. There might still be others. > > And your usual mud-slinging against anyone even vaguely associated with > anyone who vehemently opposes spam begins! By the way, I heard that you > might have stopped beating your wife, but you might still be abusing > small barnyard animals. This is rather odd, if you agree that SORBS is a bunch of nutjobs, where's the mudslinging? > > Violation of trust on other projects is another. e.g. Exactis V. MAPS, > > Several MAPS employees working for well-known spammer Scott Richter > > described in Spam Kings by Brian McWilliams. > > Yawn. I've snipped a bunch more of your ranting. It hangs together > about as well as djb's "BIND Company" black-helicopters theory. Most people (even the vehement anti-spammers) agree that MAPS had no business blocking Exactis, and that Exactis didn't meet the MAPS criteria. MAPS told its subscribers it would only do certain things. Then it didn't do that. That's a trust violation. Seems pretty straightforward. Where's the irrational ranting in that? Whats even more stunning is that MAPS employees went to work for a well known spammer. What would we think if Colin Powell, Rumsfeld, and Rice left and went to work for Bin Laden? What would we think of the judgement of the man who hired them? Someone really made an error in judgement in hiring at MAPS. Do we trust that person again? Or do we show them door, so to speak? > Look, everyone grasps that you got shafted by SORBS. This is not > terribly surprising, because SORBS/ORBS are well known to be a bunch > of nutjobs, and unpleasant nutjobs at that. But as you expand the > radius of your attack to include anyone anywhere who ever had > anything to do with spam prevention, all you're doing, from my > point of view anyway, is demonstrating that you are quite an > unpleasant nutjob yourself. I'm just expanding the radius to include those that have something to do with SORBS/ORBS. ISC hosted SORBS after they were booted by XO. That's a trust violation as well. And I'll note that I left that off my post above, and included only non-SORBS trust violations. And there are a few of those. There are a lot of people who actually have genuine interest in spam and spam prevention. The efforts of those people are insulted by the activities and abuse of a few. Those few who (ab)use anti-spam as a cover for their personal gain and personal vendettas only discredit those who actually do work to stop abuse. --Dean -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000

2 3

SORBS Identity theft alert
by Dean Anderson 11 Apr '05

11 Apr '05

See http://www.iadl.org/sorbs/sorbs-story.html SORBS seems to be collecting a lot of sensitive information to view listings: Name: Preferred Login ID: Password: Confirm Password: Home Phone: Business Phone: Mobile Phone: Email Address: Company: Autonomous Systems Number: Security Question: Security Answer: Skill Level: None, I can play games though. A little, just use them for email. Average, familiar with them, used at home and work. A lot, sysadmin or MCSE etc. My Name is Charles Babbage, or Alan Turing. Address: Address: Town/City: State/County: Zipcode/Postcode: Country: This detailed information could be sold to IT recruiters, used for identity theft, password collection, or used for other mass marketing purposes. Security questions are often used by sensitive sites such as domain registries to authenticate users who have lost their passwords. This is very alarming information collection. -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000

9 11

Maybe OT: MPLS QOS SLA Monitoring
by christian.macnevin＠uk.bnpparibas.com 11 Apr '05

11 Apr '05

Afternoon from sunny London. Feel free to let me know if there's another resource for this kinda thing, and I'll leave you to have fun reading about mail relays. I'm currently looking at what the possibilities are for monitoring network activity and SLAs against Cisco QOS mechanisms within VRFs. The most desirable method seems to be using NetFlow collectors, though it seems as though the benchmark for this is NetFlow 9, and I'm not sure if it's terribly well deployed on NetFlow collectors out there. Anyone know if it *is* well implemented for a given product? Or even if there's just a better way? Cheers, and apologies if this meets somebody's definition of spam. Christian This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ********************************************************************************************** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority.

2 1

clued/interested LEO list
by Gadi Evron 11 Apr '05

11 Apr '05

I'm creating a list of clued and/or interested LEO's, who would like to be part of CLOSED/PRIVATE/SECRET online communities such as anti-botnets, anti-spam, anti-phishing, etc. mailing lists, and/or get information in their area of responsibility. I feel such a resource has been needed for a long time, so I just decided to sit down and get it done. If anyone has someone to add, I'll be working on it in the next couple of weeks. Gadi.

6 8

Re: The power of default configurations
by Andrew Dul 11 Apr '05

11 Apr '05

-------Original Message------- > From: "Sean Donelan" <sean(a)donelan.com> > Subject: The power of default configurations > Sent: 06 Apr 2005 14:00:05 > > On Mon, 4 Apr 2005, Paul Vixie wrote: > > adding more. oh and as long as you're considering whether to restrict > > things to your LAN/campus/ISP, i'm ready to see rfc1918 filters deployed... > > Why does BIND forward lookups for RFC1918 addresses by default? Why isn't > the default not to forward RFC1918 addresses (and martian addresses). If > a sysadmin is using BIND in a local network which uses RFC1918 address, > those sysdmins can change their configuration? There was actually a very interesting discussion about this very topic regarding the proposed new ULA addresses at ipv6 working group at the last IETF meeting. This included a discussion about who should do the filtering the routers or the DNS servers etc...see the minutes below. http://www1.ietf.org/mail-archive/web/ipv6/current/msg04554.html The IESG basically rejected this draft because of the issues of DNS queries for 1918 space. They were looking for stronger language to deal with the issue we currently see with 1918 queries. http://www.ietf.org/internet-drafts/draft-ietf-ipv6-unique-local-addr-09.txt Andrew

5 5

Re: djbdns: An alternative to BIND
by Roger Marquis 10 Apr '05

10 Apr '05

David Conrad wrote: >> - Amount of code > >Again, what should be counted? Should you include rsync? Should you >include utility programs like check-namedconf, axfr-get, rbldns, >walldns, walldns-conf, etc.? You need only count the lines of code needed by the daemon/s servicing requests. That is, IMO, bind's only major failing. Too much code, too many little used features (nobody I know needs or wants rndc), and no way to compile without them. If you read Bruce Schneier, as every developer should, you know how important that "Amount of code" is. All I really want is to "configure --minimal && make && make install" and not have to fix ISC's ill thought-out defaults (like /usr/local/etc on Solaris...). Using bind 8 and 9 but still looking for something better, -- Roger Marquis Roble Systems Consulting http://www.roble.com/

5 4

(half OT) Tool for ASN statistic freaks: webalizer_asn
by Fredy Kuenzler 10 Apr '05

10 Apr '05

Webalizer_ASN v1.2b is available since a while, and according to my tests rather stable now. The ASN Data for Webalizer_ASN is based on Netlantis backend BGP engine (someone asked recently about Netlantis). If you experience a rainy lazy sunday, this might be a tool to play with a bit and build your personal Top-Ten ASN list. http://www.init7.net/webalizer_asn/ Debian Woody users could use the precompiled package. If you have existing orignal Webalizer statistics, you need to move webalizer.current file to webalizer.current.old before running the webalizer_asn - and please note: no warranty, you use the tool on your own risk - so have your statistics backuped first. Enjoy, F.

1 0

Re: djbdns: An alternative to BIND
by sthaug＠nethelp.no 10 Apr '05

10 Apr '05

> You need only count the lines of code needed by the daemon/s > servicing requests. That is, IMO, bind's only major failing. Too > much code, too many little used features (nobody I know needs or > wants rndc), and no way to compile without them. If you read Bruce > Schneier, as every developer should, you know how important that > "Amount of code" is. Ah, but how do you know what are the little used features? We use rndc a lot, just as we used ndc with BIND 8. Steinar Haug, Nethelp consulting, sthaug(a)nethelp.no

1 0

Call for Track Chairs - APRICOT 2006
by Suresh Ramasubramanian 10 Apr '05

10 Apr '05

APRICOT 2006 CALL FOR TECHNICAL CONFERENCE TRACK CHAIRS Asia Pacific Regional Internet Conference on Operational Technologies Perth, Australia Feb 22 - Mar 3, 2006 The APRICOT 2006 Program Committee is seeking interested and qualified Track Chairs to actively assist the Committee in recruiting speakers and organizing technical tracks for the 2006 Asia Pacific Regional Internet Conference on Operational Technologies. The main responsibility of the Track Chair is to identify, recruit high quality speakers to share their expertise on operationally relevent topics. As in past years, the APRICOT Program Committee will issue a general call for presentations, which typically elicits a large number of submissions. These proposals will be provided to the Track Chairs for consideration, but it is expected that the Track Chairs will primarily use their own personal networks to recruit speakers who may not have participated in past APRICOT events. Specific Track Chair responsibilities include: * Identifying and describing a track topic and relevant potential track components (panel discussions, pro/con debates, etc.) within the track that will be interesting and valuable to the APRICOT audience. Preliminary Track descriptions are due at the time of nomination, or by June 15, 2005. * Helping to publicize and recruit speakers, session moderators, and participants for their track and the conference in general. * Vetting and recommending speakers and their subjects for their Track to the Program Committee. Detailed Track content recommendations are due on August 29, 2005. * Requiring and confirming that speakers submit their proposed materials in a timely manner. Track chairs should submit speaker recommendations and abstracts to the Program Committee by September 26, 2005. Selected speakers will be announced by the Program Committee on or before October 10, 2005. * Evaluating submitted materials for content and quality suitable for an international technical/operations conference. Track chairs should submit full/detailed presentation outlines to the Program Committee by November 7, 2005. * Serving as a liaison between the Program Committee and the selected participants in your Track. Track chairs should submit all complete presentation materials to the Program Committee by January 9, 2006. * This year we will require that speakers must supply their program material in advance so that we can confirm operational content and that there is not inappropriate sales material. * Track Chairs are members of the Apricot Program Committee and will share the responsibility of determining overall program issues and planning. Track Chairs are encouraged to help find speakers for other tracks and tutorials as well. Workshop Chair and Tutorial Chair These positions are similar to the Track Chairs described above, but will be responsible for recruiting and facilitating instructors for five-day and half-day/full day instructional tutorials, respectively. A total of 5-6 Track Chairs will be selected by the Program Committee, along with a Tutorial Chair and Workshop Chair, with the expectation that 4-6 Tracks will ultimately be scheduled for presentation. Please feel free to nominate yourself or someone other than yourself who might be appropriate for either of these positions. The deadline for receiving Conference Track and Tutorial Track Chair nominations is May 2, 2005. Results of the selection process will be announced by May 18, 2005. ABOUT THE APRICOT AUDIENCE The APRICOT audience is mainly comprised of technical network operators and professional engineers with experience levels ranging from (almost) newbie to seasoned, senior technical management. APRICOT audiences always include native speakers of a dozen or more languages, so written materials and presentations should be tuned appropriately. Each year, the majority of APRICOT attendees travel internationally and commit considerable sums relative to their local economies to participate in APRICOT; they expect the highest possible quality in presentation content and delivery. APRICOT CONFERENCE TRACKS, SESSIONS, & TUTORIALS Historically, tutorials have focused on core operational skills and basic protocol knowledge, with conference sessions highlighting day-to-day operations and recent/emerging issues within a 12-18 month time horizon. APRICOT Conference Tracks are full-day events. Each Track typically encompasses three 90-minute Sessions composed of 3-4 presenters (speakers) per session; accordingly each presentation should be designed to be approximately 20-30 minutes in duration. On the recommendation of the Track Chair, individual Sessions may be moderated by persons with expertise appropriate to the subject matter of the session. Session Moderators may assist in managing speaker time and soliciting questions from the audience. APRICOT Tutorials are half or full day workshops which focus on a particular subject in-depth. They may be presented by a single Instructor, or a team of instructors working together. Tutorial attendance is typically charged separately from APRICOT conference attendance, so it is essential that tutorials are of the highest quality and deliver concrete operational value to participants. The above descriptions are suggestions only, based on past successful program offerings. Prospective Track and Tutorial Chairs are encouraged to suggest alternative schedules or structures for organizing Conference Tracks and Tutorials to the APRICOT Program Committee. *IMPORTANT NOTE* APRICOT is a TECHNICAL and OPERATIONAL conference. Marketing and commercial content is limited to the appropriate fora (e.g., designated demo areas, "Beer 'n Gear" events) and otherwise restricted from the official program. The Program Committee and Track Chairs are charged with maintaining the technical standards of APRICOT, and will therefore not accept inappropriate materials. To the greatest extent possible, all official conference materials will be designed and presented in a vendor neutral format. APRICOT attendees are technical professionals, and proposed conference materials should be appropriate to the audience. All sessions will provide time for Q&A, and presenters should be prepared to receive detailed technical questions, and to provide appropriately detailed technical responses. The APRICOT Program Committee reserves the right withdraw speaking invitations or to disallow presentations that are inconsistent with the goals and standards set forth in this call for proposals. APRICOT FUNDING AND SUPPORT APRICOT is a not-for-profit event. Every effort is made to keep attendances fee low in order to reach diverse target groups from both the developed and developing countries of the Asia Pacific region. Registration fees are waived for all Track Chairs, Tutorial instructors, and Speakers, however it is generally impossible for APRICOT to underwrite travel expenses for speakers. Only in exceptional hardship circumstances will APRICOT be able to consider assisting Track Chairs or Tutorial instructors with travel expenses. A small number of conference fellowships will be made available (on the basis of personal and local need) to prospective conference attendees from Asia Pacific region; additional information about these fellowships is available at http://www.2006.apricot.net/fellowship.html (TBA). APRICOT 2006 IMPORTANT MILESTONES: 02 May 2005: Receive all Track, Workshop, and Tutorial Chair nominations 18 May 2005: Track Chair selections announced 15 June 2005: Basic Track outlines submitted by Track Chairs to Program Committee General Presentation RFP distributed by Program Committee 29 August 2005: Initial presentation proposals submitted by Track Chairs to Program Committee 26 September 2005: Final presentation proposals submitted by Track Chairs to Program Committee 10 October 2005: Approved presentation tracks announced by Program Committee Selected APRICOT 2006 Presenters notified; 07 November 2005: Detailed presentations outlines submitted by Track Chairs to Program Committee Conference Track schedules finalized 09 January 2006: Full presentation materials submitted by Track Chairs to Program Committee 22 February 2006: APRICOT 2006 Workshops begin (through 26 February) 27 February 2006: APRICOT 2006 Conference Begins NOMINATING YOURSELF OR OTHERS AS A TRACK CHAIR If you would like to be considered as a TRACK CHAIR, please copy the following form, fill it in and email it to mailto:chair.submission@apricot.net If you know of someone else that you believe would make a good Track Chair, please forward this email to them and encourage them to submit the form, or fill in as much of the form as you can and include your contact info in the section for the "Nominator" and email it to mailto:program@apricot.net with the word "Nomination" in the subject line. -------------------- NOMINATOR CONTACT INFO (If nominating another person, please put your info here, if you are doing this for yourself you do not need to fill in this section) Nominator Name: Nominator Title: Nominator Voice Phone: Nominator Fax: Nominator email: ------------------------ TRACK CHAIR PERSONAL INFORMATION (This should be info about the person who would be the Track Chair) First (Given) Name: Middle Name: Last (Family) Name: Title: Company / School / Affiliation: Organization URL: City: State: Country: Voice Phone: Extension: Fax: email: Personal URL: Short Bio (please include enough information that we can determine that you are would be qualified as a track chair): Please also include a photo if possible. Assistant Name (Person who may be administratively submitting this for the speaker or someone who is an alternate contact for chair): Assistant Title: Assistant Voice Phone: Assistant Fax: Assistant email: ------------------------ CONTENT INFO (Select or suggest one or more Track subject you would be interested in Chairing): * Network security * Address planning, conservation, responsibility, IPv6 * Network planning, management and traffic engineering * Operation, NOC, Helpdesk and issues in deploying Internet Infrastructure * Internet exchanges, peering and collocation * Hot topics in future network protocols and techniques * BIND, DNSSEC, and Reverse and multilingual DNS * Broadband first/last mile access technologies * Mobile and wireless technologies * Content, Applications, Email, streaming and multimedia infrastructure * Service and server scaling, Redundancy and reliability, Open source * VoIP * Other Describe: Please put down any other thoughts, suggestions, ideas or comments: ------------------------ More information on the conference will be made available at http://www.2006.apricot.net/program.html Thanks for your interest in APRICOT 2006! Robert J. Berger, Chair (rberger at ibd dot com) Tom Vest, Co-Chair (tvest at pch dot net) APRICOT 2006 Program Committee

1 0