Local Internet Registry

Training Course | January 2015

Training Services

RIPE NCC

Schedule

09:00 - 09:30

Coee, Tea

11:00 - 11:15

Break

13:00 - 14:00

Lunch

15:30 - 15:45

Break

17:30

End

Introductions

Name
Number
on
the
list

Experience
with
the
RIPE
NCC

Goals

Overview

The Internet Registry (IR) System

The RIPE Database

Being an LIR

Exercise: Being an LIR Contact

Getting Resources

Distributing Resources

Exercise: Making Assignments

Exercise: Registering Assignments

Managing Resources

Tips and Tools

The Internet Registry

System
Section 1

Regional Internet Registries

Five RIRs worldwide

Not-for-profit organisations

Funded by membership fees

Policies decided by regional communities

Neutral, Impartial, Open, Transparent

The Internet Registry System

IANA
LACNIC
Latin America

ARIN
North America

RIPE NCC

Eurasia
Middle East

AFRINIC
Africa

APNIC
Asia Pacific

Goals: Registration

Why?

Ensure uniqueness of Internet number resources

RIR whois databases

Provide contact information

How?

Results:

IP address space used only by one organisation

Information available on users of Internet number resources

Goals: Aggregation

Why?

Routing tables growing too fast

Encourage announcement of whole allocations

Growth of routing tables has slowed a bit

Provide scalable routing solution for Internet

How?
Introduction of Classless Inter Domain Routing (CIDR)

Result:

Active BGP Entries

10

Active BGP Entries

600000

But the routing

table still grows
480000

360000

then filtered
240000

10
20
11
20
12
20
13
20
14
20
15

20

09

20

08

20

07

20

06

20

05

20

04

20

03

20

02

20

01

20

00

20

99

19

98

19

97

19

96

19

95

19

19

94

CIDR worked for a while

93

19

92

19

91

19

90

19

89

Projected growth
of routing table
before CIDR

19

120000

Longer prefixes
being announced

10

Goals: Conservation

Why?

IP addresses and AS Numbers are limited resources

Introduction of CIDR

These resources were not used eciently in the past

How?

Policies to ensure fair usage

Results:

Growth in IP address space usage slowed down

Resources were distributed based on need

11

IPv4 Address distribution - Historical

IANA

/0

RIR

/8

/21

/23

Allocation

12

LIR

/25

End User

/24

PA Assignment

PI Assignment

IPv4 Address distribution - Current

IANA

/0

RIR

/8

/22

/23

Allocation

13

LIR

/25

End User

/24

PA Assignment

PI Assignment

IPv6 Address distribution

14

IANA

/3

RIR

/12

/32

/56

Allocation

LIR

/48

End User

/48

PA Assignment

PI Assignment

RIPE NCC

Began operating in 1992

Not-for-profit membership organisation
11,000+ members (Local Internet Registries)
Neutral, Impartial, Open, Transparent
Provides administrative support to RIPE

15

Rseaux IP Europens (RIPE)

Started in 1989
Discussion forum open to all parties interested
Not a legal entity and no formal membership
Develops policies
Work done in Working Groups
Activities are performed on a voluntary basis
Decisions formed by consensus

16

RIPE Community

609 Attendees at RIPE 69, November 2014

Includes business, government, regulators,

2000+ subscribed to Address Policy Mailing list

law enforcement agencies, civil society,

academia, private citizens

Meets twice a year

at the RIPE meetings

17

Policy Development Process

Open

Anyone can participate

On mailing lists and at meetings

Transparent

List discussions archived publicly

YOU make the policies

Meetings transcribed

Developed bottom-up
The RIPE NCC implements them

18

Who makes policies ?

19

ICANN / IANA
ASO

AFRINIC

RIPE NCC

ARIN

APNIC

LACNIC

AFRINIC
community

RIPE
community

ARIN
community

APNIC
community

LACNIC
community

Global Policy Proposal

Who does what ?

The RIPE community

Creates proposals

Discusses proposals

Seeks consensus

Working Group (WG) chairs

Accept proposals

