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.

• https://www.ripe.net/participate/member-support/info/faqs/faq-joining
  • “And if you have questions, we’re here to help. Just email us at new-account@ripe.net or call +31 20 535 4444.”
• https://access.ripe.net/registration
  • Ludovic Pouzenc / contact-ripe@chd.sx

• https://www.ripe.net/participate/member-support/become-a-member
  • Désactiver NoScript, il y a du JS degueuleasse de partout, amazon, google…
  • You are logged in as contact-ripe@chd.sx. We will use this information to process your application
  • Join using this account
  • I want to become a RIPE NCC member
  • C'est parti pour un formulaire en 6 étapes, cf screenshots.

• Le RIPE a écrit en demandant de préciser :
  • le type d'entreprise (Example: Ltd, Plc, Inc, GmbH etc.) - on est une asso, pas d'accronyme connu de nous
  • le numéro de TVA - on est une asso, on n'en a pas, Tetaneutral a regardé le sujet : on paie les 21% de VAT de chez eux.
• En patois :

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

• Facture (invoice) reçu par e-mail par le trésorier
• Surprise : elle ne charge pas le dernier trimestre de 2015 mais l'année entière de 2016.
  • 2000 + 1400 € HT ⇒ 4114 € avec leur TVA de 21%
• Une question au support a permis d'apprendre qu'ils nous offraient Décembre (paiement des frais de services par trimestre normalement)

• Réception du courrier DHL
  • Avec une blague : il n'y a pas la raison sociale sur l'adresse mais l'identifiant RIPE (fr.commingeshd) et le nom du contact technique. Le courrier a été refusé par la mairie qui héberge administrativement l'asso car le nom du contact technique ne lui rappelait rien. Pb rattrapé par téléphone + déplacement à St-Go dans l'heure.
• Signature par la présidente le soir même

• Demande par téléphone à DHL d'un enlèvement pour le courrier de retour
  • Parti vers 15h
• Lancement du paiement par le résorie

• Courrier traité par le RIPE le 08 à 13h22. (wow)
• Attente du paiement

• Paiement reçu

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

• Connexion au LIR portal
  • Vérif des enregistrement Organisation, Person et MNTNER
  • Deux modif à faire plus tard :
    • Téléphone : ne pas avoir le 07811
    • Adresse : Jeanne d'Arc et pas Jean d'Arc (coup de fatigue pdt l'inscription, désolé)
      • Ça prends une demande de modification avec validation par un humain sur ce type de champ.
      • Le courrier arrive quand même, on peut éviter de brouiller le signal tant qu'on est dans la deadline de la migration
  • Request form rempli et validé pour les 1024 IPv4 (/22) – idem IPv6 : allocation /32

• Appel téléphonique du RIPE (au numéro laissé lors des demandes IP) : simple appel de courtoisie, “We have already validated your requests […]”, “Do you have any questions ?”.
• Les allocations apparaissent dans le LIR Portal
  • 185.131.40.0/22 : ALLOCATED PA
  • 2a03:a0a0::/32 : ALLOCATED
• Il est temps de finir de s'affûter
  • Les IP allocated ne sont pas considérées utilisées, elles doivent être assignées pour être utilisées
  • Il faut et suffit que le LIR crée les objets de type inetnum et route pour les premières assignation
  • Le LIR doit respecter :
    • IPv4 Address Allocation and Assignment Policy
    • IPv6 Address Allocation and Assignment Policy
    • Toutes les recommandations des autres documents RIPE

• Création des objets pour assigner 2 premières /24 IPv4 à CHD et une première /.. IPv6
• Surprise : dans la partie LIR Portal du site du RIPE, il n'y a rien pour assigner des plages
  • Il y a plusieurs API pour créer des objets dans la base (via mail, HTTP REST…) et une interface web pour humains appelée webupdates

• L'outil webupdates permet d'avoir le détail des champs, et propose d'emblée tous les champs “mandatory”. La position des champs de formulaire dans l'interface web détermine l'ordre des champs dans l'objet résultant. D'un autre côté, l'ordre ne semble avoir aucune sémantique.
• Pour comparer deux enregistrements en console, vimdiff et whois sont nos amis

lpouzenc@lud-msi:~/Bureau/CHD$ vimdiff <(whois 185.131.40.0) <(whois 185.61.116.0)
2 fichiers à éditer

• Pour avoir le descriptif des champs d'un type d'enregistrement : whois -v

inetnum.txt

% 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)

• Regarder les objets créés par le RIPE pour CHD le LIR
  • organisation : whois ORG-CHD1-RIPE
  • mntner: whois fr-commingeshd-1-mnt
  • person (abuse-c): whois AR34604-RIPE
  • inetnum: whois 185.131.40.0/22
  • inet6num: whois 2a03:a0a0::/32
• Se poser les questions de la longueur des préfixes qu'on veut déléguer au FAI
  • IPv4 : Couper La /22 en 4 /24 semble à peu près la seule chose intelligente
  • IPv6 : C'est moins évident. /48 pour 65k adhérent qui auraient leur /64 ?
    • https://labs.ripe.net/Members/dbayer/visibility-of-prefix-lengths
• Créer tous les objets nécessaires pour CHD le FAI
  • inetnum: whois 185.131.40.0/24
  • inetnum: whois 185.131.41.0/24
  • inet6num: whois 2a03:a0a0::/48
  • TODO : routes
  • domain: whois 40.131.185.in-addr.arpa
  • domain: whois 41.131.185.in-addr.arpa
  • TODO : whois 0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.a.3.0.a.2.ip6.arpa.in-addr.arpa