Arin policy manual

To ensure there is immediate availability of a registered nurse, one nurse per procedure room is the expectation, regardless of the sedative administered with few exceptions.

When the nurse is administering procedural sedation, the nurse can have no other responsibilities apart from monitoring the patient and administering medications per order during the case. Joint Practice Guideline for Sterile Technique during Vascular and Interventional Radiology Procedures There is a need for current formal recommendations in the interventional radiology IR literature concerning the use of sterile technique during IR procedures.

This is particularly important given the increasing incidence of antibiotic resistance, complications from nosocomial infection, cost of health care, and emphasis on quality of care. This document summarizes the findings from the available surgical and IR literature on this topic. There is, however, a general lack of published randomized controlled studies on this subject.

This position is based on an extensive literature review demonstrating technical superiority and cost advantages with capnography use. Bariatric Patient Safety in the Imaging Environment The obese patient presents specific challenges within the imaging department because of the constraints of imaging technology design, weight limits, positioning limitations; potential respiratory depression related to sedative and analgesia medications combined with cardiac and respiratory system factors unique to the obese patient; and availability of instruments of appropriate length to target the identified lesion.

Screening may reveal that anesthesia may be the most appropriate level of care to maximize safe and successful outcomes. Nursing Leadership and Performance Position Statement Imaging nurses influence patient care in a variety of settings and nursing roles. Imaging nurses are involved in the assessment, care planning, and direct care of patients before, during, and after diagnostic and therapeutic imaging procedures.

Directory Services 3. Distributed Information Service Use Requirements 3. Privatizing POC Information 3. Routing Registry 3. Acceptable Use Policy 3. Autonomous System Originations 3. Collection 3. Publication 3. Description of Data 3. Bulk Publication of Data 3. Other Formats 3. Annual POC Verification 3.

Organizations Covered by this Policy 3. Procedure for Verification 3. Non-Responsive Point of Contact Records 3. Directory Service Records 3. IPv4 4. General Principles 4. Resource Request Size 4. Aggregation 4. Reserved Pool Replenishment 4. Disposition of Resources 4. Precedence for Replenishment 4. ARIN Waitlist 4. Sequencing 4. Fulfillment 4. Principles 4. Purpose 4. Utilization Rate 4.

Slow Start 4. Minimum Allocation 4. Initial Allocation to ISPs 4. Reassigning and Reallocating Address Space to Customers 4. Efficient Utilization 4. VLSM 4. Contiguous Blocks 4. Downstream Customer Adherence 4. Utilization 4. Downstream ISPs 4. Reassignments to Multihomed Downstream Customers 4. Registration 4. Reassignment and Reallocation Information 4. Residential Subscribers 4. Residential Customer Privacy 4. ISP Additional Requests 4. Return Address Space as Agreed 4.

Request Size 4. End-users - Assignments to End-users 4. End-users 4. Minimum Assignment 4. Additional Considerations 4. Non-connected Networks 4. Additional Assignments 4. Utilization Requirements for Additional Assignment 4. Micro-allocation 4. Multiple Discrete Networks 4.

AS Numbers 5. IPv6 6. Introduction 6. Overview 6. Goals 6. Uniqueness 6. Registration 6. Aggregation 6. Conservation 6. Fairness 6. Minimized Overhead 6. Conflict of Goals 6. IPv6 Policy Principles 6. Address Space Not to be Considered Property 6. Routability Not Guaranteed 6. Consideration of IPv4 Infrastructure 6.

Policies for Allocations and Assignments 6. Terminology 6. Initial Allocation to LIRs 6. Size 6. Qualifications 6. Subsequent Allocations to LIRs 6. Subsequent Allocations for Transition 6. Reassignment Information 6. Residential Subscribers 6. Residential Customer Privacy 6. Registration Requested by Recipient 6. Initial Assignment Criteria 6. Initial Assignment Size 6. Standard Sites 6.