Chair the discussions

Decide if consensus has been reached

20

Who does what ?

The RIPE NCC

Acts as the secretariat to support the process

Publishes the documents

Implements the proposals

21

Participating in the PDP

Sign up for the Policy Development Process

Announcements mailing list
!

Join in discussions about policy proposals

Stay up-to-date with new policies
Propose a new policy

22

RIPE NCC General Meeting

Members may discuss the operations and

activities of the RIPE NCC
!

Also exercise their voting rights on:

Charging Scheme, Resolutions

Executive Board membership

Financial Report

Allows members to provide input to, and

feedback on, the RIPE NCCs Activity Plan

and Budget

23

The RIPE Database

Section 2

RIPE Database

Public Internet resource and routing registry

database

Resources (IP addresses, AS Numbers)

Contact information for resources

Reverse DNS delegations

Routing policy

25

RIPE Database objects

Resources
inetnum, inet6num, aut-num

Routing
route, route6

DNS
Reverse
domain

Security
mntner

Contact
organisation, person, role

26

Querying the RIPE Database

Web interface
Command
line

27

Full Text Search

Restful
API
(XML/JSON)

Query limits

Privacy sensitive data is protected

person/role objects

Maximum number of queries per day

When exceeding, you get blocked

Use --no-personal flag to limit the query

Request to be whitelisted

28

Querying the
RIPE Database
Demonstration

The maintainer

mntner:

LIR-MNT

admin-c:
tech-c:
mnt-by:
notify:
upd-to:

JS123-RIPE!
JS123-RIPE!
LIR-MNT!
js@example.org!
js@example.org!

!
auth:!
changed:
source:

MD5-PW $1$g3xT9SJ
js@example.org !
RIPE

30

Password

Hashed password

tiger72

$1$g3xT9SJ

Authentication

Password (MD5-PW)
!

Private key/public key

PGPKEY-<id> and key-cert object

X.509-<id> and key-cert object

RIPE NCC Access (Single Sign-On)

31

Protection

32

mntner:

LIR-MNT

person:

John Smith

admin-c:
tech-c:
mnt-by:
notify:
upd-to:

JS123-RIPE!
JS123-RIPE!
LIR-MNT!
js@example.org!
js@example.org!

address:
address:
e-mail:
phone:
nic-hdl:

My Street 9876!
Office 123!
js@example.org!
+31 20 876 5432!
JS123-RIPE!

auth:!
auth:!

MD5-PW $1$g3xT9SJ
$1$g3xT9SJ

mnt-by:!
mnt-by:!

LIR-MNT

tiger72

Protection of multiple objects

mntner:

LIR-MNT

admin-c:
tech-c:
mnt-by:

JS123-RIPE!
JS123-RIPE!
LIR-MNT

33

inetnum:

85.11.184.0/21

descr:

My Assignment!

admin-c:

LA789-RIPE!

tech-c:

LA789-RIPE!

status:

ASSIGNED PA!

mnt-by:

LIR-MNT

person:

John Smith

address:

Abbey Road 123!

phone:

+31 20 876 5432!

e-mail:

js@example.org!

nic-hdl:

JS123-RIPE!

mnt-by:

LIR-MNT

aut-num:
aut-num:

AS65432
AS64551

descr:

My AS Number!

admin-c:

LA789-RIPE!

tech-c:

LA789-RIPE!

mnt-by:

RIPE-NCC-END-MNT!

mnt-by:

LIR-MNT

Multiple protection

mntner:

ONE-MNT

admin-c:

LA789-RIPE!

tech-c:

LA789-RIPE!

mnt-by:

ONE-MNT!

auth:

MD5-PW $1$gT4W!

auth:

PGPKEY-AE6FBTI7

mntner:

TWO-MNT

admin-c:

XY456-RIPE!

tech-c:

XY456-RIPE!

mnt-by:

TWO-MNT!

auth:

MD5-PW $76$ytE7!

auth:

SSO john@email.net

34

person:

John Smith

address:

Abbey Road 123!

phone:

