From info at arin.net Thu Jan 3 12:01:08 2008 From: info at arin.net (Member Services) Date: Thu, 03 Jan 2008 12:01:08 -0500 Subject: Board adopts two policy proposals Message-ID: <477D14D4.3060808@arin.net> On 11 December 2007 the ARIN Board of Trustees adopted two policy proposals: 2007-19: IANA Policy for Allocation of ASN Blocks to RIRs. This is a global policy proposal which will be implemented after ratification by the ICANN Board of Directors. 2007-25: IPv6 Policy Housekeeping. This policy will be implemented no later than 15 February 2008. The ARIN Board of Trustees remanded two proposals to the Advisory Council (AC): 2007-21: PIv6 for legacy holders with RSA and efficient use, to facilitate further discussion regarding the policy text. 2007-22: Expand timeframe of Additional Requests, for further consideration and evaluation with respect to the public policy process. Policy proposal texts are available at the Policy Proposal Archive which can be found at: http://www.arin.net/policy/proposal_archive.html Regards, Member Services Department American Registry for Internet Numbers (ARIN) From info at arin.net Tue Jan 8 13:07:40 2008 From: info at arin.net (Member Services) Date: Tue, 08 Jan 2008 13:07:40 -0500 Subject: Deadline for Policy Proposals - 7 February 2008 Message-ID: <4783BBEC.1090102@arin.net> The ARIN XXI Public Policy Meeting will take place 7-8 April 2008 in Denver. New policy proposals must be submitted by 23:59 EST, 7 February 2008, in order to be considered by the ARIN Advisory Council for possible inclusion on the ARIN XXI agenda. The ARIN Internet Resource Policy Evaluation Process requires that proposed policies must be submitted at least 60 days prior to the meeting. Those who wish to propose new ARIN number resource policies or modifications to existing policies must submit a Policy Proposal Template. Send the template via e-mail to policy at arin.net. The Policy Proposal Template can be found at: http://www.arin.net/policy/irpep_template.html The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jan 18 15:20:07 2008 From: info at arin.net (Member Services) Date: Fri, 18 Jan 2008 15:20:07 -0500 Subject: Policy Proposal: SWIP support for smaller than /29 assignments Message-ID: <479109F7.3000308@arin.net> ARIN received the following policy proposal. In accordance with the ARIN Internet Resource Policy Evaluation Process, the proposal is being posted to the ARIN Public Policy Mailing List (PPML) and being placed on ARIN's website. The ARIN Advisory Council (AC) will review this proposal at their next regularly scheduled meeting. The AC may decide to: 1. Accept the proposal as written. If the AC accepts the proposal, it will be posted as a formal policy proposal to PPML and it will be presented at a Public Policy Meeting. 2. Postpone their decision regarding the proposal until the next regularly scheduled AC meeting in order to work with the author. The AC will work with the author to clarify, combine or divide the proposal. At their following meeting the AC will accept or not accept the proposal. 3. Not accept the proposal. If the AC does not accept the proposal, the AC will explain their decision via the PPML. If a proposal is not accepted, then the author may elect to use the petition process to advance their proposal. If the author elects not to petition or the petition fails, then the proposal will be closed. The AC will assign shepherds in the near future. ARIN will provide the names of the shepherds to the community via the PPML. In the meantime, the AC invites everyone to comment on this 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 Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Mailing list subscription information can be found at: http://www.arin.net/mailing_lists/ Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal Name: SWIP support for smaller than /29 assignments Author: Joe Maimon Proposal Version: 1 Submission Date: Jan 16, 2008 Proposal type: modify Policy term: permanent Policy statement: 4.2.2.1.2.) " ISPs must provide reassignment information on the entire previously allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks. For blocks smaller than /29 and for internal space, ISPs should provide utilization data using the table format described in Section 4.2.3.7.5. " Replace with " ISPs must provide reassignment information on the entire previously allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks. For blocks smaller than /29 and for internal space, ISPs should provide utilization data either via SWIP or RWHOIS server or by using the table format described in Section 4.2.3.7.5. " 4.2.2.2.1.) " Utilization for blocks smaller than /29 can be documented using the format described in Section 4.2.3.7.5. " Replace with " Utilization for blocks smaller than /29 can be documented via SWIP or RWHOIS server or by using the format described in Section 4.2.3.7.5. " 4.2.3.7.2.) " For blocks smaller than /29 and for internal space, ISPs should provide utilization data using the format described in Section 4.2.3.7.5. " Replace with " For blocks smaller than /29 and for internal space, ISPs should provide utilization data via SWIP or RWHOIS server or by using the format described in Section 4.2.3.7.5. " 4.2.3.7.5.) Accounting for additional utilization " The following format should be used to provide the required information for utilization of blocks smaller than /29 and for describing internal networks: " Replace with " The following format should be used to provide the required information for utilization of blocks smaller than /29 and for describing internal networks when either SWIP or RWHOIS server is not used: " Rationale: With increasing frequency of smaller than /29 assignements to customers, the ability for ISP's to utilize SWIP or RWHOIS as a single comprehensive source of their utilization data should be supported. To implement this policy change, ARIN SWIP would need to no longer reject SWIP templates smaller then /29. Timetable for implementation: Immediate From info at arin.net Tue Jan 22 13:42:45 2008 From: info at arin.net (Member Services) Date: Tue, 22 Jan 2008 13:42:45 -0500 Subject: Policy Proposal 2007-24: IPv6 Assignment Guidelines - Withdrawn by author Message-ID: <47963925.4080705@arin.net> Policy Proposal 2007-24 IPv6 Assignment Guidelines The author withdrew their proposal. The proposal is closed. The policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2007_24.html The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Proposal 2007-24 IPv6 Assignment Guidelines Author: Leo Bicknell and Ed Lewis Proposal type: new Policy term: permanent Policy statement: Delete the text in 6.5.4.2 and Replace the text in section 6.5.4.1 with the following text: Assignments by LIRs /48 or smaller will not be reviewed by ARIN. Assignments greater than /48 will be reviewed to see if the additional space is warranted according to the 0.94 HD ratio policy. If the space is not warranted, ARIN will consider the excess space to be available for a different assignment, lowering the overall utilization score of the LIR. Rationale: The existing section 6.5.4.1 does not provide clear guidance on how ARIN should treat prefixes allocated to a site should an ISP come back for additional space in the future. This makes it difficult for LIR's to know if they are allocating in accordance with the rules under which they will be judged in the future. The existing section also provides no guidence on what the LIR or ARIN should do in the case a larger prefix is necessary. Timetable for implementation: immediate From info at arin.net Wed Jan 23 12:31:23 2008 From: info at arin.net (Member Services) Date: Wed, 23 Jan 2008 12:31:23 -0500 Subject: Policy Proposal: SWIP support for smaller than /29 assignments In-Reply-To: <479109F7.3000308@arin.net> References: <479109F7.3000308@arin.net> Message-ID: <479779EB.6030708@arin.net> > The AC will assign shepherds in the near future. ARIN will provide the > names of the shepherds to the community via the PPML. The shepherds from the ARIN Advisory Council for this proposal are Owen DeLong and Bill Darte. Regards, Member Services American Registry for Internet Numbers (ARIN) Member Services wrote: > ARIN received the following policy proposal. In accordance with the ARIN > Internet Resource Policy Evaluation Process, the proposal is being > posted to the ARIN Public Policy Mailing List (PPML) and being placed on > ARIN's website. > > The ARIN Advisory Council (AC) will review this proposal at their next > regularly scheduled meeting. The AC may decide to: > > 1. Accept the proposal as written. If the AC accepts the proposal, > it will be posted as a formal policy proposal to PPML and it will be > presented at a Public Policy Meeting. > > 2. Postpone their decision regarding the proposal until the next > regularly scheduled AC meeting in order to work with the author. The AC > will work with the author to clarify, combine or divide the proposal. At > their following meeting the AC will accept or not accept the proposal. > > 3. Not accept the proposal. If the AC does not accept the proposal, > the AC will explain their decision via the PPML. If a proposal is not > accepted, then the author may elect to use the petition process to > advance their proposal. If the author elects not to petition or the > petition fails, then the proposal will be closed. > > The AC will assign shepherds in the near future. ARIN will provide the > names of the shepherds to the community via the PPML. > > In the meantime, the AC invites everyone to comment on this 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 Internet Resource Policy Evaluation Process can be found at: > http://www.arin.net/policy/irpep.html > > Mailing list subscription information can be found at: > http://www.arin.net/mailing_lists/ > > Regards, > > Member Services > American Registry for Internet Numbers (ARIN) > > > ## * ## > > > Policy Proposal Name: SWIP support for smaller than /29 assignments > > Author: Joe Maimon > > Proposal Version: 1 > > Submission Date: Jan 16, 2008 > > Proposal type: modify > > Policy term: permanent > > Policy statement: > > 4.2.2.1.2.) > > " > ISPs must provide reassignment information on the entire previously > allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks. > For blocks smaller > > than /29 and for internal space, ISPs should provide utilization data > using the table format described in Section 4.2.3.7.5. > " > > Replace with > > " > ISPs must provide reassignment information on the entire previously > allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks. > For blocks smaller > > than /29 and for internal space, ISPs should provide utilization data > either via SWIP or RWHOIS server or by using the table format described > in Section 4.2.3.7.5. > " > > 4.2.2.2.1.) > > " > Utilization for blocks smaller than /29 can be documented using the > format described in Section 4.2.3.7.5. > " > > Replace with > > " > Utilization for blocks smaller than /29 can be documented via SWIP or > RWHOIS server or by using the format described in Section 4.2.3.7.5. > " > > 4.2.3.7.2.) > > " > For blocks smaller than /29 and for internal space, ISPs should provide > utilization data using the format described in Section 4.2.3.7.5. > " > > Replace with > > " > For blocks smaller than /29 and for internal space, ISPs should provide > utilization data via SWIP or RWHOIS server or by using the format > described in Section 4.2.3.7.5. > " > > 4.2.3.7.5.) Accounting for additional utilization > > " > The following format should be used to provide the required information > for utilization of blocks smaller than /29 and for describing internal > networks: > " > > Replace with > > " > The following format should be used to provide the required information > for utilization of blocks smaller than /29 and for describing internal > networks when either SWIP or RWHOIS server is not used: > " > > Rationale: > > With increasing frequency of smaller than /29 assignements to customers, > the ability for ISP's to utilize SWIP or RWHOIS as a single > comprehensive source of their utilization data should be supported. To > implement this policy change, ARIN SWIP would need to no longer reject > SWIP templates smaller then /29. > > Timetable for implementation: Immediate > >