Extra-large Sites 6. Subsequent Assignments 6. Consolidation and Return of Separate Assignments 6. Community Network Allocations 6. Qualification Criteria 6. Allocation Size 6. Reassignments by Community Networks 6. Micro-allocations 6. Micro-allocations for Critical Infrastructure 6.

Micro-allocations for Internal Infrastructure 6. IPv6 Multiple Discrete Networks 7. Transfers 8. Principles 8. Mergers, Acquisitions, and Reorganizations 8.

Specified Transfer Recipient Requirements 8. Registration Services Agreement 8. Minimum Transfer Size 8. Initial Block 8. Block Size 8. Efficient Utilization of Previous Blocks 8. Wait List Restrictions 9.

Out of Region Use Global Number Resource Policy Existing Policy Phase Exhaustion Phase Size of the Final IPv4 Allocations Experimental Internet Resource Allocations Documentation of Recognized Experimental Activity Technical Coordination Coordination over Resource Use Resource Allocation Term and Renewal Single Resource Allocation per Experiment Resource Allocation Fees Resource Allocation Guidelines Commercial Use Prohibited Resource Request Appeal or Arbitration Registration The principle of registration guarantees the uniqueness of Internet number resources.

Conservation The principle of conservation guarantees sustainability of the Internet through efficient utilization of unique number resources. Routability The principle of routability guarantees that Internet number resources are managed in such a manner that they may be routed on the Internet in a scalable manner. Stewardship The principle of stewardship guarantees the application of these principles when managing Internet number resources.

Definitions Responsibility for management of number resources is distributed globally in accordance with the following procedures: Global number resource management is performed by the Internet Assigned Numbers Authority IANA. LIRs may further delegate number resources to other LIRs, as well as to other end-user organizations. Internet Registry IR An Internet Registry IR is an organization that is responsible for distributing IP address space to its members or customers and for registering those distributions.

Allocation, Assignment, Reallocation, Reassignment Allocation - Address space delegated to an organization directly by ARIN for the purpose of subsequent distribution by the recipient organization to other parties. End-user An end-user is an organization receiving assignments of IP addresses exclusively for use in its operational networks.

Multihomed An organization is multihomed if it receives full-time connectivity from more than one ISP and has one or more routing prefixes announced by at least two of its upstream ISPs. End Site The term End Site shall mean a single structure or service delivery address, or, in the case of a multi-tenant structure, a single tenant within said structure a single customer location. Community Network A community network is deployed, operated, and governed by its users, for the purpose of providing free or low-cost connectivity to the community it services.

Organizational Information When required, organization Information must include at a minimum: Legal name, street address, city, state, zip code equivalent and at least one valid technical and one valid abuse POC. Residential Customer End-users who are individual persons and not organizations and who receive service at a place of residence for personal use only are considered residential customers. Utilized IPv6 The term utilized shall have the following definitions when applied to IPv6 policies: A provider assignment unit shall be considered fully utilized when it is assigned to an end-site.

Larger blocks shall have their utilization defined by dividing the number of provider assignment units assigned from the containing block by the total number of provider assignment units.

This ratio will often be expressed as a percentage e. Distributed Information Service Use Requirements The minimal requirements for an organization to setup a distributed information service to advertise reassignment and reallocation information are: The distributed information service must be operational 24 hours a day, 7 days a week to both the general public and ARIN staff.

The service is allowed reasonable downtime for server maintenance according to generally accepted community standards.

The distributed information service must allow public access to reassignment and reallocation information. The service may restrict the number of queries allowed per time interval from a host or subnet to defend against DDOS attacks, remote mirroring attempts, and other nefarious acts. The distributed information service must return reassignment and reallocation information for the IP address queried.

The service may allow for privacy protections for customers. The distributed information service may return results for non-IP queries. The distributed information service must respond to a query with the minimal set of attributes per object as defined by ARIN staff. The distributed information service may include optional attributes per object that are defined locally.