+31 20 876 5432!

e-mail:

js@example.org!

nic-hdl:

JS123-RIPE!

mnt-by:

ONE-MNT!

mnt-by:

TWO-MNT

Not using a role object

35

inetnum:
person:

John Smith

nic-hdl:
address:
phone:
e-mail:
mnt-by:

JS123-RIPE
Sesame Street 1

+1 555 0101

john@example.org

LIR-MNT

person:

Sue Baker

nic-hdl:
address:
phone:
e-mail:
mnt-by:

SB436-RIPE
Sesame Street 1

+1 555 0202

sue@example.org

LIR-MNT

85.11.184.0/25

tech-c:
SB436-RIPE

JS123-RIPE

admin-c:
SB436-RIPE
JS123-RIPE

status:
PA

inetnum: ASSIGNED
85.11.184.128/25
mnt-by:
LIR-MNT
JS123-RIPE

tech-c:
SB436-RIPE
JS123-RIPE

admin-c:
SB436-RIPE
status:
PA

inetnum: ASSIGNED
85.11.186.0/27
mnt-by:
LIR-MNT
JS123-RIPE

tech-c:
SB436-RIPE
JS123-RIPE

admin-c:
SB436-RIPE
status:
PA

inetnum: ASSIGNED
85.11.186.32/25
mnt-by:
LIR-MNT
JS123-RIPE

tech-c:
SB436-RIPE
JS123-RIPE

admin-c:
SB436-RIPE
status:
PA

inetnum: ASSIGNED
85.11.186.64/26
mnt-by:
LIR-MNT
tech-c:
SB436-RIPE
JS123-RIPE

admin-c:
SB436-RIPE
JS123-RIPE

status:
ASSIGNED
ASSIGNEDPA

PA

mnt-by:
LIR-MNT
LIR-MNT

Role object

person:

John Smith

nic-hdl:
address:
phone:
e-mail:
mnt-by:

JS123-RIPE
Sesame Street 1

+1 555 0101

john@example.org

LIR-MNT

person:

Sue Baker

nic-hdl:
address:
phone:
e-mail:
mnt-by:

SB436-RIPE
Sesame Street 1

+1 555 0202

sue@example.org

LIR-MNT

36

role:

nic-hdl:
tech-c:
admin-c:
tech-c:
admin-c:
mnt-by:

LIR Admin
LA789-RIPE

JS123-RIPE
JS123-RIPE
SB436-RIPE
SB436-RIPE
LIR-MNT

Using a role object

person:

John Smith

nic-hdl:
address:
phone:
e-mail:
mnt-by:

JS123-RIPE
Sesame Street 1

+1 555 0101

john@example.org

LIR-MNT

role:

LIR Admin

nic-hdl:

LA789-RIPE

!tech-c:
!admin-c:
!tech-c:
!admin-c:

JS123-RIPE
JS123-RIPE
SB436-RIPE
SB436-RIPE
LIR-MNT

mnt-by:

37

inetnum:

85.11.184.0/25

tech-c:
admin-c:

LA789-RIPE

LA789-RIPE

inetnum:

85.11.184.128/25

tech-c:
admin-c:

LA789-RIPE

LA789-RIPE

inetnum:

85.11.185.0/24

tech-c:
admin-c:

LA789-RIPE

LA789-RIPE

inetnum:

85.11.186.0/27

tech-c:
admin-c:

LA789-RIPE

LA789-RIPE

person:

Sue Baker

inetnum:

85.11.186.32/27

nic-hdl:
address:
phone:
e-mail:
mnt-by:

SB436-RIPE
Sesame Street 1

+1 555 0202

sue@example.org

LIR-MNT

tech-c:
admin-c:
status:
mnt-by:

LA789-RIPE

LA789-RIPE

ASSIGNED PA

LIR-MNT

Route and route6 object

38

inet6num:

2001:db8::/32

aut-num:

AS65432

tech-c:
admin-c:
mnt-by:

LA789-RIPE

JD1-RIPE

RIPE-NCC-HM-MNT

