[168291] in North American Network Operators' Group
Re: Internet Routing Registries - RADb, etc
daemon@ATHENA.MIT.EDU (Joe Abley)
Fri Jan 17 11:08:08 2014
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <52D86986.3050700@massar.ch>
Date: Fri, 17 Jan 2014 11:07:34 -0500
To: Jeroen Massar <jeroen@massar.ch>
Cc: "nanog@nanog.org Operators' Group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--Apple-Mail=_B81F908E-3740-4D6D-9362-FD2446DABA2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
On 2014-01-16, at 18:21, Jeroen Massar <jeroen@massar.ch> wrote:
> On 2014-01-16 23:11, Nick Hilliard wrote:
>> On 16/01/2014 21:22, Jon Lewis wrote:
>>> Also, at least of the ones I've dealt with, there is no verification =
of
>>> records as they're entered.
>>=20
>> on the RIPE IRRDB, there is validation, so you can't just go in and
>> register route: objects for someone else's allocations or =
assignments.
>=20
> You mean auth for RIPE region prefixes, as one can also register
> ARIN/APNIC/etc prefixes in the RIPEdb and then, there is no auth (but =
a
> mail to dbm@ripe.net resolves any issues quite quickly if something =
fake
> is there)
Yep. For someone with non-RIPE NCC numbers the only manual part of the =
process is getting a maintainer object created. Once you've done that =
it's likely that your new parent route object in the RIPE db will be =
something like this:
inetnum: 199.91.32.0 - 199.255.255.255
netname: NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK
descr: IPv4 address block not managed by the RIPE NCC
remarks: ------------------------------------------------------
remarks:
remarks: Networks in this range are not in use in
remarks: the RIPE NCC service region.
remarks:
remarks: You can find the whois server to query, or the
remarks: IANA registry to query on this web page:
remarks: http://www.iana.org/assignments/ipv4-address-space
remarks:
remarks: You can access databases of other RIR's at:
remarks:
remarks: AFRINIC (Africa)
remarks: http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks: APNIC (Asia Pacific)
remarks: http://www.apnic.net/ whois.apnic.net
remarks:
remarks: ARIN (Northern America)
remarks: http://www.arin.net/ whois.arin.net
remarks:
remarks: LACNIC (Latin America and the Carribean)
remarks: http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks: ------------------------------------------------------
which includes
mnt-routes: RIPE-NCC-RPSL-MNT
corresponding to
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
Joe
--Apple-Mail=_B81F908E-3740-4D6D-9362-FD2446DABA2C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAlLZVUYACgkQNI8MvYZSOiy1rwCaAt58gT0M0lc+XVmkESsCtWbi
vWoAoIUBIZO9ZrnqDCYo0LKpFlQ7PtI4
=81jw
-----END PGP SIGNATURE-----
--Apple-Mail=_B81F908E-3740-4D6D-9362-FD2446DABA2C--