The distributed information service must return results that are up-to-date on reassignment and reallocation information. Privatizing POC Information Organizations may designate certain points of contact as private from ARIN Whois, with the exception that, at the minimum, one point of contact must be viewable.

Mirroring is only allowed by other routing registries. The user may only distribute this data using a Whois service unless prior, written permission from ARIN has been obtained. To protect those registered in the ARIN routing registry, ARIN may need to specify additional conditions on access permissions for this data in the future.

The permission to access the data is based on agreement to the conditions stipulated in this document in addition to any others that may be added in the future. Autonomous System Originations. Collection ARIN will collect an optional field in all IPv4 and IPv6 address block transactions allocation and assignment requests, reallocation and reassignment actions, transfer and experimental requests. Description of Data ARIN will produce a collection of the mappings from address blocks to ASes permitted to originate that address block.

Procedure for Verification An annual email notification will be sent to each of the Points of Contact outlined in section 3. Directory Service Records. Reserved Pool Replenishment. Disposition of Resources Any resources allocated from a reserved pool created in Sections 4. Precedence for Replenishment Staff shall return groups of blocks to the pools in scheduled batches staff shall set a reasonable schedule.

Sequencing The position of each qualified request on the waiting list will be determined by the date it was approved. Fulfillment ARIN will fulfill requests on a first-approved basis, subject to the size of each available address block as address blocks become available for distribution.

Utilization Rate Utilization rate of address space is a key factor, among others, in determining address allocation. Slow Start Because the number of available IP addresses on the Internet is limited, many factors must be considered in the determination of address space allocations.

Reassigning and Reallocating Address Space to Customers. Efficient Utilization ISPs are required to apply a utilization efficiency criterion in providing address space to their customers. Downstream Customer Adherence ISPs must require their downstream customers to adhere to the following criteria:.

Utilization A downstream customer requesting address space from an upstream ISP must document a plan to the allocating ISP for their utilization to conform to Section 4. Registration ISPs are required to demonstrate efficient use of IP address space allocations by providing appropriate documentation, including but not limited to assignment histories, showing their efficient use.

Reassignments and Reallocations Visible Within Seven Days All reassignments and reallocations shall be made visible as required in section 4. Residential Subscribers.

In the case of a section 8. ISP Additional Requests. Return Address Space as Agreed Return prior address space designated for return as agreed. End-users - Assignments to End-users. End-users ARIN assigns blocks of IP addresses to end-users who request address space for their internal use in running their own networks, but not for sub-delegation of those addresses outside their organization. Utilization Rate Organizations may qualify for a larger initial allocation by providing appropriate details to verify their month growth projection.