tech-c:
admin-c:
mnt-by:

LA789-RIPE

JD1-RIPE

RIPE-NCC-END-MNT

mnt-routes:

LIR-MNT

mnt-by:

LIR-MNT

route6:

2001:db8::/32

tech-c:
admin-c:
origin:

LA789-RIPE

JD1-RIPE

AS65432

mnt-by:

LIR-MNT

mnt-routes delegates creation of route objects

Reverse delegation
inetnum:

185.9.0.0/22

tech-c:
admin-c:
mnt-by:

LA789-RIPE

JD1-RIPE

RIPE-NCC-HM-MNT

39

mnt-domains: LIR-MNT
domain:

0.9.185.in-addr.arpa

mnt-by:
LIR-MNT

domain:
1.9.185.in-addr.arpa
mnt-by:
END-USRmnt-by:
LIR-MNT

domain:
2.9.185.in-addr.arpa
MNT

mnt-by:
END-USRmnt-by:
LIR-MNT

domain:
3.9.185.in-addr.arpa
MNT

mnt-by:
END-USRmnt-by:
LIR-MNT

MNT

mnt-by:
nserver:
nserver:

END-USR-MNT

ns1.example.com

ns2.example.com

mnt-domains delegates the reverse delegation

Updating the
RIPE Database
Demonstration

Questions?

41

Being an LIR
Section 3

LIRs responsibilities

Make assignments following RIPE policies

Register
assignments
in
the
RIPE
Database

Keep this information up-to-date

43

RIPE NCC Access

Personalised functionality on RIPE website

No need to be an LIR to have an account

44

RIPE NCC Access is our single sign-on system.

http://access.ripe.net

LIR Portal

45

View all allocated/assigned resources

Provides access to IP management tools and
The LIR Portal lets you manage your registry

RIPE NCC services

http://lirportal.ripe.net

46

LIR Portal

RIPE NCC!
Access

RIPE NCC Services

And more

LIR Portal
Demonstration

Closing LIRs

48

The RIPE NCC may close an LIR if:

The LIR cannot be contacted by the RIPE NCC for a

significant period of time

The LIR consistently violates RIPE communitys policies

The LIR does not pay its fee

The RIPE NCC takes on responsibility for address

space held by closing LIRs

Being an LIR contact

Exercise

Exercise: Being an LIR Contact

Time

15 minutes

Goal

Understand the tasks of an LIR contact

Scenario

It is your first day as an LIR contact. In which order

would you complete these tasks?

50

Getting resources
Section 4

Terminology

Allocation

Block of IP addresses reserved for future use

Assignment

A chunk of addresses from an allocation that is used:

in your own infrastructure

in an End User network

52

Allocation and Assignment

53

RIPE NCC

LIR

End User

Allocation

PA Assignment

PI Assignment

Sub-allocations

54

LIR

DOWNSTREAM
ISP / LIR

End User

PA Allocation

PA Sub-allocation

PA Assignment

Types of address space

Provider Aggregatable (PA)

Assignments made from members allocation

Allocated to LIR / Assigned by LIR

Address space remains with LIR

Customer has to renumber when changing ISP

Provider Independent (PI)

Assignment made directly by the RIPE NCC

Assigned to End User

End User takes the address space with them

55

First IPv6 allocation

Create mntner, person and role objects

Use the new organisation startup tool

Submit the First IPv6 Allocation Request form

Have a plan for making assignments within two years

Minimum allocation size is /32

Up to a /29 without additional justification

More if justified by customer numbers and the extent of

the infrastructure

56

IPv4 allocation from the last /8

Must already hold IPv6 allocation

or sub-allocation

Request IPv4 resources:

Submit the IPv4 Allocation Request form

Members can get one /22 (=1024 addresses)

57

Types of IPv4 transfers

PA allocations between RIPE NCC members

Due to merger or acquisition
From
legacy
space

PI
assignments
between
end
users

58

IPv4 allocation transfers

Only between RIPE NCC members

No minimum allocation size
Evaluated
by
the
RIPE
NCC

Cannot transfer same block again within 24 months

