From info at arin.net Mon Aug 3 16:40:40 2009 From: info at arin.net (Member Services) Date: Mon, 03 Aug 2009 16:40:40 -0400 Subject: [arin-announce] [arin-ppml] Lower End User IPv4 threshold to /24 In-Reply-To: <4A774A7B.3010109@arin.net> References: <98685203-69C4-4409-9A69-7FE956364A22@delong.com> <4A774A7B.3010109@arin.net> Message-ID: <4A774B48.3030601@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Member Services wrote: > ARIN received the following policy proposal and is posting it to the > Public Policy Mailing List (PPML) in accordance with Policy Development > Process. > > This proposal is in the first stage of the Policy Development Process. > ARIN staff will perform the Clarity and Understanding step. Staff does > not evaluate the proposal at this time, their goal is to make sure that > they understand the proposal and believe the community will as well. > Staff will report their results to the ARIN Advisory Council (AC) within > 10 days. > > The AC will review the proposal at their next regularly scheduled > meeting (if the period before the next regularly scheduled meeting is > less than 10 days, then the period may be extended to the subsequent > regularly scheduled meeting). The AC will decide how to utilize the > proposal and announce the decision to the PPML. > > In the meantime, the AC invites everyone to comment on the proposal on > the PPML, particularly their support or non-support and the reasoning > behind their opinion. Such participation contributes to a thorough > vetting and provides important guidance to the AC in their deliberations. > > The ARIN Policy Development Process can be found at: > https://www.arin.net/policy/pdp.html > > Mailing list subscription information can be found > at: https://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > ## * ## > > Owen DeLong wrote: >> TEMPLATE: ARIN-POLICY-PROPOSAL-TEMPLATE-2.0 >> >> 1. Policy Proposal Name: /24 End User Minimum Allocation Unit >> 2. Proposal Originator: Owen DeLong >> >> 3. Proposal Version: 0.9 >> 4. Date: 8/3/09 >> 5. Proposal type: new >> 6. Policy term: permanent >> 7. Policy statement: >> >> Replace section 4.3.2.2 of the NRPM with the following: >> >> 4.3.2.2 Multihomed Connection >> >> For end-users who demonstrate an intent to announce the requested >> space in a >> multihomed fashion to two or more distinct providers, the minimum >> block of IP >> address space assigned is a /24. If assignments smaller than a /24 >> are needed, >> multihomed end-users should contact their upstream providers. When >> prefixes are >> assigned which are longer than /20, they will be from a block >> reserved for that >> purpose so long as that is feasible. End-users may not receive a >> block smaller >> than /22 under this policy if they already have resources from ARIN, >> except as >> specified in section 4.3.6.2. >> >> Renumber the existing paragraph under the 4.3.6 to >> 4.3.6.1 Utilization requirements for additional Assignment >> >> Add the following paragraph 4.3.6.2 >> >> 4.3.6.2 Replacement assignments for small multi-homers >> >> Any end-user that possesses an assignment smaller than /22 under any >> part of >> section 4.3 shall not be able to get an additional assignment unless >> they agree >> to return all existing assignments within 12 months of receiving a >> new assignment. >> The new assignment shall be sized to accommodate their existing >> utilization in >> addition to their justified additional growth space under section >> 4.3.6.1. >> The common cases for this are expected to be a /24 returned after >> receipt of a /23, >> or a /23 returned after receipt of a /22. >> >> 8. Rationale: >> >> This policy attempts to incorporate the recent and historical >> discussions of >> policy for multi-home users on PPML. The intent is to provide as fair >> a process >> as possible for multi-homed organizations down to the smallest >> feasible size >> while still preserving some control over growth in the routing table. >> >> It has been repeatedly noted that /24 multi-homers exist today with >> PA space >> and still occupy a routing table slot, so, it is unlikely that moving >> this >> boundary to /24 would significantly impact the routing table. >> >> By requiring smaller assignments to renumber and return, rather than >> add more >> small blocks to their assignments, this policy seeks to further >> reduce the >> chances of unnecessary growth in the routing table and encourage good >> aggregation >> where possible. >> >> 9. Timetable for implementation: Immediate >> >> END OF TEMPLATE >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> PPML >> You are receiving this message because you are subscribed to >> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net). >> Unsubscribe or manage your mailing list subscription at: >> http://lists.arin.net/mailman/listinfo/arin-ppml >> Please contact info at arin.net if you experience any issues. > > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List (ARIN-PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-ppml > Please contact info at arin.net if you experience any issues. > From info at arin.net Tue Aug 4 11:03:44 2009 From: info at arin.net (Member Services) Date: Tue, 04 Aug 2009 11:03:44 -0400 Subject: [arin-announce] [arin-ppml] Multihomed Microallocations In-Reply-To: <4A784D69.3060802@arin.net> References: <3c3e3fca0908031556y1d0ba367kc92761a23b8b0fcb@mail.gmail.com> <4A784D69.3060802@arin.net> Message-ID: <4A784DD0.4030204@arin.net> The following is a new policy proposal that has been posted to the ARIN Public Policy Mailing List for discussion on that list. Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Member Services wrote: > ARIN received the following policy proposal and is posting it to the > Public Policy Mailing List (PPML) in accordance with Policy Development > Process. > > This proposal is in the first stage of the Policy Development Process. > ARIN staff will perform the Clarity and Understanding step. Staff does > not evaluate the proposal at this time, their goal is to make sure that > they understand the proposal and believe the community will as well. > Staff will report their results to the ARIN Advisory Council (AC) within > 10 days. > > The AC will review the proposal at their next regularly scheduled > meeting (if the period before the next regularly scheduled meeting is > less than 10 days, then the period may be extended to the subsequent > regularly scheduled meeting). The AC will decide how to utilize the > proposal and announce the decision to the PPML. > > In the meantime, the AC invites everyone to comment on the proposal on > the PPML, particularly their support or non-support and the reasoning > behind their opinion. Such participation contributes to a thorough > vetting and provides important guidance to the AC in their deliberations. > > The ARIN Policy Development Process can be found at: > https://www.arin.net/policy/pdp.html > > Mailing list subscription information can be found > at: https://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > ## * ## > > William Herrin wrote: >> 1. Policy Proposal Name: Multihomed Microallocations >> 2. Proposal Originator: William Herrin >> 3. Proposal Version: 1.0 >> 4. Date: 3 August 2009 >> 5. Proposal type: new >> 6. Policy term: permanent >> 7. Policy statement: >> >> 4.4 IPv4 Allocations and Assignments to Small Multihomed Organizations >> >> 4.4.1 Section 4.4 specifies criteria for allocating /23 and /24 IPv4 >> address blocks to end users and ISPs where the requesting organization >> is multihomed with multiple Internet vendors but does not meet the >> minimum usage criteria for address allocation or assignment under >> Sections 4.2 and 4.3. >> >> 4.4.2 Except as specified in section 4.4, the requesting organization >> must also meet all criteria for receiving addresses specified in >> section 4.2 if an ISP or section 4.3 if an end user. >> >> 4.4.3 Criteria for allocation or assignment >> >> 4.4.3.1 The requesting organization must hold exactly one AS number >> and must already announce IPv4 addresses to the Internet via BGP using >> its AS number. >> >> 4.4.3.2. The requesting organization must announce IPv4 addresses to >> the Internet via at least two distinct Internet vendors. >> >> 4.4.3.3. The requesting organization must spend at least $8000/year on >> the Internet services in 4.4.3.2. >> >> 4.4.3.4. Upon annual renewal of the allocation or assignment received >> under section 4.4, if the requesting organization fails to demonstrate >> that it continues to announce IPv4 addresses to the Internet via at >> least two distinct Internet vendors the allocation or assignment is >> revoked and returned to ARIN. >> >> 4.4.3.5. The requesting organization must agree to withdraw any other >> BGP routes it announces from the BGP table within 6 months of >> receiving an allocation or assignment under section 4.4. If the >> organization continues to receive IP addresses from its ISPs, those IP >> addresses will be single-homed within the ISP's larger aggregate >> announcement. >> >> 4.4.3.6. If the requesting organization fails to announce the >> allocation or assignment received under section 4.4 to the Internet >> using its AS number for at least 4 months total within a service year, >> the allocation or assignment is revoked and returned to ARIN. >> >> 4.4.3.7. If the requesting organization already holds IPv4 addresses >> directly from ARIN, from any other RIR or legacy addresses, the >> organization must agree to renumber out of those addresses and >> surrender them to the appropriate RIR within 6 months of receiving an >> allocation or assignment under section 4.4. >> >> 4.4.3.8. The requesting organization agrees to return the allocation >> or assignment received under section 4.4 to ARIN within 6 months of >> receiving another allocation or assignment from any RIR. >> >> 4.4.3.9. For allocations of /23 and larger, the requesting >> organization shall meet the utilization rate criteria described in >> section 4.2 for ISPs and section 4.3 for end users. As /24 is the >> smallest address block known to be generally routable on the Internet, >> no utilization criteria will be applied to requests for a /24. >> >> >> 8. Rationale >> >> The reason behind a /20 minimum assignment for single-homed orgs is >> fairly straightforward: an ARIN allocation adds a route to the BGP >> table which wouldn't otherwise be needed. Routes are expensive and the >> cost falls into overhead since it isn't recoverable directly from the >> org announcing the route. And we're not really certain how many routes >> we can handle before the network falls over. So, we restrict the >> availability of non-aggregable IP addresses to just very large >> organizations. For smaller orgs, renumbering sucks but at least it >> only costs the renumbering org, not everyone else. >> >> The reason behind nothing smaller than a /24 is also straightforward: >> many if not most ISPs filter out BGP announcements smaller than /24. >> There is tremendous inertia behind /24 as the minimum >> backbone-routable quantity going back to the pre-CIDR days of class-C >> addresses. So, an ARIN allocation smaller than /24 would generally be >> wasted addresses, unusable on the Internet. >> >> But why peg multihomed orgs at /22 instead of /24? Multivendor >> multihomed orgs have to announce a route anyway, regardless of whether >> the addresses are from an ISP or directly from ARIN. Their routes are >> not aggregable, even if assigned from ISP space. That's the way the >> technology works and no new tech in the pipeline is likely to change >> it. >> >> With load balanced server clusters and NAT you can pack a heck of a >> lot of punch into a multihomed /24 if you want to. And as a community >> it's to our benefit to want registrants to pack the maximum punch into >> their address space: IPv4 addresses are becoming scarce. So why >> restrict ARIN assignments to folks who can write papers which justify >> a /22? >> >> FAQ >> >> Q. Why not just use ISP addresses if you're too small? >> >> A1. ISPs have conflicting requirements placed on their use of IP >> addresses. They want, for example, to prevent address spoofing at >> their borders by not allowing traffic from their addresses to enter >> their network from another ISP. These goals conflict with multivendor >> multihoming and generally make a mess when a customer wants to >> multihome. >> >> A2. Renumbering is expensive and painful. We should require it only >> when it serves a reasonable public policy goal such as reducing the >> consumption of BGP routing slots. >> >> A3. We've seen common counterproductive situations where multihomed >> end users make many discontiguous /24 announcements until they >> eventually seek ARIN address space. >> >> Q. But aren't your routes aggregable with your ISP's routes if you use >> your ISP's address space? >> >> A. No. For routes to be aggregable, two things must be true: >> >> 1. The routes must be contiguous, sharing a common network/netmask. >> 2. The routes must share an identical network topology. >> >> In the mutlivendor multihomed case addressed by this proposal, the >> routes almost never share an identical network topology. As a result >> the routes can not be aggregated even if cut from the ISP's address >> space. Single-homed networks are excluded from this proposal precisely >> because they always share a network topology with the ISP. >> >> Q. Can't other organizations filter routes at the RIR minimums and >> user the ISP's covering route to reach you? >> >> A. Maybe. With a bunch of ifs. You might not be connected to the ISP >> who has the covering route, and what if he doesn't have the more >> specific route to you? >> >> The answer is more decisive on a practical level: The author was >> unable to identify any ISPs who presently both filters on RIR minimums >> and chooses not to carry a default route to an upstream ISP that >> doesn't filter. Hence there is no apparent route filtering value to >> the RIR minimums. >> >> Q. What's so messy about multihoming with a cutout from an ISP's >> allocation? >> >> A. Many things. Here are some of them: >> >> * As an ISP I want to drop packets from the Internet that purport to >> be from my addresses (spoofed packets). I can't do that with packets >> from a multihomed network: in the normal course of failure recovery or >> traffic engineering, the multihomed user may originate packets to >> hosts on my network using the IP addresses I assigned him, but via his >> other ISPs. These packets will arrive at my Internet interfaces and if >> I drop them as spoofed packets, I've broken my customer's >> connectivity. >> >> * As an ISP I want to reject false route announcements entering my >> system which purport to serve my addresses. And I want my pager to go >> off and let me know someone is trying to hijack my address space. My >> multihomed customer will, in some circumstances, want me to route all >> packets to him via his other ISP. That means I have to accept his >> route announcement from other ISPs. To do this, I have to write some >> tricky filtering rules that accept his routes right smack in the >> middle of the address space where I generally want to reject routes. >> >> * As an ISP, I want to aggregate my contiguous address space into a >> single route announcement. It's part of being a good citizen: don't >> waste the TCAM slots in everybody else's router. But I have to >> carefully exclude my multihomed customer's routes from that >> aggregation. Packets follow the more specific route. If he announces >> his more specific route to his other ISP but I roll his route up into >> my less specific route when I announce it then all his packets will go >> to his other ISP instead of to me and I won't get paid. >> >> * Lots of folks disaggregate their route announcements for the purpose >> of traffic engineering. Two or three hops away from their system, >> those TE routes are irrelevant. In theory I should be able to filter a >> lot of that out by discarding the routes smaller than the RIR minimum >> allocation for that /8. That would save me money and make my routing >> updates work faster. But if I try it, I end up filtering mutlihomed >> customers so that I can only reach them via the ISP that assigned >> their addresses. At best that damages the effectiveness of my routing. >> At worst it cuts me off from sites my customers want to access when my >> competitors who just accept /24 everywhere don't have a problem. Oops. >> >> Q. Where do the announced addresses in 4.4.3.1 come from? >> >> A. Most likely from one of the ISPs as described in NRPM section >> 4.2.3.6. You go through the process of getting them assigned and >> announced to demonstrate that you're not a poser. Then you get >> addresses from ARIN under this proposal and return the 4.2.3.6 >> addresses to your ISP. >> >> Q. What does "distinct vendors" mean? >> >> A. It means two different ISPs like Verizon and Sprint. Two T1s with a >> single ISP can be accommodated without announcing a route into the >> Internet backbone, so such a connection does not qualify for addresses >> under this proposal. >> >> Q. $8000? What's that all about? >> >> A. The best available estimate of the systemic cost of carrying a >> route in the Internet backbone table is around $8000/year. See >> http://bill.herrin.us/network/bgpcost.html for the cost estimate. >> If you're going to play in the backbone, you should really be putting >> more money into the system than you're taking out. If you have two >> $600 T1's then you're spending nearly twice that anyway. This limits >> the folks who want to multihome their $50 DSL and cable modems. >> >> Q. How reliable is that estimate? Does it change? Shouldn't ARIN >> routinely update that estimate rather than codifying the specific >> number in the policy? >> >> A. In theory ARIN staff should set the number. In practice, >> professional cost analysts are expensive and hard data on things like >> router count is almost impossible to get anyway. Even if a more >> reliable cost analysis could be produced, we still wouldn't know what >> multiple of that cost was "fair" for the pay-in. 1x? 2x? 5x? Let's >> just pick a number that's our best guess at fair, and move forward >> with it. >> >> Besides, the $8k rule will probably turn out to be a non-operative >> part of the policy. Companies providing $50 DSL service are >> disinclined to set up BGP sessions with their customers anyway. I >> include it in the name of caution so that we're proof against a deluge >> of multihomed cable-modem users but I expect that with some experience >> under our belts we'll find that we can safely submit a follow-on >> policy proposal that removes the $8k requirement. >> >> Q. I have to renumber when exactly? >> >> A. If you have IP addresses under section 4.4, you get to announce >> that one allocation or assignment to the Internet via BGP. In fact, >> we'd really prefer that you only announce one single route, even if >> you get a /23 or larger. You don't get to collect two assignments and >> then ten discontiguous assignments and burn up the BGP table. Until >> you reach the minimums in sections 4.2 or 4.3, you renumber each time >> you grow large enough to justify the next bigger allocation or >> assignment. Yes, that's unfortunate and painful. But burning up the >> BGP table would be even more unfortunate. >> >> Practically speaking, you'll renumber zero or one times. Either you'll >> never renumber because the /24 was enough to do the job, or when you >> run out of space in your original assignment, you'll be big enough to >> find a way to meet the minimum size criteria in section 4.2 or 4.3 so >> that you don't have to renumber again. >> >> Q. But renumbering is expensive! What's the difference between having >> to renumber under this proposal and having to renumber when I change >> ISPs? >> >> A. You'll have to renumber less often if at all. The big deal is that >> you don't have to renumber merely because you changed vendors and you >> don't run into a sticky mess of filtering rules as ISPs try to keep >> control of their address space. >> >> Q. Doesn't this discriminate against some kinds of multihoming? >> >> A. In addition to multihoming with your own AS number, its possible to >> have two ISPs separately announce your addresses or announce with a >> private AS number that they strip from their peer announcements. This >> proposal is more than complex enough. For the sake of making >> verification simple, let's just say that tiny registrants will >> announce with their own AS number, period. >> >> Q. Does this proposal affect IPv6 allocations and assignments? >> >> A. It does not appear to impact ISP allocations whose criteria is >> spelled out in NRPM section 6.5.1.1. It does impact end user >> assignments under NRPM section 6.5.8.1. End users who qualify for >> addresses under this policy will also be qualified for an IPv6 /48. >> >> Q. Have there been previous policy proposals to extend allocations and >> assignments from ARIN to /24? >> >> A. Yes. See the discussions in March and April of 2007 for proposal >> 2007-6. http://lists.arin.net/pipermail/arin-ppml/ >> >> In proposal 2007-6, the /22 size for multihomers in section 4.3 was >> simply changed to /24. It met the following criticisms: >> >> * Could make it easier for spammers. This seems to reflect some >> concern at the time over whether ARIN's policies made things easy for >> spammers to hop IP addresses and was probably a red herring. Spammers >> aren't interested in registering with anybody. They want address space >> as anonymously as possible for as long as possible as cheaply as >> possible exerting as little effort as possible. All of these things >> make address space under this proposal unattractive to spammers. >> >> * Could create a land rush. This seems like an unreasonable concern >> for the instant proposal: anyone who can justify addresses under this >> proposal can justify the same addresses from their ISP already. So why >> hassle them with ISP addresses? >> >> * Could create a new swamp. The renumbering requirements in this >> proposal prevent that problem. >> >> * Unfair to ISPs since it only applies to end users. This proposal >> applies to both. >> >> * Staff worried that it could increase request workload. If it does, >> the fees could presumably be set accordingly. >> >> Proposal 2007-6 also tried to make the following point: Don't penalize >> the honest. An org that has ponied up the cash to be multihomed with >> multiple vendors can often restructure their network to require a /22 >> long enough to get one. Refusing ARIN assignments smaller than /22 >> encourages behavior which is contrary to ARIN's general public policy >> goal of conservation. We'll be better off as a community if the folks >> who are completely honest about their need get the same or better >> treatment than the ones who lie. >> >> >> Implementation notes: >> >> This proposal asks for verification of multihoming somewhat beyond >> what the rest of the NRPM requires. It does this in order to prevent a >> land rush of cheaters. Not that there's likely to be a land rush of >> cheaters (or if there is that they're likely to ask for less than a >> /22), but better safe than sorry. >> >> Verifying that there's a BGP announcement is trivial: go to any of the >> hundreds of looking glasses. For the four-month rule, staff may want >> to let it be practiced in the breach for now. That is, don't go out >> and look unless someone complains. Writing software that actively >> checks for it can be part of the address recovery strategy after >> depletion. >> >> Same deal with the route withdrawals: if slot consumption bugs the >> ISPs, let them write a script which trolls for cheaters and then >> complain. >> >> To verify multihoming, I would suggest asking the registrant to >> provide a letter of service from two ISPs in which they indicate that >> they're under contract to announce routes for AS XXX. >> >> To verify $8k, you might ask for a month's bills and check that 12 >> months worth adds up to $8k. >> >> There's a respectable chance that folks requesting a /23 or larger >> will continue to grow. It would be nice if ARIN staff made reasonable >> efforts to reserve adjacent space for a year or so they may be able to >> get the next larger size without having to renumber. With the scarcity >> of IPv4 addresses this won't always be possible, but it would be good >> to do as a "best efforts" kind of thing. . >> >> >> 9. Timetable for implementation: immediate >> >> >> > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List (ARIN-PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-ppml > Please contact info at arin.net if you experience any issues. > From info at arin.net Tue Aug 4 11:21:57 2009 From: info at arin.net (Member Services) Date: Tue, 04 Aug 2009 11:21:57 -0400 Subject: [arin-announce] Volunteers Needed by 7 August to Select Meeting Fellows Message-ID: <4A785215.10308@arin.net> This is a reminder that ARIN has issued a call for General Members in good standing to serve on the ARIN Meetings Fellowship Program Selection Committee. To qualify, you must have attended at least one ARIN Public Policy and Member's Meeting in the past three years. General Member in good standing is defined at: https://www.arin.net/participate/membership/member.html The fellowship program provides financial support for one individual from each of the three sectors within ARIN's service area (Canada, the Caribbean and North Atlantic Islands, and the United States and Outlying Areas)to attend each Public Policy and Members Meeting. To learn more about ARIN XXIV in Dearborn and the fellowship program go to: https://www.arin.net/participate/meetings/ARIN-XXIV/index.html The Selection Committee, comprised of one member of the Board of Trustees (Chair), one member of the Advisory Council, and two General Members in good standing is charged with reviewing all eligible applications and selecting one qualified individual per ARIN region sector to attend each ARIN Public Policy and Members meeting. Committee members will be subscribed to an e-mail list where information will be exchanged and discussed. They must also attend all conference calls held during the decision making process. Working with the committee, the Chair will initiate mail list discussions and schedule teleconference calls as needed. There will be approximately two to three weeks of application review, e-mail exchanges, and conference calls amongst committee members during early September in order to select Fellows for the October meeting. Learn more about the Selection Committee by visiting: https://www.arin.net/participate/meetings/fellowship.html#process Become more involved with ARIN and volunteer for the Selection Committee by sending an e-mail with your name, organization and org id, contact info, and last ARIN meeting attended to info at arin.net by 7 August 2009. Two eligible members will be randomly selected to serve on the committee. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Aug 4 16:05:45 2009 From: info at arin.net (Member Services) Date: Tue, 04 Aug 2009 16:05:45 -0400 Subject: [arin-announce] Apply Now for ARIN Meetings Fellowship to Attend ARIN XXIV Message-ID: <4A789499.6000205@arin.net> ARIN is pleased to offer the Meetings Fellowship Program in an effort to broaden educational outreach and bring new ideas into the public policy discussions. We are issuing a call for Fellows to attend ARIN XXIV in Dearborn this October. If you are interested in applying for the program, you have until 28 August to submit an application. The application, submission instructions, and a detailed description of the program can be found at: https://www.arin.net/participate/meetings/fellowship.html The program provides financial support for one individual from each of the three sectors within ARIN's service area (Canada, the Caribbean and North Atlantic Islands, and the United States and Outlying Areas) to attend each Public Policy and Members Meeting. Members of the ARIN Advisory Council will be invited to serve as Mentors for the ARIN Meeting Fellows to advise them and help provide a smooth transition into the ARIN community. Individuals selected for the fellowship will receive the following benefits: * Free meeting registration https://www.arin.net/participate/meetings/ARIN-XXIV/index.html * Round-trip economy class airfare to the meeting, booked directly by ARIN * Hotel accommodations at the venue hotel, booked directly by ARIN * A stipend to cover meals and incidental travel expenses. Please contact info at arin.net if you have any questions concerning the program and the application process. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Aug 5 10:31:39 2009 From: info at arin.net (Member Services) Date: Wed, 05 Aug 2009 10:31:39 -0400 Subject: [arin-announce] Call for Nominations: ARIN Board, ARIN AC, and NRO NC Message-ID: <4A7997CB.2040506@arin.net> ARIN is currently seeking nominations for the following positions as originally announced on 27 July: * Three (3) seats on the ARIN Board of Trustees * Five (5) seats on the ARIN Advisory Council * One (1) seat on the Number Resource Organization (NRO) Number Council Board of Trustees and Advisory Council: You must be a Trustee or ARIN General Member in good standing to make nominations for the Board of Trustees and Advisory Council. However, those nominated do not need to be ARIN members. Self-nominations are permitted. A petition process is available to nonmembers seeking to nominate themselves for the Board of Trustees. NRO Number Council: Any individual residing within the ARIN service region may be nominated, with the exception of Regional Internet Registry staff members. Self-nominations are permitted. Nominators are not required to be ARIN General Members in good standing. All nominees are subject to the Nomination and Appointment Conflict of Interest List at: https://www.arin.net/participate/elections/conflicts.html Please take the time to nominate qualified candidates for these positions. The call for nominations closes at 17:00 ET on Monday, 31 August 2009. The nomination form is available through ARIN?s online Election Headquarters at: https://www.arin.net/app/election/ Now is also a good time for ARIN member organizations to check with Member Services to ensure they have a designated member representative (DMR) eligible to vote in the upcoming election. Direct any questions concerning this process to Member Services at info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Aug 6 13:12:46 2009 From: info at arin.net (Member Services) Date: Thu, 06 Aug 2009 13:12:46 -0400 Subject: [arin-announce] Remote Participation Features at ARIN XXIV Message-ID: <4A7B0F0E.4030700@arin.net> If you are unable to attend ARIN XXIV in person, please join us online by registering as a remote participant and take advantage of this opportunity to contribute to policy discussions and other meeting sessions. Follow the ?Register for ARIN XXIV? link at https://www.arin.net/participate/meetings/ARIN-XXIV/ and choose "ARIN XXIV Remote Participant" from the drop-down menu. Before you register as a remote meeting participant, make sure you have a Jabber Identifier (JID). You will need to provide your JID on the remote participation registration form in order to log in to the meeting chat rooms. To learn more about the remote participation services, including specific details on how to get started and schedules, please go to: https://www.arin.net/participate/meetings/ARIN-XXIV/remote.html Before the meeting, be sure to download the meeting materials, which will be available online. Use the meeting program, discussion guide, and other meeting support documents to help you follow along. Registration is not required to view the webcast or live transcript, but as a registered remote participant, you will be able to submit comments for moderated presentation during normal question and answer periods, and ?raise your hand? to be counted during polling. All remote participants are subject to the Remote Participation Acceptable Use Policy (AUP). Complete information about remote participation is available at the link above. Whether you plan to be on-site or taking part remotely, we look forward to and appreciate your participation at ARIN XXIV. Please contact Member Services at info at arin.net if you have any questions. Regards, Member Services Department American Registry for Internet Numbers (ARIN) From info at arin.net Fri Aug 7 14:30:52 2009 From: info at arin.net (Member Services) Date: Fri, 07 Aug 2009 14:30:52 -0400 Subject: [arin-announce] ARIN Research Opportunity Message-ID: <4A7C72DC.80907@arin.net> The American Registry for Internet Numbers? Board of Trustees recently ratified changes to ARIN?s Transfer Policy, Number Resource Policy Manual Section 8 - Transfers https://www.arin.net/policy/nrpm.html#eight. Section 8.3 specifically allows organizations to release Internet Number resources to another organization subject to guidelines as stated in the policy. This policy change combined with the continued depletion of Regional Internet Registry (RIR) available IPv4 address space may create a market condition in which bidders, organizations that need IPv4 address space, competitively make offers, for available IPv4 address space, to sellers. Under these conditions, it is assumed that sellers may seek the highest dollar value for their available address space. Understanding these potential market conditions, ARIN is requesting research analysis and a report on potential market pricing for IPv4 address space in increments commonly allocated by the RIRs (/22, /21, /20?/16..). The research analysis and report should focus on the period near and through IPv4 exhaustion when competitive conditions may result in maximum prices that bidders are willing to offer for IPv4 address space. Research should consider and report all conditions that may influence the market conditions and impact on pricing throughout the period in which the RIRs cannot meet demand well beyond exhaustion, until market equilibrium is achieved. ARIN is seeking innovative thought from an established economics and market researcher with a proven record of analyzing and predicting future market characteristics, specifically in market pricing. Ideally, the researcher would have experience in establishing new markets as well. ARIN requires a new research effort, not simply a review of similar studies that may have been done and/or are currently underway. ARIN may request the researcher to update the pricing analysis as conditions change over time. The ARIN Board of Trustees will use the results of this research to determine changes in strategic direction, operating plan objectives, and may share with the Internet community and other interested parties for policy evaluation and consideration. Please submit your proposal for the research referenced above to FundResearch at arin.net following ARIN?s Policy Guidelines for Research Projects which are located at https://www.arin.net/about_us/corp_docs/research.html Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) From info at arin.net Mon Aug 17 09:32:10 2009 From: info at arin.net (Member Services) Date: Mon, 17 Aug 2009 09:32:10 -0400 Subject: [arin-announce] Apply for an ARIN XXIV Meeting Fellowship Message-ID: <4A895BDA.1010501@arin.net> ARIN is pleased to offer the Meetings Fellowship Program in an effort to broaden educational outreach and bring new ideas into the public policy discussions. We are issuing a call for Fellows to attend ARIN XXIV in Dearborn this October. If you are interested in applying for the program, you have until 28 August to submit an application. The application, submission instructions, and a detailed description of the program can be found at: https://www.arin.net/participate/meetings/fellowship.html The program provides financial support for one individual from each of the three sectors within ARIN's service area (Canada, the Caribbean and North Atlantic Islands, and the United States and Outlying Areas) to attend each Public Policy and Members Meeting. Members of the ARIN Advisory Council will be invited to serve as Mentors for the ARIN Meeting Fellows to advise them and help provide a smooth transition into the ARIN community. Individuals selected for the fellowship will receive the following benefits: * Free meeting registration https://www.arin.net/participate/meetings/ARIN-XXIV/index.html * Round-trip economy class airfare to the meeting, booked directly by ARIN * Hotel accommodations at the venue hotel, booked directly by ARIN * A stipend to cover meals and incidental travel expenses. Please contact info at arin.net if you have any questions concerning the program and the application process. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Aug 17 11:04:11 2009 From: info at arin.net (Member Services) Date: Mon, 17 Aug 2009 11:04:11 -0400 Subject: [arin-announce] =?windows-1252?q?Consultation_Closed=3A_ARIN=92s_?= =?windows-1252?q?Bulk_WHOIS_AUP?= Message-ID: <4A89716B.4050003@arin.net> ARIN thanks the community for its input regarding updating the Bulk WHOIS AUP to include the following: "Distribution of derivative data is only permitted with express written permission of ARIN and under the same terms as this AUP." Based on the feedback received, by 15 September ARIN plans to include the expanded AUP on the request form for Bulk WHOIS recipients. Those who have a current signed agreement are welcome to sign the new form to take advantage of the changes to the AUP. The archives of this discussion are available at: http://lists.arin.net/pipermail/arin-consult/ Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Aug 19 12:04:27 2009 From: info at arin.net (Member Services) Date: Wed, 19 Aug 2009 12:04:27 -0400 Subject: [arin-announce] Call for Nominations: ARIN Board, ARIN AC, and NRO NC Message-ID: <4A8C228B.8090504@arin.net> ARIN is currently seeking nominations for the following positions as originally announced on 27 July: * Three (3) seats on the ARIN Board of Trustees * Five (5) seats on the ARIN Advisory Council * One (1) seat on the Number Resource Organization (NRO) Number Council Board of Trustees and Advisory Council: You must be a Trustee or ARIN General Member in good standing to make nominations for the Board of Trustees and Advisory Council. However, those nominated do not need to be ARIN members. Self-nominations are permitted. A petition process is available to nonmembers seeking to nominate themselves for the Board of Trustees. NRO Number Council: Any individual residing within the ARIN service region may be nominated, with the exception of Regional Internet Registry staff members. Self-nominations are permitted. Nominators are not required to be ARIN General Members in good standing. All nominees are subject to the Nomination and Appointment Conflict of Interest List at: https://www.arin.net/participate/elections/conflicts.html Please take the time to nominate qualified candidates for these positions. The call for nominations closes at 17:00 ET on Monday, 31 August 2009. The nomination form is available through ARIN?s online Election Headquarters at: https://www.arin.net/app/election/ Now is also a good time for ARIN member organizations to check with Member Services to ensure they have a designated member representative (DMR) eligible to vote in the upcoming election. Direct any questions concerning this process to Member Services at info at arin.net. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Aug 21 10:24:54 2009 From: info at arin.net (Member Services) Date: Fri, 21 Aug 2009 10:24:54 -0400 Subject: [arin-announce] Maintenance Work Scheduled for Sunday, 23 August 2009 Message-ID: <4A8EAE36.2070204@arin.net> On Sunday, 23 August 2009, ARIN will be conducting maintenance on back-end systems. The work will take place from 10AM until approximately 1PM EDT. ARIN will experience interruption of two external services while this maintenance is performed. For the duration, any mail sent to Registration Services (hostmaster at arin.net and reassign at arin.net) will be queued, and you will not be able to use your ARIN web account to submit transactions. Once the systems are back online, queued mail will be processed, and you will regain use of your ARIN Web account. All other publicly available services (WHOIS, IRR, etc.) will not be affected by this outage. Thank you for your patience and cooperation, Mark Kosters Chief Technical Officer American Registry for Internet Numbers (ARIN) From jcurran at arin.net Mon Aug 24 17:46:18 2009 From: jcurran at arin.net (John Curran) Date: Tue, 25 Aug 2009 05:46:18 +0800 Subject: [arin-announce] Still time to nominate for the ARIN Board, ARIN AC, and NRO NC positions References: <4A8C228B.8090504@arin.net> Message-ID: As a reminder, there are only four days remaining for nominations for positions on the ARIN Board, ARIN AC, and NRO NC. I encourage members to consider those in the community who would be good in these roles and to submit your nominations as soon as possible per the attached instructions. Thanks! /John John Curran President and CEO ARIN Begin forwarded message: > From: Member Services > Date: August 20, 2009 12:04:27 AM GMT+08:00 > To: arin-announce at arin.net > Subject: [arin-announce] Call for Nominations: ARIN Board, ARIN AC, > and NRO NC > > ARIN is currently seeking nominations for the following positions as > originally announced on 27 July: > > * Three (3) seats on the ARIN Board of Trustees > * Five (5) seats on the ARIN Advisory Council > * One (1) seat on the Number Resource Organization (NRO) Number > Council > > Board of Trustees and Advisory Council: > You must be a Trustee or ARIN General Member in good standing to make > nominations for the Board of Trustees and Advisory Council. However, > those nominated do not need to be ARIN members. Self-nominations are > permitted. A petition process is available to nonmembers seeking to > nominate themselves for the Board of Trustees. > > NRO Number Council: > Any individual residing within the ARIN service region may be > nominated, > with the exception of Regional Internet Registry staff members. > Self-nominations are permitted. Nominators are not required to be ARIN > General Members in good standing. > > All nominees are subject to the Nomination and Appointment Conflict of > Interest List at: > > https://www.arin.net/participate/elections/conflicts.html > > Please take the time to nominate qualified candidates for these > positions. The call for nominations closes at 17:00 ET on Monday, 31 > August 2009. > > The nomination form is available through ARIN?s online Election > Headquarters at: > > https://www.arin.net/app/election/ > > Now is also a good time for ARIN member organizations to check with > Member Services to ensure they have a designated member representative > (DMR) eligible to vote in the upcoming election. Direct any questions > concerning this process to Member Services at info at arin.net. > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > > _______________________________________________ > ARIN-Announce > You are receiving this message because you are subscribed to > the ARIN Announce Mailing List (ARIN-announce at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-announce > Please contact info at arin.net if you experience any issues. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Aug 25 16:33:15 2009 From: info at arin.net (Member Services) Date: Tue, 25 Aug 2009 16:33:15 -0400 Subject: [arin-announce] Last Call for ARIN Meetings Fellowship Applicants Message-ID: <4A944A8B.5070305@arin.net> ARIN is pleased to offer the Meetings Fellowship Program in an effort to broaden educational outreach and bring new ideas into the public policy discussions. We are issuing a call for Fellows to attend ARIN XXIV in Dearborn this October. If you are interested in applying for the program, you have until this Friday 28 August to submit an application. The application, submission instructions, and a detailed description of the program can be found at: https://www.arin.net/participate/meetings/fellowship.html The program provides financial support for one individual from each of the three sectors within ARIN's service area (Canada, the Caribbean and North Atlantic Islands, and the United States and Outlying Areas) to attend each Public Policy and Members Meeting. Members of the ARIN Advisory Council will be invited to serve as Mentors for the ARIN Meeting Fellows to advise them and help provide a smooth transition into the ARIN community. Individuals selected for the fellowship will receive the following benefits: * Free meeting registration https://www.arin.net/participate/meetings/ARIN-XXIV/index.html * Round-trip economy class airfare to the meeting, booked directly by ARIN * Hotel accommodations at the venue hotel, booked directly by ARIN * A stipend to cover meals and incidental travel expenses. Please contact info at arin.net if you have any questions concerning the program and the application process. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Aug 31 08:54:23 2009 From: info at arin.net (Member Services) Date: Mon, 31 Aug 2009 08:54:23 -0400 Subject: [arin-announce] Last Call for ARIN Board, AC, and NRO NC Nominations Message-ID: <4A9BC7FF.8030905@arin.net> The candidate nomination period for the upcoming ARIN Board of Trustees (3 open seats) and Advisory Council (5 open seats) elections ends today 5:00 PM EDT, 31 August. This is also your last chance to nominate candidates for the open Number Resource Organization (NRO) Number Council seat. These representatives will play key roles at ARIN and in the Internet community in upcoming years, so don?t let this opportunity pass you by. Nomination forms and election information are available through ARIN Election Headquarters at: https://www.arin.net/app/election/ All nominees are subject to the Nomination and Appointment Conflict of Interest List at: https://www.arin.net/participate/elections/conflicts.html The initial slate of candidates will be posted online on 15 September 2009. Online voting for the Board and Advisory Council will begin during the ARIN XXIV Public Policy and Members Meetings on 21 October. Online voting for the NRO NC representative will be available 14-21 October 2009. Please contact Member Services at info at arin.net if you have any questions. Regards, Member Services American Registry for Internet Numbers (ARIN)