You are here: Home > Publications > RIPE Document Store > Supporting Notes for the Anycast Assignment Request Form

Changes to Supporting Notes for the Anycast Assignment Request Form

Legend	(+) Added	(-) Deleted
Changed	Tag Added	Tag Deleted

ripe-474: 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.6 of “IPv4 Address Allocation and Assignment Policies ripe-459: Supporting Notes for the RIPE NCC Service Region”. No more IPv4 Anycast can be assigned. Assignment Request Form

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.6 of “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”. No more IPv4 Anycast can be assigned. delete:  delete:  This document contains instructions for LIRs on how to complete the " delete: <a data-val="67eaa74d1e500f57512417ed9bf6dda1" href="resolveuid/67eaa74d1e500f57512417ed9bf6dda1" data-linktype="internal" class="internal-link"> Anycast Assignment Request Form delete: </a> ". delete:   delete:   The instructions are based on the " delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policy for the RIPE Region delete: </a> ", the " delete: <a href="http://www.ripe.net/ripe/docs/ipv6policy.html"> IPv6 Address Allocation and Assignment Policy delete: </a> " and also " delete: <a href="http://www.ietf.org/rfc/rfc4786.txt"> RFC 4786 delete: </a> ". delete:  delete:  delete:  delete: <hr /> delete: <ul> delete: <li> delete: <a href="#general"> General Information delete: </a> delete: </li> delete: <li> delete: <a href="#user"> Address Space User delete: </a> delete: </li> delete: <li> delete: <a href="#information"> Initial Information delete: </a> delete: </li> delete: <li> delete: <a href="#plan"> Anycast Node Plan delete: </a> delete: </li> delete: <li> delete: <a href="#description"> Network Description delete: </a> delete: </li> delete: <li> delete: <a href="#documentation"> Supporting Documentation delete: </a> delete: </li> delete: <li> delete: <a href="#database"> Database Template(s) delete: </a> delete: </li> delete: <li> delete: <a href="#end"> End of Request delete: </a> delete: </li> delete: </ul> delete: <hr /> delete: <h2> delete: <a name="general"> delete: </a> General Information delete: </h2> delete: <pre> #[GENERAL INFORMATION]# delete:   % delete:   % Please add your RegID. delete:   delete:   request-type: anycast-assignment delete:   form-version: 1.0 delete:   x-ncc-regid: delete:  nl.bluelight delete:  delete: </pre> delete:  Please do not change the value of the " delete:  request-type: delete:  " and " delete:  form-version: delete:  " fields. delete:  delete:  Enter your Registry Identifier (RegID) in the " delete:  x-ncc-regid: delete:  " field. RegIDs have the following format: <country code>.<name>. If you do not know your RegID, please contact delete: <a href="mailto:[email protected]"> [email protected] delete: </a> . delete:  delete: <h2> delete: <a name="user"> delete: </a> Address Space User delete: </h2> delete: <pre> #[ADDRESS SPACE USER]# delete:   % delete:   % Is this request being sent by a sponsoring LIR on behalf of an delete:   % End User? (Yes/No) delete:   delete:   end-user-of-sponsoring-lir: delete:  Ye delete:  s delete:   delete:   % If yes, please confirm that the "End User Assignment Agreement" delete:   % contains all of the elements listed in paragraph 2.0 of delete:   % "Contractual Requirements for Provider Independent Resource Holders delete:   % in the RIPE NCC Service Region".(Yes/No) delete:   delete:   confirmation: delete:  Yes delete:  delete:   delete:   % Which TLD or ENUM operator will use the requested address space? delete:   delete:   legal-organisation-name: delete:  North Santa NIC delete:  delete:   tld(s) or ENUM delegation(s): delete:  com biz nn delete:  delete:   organisation-location: delete:  Santa City, NN delete:  delete:   website-if-available: delete:  http://www.ns-nic.nn delete:  delete: </pre> delete:  The End User should be a recognised TLD or ENUM Tier 1 operator, as listed in these documents: delete:   delete:   delete: <a href="http://www.iana.org/domains/root/db/"> Root Zone Database delete: </a> delete: <a href="http://www.itu.int/oth/T0208000001"> Approved ENUM Delegations delete: </a> delete:  delete: <pre> % Does this End User already have address space in use for delete:   % anycast? (Yes/No) delete:   delete:   space-available: delete:  No delete:  delete:   delete:   % Will the End User return any address space? delete:   delete:   address-space-returned: delete:   delete: </pre> delete:  If you are an LIR sending this request on behalf of an End User, you should answer 'Yes' in the "end-user-of-sponsoring-lir" field. delete:  delete:  If you answered "Yes" you should also confirm that all of the elements of paragraph 2.0 of " delete: <a href="http://www.ripe.net/ripe/docs/contract-req.html"> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </a> " are listed in the 'End User Assignment Agreement' that is signed by the End User and the sponsoring LIR. Anycast assignments can only be made to End Users if there is a signed 'End User Assignment Agreement' between the sponsoring LIR and the End User. delete:  delete:  You can find an example agreement at delete: <a data-val="391df1203f5f7d0cf5f62b4d65424e23" href="resolveuid/391df1203f5f7d0cf5f62b4d65424e23" data-linktype="internal" class="internal-link"> http://www.ripe.net/membership/lir-end-user-agreement.html delete: </a> . delete:  delete:  You can send us an agreement in your local language or use the English version. delete:  delete:  If this request is sent by a Direct Assignment User, you answer "No" to the above two questions. Direct Assignment Users have already signed an 'End User Assignment Agreement' with the RIPE NCC. If the request is for an LIR, you should also answer with "No". delete:   delete:   Enter the legal name of the organisation that will use the anycast assignment in the "legal-organisation-name:" field and list all of their TLDs (Top-Level Domains) in the "tld(s):" field. delete:   delete:   Enter the primary location of the organisation in the "organisation-location:" field and, if they have a website, enter the URL in the "website-if-available:" field. delete:   delete:   If the End User already has address space in use for anycast, list this in the "space-available:" field. delete:   delete:   If there is any address space assigned to the End User that they will return, list each prefix in separate " delete:  address-space-returned: delete:  " fields. delete:  delete:  The expected time for renumbering is three months. You can use the following syntax: <x.x.x.x/xx> to <which LIR/ISP> in <time period> for this field. delete:  delete:  delete:  delete: <h2> delete: <a name="information"> delete: </a> Initial Information delete: </h2> delete: <pre> #[INITIAL INFORMATION]# delete:   % delete:   % Does the End User accept the policies on anycast assignments? delete:   % http://www.ripe.net/ripe/docs/ipv4-policies.html delete:   % http://www.ripe.net/ripe/docs/ipv6policy.html (Yes/No) delete:   delete:   confirmation: delete:  Yes delete:  delete:   delete:   % Is the End User requesting an IPv4 assignment, an IPv6 delete:   % assignment, or both? (IPv4/IPv6/Both) delete:   delete:   ip-version: delete:  Both delete:  delete:   delete:   % If the End User is requesting an IPv4 assignment, will the TLD delete:   % nameserver set apply anycasting as described in BCP126/RFC4786? delete:   % http://www.ietf.org/rfc/rfc4786.txt (Yes/No) delete:   delete:   rfc4786: delete:  Yes delete:  delete: </pre> delete:  The End User must read the delete: <a href="http://www.ripe.net/ripe/docs/ipv4-policies.html"> IPv4 Address Allocation and Assignment Policies delete: </a> and/or the delete: <a href="http://www.ripe.net/ripe/docs/ipv6-policy.html"> IPv6 Address Allocation and Assignment Policy delete: </a> , and in particular the sections that refer to anycast assignments. Enter 'yes' in the " delete:  confirmation: delete:  " field if the End User agrees to follow these policies. delete:  delete:  We need to know whether the End User would like us (RIPE NCC) to make an IPv4 assignment or an IPv6 assignment. If they need both, enter 'Both' in the " delete:  ip-version: delete:  " field and make any additional comments in the " delete:  Network Description delete:  " section. delete:  delete:  If the End User is requesting an IPv4 assignment, please check that their TLD nameserver set conforms to the practices outlined in delete: <a href="http://www.ietf.org/rfc/rfc4786.txt"> RFC 4786 delete: </a> . delete:  delete:  delete:  delete: <h2> delete: <a name="plan"> delete: </a> Anycast Node Plan delete: </h2> delete: <pre> #[ANYCAST NODE PLAN]# delete:   % delete:   % Which anycast nodes will be used? delete:   % delete:   % Node Name Peers Location delete:   delete:   node: delete:  Z-root Santa see Network Descr. Santa City IX delete:  delete:   node: delete:  Z-root Rudolf see Network Descr. Rudolf Town IX delete:  delete:   node: delete:   delete:   number-of-nodes: delete:  2 delete:  delete: </pre> delete:  The Anycast Node Plan shows how the End User will use the requested address space. delete:  delete:  You can repeat the " delete:  node: delete:  " row as many times as needed. delete:  delete:  Delete any empty " delete:  node: delete:  " fields before you send the request. delete:  delete:  In the " delete:  Node Name delete:  " column, enter the name of each node. delete:  delete:  In the " delete:  Peers delete:  " column, enter the AS Numbers of the peers for each node. delete:  delete:  In the " delete:  Location delete:  " column, enter the primary location of the node. delete:  delete:  If needed, you can write more detailed descriptions of any of the fields in the " delete:  Network Description delete:  " section. delete:  delete: <h2> delete: <a name="description"> delete: </a> Network Description delete: </h2> delete: <blockquote> delete: <pre> % Please add more information if you think it will help us understand delete:   % this request. delete:   delete: </pre> delete: </blockquote> delete:  delete:  We plan to provide anycasting from Santa City and Rudolf Town. The peers at Santa City IX are listed at http://www.scix.nn/peers and the peers at Rudolf Town IX are listed at http://www.rtix.nn/peers. delete:  delete:  delete:  You can use this space for additional information that you think will be helpful for us when we evaluate your request. A clearer understanding of the End User's addressing needs can help us to evaluate your request more quickly. delete:  delete: <h2> delete: <a name="documentation"> delete: </a> Supporting Documentation delete: </h2> delete: <pre> #[SUPPORTING DOCUMENTATION]# delete:   % delete:   % If this request being sent by a sponsoring LIR on behalf of an delete:   % End User, please attach a copy of the signed "End User delete:   % Assignment Agreement" and the company registration papers of the delete:   % End User. delete:   % You can also attach a network diagram or other supporting documentation. delete:   % delete:   % Have you attached any files/documents to this request? (Yes/No) delete:   file-attached: delete:  Yes delete:   delete:  delete: </pre> delete:  delete:   For each anycast assignment that is requested through a sponsoring LIR for an End User, we need to receive a copy of 'End User Assignment Agreement' and the company registration papers of the End User. delete:   delete:   If this request is for an LIR or a "Direct Assignment User", you do not have to attach a copy of 'End User Assignment Agreement' and company registration papers. delete:   delete:   A network diagram (topology map) can help us to understand the set-up of the network and its addressing needs. delete:  delete: <h2> delete: <a name="database"> delete: </a> Database Template(s) delete: </h2> delete: <pre> #[DATABASE TEMPLATES]# delete:   delete:   % IPv4 delete:   % Please complete all of the fields below. delete:   delete:   inetnum: delete:   netname: delete:  NS-NIC delete:  delete:   descr: delete:  North Santa NIC delete:  delete:   country: delete:  NN delete:  delete:   org: delete:  ORG-NSN3000-RIPE delete:  delete:   admin-c: delete:  HOHO1-RIPE delete:  delete:   tech-c: delete:  HOHO1-RIPE delete:  delete:   status: ASSIGNED ANYCAST delete:   mnt-by: RIPE-NCC-END-MNT delete:   mnt-lower: RIPE-NCC-END-MNT delete:   mnt-by: delete:  SANTA-MNT delete:  delete:   mnt-routes: delete:  SANTA-MNT delete:  delete:   mnt-domains: delete:  SANTA-MNT delete:  delete:   changed: [email protected] delete:   source: RIPE delete:   delete:   % IPv6 delete:   % Please complete all of the fields below. delete:   delete:   inet6num: delete:   netname: delete:  NS-NIC delete:  delete:   descr: delete:  North Santa NIC delete:  delete:   country: delete:  NN delete:  delete:   org: delete:  ORG-NSN3000-RIPE delete:  delete:   admin-c: delete:  HOHO1-RIPE delete:  delete:   tech-c: delete:  HOHO1-RIPE delete:  delete:   status: ASSIGNED ANYCAST delete:   mnt-by: RIPE-NCC-END-MNT delete:   mnt-lower: RIPE-NCC-END-MNT delete:   mnt-by: delete:  SANTA-MNT delete:  delete:   mnt-routes: delete:  SANTA-MNT delete:  delete:   mnt-domains: delete:  SANTA-MNT delete:  delete:   changed: [email protected] delete:   source: RIPE delete:   delete: </pre> delete:  If the End User is requesting an IPv4 assignment and an IPv6 assignment, please complete both templates. You can repeat each template as many times as needed. delete:  delete:  Leave the " delete:  inetnum:/inet6num: delete:  " field empty as we will choose the address range. delete:  delete:  The " delete:  netname: delete:  " should be a short and descriptive name for the network and should reflect the organisation name of the End User. delete:  delete:  Enter the End User's legal organisation name in the " delete:  descr: delete:  " field. delete:  delete:  Use the ISO country code of the End User's location in the " delete:  country: delete:  " field. If the End User is multi-national, repeat the " delete:  country delete:  " field as many times as needed. delete:  delete:  Enter the org-ID of the End User's delete:  organisation delete:  object in the " delete:  org: delete:  " field. delete:  delete:  If they don't have an delete:  organisation delete:  object, you can create one for them using the LIR Portal ( delete: <a href="https://lirportal.ripe.net"> https://lirportal.ripe.net delete: </a> ). delete:  delete:  The nic-handle of the delete:  role delete:  or delete:  person delete:  object in the " delete:  admin-c: delete:  " field should reflect someone who is administratively responsible for the network. delete:  delete:  The nic-handle of the delete:  role delete:  or delete:  person delete:  object in the " delete:  tech-c: delete:  " field should reflect someone who has technical knowledge of the network. delete:  delete:  The " delete:  status: delete:  " field must be ASSIGNED ANYCAST . delete:  delete:  The " delete:  mnt-by: delete:  " and " delete:  mnt-lower: delete:  " fields must contain RIPE-NCC-END-MNT. delete:  delete:  The second " delete:  mnt-by: delete:  " field shows which maintainer authenticates object updates. delete:  delete:  The " delete:  mnt-routes: delete:  " and " delete:  mnt-domains: delete:  " fields show which maintainers authenticate the creation of delete:  route delete:  and delete:  domain delete:  objects. delete:  delete:  The RIPE Database must contain all of the objects that you use. delete:  delete:  The " delete:  changed: delete:  " field must be delete:  [email protected] delete:  . delete:  delete:  The " delete:  source: delete:  " field must be RIPE . delete:  delete: <h2> delete: <a name="end"> delete: </a> End of Request delete: </h2> delete: <pre> #[END of REQUEST]# delete:   delete:  delete:   Best Regards, delete:   Jan Janssen, Bluelight Admin delete:  delete: </pre> delete:  Please write your full name below the "#[END of REQUEST]#" header. delete: 