Ceci est une ancienne révision du document !
La procédure de création d'un Local Internet Regsitry (LIR) auprès du RIPE NCC est simple et rapide. Ci-après et en très détaillé, l'ensemble des démarches faites.
Dear Ludovic Pouzenc, Thank you for your application to join the RIPE NCC. We will contact you shortly regarding the next steps in the process. If you have any questions about your application, please feel free to contact us at [[new-account@ripe.net|new-account@ripe.net]] using your ticket number NCC#2015114468 as a reference. Kind regards, RIPE NCC
Dear Ludovic, Thank you for your response. However we still require some further information. You have not specified which type of business entity your company is (Example: Ltd, Plc, Inc, GmbH etc.). Once you provide official registration papers from the trade register that proves your company is a registered legal entity we can proceed with your application. If you have any further questions do not hesitate to contact us. Best regards, Eamonn Lane -------------- Customer Services RIPE NCC
Hi, Thanks for the speed about starting to check our appliance form. French terms will be in italic. //Comminges Haut Debit// is not a company. It's a kind of non-profit organisation, this kind is called //Association Loi 1901// in France. I have no clue about an english acronym which make sense to designate those kind of structure. I think that I have uploaded the official paper about the register of this //association// in the registration form. Let me know if I've made a mistake there. Do you have it ? In France, the process of creation, publication and the registry about //associations// is hold in the //Journal Officiel// which I gave the URL in the appliance form. There is a search field allowing you to check that we are in this official registry there : https://www.journal-officiel.gouv.fr/association/ Please let us know if anything seems wrong. You can even make a call if you aren't afraid about poor English accent. Best regards, -- Ludovic Pouzenc Comminges Haut Débit
Hi Ludovic, Thank you for your email. Regarding your application submitted on the 2015-11-23 we indeed received the document of registration of this association. However before we can proceed, would you be so kind to provide the correct VAT number otherwise we will need to charge you 21% Dutch VAT on top of the invoice which already contains Sign up Fee 2000 Euro + Service Fee last quarter 400 Euro. Hope to have informed you sufficiently. If you have any further questions do not hesitate to contact us. Kind Regards, Valentino Dijkstra ------------------ Customer Services RIPE NCC
Hi, French non-profit organisation, in the way we created it does not have VAT numbers. Tetaneutral.net has dig into the details of that a few month ago with you. The conclusion was : pay Dutch VAT. We are fine with (2000+400)*(1+0,21) = 2904 € Regards, -- Ludovic Pouzenc Comminges Haut Débit
Dear Ludovic, Regarding this submitted application we received the uploaded document in good order. I have now approved your application. Shortly we will send by DHL courier: - 2 copies of the Standard Service Agreement; - 1 copy of the first invoice; - 1 copy of the current charging scheme. We can activate your RIPE NCC account as soon as we receive: - 1 signed Standard Service Agreement; and - your payment for the first invoice. Please be aware that the RIPE NCC started allocating IPv4 address space from the last /8; this means that we can not assign any IPv4 Provider Independent (PI) space. We can only allocate one /22 Provider Aggregatable (PA) address space per RIPE NCC member. For more information, please see: https://www.ripe.net/internet-coordination/ipv4-exhaustion/ http://ripe.net/ripe/docs/ipv4-policies Hope to have informed you sufficiently. If you have any further questions do not hesitate to contact us. Kind Regards, Valentino Dijkstra ------------------ Customer Services RIPE NCC
Dear Ludovic Pouzenc, We'd like to warmly welcome COMMINGES HAUT DEBIT to the RIPE NCC. We have activated your account! There are a number of important processes and actions you need to take and we'd like to help guide you through those steps. All the detailed information you need to know is available at: https://www.ripe.net/lir-services/new-member If you can't find the information you need or you have any other problems, please reply to this email and we'd be happy to help you. Kind regards, Axel Pawlik Managing Director RIPE NCC
lpouzenc@lud-msi:~/Bureau/CHD$ vimdiff <(whois 185.131.40.0) <(whois 185.61.116.0) 2 fichiers à éditer
whois -v
% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf The inetnum class: An inetnum object contains information on allocations and assignments of IPv4 address space. inetnum: [mandatory] [single] [primary/lookup key] netname: [mandatory] [single] [lookup key] descr: [mandatory] [multiple] [ ] country: [mandatory] [multiple] [ ] geoloc: [optional] [single] [ ] language: [optional] [multiple] [ ] org: [optional] [single] [inverse key] sponsoring-org: [optional] [single] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] status: [mandatory] [single] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] mnt-lower: [optional] [multiple] [inverse key] mnt-domains: [optional] [multiple] [inverse key] mnt-routes: [optional] [multiple] [inverse key] mnt-irt: [optional] [multiple] [inverse key] changed: [optional] [multiple] [ ] created: [generated] [single] [ ] last-modified: [generated] [single] [ ] source: [mandatory] [single] [ ] The content of the attributes of the inetnum class are defined below: inetnum Specifies a range of IPv4 that inetnum object presents. The ending address should be greater than the starting one. <ipv4-address> - <ipv4-address> netname The name of a range of IP address space. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. descr A short decription related to the object. A sequence of ASCII characters. country Identifies the country. Valid two-letter ISO 3166 country code. geoloc The location coordinates for the resource. Location coordinates of the resource. Can take one of the following forms: [-90,90][-180,180] language Identifies the language. Valid two-letter ISO 639-1 language code. org Points to an existing organisation object representing the entity that holds the resource. The 'ORG-' string followed by 2 to 4 characters, followed by up to 5 digits followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. sponsoring-org Points to an existing organisation object representing the sponsoring organisation responsible for the resource. The 'ORG-' string followed by 2 to 4 characters, followed by up to 5 digits followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. admin-c References an on-site administrative contact. From 2 to 4 characters optionally followed by up to 6 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. tech-c References a technical contact. From 2 to 4 characters optionally followed by up to 6 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. status Specifies the status of the resource. Status can have one of these values: o ALLOCATED PA o ALLOCATED PI o ALLOCATED UNSPECIFIED o LIR-PARTITIONED PA o LIR-PARTITIONED PI o SUB-ALLOCATED PA o ASSIGNED PA o ASSIGNED PI o ASSIGNED ANYCAST o EARLY-REGISTRATION o NOT-SET o LEGACY remarks Contains remarks. A sequence of ASCII characters. notify Specifies the e-mail address to which notifications of changes to an object should be sent. This attribute is filtered from the default whois output. An e-mail address as defined in RFC 2822. mnt-by Specifies the identifier of a registered mntner object used for authorisation of operations performed with the object that contains this attribute. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names. mnt-lower Specifies the identifier of a registered mntner object used for hierarchical authorisation. Protects creation of objects directly (one level) below in the hierarchy of an object type. The authentication method of this maintainer object will then be used upon creation of any object directly below the object that contains the "mnt-lower:" attribute. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names. mnt-domains Specifies the identifier of a registered mntner object used for reverse domain authorisation. Protects domain objects. The authentication method of this maintainer object will be used for any encompassing reverse domain object. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names. mnt-routes This attribute references a maintainer object which is used in determining authorisation for the creation of route objects. After the reference to the maintainer, an optional list of prefix ranges inside of curly braces or the keyword "ANY" may follow. The default, when no additional set items are specified, is "ANY" or all more specifics. Please refer to RFC-2622 for more information. <mnt-name> [ { list of <address-prefix-range> } | ANY ] mnt-irt May appear in an inetnum or inet6num object. It points to an irt object representing a Computer Security Incident Response Team (CSIRT) that handles security incidents for the address space specified by the inetnum or inet6num object. An irt name is made up of letters, digits, the character underscore "_", and the character hyphen "-"; it must start with "irt-", and the last character of a name must be a letter or a digit. changed Specifies who submitted the update, and when the object was updated. This attribute is filtered from the default whois output. This attribute is deprecated and will be removed in a next release. An e-mail address as defined in RFC 2822, followed by a date in the format YYYYMMDD. created This attributes reflects when the object was created in ISO8601 format (yyyy-MM-dd'T'HH:mm:ssZ). Attribute generated by server. last-modified This attributes reflects when the object was last changed in ISO8601 format (yyyy-MM-dd'T'HH:mm:ssZ). Attribute generated by server. source Specifies the registry where the object is registered. Should be "RIPE" for the RIPE Database. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a registry name must be a letter, and the last character of a registry name must be a letter or a digit. % This query was served by the RIPE Database Query Service version 1.83.1 (DB-4)
whois ORG-CHD1-RIPE
whois fr-commingeshd-1-mnt
whois AR34604-RIPE
whois 185.131.40.0/22
whois 2a03:a0a0::/32
whois 185.131.40.0/24
whois 185.131.41.0/24
whois 2a03:a0a0::/48
whois 40.131.185.in-addr.arpa
whois 41.131.185.in-addr.arpa
whois 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.a.3.0.a.2.ip6.arpa