From info at arin.net Mon Apr 24 13:37:01 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:37:01 -0700 Subject: Advisory Council Meeting Results - April 2023 Message-ID: <2F40E495-0A6B-4961-831D-A498D6604807@arin.net> In accordance with the Policy Development Process (PDP), the Advisory Council met on 19 April 2023. The AC has advanced the following to Last Call (will be posted separately for discussion): * ARIN-2021-8: Deprecation of the ?Autonomous System Originations? Field * ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy * ARIN-2022-3: Remove Officer Attestation Requirement for 8.5.5 * ARIN-2022-4: Clean-up of NRPM Sections 2.1 and 2.2 * ARIN-2022-5: Clean-up of NRPM Section 2.11 * ARIN-2022-8: Streamlining Section 11 Policy Language * ARIN-2022-11: Clean-up of NRPM ? Introduction of Sections 2.17 Regarding ARIN-2022-11, The ARIN Advisory Council advances ?Recommended Draft Policy ARIN 2022-11: Clean-up of NRPM ? Introduction of Section 2.17? to Last Call, for an extended period with communication sent from staff. ARIN staff confirms the correct Recommended Draft Policy text was communicated to PPML on 16 March 2023 and again on 21 March 2023. The appropriate text was presented ARIN 51 on 17 April 2023 which received community support. It has been noted https://www.arin.net/participate/policy/drafts/2022_11/ on ARIN?s website did not exactly match the text sent to PPML or the text presented at ARIN 51. ARIN?s website has been corrected, and ARIN staff apologizes for any confusion this may have caused. The AC is continuing to work on: Draft Policies: * ARIN-2022-12: Direct Assignment Language Update 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 Senior Policy Analyst American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:38:24 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:38:24 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2021-8: Deprecation of the 'Autonomous System Originations' field. Message-ID: <99107242-0912-49D8-A117-5877E413BFAE@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * ARIN-2021-8: Deprecation of the 'Autonomous System Originations' field. Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2021_8/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2021-8: Deprecation of the 'Autonomous System Originations' field. AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Based on community feedback and AC discussion we motion to move ARIN-2021-8: Deprecation of the ?Autonomous System Originations? Field to Recommended Draft, with the following change to Language: The removal of ?OriginAs? fields from December 31st 2024 to 24 months after board adoption. Problem Statement: In the last two decades, ARIN has developed multiple services which provide mechanisms for Internet Number Resource holders to publish information about their routing intentions. The optional ?OriginAS? field was invented before RPKI existed in practice. At that time, ARIN?s Internet Routing Registry (IRR) followed a weak authorization model compared to available and in use today such as RPKI. The ?OriginAS? data was an improvement compared the other mechanisms that were available at that time. However, there are issues with the consumption of the data in the OriginAS field: Consuming the ?OriginAS? field in a high-scale automated pipeline is challenging. The consumer needs to enter into a ?Bulk Whois Data? agreement with ARIN, download a multiple-gigabytes XML file (which is only generated once a day), parse this XML file, and then extract the OriginAS field. Querying objects one-by-one via the HTTPS interface does not scale well. Policy statement: 1) Remove Section 3.5 ?Autonomous System Originations? of the NRPM in its entirety. 2) Remove the ?OriginAS? field from the database Timetable for Implementation: 1) Removal of section 3.5: Immediate after ARIN Board adoption. 2) Removal of the ?OriginAS? field from the database: 24 months after ARIN Board adoption. Policy Term: Permanent -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:38:32 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:38:32 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy Message-ID: <17141B48-7806-4E07-9967-BCDF5C4EF209@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_2/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-2: Remove Barrier to BGP Uptake in ASN Policy AC Assessment of Conformance with the Principles of Internet Number Resource Policy: This Draft Policy is fair, impartial, and technically sound. ARIN-2022-2 would rewrite ARIN?s Autonomous System Numbers policy, reducing its overall size and specifying single-ASN issuance as the default action. The Draft Policy deals with issuance and manually vetted request documentation requirements, which have no significant registry impact as a result of implementation. Problem Statement: The current requirements for getting an ASN have resulted in confusion particularly for new entrants, who have their hands more than full with the mechanics of getting BGP up and running.The availability of 32 bit ASNs provides an opportunity for the removal of unnecessary constraints and processes for the allocation of ASNs. ARIN does not provide guidance to use RFC1918 space if possible and likewise ARIN should not require the use of private ASNs in preference to public ASNs. Further Technical Rationale Four octet (32 bit) ASNs were defined in May 2007 in RFC 4893. It has taken several years for routing equipment in general use to catch up, but today 32 bit ASNs are generally accepted and it is rare that an organization which has been issued a 32 bit ASN comes back to ARIN and says they need a 16 bit ASN instead. The austerity measure of requiring extensive documentation to get an ASN is left over from the days of 16 bit ASNs (total space 65000). It is no longer appropriate and we should align our conservation requirements with those found in other 32-bit spaces (total space four billion). Consider: A /32 of IPv6 space is the default allocation and will be assigned to any ISP that requests it. Temporary assignment of a /32 of IPv4 space can be acquired on most residential ISPs by issuing a DHCP request. We propose making issuance of the first 32 bit ASN for any ORGID (or each site for organizations that have number resources under multiple discrete networks policy) be pro-forma upon request. If an org?s technical people think they need a public ASN, they probably do! Policy Statement: Replace the entirety of Section 5, which currently reads: There are a limited number of available Autonomous System Numbers (AS Numbers), therefore, it is important to determine which sites require unique ASNs and which do not. If a unique ASN is not required for a given network design, one or more of the ASN reserved for private use should be utilized. Those numbers are: 64512 through 65534 and 4200000000 through 4294967294 inclusive. In order to be assigned an ASN, each requesting organization must provide ARIN with verification that it requires a unique routing policy, such as a plan: To originate announcement of IP Number Resources via an accepted protocol (such as Border Gateway Protocol) from an ASN different than that of its upstream provider; To multihome a site with one or more Autonomous Systems; or To use an ASN to interconnect with other Autonomous Systems. ASNs are issued based on current need, as set out in this section 5. With the following new Section 5: Any organization may be issued a single Autonomous System Number (ASN) upon request. Organizations that have space issued under Multiple Discrete Networks policy may be issued one ASN per discrete network upon request. Additional ASN requests should include proof of the requestor?s need for a unique routing policy, or other technical justification for the need for more than one ASN. Timetable for Implementation: Any -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:38:51 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:38:51 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-3: Remove Officer Attestation Requirement for 8.5.5 Message-ID: The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * Recommended Draft Policy ARIN-2022-3: Remove Officer Attestation Requirement for 8.5.5 Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_3/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-3: Remove Officer Attestation Requirement for 8.5.5 AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Draft Policy 2022-3 conforms with the principles of the ARIN Policy Development Process. It is fair, impartial, and technically sound. This policy, if adopted, will remove the requirement of officer attestation from specified transfer recipients. The policy has received support from the community. Problem Statement: Requiring an officer attestation requires unnecessary resources and increases the time to complete an IPv4 transfer. Policy statement: 8.5.5. Block Size Organizations may qualify for the transfer of a larger initial block, or an additional block, by providing documentation to ARIN which details the use of at least 50% of the requested IPv4 block size within 24 months. Removing ?An officer of the organization shall attest to the documentation provided to ARIN.? Timetable for implementation: Immediate Comments: This is the only remaining mention outside Section 9 (which makes good use of the restrictions it has). Due to the cost of IPv4 at this time it is safe to say that someone of authority is aware of this transaction without having them provide an attestation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:39:11 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:39:11 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-4: Clean-up of NRPM Sections 2.1 and 2.2 Message-ID: <98ABD910-7973-4A3D-AF8D-4563479CB86C@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * Recommended Draft Policy ARIN-2022-4: Clean-up of NRPM Sections 2.1 and 2.2 Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_4/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-4: Clean-up of NRPM Sections 2.1 and 2.2 AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Based on community feedback and AC discussion, we motion to move ARIN-2022-4: Clean-up of NRPM Sections 2.1 and 2.2 to Recommended Draft, with the following change in text: In Section 2.1, change the text ?IP address space? to ?Internet number resources?, and in Section 2.2, change the text ?address space? to ?number resources?. This Draft Policy is fair, impartial, and technically sound and will clarify the intent of the text in sections 2.1 and 2.2. Problem Statement: This proposal continues the work that the ARIN AC NRPM Clean-up Working Group undertook to conduct an editorial review of the NRPM. It relates specifically to Sections 2.1 and 2.2. The focus of this proposal is to increase the consistency of terminology employed in the NRPM. Policy statement: In Section 2.1, change the text ?IP address space? to ?Internet number resources?, and in Section 2.2, change the text ?address space? to ?number resources? to reflect all of the types of Internet number resources administered by the types of entities defined in those sections. Timetable for implementation: Immediate Comments: This proposal is intended to replace Prop-305 in part. Although the proposal was drafted in the course of an editorial review of Sections 2.1 and 2.2, some of the changes proposed may not be considered purely editorial in nature and so this proposal is not being presented as strictly editorial. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:39:31 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:39:31 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-5: Clean-up of NRPM Section 2.11 Message-ID: <726AC30A-DF38-4BB7-AA08-F617393C284E@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * Recommended Draft Policy ARIN-2022-5: Clean-up of NRPM Section 2.11 Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_5/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-5: Clean-up of NRPM Section 2.11 AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Recommended Draft Policy ARIN-2022-5 conforms to the principles of the ARIN Policy Development Process. This policy, if adopted, will add clarity to the text in Section 2.11 of the NRPM regarding community networks. It is fair, impartial, technically sound and has received support from the community. Problem Statement: This proposal continues the work that the ARIN AC NRPM Clean-up Working Group undertook to conduct an editorial review of the NRPM. It relates specifically to Section 2.11. The focus of this proposal is to ensure that the intended meaning of the text is clear. Policy statement: Change the text ?A community network is deployed, operated and governed by its users? to ?A community network is one that is deployed, operated and governed by its users? in the first line and change the text ?to the user community it services? from ?to the community it services? in the second line. Timetable for implementation: Immediate Comments: This proposal is intended to replace Prop-305 in part. Although the proposal was drafted in the course of an editorial review of Section 2.11, some of the changes proposed may not be considered purely editorial in nature and so this proposal is not being presented as strictly editorial. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:40:05 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:40:05 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-8: Streamlining Section 11 Policy Language Message-ID: <96F83DCF-6B5A-4F69-A087-246F1F3DEDD6@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call: * Recommended Draft Policy ARIN-2022-8: Streamlining Section 11 Policy Language Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 8 May 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_8/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-8: Streamlining Section 11 Policy Language AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Recommended Draft Policy 2022-8 conforms to the ARIN Policy Development Process since: (1) the simplifications and additional clarity of the proposed text enhance the fair and impartial administration of number resources by ARIN; (2) clarifications contained in the text regarding the temporary nature of the use of number resources for experimental purposes are technically sound, since they support the conservation and efficient utilization of number resources; and (3) the proposed text appears to be supported by the community generally based on feedback received so far. Problem Statement: Section 11 of the NRPM contains a great deal of language that is either explicitly not policy, or is not impactful on ARIN?s administration of Internet number resources for experimental allocations, or to the customers requesting said resources. A revision to transform Section 11 into a collection of policies for experimental allocations serves to make the Section more easily digested by the reader, and a more functional reference for customers and ARIN staff during experimental allocation requests. Policy Statement: Section 11 Overview Current text: Experimental Internet Resource Allocations ARIN will allocate Numbering Resources to entities requiring temporary Numbering Resources for a fixed period of time under the terms of recognized experimental activity. ?Numbering Resources? refers to unicast IPv4 or IPv6 address space and Autonomous System numbers. The following are the criteria for this policy: Proposed text: Experimental Internet Resource Allocations ARIN will allocate Internet Number Resources to organizations requiring temporary Internet Number Resources for a fixed period of time under the terms of a recognized experimental activity. Section 11.1 Current text: 11.1. Documentation of Recognized Experimental Activity A Recognized Experimental Activity is one where the experiment?s objectives and practices are described in a publicly accessible document. It is a normal requirement that a Recognized Experimental Activity also includes the undertaking that the experiment?s outcomes be published in a publicly accessible document at the end of the experiment. The conditions for determining the end of the experiment are to be included in the document. Applicants for an experimental allocation are expected to demonstrate an understanding that when the experiment ends, the allocation will be returned; a successful experiment may need a new allocation under normal policies in order to continue in production or commercial use, but will not retain the experimental allocation. A ?publicly accessible document? is a document that is publicly and openly available free of charges and free of any constraints of disclosure. ARIN will not recognize an experimental activity under this policy if the entire research experiment cannot be publicly disclosed. ARIN has a strong preference for the recognition of experimental activity documentation in the form of a document which has been approved for publication by the IESG or by a similar mechanism as implemented by the IETF. Proposed text: 11.1. Eligibility Criteria for Recognized Experimental Activity The eligibility criteria for a recognized experimental activity under this policy are: The experiment?s description and objectives are published in a publicly accessible document, which for the purposes of this policy means that the document is readily available free of charge to the public, and free of any constraints of disclosure within one year after the end of the experiment; The experiment?s outcomes must also be published in a publicly accessible document; Demonstration to ARIN that the experimental activity is technically sound; and Demonstration to ARIN that the experimental activity is technically coordinated in that consideration of any potential negative impact of the proposed experiment on the operation of the Internet and its deployed services has been considered, and a description of experimenter mitigation plans to contain any negative impacts has been provided. Retire Sections 11.2 and 11.3 Section 11.4 Current text: 11.4. Resource Allocation Term and Renewal The Numbering Resources are allocated for a period of one year. The allocation can be renewed on application to ARIN providing information as per Detail One. The identity and details of the applicant and the allocated Numbering Resources will be published under the conditions of ARIN?s normal publication policy. At the end of the experiment, resources allocated under this policy will be returned to the available pool. Proposed text: 11.4. Resource Allocation Term and Renewal The Internet Number Resources are allocated for a period of one year under this policy. The allocation can be renewed on application to ARIN, prior to the expiry of the one-year period, providing information as to why an extension is necessary for a successful experiment. The resources allocated under this policy must be returned to ARIN at the earliest of: (1) the recognized experimental activity has ended; or (2) the end of the one-year period and any extension thereof. Section 11.5 Current text: 11.5. Single Resource Allocation per Experiment ARIN will make one-off allocations only, on an annual basis to any applicant. Additional allocations to an organization already holding experimental activity resources relating to the specified activity outside the annual cycle will not be made unless justified by a subsequent complete application. It?s important for the requesting organization to ensure they have sufficient resources requested as part of their initial application for the proposed experimental use. Proposed text: 11.5. Single Resource Allocation per Experiment ARIN will make only one allocation per recognized experiment. An allocation may consist of multiple Internet Number Resources if required to conduct the recognized activity. Additional allocations to an organization already holding experimental activity resources will not be made under this policy unless justified by a subsequent complete application relating to a different experimental activity. Retire Section 11.6 Section 11.7 Current text: 11.7. Resource Allocation Guidelines The Numbering Resources requested come from the global Internet Resource space, do not overlap currently assigned space, and are not from private or other non-routable Internet Resource space. The allocation size shall be consistent with the existing ARIN minimum allocation sizes, unless smaller allocations are intended to be explicitly part of the experiment. If an organization requires more resources than stipulated by the minimum allocation size in force at the time of its request, the request must clearly describe and justify why a larger allocation is required. All research allocations must be registered publicly in whois. Each research allocation will be designated as a research allocation with a comment indicating when the allocation will end. Proposed text: 11.7. Resource Allocation Guidelines The Internet Number Resources requested come from the global Internet Number Resource space, shall not overlap any currently assigned space, and shall not be from private or other non-routable Internet Number Resource space. The allocation size shall be consistent with existing ARIN minimum allocation sizes, unless smaller allocations are explicitly required due to the nature of the experiment. If an organization requires more resources than stipulated by the minimum allocation size in force at the time of its request, the request must clearly describe and justify why a larger allocation is required. All research allocations must be registered publicly in ARIN?s directory services. Each research allocation will be designated as a research allocation with a comment indicating when the allocation will end. Section 11.8 Current text: 11.8. Commercial Use Prohibited If there is any evidence that the temporary resource is being used for commercial purposes, or is being used for any activities not documented in the original experiment description provided to ARIN, ARIN reserves the right to immediately withdraw the resource and reassign it to the free pool. Proposed text: 11.8. Commercial Use Prohibited If there is any evidence that the temporary resource is being used for commercial purposes or is being used for any activities not documented in the original experiment description provided to ARIN, ARIN reserves the right to immediately withdraw the resource. Retire Section 11.9 Timetable for Implementation: Immediate Comments: Due to the scope of this Draft Policy?s recommended edits, a tracked document is available at https://www.arin.net/participate/policy/drafts/pdf/NRPM-Section11-update-20230314.pdf -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Apr 24 13:41:13 2023 From: info at arin.net (Edward Diego) Date: Mon, 24 Apr 2023 10:41:13 -0700 Subject: LAST CALL - Recommended Draft Policy ARIN-2022-11: Clean-up of NRPM =?UTF-8?B?4oCT?= Introduction of Section 2.17 Message-ID: <0D8BFA2A-B8EB-4D6F-A411-221E9693FE38@arin.net> The ARIN Advisory Council (AC) met on 19 April 2023, and sent the following Recommended Draft Policy to Last Call for an extended period with communication sent from staff: * Recommended Draft Policy ARIN-2022-11: Clean-up of NRPM ? Introduction of Section 2.17 ARIN staff confirms the correct Recommended Draft Policy text was communicated to PPML on 16 March 2023 and again on 21 March 2023. The appropriate text was presented at ARIN 51 on 17 Apr 2023 which received community support. It has been noted https://www.arin.net/participate/policy/drafts/2022_11/ on ARIN?s website did not exactly match the text sent to PPML or the text presented at ARIN 51. ARIN?s website has been corrected, and ARIN staff apologizes for any confusion this may have caused. Feedback is encouraged during the Last Call period. All comments should be provided to the Public Policy Mailing List. Last Call will expire on 9 Jun 2023. The Recommended Draft Policy text is below and available at: https://www.arin.net/participate/policy/drafts/2022_11/ The ARIN Policy Development Process is available at: https://www.arin.net/participate/policy/pdp/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2022-11: Clean-up of NRPM ? Introduction of Section 2.17 AC Assessment of Conformance with the Principles of Internet Number Resource Policy: Based on community feedback and AC discussion we motion to move ARIN-2022-11: Clean-up of NRPM ? Introduction of Section 2.17 to Recommended Draft, with the following definition: ?Internet number resources are unique identifiers within the Internet Numbers Registry System [as described in IETF RFC 7020] and this includes ranges (or ?blocks?) of contiguous Internet Protocol (?IP?) addresses and Autonomous System Numbers (?ASNs?).? This Draft Policy is fair, impartial, and technically sound and will add clarity to the term ?Internet number resources?. Problem Statement: The term Internet Number Resources is referenced in several sections of the NRPM but is not defined. Policy Statement: ?Internet number resources are unique identifiers within the Internet Numbers Registry System [as described in IETF RFC 7020] and this includes ranges (or ?blocks?) of contiguous Internet Protocol (?IP?) addresses and Autonomous System Numbers (?ASNs?).? Timetable for Implementation: Immediate Comments: Although this proposal was drafted in the course of an editorial review of Section 2 of the NRPM, the addition of a new definition may not be considered purely editorial in nature and so this proposal is not being presented as strictly editorial. -------------- next part -------------- An HTML attachment was scrubbed... URL: