From asuhelin at mpi-inf.mpg.de Fri Sep 13 14:13:40 2024 From: asuhelin at mpi-inf.mpg.de (Aleeza Suhel Inamdar) Date: Fri, 13 Sep 2024 20:13:40 +0200 Subject: [arin-ppml] =?utf-8?q?Qualitative_Study=3A_=E2=80=9CRouting_Real?= =?utf-8?q?ities=3A_Assessing_the_practicality_of_academic_BGP_security_so?= =?utf-8?q?lutions_in_network_operations=E2=80=9D?= Message-ID: Hello! My name is Aleeza, and I am a student pursuing my Master's thesis at the Max-Planck-Institute for Informatics. I am writing to cordially invite you to participate in an asynchronous online focus group study as part of our research project titled ?Routing Realities: Assessing the practicality of academic BGP security solutions in network operations?. Study Overview: This study, conducted by our research team, including myself, Mannat Kaur, and Tobias Fiebig, aims to explore the practicality of academic solutions, with a particular focus on BGP security. Your insights as a network operator will be invaluable in helping us understand the challenges and identify opportunities for improvement. Focus Group Details: Start Date: Around 3rd week of September Platform: Mattermost Total Runtime: 4 - (max) 6 weeks Total Questions: 6 Format: 1 week(maximum)/question Your Participation: As a participant, you will be asked to share your experiences, challenges, perspectives on the practical implementation of BGP security solutions proposed by academic research in real-world network environments, and engage in online group discussions with other network operators. The focus group discussions are asynchronous, and we encourage you to contribute your insights at a pace that suits your schedule. You can engage in the discussions all at once or spread your contributions across multiple days, depending on what is most convenient for you. If you have any questions or need additional information, please feel free to contact us. Registration: https://nextcloud.mpi-inf.mpg.de/index.php/apps/forms/s/WHnXHBDRgo3srisj5w3EYgqA I look forward to your participation in this study. Contact: asuhelin at mpi-inf.mpg.de, mkaur at mpi-inf.mpg.de, tfiebig at mpi-inf.mpg.de Thank you! From info at arin.net Fri Sep 13 15:51:04 2024 From: info at arin.net (ARIN) Date: Fri, 13 Sep 2024 15:51:04 -0400 Subject: [arin-ppml] Revised - ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2 Message-ID: The following Draft Policy has been revised: * ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2 Revised text is below and can be found at: https://www.arin.net/participate/policy/drafts/2024_10/ Note, only the Draft Policy title has been revised from ?Modernization of Registration Requirements? to ?ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2?. This revision intends to eliminate any confusion between Draft Policy ARIN-2024-10 and the previous draft policy with the same name: ?ARIN-2023-4: Modernization of Registration Requirements?. You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this Draft Policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are: * Enabling Fair and Impartial Number Resource Administration * Technically Sound * Supported by the Community The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Draft Policy ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2 Problem Statement: Registration is central to the value provided by ARIN to the community. Registry quality depends greatly upon the timely registration of reassignments from ISPs to end users. The motivation for registration has waned since the depletion of the free pool. Registration remains vital to a number of stakeholders, including law enforcement and network operators. This proposal aims to modernize the registration-related policies in Section 4 by introducing language that is meant to remind ISPs of the importance of registration when feasible for the benefit of the community. Policy Statement: REPLACE: Section 4.2.3.7.1 Original Text: ?Each IPv4 reassignment or reallocation containing a /29 or more addresses shall be registered via SWIP or a directory services system which meets the standards set forth in section 3.2.? New Text: ?Each IPv4 reassignment or reallocation containing a /29 or more addresses shall be registered via a directory services system which meets the standards set forth in section 3.2, within 14 days.? RETIRE: Section 4.2.3.7.2 - Reassignments and Reallocations Visible Within Seven Days RENAME: 6.5.5.1 from ?Reassignment Information? to ?Reassignment and Reallocation Information?. Timetable: Immediate Comments: This is an iteration of abandoned policy ARIN-2023-4. Due to substantial changes in the problem statement, it was preferred to abandon that policy and resubmit, as opposed to modifying the policy during its PDP cycle. From info at arin.net Tue Sep 24 13:11:24 2024 From: info at arin.net (ARIN) Date: Tue, 24 Sep 2024 13:11:24 -0400 Subject: [arin-ppml] Advisory Council Meeting Results - September 2024 Message-ID: <7090AD1B-FF5B-451A-B6F1-28E2B235B8C0@arin.net> In accordance with the Policy Development Process (PDP), the Advisory Council met on 19 September 2024. The AC has advanced the following to Recommended Draft Policy status (will be posted separately for discussion): --------- *ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Based on community feedback and AC discussion, we have promoted ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks to Recommended Draft Policy. This Draft Policy is fair, impartial, and technically sound; it will add clarity and readability to the NRPM sections being updated by this proposal. --------- *ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Following a review of community feedback, staff and legal recommendations, and AC discussions, Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information, was found to conform to the principles of the ARIN Policy Development Process. Based on being fair, impartial, and technically sound, this Draft Policy was moved to Recommended Draft state. If adopted by the board, it would further clarify what information is collected and published via ARIN's public Whois service. --------- *ARIN-2024-9: Remove Outdated Carveout for Community Networks AC Assessment of Conformance with the Principles of Internet Number Resource Policy: ARIN policy 2024-9 ?Remove Carveout for Community Networks? is fair and impartial, technically sound and has the support of the community to move to recommended status. The policy, if adopted, will retire sections 2.11 and 6.5.9 regarding Community Networks from the NRPM as there is no longer any advantage to obtaining space as a community network, and qualifying for community space is in fact more difficult than without the community requirements. The AC advances Draft Policies to Recommended Draft Policy status once they have been fully developed and meet ARIN's Principles of Internet Number Resource Policy. Specifically, these principles are: * Enabling Fair and Impartial Number Resource Administration * Technically Sound * Supported by the Community The AC is continuing to work on: Policy Proposals: *ARIN-prop-338: IPv4 Transition Efficiency Reallocation Policy (ITERP) Draft Policies: *ARIN-2023-8: Reduce 4.1.8 Maximum Allocation *ARIN-2024-4: Internet Exchange Point Definition *ARIN-2024-5: Rewrite of NRPM Section 4.4 Micro-Allocation *ARIN-2024-6: 6.5.1a Definition Update *ARIN-2024-7: Addition of Definitions for General and Special Purpose IP Addresses *ARIN-2024-8: Restrict the Largest Initial IPv6 Allocation to /20 *ARIN-2024-10: Registration Requirements and Timing of Requirements with Retirement of Section 4.2.3.7.2 Recommended Draft Policies: *ARIN-2022-12: Direct Assignment Language Update *ARIN-2024-1: Definition of Organization ID/Org ID The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) From info at arin.net Tue Sep 24 13:11:40 2024 From: info at arin.net (ARIN) Date: Tue, 24 Sep 2024 13:11:40 -0400 Subject: [arin-ppml] Recommended Draft Policy ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks Message-ID: <6D3CDD48-5264-4C77-B176-59986CFEDD7B@arin.net> On 19 September 2024, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status: *ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Based on community feedback and AC discussion, we have promoted ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks to Recommended Draft Policy. This Draft Policy is fair, impartial, and technically sound; it will add clarity and readability to the NRPM sections being updated by this proposal. The text of the Recommended Draft Policy is below, and may also be found at: https://www.arin.net/participate/policy/drafts/2023_7/ You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus. The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) ----------- Recommended Draft Policy ARIN-2023-7: Clarification of NRPM Sections 4.5 and 6.11 Multiple Discrete Networks Problem Statement: Section 4.5 and 6.11 of the NRPM does not adhere to the style guide used by the remainder of the document. The numbered lists in these two sections also detracts from the readability and usability of the NRPM. Policy Statement: Current: 4.5 Multiple Discrete Networks Organizations with multiple discrete networks desiring to request new or additional address space under a single Organization ID must meet the following criteria: 1. The organization shall be a single entity and not a consortium of smaller independent entities. 2. The organization must have compelling criteria for creating discrete networks. Examples of a discrete network might include: 3. Regulatory restrictions for data transmission, 4. Geographic distance and diversity between networks, 5. Autonomous multihomed discrete networks. 6. The organization must keep detailed records on how it has allocated space to each location, including the date of each allocation. 7. When applying for additional internet address registrations from ARIN, the organization must demonstrate utilization greater than 50% of both the last block allocated and the aggregate sum of all blocks allocated from ARIN to that organization. If an organization is unable to satisfy this 50% minimum utilization criteria, the organization may alternatively qualify for additional internet address registrations by having all unallocated blocks of addresses smaller than ARIN?s current minimum allocation size. 8. The organization may not allocate additional address space to a location until each of that location?s address blocks are 80% utilized. 9. The organization should notify ARIN at the time of the request their desire to apply this policy to their account. 10. Upon verification that the organization has shown evidence of deployment of the new discrete network site, the new network(s) shall be allocated the minimum allocation size under section 4.2.1.5. Proposed: Replace Section 4.5 in its entirety with the following text: 4.5 Multiple Discrete Networks Organizations with multiple discrete networks desiring to request a new or additional IP address space allocation under a single Organization ID must meet the following criteria: 1. The organization must be a single entity and not a consortium of smaller independent entities. 2. The organization must have compelling criteria for creating discrete networks. Examples of situations which may represent compelling criteria for multiple discrete networks might include: * Regulatory restrictions for data transmission; * Geographic distance and diversity between networks; or * Autonomous multihomed discrete networks. 3. The organization must keep detailed records on how it has allocated IP addresses to each location, including the date of each allocation. 4. When applying for additional IP address allocations from ARIN, the organization must demonstrate utilization greater than 50% of both the last IP addresses allocated and the aggregate sum of all IP addresses allocated from ARIN to that organization. If an organization is unable to satisfy this 50% minimum utilization criteria, the organization may alternatively qualify for additional IP address allocations by having all unallocated IP address blocks smaller than ARIN?s current minimum allocation size. 5. The organization must not allocate additional IP address space to a location until each of that location?s IP address allocations are 80% utilized. The organization must notify ARIN at the time of the request of their desire to apply this policy to their account. Current: 6.11. IPv6 Multiple Discrete Networks Organizations with multiple discrete IPv6 networks desiring to request new or additional address space under a single Organization ID must meet the following criteria: 1. The organization shall be a single entity and not a consortium of smaller independent entities. 2. The organization must have compelling criteria for creating discrete networks. Examples of a discrete network might include: * Regulatory restrictions for data transmission, * Geographic distance and diversity between networks, * Autonomous multihomed discrete networks. 3. The organization must keep detailed records on how it has allocated space to each location, including the date of each allocation. 4. The organization should notify ARIN at the time of the request their desire to apply this policy to their account. 5. Requests for additional space: 6. Organization must specify on the application which discrete network(s) the request applies to 7. Each network will be judged against the existing utilization criteria specified in 6.5.2 and 6.5.3 as if it were a separate organization, rather than collectively as would be done for requests outside of this policy. Proposed: Replace Section 6.11 in its entirety with the following text: 6.11. IPv6 Multiple Discrete Networks Organizations with multiple discrete IPv6 networks desiring to request new or additional IPv6 address allocations under a single Organization ID must meet the following criteria: 1. The organization must be a single entity and not a consortium of smaller independent entities. 2. The organization must have compelling criteria for creating discrete networks. Examples of situations which may represent compelling criteria for multiple discrete networks might include: * Regulatory restrictions for data transmission; * Geographic distance and diversity between networks; or * Autonomous multihomed discrete networks. 3. The organization must keep detailed records on how it has allocated IPv6 addresses to each location, including the date of each IPv6 address allocation. 4. When an organization is requesting additional IPv6 address allocations under this policy, the organization must specify on the application which discrete network(s) the IPv6 address request applies to. A request for additional space will be judged against the existing utilization criteria specified in 6.5.2 and 6.5.3 as if it were a separate organization, rather than collectively as would be done for requests outside of this policy. The organization must notify ARIN at the time of the request their desire to apply this policy to their account. Timetable for implementation: Immediate From info at arin.net Tue Sep 24 13:11:57 2024 From: info at arin.net (ARIN) Date: Tue, 24 Sep 2024 13:11:57 -0400 Subject: [arin-ppml] Recommended Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information Message-ID: <62870430-AE12-4CC8-A9B6-1C907A2AC209@arin.net> On 19 September 2024, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status: *ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Following a review of community feedback, staff and legal recommendations, and AC discussions, Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information, was found to conform to the principles of the ARIN Policy Development Process. Based on being fair, impartial, and technically sound, this Draft Policy was moved to Recommended Draft state. If adopted by the board, it would further clarify what information is collected and published via ARIN's public Whois service. The text of the Recommended Draft Policy is below, and may also be found at: https://www.arin.net/participate/policy/drafts/2024_2/ You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus. The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, ? Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information Problem Statement: ARIN?s mission includes maintaining and distributing registration information about who holds Internet number resources (Internet Protocol (IP) addresses and Autonomous System Numbers (ASNs)) in a public database referred to as Whois. Whois provides network operators, technical troubleshooters, law enforcement, researchers, and other interested parties with information about which organization administers specific Internet number resources. Distributing this non-personal information is very much in the public interest of proper functioning of the Internet. While ARIN continues to recognize the ongoing relevancy and importance for publicly available Whois information in its control, ARIN must also take stock of evolving regional developments pertaining to data privacy and the cross-border sharing of personally identifying information (PII) which have led to or could lead to redactions among similar Whois resources outside of ARIN?s purview. In light of such developments, it is important for ARIN to codify its Whois data requirements and disclosure practices in a manner that is both a) respectful of privacy rights pertaining to PII and b) cognizant of the value non-PII data plays in the security of the Internet and the protection of the general public. Currently there are no ARIN policies that clearly define what organization and associated point of contact information must be provided and registered in the public Whois. This proposal attempts only to clarify and codify ARIN?s existing practice regarding organization and contact data collection and display in Whois. Policy Statement: 2.12 Organizational Information Modify 2.12 to read: Information needed to uniquely identify an Organization. 3.8 Directory Service Records Modify 3.8.1 to include the following sentence: All organization registration records will be visible in the public Whois. Organizations that are registered as D/B/A may choose to show the Business name rather than the registered party?s name. Add 3.8.2 3.8.2 Required Organization Record Information The following information must be provided to ARIN to register an organization record: * Org Name * Org Postal Address including country Add 3.8.3 Point of Contact Record Creation An organization must register designated Points of Contact to manage its organization and resource registration records to include Administrative, Technical, NOC and Abuse contacts. These Points of Contact shall be representatives of the organization and any information provided to ARIN shall be that contact?s associated organizational information and not personal data. Point of Contact registration records will generally be visible in the public Whois. Refer to NRPM 3.3 and NRPM 4.2.3.7.3.2 for exceptions to this general rule. Add 3.8.4 Required Point of Contact Record Information. The following information must be provided to ARIN to register a Point of Contact: * Contact Name (this can be an individual representative of the company or a Role POC) * Contact?s Company Name (Required for Role POC) * Contact?s Postal Address including country * Contact?s Organization Phone Number (optional) * Contact?s Organization E-Mail Address Timetable: Immediate From info at arin.net Tue Sep 24 13:12:04 2024 From: info at arin.net (ARIN) Date: Tue, 24 Sep 2024 13:12:04 -0400 Subject: [arin-ppml] Recommended Draft Policy ARIN-2024-9: Remove Outdated Carveout for Community Networks Message-ID: <03F49585-4CA1-4151-9439-5E5DAF23A114@arin.net> On 19 September 2024, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status: *ARIN-2024-9: Remove Outdated Carveout for Community Networks AC Assessment of Conformance with the Principles of Internet Number Resource Policy: ARIN policy 2024-9 ?Remove Carveout for Community Networks? is fair and impartial, technically sound and has the support of the community to move to recommended status. The policy, if adopted, will retire sections 2.11 and 6.5.9 regarding Community Networks from the NRPM as there is no longer any advantage to obtaining space as a community network, and qualifying for community space is in fact more difficult than without the community requirements. The text of the Recommended Draft Policy is below, and may also be found at: https://www.arin.net/participate/policy/drafts/2024_9/ You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus. The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, ? Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) -------- Recommended Draft Policy ARIN-2024-9: Remove Outdated Carveout for Community Networks Problem Statement: Sections 2.11 and 6.5.9 define Community Networks, and provide special dispensation for Community Networks to receive only a /40 of IPv6 space. When these sections were last materially updated in 2017 (ARIN-2017-8), the smallest allowed allocation to a normal ARIN LIR was a /36, so the Community Networks sections still provided value. In 2020 (ARIN-2020-3) however, the NRPM was amended such that any LIR may request to receive only a /40 for any reason. As such, the carveout for Community Networks to receive a /40 is no longer necessary, and potentially confusing. Policy Statement: Retire Sections 2.11 and 6.5.9 Timetable for Implementation: Immediate. From lsawyer at gci.com Fri Sep 27 13:04:58 2024 From: lsawyer at gci.com (Leif Sawyer) Date: Fri, 27 Sep 2024 17:04:58 +0000 Subject: [arin-ppml] Recommended Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information In-Reply-To: <62870430-AE12-4CC8-A9B6-1C907A2AC209@arin.net> References: <62870430-AE12-4CC8-A9B6-1C907A2AC209@arin.net> Message-ID: Hello, PPML ? Given that we are just a few short weeks away from ARIN53, where this proposal will be presented as a Recommended Draft, now is your chance to let your opinions be heard and recorded for the presentation in the ?community feedback? section. With the changes to the policy as called out by the Staff and Legal now in place, this will be the last presentation for this policy if there is a lack of opposition to it. Therefore, any feedback, positive or negative, is very welcome and necessary at this stage of the Policy?s lifecycle. We appreciate your time and opinions, and we?ll see you in just over 3 weeks. -Leif ARIN Advisory Council Leif Sawyer GCI | he/him | Engineer, Network & Systems Delivery Engineering t: 907-351-1535 | w: www.gci.com From: ARIN-PPML On Behalf Of ARIN Sent: Tuesday, September 24, 2024 9:12 AM To: arin-ppml at arin.net Subject: [arin-ppml] Recommended Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information [EXTERNAL EMAIL - CAUTION: Do not open unexpected attachments or links.] On 19 September 2024, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status: *ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Following a review of community feedback, staff and legal recommendations, and AC discussions, Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information, was found to conform to the principles of the ARIN Policy Development Process. Based on being fair, impartial, and technically sound, this Draft Policy was moved to Recommended Draft state. If adopted by the board, it would further clarify what information is collected and published via ARIN's public Whois service. The text of the Recommended Draft Policy is below, and may also be found at: https://www.arin.net/participate/policy/drafts/2024_2/ You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus. The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2024-2: Whois Data Requirements Policy for Non-Personal Information Problem Statement: ARIN?s mission includes maintaining and distributing registration information about who holds Internet number resources (Internet Protocol (IP) addresses and Autonomous System Numbers (ASNs)) in a public database referred to as Whois. Whois provides network operators, technical troubleshooters, law enforcement, researchers, and other interested parties with information about which organization administers specific Internet number resources. Distributing this non-personal information is very much in the public interest of proper functioning of the Internet. While ARIN continues to recognize the ongoing relevancy and importance for publicly available Whois information in its control, ARIN must also take stock of evolving regional developments pertaining to data privacy and the cross-border sharing of personally identifying information (PII) which have led to or could lead to redactions among similar Whois resources outside of ARIN?s purview. In light of such developments, it is important for ARIN to codify its Whois data requirements and disclosure practices in a manner that is both a) respectful of privacy rights pertaining to PII and b) cognizant of the value non-PII data plays in the security of the Internet and the protection of the general public. Currently there are no ARIN policies that clearly define what organization and associated point of contact information must be provided and registered in the public Whois. This proposal attempts only to clarify and codify ARIN?s existing practice regarding organization and contact data collection and display in Whois. Policy Statement: 2.12 Organizational Information Modify 2.12 to read: Information needed to uniquely identify an Organization. 3.8 Directory Service Records Modify 3.8.1 to include the following sentence: All organization registration records will be visible in the public Whois. Organizations that are registered as D/B/A may choose to show the Business name rather than the registered party?s name. Add 3.8.2 3.8.2 Required Organization Record Information The following information must be provided to ARIN to register an organization record: * Org Name * Org Postal Address including country Add 3.8.3 Point of Contact Record Creation An organization must register designated Points of Contact to manage its organization and resource registration records to include Administrative, Technical, NOC and Abuse contacts. These Points of Contact shall be representatives of the organization and any information provided to ARIN shall be that contact?s associated organizational information and not personal data. Point of Contact registration records will generally be visible in the public Whois. Refer to NRPM 3.3 and NRPM 4.2.3.7.3.2 for exceptions to this general rule. Add 3.8.4 Required Point of Contact Record Information. The following information must be provided to ARIN to register a Point of Contact: * Contact Name (this can be an individual representative of the company or a Role POC) * Contact?s Company Name (Required for Role POC) * Contact?s Postal Address including country * Contact?s Organization Phone Number (optional) * Contact?s Organization E-Mail Address Timetable: Immediate _______________________________________________ ARIN-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: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact info at arin.net if you experience any issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Sep 30 13:29:37 2024 From: info at arin.net (ARIN) Date: Mon, 30 Sep 2024 13:29:37 -0400 Subject: [arin-ppml] Revised - ARIN-2023-8: Reduce 4.1.8 Maximum Allocation Message-ID: <8218B197-70EB-4A1A-A6FD-4B4702B0AE70@arin.net> The following Draft Policy has been revised: ? * ARIN-2023-8: Reduce 4.1.8 Maximum Allocation ? Revised text is below and can be found at: ? https://www.arin.net/participate/policy/drafts/2023_8 ? You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this Draft Policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are: ? * Enabling Fair and Impartial Number Resource Administration * Technically Sound * Supported by the Community ? The PDP can be found at: ? https://www.arin.net/participate/policy/pdp/ ? Draft Policies and Proposals under discussion can be found at: ? https://www.arin.net/participate/policy/drafts/ ? ? Regards, ? Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) --------- Draft Policy ARIN-2023-8: Reduce 4.1.8 Maximum Allocation Problem Statement: 4.1.8 waiting times are too long, making justifications untimely by the time a request is met. New entrants to the waiting list are expected to wait three years for their need to be met under current policy, with a waiting list of around 700 at this point. Data indicates that reducing the current /22 maximum further to a /24 would significantly reduce this waiting period, and further tightening the requirements by replacing the /20 recipient maximum holdings with a /24, and preventing multiple visits to the waiting list queue. Policy Statement: 4.1.8. ARIN Waitlist ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an organization may qualify for is a /24. Organizations which ever held any IPv4 space other than special use space received under section 4.4 or 4.10 are not eligible to apply. Address space distributed from the waitlist will not be eligible for transfer, with the exception of Section 8.2 transfers, for a period of 60 months. This policy will be applied to all future distributions from the waitlist to include those currently listed. Qualified requesters will also be advised of the availability of the transfer mechanism in section 8.3 as an alternative mechanism to obtain IPv4 addresses. Waiting list recipients must demonstrate the need for a /24 on an operating network. This policy will apply to waitlist requests received following the implementation of this policy. Waitlist requests received prior to the implementation of this policy will not be affected. In section 4.2.2 replace the sentence: FROM: ?All ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of up to a /22, subject to ARIN?s minimum allocation size.? TO: ?All ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of a /24.? In section 8.3 Conditions on the source of the transfer, remove this sentence: ?The source entity will not be allowed to apply for IPv4 address space under Section 4.1.8 ARIN Waitlist for a period of 36 months following the transfer of IPv4 address resources to another party.? Timetable for Implementation: Immediate Comments: Corrections were made for a typo (references to 4.18 as opposed to 4.1.8 as intended) in a number of places in the document, and a reference to 4.22 instead of 4.2.2. The core text remains unchanged, however. (Necessary changes/corrections made on Feb 6, 2024) Needs more careful review for intersection with other elements of the NRPM. Need to be careful with existing list member treatment. The author claims that they haven?t scanned the NRPM for other mentions of 4.1.8 that may need to be addressed. The author thinks section 4 can be drastically simplified further with this change. The intention in requiring demonstrated need is avoidance of the situation at RIPE where every new entrant got an automatic allocation, which resulted in many new entities incorporated only to receive this allocation. The author also noted a serendipity in the number of waiting list entries (703) and the amount of entries that could have been met with a /24 cap (703) in John Sweeting?s ARIN 52 presentation. Current waitlist entrants should be given retroactive consideration, but their maximum allocation reduced to /24. Additional text provides consideration and protection to those already on the Waitlist, to not be retroactively impacted by the policy once implemented. (Aug/Sept 2024)