A greater utilization rate may be required based on individual network requirements. Additional Considerations End-users may qualify for address space under other policies such as Micro-allocation [ 4. Additional Assignments. 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: The organization shall be a single entity and not a consortium of smaller independent entities.

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.

The organization must keep detailed records on how it has allocated space to each location, including the date of each allocation. The organization should notify ARIN at the time of the request their desire to apply this policy to their account. 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.

An applicant requesting multiple allocations under this policy to support Multiple Discrete Networks, as defined under Section 4. In order to be assigned an AS Number, each requesting organization must provide ARIN with verification that it has one of the following: A unique routing policy its policy differs from its border gateway peers A multihomed site.

Overview This document describes policies for the allocation and assignment of globally-unique Internet Protocol Version 6 IPv6 address space. Goals IPv6 address space is a public resource that must be managed in a prudent manner with regards to the long-term interests of the internet. Registration Internet address space must be registered in a registry database accessible to appropriate members of the Internet community. Aggregation Wherever possible, address space should be distributed in a hierarchical manner, according to the topology of network infrastructure.

IPv6 address policies should seek to avoid fragmentation of address ranges. Conservation Although IPv6 provides an extremely large pool of address space, address policies should avoid unnecessarily wasteful practices.

Fairness All policies and practices relating to the use of public address space should apply fairly and equitably to all existing and potential members of the Internet community, regardless of their location, nationality, size or any other factor.

Minimized Overhead It is desirable to minimize the overhead associated with obtaining address space. Conflict of Goals The goals described above will often conflict with each other, or with the needs of individual IRs or end users. In IPv6 address policy, the goal of aggregation is considered to be the most important.

IPv6 Policy Principles To address the goals described in the previous section, the policies in this document discuss and follow the basic principles described below. Address Space Not to be Considered Property It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property. Routability Not Guaranteed There is no guarantee that any address allocation or assignment will be globally routable.

Consideration of IPv4 Infrastructure Where an existing IPv4 service provider requests IPv6 space for eventual transition of existing services to IPv6, the number of present IPv4 customers may be used to justify a larger request than would be justified if based solely on the IPv6 infrastructure. Policies for Allocations and Assignments.

Terminology The terms ISP and LIR are used interchangeably in this document and any use of either term shall be construed to include both meanings.

Initial Allocation to LIRs. Size All allocations shall be made on nibble boundaries. In such a case, the prefixes necessary for such a reallocation should be treated as fully utilized in determining the block sizing for the parent LIR. An LIR is not required to design or deploy their network according to this structure.

Are currently multihomed for IPv6 or will immediately become multihomed for IPv6 using a valid assigned global AS number. In either case, they will be making reassignments or reallocations from allocation s under this policy to other organizations.

Provide ARIN a reasonable technical justification indicating why an allocation is necessary. Justification must include the intended purposes for the allocation and describe the network infrastructure the allocation will be used to support. Justification must also include a plan detailing anticipated reassignments and reallocations to other organizations or customers for one, two and five year periods, with a minimum of 50 assignments within 5 years.

The LIR is encouraged, but not required to renumber into the new allocation over time and return any allocations no longer in use. Subsequent Allocations for Transition Subsequent allocations will also be considered for deployments that cannot be accommodated by, nor were accounted for, under the initial allocation. Registration ISPs are required to demonstrate efficient use of IP address space allocations by providing appropriate documentation, including but not limited to reassignment and reallocation histories, showing their efficient use.

Reassignments and Reallocations Visible Within Seven Days All reassignments and reallocations shall be made visible as required in section 6. Existing IPv6 Address Space Holders LIRs which received an allocation under previous policies which is smaller than what they are entitled to under this policy may receive a new initial allocation under this policy.

Examples of justifications for why addresses from an ISP or other LIR may be unsuitable include, but are not limited to: An organization that operates infrastructure critical to life safety or the functioning of society can justify the need for an assignment based on the fact that renumbering would have a broader than expected impact than simply the number of hosts directly involved.

These would include: hospitals, fire fighting, police, emergency response, power or energy distribution, water or waste treatment, traffic management and control, etc. Regardless of the number of hosts directly involved, an organization can justify the need for an assignment if renumbering would affect or more individuals either internal or external to the organization. An organization with a network not connected to the Internet can justify the need for an assignment by documenting a need for guaranteed uniqueness, beyond the statistical uniqueness provided by ULA see RFC An organization with a network not connected to the Internet, such as a VPN overlay network, can justify the need for an assignment if they require authoritative delegation of reverse DNS.

Subsequent Assignments Requests for subsequent assignments with supporting documentation will be evaluated based on the same criteria as an initial assignment under 6. If the organization received an assignment per section 6. When possible subsequent assignments will result it the expansion of an existing assignment by one or more nibble boundaries as justified.

If it is not possible to expand an existing assignment, or to expand it adequately to meet the justified need, then a separate new assignment will be made of the size justified.

Consolidation and Return of Separate Assignments Organizations with multiple separate assignments should consolidate into a single aggregate, if feasible. Community Network Allocations While community networks would normally be considered to be ISP type organizations under existing ARIN criteria, they tend to operate on much tighter budgets and often depend on volunteer labor.

Community networks may also qualify under section 6. Reassignments by Community Networks Similar to other LIRs, Community networks shall make reassignments to end-users in accordance with applicable policies, in particular, but not limited to sections 6. Micro-allocations for Critical Infrastructure ARIN will make micro-allocations to critical infrastructure providers of the Internet, including public exchange points, core DNS service providers e.

Micro-allocations for Internal Infrastructure Organizations that currently hold IPv6 allocations may apply for a micro-allocation for internal infrastructure.

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: The organization shall be a single entity and not a consortium of smaller independent entities.

Requests for additional space: Organization must specify on the application which discrete network s the request applies to Each network will be judged against the existing utilization criteria specified in 6.

Principles Number resources are nontransferable and are not assignable to any other organization unless ARIN has expressly and in writing approved a request for transfer. Mergers, Acquisitions, and Reorganizations ARIN will consider requests for the transfer of number resources in the case of mergers, acquisitions, and reorganizations under the following conditions: The current registrant must not be involved in any dispute as to the status of the resources to be transferred. The new entity must sign an RSA covering all resources to be transferred.

The resources to be transferred will be subject to ARIN policies. The minimum transfer size is the smaller of the original allocation size or the applicable minimum allocation size in current policy. The Internet number resources being transferred as part of an 8. AND one or more of the following: The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant.

OR The recipient must show that they have acquired the entire entity which is the current registrant. Conditions on source of the transfer: The source entity must be the current registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources.

The source entity must not have received a transfer, allocation, or assignment of IPv4 number resources from ARIN for the 12 months prior to the approval of a transfer request. Conditions on recipient of the transfer: The recipients must meet the transfer requirements as defined in section 8.

The resources transferred will be subject to current ARIN policies. If applicable the recipient will be removed from the ARIN Waitlist and will not be allowed to reapply under section 4. ARIN Waitlist for a period of 90 days. Conditions on source of the transfer: The source entity must be the current rights holder of the IPv4 address resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.

Conditions on recipient of the transfer: The conditions on a recipient outside of the ARIN region will be defined by the policies of the receiving RIR. Specified recipients within the ARIN region must meet the transfer requirements as defined in section 8.

Specified Transfer Recipient Requirements. Registration Services Agreement The receiving entity must sign an RSA covering all resources to be transferred unless that entity has a current within the last two versions RSA on file.

An organization may qualify via 8. Wait List Restrictions Any organization which is on the wait list and submits a request to be the source of a transfer under any provision in section 8 will be removed from the wait list. Methods that entities may consider using, including cumulatively, to prove that they are carrying on business in the ARIN region in a meaningful manner include: Demonstrating a physical presence in the ARIN region through a bricks and mortar location that is actually used for the purposes of conducting business in the ARIN region in a meaningful manner.

That is to say, the location is not merely a registered office that serves no other business purpose. Demonstrating that the entity has staff in the ARIN region. The greater the number of staff, the stronger this connecting factor is.

Demonstrating that the entity holds assets in the ARIN region. The greater the asset value, the stronger this connecting factor is. Demonstrating that the entity provides services to and solicits sales from residents of the ARIN region. Demonstrating that the entity holds periodic meetings in the ARIN region. Demonstrating that the entity raises investment capital from investors in the ARIN region. Demonstrating that the entity has a registered corporation in the ARIN region, although this factor on its own shall not be sufficient.

Global Number Resource Policy. The IANA will allow for the RIRs to apply their own respective chosen allocation and reservation strategies in order to ensure the efficiency and efficacy of their work. B Submit a clear and detailed justification of the above mentioned projection Item A. Submit a clear and detailed justification of the above mentioned projection Item A.

The process for the allocation of the remaining IPv4 space is divided in two consecutive phases:. It will contain: a.