Changes to Anycast Assignment Request Form

delete: <strong> Please note: all email-based request forms have been archived on the website and are available through the LIR Portal. You can find an announcement about this delete: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/ncc-services-wg/2014-October/002890.html" target="_self" title=""> here delete: </a> . delete: </strong> delete: </p> delete: <p> To request resources from the RIPE NCC, members should now use the request forms in the delete: <a class="external-link" href="https://lirportal.ripe.net/" target="_self" title=""> LIR Portal delete: </a> . delete: </p> delete: <p> The delete: <a class="external-link" href="https://www.ripe.net/data-tools/developer-documentation/resource-request-api" target="_self" title=""> Resource Request API delete: </a> and accompanying documentation is available for members with workflows that prevent them from using the LIR Portal request forms. delete: </p> delete: <p> delete: </p> delete: <p> The RIPE NCC is now allocating IPv4 address space to its members (LIRs) from the last /8 (185/8) that was allocated to the RIPE NCC by IANA. IPv4 addresses from this /8 are allocated according to section 5.1 of “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”. No more IPv4 Anycast can be assigned. delete: </p> delete: <p> delete: <img src="./resolveuid/1f075ef0-1420-4b37-95a9-b77d6721138b" alt="" class="image-inline" title="" data-val="1f075ef0-1420-4b37-95a9-b77d6721138b" data-linktype="image" /> delete: </p> delete: <pre> delete: <br /> % Anycast Assignment Request Form delete: <br /> delete: <br /> % RIPE NCC members (LIRs) can use this form delete: <br /> % to request an anycast assignment. Please see delete: <br /> % Supporting Notes for the Anycast Assignment Request Form delete: <br /> % for instructions on how to complete this form. delete: <br /> % delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/anycast-request-support.html"> http://www.ripe.net/ripe/docs/anycast-request-support.html delete: </a> delete: <br /> % delete: <br /> % Please note that the End User should have a signed "End User delete: <br /> % Assignment Agreement" with either the sponsoring LIR or the RIPE NCC. delete: <br /> delete: <br /> #[GENERAL INFORMATION]# delete: <br /> % delete: <br /> % Please add your RegID. delete: <br /> delete: <br /> request-type: anycast-assignment delete: <br /> form-version: 1.1 delete: <br /> x-ncc-regid: delete: <br /> delete: <br /> #[ADDRESS SPACE USER]# delete: <br /> % delete: <br /> % Is this request being sent by a sponsoring LIR on behalf of an delete: <br /> % End User? (Yes/No) delete: <br /> delete: <br /> end-user-of-sponsoring-lir: delete: <br /> delete: <br /> % If yes, please confirm that the "End User Assignment Agreement" delete: <br /> % contains all of the elements listed in paragraph 2.0 of delete: <br /> % "Contractual Requirements for Provider Independent Resource Holders delete: <br /> % in the RIPE NCC Service Region".(Yes/No) delete: <br /> delete: <br /> confirmation: delete: <br /> delete: <br /> % delete: <br /> % Which TLD operator will use the requested address space? delete: <br /> delete: <br /> legal-organisation-name: delete: <br /> tld(s) or ENUM delegation(s): delete: <br /> organisation-location: delete: <br /> website-if-available: delete: <br /> delete: <br /> % Does this End User already have address space in use for delete: <br /> % anycast? (Yes/No) delete: <br /> delete: <br /> space-available: delete: <br /> delete: <br /> % Will the End User return any address space? delete: <br /> delete: <br /> address-space-returned: delete: <br /> delete: <br /> #[INITIAL INFORMATION]# delete: <br /> delete: <br /> % Does the End User accept the policies on anycast assignments? delete: <br /> % delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv4-policies.html"> http://www.ripe.net/ripe/docs/ipv4-policies.html delete: </a> delete: <br /> % delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/ipv6policy.html"> http://www.ripe.net/ripe/docs/ipv6policy.html delete: </a> (Yes/No) delete: <br /> delete: <br /> confirmation: delete: <br /> delete: <br /> % Is the End User requesting an IPv4 assignment, an IPv6 delete: <br /> % assignment, or both? (IPv4/IPv6/Both) delete: <br /> delete: <br /> ip-version: delete: <br /> delete: <br /> % If the End User is requesting an IPv4 assignment, will the TLD delete: <br /> % nameserver set apply anycasting as described in BCP126/RFC4786? delete: <br /> % delete: <a class="external-link" href="http://www.ietf.org/rfc/rfc4786.txt"> http://www.ietf.org/rfc/rfc4786.txt delete: </a> (Yes/No) delete: <br /> delete: <br /> rfc4786: delete: <br /> delete: <br /> #[ANYCAST NODE PLAN]# delete: <br /> % delete: <br /> % Which anycast nodes will be used? delete: <br /> delete: <br /> Node Name Peers Location delete: <br /> delete: <br /> node: delete: <br /> node: delete: <br /> node: delete: <br /> delete: <br /> number-of-nodes: delete: <br /> delete: <br /> #[NETWORK DESCRIPTION]# delete: <br /> % delete: <br /> % Please add more information if you think it will help us understand delete: <br /> % this request. delete: <br /> delete: <br /> <add more information> delete: <br /> delete: <br /> delete: <br /> #[SUPPORTING DOCUMENTATION]# delete: <br /> % delete: <br /> % If this request being sent by a sponsoring LIR on behalf of an delete: <br /> % End User, please attach a copy of the signed "End User delete: <br /> % Assignment Agreement" and the company registration papers of the delete: <br /> % End User. delete: <br /> % You can also attach a network diagram or other supporting documentation. delete: <br /> % delete: <br /> % Have you attached any files/documents to this request? (Yes/No) delete: <br /> delete: <br /> file-attached: delete: <br /> delete: <br /> delete: <br /> #[DATABASE TEMPLATE(S)]# delete: <br /> % delete: <br /> % IPv4 delete: <br /> % Please complete all of the fields below. delete: <br /> delete: <br /> inetnum: <leave empty> delete: <br /> netname: <add netname> delete: <br /> descr: <add End User organisation name> delete: <br /> country: <add country code> delete: <br /> org: <add org-ID> delete: <br /> admin-c: <add nic-handle of administrative contact> delete: <br /> tech-c: <add nic-handle of technical contact> delete: <br /> status: ASSIGNED ANYCAST delete: <br /> mnt-by: RIPE-NCC-END-MNT delete: <br /> mnt-lower: RIPE-NCC-END-MNT delete: <br /> mnt-by: <add mntner name> delete: <br /> mnt-routes: <add mntner name> delete: <br /> mnt-domains: <add mntner name> delete: <br /> changed: [email protected] delete: <br /> source: RIPE delete: <br /> delete: <br /> % IPv6 delete: <br /> % Please complete all of the fields below. delete: <br /> delete: <br /> inet6num: <leave empty> delete: <br /> netname: <add netname> delete: <br /> descr: <add End User organisation name> delete: <br /> country: <add country code> delete: <br /> org: <add org-ID> delete: <br /> admin-c: <add nic-handle of administrative contact> delete: <br /> tech-c: <add nic-handle of technical contact> delete: <br /> status: ASSIGNED ANYCAST delete: <br /> mnt-by: RIPE-NCC-END-MNT delete: <br /> mnt-lower: RIPE-NCC-END-MNT delete: <br /> mnt-by: <add mntner name> delete: <br /> mnt-routes: <add mntner name> delete: <br /> mnt-domains: <add mntner name> delete: <br /> changed: [email protected] delete: <br /> source: RIPE delete: <br /> delete: <br /> #[END of REQUEST]# delete: </pre> delete: <p> delete: <img src="./resolveuid/93c82862-6241-4309-8d0f-9d4355eeded7" alt="" class="image-inline" title="" data-val="93c82862-6241-4309-8d0f-9d4355eeded7" data-linktype="image" /> delete: </p>