7/01/2017
Récupéré justificatif d'identité.
Attente du service agreement.

Matthieu Herrb a écrit :

Demande de prefixe PI IPv6 pour Petrus LT.

et ASN...

Echanges avec le RIPE pour allocation de + d'un /48 PI:

Thank you for your message.

Yes, it is indeed possible to request a /48 per location that would have their
+own separate connection to the internet.

The approval will be made in adjacent blocks. If they can document six separate
+End Sites with unique routing requirements, an approval of one /46 + one /47
+will be made. For PI addressing space it is not possible to round up the
+approval size for any form of administrative ease.

In addition, the usage restrictions of IPv6 PI space will apply. Unless the
+current IPv6 PI policy proposal is accepted, and the request is sent in after
+the proposal has been implemented:
https://www.ripe.net/participate/policies/proposals/2016-04

Kind regards,
Kjell Leknes
IP Resource Analyst
RIPE NCC

On Sun, 5 Mar 2017 14:20:48 +0100, Matthieu Herrb wrote:

x-ncc-regid: fr.tetaneutralnet

Hi,

we (TETANEUTRAL.NET LIR) have a customer who would like to request the
assignation of a larger than /48 PI IPv6 address space.

His motivation is that the adress space will be used on several (6 in
the next 3 months, up to 12 in the next 2 years) geographical sites
with different upstreams provider on each site. So each site needs its
own /48 prefix. Each site will be multi-homed.

My question is whether as LIR we should request one PI /44 prefix for
him and let him announce the /48s inside this allocation, or if we
should request separate /48s for each of his points of presences.

Thank you for your help.

Best regards,
--
Matthieu Herrb
for Tetaneutral.net (ORG-TA940-RIPE)

Demandes faites le 11/3:

1. NCC#2017033216 fr.tetaneutralnet Request for an IPv6 PI assignment received
2. NCC#2017033217 fr.tetaneutralnet Request for an IPv6 PI assignment received
3. NCC#2017033219 fr.tetaneutralnet Request for an IPv6 PI assignment received
4. NCC#2017033220 fr.tetaneutralnet Request for an IPv6 PI assignment received
5. NCC#2017033221 fr.tetaneutralnet Request for an IPv6 PI assignment received
6. NCC#2017033224 fr.tetaneutralnet Request for an IPv6 PI assignment received
7. NCC#2017033228 fr.tetaneutralnet Request for an ASN assignment received

Retour négatif du RIPE le 14/03 :

You mentioned that a single AS number will be used (requested in
NCC#2017033228). Will the same AS number be used at every site? If that is the
case it means there is just a single routing policy (in this case one network).

Because of this PIERRE EMERIAUD could be assigned a single /48 for their entire
network and a smaller subnet given per site. (For example a /52 per site would
satisfy the bit boundary and permit 16 sites to be connected).

Please share with us more information about the IPv6 network implementation for
PIERRE EMERIAUD. Any network diagrams would also be useful.

Please let us know if we can answer any questions for you.

ACK de Petrus_lt le 15/03 pour faire avec un /48

Date: Thu, 16 Mar 2017 17:25:46 +0100
From: RIPE NCC Hostmaster <hostmaster@ripe.net>
To: Matthieu Herrb <matthieu@herrb.eu>
Subject: NCC#2017033216 IPv6 prefix 2001:678:3cc::/48 Assigned to PIERRE EMERIAUD

Dear Matthieu,

Many thanks for the clarification. I have approved the /48 through this request
+NCC#2017033216. I will proceed to approve the AS number next.

Here is the /48 IPv6 prefix:

2001:678:3cc::/48 to PIERRE EMERIAUD

The RIPE database shows the following information:

    inet6num:            2001:678:3cc::/48
    netname:             FR-TETANEUTRALNET-20170316
    country:             FR
    org:                 ORG-EMER1-RIPE
    sponsoring-org:      ORG-TA940-RIPE
    admin-c:             PE3519-RIPE
    admin-c:             TTNN1-RIPE
    tech-c:              PE3519-RIPE
    tech-c:              TTNN1-RIPE
    status:              ASSIGNED PI
    mnt-by:              RIPE-NCC-END-MNT
    mnt-by:              SYNHACX-MNT
    mnt-by:              TETANEUTRAL-MNT
    created:             2017-03-16T16:21:10Z
    last-modified:       2017-03-16T16:21:10Z
    source:              RIPE

Please update your records accordingly.

fr.tetaneutralnet is the Sponsoring LIR for this resource.

Date: Thu, 16 Mar 2017 17:27:54 +0100
From: RIPE NCC Hostmaster <hostmaster@ripe.net>
To: Matthieu Herrb <matthieu@herrb.eu>
CC: ripe-contact@tetaneutral.net
Subject: NCC#2017033228 Autonomous System Number AS206155 Assigned to PIERRE EMERIAUD

Dear Matthieu,

Today, the RIPE NCC assigned the following Autonomous System Number:

AS206155 to PIERRE EMERIAUD

The RIPE Database shows the following information:

    aut-num:             AS206155
    as-name:             EMERIAUD-NET-AS
    org:                 ORG-EMER1-RIPE
    sponsoring-org:      ORG-TA940-RIPE
    import:              from AS204092 accept ANY
    export:              to AS204092 announce AS206155
    import:              from AS197422 accept ANY
    export:              to AS197422 announce AS206155
    admin-c:             PE3519-RIPE
    admin-c:             TTNN1-RIPE
    tech-c:              PE3519-RIPE
    tech-c:              TTNN1-RIPE
    remarks:             For information on "status:" attribute read https://www
+.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources
    status:              ASSIGNED
    mnt-by:              RIPE-NCC-END-MNT
    mnt-by:              TETANEUTRAL-MNT
    mnt-by:              SYNHACX-MNT
    mnt-routes:          SYNHACX-MNT
    mnt-routes:          TETANEUTRAL-MNT
    created:             2017-03-16T16:26:58Z
    last-modified:       2017-03-16T16:26:58Z
    source:              RIPE

Please update your records accordingly.

fr.tetaneutralnet is the Sponsoring LIR for this resource.