Changes to Temporary Internet Number Assignment Policies
| Legend | (+) Added | (-) Deleted |
|---|---|---|
| Changed | Tag Added | Tag Deleted |
insert: <b> Summary of Proposal: insert: </b>
This proposal expands the RIPE NCC's ability to assign number resources for temporary purposes and allows the RIPE NCC to reserve pools of IP addresses and Autonomous System (AS) Numbers, which can be used by the RIPE NCC to make temporary direct assignments to End Users.
Key to this proposal is that all temporary resources assigned under this policy proposal are assigned on a strictly temporary basis, ensuring that they can be quickly re-assigned to other End Users after the assignment period expires.
The proposal is not intended to stretch the lifetime of the unallocated pool for assignments or allocations of indefinite duration.
The proposal is independent of other proposals to reserve address space for transition purposes and/or new entrants. It can be implemented independently of these.
delete: <div class="bold"> delete: <h2> Policy Text: delete: </h2> delete: </div> delete: <p> As well as producing a new RIPE Document (see delete: <span class="anchor-link"> Draft Documentation Tab delete: </span> ), this policy proposal would result in changes to three existing RIPE Documents: delete: </p> delete: <table class="grid listing"> delete: <tbody> delete: <tr> delete: <th> delete: </th> delete: </tr> delete: </tbody> delete: </table> delete: <em> Following text is to be removed from the RIPE Policy document: delete: <a class="internal-link" href="resolveuid/50e8a78e6763314cc01495afdf1070be" data-val="50e8a78e6763314cc01495afdf1070be" data-linktype="internal"> Autonomous System (AS) Number Assignment Policies and Procedures delete: </a> . delete: </em> delete: <br /> delete: <h3> 3.0 Assignments for Internet Experiments delete: </h3> delete: <p> Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. delete: </p> delete: <p> The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. delete: </p> delete: <h3> 3.1 Defining the Experiment delete: </h3> delete: <p> The experiment for which the organisation receives numbering resources must be documented. This may be in the form of a current IETF Experimental RFC (see delete: <a href="ftp://ftp.ripe.net/rfc/rfc2026.txt"> RFC 2026 delete: </a> , Section 4.2.1 or an “experiment proposal” detailing the resources required and the activities to be carried out. A single AS Number will be assigned. If more than one AS Number is required for the experiment, this should be indicated and explained in the request. delete: </p> delete: <p> The experiment proposal must be made public (e.g. published on a website), upon registration of the resources by the RIPE NCC. When the experiment is concluded the results must be published free of charge and free from disclosure constraints. delete: </p> delete: <h3> 3.2 Non-commercial Basis delete: </h3> delete: <p> Resources issued for an experiment must not be used for commercial purposes. delete: </p> delete: <h3> 3.3 Period of the Resource Registration delete: </h3> delete: <p> The resources will be issued on a temporary basis for a period of one year. Renewal of the resources' registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. delete: </p> delete: <p> The resources issued cannot be used for a commercial service following the conclusion of the experiment. At the end of the assignment period the AS Number must be returned to the RIPE NCC. delete: </p> delete: <p> delete: </p> delete: <table class="listing grid"> delete: <tbody> delete: <tr> delete: <th> delete: <em> Following text is to be removed from the RIPE Policy document: delete: <a class="internal-link" href="resolveuid/e170b121e07ecd5a96edc8b6211dbac1" data-val="e170b121e07ecd5a96edc8b6211dbac1" data-linktype="internal"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region delete: </a> delete: </em> delete: </th> delete: </tr> delete: </tbody> delete: </table> delete: <p> delete: </p> delete: <h3> delete: <strong> 8.0 Assignments for Internetworking Experiments delete: </strong> delete: </h3> delete: <p> Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. delete: </p> delete: <p> An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC ( delete: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt delete: </a> Sec. 4.2.1) or an "experiment proposal" detailing the resources required and the activities to be carried out. delete: </p> delete: <p> The assignment size will be equal to the existing minimum allocation size on the date the request is received. Where the experiment requires a variation to this rule it should be noted in the resource request. delete: </p> delete: <p> The experiment proposal must be made public (e.g. published on website), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints. delete: </p> delete: <p> Resources issued must not be used for commercial purposes during or following the conclusion of the experiment. delete: </p> delete: <p> The resources will be issued on a temporary basis for a period of one year. Renewal of the resource's registration is possible on receipt of a new request that details continuation of the experiment during the extended period. delete: </p> delete: <p> The RIPE NCC will register the resources issued in the RIPE Database. delete: </p> delete: <p> The request must be made by an LIR using the appropriate request form. Details of the experiment should be noted in the form delete: <a class="internal-link" href="resolveuid/f79524cd78d2aab9624bb77fcf4dd9e1" data-val="f79524cd78d2aab9624bb77fcf4dd9e1" data-linktype="internal"> found online delete: </a> . delete: <a href="http://www.ripe.net/ripe/docs/internet-registries.html#request"> delete: <br /> delete: </a> delete: </p> delete: <table class="plain"> delete: <tbody> delete: <tr> delete: <th> delete: <em> Following text is to be removed from the RIPE Policy document: delete: <br /> delete: <a class="internal-link" href="resolveuid/eefd779fcf78b266160131b9d78af2f3" data-val="eefd779fcf78b266160131b9d78af2f3" data-linktype="internal"> IPv6 Address Allocation and Assignment Policy delete: </a> delete: </em> delete: </th> delete: </tr> delete: </tbody> delete: </table> delete: <p> delete: </p> delete: <h3> delete: <strong> 6.0 Assignments for Internet Experiments delete: </strong> delete: </h3> delete: <p> Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. delete: </p> delete: <h3> delete: <strong> 6.1 Defining the experiment delete: </strong> delete: </h3> delete: <p> An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC ( delete: <a href="http://www.ietf.org/rfc/rfc2026.txt"> [2026] see Sec. 4.2.1 delete: </a> ) or an "experiment proposal" detailing the resources required and the activities to be carried out. delete: </p> delete: <h3> delete: <a name="-b-----publication--b-"> delete: </a> delete: <strong> 6.2 Publication delete: </strong> delete: </h3> delete: <p> The experiment proposal must be made public (e.g. published on web site), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints. delete: </p> delete: <h3> delete: <strong> 6.3 Non-commercial basis delete: </strong> delete: </h3> delete: <p> Resources issued for an experiment must not be used for commercial purposes. delete: </p> delete: <h3> delete: <strong> 6.4 Period of the Temporary Resource Registration delete: </strong> delete: </h3> delete: <p> The resources will be issued on a temporary basis for a period of one year. Renewal of the resource's registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. delete: </p> delete: <p> The resources issued cannot be used for a commercial service following the conclusion of the experiment. delete: </p> delete: <h3> delete: <strong> 6.5 Registration delete: </strong> delete: </h3> delete: <p> The RIPE NCC will register the resources issued in the RIPE Whois Database. delete: </p> delete: <h3> delete: <strong> 6.6 Making the request delete: </strong> delete: </h3> delete: <p> The request must be made by a Local Internet Registry (LIR) using the appropriate request form for the resource delete: <a class="internal-link" href="resolveuid/f79524cd78d2aab9624bb77fcf4dd9e1" data-val="f79524cd78d2aab9624bb77fcf4dd9e1" data-linktype="internal"> found online delete: </a> . delete: </p> delete: <table class="listing grid"> delete: <tbody> delete: <tr> delete: <th> delete: </th> delete: </tr> delete: </tbody> delete: </table> delete: <em> Following text is to be added in a new RIPE document: delete: </em> delete: <p> delete: <strong> Temporary Internet Number Assignment Policies delete: </strong> delete: </p>Abstract delete: </h2> delete: <p> This document outlines policies for temporary direct assignments of IPv4/IPv6 address space and Autonomous System (AS) Numbers in the RIPE NCC service region. delete: </p> delete: <h2> Contents delete: </h2> delete: <p> 1.0 Introduction delete: <br /> 2.0 Internet Registry Number Resource Pool Reservation delete: <br /> 2.1 RIPE NCC Assignment Procedures delete: <br /> 3.0 End User Term and Limitations delete: <br /> 3.1 Assignment Time Limits delete: <br /> 3.2 Realistic Expectations delete: <br /> 3.3 IPv4 Address Utilisation Rate delete: <br /> 3.4 Compliance with Other RIPE NCC Assignment Policies delete: </p> delete: <h2> delete: <a id="10" name="10"> delete: </a> 1.0 Introduction delete: </h2> delete: <p> This policy allows the RIPE NCC to assign number resources for temporary direct assignment purposes and, for this purpose, to reserve pools of IPv4/IPv6 addresses, AS Numbers and any other numbers for which it acts as Regional Internet Registry (RIR). delete: </p> delete: <h2> delete: <a name="2"> delete: </a> 2.0 Internet Registry Number Resource Pool Reservation delete: </h2> delete: <p> The RIPE NCC is authorised to reserve pools of IPv4 addresses, IPv6 addresses, 16-bit AS Numbers and 32-bit AS Numbers for the purpose of direct assignment under this policy. delete: </p> delete: <h3> 2.1 RIPE NCC Assignment Procedures delete: </h3> delete: <p> The RIPE NCC may assign number resources to End Users on a temporary deployment basis for a specific time-limited purpose. Examples of specific purposes include, but are not limited to, academic research and experimental purposes, conferences and other types of events which require network connectivity for short periods of time, and other strictly time-limited projects such as deployment tests for new Internet services and technologies. delete: </p> delete: <p> Resources issued for temporary assignments must not be used for purposes other than those specified in the application, and they may be returned to the RIPE NCC at any time during the approved assignment period. The number resources will be automatically de-registered and returned to the appropriate reservation pool at the end of the approved assignment period. delete: </p> delete: <p> The RIPE NCC will register the issued number resources in the RIPE Database for the duration of the assignment and will note the start and end dates of the assignment period for each database object. delete: </p> delete: <h2> delete: <a id="30" name="30"> delete: </a> 3.0 End User Terms and Limitations delete: </h2> delete: <h3> 3.1 Assignment Time Limits delete: </h3> delete: <p> Depending on the specified purpose of the assignment request, different upper time limits may apply. For conferences and other events of short, fixed duration, the maximum assignment time period will be seven calendar days more than the scheduled length of the conference/event but no longer than one month in any case. delete: </p> delete: <p> For longer term projects and research purposes, the number resources may be issued on a temporary basis for a period of up to six calendar months, or two calendar weeks longer than the expected life of the project/research/experiment, whichever is shorter. delete: </p> delete: <p> In the case where an End User requires number resources for research purposes, and where the research project details are made public upon registration of the number resources by the RIPE NCC, and where the End User commits to making public the results of their research project free of charge and free from disclosure constraints, then the requested number resources may be issued for a period of up to one calendar year. delete: </p> delete: <p> At the RIPE NCC’s discretion renewal of the registration of the resources may be possible in exceptional circumstances on receipt of a new request that details continuation of the End User's requirements during the extended period. Should this request be denied by the RIPE NCC, an appeal may be made using the RIPE NCC Conflict Arbitration Procedure. delete: </p> delete: <h3> 3.2 Realistic Expectations delete: </h3> delete: <p> Assignments may only be based on realistic expectations recorded on the request form. The RIPE NCC may require the End User to provide documentation or other evidence supporting the End User's assignment request. delete: </p> delete: <h3> 3.3 IPv4 Address Utilisation Rates delete: </h3> delete: <p> For short-lived assignments of less than one month, the immediate IPv4 address utilisation rate should be no less than 50% of the total temporary assignment. For all other temporary assignments, immediate IPv4 address utilisation should be no less than 25%, and utilisation after one month should be no less than 50%. delete: </p> delete: <h3> 3.4 Compliance with Other RIPE NCC Assignment Policies delete: </h3> delete: <p> In all respects not covered by this document, temporary assignment policies are subject to all other RIPE NCC policies regarding standard direct assignment of number resources. delete: </p> delete: <h3 class="bold"> delete: </h3> delete: <h2> insert: <b> Rationale: insert: </b>
The RIPE NCC currently has the ability to assign IP addresses on a temporary basis for experimental purposes. This policy proposal creates a long-term basis for opening up temporary number resource assignments to a wider variety of End Users.
Furthermore, it is expected that little or no resources will be available for this purpose in the RIR IPv4 address space or 16-bit AS Number pools unless a reservation is made.
Most number resource assignments are made on the basis of indefinite duration, which means that unless the address space is returned to the RIPE NCC, they can only provide value to one End User body or organisation. However, temporary resource assignments can be made repeatedly to any number of different End Users, ensuring that such a pool would provide permanent value to the RIPE community.
delete: <h3> delete: <strong> insert: <p>insert: <b> a. Arguments supporting the proposal delete: </strong> delete: </h3> insert: </b> insert: </p>
Temporary resource assignments provide a useful facility for End Users who require a specific amount of address space and/or AS Number on a strictly time-limited basis. As the number resource can be re-used again and again, the amount of address space or number of AS Numbers that would need to be set aside for temporary assignment pools would be small when measured against the current number resource run-rates. On this basis, creating an address pool for this purpose would have a negligible effect on the final RIPE NCC IANA-supplied IPv4 address pool depletion date and the 16-bit AS Number depletion date.
delete: <h3> delete: <strong> insert: </div>insert: <b> b. Arguments opposing the proposal delete: </strong> delete: </h3> Opposing the Proposal insert: </b> insert: </p>
It could be argued that if there were resources consistently available in a temporary assignment pool, that these unassigned resources could be better used by assigning or allocating them to an End User or LIR on an indefinite basis, and that by not assigning them, LIRs and other End Users would be disadvantaged or discriminated against.
If a temporary assignment was used at any time for malicious ends, the resources used for this purpose could end up on blacklists and the value of the resources would be significantly diminished for future End Users.
insert: <b> Policy Text: insert: </b> insert: </h2>
a. Current policy text insert: </h2>
insert: <p>insert: <i> [Following text is to be removed from the RIPE Policy delete: </a> delete: </li> delete: <li> delete: <a class="internal-link" href="resolveuid/b3fd3068102af689f904af884aa541b4" data-val="b3fd3068102af689f904af884aa541b4" data-linktype="internal"> DRAFT: Document [ insert: <a class="internal-link" href="resolveuid/d0f8d5d575b44c0db21ae4843ef41777" data-val="d0f8d5d575b44c0db21ae4843ef41777" data-linktype="internal"> Autonomous System (AS) Number Assignment Policies and Procedures delete: </li> delete: <li> delete: <a class="internal-link" href="resolveuid/73f1ee680b7504525934cff3b111467e" data-val="73f1ee680b7504525934cff3b111467e" data-linktype="internal"> DRAFT: Temporary ], if the proposal reaches consensus. This would result in a new policy document "Temporary Internet Number Assignment Policies"] insert: </i> insert: </p>
insert: <p>insert: <b> 1.1 Assignments for Internetworking Experiments insert: </b> insert: </p>
insert: <p>Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. insert: </p>
insert: <p>The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. insert: </p>
insert: <p>insert: <b> 1.2 Defining the Experiment insert: </b> insert: </p>
insert: <p>An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC (see RFC 2026, Sec. 4.2.1) or an “experiment proposal” detailing the resources required and the activities to be carried out. insert: </p>
insert: <p>A single AS Number will be assigned. Where the experiment requires a variation to this rule it should be noted in the resource request forms sent to the RIPE NCC. insert: </p>
insert: <p>insert: <b> 1.3 Publication insert: </b> insert: </p>
insert: <p>The experiment proposal must be made public (e.g. published on web site), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints. insert: </p>
insert: <p>insert: <b> 1.4 Non-commercial Basis insert: </b> insert: </p>
insert: <p>Resources issued for an experiment must not be used for commercial purposes. insert: </p>
insert: <p>insert: <b> 1.5 Period of the Temporary Resource Registration insert: </b> insert: </p>
insert: <p>The resources will be issued on a temporary basis for a period of one year. Renewal of the resource’s registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. insert: </p>
insert: <p>The resources issued cannot be used for a commercial service following the conclusion of the experiment. insert: </p>
insert: <p>... insert: </p>
insert: <p>insert: <b> 1.7 Requesting an AS Number insert: </b> insert: </p>
insert: <p>Regardless of whether the AS Number is required as an experimental assignment or otherwise, the RIPE NCC assigns AS Numbers for Autonomous Systems located in the RIPE NCC service region. insert: </p>
insert: <p>... insert: </p>
insert: <p>insert: <i> [Following text is to be removed from the RIPE Policy Document [ insert: <a class="internal-link" href="resolveuid/e170b121e07ecd5a96edc8b6211dbac1" data-val="e170b121e07ecd5a96edc8b6211dbac1" data-linktype="internal"> IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region delete: </li> delete: </ul> ], if the proposal reaches consensus. This would result in a new policy document "Temporary Internet Number Assignment Policies"] insert: </i> insert: </p>
insert: <p>insert: <b> 8.0 Assignments for Internetworking Experiments insert: </b> insert: </p>
insert: <p>Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. insert: </p>
insert: <p>An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC ( insert: <a href="http://www.ietf.org/rfc/rfc2026.txt"> http://www.ietf.org/rfc/rfc2026.txt insert: </a> Sec. 4.2.1) or an “experiment proposal” detailing the resources required and the activities to be carried out. insert: </p>
insert: <p>The assignment size will be equal to the existing minimum allocation size on the date the request is received. Where the experiment requires a variation to this rule it should be noted in the resource request. insert: </p>
insert: <p>The experiment proposal must be made public (e.g. published on website), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints. insert: </p>
insert: <p>Resources issued must not be used for commercial purposes during or following the conclusion of the experiment. insert: </p>
insert: <p>The resources will be issued on a temporary basis for a period of one year. Renewal of the resource’s registration is possible on receipt of a new request that details continuation of the experiment during the extended period. insert: </p>
insert: <p>The RIPE NCC will register the resources issued in the RIPE Database. insert: </p>
insert: <p>The request must be made by an LIR using the appropriate request form. Details of the experiment should be noted in the insert: <a class="internal-link" href="resolveuid/f79524cd78d2aab9624bb77fcf4dd9e1" data-val="f79524cd78d2aab9624bb77fcf4dd9e1" data-linktype="internal"> form found online insert: </a> . insert: </p>
insert: <p>insert: <i> [Following text is to be removed from the RIPE Policy Document [ insert: <a class="internal-link" href="resolveuid/eefd779fcf78b266160131b9d78af2f3" data-val="eefd779fcf78b266160131b9d78af2f3" data-linktype="internal"> IPv6 Address Allocation and Assignment Policy insert: </a> ], if the proposal reaches consensus. This would result in a new policy document "Temporary Internet Number Assignment Policies"] insert: </i> insert: </p>
insert: <p>insert: <b> 6.0 Assignments for Internet Experiments insert: </b> insert: </p>
insert: <p>Organisations often require deployment tests for new Internet services and technologies. These require numbering resources for the duration of the test. insert: </p>
insert: <p>The policy goal of resource conservation is of reduced importance when resources are issued on a temporary basis. insert: </p>
insert: <p>insert: <b> 6.1 Defining the experiment insert: </b> insert: </p>
insert: <p>An organisation receiving numbering resources must document the experiment. This may be in the form of a current IETF Experimental RFC ( insert: <a href="http://www.ietf.org/rfc/rfc2026.txt"> [2026] see Sec. 4.2.1 insert: </a> ) or an “experiment proposal” detailing the resources required and the activities to be carried out. insert: </p>
insert: <p>insert: <b> 6.2 Publication insert: </b> insert: </p>
insert: <p>The experiment proposal must be made public (e.g. published on web site), upon registration of the resources by the RIPE NCC. Following the conclusion of the experiment the results must be published free of charge and free from disclosure constraints. insert: </p>
insert: <p>insert: <b> 6.3 Non-commercial basis insert: </b> insert: </p>
insert: <p>Resources issued for an experiment must not be used for commercial purposes. insert: </p>
insert: <p>insert: <b> 6.4 Period of the Temporary Resource Registration insert: </b> insert: </p>
insert: <p>The resources will be issued on a temporary basis for a period of one year. Renewal of the resource’s registration is possible on receipt of a new request that details any continuation of the experiment during the extended period. insert: </p>
insert: <p>The resources issued cannot be used for a commercial service following the conclusion of the experiment. insert: </p>
insert: <p>insert: <b> 6.5 Registration insert: </b> insert: </p>
insert: <p>The RIPE NCC will register the resources issued in the RIPE Whois Database. insert: </p>
insert: <p>insert: <b> 6.6 Making the request insert: </b> insert: </p>
insert: <p>The request must be made by a Local Internet Registry (LIR) using the appropriate request form for the resource insert: <a class="internal-link" href="resolveuid/f79524cd78d2aab9624bb77fcf4dd9e1" data-val="f79524cd78d2aab9624bb77fcf4dd9e1" data-linktype="internal"> found online insert: </a> . insert: </p>
insert: <h2>b. New policy text insert: </h2>
insert: <p>insert: <b> Abstract insert: </b> insert: </p>
insert: <p>This document outlines policies for temporary direct assignments of IPv4/IPv6 address space and Autonomous System (AS) Numbers in the RIPE NCC service region. insert: </p>
insert: <p>insert: <b> 1. Introduction insert: </b> insert: </p>
insert: <p>This policy allows the RIPE NCC to assign number resources for temporary direct assignment purposes and, for this purpose, to reserve pools of IPv4/IPv6 addresses, AS Numbers and any other numbers for which it acts as Regional Internet Registry (RIR). insert: </p>
insert: <p>insert: <b> 2. Internet Registry Number Resource Pool Reservation insert: </b> insert: </p>
insert: <p>The RIPE NCC is authorised to reserve pools of IPv4 addresses, IPv6 addresses, 16-bit AS Numbers and 32-bit AS Numbers for the purpose of direct assignment under this policy. insert: </p>
insert: <p>insert: <b> 2.1 RIPE NCC Assignment Procedures insert: </b> insert: </p>
insert: <p> The RIPE NCC may assign number resources to End Users on a temporary deployment basis for a specific time-limited purpose. Examples of specific purposes include, but are not limited to, academic research and experimental purposes, conferences and other types of events which require network connectivity for short periods of time, and other strictly time-limited projects such as deployment tests for new Internet services and technologies. insert: <br />
insert: <br />
Resources issued for temporary assignments must not be used for purposes other than those specified in the application, and they may be returned to the RIPE NCC at any time during the approved assignment period. The number resources will be automatically de-registered and returned to the appropriate reservation pool at the end of the approved assignment period. insert: <br />
insert: <br />
The RIPE NCC will register the issued number resources in the RIPE Database for the duration of the assignment and will note the start and end dates of the assignment period for each database object. insert: </p>
insert: <b> 3.0 End User Terms and Limitations insert: </b> insert: </p>
insert: <p> insert: <b> 3.1 Assignment Time Limits insert: </b> insert: <br />
insert: <br />
Depending on the specified purpose of the assignment request, different upper time limits may apply. For conferences and other events of short, fixed duration, the maximum assignment time period will be seven calendar days more than the scheduled length of the conference/event but no longer than one month in any case. insert: </p>
For longer term projects and research purposes, the number resources may be issued on a temporary basis for a period of up to six calendar months, or two calendar weeks longer than the expected life of the project/research/experiment, whichever is shorter. insert: </p>
insert: <p>At the RIPE NCC’s discretion, but subject to the RIPE NCC Conflict Arbitration Procedure, renewal of the registration of the resources may be possible in exceptional circumstances on receipt of a new request that details continuation of the End User's requirements during the extended period. insert: </p>
insert: <p>insert: <b> 3.2 Realistic Expectations insert: </b> insert: </p>
insert: <p>Assignments may only be based on realistic expectations recorded on the request form. The RIPE NCC may require the End User to provide documentation or other evidence supporting the End User's assignment request. insert: </p>
insert: <p>insert: <b> 3.3 IPv4 Address Utilisation Rates insert: </b> insert: </p>
insert: <p>For short-lived assignments of less than one month, the immediate IPv4 address utilisation rate should be no less than 50% of the total temporary assignment. For all other temporary assignments, immediate IPv4 address utilisation should be no less than 25%, and utilisation after one month should be no less than 50%. insert: </p>
insert: <p>insert: <b> 3.4 Compliance with Other RIPE NCC Assignment Policies insert: </b> insert: </p>
insert: <p>In all respects not covered by this document, temporary assignment policies are subject to all other RIPE NCC policies regarding standard direct assignment of number resources. insert: </p>
insert: </div>