Transfers can be permanent or temporary

59

IPv4 PI assignment transfers

No minimum/maximum block size

Oering & Receiving parties must have a

sponsoring LIR before transfer takes place

Evaluated by the RIPE NCC

Cannot transfer again same block or parts of

the transferred block within 24 months

Transfers can be permanent or temporary

Documentation and objects from new user
are required

60

IPv4 Transfers: where to look

IPv4 Listing Service

Accessible from LIR Portal account

Brokers

Listed on RIPE NCC website

NOT endorsed by RIPE NCC

Signed an agreement to conform to RIPE Policies

61

IPv4 Transfers: how to request it

Send an email to lir-help@ripe.net

Include the following information & documents:

IPv4 blocks(s) being transferred

company names and contact details

company registration papers

IPv4 Transfer Agreement

For PI transfers, sponsoring LIR agreement is needed too

62

Requesting an IPv6 PI Assignment

63

Every PI Assignment must have a Sponsoring LIR

Needs organisation, person and mntner objects
Minimum size = /48
Send us:

PI Assignment Request Form

End User Assignment Agreement

Company registration document or picture ID (for a

private individual)

IPv6 PI Assignments

64

PI space cannot be used for sub-assignments!

Not even a single address for the connection

If you have customers, you cannot use PI for them

inet6num: 2001:db8::/48
inet6num:
2001:db8:1234::/48

descr:!
status: !
mnt-by:
mnt-lower:
mnt-by:
mnt-routes:
mnt-domains:

!
!

LIR PI Assignment !
ASSIGNED PI!
RIPE-NCC-END-MNT!
RIPE-NCC-END-MNT!
ENDUSER-MNT!
ENDUSER-MNT!
ENDUSER-MNT

Yearly charges for PI Assignments

See the RIPE NCC Charging Scheme

IPv4 PI Assignments

Can
be
transferred
to
another
end
user

No sub-assigning allowed
Yearly charges for PI Assignments

Since IPv4 exhaustion, no new PI assignments

See the RIPE NCC Charging Scheme

65

Autonomous System numbers

Assignment requirements

Address space

Multihoming

One AS Number per network

For
End
User

For LIR itself

Sponsoring LIR requests it for End User

32-bit is the default

16-bit available on request

66

PI / ASN without sponsoring LIR

Sign End User Agreement with the original LIR

- or -

Find a new sponsoring LIR

Become
an
LIR

Return
the
resources

Sponsoring LIR is published in the RIPE DB

Known as 2007-01 project

67

Questions?

68

Distributing resources
Section 5

How much address space?

70

Think about how the network will be split up

Subnets are used to group hosts

Production
Servers
Guest VLAN

NOC VLAN
Customers

Calculate how much address space you will need!

IPv4 subnets

71

gateway

network

broadcast

255

3 IPs required per subnet

network

broadcast

gateway

Usable IPs = [subnet size] - 3 IPs

/24 = 256 IPs = 256 - 3 = 253 usable IPs

IPv6 subnets

72

/64 = 1 subnet = 18,446,744,073,709,551,616 IPs

/60 = 16 subnets

/56 = 256 subnets

/52 = 4096 subnets

/48 = 65536 subnets

In IPv6
the amount of hosts
in a subnet is
irrelevant!

Making assignments
Exercise

Exercise: Making assignments

Time

30 minutes

Goal

Understand and practice the Assignment Process

Task

Ask the End User for more information, if needed

Decide the assignment sizes

74

IPv4 resources

LIRs are allocated only one /22

More IPv4 space through transfers

Assignment size is limited to total of IPv4 space an

LIR holds

All assignments must be registered correctly

in the RIPE Database

http://www.ripe.net/ripe/docs/ipv4-policies.html

75

IPv4 registration in the database

76

All assignments and sub-allocations must be

registered to make them valid!
inetnum:
descr:!
country:
admin-c:
tech-c:
status: !
mnt-by:

