ARIN XX Members Meeting Draft Transcript - Friday, 19 October 2007
"This transcript of the meeting may contain errors due to errors in transcription or in formatting it for posting. Therefore, the material is presented only to assist you, and is not an authoritative representation of discussion at the meeting."
Meeting Called to Order
MR. PLZAK: Okay, good morning.
SPEAKERS: Good morning.
MR. PLZAK: A smaller crowd, that's okay, that means there is more chances for people to win this little prize, because you've got to be present. Okay, let's see. First of all, let's thank our sponsors, One Connect IP. (Applause)
MR. PLZAK: And thank yourselves again please? (Applause)
MR. PLZAK: Okay. The three Help Desks are open, at the time shown, and as promised, we do have the consolation prize. And please remember to fill out the survey; we actually have two lucky winners -- Shaw. (Applause)
MR. PLZAK: By the way, I'll point out that Shaw has over the last several years frequently come up with little ad hoc things to help us to get information from you. So, if anyone else in the room has a desire to follow Shaw's example, it would be greatly appreciated. Reminder: If you have a wireless card, turn it in before you leave, or it'll be yours, and the wireless network will shut down after this meeting this morning. And a discussion reminder, we have rules and courtesies, Chair, you want to say anything at this point?
MR. CURRAN: No. You guys know.
MR. PLZAK: Okay. And so, first order of business is the drawing for the consolation prize. So, I'm going to need the assistance from someone that doesn't want to win theirs, or doesn't have their name in the barrel, or whatever -- the barrel's right over here -- to come over and make a drawing. (Pause)
MR. PLZAK: Ah, see. Carolyn Kim, Kio? I can't really read this. I think its K-i-o -- K-e-o; Carolyn Keo?
SPEAKER: (off mike)
MR. PLZAK: No. No, it's not very good. Okay, one -- obviously not here. (Discussion off the record)
MR. PLZAK: She obviously didn't feel the need for consolation or whatever. (Laughter)
MR. PLZAK: Looking at some of the others. Nigel Cassimire? (Applause)
MR. PLZAK: You know, I pointed out at the last meeting, when we did a newcomer's drawing that another person from the Caribbean won this thing. So, I would expect that the people that are here from the Caribbean would go back and tell their colleagues that hey, if you want something neat, come to the ARIN meeting, because you'll win it. (Laughter)
MR. PLZAK: Nigel, here you go. (Applause)
ARIN Board and Advisory Council Election Procedures
MR. PLZAK: Okay, on to the agenda at hand. First person I want to call up here is Erika to give us a little discussion about the upcoming elections. Erika? (Discussion off the record)
MS. GOEDRICH: Good morning everybody. Well, it is a small crowd up here today -- and hello, to everyone who is watching the webcast, I'm just going to take a couple of few minutes to review some of the procedures for elections and then we'll get to the good stuff on the candidate speeches. Here is the calendar for you, at 12:00 o'clock Eastern, which will be coming up here 10:00 o'clock, local time -- less than an hour, voting opens. One week later, at 12:00 o'clock Eastern, next Friday, voting closes and then the results are announced a week later. Election headquarters, we have the voting booth -- to vote, you click on the yellow "Vote Now" button. We've got candidate biographies and statements of support. You can view the statements that other people have posted, or you can still post -- statements of support for candidates throughout the election period. This is what the voting ballot looks like. There are 7 candidates for the Board of Trustees, you can select up to 2. There are 11 candidates for the Advisory Council, you can select up to 5. Candidates are listed in alphabetical order, their terms begin on January 1, 2008, 3-year terms. Voting procedures: You guys should know the drill that only designated member representatives from general members in good standing can vote. The deadline to establish voter eligibility was the 5th of October. That means that you had to be current on your billing, you couldn't be more than 60 days outstanding on any invoice and you also had to have a valid DMR listed with an e-mail address that included their name or initials and their organization domain name. In a little while, we'll be sending out an e- mail to all eligible DMRs, as well as posting an announcement to arin-announce that voting is open. Three easy steps to vote: You register, if you haven't voted before, or if you've voted in one of our previous elections, then you log in using your username and password. Vote, you confirm your vote. And as a reminder, you have until 12:00 o'clock p.m. Eastern time next Friday, to vote. Any questions? Okay, well if you come up with any questions I'll be out at the Election Help Desk -- during the break, come and see me or after the meeting or next week, e-mail me at firstname.lastname@example.org. With that I will turn it back over to Ray, to introduce the candidates to you. (Applause)
MR. PLZAK: Okay, thank you, Erika. Okay, so, the first group of candidates are the Advisory Council candidates and for those candidates who are not here, I will be reading their bios and statements of intent. And I will say this and I always kind of say it wrong but, it really is important to you to consider the fact that even though they may not be here, it doesn't mean that they are not interested, okay? As you all know that there are circumstances that preclude you from being at certain places at times because of -- of other commitments. So, please take that into consideration that the person's absence does not mean that they don't want this job. So, the people listed in white are the people that are not here today. So, they're listed in alphabetical order, and I will begin with Paul Anderson. You have about 3 minutes.
Advisory Council Candidates
MR. ANDERSEN: Good morning, again my name is Paul Andersen. I thought with so many candidates speaking today, would use the opportunity being first to set for the precedent for these speeches by being quick and to the point. Very briefly I am -- (Applause)
MR. ANDERSEN: Thank you. (Laughter)
MR. ANDERSEN: Very briefly, I am a current member of ARIN's Advisory Council; I'm also the president of egateNETWORKS, which is a regional ISP out of Toronto, Canada, which I started back in 1996. Since its inception, I've either implemented or have been responsible for all network related aspects of the operation. I also sit on the Board of Directors for the Canadian Internet Registration Authority or CIRA, which is responsible for operating the.ca registry, and I also sit on the Board of the Toronto Internet Exchange (TorIX), which is Canada's largest public IX. I believe ARIN Advisor Council is doing an excellent job currently, but there are two small points I'll make. I believe the Advisory Council continues to benefit from wider geographic representation to ensure that the policy process reflects input from all of the regions that ARIN is responsible for representing. And, I wish to continue to bring the smaller operator perspective to the ARIN process, because I believe it represents a large portion of the community but is often underrepresented at meetings. I feel this view is of increasing importantance as we get further with the transition to v6 and we begin dealing with the approaching depletion of the v4 pool. I'd very much appreciate your support and thank you for your time.
MR. PLZAK: Thank you. (Applause)
MR. PLZAK: Next we have Cathy Aronson. Cathy, you have about 3 minutes.
MS. ARONSON: Does this count in my 3 minutes?.
MR. PLZAK: No, this does not count as your three minutes. (Laughter)
MR. PLZAK: That does. (Laughter)
MS. ARONSON: Hi, I'm Cathy Aronson and if elected, I'd like to say that I want to bring IP addresses and universal healthcare to every American. (Laughter & applause)
MS. ARONSON: Anyway, sorry wrong speech. But I was -- I was sending Erika some information, because I've been on the Advisory Council for a while and it turns out that I thought that this would be my third term, but it'll actually be my fourth term, which I guess, time flies, when you're having fun. So, why do I want to -- still be on the Advisory Council? I think that there's a lot that still needs to be done and I continue to be one of those people that sees something that needs to be done and -- and goes and does it. I've setup panels and other forums to get people involved in the IP address policy process. I get people to come here and speak against their will -- any number of things like that. I think that with the upcoming depletion of v4 I really want to be involved in that process and try to help the community as best I can. So, I appreciate your vote and -- again, I'll work on the healthcare thing. Thanks. (Applause)
MR. PLZAK: Thank you, Cathy. Marla, you have about three minutes.
MS. AZINGER: Hello, my name is Marla Azinger; I work for Frontier Communications, as a senior IP engineer and as the new peering coordinator for 5650. I would first like to thank everyone who voted for me to be on the AC three years ago and thank the Advisory Council for bestowing the honor of being the Chair for this year. Being on the AC is a welcome challenge and I enjoy serving you all as one of your 15 representatives. I spent the last three years working hard to keep balance in our policies and facilitate the adoption of IPv6. In addition to this, I've been actively involved at ARIN, NANOG, and IETF in order to facilitate communication that will help bridge the gaps and scope- creep, in regards to RFC inherent policy. These things will continue to be my goals, should I have the honor of serving you for another three years. We have a lot of work on both global policies and within the ARIN region and I want you to know that I am committed to getting the job done. So, I stand before you all now, asking you, may I please have your vote, so that I can continue to support you? Thank you. (Applause)
MR. PLZAK: Thank you, Marla. Okay John is not here, so I will read. His motivation is to help fulfill the goals and policies of the Internet community. "One of my main goals would be to facilitate the transition to IPv6." His brief biography is shown here: Director of Network Engineering for Cablevision; more than 25 years of experience in the computer and networking industry, with a B.S. in Software Engineering; previous employers are as listed; he has a list of network certifications and he is a member of Cablelabs and SCTE. Owen? And Owen you have about three minutes.
MR. DeLONG: Most of the people here already know me; they've seen me at the mics. I put a lot of effort and time into trying to craft better ARIN policy. I think on the AC I've got a role to fill that will help us craft better policy going forward. I think this is going to become especially important as we address an increasingly diverse user community migrating to v6 and I am committed to making v6 workable for the widest possible base of users and I think there is a lot ARIN policy work to be done in that area. I'm one of the authors of 2005-1, which set the precedent for being able to get provider independent space for people who are not ISPs and I think there's more work to be done in that area, and I'm asking for your vote to allow me to do even more of that. Thank you. (Applause)
MR. PLZAK: Thank you, Owen. David? Ah, there we go. And you've got about three minutes, David.
MR. DIVINS: A lot of you must be confused, Paul Vixie has not let himself go, I'm actually Dave Divins. (Laughter)
MR. DIVINS: I am a principle engineer -- ServerVault and there are a lot of great candidates running this year, so, you really can't go wrong, everybody is really good. But there are three reasons why I'd like to join. One, it's an important time for the community and I think, I can help out. As a web hoster I see a little different perspective than a lot of the transit providers. So, I think I can throw that out there. The second thing is I really want to fulfill a lifelong dream to be Paul Vixie's crony; I've never had that opportunity before. So, that would be great. And finally, I'm told chicks dig Internet governance guys, so, I could really use the help. (Laughter) All right, thank you.
MR. PLZAK: Okay, Tine is not here. "Motivation to serve on the AC: I want to serve on the Advisory Council in order to offer my perspective on any technical challenges that may arise, and to serve the Internet community." Brief statements are shown here. "Director of network engineering, United Online, 2001 to present. Previously, CAIS Internet, responsible for traditional network connections and a large DSL installation and connections into hotels and apartments. And, previous to that network engineer for InterAccess." Mark McFadden, not here. "Motivation: At a time when a significant transition is occurring in the area of numbering resources, I would like to help evaluate policies that will affect ISPs, transit providers and their customers. I am especially interested in being a constructive voice in the discussion of how to manage the end of IPv4's traditional lifetime. My goal as an AC member is to bring a global perspective to ARIN's policies regarding numbering resources. "Brief Biography: Lead strategist IP addressing policy and strategy group, BT Americas, 2005 to the present." Prior to that "Assistant professor for Internet technologies, University of Wisconsin, Milwaukee." Prior to that also, "Secretary to the ISP constituency in the gNSO in ICANN." And also previously a "ARIN representative," actually, more correctly phrased I guess would be "A member from the ARIN region of the Address Council." But I think you get Mark's idea there. So -- and Scott, are you here? Oh, you didn't run away? And you have about three minutes.
MR. LEIBRAND: Scott Leibrand, Internap. As Owen said, you've seen me up at the microphone before, so, you kind of have an idea of what I'm up to. I work for Internap, so I've had a good perspective on the diverse needs of service providers, of Internap's customers and of the web hosting side and in personal endeavors I've seen some of the new and emerging types of networks that will need IP addressing. I think I have a very holistic understanding of what the IP address needs are of all those communities. As you've probably seen, I'm very active on PPML and in policy discussions, when I get a chance to come to the meetings. I would like to continue to be active in that and I think the ARIN Advisory Council would be a good way to do that. I think some of the issues that are before the community in the next few years that really need to be addressed are some of the things that we've been addressing so far but, particularly, going down the road I think we need to seriously consider how we're going to make IP addresses available to everyone who needs them as we transition -- that means making v6 addresses available, but also making sure that v4 addresses remain available to those who would have a harder time transitioning. So, one of the questions would be, should we -- what should we do to encourage v4 and Legacy addresses to become available for redistribution to others? What should we do to encourage people who can adopt v6 and free up v4 addresses to make those available? I also think that we need to be very cognizant as we go forward in the need to balance the need for PI space with the need to prevent deaggregation and protect the (off mike). I supported 2005-1, but I also have a very clear understanding of the routing deaggregation problem and have a number of ideas but I'm most interested in listening to proposals from others and evaluating those with an eye towards balancing those two. I hope you will allow me the opportunity to serve on the AC and, if you do, I ensure you that I'll do my best to make sure that all the needs of the community are considered, balanced, and I'll do my best to work with policy authors towards policies that can achieve consensus and make sense for the committee, thank you. (Applause)
MR. PLZAK: David Williamson. David. You have about three minutes.
MR. WILLIAMSON: Hello, I am David Williamson, my current position is the manager of Network Architecture and operations architect for Tellme Networks, a Microsoft subsidiary. It kind of covers the resume section. I was trying to do something utterly glib, I could add to this discussion after all the previous speakers here had immediately stopped and remember me when you went to vote, alas nothing came to mind immediately. I do think this is an interesting time for the AC and for ARIN in general. ARIN is doing pretty well and is fairly healthy, but there are obviously challenges ahead with v4 depletion and v6 adoption has been proven to the new world. I think I have several ideas to contribute to this. I'd like to think that as a non-transit service provider as an ASP effectively, I have some experience that might be interesting or at least a little different from some of the rest of the community. I'd hope that would be a useful addition to the AC. Thanks for your consideration and please vote. Thanks. (Applause)
MR. PLZAK: And Ed Winstead is not here, his motivation to serve the AC. "We are in a very interesting time regarding the eventual depletion of IPv4 resources. I would like to spend the next three years involved with policy decisions that will affect the success of the full or partial transition to IPv6." "As a long time employee of an organization that is a legacy space holder I feel I can offer valuable insights on potential policies designed to encourage more cooperation from legacy holders." Brief biography, lead DNS administrator and IP address manager NCREN, systems analyst for NCREN, prior to that computer operations interim, and NC Super Computer Center MCNC, and also a MCNC representative to the Internet Society Advisory Council. So that is all of the candidates for the Advisory Council, remember to exercise your right and your privilege to vote if you are the DMR. And so let's give them all a warm round of applause. (Applause)
MR. PLZAK: Okay, now on to the Board of Trustees' candidates. There are several in there -- the slide is incorrect. Lyman Chapin did withdraw because of a mutually discovered conflict of interest between him and the ARIN Board and that's enough said on that. So the rest of the people that are in gold are here, the two in white are not here, so Elise are you -- there she is. Okay. You've got about three minutes, for once you get a fast job.
MS. GERICH: Okay, thanks. Hi my name is Elise Gerich, and when I was first asked if I would stand for nomination, my first question was, well, what do the Board of Trustees do? The next thing I knew I was nominated. So -- (Laughter)
MS. GERICH: I figured I better find out for myself, so online ARIN has a very nice little synopsis. The Board of Trustees are responsible for business affairs, financial health of ARIN, and management of ARIN's operations, in a manner consistent with guidance from the Advisory Council, and the goals set by the membership. So I thought it probably would be a good idea to tell you why I think that I can fulfill those responsibilities. As for managing ARIN's operations in a manner consistent with what the membership wants, and the Advisory Council advises I have had positions of this nature before. I was a founder of NANOG, and served on its Program Committee, so therefore we had a constituency base that we had to address and take into consideration. I think that's good foundation for serving on ARIN. As for business affairs I've had three different positions within the Internet business, one the NSF net backbone. The second was the @Home backbone, and finally I've been at Juniper Networks. So I've had experience with the business of the Internet, and that's what ARIN is all about, is enabling the business of the Internet. Finally, financial health, the fiduciary stuff. So in all of my roles at Merit, at At Home Network, and at Juniper Networks, I've had budgetary responsibilities. That means living within the budget, that means coming up with ideas to make more money, so that you can do more things, and it makes means managing the assets and the people who provide the services to the ARIN community. I feel that I have the necessarily qualifications to serve on the ARIN Board and I would certainly be pleased if you chose to elect me. And I want to thank you very much for the nomination. (Applause)
MR. PLZAK: Next, Ed Lewis. And you have about three minutes.
MR. LEWIS: When I started preparing my notes for this speech I was going to spend time talking about my technical qualifications, but then I noticed Tuesday morning the key note at NANOG was given by the ARIN legal council, and he was the first speaker at the two, at least two of the last three ARIN meetings. So I am not sure if it's a NGO's world anymore, so. But I'll start with my technical qualifications anyway. I have about five or six years of working inside registries I worked for domain name registry now, I worked for ARIN years before that. I also have with respect to have been on the outside of ARIN as a member in dealing with organizations in a different perspective. Before that and also while I am doing this I worked in the IETF working on lot of the protocols the registries use in daily operation: DNS, routing protocols, and so on. The last couple of years I've attended every ARIN meeting, APNIC meeting, RIPE meeting, NANOG meeting and IETF meeting which means I basically heard Geoff Huston talk quite a bit. (Laughter)
MR. LEWIS: I don't know if he is here to hear that dig at him one more time, but anyway. Why do I want to run for the Board of ARIN, I think ARIN is in a vital role to the Internet, it's a very key part of the Internet operations spectrum. And not just the public Internet, but all IP protocol networks around the world and some private ones that aren't connected to what we all think of as the Internet. I think that in such position ARIN gives you a real good view of what's happening in the world, what's happening in the technology world, the Internet world. I think it's a very interesting place to be and for instance seeing this technology go forward. What I am also aware of is that when you are in such position you have to be very careful because what you do in these set core places and that ARIN is not the only one, but ARIN is one of the core places, small changes here can have huge repercussions throughout the industry. And I think that we want to be careful about that we have gone from a technical community that's built the Internet to being what it is. We have an industry now, with legal economic concerns. I think we have to run ARIN correctly from what it was that deals of ARIN and try to get that into the future. Now that we have new pressures on us, new interests coming in, it's not just the same world that we thought we were in going into when we started the Internet work years ago. So I think that one of the important things is maintain the open and transparent fabric of ARIN. I think open mike sessions are some of the most important parts of these meetings, and so on and the e- mail also. So being on the ARIN Board I realize that the job is to keep ARIN what it is, what it is supposed to be, and help in transition from, mostly just technology, but also to all the other things that are impacting Internet today. And I hope that I can play a role in this as a member of the Board. Thanks. (Applause)
MR. PLZAK: Okay. Mr. Manning. And you have about three minutes.
MR. MANNING: I am Bill Manning I'd like to thank you. I've been on the Board of Trustees now for two terms; I'd like to thank you for your trust. And I've enjoyed serving. I will point out if you aren't paying attention we have a very strong pool of candidates. Any of which would be a fine choice to sit on the Board of Trustees. If you choose to bring me back I would appreciate that opportunity to serve. I guess that's pretty much it. Don't forget to vote. Thank you. (Applause)
MR. PLZAK: Danny is not here. His motivation to serve on the Board, "In addition to assisting with the financial health business affairs and supporting the AC I hope to work with the ARIN membership in greater community in considering and selecting optimal paths through what seems to be imminently challenging times ahead, exempli gratia allocation and authority for Internet names and numbers, issues surrounding operational security, security and scalability of the global routing system, Internet governance and the regulation of IPv4 and IPv6 addressing and deployment, et cetera." Brief biographical notes, Chief Research Officer at Arbor Networks, 2003 to present, Director of Emerging Technology, Amber Networks acquired by Nokia, Network Engineer Architect, MCI, Genuity, GTEL, Qwest, Elected Member Internet Architecture Board to the present and 13 plus years participation in Internet operations and standardization. And Chris is not here as well, his motivation, "I wish to represent the operational community. Bring the perspective of surviving Internet companies dealing with acquired ARIN assets, and retrofitting ARIN policy compliance, and be eligible to be assigned additional ARIN assets." Biographic notes, Director of Network Architecture, Hostway Corporation 2003 to present, prior Infrastructure Architect Bang Networks, Team Lead, Senior Team Lead, Neteng, Digital Island, Network Architect Montgomery securities/Banc America securities. Various development positions Novell, UB, 3Com, Bridge Communications. IETF participant in 1982 to 1984, excuse me 1994. So that is 1982 to 1994. Cal. There we go, you will have to excuse me, this light sometimes blinds you as far as we look in certain directions. And you have about three minutes.
MR. THIXTON: My name is Cal Thixton. I run a regional ISP of Illinois and Wisconsin, for like the last dozen years or so. I was approached last spring after the last meeting to run for the Board, and to be honest I hadn't been paying attention to the ARIN Board like probably most of my peers. I think I was sort of tapped because I was maybe the target market for trying to bring people back into ARIN. And with the policies coming up and the legacy issues and the dwindling IP war space I may be the target victim as well perhaps because I am basically one of those folks who probably hasn't really been paying attention that maybe our -- I mean, I had to do something here soon. I was urged to talk about by my technical background a little bit I was at Sun Microsystems for five years, I opened up the first office outside of California I got drafted to go work in Next Computers which is probably why I am over dressed and wearing black. For eight years I then got drafted to go start another ISP called "ThoughtPort Authority" who had grand visions of melding sound studios and Kinkos into a business model that didn't really quite work. But we did turn into an ISP that survives today. Most of the things I do these days is acquisitions and mergers and I have been buying up the dregs of all the ISPs in Illinois and Wisconsin that aren't around anymore, I mean, 90 percent of my counterparts are all dead and buried. I've inherited several of their names which is why I have such a long name tag on the site which is a little embarrassing, but you know, I've this it is as it is. But so I lately I've been mostly been doing business, but you know, I've my technical, you know, I still have an OC3 in my basement from when NorthPoint was still around. But I also do the physical mergers and facilities, integrations for the acquisitions that we do today. I am interested in where ARIN's going and what it's going to do particularly to someone like me who probably the only reason we are still alive is small ISPs is because we are just agile. The big guys don't really care about us a whole lot, and we are not that important on their Richter scale, but because we are smart and agile and nimble we manage to sort of still manage to survive. That will be an interesting thing to see in five years or ten years as the next evolution of the Internet you know, comes upon us, but I am interested in knowing how I can contribute to the ARIN Board from here going out, and I would appreciate your support. Thank you. (Applause)
MR. PLZAK: Paul Vixie, Paul. You have about three minutes.
MR. VIXIE: Hello, good morning. Three years ago I was elected to the Board of Trustees as the outside Board member. And what I mean by that is I had never attended an ARIN Board meeting and -- or any kind of ARIN meeting and I was not a frequent poster on the PPML. I have not even subscribed to the PPML; somebody had to tell me about it. So it's been an interesting three years, I've gotten to know those of you who were not also in the NANOG or IETF communities where I have been a longer term denizen, I've leaned a lot about ARIN. So we as a community have a very interesting set of roles. ARIN is incorporated to serve the public interest. You as members have chosen to help ARIN with that mission. ARIN has certain gimmies back to the people who help it, and that it also has a lot of contracts you don't have to be a member to sign an RSA that sort of thing. The role of the Board is to serve the company and the role of the company is to serve the community. And it's a big recursive mutually recursive hairball which we sort out sometimes with our voices raised at every Board member to try and -- every Board meeting to try and figure out what are the implications, and who are those implications upon. Now, if you look at my biography you'll see that whenever we get the band back together to start another company I am the one who gets tagged with president or CEO. And part of the reason for that is that I would rather be a technically competent CEO than to be an administratively competent technical guy. And you might read into that I am a better administrative guy than a technical guy. I will say I have to admit I like talking to lawyers and I like looking at financial reports -- (Laughter)
MR. VIXIE: And I mean, I don't like talking to the lawyers who are deposing me in lawsuits, don't get me wrong. But it is I am not qualified to be on the AC because I don't implement policy inside of ISC that's why a Leo and people like Leo do that, I am simply not technical enough to do what Leo and Suzanne do, so I am glad that they do it. I am administratively competent to serve on the Board of Trustees. I hope that you will decide likewise and elect me to another term. Thank you. (Applause)
MR. PLZAK: Okay. Before I go on, same thing as I said before, remember to exercise your right and your privilege to vote and let's give the candidates a warm round of applause. (Applause)
MR. PLZAK: Some quick reminders, one vote per general member in good standing cast by its designated member representative. You get to vote for two Board candidates and five Advisory Council candidates the polls open and close as shown on the slide. There is an election handout in your meeting folder which has hopefully will answer all of your questions, but if it doesn't you can always direct questions to email@example.com, and while it is open you can also go to the election helpdesk. Erika doesn't want to be lonely -- in that regard. (Laughter)
ARIN Department Reports
Member Services Department Report
MR. PLZAK: So with that I'll say thank you, and let's move on to the next portion of the agenda. And that will be the department reports. And the first report will be that from the Member Services Department by its director Susan Hamlin. Susan.
MS. HAMLIN: Thanks Ray, good morning everyone. I want to spend a few minutes talking about some of our recent and planned activities as we always strive to reach out to the members in the Internet community in the ARIN service region, and also to elicit some feedback on ways that we can better serve you. So we have undergone a little bit of reorganization within the Member Services Department. Our Public Affairs Officer position function has now moved out of Member Services, and is reporting to the Chief Information Officer, which means that Megan is now reporting to Richard. (Applause)
MS. HAMLIN: We have changed a few titles. Our Membership Operations Manager has been renamed, with a few different responsibilities, Communications Manager, and that is the role Jason is currently filling. Our Membership Coordinator Erika has moved up into a direct report to me, and then we have recently undertaken some growth in the communications area. Lori, our Web Support Specialist is back at home taking care of all our needs here. We have added a Communications Writer position, and in fact, Hollis joined ARIN this Tuesday, and we put her on a plane to Albuquerque. So she has been observing and learning for the last couple of days. We also established a -- created a new Graphic Designer position and yesterday learned that our offer had been accepted, so we have a new person starting a week from Monday. And Erin Centanni, Meeting Planner will continue to report to Jason. So that's our new structure. And I would just like to ask all of the Member Services folks that are here to please standup, and thank you for all of your efforts for this meeting. (Applause)
MS. HAMLIN: Megan, you can standup since you were there part of the year -- here you go. Okay. Looking at membership growth these are the stats the far right column for the past five years as of September 30th, and it's broken down by the various regions within our sector. And I did want to say that there are two ways folks become a member either by paying anyone can join ARIN by filling out a membership application form and paying a nominal annual fee or any organization that receives a direct allocation from ARIN is an automatic member. And of the 2,901 members we had September 30th, 129 are paid members, the remainder are members because they have a direct allocation with ARIN. All right, these are the services that fall under Member Services Department. We take care of the association business the most obvious one right now is facilitating the election process. We also facilitate the policy development process and one of the things we have done since our last meeting is to go on out and try to encourage additional subscribers to the Public Policy Mailing List and we were fairly successful in that. Had an increase of about 500 subscribers, and I think you all are probably seeing new faces posting to the list. We are also responsible for meetings, we have 2008 meetings pretty well planned, but we are always looking for sponsors for the future, and would like to plan out a year or two ahead, so anybody who is interested in sponsoring wants to bring the meeting to your hometown please contact us. We also work in the outreach area looking for new ways to meet folks, and also new ways to get your input and I'll talk about that a little later. And the communication and education area we continue to make improvements on the website, we have the ARIN Consultation and Suggestion Process which I'll talk about later, and we develop new materials. So this slide shows some of the areas, where ARIN has been out and about in the public, these are opportunities in addition to meetings of other RIRs, ICANN, IETF, Joint Tech, places where ARIN staff routinely participates, and these are some of the places ARIN has either had speaking engagements and/or had an ARIN booth since our last meeting. And some new things we've done since the last meeting we have instituted an RSS feed of the Public Policy Mailing List and it's available in two different formats, one, a digestive every post to PPML. And also one of just the ARIN announcements to PPML, which mean anytime a new proposal, is introduced, and then results of the Advisory Council findings on that would be available if you find the total post to overwhelming at times. In response to the Board resolution about the migration to IPv6 we added an IPv6 information center on the website, and most recently an IPv6 Wiki and we are hoping that community will take advantage and participate in the wiki. It's a hopefully a centralized location where people can share experiences, post links to references resources that others might find valuable. We continue to publish information sheets, try to digest complicated technical topics into one-page fact sheets; this is an area that Megan and public affairs will continue to work at. Hopefully, you've taken a look at some of the publications in the Cyber Café this week. And the latest one is one of IPv6 transition what it means to the average Internet user. And one of our big efforts in the last six months regarding members is the creation of this membership handbook, which we sent out to all designated member representatives, going forward we will send this out once a month to all new members. It contains a lot of succinct information on ways you need can and should interact with ARIN from how you get resources, how you pay for those resources, how you can subscribe to the mailing list and we hope that you all will find this useful and pass it around to those in your organizations, who have various responsibilities with ARIN. Okay. Looking ahead we will have some additional issues of the comic book coming out before the end of the year, dealing with some popular topics IPv4 exhaustion migration to IPv6. We'll be working on a new flash presentation, and about ARIN not cartoon based this time, and we also are working to make the website compliant with the accessibility standards out there and that's a job that Lori is starting on this week. And looking forward our next ARIN meeting will be held in Denver, we recently posted that, April 6th through 9th 2008. We look forward to seeing all of you out there, and hopefully within the next month we'll be able to announce the location of the fall meeting, so, that's it. Any questions?
MR. MANNING: Yes, let me see here. There was a question from faraway, a remote question that came in to me which was, when will RSS summaries be turned on, the feed with just subject is of limited use?
MS. HAMLIN: We will look into that, and respond. Okay. Anything else?
MR. DARTE: Yeah, hi, I am Bill Darte with the ARIN Advisory Council and I'd like to you know, just say that Susan and her group, creating all of these fact sheets have done an outstanding job. I constantly run into Susan, and ask her I'd say, we really need some information about whatever. And then she takes me over to the Board and shows me that that stuff has already been done, and this has happened over and over again, so I really do encourage everyone to take a look at that information that they put together, and take some of that and distribute it to people that you know, colleagues, and other people in the industry, business people, et cetera who ought to know more about what all these issues that we are facing are. So I'd just like to thank them and encourage you all to do that. (Applause)
Registration Services Department Report
MR. PLZAK: Thank you, Susan. Next will be the report from Leslie Nobile on Registration Services.
MS. NOBILE: Okay. Good morning, everyone. Quick update. This is the Registration Services staff. I think most of you know what we do, so I won't go into details. The left side of the screen is our senior staff. The right side is our Resource Analysts. Cathy actually supervises the five people on the right. David is our Technical Liaison and specialist, and Jon is a Senior Analyst. These eight people do an excellent job in responding to the needs of our community and our customers. There is only eight, and there's a lot of work they take care of, so I really want to thank them as they do a fabulous job. Statistics. I have a variety of kind of wacky statistics that they're -- they kind of -- some of them flow, some of them don't, so please bear with me. Just quick look at what we've been doing this year as far as statistics on this -- on the help desk. We're processing about 50,000 templates per month. About 94 percent of those are auto processed, they're mostly SWIPs. We read and respond to about 1,100 non-template e-mails. That's hostmaster questions that come in. That figure on the right which says 10,000 in hostmaster has actually been about 122,000 e-mails in hostmaster, but we kind of filter out the spam. We actually manually push away the spam, and only respond to the valid e-mails, so. The phone calls -- we're getting about 1,175 phone calls on the help desk average per month. So -- recovered resources. We went back and looked about for the -- over the past two years to see how many resources are coming back to ARIN. There is no policy where we're actually actively pursuing these resources. However, we have people who voluntarily return resources to us. And we also, on occasion, when we see unutilized resources in the course of a transfer, we ask people to give them back and some of them actually do. So as far as returned resources, over the past couple of years, we've gotten a 113/16s back into the global pool, we've got 965 /24s in about 401 ASNs. Revoke space. We revoke space for nonpayment of fees; we also revoke space when we find fraud. So we've recovered 31 /16s about 8,000 /24s and over 2,000 ASNs. And in fact -- and let me just add that we actually hold all of these resources for at least one year so they clear routing filters et cetera before we reissue. The ASNs. We haven't had to go back to the IANA for a block of 2-byte ASNs since last March 2006, and we don't yet expect going anytime in the near future with the amount of ASNs we're recovering and recycling. Subscription holders by category. This is a really bad slide, I apologize. I can barely see it, so I'm sure you can't. But I -- it was really just to illustrate last year at the end of 2006 there were about 2,800 subscription holder members, and 61 percent of those are in the small category. The next size category is mediums, the next number about 559 in the medium category. Extra small would be next. Those are micro allocations and multihomers. Excuse me. And then the large category and extra large only account for 3 percent each, of the total amount of subscription holders. So I just kind of wanted to throw that up. There's another slide that somewhat relates to this later on. We want -- I want to show a report on a couple of policies that were implemented this year. The 4-byte ASN policy seems to be confusing quite a few people. We've had 61 requests since it was implemented in January. Forty-six of those were either abandoned or switched to 2-byte ASNs when we wrote back to them and said, "Do you understand what you're asking for?" And they wrote back and said, "No, we don't actually. We're changing to 2-byte." We issued 15 all, you know, through the year, and then 11 were subsequently exchanged for 2-byte ASNs. So right now there is four that are currently registered and active. I think we need to put out some more information about 4-byte ASNs, and I think we'll be working on that, because I do not think the community actually understands the implications. Capturing originations. This was a policy that was implemented in March of this year; that is capturing origin AS data in the templates. Right now, it's got about 1.7 million on network registration records on WHOIS. About 10,000 of them now have origin AS data, or about 6 percent of the total records. 91 percent of those are being added to SWIPs to reassignments, and 9 percent are being added to direct allocations and assignments. So the policy has proven to be quite well used. So we went back and looked at from 2006 October 1st through September 2007 -- September 30th to get some more data and statistics. So as far as demographics go, ARIN's issued about 2,500 number resources to about 2,500 different accounts. And there is the breakdown as far as -- obviously most of them are in the U.S., 200 or so in Canada, and about 30 (sic) throughout the Caribbean region and Bermuda. So we're consistently issuing space to the Caribbean. In that last year -- this is -- sort of it speaks to approval rates. What are we issuing, and what are we approving. We've issued -- we've gotten about 785 requests from ISPs in v4 -- this is v4 only, and about 590 from end-users. And we are approving about 66 percent of all ISP requests and we're approving about 52 percent of all requests from end-users in v4. So in this last year we've issued 2.88 /8s to about 1,138 different companies. Forty-eight companies have received 88 percent of this space that we've issued, and that's /16s or larger. So these are the larger companies. 1,090 companies have received the remaining 12 percent of the space that we have issued. So this is pretty consistent with some of the information that's been on the mailing list. The large companies are getting most of the larger allocations, and the small companies are getting smaller percentage of what we're issuing. IPv6 requests. We were asked to give some info on v6 at the last meeting. So as far as approval ratings we're getting -- we got about a 100 requests from ISPs, 109 from end-users, and we've approved -- we're approving about 82 percent of all ISPv6 requests, and 85 percent of end-user requests. So -- the person who actually asked for these numbers, I don't think he's here. It was Jordi, but we'll go with it anyway. So denial or abandonment. As I had stated previously at other meetings, just because the request isn't approved doesn't mean it's denied. A lot of people just abandon them in midway and they don't actually follow through. Once we start asking questions, they may realize they don't qualify, but they do abandon the request. So of the 18 ISP requests we haven't approved in v6, 10 are still pending -- we're still going back and forth; 4 we abandoned completely -- we never heard from them again; and 4 we outright denied. Of the end-user requests we haven't approved, 5 are still pending, 3 were abandoned, and 7 were outright denied. So why were they denied? In the ISP denials 3 were actually end-users, and we actually refer them to the ISP policy, and they were subsequently -- I'm sorry, 3 were to the end-user policy, and they were subsequently approved under the end-user policy. One was denied for not having 200 customers, that requirement in the v6 policy, or being a known ISP. The end-users denials -- 2 were ISPs and we referred them to the other policy, and they were both subsequently approved under the ISP policy; and 5 didn't qualify under any existing IPv4 policy, which is the requirement -- one of the requirements or criteria in the v6 end-user policy. So that's all I have. Are there any questions? (No response)
MS. NOBILE: Okay, thank you. (Applause)
MS. NOBILE: I was too quick, sorry.
MS. SCHILLER: Tell everyone about the templates.
MS. NOBILE: Oh, I can do that. Actually I would -- I can send out an announcement, but Heather had asked at the last meeting this did come up. The reassignment templates had all been changed in a recent -- last year when we -- we were trying to revamp and streamline templates, and we apparently took away some really useful and vital fields. So we have actually reissued the corrected templates, and they're out there for your use. So they -- we've gotten a lot of requests for them, and I think that people will be happy to see them back online. So thanks. (Applause)
Financial Services Department Report
MR. PLZAK: Thanks, Leslie. Next, financial services from Bob. However, Bob is not here, so his able second, Val, will give the report. Val?
MS. WINKELMAN: Thank you, Ray. I'm sure some of you are asking what about Bob? Why am I here? Well, Bob was here earlier for a couple meetings, and he's been called back to Chantilly, and he's currently watching us on the web. So hi, Bob. (Laughter)
MS. WINKELMAN: Okay. No, I don't know how to work this. Ah. Okay, I'm going to be giving a review of the department.
SPEAKER: Just pull this back --
MS. WINKELMAN: Okay, thank you. The staff -- Bob Stratton, of course, is director of finance; Tammy Rowe, our AR supervisor is here at the meeting, and she supervises Amaris Wang, Dawn Anderson, Tanya McKnight, Amy Lee -- and Amy also is here today; and Tyler Thompson, he is our newest hire, he's a part-time employee, and he is managing the RSAs as they come in, doing address changes and other duties as assigned, and then myself. Well, I'm going to go over some summaries of activities; the first is to change the due dates. The invoice due dates for renewals are being changed effective January 2008. Your anniversary month will remain the same, only the date will change to the last day of the month, and this would be for everyone. This will help billing; get the invoices processed approximately 60 days before the due date for a particular month. We'll also have to manage the e-mail reminders and make the timing of the reminders more accurate. So now when you receive a reminder and we say your invoice is days overdue, everyone in that month will actually be days overdue where before some were billed on the 1st, some were billed on the 30th. So this is going to be a great help for our department. Digitizing RSAs. Tammy Rowe has headed up this project of getting all the RSAs put into PDF format. And the first batch have -- has been scanned and returned to ARIN, the second batch has been sent off, and there's only one more batch to be sent out, which will catch us up to 2007. And then each quarter, we'll go ahead and send the RSAs out to be scanned so that we can actually retrieve them electronically now, which is much more efficient and much more secure. Cross training. Tammy's group again has been doing some cross training, which ensures that every function is covered during vacations and any time off. And the cross training gives more flexibility in managing the workforce to get the job done. It also allows employees to learn new skills and makes them more valuable to ARIN. Ongoing operations. The inventory is actually going to start next week when we return back to ARIN, so we can try to get this done by the end of the month -- or the end of the year, sorry. Overdue notifications continue to be sent out, and this has really helped tremendously with cash flow and getting clients pay the bills more timely. And we're continuing to have updates to our software, which helps us to eliminate manual functions and keeps up with the billing changes that we have just talked about. Now this is Bob's favorite slide, his key economic stats. The U.S. dollar has declined in 2007 by 8 percent since January 2006 according to the U.S. Federal Reserve. The current U.S. gross domestic product is 2 percent, U.S. inflation is 2 percent, and the 10-year government bond rate is 4.61 percent. And payment types received. Checks still outweigh credit cards, which you think in electronic age there'd be more credit card payments, but they are higher in both volume and dollar amounts. Thank you. Any questions? (No response)
MS. WINKELMAN: Okay. (Applause)
Engineering Department Report
MR. PLZAK: Next, engineering. The Director of Engineering, the Chief Technical Officer of ARIN, Mark Kosters. (Applause)
MR. KOSTERS: So I guess I'd like to start out saying I'm kind of both new and old to this business. So if you look back at the history of ARIN, it's actually nonprofit spin-off of Network Solutions, of which I was employed for 16 years. And I just recently joined ARIN a week-and-a-half ago. So I'm going to try to keep up the speed. There's a lot of things I need to learn, and I'd like to get some audience participation at this point. So --
MR. MANNING: Okay. So audience participation. How much of your original code from 16 years ago is still running in ARIN? (Laughter)
MR. KOSTERS: So -- I hear that part of it is still running.
SPEAKER: (off mike) qualified for --
MR. KOSTERS: Absolutely. So anyways, one of the things that it's -- is about ARIN I've learned is that is a very acronym-friendly sort of environment. And, you know, ARIN staff can answer this, but I wanted to ask the rest of you. What does "PSM" mean? (Laughter)
MR. KOSTERS: PSM. So -- actually I'm really glad to see that no one's raised their hands, because I had no idea, either. And what it means is, please see me -- in this -- (Laughter)
MR. KOSTERS: So this is one of the first things I learned at ARIN is -- PSM, okay, all right, good, good.
SPEAKER: (off mike)?
MR. KOSTERS: And no, I wasn't in trouble, but I --
MR. PLZAK: Mark, I'm just being polite. If you want I can change that acronym just for you. (Laughter)
MR. KOSTERS: So let's go -- keep on going here. So --
SPEAKER: The other acronym is YF.
MR. KOSTERS: YF? You're fired.
SPEAKER: You're fired, right.
MR. KOSTERS: Okay. I see that one coming. (Laughter)
MR. KOSTERS: So let's go ahead and do this. So here is kind of overview where I plan on going. By the way, Cathy did all these slides, and you can see her sense of humor getting after me here very shortly. So here is the staff. Ron Henderson is new, and one of the things that he liked to throw a -- dig me on is the year I graduated from high school is the year that he was born. So -- actually, if you could stand up, Ron, so that you all can see him, and he is the newest member of the engineering team. The other people are here that you probably know about -- you can sit down again, thanks. (Laughter)
MR. KOSTERS: The other people are here are Cathy, Matt Ryanczak, Ray Stark, and Tim. So -- and I'm sure you all know him; at least I did for a long time. So -- and back at the fort you can see that there is a group of engineers there as well. So I'm very happy about the staff. I've been able to talk to them, and I'm very impressed with their knowledge and their geekerie. So this is going to be great fun. So let's talk next about the WHOIS query load. And actually, one of the things that is part of that, you know, wherein your Internet companies everything goes like this, right? I know, it goes this way. (Laughter)
MR. KOSTERS: And you could see that ARIN is joining that popularity, and the WHOIS query rates are continually growing, and one of the things that's great about this. And this was one part of the code that they did replace that was mine, is in 2002 I believe they replaced it with several of the new code made by Abram. And it's actually doing quite well, and there has been no changes since, and has been able to keep up, which is great. So -- now here is the interesting slide. So when I saw this, I'm going, oh, oh, what does this mean? And one way of looking at this is, you know, when you're sick and you're close to death they put that thing on you just a EKG to see whether or not you're still alive, and then it kind of looks like this is a heartbeat and seeing whether they're not through out and registry is still alive. And I'm happy to tell you that it is still alive. So what you're seeing here, these spikes, are actually a researcher most recently out of University of Delft in the Netherlands actually doing some traversals via AS numbers. So you can see that it's kind of interesting. It is kind of on the low side frankly, though, it's like one query per minute. So there is not a tremendous use of this system, but it is there and it is being used, and it is still alive. This slide, this is basically talking about sort of the origin ASs and so on. This is a recent policy. This was actually passed by ARIN not too long ago, and was implemented very recently in 2007. And one of things that it does is it ties the origin AS to the network so people can actually see whether or not this route is actually coming from the right AS, and people can feel pretty comfortable about this. And what's interesting about this is -- and I could have these numbers wrong, but I'm pretty confident I have it right -- is about 25 percent of ARIN's registered networks are actually -- have their origin ASs associated with them now. And they're actually -- the accuracy is quite high. We actually looked against route views to see whether or not they actually match what was actually in the route views, and it turns out that this information seems to be pretty much dead on. So the origin found was incorrect, it was 91 percent, the origin not found or incorrect in some way was 8 percent, or route not found but was in WHOIS was 1 percent. So that's great, that's great. Glad to see it. So -- oh, Cathy has a question.
MR. KOSTERS: Oh, so -- that's a good question. I have here in my notes that there is 88 v6 networks. I don't believe that it was actually checked again for obvious. Is that correct, Cathy?
MS. ARONSON: Right. It's only the v4 that were checked.
MR. KOSTERS: Okay.
MS. ARONSON: Because it would be interesting, you know, that slide I always put up of Gerd's for the v6 and right, it would be interesting to do a similar thing with our routes and see what it look like.
MR. KOSTERS: Absolutely. I think it's a great idea. So anyways, from a geek perspective, I really like this slide, because that shows that one of the policies that was passed by you all was actually being used -- it's being used by the community, and it is making a difference. So this is awesome. So keep up the good work. So, okay, now we get into the fun stuff. Utilization reporting. And I think you all can figure out where this is going. We're going to RWhois land. And for you, who don't know, many, many years ago in a lifelong far away, there was a guy named Scott Williamson and I came up with this idea of RWhois. An idea for RWhois was actually to try to get various ISPs actually do their -- management of their own allocations locally. And the software wasn't quite right. And it's been kind of a pain, and has continued to be a pain for about 15 years. But what's interesting about this is that most people use SWIP, and the larger ISPs use SWIP as well. But there are still significant number of people that use RWhois. So, this slide is not so great in that it shows that approximately 40 to 47 percent of RWhois servers are down in some fashion at any one point of time. There has been monitoring being done by ARIN since 2004, and has been rather consistent. So this is something that it would be very useful for people to -- who have RWhois servers that are down now, to actually get them back up again. So please, please, make that happen. And going on to the next slide, you can see here are the reasons why the RWhois servers are not working. Most of them are basically unreachable, a large majority of them. And you can see that others are timing out in some fashion, which is close to being unreachable, or maybe about the same thing -- errors. There is a protocol problem with RWhois server that they put together; they need to read their RFC, or some other sort of error that's occurred. So now -- but on the positive side -- oh, you have a question.
MS. SCHILLER: I have a question.
MR. KOSTERS: Yeah.
MS. SCHILLER: Does ARIN staff notify --
MR. BRADNER: You should identify yourself, so people out there know you are in.
MS. SCHILLER: Sorry, Heather Schiller, UUNet, Verizon Business. Just wondering if ARIN staff notifies folks who have RWhois servers that are unreachable.
MS. SCHILLER: Okay.
MR. KOSTERS: So the answer from the floor is yes. So I'm glad to hear that. So everybody who gets those notes, please honor them and get those servers up. On the positive side, there has been pretty a significant growth in RWhois servers and the referrals. About 75 percent of the referrals are actually correct, which is better than the slides that we saw before. And over -- since 2004 we've almost had a doubling. A number of organizations have had RWhois servers. In 2004, there was 221 organizations that had RWhois servers, now there is 448. And in terms of RWhois servers that each of those organizations ran, back in 2004, there was a 194, now there is 405. And in terms of networks that were associated with those RWhois servers, back in 2004 there was 1,598 and now there is 4,731. So that's interesting source stat. So now here for the accomplishments, the staff has been actually really hard at work. A lot of the work has been done -- has been focused internally, but there's been a number of external things that you've seen. One is the DNS infrastructure for secondary services that ARIN offers, has been rebuilt and serving the community quite well and responding to DNS queries, that that part of the net has had dramatic growth. And I'm glad to hear that ARIN is doing a great job here. The registration tools are a continual enhancement of the template that just were put out. There is a lot of code that had to be put into that as well. PGP authentication just rolled out and is going well. There is a Lame DNS testing system that's been put into place. It's going around for the first month, I believe. And out of that -- the results, there were 32 really bad Lame delegations that have gone out, and people have been notified. We also have participated in a PCI audit and -- who knows what PCI is? (No response)
MR. KOSTERS: Okay. So Owen, answer --
SPEAKER: Payment card industries.
MR. KOSTERS: Payment card industries. That's close enough. So basically what they do is, they audit the system, and to make sure that we're in compliance with their policies and procedures. And they look at for multiple asset -- facets, but the big one from the technical community is making sure that our security is in place, and we have the right sort of procedures going forward.
MR. BRADNER: And the results were?
MR. KOSTERS: The results were --
SPEAKER: We took back the --
MR. KOSTERS: Okay. So it's upcoming. I hear that we're pretty clean. Is that right?
SPEAKER: (off mike)
MR. KOSTERS: Okay. So work in progress. A lot of this is actually internally focused. So from -- as a outsider looking in and now a insider looking out, I can kind of understand why you're looking at this and saying, "Well, this doesn't make a lot of sense to me." But a lot of this stuff has to do with sort of compliance sort of issues to making it easier on the engineers internally. Internal authentication -- we have LDAP server that actually authenticates users now. Formalizing data storage requirements -- and this deals with actually tying together various parts of the system whether it be Registration Services, membership services, and financial services together and make the integration more seamless. We also have to -- we're going to go through a pretty significant challenge. Some of the systems that are internally -- not only are they running some of my code, but I remember some of those boxes -- they look really familiar for me since they are now 10 years old, and we have a lot of work to do on cleaning those up and moving them out. We might have a history museum in the making, we'll see. (Laughter)
MR. KOSTERS: And finally this is really cool sort of geek work is research -- resource certification which has brought -- been brought to you in the past. That work is under way, and it's doing quite well. So what's ahead? We have -- financial services has a new way of looking at revenue and we have to support that. Infrastructure improvements -- trying to make things act more reliable. Follow-up tasks from the PCI audit that you're going to be talking about. And first -- and also this is sort of foreshadowing of something coming. And I'm not going to say much about it yet, but you'll hear about it I'm sure in the next ARIN meeting. We have some customer service interface improvements that I think that you all are really going to like. So with that said, do you have any questions?
MR. WOODCOCK: Mark, before you sit down, you should know that Owen put a $5 bounty on the first person to say "Fix Rwhois" at the mic, and in honor of Bob Stratton and because it's all we have handy, it's being dispersed in euros. (Laughter) (Applause)
MR. KOSTERS: I think this is more than $5 now, isn't it?
MR. KOSTERS: Wow, I'm rich.
MR. PLZAK: Okay. Well, on the RWhois vein, I was also an employee at Network Solutions at the time that Scott and Mark wrote that, and my motivation for bringing Mark onboard was I got tired of hearing the community and him say things about Rwhois, so he's now got it. (Laughter)
Human Resources and Administration Department Report
MR. PLZAK: Okay. Now -- well, actually the other person that is a member of ARIN staff that was working for Network Solutions in those days of course is Leslie. So we got couple old heads here. So anyway. Human Resources -- Mary K.
MS. LEE: Okay. All right. Very good. Good morning. As you can see, we've hired a couple of new people with one more starting next week, and one of our new requirements is that all people we hire must have a great sense of humor. So I'm glad to see that's working well. Okay, just going to overview like everyone else has done. Our department staff, a little bit about us. And I've resurrected the computer survey from about five, six years ago since that seemed to be the most popular. Therese and Teresa are both back at the office. We've kept them working. Therese may not be here, but she was on the phone this morning taking minutes for the Board meeting as she did Wednesday morning. And Teresa is always busy back at the office because so many of us go away, it's kind of chaotic without someone to keep an eye on things; and myself. A little bit about us. Here is our three logos through the years. You can see it's changed quite a bit. The last one obviously is on the bottom. We will be (sic) 10 years old on December 22, 1997. At that time we had 16 employees, it was 8 women and 8 men. And then December of -- five years after that, December 22, 2002, we were up to 35 employees -- 16 women and 19 men. And as of this week, 43 employees full time, it will be 44 on October the 29th, but right now it's still 43, one part-time, and 23 men and 21 women at the current time. I was requested by one of my colleagues to no longer state our average age, so I won't do that today. (Laughter)
MS. LEE: However, I will tell you our average tenure is 4.7 years, so almost 5 years at this point. Nineteen employees have been at ARIN for five years or more, and we've had two recent five-year anniversaries, Tanya Gomez who is back at the office and Matt Ryanczak who is in the back of the room. Our current projects -- this is either current or pretty much complete. We transitioned to a new payroll company on July the 1st of this year. It's going quite well, very smaller company, but they cater to smaller companies, they're aligned with our 401k companies so I get better reporting from them on both areas. We have been working not so diligently on our business continuity plan as well. We have pieces of it that we need to put together into a cohesive whole. I want to thank Andrew de la Hoya who met with us earlier this week, and he gave us an overview of how they went through the process and kind of an outline of things. So we'll be working on that quite a bit, and of course we'll have Mark Kosters involved in that as well. And last year, we did a company culture survey. We put it out to the whole company. It's really just to -- who are we internally, you know, what kind of place is it to work. And it was a very simple survey. We just asked, "Describe ARIN's culture." Second question was, "What would you keep the same?" And the third question was, "What would you change?" Well, I formulated a bit of it into a report that the (off mike) are going to see pretty shortly. And then we actually plan to get back to the staff and show them, okay, here is the things you wanted to keep, hopefully we're still doing those, and here is the things that you -- we recommended changing, some of which of course we'll try and change. Sometimes you can't always do everything that everyone would like. This is the staff computer survey. I'll give everybody a minute to look at this. Had really great participation this time, about three quarters of the company answered. In the past, I did a comparison of number of computers per household versus number of children per household, but I didn't ask the number of children this time, just the computers. Matt Ryanczak helped me put these little steps here together. So if you have any questions, please address them to Matt -- thank you. And I want to thank the staff for answering the survey, thought it was kind of fun. And thank you all. (Applause)
MR. PLZAK: Any questions for Mary K.? (No response)
MR. PLZAK: Okay. What we'll do now is do the report from Susan on the consultation and suggestion process. You are now standing in the way of the break.
MS. HAMLIN: I'll be really quick. Just a status report. The ARIN Consultation and Suggestion Process was introduced, September of last year. And it serves two purposes. It is a mechanism for the community to provide suggestions or changes they would like to see to ARIN services and practices, and it is also a mechanism for the Board or the President to solicit feedback from the community or members about ARIN services or practices. A couple of things that have -- we have made some improvements in the process, some of them based on suggestions. We have also posted an archive of all the suggestions and consultations on the ARIN website. So these are a few of the things that were changed based on community input. We tried to clarify the process, make it easier to find, make the form clear. We changed the format of the responses back to suggesters to be a little more friendly in tone. We do take all of these suggestions seriously; spend a lot of time internally reviewing them, talking about them, discussing them, so we wanted to make sure that that was conveyed in our responses. And also in July of this year, the actual document was amended by the Board to add a requirement that the president respond to the submitter within ten business days. Either explaining what action will be taken or to give a date when we will be able to announce the action to be expected. These are the statistics -- the use of the ACSP since, as of 30th September. You'll see that we've received a total of 40 suggestions, and if you look down, these are the actions. We currently have two pending. We have seven on which action was taken, 16 where no action was required, either because ARIN was already working in that area, those things were addressed in other means, and the very bottom, spam. So consultations -- this is the other part of the process, and sometimes a suggestion comes in, and it is felt like we need more input from the community in order to know what direction to take. So we have had two consultations both of which dealing with WHOIS and directory services and the results of that feedback are being funneled into a project that will, I think is on the road map for early next year. And as Ed Lewis pointed out a couple of times this week, we have a consultation currently opened until the 23rd of October dealing with Lame delegations. And if you go to the homepage of the ARIN website, on the right- hand side you will see a list of URLs and there is one currently highlighted that says, "consultation underway" and if you click on that it will take you to the message and it will explain the questions we are asking and we would encourage everybody to participate. So that's it. Questions? Suggestions? Okay, thank you.
MR. DUL: Andrew Dul, Perkins Coie. I made a suggestion shortly around the last meeting about developing a website for members to see and use the resources. And the answer I got back was we would have an update at this meeting. So I was hoping there would be something in the Members Meeting this morning, but I haven't seen something so far.
MR. PLZAK: Actually -- excuse me. Actually Mark mentioned that in his report.
MR. DUL: But he basically said, you are sort of, working on it. I was hoping for more than that.
MR. PLZAK: Yeah, the answer is, yes. You will see some things starting to pop out early next year. As you can imagine, there are a lot of things we have to figure out in which order to integrate services, we have to keep services running at the same time. We also are working at the same time in the web compliance issues and so forth, but it is underway. We have a work plan. We are identifying if we have to attain any other additional resources and so forth. So there is a lot of work underway on that.
MR. DUL: Great. Thank you.
MR. PLZAK: Yeah. (Applause)
MR. PLZAK: Okay, and I am standing in the way of the break. Okay, a reminder, the help desks are open. And please, if you have questions about the election, and want to talk to a living breathing person, Erika will be glad to talk to you about elections. And the refreshments are available. We will resume back at 10:45, 15 minutes from now. (Recess)
ARIN Advisory Council Report
MR. PLZAK: Okay. Let's get started. Now we have three reports. The first of which will be the report from the Advisory Council, by the chair, Marla.
MS. AZINGER: Okay. Hello, my name is Marla Azinger, and over the past several years, it has become apparent to several members in our community that adjustments to the current AC processes were needed. Since January, I have been working with the AC on organizing and improving our process, and we have also been using a time-release implementation plan since we all have day jobs too, so it's a lot of work. The changes that have been made were analyzed, and voted on by the AC before implementing, and then we proceeded forward. This is the overview of the two subjects I am going to cover; Advisory Council improvements, what I just briefly spoke of, and then I will get to the policy proposal update from our meeting last night. So change is good. Do not fear. We have done quite a few things. As you can see the list is a little long. Sorry, the slide is kind of full, but we have relocated the time in which AC Shepherds are assigned to proposals. In the past a shepherd was not assigned until after a proposal was discussed at the AC initial review. Moving the shepherd assignment forward, we now work with the authors at an earlier date and achieved comprehensive initial reviews. Sorry, my notes are on a different thing here. So the process was slightly revised in just a quick review. The policy proposal template is received by ARIN, and acknowledged by ARIN. And then within one business day of receipt of the proposal, ARIN announces the proposal to the community via PPML and the ARIN website. Then ARIN sends a message to the Advisory Council mail list -- mailing list asking the chair to identify shepherds for the proposal. We get two shepherds and then, I send that back to, as chair, to ARIN, and then they notify via PPML who the shepherds are. In addition to this, we now require primary shepherds to fill out a proposal report, prior to the AC initial review meeting. This new step has been successful in ensuring that proper analysis, and research, if necessary of the proposal is done before, the initial review. This makes it easier for the AC to ensure a proposal gets a proper initial review, because with this proposal report, we have a very clear picture of the proposal's current written state and the intent. The process, no later than one day prior to the AC initial review meeting, the Shepherd will send a proposal report to the AC. We have realigned the motions we were allowed to make on the AC with proper Robert's Rules of Order. The actions of the motions are relatively the same. However, following the Robert's Rules of Order, we find things are better clarified in the vocabulary, is not offensive. The process, at the conclusion of the discussion of the proposal at the initial review meeting, the AC will take one of the following actions; accept the proposal, postpone the decision regarding the proposal until the next scheduled AC meeting in order to work with an author, or not accept that proposal. After the conference call has ended, the proposal shepherds now send a personal e- mail to the author, with pertinent details regarding what decision has been made, and why, and details on any further action that may be required from the author. In the past, authors were not immediately given feedback, and most often received the outcome of their proposal via PPML, which we felt was just too impersonal and not -- we could serve you better, so we changed it for you. So the process, the shepherds inform the author of the proposal, of the action taken by the AC regarding the proposal within one business day. Then two business days after the meeting, ARIN will inform the community as a whole of the action taken by the AC via PPML. If the AC does not accept their proposal, ARIN will also inform the proposal author of this petition, of the petition option. After a conference call, the AC works with ARIN staff to ensure the PPML e-mail includes informative details when a proposal has been postponed or not accepted. In the past, you just got, it was this or that, and no details. Now we actually are giving more information so you all know, what's in our minds and why we made the decision we did. AC has now made a commitment to ensure operational and administrative details will not be added to NRPM. And that the current ones in the NRPM will be worked out and relocated to a more accurate document and the ARIN staff is actually helping on that. So it has just passed all the changes we made for you all, and gets us to what we have all been here for this week. Policy Proposal 2007-19 - IANA Policy for Allocations of ASN Blocks to RIRs has been moved to last call. Policy Proposal 2007-21 - PIv6 for legacy holders with RSA and efficient use, has been moved to last call. Policy Proposal 2007-22 - Expand Timeframe of Additional Requests, has been moved to last call. Policy Proposal 2007-25 - IPv6 Policy Housekeeping, moved to last call. Policy Proposal 2007-16 - IPv4 Soft Landing, we chose that we want to work with the author on some edits and take the community input, so that's what is being done. Policy Proposal 2007-17 - Legacy Outreach and Partial Reclamation, again we felt that we needed to take some of the community input and work with the author on that and make some revisions. Policy Proposal 2007-24 - IPv6 Assignment Guidelines, again work with author. We had a lot of good community input, so we are going to work with revisions on that. Policy Proposal 2007-14 - Resource Review Process, being redundant, yes, sorry, but we are going to work with the author given with the feedback we got from the community. Policy Proposal 2007-18 - Global Policy for the Allocation of the Remaining IPv4 Address Space; we abandoned this one. Policy Proposal 2007-23 - End policy for IANA, IPv4 allocations to RIRs; so we abandoned one and we chose to work with the authors on 2007-23 but we also are going to work with authors from 2007-18. We are choosing to combine the efforts into just one document, given the feedback of what -- it sounded like the community preferred most, so the one document reads as abandoned, but we are not saying goodbye to those authors. We actually want to work with them on one document with the other one as well. Policy Proposal 2006-7 - Changes to IPv6 initial allocation criteria; based on the feedback from the community and no revisions, we abandoned this one. Policy Proposal 2007-15 - Authentication of the legacy resources; this one was withdrawn by the author. Policy Proposal 2007-13 - Removal of ISP Immediate Need from End-user; again this one was withdrawn by the author. And I would like to thank all the conference attendees, PPML participants, and all of our remote view attendees. Thank you. (Applause)
MS. AZINGER: Yeah, sorry, you can ask questions. Does anybody have a question? Thank you.
ARIN Financial Report
MR. PLZAK: I am sure there will be a few questions on the PPML, Marla. Okay, we are re-ordering the agenda slightly. The next report will be the financial report by Lee.
MR. HOWARD: Good morning. My name is Lee Howard. I am a Board member and treasurer, and I have a rare honor that I know, at this time I am least interesting -- that's a common honor for me, but I am not last, so I am not going to put everybody to sleep before you get on the airplane. I do have a couple of things to talk about some which are somewhat interesting, some which probably aren't. First, the statements, financial of -- actually our 2006 financial statements. And then some other changes that we have gone through, mostly in response to things that have been requested by members of the public and the -- and ARIN members. I would like to suggest that I think I've been through the 2006 financial statements and they have been posted on ARIN's website, if you go to, about us, and then corporate documents, our actual audited financial -- or our full audit report for 2006 has been posted for about a month or so now. So if you really want to get into details, go there. Otherwise, I've never had a question in five years on these statements, so we are just going to kind of cycle through it. This does of course become part of the record for the meeting, so would you go ahead and show us the statements of financial position? These are our assets and the next slide is our liabilities to see for comparative -- for comparison there. Next, is our statement of activities for comparing of course, end-of-the-year position, 2005-2006 as normally presented. And the last one, I'm sorry -- go ahead. And I changed net assets. I think the last one is escrows? Sorry, I'm sorry that was in that. The -- yeah, go ahead. Unless anybody wants to stop and ask me questions about those, I will go back and talk about those, but really, it is the most boring part of the thing that I do for the ARIN Board. Okay, again, perfectly willing to, you can always send me an e-mail. Again, go to the ARIN website, about us, Board members, and all of our e-mail addresses are up there. Send me a personal e- mail; I'd be happy to talk to anybody about pretty much anything. One of the things that we did this year, is we changed the way that we recognized certain revenue. This is to be compliant with the generally -- GAAP, generally accepted accounting principles. What we've done is, now, when we send an invoice for your annual renewal as an ISP, whether you would regard this a size category, we recognize that as revenue, on the date we send the invoice. This is what you are supposed to do and we hadn't been doing this initially, because when we stood -- for a couple of reasons, when ARIN started out we were actually using cash basis accounting and that is not part of generally accepted accounting principles under cash basis. So it wasn't really best practice then. As we moved forward, we changed some of our other accounting principles and this would kind of lag behind in becoming complaint with GAAP. Because we didn't have the history to know, how much we would actually collect. Was that my time being up? Is that what that was? So we haven't -- it didn't change that. We talked about this a couple of years ago and we decided that we need a little more history to know how much of our invoices would be uncollectible. Because what you do is, you send the invoice, you recognize this -- it as revenue, but then you also have an offsetting percentage as uncollectible. And we didn't have, we didn't know what percentage that ought to be, as we couldn't make a good guess there. What we've done is we were about to make that change, so we said, well you know what, we are actually making a major collections effort, so we are going to build a new history of what is uncollectible. We've had a fantastic record in the past, I think, it is two years, maybe it is almost three years, of going back on our overdue accounts and actually collecting revenue that was due. And so now that we have done all that and of course all -- you see here that our auditors this year did recommend it. Now that we have that history we are able to make this change and actually do things that make sense. I don't think that this is going to be material in ARIN's financial position, but it is just a change in the way that we do things. Go on. This is -- Mark talked about, the PCI credit card audit, the payment card industry audit. We, the Finance Committee and the Board talked about it. ARIN does accept payments through credit cards and there are audits -- there are best practices for how to accept payment. We said, "Hey staff, please go and make sure that we are compliant with the industry standards." So we had a vendor come in and they did perform an audit and we are happy with the way we do things. We talked about -- they did say, if we make certain changes in the future, which we may do in the way we process credit cards, they would have to come back in and audit us again. Fine, we are happy to -- we just want to make sure that we are doing things the best way, the way you are supposed to do them. Going on, that would be your -- since I am not using that -- I didn't bother learning to reading the manual for the control here. Another audit that we are doing this year, is the financial controls audit. This is something we did a few years ago, and we are pretty happy with the results. We are not, the inspiration was, I am sure you all remember, a few years ago, maybe financial controls in the Internet industry weren't maybe as good as they could be -- Jason and Heather. They got better, Sarbanes-Oxley Act was passed and we said, "Boy, there are some really good practices in there." What should we do -- you know, are there things, are there models that we can follow, similar to what is required by Sarbanes-Oxley? So a few years ago, the Board brought in an outside, contractor, somebody who is not our regular auditor, so that there wouldn't be a conflict of interest there, performed a review. They had some recommendations. There was one material deficiency in that we opened mail by -- one person opened mail instead of two people. So we fixed that one pretty quickly, pretty easy process to fix. And we decided that we want to do that audit again. Now, that's been a couple of years. The best practices for financial controls have sort of matured, and we want to know that we are doing the best we can. That is in progress, they are actually coming in later this year, and I hope to have some kind of report back to the Board early next year. Let me make sure -- check the slides here and make sure I've said everything I've wanted to say. Yeah, we are not required to do this but we want to make sure that we are doing, that we are being as rigorous as we can in the way we handle your money. So specifically in response to requests from, on PPML and ARIN discuss, and people in the halls, and private e-mail, and the solicitation and consultation process. Lots of different ways that people made requests for us to change how we structure IPv6 fees and waivers. So the existing waiver that the Board passed, I don't know, about four years ago, is expiring at the end of this year. So if you really like the waiver as it stands now, put in your application soon, because that waiver is going away. When that goes away, there will no longer be any waiver of fees for end-users, for end-user assignments, and IPv6. Right now, the Board has waived all, but $500 for end-user assignments for IPv6. January 1st, 2008, if you apply for an IPv6 assignment from ARIN, you will be expected to pay the full fee, and that's -- I think it is $1,250 for a small -- I think it is $1,250 for an extra -- for a small under /32. I think that's how it is categorized. Obviously, go to the main website, under -- lets see -- under billing, there is the fee schedule. It is on there, it is pretty clear. I like -- it sure is going to be on the later slide too, so we will refer to that one. Okay, so that's the -- so there is the end-user assignments. For many ISPs in our region who already have an IPv4 allocation from ARIN, you are paying your annual renewal, you are a member in good standing; we are continuing the waiver of the initial fee. So if you already have IP -- and IPv4 allocation from ARIN, you come into ARIN and say, I need IPv6, and you go through the regular approval process, you are a member in good standing, and of course this is under the same org id, then the initial fee is waived. You don't pay the initial $4,500, $9,000, or $18,000. And for renewal fees, you will only pay either your IPv4 renewal or your IPv6 renewal, whichever one is greater. So we are not trying to double hit you on these allocations. We want to do -- one or the other will make sure you are still know this. All right, next slide. As we went through this process, we had heard several times from the last meeting, and on the mailing lists that the description of the fee waivers wasn't clear. And I promised then, and I promised in the mailing list that we would work on it, and we would try and clarify that. We have done that -- there was an announcement; we tried, we worked very hard to make sure that we were happy with the way the information is presented. I hope it is clearer now, I hope that what I've explained here has helped clarify. I really want people to understand what we are trying to do. There is no benefit to anybody for -- of ambiguity. I really want to make sure that it is clear. If you have suggestions that is not clear, or you want other -- want other clarifications, let me know, we will work on the language some more. What we tried to clarify was that, again what I just said, any organization that has an IPv4 allocation and IPv6 allocation will only charge the greater of the two. And that this is -- and we're trying to encourage, we're trying to lower the bar for entry into IPv6. We don't want to be perceived as hindering the adoption of IPv6. So here is the new waiver that the Board has adopted. And this was suggested by a member of the community. And this was -- and actually we had almost 15 separate suggestions that the finance committee considered individually. Every single suggestion for how to structure IPv6 fees was an agenda item at a finance committee meeting. This is -- we had several that we thought were very interesting and were worth further consideration, we're going to come back to those. This is the one that we could adopt and recommend to the Board for adoption, and so this is where we ended up, so this where we are now. This is the declining fee waiver. So what we have is, you can see, based on your size category, and again I think /32 is the default size for an ISP allocation. That puts you in a small category. So if you have a -- if you are a small ISP, meaning you have /32, that puts you in the small category. The base fee would be $2,250 per year. Again, that initial allocation fee is waived if you have an IPv4 allocation from ARIN. Then what we're going to do is we're going to waive part of the renewal fee over the next several years. And the part of the renewal fee that we're waiving is represented here. In 2008 we're going to waive 90 percent of that. So you -- if you're a small, you have a /32 IPv6 allocation from ARIN your renewal fee next year is $225, which seems like a pretty low bar. And then that increases, we're waiving 90 percent at the first year, 75 percent at the second year, 50 percent at the third year, 25 percent after that. That's typo up there. It's not 75 percent again, sorry about that. Funny, several of us who are very good at details looked at -- I mean, three very detail oriented people -- Erika is laughing -- very -- three very detailed oriented people looked at this, we changed punctuation, we didn't catch that one until I was standing up here right now. So it's only 25 percent waives the -- in 2011. And I believe the number of the math there is actually correct even though the 75 percent on the digital int. count is incorrect. And then -- so in 2012 that's what it is. One very nuanced point, that it is conceivable that a future Board could adopt a different fee structure. This is what we intent, this is what we plan to do. It's possible that this could change so I need to warn you that there -- that we always have that potential that would be, of course, continuing in response to input from the members and from the community. And I think that brings us pretty close, there we go. Always, I think we've been -- oh, there is one more thing that I have to say. I promised Allie at the beginning of the week that I would say something nice about Microsoft. I think that Microsoft's PowerPoint product has done a very nice job of conveying information here. Thank you very much. (Applause)
MS. SETTLEMYRE: Thank you, Lee.
MR. HOWARD: You're welcome. Did anybody else have any questions, or comments, or further information? Of course, you have my e-mail address on the mailing -- great, thank you.
Board of Trustees Report
MR. PLZAK: Okay. Next on the agenda is the Board of Trustees report by the Chair. John.
MR. CURRAN: Thank you, Ray. Hello and welcome. I'm here to report on the activities of the Board of Trustees since our last meeting. I'll start out in the policy area. We -- following the recommendations of the Advisory Council adopted policy changes 2007-4, 7, 2007-7, 2007-8, 2007-9, 2007-11, all those have been incorporated into your policy manual. We didn't actually adopt a few recommendations. Some of the recommendations were more of the nature of administrative matters. This was with respect to adding authentication methods, PGP authentication, mail-from authentication, making that a little more formal. The Board actually adopted the essence of the recommendation, noted that they weren't per se policy proposals, and then we went on to look at the ARIN Consultation and Suggestion Process to make improvements there so that it was clear that people should be -- can make use of that for suggestions, that there was better accounting of the suggestions made, and you saw the presentation earlier. We're going to make sure that suggestions that come from the community don't get lost, are visible, get well heard and well reviewed. Then moving on from there into governance matters we spent a bit of time working on the conflict of interest process for Board members in terms of agreements and disclosures. This became particularly important because we knew we were going to move into matters like discussing policies on legacy addresses and it's important for us to know exactly where everyone stands, so we have a very formal, very tight conflict of interest process and disclosure statement that we all went through. Also one of the things that comes up as we begin to look at the upcoming depletion in IPv4 resources is we're really concerned that this is a member community, it was representative of the membership, so we spent some time looking at making sure that ARIN couldn't be captured or taken over, we looked at anti-takeover provisions and considered them just to make sure that it would be hard for someone to come in and displace all the Board members or all the AC to get a policy through. And we've taken no action there, we studied the matter, we feel pretty confident. There may be something in the future we need to do. But, in general, the way we staggered terms, and the way that we are actually nominated and elected we're pretty sure that you're not going to see all of us representing some one firm like a big company, or big provider, or a software company. It would be very hard to accomplish that. But we did spend quite bit of time looking at that just to make sure that we are well organized for the coming years ahead. Legal matters, actually Counsel already gave his formal report, but I would just like to highlight, we did -- the Board was heavily involved and ended up working with Counsel to get the final dispensation on the Kremen matter, also on the arin.com matter. Financial, the Board is always heavily involved in financial. Lee gave his report. He talked heavily about the IPv6 fee waiver, the schedule we adopted to provide people certainty. I'd also like to note some other things the Board was involved in that area. We did adopt a formal statement saying that we'd have two year operating reserve at all times. We feel that's the right thing for us to. Particularly, if you look at 10 or years, we're not sure exactly how we want fees to go. It's good to have a reserve. So if we need to change dramatically the structure we have time to do that and introduce that to the membership. We also, of course, began work on the 2008 budget because we want to start that work early and get it out of the way. I guess the last area I will dive into is strategy, which is where the Board increasingly needs to pay attention. It's not necessarily the same status quo situation we have in the past. So amongst these items include -- earlier in May this year May 7th the Board issued a statement which formally told the community that we foresee the fact that we will be unable to satisfy a need for contiguous IPv4 blocks going out some number of years. This statement is a statement of, pretty much, fact. The free pool curves, we all know what they look like. But you'd be amazed though, well we all know this in the room, there is a lot of folks out there who truly do not understand what's happening with IPv4 and the depletion of the free pool. So we issued that statement, spent a bit of time talking about the press, talking to actually some of the members. While we have great representation here amongst the community and the members I actually had some number of folks call us up directly and say you didn't tell me we were running out. Well, okay, that's important to know. If you're a nationwide backbone and your capital cycle is three to five years you might want to know that this is happening. So it's actually a very good thing to do. It did raise the awareness. We have had people say, you know, ARIN is running around waiving a flag screaming the world is ending. It's not ending, but if you're looking at five year plans you probably want to know about the IPv4 depletion. So we did that. It also caused some other follow up. We've -- a number of us -- we all talked to the other RIRs, but a number of us actually managed to get together informally with them in San Juan and have a discussion about this matter, and the fact that it is a global matter, it effects all of the RIRs. And some of that is just discussing how our policy processes will respond to this and what happens if we do need to change policies, how that will occur. I think you actually saw some follow up of that. Raúl posted a message through a mailing list saying we need to think about how to get global policies made, particularly if we have to do them quickly. We have no good answers to this. But the RIRs are aware that we may need to act in a bottoms-up but well coordinated manner because we don't want a comma or a punctuation mark to cause what's otherwise a global policy change to be delayed for six months or a year. Also along the lines of policy changes I will say that we looked a little bit at the -- at the policies that we used, the Internet Resource Policy Evaluation Process. It's recognized that that process is, has always a -- something that can always involve continuous improvement. We actually met as soon as today and talked about improvements to it. Now, one of the problems we have is that as the Advisory Council, which has been remarkable and it's, as Marla pointed out, remarkable in its maturity and its ability to handle the work in a professional manner. We need to look at the -- now the process itself and make sure that we can get proposals in front of the AC that are well thought out, well considered, have a lot of the kinks worked out so that we don't end up wasting everyone's time. So the Board is actually looking at that and taking lot of feedback from the community and the AC on how to better run things. We will be working on that going forward. I just want to end with the fact that, of course one of the items that takes-up a lot of the Board's time is looking at this change coming up with IPv4 depletion. We did actually contract to have Ben Edelman, who actually, as you know, was here this week, come and educate us, because Ben is an economist, and the Board is not made up of economists. And one of the things that happens is, we want to understand the pros and cons if some of the more wild proposals that have been kicking around in the community would be adopted. So as an educational measure we've been trying to improve the Board IQ as to how things work in a whole bunch of models. So I don't want anyone to feel concerned about that. It truly is the Board being prepared so that we can do reasonable assessments. It's a forecast or a direction per se. We did do a little bit of work, which I guess could be a little forward leaning, which is that one of our policy proposals called for the creation of a legacy RSA. And I think everyone noted that a legacy RSA was forthcoming from ARIN just about a week ago. We wanted to get it out before the meetings so that there will be time for comments. I think there was one or two comments on the mailing list about it, and the Board actually had heard those comments. We've actually incorporated it already, we've begun to make a list of changes to make the RSA more community friendly, and I'm happy to say that includes changes to areas such as section 9 of the RSA, what resources are actually governed by a legacy RSA. It also will include changes to termination to make sure that if for some reason ARIN doesn't live up to its obligations and parties have to walk away, you walk away the same way you came into the game with your legacy resources in your hand. So, we are trying to be very flexible and hear the community. At the same time, of course, the Board has a responsibility to protect the mission of the organization and so it's a balancing act. We will see probably a new legacy RSA come out, an updated FAQ, sometime by the end of next week. That's it for the Board report. It doesn't seem like much for six months. But I know it seemed like a lot when I was doing it.
MR. CURRAN: So I guess along those lines I am done with the report, and I would also like to note that we're moving into an open microphone session. So the floor is open for matters of my report, earlier presenters, or the ARIN open mic.
MR. PLZAK: John, please remind them that this open mic is not for discussion of the past two days or any policy related matter.
MR. CURRAN: Right. We try to constrain this last open microphone to issues of the organization, its structure and operation, and not to rehash policy proposals. It's also just, I'll note, the AC met last night, made some decisions, so rehashing policy proposals wouldn't exactly be productive at this form, it's much better taken up on the list.
MR. LEWIS: Yes, Ed Lewis, NeuStar. Lot of time I bring up the performance of ARIN services at the open mic, and I want to thank you, this time, for having handout in the brochure saying this is what is happening, although the web servers are up 1100 percent of the time -- cut some of the budget there, I think.
MR. CURRAN: Okay. Good to know. Microphones remain open. Microphones remain open. Any matter on ARIN organization, structure, operation. The microphones will be closing shortly, very shortly.
MR. CASSIMIRE: I'm --
MR. CURRAN: The microphones are closed. (Laughter)
MR. CURRAN: We have someone here, yes.
MR. CASSIMIRE: I am Nigel Cassimire, Caribbean Telecommunications Union. This is my first experience at an ARIN public meeting, and it was a very pleasant experience. I like the dynamics in the room and the way that -- I think there is an openness here that is very useful for the progress of the internet and the work that is being done here. Again, this is my first experience with the -- actually being in the policy development process. And one suggestion I would have -- it might be just because I'm new --in terms of the information provided during the policy discussions as so on, one thing that I would have found useful would have been an idea of the number of people that would be affected by a particular policy change. All right. So if, for example, some of the information that's provided during the discussion is -- and this policy we expect to impact maybe X percent of the user base or only the extra, extra large constituency or something like that. So some of them you can infill from what is given, but sometimes it's not the case. And also some --
MR. CURRAN: So noted.
MR. CASSIMIRE: And also some data elements as well because there were a couple of the policies during the discussion we -- one had to refer to ARIN staff to maybe get some statistics on what the impact would be. So those things I think if we could anticipate some of those questions coming before hand I think it would also help to improve the discussion and the progress of the policy discussions.
MR. CURRAN: Excellent suggestions. There were similar discussions going on among the Board members this morning about anticipating the need for staff and policy proposal interaction. And I think we will take those suggestions and add that into the mix of what we're trying to work on based on what we've heard from AC members and the community at large. Yes.
MR. LEIBRAND: A follow up to that. I really applaud ARIN's work to add staff comments since I first started getting involved. I think these are along the line of extending that. So I would be heartily in favor of extending the staff analysis in advance and putting that out with the current staff comments.
MR. CURRAN: If you say much more I'll suspect you were listening to our Board meeting, but, yes, that's a great idea.
MR. LEIBRAND: I was not, but I will say that either great minds think alike, or we're all not so great.
MR. CURRAN: We're all subject -- I think we are all subject to the same consequences and see the impact. I think, in particular, the ability to see those comments and make sure at least as the clarity of the proposal and its interaction with the policy and the current practices should be well understood before the meeting. Microphones remain open. Actually, I closed them, I guess. (Laughter)
MR. CURRAN: But we have lots of time. If anyone has one pressing item -- no? Okay, they truly do remain closed. Thank you very much. (Applause)
Closing Announcements and Adjournment
MR. PLZAK: Thanks John. We are now to the portion of the meeting that the staff thinks never comes. Okay, first of all reminder, if you do have a wireless card please return it to the registration desk before leaving. And also reminder, the wireless network will shutdown after the members meeting. So when is after, guys? Give me a time, like when the last person is out of the room.
MR. PLZAK: Noonish, okay, how is that? Noonish the network will be down. And I will not define noonish. All right remember, your input is very important and periodically people say that they really like the way we do things at the meetings as so forth. Well, part of the reason that we do the things they way they are at the meeting is because you tell us what to do, and so please fill out these surveys, it's very, very important to us. And also remember we not only have one, but we have two lucky winners, and one more round of applause for Shaw. (Applause)
MR. PLZAK: A thank you to Merit, because they are the ones that have been running the wireless network. So Merit, thank you very much. (Applause)
MR. PLZAK: And thank you to our sponsor One Connect IP. (Applause)
MR. PLZAK: Thank you to you, and also I would please ask the ARIN staff to stand. I want to personally thank you. And the staff that is at home please stand, we want to thank you as well. (Laughter)
MR. PLZAK: So thank you guys. (Applause)
MR. PLZAK: Reminder. The polls will be opening. And we have two very important elections.
SPEAKER: They are open.
MR. PLZAK: Okay. They are open. That's right, they opened in the Eastern Time -- we are -- so they are now open, please vote. You have right and a responsibility and a privilege. There are two very important elections as you heard in the candidate's speeches there are lot of things that have to be take care of as we go forward, so please do vote. And with that I say thank you, and I'll see you in Denver.
(Whereupon, at 11:28 a.m., the PROCEEDINGS were adjourned.)