[routing-wg] network failed, was re: Notification of RIPE Database changes

Folks,

this is what I got back from the DBM folks. I think it does explain what
happened, and "how". But at the same time it opens a new set of Q.s, in
particular how to deal with the fact that no registry, at least as of now,
has implemented "rpsl-dist".

Wilfried.

PS: on top of my journey to BKK, another reason for the delay in forwarding
    was double-checking that the original question was public already, as I
    initially read the copy to the DB-WG Chairs, and not on the Routing WG list.
_____________________________________________________________________________

Dear Wilfried,

Thank you for contacting us.

It is possible to create a route object in the RIPeDatabase for an
address space which is registered outside the RIPE Region.

In order to create the route object you will need to pass the authentication of RIPE-NCC-RPSL-MNT which is a public maintainer. The
authentication password for this maintainer is written in the remarks of the mntner object itself:

% Information related to 'RIPE-NCC-RPSL-MNT'

mntner:         RIPE-NCC-RPSL-MNT
descr:          This maintainer may be used to create objects to represent
descr:          routing policy in the RIPE Database for number resources not
descr:          allocated or assigned from the RIPE NCC.
admin-c:        RD132-RIPE
auth:           MD5-PW # Filtered
remarks:        *******************************************************
remarks:        * The password for this object is 'RPSL', without the *
remarks:        * quotes. Do NOT use this maintainer as 'mnt-by'.     *
remarks:        *******************************************************
mnt-by:         RIPE-DBM-MNT
referral-by:    RIPE-DBM-MNT
source:         RIPE # Filtered

However please note that we do not control routing configuration and
do not have an active role in the configuration of the routers and BGP
setting being used.

Entering Route object into the RIPE Database does not automatically
mean those routes will be picked up by the providers/networks.

Some networks filter and configure their routers automatically using
the RIPE Database Internet Routing registry (IRR).

The RIPE Database is authoritative only for the address space which is
registered under the RIPE Region.

If you want to see which Database is authoritative for a certain
address space you can use the --resource option:

$ whois --resource 41.76.128.0/21
% 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

% Information related to '41.76.128.0 - 41.76.135.255'

inetnum:        41.76.128.0 - 41.76.135.255
netname:        VANILLA
descr:          Future Perfect Corporation cc T/A Vanilla
country:        ZA
admin-c:        DUMY-RIPE
tech-c:         DUMY-RIPE
org:            ORG-FPCc1-AFRINIC
status:         ALLOCATED PA
mnt-by:         AFRINIC-HM-MNT
mnt-lower:      VANILLA-MNT
notify:         alan at vanilla.co.za
notify:         accounts at vanilla.co.za
changed:        unread at ripe.net 20000101
source:         AFRINIC-GRS
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************

organisation:   ORG-FPCc1-AFRINIC
org-name:       Future Perfect Corporation cc T/A Vanilla
org-type:       LIR
address:        125 Buitengracht St, #611
address:        Cape Town 8018
e-mail:         alan at vanilla.co.za
e-mail:         accounts at vanilla.co.za
phone:          +27214097997
fax-no:         +27214097050
admin-c:        AL7-AFRINIC
tech-c:         AL7-AFRINIC
mnt-ref:        AFRINIC-HM-MNT
mnt-by:         AFRINIC-HM-MNT
notify:         hostmaster at afrinic.net
changed:        hostmaster at afrinic.net 20100412
source:         AFRINIC-GRS

% Information related to '41.76.128.0/21AS29606'

route:          41.76.128.0/21
descr:          Borwood via AS29606
origin:         AS29606
mnt-by:         BORWOOD-MNT
mnt-by:         RIPE-NCC-RPSL-MNT
changed:        unread at ripe.net 20000101
source:         RIPE-GRS
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************

% This query was served by the RIPE Database Query Service version

-- If you have any questions, please feel free to contact us. Best regards, Andrea Di Menna Customer Services RIPE NCC RIPE NCC Customer
Satisfaction Survey ************************************* Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants
will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 On Thu, 13 Jun 2013 14:16:09 +0200,
<Woeber at CC.UniVie.ac.at> wrote:

>> Dear RIPE-DBM Team!
>>
>> Please have a look at the mail exchange below, and in particular towards
>> the end.
>>
>> We would like to understand whether our assessment of the situation is
>> correct and whether you can add anything relevant or helpful to that?
>>
>> Best regrds, TIA,
>> Wilfried.
>>
>> Sander Steffann wrote:
>>
>
>>> > Hi,
>>> >
>>> >
>>
>>>> >>thanks for the forward!
>>>> >>
>>>> >>Looking at the output for 41.76.128.0/21 in the RIPE DB and the AFRINIC DB
>>>> >>it looks like the block was subject to transfer from RIPE to AFRINIC, when
>>>> >>this new RIR was created.
>>>> >>
>>>> >>There is no inetnum: entry in the RIPE DB for this address space, but it does
>>>> >>exist in the AFRINIC's:
>>>> >>
>>>> >>mnt-by:         AFRINIC-HM-MNT
>>>> >>mnt-lower:      VANILLA-MNT
>>>> >>notify:         alan at vanilla.co.za
>>>> >>notify:         accounts at vanilla.co.za
>>>> >>changed:        unread at ripe.net 20000101
>>>> >>
>>>> >>I also understand from 2nd-hand reports, that AFRINIC does *not* operate
>>>> >>a Routing Registry.
>>>> >>
>>>> >>Thus, the safeguards that we do have in place in our region, that a route
>>>> >>object can only be created if and when both parties (address and AS# holders)
>>>> >>supply the authorisation credentials.
>>>> >>
>>>> >>So you feel that this should be dicussed publicly on the DB-WG mailing list?
>>>> >>
>>>> >>Personally, I would like to ask for clarification by the NCC's DB group, what
>>>> >>the bahaviour is - or shiuld be - when a route: object is created for which no
>>>> >>corresponding inet[6]num entra exists.
>>
>>> >
>>> >
>>> > Sounds like a plan  :-)
>>> >
>>> > Also ask why the NCC seems to have helped to create this object, as authorisation from RIPE-NCC-RPSL-MNT is necessary:
>>> >
>>> > route:          41.76.128.0/21
>>> > descr:          Borwood via AS29606
>>> > origin:         AS29606
>>> > mnt-by:         BORWOOD-MNT
>>> > mnt-by:         RIPE-NCC-RPSL-MNT
>>> > changed:        paulo at borwood.net 20120508
>>> > source:         RIPE
>>> >
>>> > Cheers,
>>> > Sander
_____________________________________________________________________________