10.0.3.0 - 10.0.3.255
Customer 847!
EU!
inetnum: 10.0.2.0 - 10.0.2.255
LA789-RIPE!
LA789-RIPE!
descr:!
Customer 593!
ASSIGNED!
country:
EU!
inetnum: 10.0.1.0 - 10.0.1.255
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
LA789-RIPE!
descr:!
Customer 246!
status: !
ASSIGNED! EU!
country:
inetnum: 10.0.0.0 - 10.0.0.255
mnt-by:
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
LA789-RIPE!
descr:!
Customer 321!
status: !
ASSIGNED! EU!
country:
mnt-by:
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
status: !
mnt-by:

LA789-RIPE!
ASSIGNED PA!
LIR-MNT

IPv6 assignments

Default IPv6 subnet = /64

Every end site can be assigned between /64

77

and /48 without prior approval of the RIPE NCC

For larger assignments, send in request form

Assignments for your own infrastructure

/48 per Point of Presence

Additional /48 for the core network

IPv6 registration in the database

78

All assignments and sub-allocations must be

registered to make them valid!
inet6num:

2001:db8:dddd::/48

descr:!
country:
admin-c:
tech-c:
status: !
mnt-by:

Customer 847!
EU!
inet6num: 2001:db8:cccc::/48
LA789-RIPE!
LA789-RIPE!
descr:!
Customer 593!
ASSIGNED!
country:
EU!
inet6num: 2001:db8:bbbb::/48
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
LA789-RIPE!
descr:!
Customer 246!
status: !
ASSIGNED! EU!
country:
inet6num: 2001:db8:aaaa::/48
mnt-by:
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
LA789-RIPE!
descr:!
Customer 321!
status: !
ASSIGNED! EU!
country:
mnt-by:
LIR-MNT
admin-c:
LA789-RIPE!
tech-c:
status: !
mnt-by:

LA789-RIPE!
ASSIGNED!
LIR-MNT

Grouping customer assignments

inet6num:

2001:db8::/36

descr:!
admin-c:
tech-c:
status: !
assignment-size:
mnt-by:

DSL customers!
LA789-RIPE!
LA789-RIPE!
AGGREGATED-BY-LIR!
48!
LIR-MNT

inet6num:

79

2001:db8:103::/48

descr:! 2001:db8:102::/48
Customer 321!
inet6num:
country:
EU!
descr:!
Customer
321!
inet6num:
2001:db8:101::/48
admin-c:
LA789-RIPE!
country:
tech-c: EU! LA789-RIPE!
descr:!admin-c:
Customer
321!
inet6num:
2001:db8:100::/48
LA789-RIPE!
status: !
ASSIGNED!
country:
EU!
tech-c:
LA789-RIPE!
mnt-by:
LIR-MNT
descr:!
Customer
321!
admin-c:
LA789-RIPE!
status: !
ASSIGNED!
country:
EU!
tech-c:mnt-by: LA789-RIPE!
LIR-MNT
admin-c:
LA789-RIPE!
status: !
ASSIGNED!
tech-c:
mnt-by: LA789-RIPE!
LIR-MNT
status: !
ASSIGNED!
mnt-by:
LIR-MNT

Infrastructure vs. End User

Infrastructure
!

80

End User
!

Blocks for connections to End

Users:

Their equipment,
their location

Point of Presence
Point-to-Point
Broadband address pools

End User networks

Offices
Co-located subnets

(Also LIRs own network)

Infrastructure vs. End User

Infrastructure
!
Blocks for connections to End
Users:

Point of Presence
Point-to-Point
Broadband address pools

!
Grey Area
!
!

Co-location
Server housing
Web hosting
Application Services

81

End User
!
Their equipment,
their location

End User networks

Offices
Co-located subnets

(Also LIRs own network)

When the End User has

a few addresses out of
a larger address block

If the End User has

a separate subnet

Registering the
assignments
Exercise

Exercise: Registering an assignment

Time

15 minutes

Goal

Practice how to register an assignment

Use the assignment from previous exercise

Task
Choose the range(s) from your allocation

Create the inetnum and inet6num objects in the

TEST RIPE Database

