From info at arin.net Wed Sep 5 08:44:04 2007 From: info at arin.net (Member Services) Date: Wed, 05 Sep 2007 08:44:04 -0400 Subject: Policy Proposal 2007-24: IPv6 Assignment Guidelines Message-ID: <46DEA494.9040001@arin.net> On 30 August 2007, the ARIN Advisory Council (AC) concluded their initial review of "IPv6 Assignment Guidelines" and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-24: IPv6 Assignment Guidelines. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_24.html All persons in the community are encouraged to discuss Policy Proposal 2007-24 prior to it being presented at the ARIN Public Policy Meeting in Albuquerque, New Mexico, 17-18 October 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.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 Sep 5 08:45:06 2007 From: info at arin.net (Member Services) Date: Wed, 05 Sep 2007 08:45:06 -0400 Subject: Policy Proposal 2007-25: IPv6 Policy Housekeeping Message-ID: <46DEA4D2.3070409@arin.net> On 30 August 2007, the ARIN Advisory Council (AC) concluded their initial review of "IPv6 Policy Housekeeping" and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-25: IPv6 Policy Housekeeping. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_25.html All persons in the community are encouraged to discuss Policy Proposal 2007-25 prior to it being presented at the ARIN Public Policy Meeting in Albuquerque, New Mexico, 17-18 October 2007. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-25 IPv6 Policy Housekeeping Author: Leo Bicknell Proposal type: modify Policy term: permanent Policy statement: Change I: In section 6.5.1.1.d, replace the existing statement with the new statement: "be an existing, known ISP in the ARIN region or have a plan for making at least 200 end-site assignments to other organizations within 5 years." Change J: Remove section 6.5.3 entirely. Update all subsequent sections to have new section numbers (6.5.[n-1]). Replace part of the text as (new) section 6.5.4.4: "All /56 and larger assignments to end sites are required to be registered either by the LIR or its subordinate ISPs in such a way that the RIR/NIR can properly evaluate the HD-Ratio when a subsequent allocation becomes necessary." Change K: Section 6.5.8.2, add the following sentence to the end of the first paragraph: "An HD-Ratio of .94 must be met for all assignments larger than a /48." Add to the end of the second paragraph: "This reservation may be assigned to other organizations later, at ARIN's discretion." Change L: Section 6.5.8.3, add a sentence between the two existing sentences: "Justification will be determined based on the .94 HD-Ratio metric." Rationale: When the IPv6 policy was passed, it was considered to be an "interim" policy, and it was intended to be similar in all 5 RIR's. Since that time it has become clear the policy is no longer interim (and proposal 2007-4 was passed to change just that) and it has also been modified separately in the different RIR's. It was brought to the ARIN AC's attention that there were a number of problems with "Section 6" of the NRPM as a result of this legacy: * The policy contained a large number of items that were not policy. * The policy contained a few items that were self contradictory. * The added text was redundant in some cases with existing text. * The policy was overly vague in a few areas, leaving ARIN staff to have to make interpretations of what the policy intended. * Policy changes made since the initial IPv6 policy was adopted have not always updated all of the relevant sections due to the complexity of section 6. The intent of these changes is not to change any existing policy, but rather to remove all non-policy items, and update any ambiguous items with the way that ARIN staff is currently interprets the policy. Change I: Proposal 2005-8 amended section 6.5.4.1 to allow /56 and /64 allocations, but section 6.5.1.1.d was never updated to match the change. It is believed the intent of the policy, and ARIN staff's current interpretation of the policy match the updated text. Change J: The first part is not policy, and incorrectly states there is no policy as section 6.5.4 has the policy in it. Take the one useful part and make it part of the 6.5.4 criteria. Change K: No metric is currently listed to justify a larger initial assignment. It is believed ARIN staff is currently applying the HD-Ratio similar to the ISP policy, this puts that in writing. Make it clear that the reservation may not exist in perpetuity. Change L: No metric is given to justify additional assignments. It is believed that ARIN staff is currently applying the HD_Ratio similar to the ISP policy, this puts that in writing. Timetable for implementation: Immediate From info at arin.net Tue Sep 11 20:29:29 2007 From: info at arin.net (Member Services) Date: Tue, 11 Sep 2007 20:29:29 -0400 Subject: [ppml] Policy Proposal -- Eliminate Lame Server policy In-Reply-To: References: Message-ID: <46E732E9.5030108@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 a formal policy 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. 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) ## * ## Owen DeLong wrote: > Template: ARIN-POLICY-PROPOSAL-TEMPLATE-1.0 > > 1. Policy Proposal Name: Deprecate Lame Server Policy > 2. Author > a. name: Owen DeLong > b. email: owen at delong.com > c. telephone: 408-921-6984 > d. organization: JITTR Networks > > 3. Proposal Version: 1.0 > 4. Submission Date: 11 September, 2007 > 5. Proposal type: delete > new, modify, or delete. > 6. Policy term: permanent > temporary, permanent, or renewable. > 7. Policy statement: > Delete section 7 from the NRPM > > 8. Rationale: > Recent PPML discussion has called attention to the > fact that lame DNS delegations are more an operational > issue than one of policy. As such, the existing lame > delegation policy should be removed from the NRPM > to remove the resultant confusion. This is not meant > to prevent ARIN staff from taking reasonable action > WRT DNS operational issues related to resources issued > by ARIN, but, such action can be covered by staff > operational guidelines and is not within the scope > of Address Policy. > > 9. Timetable for implementation: > 1 June, 2008 > 10. Meeting presenter: > END OF TEMPLATE > _______________________________________________ > PPML > You are receiving this message because you are subscribed to the ARIN Public Policy > Mailing List (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Wed Sep 12 11:06:36 2007 From: info at arin.net (Member Services) Date: Wed, 12 Sep 2007 11:06:36 -0400 Subject: Policy Proposal: Modification to Reverse Mapping Policy In-Reply-To: References: Message-ID: <46E8007C.6010507@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 a formal policy 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. 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: Modification to Reverse Mapping Policy Author: John Von Essen Proposal Version: 1.0 Submission Date: September 11, 2007 Proposal type: modify Policy term: permanent Policy statement: I am proposing a modification to section 7 of the IPv4 policy such that a more precise definition and overview of lameness is described. Below is how I think section 7 should be re-written. START NEW Section 7. Reverse Mapping 7.1. Maintaining IN-ADDRs All ISPs receiving one or more distinct /16 CIDR blocks of IP addresses from ARIN will be responsible for maintaining all IN- ADDR.ARPA domain records for their respective customers. For blocks smaller than /16, and for the segment of larger blocks which start or end with a CIDR prefix longer than /16, ARIN can maintain IN-ADDRs through the use of the SWIP (Reallocate and Reassign) templates or the Netmod template for /24 and shorter prefixes. 7.2 Definitions 7.2.1 Lame Delegation A delegation is defined as being lame if all of the in-addr.arpa zones for a given name server of a specific network registration are lame. An in- addr.arpa zone is defined as lame when ARIN requests the SOA record from the name server registered in whois, but does not receive an answer. 7.2.2 Partially Lame Delegation A delegation is defined as being partially lame if at least one in- addr.arpa zone for a given name server of a specific network registration is lame. An in- addr.arpa zone is defined as lame when ARIN requests the SOA record from the name server registered in whois, but does not receive an answer. 7.3. Handling of Lame and Partially Lame Delegations in IN-ADDR.ARPA ARIN will actively identify lame and partially lame DNS name server (s) for reverse address delegations associated with address blocks allocated, assigned or administered by ARIN. Upon identification of a lame or partially lame delegation, ARIN shall attempt to contact the POC for that resource and resolve the issue. If, following due diligence, ARIN is unable to resolve the lame or partially lame delegation, ARIN will update the WHOIS database records resulting in the removal of lame or partially lame DNS servers. ARIN's actions in resolving lame and partially lame delegations is governed by the procedures set forth in (Lame-Ref). 7.4 References (Lame-Ref) "Lame Delegations In IN-ADDR.ARPA", http://www.arin.net/ reference/lame_delegations.html STOP NEW Section Rationale: Current policy only considers an Org's delegation being deemed lame if all of in-addr.arpa zones for a given name server of a specific network registration are lame. Lame is defined when ARIN tests an in-addr.arpa zone by requesting the SOA record from the name server registered in whois, but does not receive an answer. If deemed lame, ARIN has an appropriate procedure for contacting the Org and handling the issue as per "http://www.arin.net/ reference/lame_delegations.html". Unfortunately, the policy does not cover the situation of a so-called partially lame delegation. That is, some of the in-addr.arpa zones belonging to the network registration return a valid SOA upon testing, and some do not. Even if only one /24 in-addr.arpa reverse tests comes back as lame, it is my opinion that this still taints the reputation of entire network registration. IPs belonging to that lame in-addr.arpa zone will cause query timeouts to 3rd party dns resolvers, both public and private. These excessive timeouts in my opinion can harm the overall well-being of reverse dns functionality throughout the internet. The only way to prevent such harm is for ARIN to not delegate reverse authority to the so-called partially lame dns server as registered in whois. That is the purpose of this policy proposal, to consider partial lameness with the same prejudice as traditionally defined lameness. Org's who are partially lame should be contacted by ARIN and lame in-addr.arpa zones should be resolved as the procedures per "http://www.arin.net/reference/ lame_delegations.html" dictate. Timetable for implementation: June 1, 2008 From info at arin.net Thu Sep 13 11:05:41 2007 From: info at arin.net (Member Services) Date: Thu, 13 Sep 2007 11:05:41 -0400 Subject: ARIN Implements PGP for Template Transactions Message-ID: <46E951C5.1020405@arin.net> ARIN has implemented PGP (Pretty Good Privacy) as a method to secure template transactions sent to ARIN when managing Internet number resources. This is in response to a 14 June 2007 directive from the Board of Trustees (http://www.arin.net/announcements/archives/20070621.html). Cryptographic signing enables more secure communication between ARIN and its customers. In addition to PGP, ARIN offers X.509 certificates as a method of cryptographic authentication. A wide variety of mail and signing software exists; ARIN encourages its customers to examine their mail software for PGP and X.509 support. While there are a few known issues with some mail user agent (MUA) implementations of PGP and X.509 standards, ARIN will work with its customers to provide additional processing support when needed. ARIN will also continue to support Mail-From as an authentication method, though it is not as secure as digitally signed transactions. For more details on cryptographic authentication at ARIN, including information on using PGP and X.509 certificates with ARIN, please visit: http://www.arin.net/CA/. If you have any questions regarding PGP or X.509 certificates, please contact Registration Services at hostmaster at arin.net or +1.703.227.0660. Regards, Raymond A. Plzak President and CEO American Registry for Internet Numbers (ARIN) From info at arin.net Thu Sep 13 14:50:55 2007 From: info at arin.net (Member Services) Date: Thu, 13 Sep 2007 14:50:55 -0400 Subject: [ppml] Policy Proposal -- Eliminate Lame Server policy In-Reply-To: <46E732E9.5030108@arin.net> References: <46E732E9.5030108@arin.net> Message-ID: <46E9868F.7030005@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 Cathy Aronson and Robert Seastrom. 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 a formal policy 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. 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) > > > ## * ## > > > Owen DeLong wrote: > >>Template: ARIN-POLICY-PROPOSAL-TEMPLATE-1.0 >> >>1. Policy Proposal Name: Deprecate Lame Server Policy >>2. Author >> a. name: Owen DeLong >> b. email: owen at delong.com >> c. telephone: 408-921-6984 >> d. organization: JITTR Networks >> >>3. Proposal Version: 1.0 >>4. Submission Date: 11 September, 2007 >>5. Proposal type: delete >> new, modify, or delete. >>6. Policy term: permanent >> temporary, permanent, or renewable. >>7. Policy statement: >> Delete section 7 from the NRPM >> >>8. Rationale: >> Recent PPML discussion has called attention to the >> fact that lame DNS delegations are more an operational >> issue than one of policy. As such, the existing lame >> delegation policy should be removed from the NRPM >> to remove the resultant confusion. This is not meant >> to prevent ARIN staff from taking reasonable action >> WRT DNS operational issues related to resources issued >> by ARIN, but, such action can be covered by staff >> operational guidelines and is not within the scope >> of Address Policy. >> >>9. Timetable for implementation: >> 1 June, 2008 >>10. Meeting presenter: >>END OF TEMPLATE >>_______________________________________________ >>PPML >>You are receiving this message because you are subscribed to the ARIN Public Policy >>Mailing List (PPML at arin.net). >>Unsubscribe or manage your mailing list subscription at: >>http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services >>Help Desk at 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 (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Thu Sep 13 14:52:57 2007 From: info at arin.net (Member Services) Date: Thu, 13 Sep 2007 14:52:57 -0400 Subject: [ppml] Policy Proposal: Modification to Reverse Mapping Policy In-Reply-To: <46E8007C.6010507@arin.net> References: <46E8007C.6010507@arin.net> Message-ID: <46E98709.5000808@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 Robert Seastrom and Cathy Aronson. 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 a formal policy 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. 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: Modification to Reverse Mapping Policy > > Author: John Von Essen > > Proposal Version: 1.0 > > Submission Date: September 11, 2007 > > Proposal type: modify > > Policy term: permanent > > Policy statement: > > I am proposing a modification to section 7 of the IPv4 policy such that > a more precise definition and overview of lameness is described. > Below is how I think section 7 should be re-written. > > START NEW Section > > 7. Reverse Mapping > > 7.1. Maintaining IN-ADDRs > > All ISPs receiving one or more distinct /16 CIDR blocks of IP addresses > from ARIN will be responsible for maintaining all IN- ADDR.ARPA domain > records for their respective customers. For blocks smaller than /16, and > for the segment of larger blocks which start or end with a CIDR prefix > longer than /16, ARIN can maintain IN-ADDRs through the use of the SWIP > (Reallocate and Reassign) templates or the Netmod template for /24 and > shorter prefixes. > > 7.2 Definitions > > 7.2.1 Lame Delegation > > A delegation is defined as being lame if all of the in-addr.arpa zones > for a given name server of a specific network registration are lame. An > in- addr.arpa zone is defined as lame when ARIN requests the SOA record > from the name server registered in whois, but does not receive an answer. > > 7.2.2 Partially Lame Delegation > > A delegation is defined as being partially lame if at least one in- > addr.arpa zone for a given name server of a specific network > registration is lame. An in- addr.arpa zone is defined as lame when ARIN > requests the SOA record from the name server registered in whois, but > does not receive an answer. > > 7.3. Handling of Lame and Partially Lame Delegations in IN-ADDR.ARPA > > ARIN will actively identify lame and partially lame DNS name server > (s) for reverse address delegations associated with address blocks > allocated, assigned or administered by ARIN. Upon identification of a > lame or partially lame delegation, ARIN shall attempt to contact the POC > for that resource and resolve the issue. If, following due diligence, > ARIN is unable to resolve the lame or partially lame delegation, ARIN > will update the WHOIS database records resulting in the removal of lame > or partially lame DNS servers. ARIN's actions in resolving lame and > partially lame delegations is governed by the procedures set forth in > (Lame-Ref). > > 7.4 References > > (Lame-Ref) "Lame Delegations In IN-ADDR.ARPA", http://www.arin.net/ > reference/lame_delegations.html > > > STOP NEW Section > > > Rationale: > > Current policy only considers an Org's delegation being deemed lame if > all of in-addr.arpa zones for a given name server of a specific network > registration are lame. Lame is defined when ARIN tests an in-addr.arpa > zone by requesting the SOA record from the name server registered in > whois, but does not receive an answer. If deemed lame, ARIN has an > appropriate procedure for contacting the Org and handling the issue as > per "http://www.arin.net/ reference/lame_delegations.html". > > Unfortunately, the policy does not cover the situation of a so-called > partially lame delegation. That is, some of the in-addr.arpa zones > belonging to the network registration return a valid SOA upon testing, > and some do not. Even if only one /24 in-addr.arpa reverse tests comes > back as lame, it is my opinion that this still taints the reputation of > entire network registration. IPs belonging to that lame in-addr.arpa > zone will cause query timeouts to 3rd party dns resolvers, both public > and private. These excessive timeouts in my opinion can harm the overall > well-being of reverse dns functionality throughout the internet. The > only way to prevent such harm is for ARIN to not delegate reverse > authority to the so-called partially lame dns server as registered in > whois. That is the purpose of this policy proposal, to consider partial > lameness with the same prejudice as traditionally defined lameness. > Org's who are partially lame should be contacted by ARIN and lame > in-addr.arpa zones should be resolved as the procedures per > "http://www.arin.net/reference/ lame_delegations.html" dictate. > > Timetable for implementation: June 1, 2008 > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to the ARIN Public Policy > Mailing List (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Fri Sep 14 10:11:23 2007 From: info at arin.net (Member Services) Date: Fri, 14 Sep 2007 10:11:23 -0400 Subject: ARIN commments regarding Lame Delegation Policy Message-ID: <46EA968B.40104@arin.net> The following comments are being provided in response to recent discussions and questions raised on the ppml. ARIN has implemented the methodology for identifying lameness as described at: http://www.arin.net/reference/lame_delegations.html Using the 208.114.64.0/19 example posted on ppml, each name server would be tested for all 32 reverse zones. A name server would be deemed lame only when all zones fail. If one or more of the reverse zones in the /19 is configured properly for a given name server, the name server delegation for that /19 would be declared 'good'. With regard to lame delegations reported to ARIN by third parties, ARIN will not respond to requests to remove these delegations without exercising the procedure adopted to implement the lame delegation policy. ARIN staff believes the current policy, as ratified, provides sufficient direction for lame delegations to be cleaned up. Regards, Nate Davis Chief Operations Officer American Registry for Internet Numbers (ARIN) From info at arin.net Mon Sep 17 13:41:23 2007 From: info at arin.net (Member Services) Date: Mon, 17 Sep 2007 13:41:23 -0400 Subject: ARIN XX - Policy Proposals and Draft Agenda Message-ID: <46EEBC43.7070805@arin.net> The following policy proposals have been under discussion on the ARIN Public Policy Mailing List and will be presented for consideration at the upcoming ARIN XX Public Policy Meeting in Albuquerque, New Mexico, on 17-18 October 2007. 2007-25: IPv6 Policy Housekeeping 2007-24: IPv6 Assignment Guidelines 2007-23: End Policy for IANA IPv4 allocations to RIRs 2007-22: Expand timeframe of Additional Requests 2007-21: PIv6 for legacy holders with RSA and efficient use 2007-20: Definition of known ISP and changes to IPv6 initial allocation criteria 2007-19: IANA Policy for Allocation of ASN Blocks to RIRs 2007-18: Global Policy for the Allocation of the Remaining IPv4 Address Space 2007-17: Legacy Outreach and Partial Reclamation 2007-16: IPv4 Soft Landing 2007-15: Authentication of Legacy Resources 2007:14: Resource Review Process 2007-13: Removal of ISP Immediate Need from End-User 2006-7: Changes to IPv6 initial allocation criteria The full text for each proposal can be found at: http://www.arin.net/policy/proposal_archive.html Agenda information has been updated. Find the draft agenda as well as hotel information at: http://www.arin.net/ARIN-XX/ Check back as the agenda information is updated periodically. Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Sep 17 16:52:24 2007 From: info at arin.net (Member Services) Date: Mon, 17 Sep 2007 16:52:24 -0400 Subject: [ppml] Revised 2007-17 In-Reply-To: <2E14E78C-06D7-49CC-9093-1385B436CF58@delong.com> References: <2E14E78C-06D7-49CC-9093-1385B436CF58@delong.com> Message-ID: <46EEE908.6080101@arin.net> Policy Proposal 2007-17: Legacy Outreach and Partial Reclamation has been revised. This proposal is open for discussion on this mailing list and will be on the agenda at the upcoming ARIN Public Policy Meeting. The current policy proposal text is provided below and is also available at: http://www.arin.net/policy/proposals/2007_17.html Regards, Member Services American Registry for Internet Numbers (ARIN) Owen DeLong wrote: > Based on input from the AC and comments on the mailing list, I have > decided to revise 2007-17. > > Specific ideas incorporated into this proposal: > 1. Specific fee statements removed. Fees are not the realm > of IRPEP, so, it is replaced with a requirement for the BoT > to develop appropriate incentives. > > 2. An oversight in the original version did not provide a > timeframe in which addresses were to be returned. > This version adopts a 12 month timeframe with staff > discretion for up to 2 extensions of 6 months each. > > 3. This proposal differs from the existing section 4.6 in > that it places discretion over whether a subnet of > a returned block may be retained or not in the hands > of the address holder. There was some suggestion > from some AC members that this discretion should > only be given to legacy holders while ARIN staff should > retain discretion over non-legacy resources. I do not > have a strong opposition to such a change, but, I do > feel that the policy is actually better as is, so, I have > chosen not to add this revision. I would like to see > discussion on this area, and, if it is possible, I would > like this version to allow the AC discretion to gauge > consensus on whether this edit should be added > prior to last call. > > > Revised proposal is as follows: > > > Policy Proposal 2007-17 > Legacy Outreach and Partial Reclamation > > Author: Owen DeLong > > Proposal Version: 1.0 > Submission Date: 2007 September 15 > > Proposal type: modify > > Policy term: permanent > > Policy statement: > > Modify section 4.6 as follows: > > 4.6 Amnesty Requests: > > ARIN will accept the return or relinquishment of > any address space from any existing address holder. If the address > holder wishes to aggregate into a single block, ARIN may work with the > address holder to arrive at an allocation or assignment which is equal > to or smaller than the sum of their existing blocks and which best meets > the needs of the existing holder and the community. The organization > returning the addresses shall have 12 months from the date they receive > their new addresses to return the addresses under this policy. > Organizations > may request no more than 2 six month extensions to this time, which, > may be granted at ARIN the discretion of ARIN staff. There shall be no > fee for returning addresses under this policy. Further, organizations > returning addresses under this policy shall receive the following > benefits: > > 1. If the organization does not currently pay ARIN fees, they shall > remain fee exempt. > > 2. The BoT shall develop an incentive program to encourage such > returns. Such incentives may include fee reductions and/or other > such mechanisms as the BoT deems appropriate. > > 3. Any organization returning address space under this policy shall > continue under their existing RSA or they may choose to sign the current > RSA. For organizations which currently do not have an RSA, they may sign > the current RSA, or, they may choose to remain without an RSA. > > 4. All organizations returning space under this policy shall, if they > meet other eligibility requirements and so request, obtain an > appropriate IPv6 end-user assignment or ISP allocation as applicable, > with no fees for the first 5 years. Organizations electing to receive > IPv6 allocation/assignment under this provision must sign a current RSA > and must agree that all of their IPv4 and ASN resources are > henceforth subject > to the RSA. Organizations taking this election shall be subject to > end-user fees for their IPv4 resources not previously under an ARIN RSA. > If they are already an ARIN subscriber, then IPv4 resources affected by > this process may, instead, be added to their existing subscriber > agreement at the address holder's discretion. > > Rationale: > > The current amnesty policy does a nice job of facilitating aggregation, > which was the intent when it was drafted. However, as we approach IPv4 > free-space exhaustion, the community now has an additional need to > facilitate address reclamation. > > A very high percentage of underutilized space is in the hands of legacy > holders who currently have no benefit to joining the ARIN process. > Further, there is an unfortunate perception that doing so will require > force the legacy holder into certain future disadvantages. This proposal > attempts to resolve both of those issues while also providing some > incentive to legacy organizations to start using IPv6 resources and > bring their IPv4 resources into the ARIN process. > > This policy attempts to provide some benefit and remove most of the > costs of making partial IPv4 returns. It also attempts to provide an > incentive for these IPv4 holders to join the ARIN process. > > It is suggested that the BoT adopt fee incentives such as the > elimination of 2 years of ARIN fees for each /20 returned. > > > Timetable for implementation: Immediate > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to the ARIN Public Policy > Mailing List (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Tue Sep 18 14:27:27 2007 From: info at arin.net (Member Services) Date: Tue, 18 Sep 2007 14:27:27 -0400 Subject: [ppml] proposal 2007-20 In-Reply-To: <46EF26CE.20800@kl.net> References: <46EF26CE.20800@kl.net> Message-ID: <46F0188F.5030708@arin.net> Policy Proposal 2007-20 has been withdrawn by the author. The proposal text has been archived at: http://www.arin.net/policy/proposals/2007_20.html Regards, Member Services American Registry for Internet Numbers (ARIN) Kevin Loch wrote: > I would like to withdraw my 2007-20 from consideration. If the community > finds parts of it useful I recommend incorporating them into one of the > other proposals up for consideration (perhaps 2007-25). > > 2007-25 already addresses one of the issues (200 /48 -> 200 separate > customers). A definition of what exactly an "existing ISP" is might > still be useful. > > - Kevin > _______________________________________________ > PPML > You are receiving this message because you are subscribed to the ARIN Public Policy > Mailing List (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Wed Sep 19 11:15:13 2007 From: info at arin.net (Member Services) Date: Wed, 19 Sep 2007 11:15:13 -0400 Subject: ARIN XX: Act Now and Save Money! Message-ID: <46F13D01.7040201@arin.net> ARIN looks forward to your participation at the ARIN XX Public Policy and Members Meeting, taking place 17-19 October 2007, in Albuquerque, New Mexico. Register today to take advantage of the early registration fee of $100. It increases to $150 on 3 October. The meeting will take place at the Hyatt Regency Albuquerque. ARIN XX attendees are eligible for a special room rate of $158 (USD), based on availability, if reservations are made before 24 September. Hotel and travel information, meeting registration, and agenda details, are available through http://www.arin.net/ARIN-XX/. In addition to ARIN policy proposal discussions, the meeting will also feature the following: Sunday, 14 October * An all-day program focusing on IPv6, including a workshop, tutorial, and panel discussions. Visit http://www.arin.net/ARIN-XX/v6_sunday.html for details. Tuesday, 16 October * A First Timer Lunch from 12:30 - 1:30 PM, where those new to the ARIN community or meetings can meet members of ARIN's Board, Advisory Council, and staff * A brief session "Introduction to the Internet Resource Policy Evaluation Process" will begin at 5:30 PM * The Open Policy Hour will begin at 6:00 PM Wednesday, 17 October * The ARIN XX Social Event, a southwestern evening at the Los Amigos Roundup Ranch on the Sandia Indian Reservation from 7:00 PM to 10:00 PM. More information is available at: http://www.arin.net/ARIN-XX/social.html If you are interested in any of the Tuesday or Wednesday activities, select the events on your registration form; the Sunday IPv6 training sessions do not require pre-registration. If you have already registered, but would like to modify your choice of events, click on the "Update Existing Registration" link available through the URL at the top of the page. As always, please contact ARIN Member Services at info at arin.net with any questions. We look forward to seeing you in Albuquerque! Regards, Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Sep 24 08:45:37 2007 From: info at arin.net (Member Services) Date: Mon, 24 Sep 2007 08:45:37 -0400 Subject: ARIN XX - Open Policy Hour Message-ID: <46F7B171.3050906@arin.net> Some Questions about the Policy Process: 1. Do you want to know what policy proposals will be discussed at the upcoming ARIN Public Policy Meeting? 2. Do you have an idea about how ARIN should manage Internet Number Resources? 3. Do you think that a current policy should be enhanced or changed, or even retired? 4. Are you hesitant about making a formal proposal on the Public Policy Mail List (PPML)? 5. Are you new to the Policy Development Process? If the answer to any of these questions is yes, then you should attend the Open Policy Hour! What is The Open Policy Hour? It is your opportunity to get a better understanding of what is going to be discussed at the upcoming Public Policy Meeting or for you to discuss your ideas in an open, informal forum and receive feedback or both! The Open Policy Hour consists of two parts. Part One is the P2B2 or the Policy Proposal Background Briefing. ARIN staff will provide summary information regarding the policy proposals that will be discussed at the meeting. Members of the ARIN Advisory Council will be present to answer general questions about the policy proposals. There will be no discussion of the proposals, just the information that you need to help you understand the nature of the proposals. Part Two is the P2B or the Policy Proposal BoF. This is where you get a chance to "test drive" a policy idea. How can you participate? Bring your ideas and questions. If you have a policy suggestion for which you would like to receive feedback prior to submitting it to the community on the PPML, here is your opportunity. If you have a short (3-minute) presentation prepared you will be given the first opportunity to present it. To sign up to give a presentation please send an e-mail to policy at arin.net by 12 October 2007 with your name, organization, and a brief description of your policy subject. Come join your colleagues in this informal setting. The Open Policy Hour for ARIN XX will be held on Tuesday, 16 October, from 6:00 - 7:00 PM. If you are not familiar with the way policies are developed in the ARIN region, join ARIN staff a half hour earlier, at 5:30 PM, for a review of the Internet Resource Policy Evaluation Process. Registration and hotel information for ARIN XX is available at: http://www.arin.net/ARIN-XX/ 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 Tue Sep 25 14:11:32 2007 From: info at arin.net (Member Services) Date: Tue, 25 Sep 2007 14:11:32 -0400 Subject: [ppml] Policy Proposal: Modification to Reverse Mapping Policy - AC did not accept In-Reply-To: <46E8007C.6010507@arin.net> References: <46E8007C.6010507@arin.net> Message-ID: <46F94F54.1090601@arin.net> On 20 September 2007, the ARIN Advisory Council (AC) concluded its review of the proposed policy 'Modification to Reverse Mapping Policy' and did not accept it as a formal policy proposal. The AC provided the following explanation of their decision: "Although the Advisory Council is sympathetic to your cause we have moved to not accept your proposal: Modification to Reverse Mapping Policy. The reason we have chosen this motion is because detailed operational techniques do not belong in the the NRPM. Although this may have occurred in the past, we are taking measures to ensure that we move detailed operations into staff process and not the NRPM. We believe moving forward that the best way to suggest and or change operational process is through the ARIN Consultation and Suggestion Process." During the initial review period the AC may decide to: 1) Accept the proposal as a formal policy proposal as written. 2) Postpone their decision regarding the proposal until the next regularly scheduled AC meeting in order to work with the author. 3) Not accept the policy proposal. In the event that the AC decides not to accept the proposal, then the author may elect to use the petition process to advance the proposal. For petition details see the section called "Petition Process" in the ARIN Internet Resource Policy Evaluation Process which can be found at: http://www.arin.net/policy/irpep.html The deadline for the author to initiate a petition per the ARIN Internet Resource Policy Evaluation Process is 40 days prior to the meeting; the petition deadline for the ARIN XXI Public Policy Meeting is 23:59 EDT, 27 February 2008. If the author chooses not to petition or the petition is unsuccessful, then the proposed policy is closed. If a petition is successful, then the proposal will be numbered and posted for discussion and presented at ARIN's Public Policy Meeting. 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 a formal policy 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. 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: Modification to Reverse Mapping Policy > > Author: John Von Essen > > Proposal Version: 1.0 > > Submission Date: September 11, 2007 > > Proposal type: modify > > Policy term: permanent > > Policy statement: > > I am proposing a modification to section 7 of the IPv4 policy such that > a more precise definition and overview of lameness is described. > Below is how I think section 7 should be re-written. > > START NEW Section > > 7. Reverse Mapping > > 7.1. Maintaining IN-ADDRs > > All ISPs receiving one or more distinct /16 CIDR blocks of IP addresses > from ARIN will be responsible for maintaining all IN- ADDR.ARPA domain > records for their respective customers. For blocks smaller than /16, and > for the segment of larger blocks which start or end with a CIDR prefix > longer than /16, ARIN can maintain IN-ADDRs through the use of the SWIP > (Reallocate and Reassign) templates or the Netmod template for /24 and > shorter prefixes. > > 7.2 Definitions > > 7.2.1 Lame Delegation > > A delegation is defined as being lame if all of the in-addr.arpa zones > for a given name server of a specific network registration are lame. An > in- addr.arpa zone is defined as lame when ARIN requests the SOA record > from the name server registered in whois, but does not receive an answer. > > 7.2.2 Partially Lame Delegation > > A delegation is defined as being partially lame if at least one in- > addr.arpa zone for a given name server of a specific network > registration is lame. An in- addr.arpa zone is defined as lame when ARIN > requests the SOA record from the name server registered in whois, but > does not receive an answer. > > 7.3. Handling of Lame and Partially Lame Delegations in IN-ADDR.ARPA > > ARIN will actively identify lame and partially lame DNS name server > (s) for reverse address delegations associated with address blocks > allocated, assigned or administered by ARIN. Upon identification of a > lame or partially lame delegation, ARIN shall attempt to contact the POC > for that resource and resolve the issue. If, following due diligence, > ARIN is unable to resolve the lame or partially lame delegation, ARIN > will update the WHOIS database records resulting in the removal of lame > or partially lame DNS servers. ARIN's actions in resolving lame and > partially lame delegations is governed by the procedures set forth in > (Lame-Ref). > > 7.4 References > > (Lame-Ref) "Lame Delegations In IN-ADDR.ARPA", http://www.arin.net/ > reference/lame_delegations.html > > > STOP NEW Section > > > Rationale: > > Current policy only considers an Org's delegation being deemed lame if > all of in-addr.arpa zones for a given name server of a specific network > registration are lame. Lame is defined when ARIN tests an in-addr.arpa > zone by requesting the SOA record from the name server registered in > whois, but does not receive an answer. If deemed lame, ARIN has an > appropriate procedure for contacting the Org and handling the issue as > per "http://www.arin.net/ reference/lame_delegations.html". > > Unfortunately, the policy does not cover the situation of a so-called > partially lame delegation. That is, some of the in-addr.arpa zones > belonging to the network registration return a valid SOA upon testing, > and some do not. Even if only one /24 in-addr.arpa reverse tests comes > back as lame, it is my opinion that this still taints the reputation of > entire network registration. IPs belonging to that lame in-addr.arpa > zone will cause query timeouts to 3rd party dns resolvers, both public > and private. These excessive timeouts in my opinion can harm the overall > well-being of reverse dns functionality throughout the internet. The > only way to prevent such harm is for ARIN to not delegate reverse > authority to the so-called partially lame dns server as registered in > whois. That is the purpose of this policy proposal, to consider partial > lameness with the same prejudice as traditionally defined lameness. > Org's who are partially lame should be contacted by ARIN and lame > in-addr.arpa zones should be resolved as the procedures per > "http://www.arin.net/reference/ lame_delegations.html" dictate. > > Timetable for implementation: June 1, 2008 > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to the ARIN Public Policy > Mailing List (PPML at arin.net). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services > Help Desk at info at arin.net if you experience any issues. > From info at arin.net Tue Sep 25 14:12:27 2007 From: info at arin.net (Member Services) Date: Tue, 25 Sep 2007 14:12:27 -0400 Subject: Policy Proposal 2007-26: Deprecate Lame Server Policy Message-ID: <46F94F8B.7050100@arin.net> On 20 September 2007, the ARIN Advisory Council (AC) concluded their initial review of "Deprecate Lame Server Policy" and accepted it as a formal policy proposal for discussion by the community. The proposal is designated Policy Proposal 2007-26: Deprecate Lame Server Policy. The proposal text is below and can be found at: http://www.arin.net/policy/proposals/2007_26.html All persons in the community are encouraged to discuss Policy Proposal 2007-26 prior to it being presented at the ARIN XXI Public Policy Meeting in April 2008. Both the discussion on the Public Policy Mailing List and at the Public Policy Meeting will be used to determine the community consensus regarding this policy proposal. The ARIN Internet Resource Policy Evaluation Process can be found at: http://www.arin.net/policy/irpep.html ARIN's Policy Proposal Archive can be found at: http://www.arin.net/policy/proposals/proposal_archive.html Regards, Member Services American Registry for Internet Numbers (ARIN) ## * ## Policy Proposal 2007-26 Deprecate Lame Server Policy Author: Owen DeLong Proposal type: modify Policy term: permanent Policy statement: Replace Section 7 of the NRPM in it's entirety with the following text: 7. Staff action to improve ARIN public database accuracy and consistency. 7.1 ARIN staff shall take reasonable and practicable means to ensure and improve the accuracy of all ARIN public databases, including, but, not limited to WHOIS, delegations of the in-addr.arpa zone, and, delegations of the ip6.arpa zone. Rationale: Recent PPML discussion has called attention to the fact that lame DNS delegations are more an operational issue than one of policy. As such, the existing lame delegation policy should be removed from the NRPM to remove the resultant confusion. This is not meant to prevent ARIN staff from taking reasonable action WRT DNS operational issues related to resources issued by ARIN, but, such action can be covered by staff operational guidelines and is not within the scope of Address Policy. Timetable for implementation: 1 June, 2008 From info at arin.net Thu Sep 27 12:49:29 2007 From: info at arin.net (Member Services) Date: Thu, 27 Sep 2007 12:49:29 -0400 Subject: ARIN XX Remote Participation and Webcast Message-ID: <46FBDF19.6080401@arin.net> Unable to join us in Albuquerque for ARIN XX? If so, and you?re frustrated at the thought of missing the policy discussions and other interesting presentations, we have a solution for you! In its continuing effort to provide the community with an open forum, ARIN is offering a live webcast of the entire ARIN XX Public Policy and Member Meeting. In addition to the policy discussions, you?ll be able to hear the NRO Number Council candidate speeches on Wednesday morning and the Board of Trustees and Advisory Council candidate speeches on Friday morning. ARIN also invites individuals who cannot attend the meeting in person to participate remotely. Remote participants may e-mail questions and comments to be addressed in normal question and answer periods throughout the agenda. To register for remote participation, please visit http://www.arin.net/ARIN-XX/. Click the "Meeting Registration" button at the top of the page, choose "ARIN XX Remote Participant" from the drop-down box, and complete the form. The live meeting webcast is available without registering as a remote participant. All remote participants are subject to the Remote Participation Acceptable Use Policy (AUP). Additional information about remote participation and the webcast, including the Remote Participation AUP, is available at: http://www.arin.net/ARIN-XX/webcast.html Detailed information on how to access the meeting webcast will be posted through the URL above before the meeting. There are a variety of formats in which the meeting webcast will be streamed, and the broadcast will begin Wednesday, 17 October 2007 at 9:00 AM MDT (UTC/GMT -7 hours). For details on what types of feeds are available, please see the URL above. Regards, Member Services American Registry for Internet Numbers (ARIN)