archives:ripe_ipv4_demande
no way to compare when less than two revisions
Différences
Ci-dessous, les différences entre deux révisions de la page.
— | archives:ripe_ipv4_demande [2013/09/09 22:32] (Version actuelle) – créée - modification externe 127.0.0.1 | ||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
+ | % Provider Aggregatable (PA) Assignment Request Form | ||
+ | | ||
+ | | ||
+ | % RIPE NCC members can use this form to request a PA assignment. Please see | ||
+ | % ripe-584 for instructions on how to complete this form. | ||
+ | | ||
+ | | ||
+ | #[GENERAL INFORMATION]# | ||
+ | % | ||
+ | % Please add your RegID. | ||
+ | | ||
+ | request-type: | ||
+ | form-version: | ||
+ | x-ncc-regid: | ||
+ | | ||
+ | | ||
+ | #[ADDRESS SPACE USER]# | ||
+ | % | ||
+ | % Who will use the requested address space? | ||
+ | | ||
+ | legal-organisation-name: | ||
+ | organisation-location: | ||
+ | website-if-available: | ||
+ | | ||
+ | % Does this End User already have address space that can be | ||
+ | % used for this assignment? (Yes/No) | ||
+ | | ||
+ | space-available: | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | # | ||
+ | % How will the End User use this address space? | ||
+ | % | ||
+ | % | ||
+ | % size (/nn) | ||
+ | | ||
+ | subnet: /26 /26 /26 /26 infrastructure | ||
+ | subnet: /26 /26 /26 /26 interconnections with others operators | ||
+ | subnet: /25 /25 /25 /25 Customers over xDSL | ||
+ | subnet: /25 /25 /25 /25 Customers over WiFi | ||
+ | subnet: /25 /25 /25 /25 Customers over FTTH | ||
+ | totals: /23 | ||
+ | | ||
+ | number-of-subnets: | ||
+ | | ||
+ | % Which netname will you use for this assignment? | ||
+ | | ||
+ | netname: FR-ILOTH-V4 | ||
+ | | ||
+ | % Will the End User return any address space? | ||
+ | | ||
+ | address-space-returned: | ||
+ | | ||
+ | | ||
+ | #[EQUIPMENT DESCRIPTION]# | ||
+ | % | ||
+ | % What equipment will be used and how will it use the requested | ||
+ | % address space? | ||
+ | | ||
+ | equipment-name: | ||
+ | manufacturer-name: | ||
+ | model-number: | ||
+ | other-data: running debian/ | ||
+ | | ||
+ | equipment-name: | ||
+ | manufacturer-name: | ||
+ | model-number: | ||
+ | other-data: running debian | ||
+ | | ||
+ | | ||
+ | #[NETWORK DESCRIPTION]# | ||
+ | % | ||
+ | % Please add more information if you think it will help us understand | ||
+ | % this request. | ||
+ | | ||
+ | Internet Libre et Ouvert Pour Tous dans l' | ||
+ | provider with no profit goal. The aim is to provide a real Internet in pure | ||
+ | spirit of neutrality. | ||
+ | Members will be connected through different technologies : copper (xDSL), | ||
+ | wireless, FTTH. | ||
+ | | ||
+ | #[NETWORK DIAGRAM]# | ||
+ | % | ||
+ | % Have you attached a network diagram to this request? (Yes/No) | ||
+ | | ||
+ | diagram-attached: | ||
+ | | ||
+ | | ||
+ | #[END of REQUEST]# | ||
+ | | ||
+ | Demande d'AS | ||
+ | | ||
+ | | ||
+ | % AS Number Request Form | ||
+ | | ||
+ | % RIPE NCC members (LIRs) can use this form | ||
+ | % to request an Autonomous System (AS) Number. For instructions on how to | ||
+ | % complete this form see: | ||
+ | %" | ||
+ | % http:// | ||
+ | % | ||
+ | % Please note that the End User should have a signed "End User | ||
+ | % Assignment Agreement" | ||
+ | | ||
+ | #[GENERAL INFORMATION]# | ||
+ | % | ||
+ | % Please add your RegID | ||
+ | | ||
+ | request-type: | ||
+ | form-version: | ||
+ | x-ncc-regid: | ||
+ | | ||
+ | #[AS NUMBER USER]# | ||
+ | % | ||
+ | % Who will use the AS Number being requested? | ||
+ | | ||
+ | legal-organisation-name: | ||
+ | website-if-available: | ||
+ | | ||
+ | % Is this request being sent by a sponsoring LIR on behalf of an | ||
+ | % End User? (Yes/No) | ||
+ | | ||
+ | end-user-of-sponsoring-lir: | ||
+ | | ||
+ | % If yes, please confirm that the "End User Assignment Agreement" | ||
+ | % contains all of the elements listed in paragraph 2.0 of | ||
+ | % " | ||
+ | % in the RIPE NCC Service Region" | ||
+ | | ||
+ | confirmation: | ||
+ | | ||
+ | #[ADDRESS SPACE TO BE ANNOUNCED]# | ||
+ | % | ||
+ | % Which address prefix will originate from the new AS number? | ||
+ | | ||
+ | prefix: | ||
+ | | ||
+ | % If the address assignment is waiting for approval, please | ||
+ | % include the ticket number of the request below. | ||
+ | | ||
+ | pending-ticket-ID: | ||
+ | | ||
+ | #[PEERING CONTACTS]# | ||
+ | % | ||
+ | % Please list the email contact addresses of peering | ||
+ | % partners for the requested AS Number. | ||
+ | | ||
+ | peering: peering@ovea.com | ||
+ | peering: peering@bluenetech.com | ||
+ | | ||
+ | # | ||
+ | % | ||
+ | % Please add more information if you think it will help us understand | ||
+ | % this request. | ||
+ | | ||
+ | | ||
+ | | ||
+ | % If you require a 16-bit AS Number instead of a 32-bit AS Number, | ||
+ | % please indicate this below and tell us why. For more information, | ||
+ | % see http:// | ||
+ | | ||
+ | AS Number Type: 32-bit [change as required] | ||
+ | | ||
+ | Why 16-bit: | ||
+ | | ||
+ | # | ||
+ | % | ||
+ | % If this request is being sent by a sponsoring LIR on behalf of | ||
+ | % an End User, please attach a copy of the signed | ||
+ | % "End User Assignment Agreement" | ||
+ | % of the End User. | ||
+ | % You can also attach a network diagram or other supporting documentation. | ||
+ | % | ||
+ | % Have you attached any files/ | ||
+ | | ||
+ | file-attached: | ||
+ | | ||
+ | #[DATABASE TEMPLATE(S)]# | ||
+ | % | ||
+ | % Please complete all of the fields below | ||
+ | | ||
+ | aut-num: | ||
+ | as-name: | ||
+ | descr: | ||
+ | org: < | ||
+ | import: | ||
+ | export: | ||
+ | import: | ||
+ | export: | ||
+ | admin-c: | ||
+ | tech-c: | ||
+ | mnt-by: | ||
+ | mnt-by: | ||
+ | mnt-routes: | ||
+ | changed: | ||
+ | source: | ||
+ | | ||
+ | #[END of REQUEST]# | ||
+ | :!: Ci-dessous, ancienne demande pour documentation | ||
+ | |||
+ | 1 - Current space | ||
+ | ================== | ||
+ | Please list all IP ranges the end user now uses for the same services. | ||
+ | Will they return any? If yes, when? | ||
+ | |||
+ | => Currently, we have none IP ranges. We are just an young and new organization. | ||
+ | |||
+ | |||
+ | 2 - Current customers / IPs | ||
+ | ================== | ||
+ | > subnet: /25 64 128 128 Customers over xDSL | ||
+ | > subnet: /25 64 128 128 Customers over WiFi | ||
+ | ?subnet: /25 64 128 128 Customers over FTTH | ||
+ | |||
+ | -How many total customers do they have for these broadband services? | ||
+ | -How many total customers did they have for these broadband services 3 months ago? | ||
+ | |||
+ | Internet Libre et Ouvert Pour Tous dans l' | ||
+ | provider, located at Montpellier, | ||
+ | The organisation is without profit goal. | ||
+ | The aim is to provide a real Internet in pure spirit of neutrality to our members without any QoS, | ||
+ | any filter, any kind of proxies. All packets must flow freely. | ||
+ | Members will be connected through different technologies : copper (xDSL), | ||
+ | wireless, FTTH, without restriction. We consider all these technologies equal, depending only of their availabilty | ||
+ | for the member. The member may choose the technology best suited to their needs. | ||
+ | Before having our own infrastructure on these technologies, | ||
+ | in a neutral way, due to more and more big French ISPs act as non-neutral providers. | ||
+ | |||
+ | -How many IPs do they assign to each of them? | ||
+ | 1 IPv4. | ||
+ | |||
+ | -Is it dynamic or static assignment? | ||
+ | |||
+ | We use static assignment. It's more easy to log and to respect French Laws for network operators. | ||
+ | |||
+ | |||
+ | 3 - Infrastructure | ||
+ | ================== | ||
+ | > subnet: /26 8 16 64 Infrastructure | ||
+ | |||
+ | Please explain how these IPs will be used in the next 3 months. | ||
+ | |||
+ | => These IPs will be used for servers with services : mail, web, dns, news, ftp, monitoring, voip, ntp, pxe, bgp, mysql | ||
+ | git with redondant and backup servers, virtual private servers for members and hardware : switch, upc ip, kvm ip, and routers. | ||
+ | |||
+ | Please list also the devices that will be in the network. | ||
+ | * Servers : HP (gift from INRIA/IRISA department via Free Software Fondation) | ||
+ | * Switch : dlink | ||
+ | * Routers : soekris, microtik, ubiquiti, and software (supermicro running quagga/bgp) | ||
+ | * UPC IP | ||
+ | * Kvm IP | ||
+ | * ATLAS Sonde | ||
+ | |||
+ | 4 - Interconnection with providers | ||
+ | ================== | ||
+ | > subnet: /26 8 16 64 Interconnection with providers | ||
+ | |||
+ | How many are the providers? | ||
+ | |||
+ | => Immediately, | ||
+ | at Paris, Blue Networks Technologies and Gitoyen (for xDSL), waiting for a local xDSL collect. | ||
+ | Then, we want to be connected to all local providers in Hérault. ATM, there is no regional IX. :( | ||
+ | and to a lot of providers and IX with our infrastructure in Paris. | ||
+ | |||
+ | |||
+ | Is this subnet for point to point links? | ||
+ | |||
+ | => we use /31 PtP Link RFC 3021 to make interconnection with providers | ||
+ | |||
+ | How many IPs will be used per link? | ||
+ | |||
+ | => only 2, one on our side, the other one with the provider | ||
+ | |||
+ | |||
+ | 5 - Agreement | ||
+ | ================== | ||
+ | Please include in the agreement the definitions of the two companies; stating which company is the LIR and which the end user. | ||
+ | You can add this information at the end of the document - under the respective signatures. | ||
+ | Please add the words LIR / end user and please also include the full name of the end user ' | ||
+ | (ce point me concerne plus particulièrement, | ||
+ | |||
+ | |||
+ | 6 - Update in ORG-IL240-RIPE | ||
+ | ================== | ||
+ | Please change the org-name of the object into Association Internet Libre et Ouvert pour Tous dans l Herault (ILOTH). | ||
+ | You just need to add the part (ILOTH). | ||
+ | |||
+ | => Done |
archives/ripe_ipv4_demande.txt · Dernière modification : 2013/09/09 22:32 de 127.0.0.1