83

Managing Resources
Section 6

Managing IPv6 address space

Consider your mental health

Use assignments on 4-bit boundary

Dont be too conservative

Business customers often get a /48

/56 is a popular size for residential customers

Use AGGREGATED-BY-LIR

to group assignments of the same size

85

IPv6 Analyser

86

Managing IPv4 address space

LIRs get only one last /22 allocation

Its up to the LIR to manage it eciently

Need is not a criteria for obtaining more

IPv4 address space

Keep the RIPE database up to date

You can see how many IPs you have unused

87

IP Analyser

88

ARC

Assisted Registry Check

89

ARC Goals

Keep registry clean and up to date

Make you aware of any inconsistencies with

the registry data

Support the LIR with their registration tasks

Keep in touch with members

90

ARC Procedure

91

An IPRA will be
assigned to the task
Checks many aspects
of the registry
Sets up a call to talk
about the registry
Helps the LIR take
action, if needed

RPKI digital resource certificates

92

Issue digital certificates along with the registration

of Internet number resources

Two main purposes:

Make the registry more robust

Making Internet routing more secure

Added value comes with validation

The possibility to perform BGP Origin Validation

Using certificates

Certification is a free, opt-in service

Your choice to request a certificate

Linked to your membership

Renewed every 12 months

Available in LIR Portal

Certificate does not list any identity information

That information is in the RIPE Database

and youre authorised to announce it

Digital proof you are the holder of a resource

93

Questions?

94

Tips and Tools

Section 7

IPv4 management tips

Make a plan before distributing the last /22

How many addresses do you have left?

Do you need any IPv4 for a transition mechanism?

How does IPv4 exhaustion aect your organisation?

Do not waste IPv4 addresses

Make classless assignments

Do not fragment your allocation

Document assignments: whos using your IPs?

inetnum does not have to be CIDR

96

Protect your resources

Keep
your
LIR
contacts
in
the
LIR
Portal
up
to
date

Know
the
policies
and
procedures

In case of questions, contact

Maintain your contact info in the RIPE database

Registration Services

lir-help@ripe.net

97

Lost maintainer password

Go to https://apps.db.ripe.net/change-auth/
Automated process

Recovery link sent to upd-to: email address

Manual process

Send statement & registration papers to us

After verification, we will send you an email with the

recovery link

We will add your Access account to the maintainer

98

RIPE NCC Resource quality assistance

99

Address distribution - no claims about routability

Assistance in case of filtering issues:

Help to establish a direct communication

Provide available contact details

Provide information about tools

To reduce routability problems, the RIPE NCC:

Announces pilot prefixes of every newly allocated IP

address block

Quarantines returned IP address space

RIPEstat

100

One-stop-shop for viewing all IP-resource

related data from RIPE NCC

Registry data, routing, reverse DNS,

measurements & 3rd-party data
Main interface: web-based widgets

also available as: CLI, data API & mobile

personalised via RIPE NCC Access

http://stat.ripe.net

RIPE Atlas - active measurements

Next generation Internet measurement network

Gives a big picture about Internet trac

User
Defined
Measurements
available
for
LIRs

Currently around 7,500 active probes worldwide

ping, traceroute, DNS, SSL

Set up IPv6 reachability test

http://atlas.ripe.net

101

RIPE Labs

102

A place to showcase new and interesting

Internet related developments

Anyone can:

Present research

Showcase prototype tools

Share operational experience

Exchange ideas

http://labs.ripe.net

Questions?

103

RIPE NCC Academy

Graduate to the next level!

http://academy.ripe.net

104

Feedback!

https://www.ripe.net/training/lir/feedback

105

Follow us!

@TrainingRIPENCC

106

The End!

Y Diwedd

Ende
Konec

Beigas

Lpp

Fine

Einde

Liugt

Finvezh
nn

Kraj

Vge
Endir

Finis
Ki

Fund
Son

An Croch

Sfrit

Fin
Slut

Pabaiga
Fim

Amaia

Loppu

Kpaj

Tmiem

Slutt
Koniec