What is an LIR?

RIPE NCC 

Local Internet Registry 

Training Course 

LIR Training Course 

Spring 2007 

http://www.ripe.net 

1

Learning Goals 

• Your responsibilities as LIRs 

• IP resources administration 

• Efficient communication with the RIPE NCC 

LIR Training Course Spring 2007 

http://www.ripe.net 2

Overview 

1. Introduction to the RIPE NCC 

2. Being an LIR 

3. The RIPE Database 

4. Making Assignments 

5. Assignment Window 

6. Managing Allocations 

7. PI Address Space 

8. IPv6 

9. Reverse DNS 

10. ASN 

11. RIPE & Policy Development Process 



1. Introduction to the RIPE NCC 

• RIPE 

• RIPE NCC 

• Internet Registry System 


Spring 2007 


4

RIPE and RIPE NCC 

• Réseaux IP Européens (1989) 

- collaborative operators’ community for coordinating 

IP infrastructure development 

- open to all 

- developing policies; input to the RIPE NCC 

• RIPE Network Coordination Centre (1992) 

- independent not-for-profit membership organisation 

- one of five Regional Internet Registries (RIRs) 



RIR Service Regions 



Problem 

Internet Registry System Goals 

Uniqueness and 

contact details 

Routing table 

growth 

Limited resource 

Solution 

RIPE Database 

Scalable routing 

Efficient use 


Principle/Goal 

Registration 

Aggregation 

Conservation 


Hierarchical Distribution 



RIPE NCC Services 

Member Services 

• IP resources 

- IPv4 

- IPv6 

- AS Numbers 

• Reverse DNS delegation 

• Training courses 

- LIR 

- Routing Registry & Tools 

- DNS for LIRs 


Public Services 

• RIPE Database 

– Routing Registry 

• RIPE support 

• Spreading information 

• ENUM (e164.arpa) 

• K-root name server 

• Test Traffic Measurements* 

• DNSMon* 

• E-Learning 




Influencing RIPE NCC 

Members attending 

RIPE NCC General Meeting 

vote on Charging Scheme 

RIPE NCC proposes yearly 

Activity Plan and Budget 

RIPE proposes actions 



Organisation Structure 


Spring 2007 


12

Budget and Charging Scheme 

• RIPE NCC is not-for-profit 

- activities determined by RIPE; expenses based on activities 

- money comes from (yearly) membership fees 

- money split from between existing and projected new / closed LIRs 

• Your fee / category depends on: 

• your "score“ and “scores" of all the other LIRs 

• “draft income budget” 

• Your billing score based on: 

• units and formula in (yearly) "Charging Scheme“ 

• Score matched to category in "Billing Procedure“ 

- document published only after the approval of GM (Oct.) 

- category can not be guessed beforehand! 

• Billing phases 



RIPE NCC: Learning Points 

• The RIPE NCC is not RIPE 

• You can influence RIPE NCC activities 

• Remember: aggregation, conservation, registration 

Questions? 


Spring 2007 


14

2. Being an LIR 

• Benefits and Responsibilities 

• Terminology 

• Set-Up Procedure 



What is an LIR? 

• Local Internet Registry 

- responsible for obtaining, distributing and registering 

IP resources, according to the RIPE policies 

• Member of the RIPE NCC 

- receiving resources directly from the RIPE NCC 

• Benefits 

- flexibility 

- independence (BGP multihoming) 



Allocation and Assignment 

/24 

/21 

/25 /26 


/8 

RIPE NCC Allocation 

LIR Allocation 

End User Assignments 

or LIR’s Infrastructure 


Terminology 

• Allocation: 

- address space set apart, by the RIPE NCC for LIR’s and 

its customers’ future use 

• Assignment: 

- address space in use in networks 

(End User, downstream ISP or LIR’s own infrastructure) 

- made from allocation or sub-allocation 

• Assignment Window: 

- maximum nr of addresses an LIR can assign without 

RIPE NCC’s approval. New LIR: AW=0 



PI versus PA Assignments 

No Aggregation 

BGP Announcements (4) 

ISP 

Customer Assignments 

Provider Independent 

(Portable Assignments) 


Aggregation 

BGP Announcement (1) 

Customer Assignments 

Provider Aggregatable 

(Non-portable Assignments) 

LIR 

Allocation 


Classless Addressing 

• Classful addressing (’80-’93) now obsolete 

- waste of addresses; routing table growth 

• ’93: Classless Inter Domain Routing (CIDR) 

– flexible allocation / assignment sizes 

– w.x.y.z/nn notation 

• CIDR implemented in all modern routing protocols 

• CIDR used for address space distribution 



LIR Set-up Process 

• Steps 

- read policy documents 

- apply for membership 

• RegID, contacts 

- pay the fees 

- sign the contract 

• Next steps 

- LIR: register RIPE Database contact data 

- RIPE NCC: “Reg” file, “organisation” object 

- LIR: activate LIR Portal account 



Sources of Contact Information 

LIR Portal 

• RIPE NCC confidential 

- access only by “users” 

• “admin” creates “users” 

• “users” create “contacts” 

• Log-in: Reg-ID, user, pwd 

Reg File 

• RIPE NCC “contacts” can: 

- request resources 

- update contact info 

• Use: Reg-ID, name 


RIPE Database 

• Public info 

- access by anyone 

- updates by anyone 

• Operational contacts 

- troubleshooting 

• Responsibility over 

registered resources 

• Use: nic-handle 

• Additional authorisation: 

using “maintainer” 


First IPv4 Allocation 

• If you 

- want independent addresses 

- have an estimate of usage for two years 

- know how much space needed in first six months 

• Send us 

- “IPv4 first allocation request form” 

- PA assignment request form for infrastructure 

- PA assignment request form for each customer 

• Slow start: minimum initial allocation size /21 



Being an LIR: Learning Points 

• You are part of the global Registry System 

• Think CIDR! 

• LIR Portal: main interface 

Questions? 


Spring 2007 


24

3. The RIPE Database 

• Creating contact information objects 

• Protection 


Spring 2007 


25

RIPE Database Contact Info 

• All LIRs must have 

-person object 

- maintainer (mntner) object 

-organisation object 

-role object, use it! 

• To create / update object 

- use “webupdates”; or 

- “syncupdates”; or 

- e-mail completed template to 



Creating person Object 

person: John Smith 

address: Herengracht 258 

phone: +31 20 535 4444 

e-mail: john.smith@bluelight.net 

abuse-mailbox: abuse@bluelight.net 

nic-hdl: auto-1 

changed: j.smith@bluelight.net 20051031 

source: RIPE 


JS5888-RIPE 


Contact Person Leaves 

1. Get all the relevant objects (inetnum, aut-num, etc) 

2. Create new person object 

3. Change the “tech-c:” reference in all objects 

4. Delete old person object 

inetnum: 

80.35.64.80 

JAJA1-RIPE 

CD2-RIPE 

... 

inetnum: 

80.35.64.130 

CD2-RIPE JAJA1-RIPE 


person: 

CD2-RIPE 

person: 

JAJA1-RIPE 


inetnum: 

80.35.64.80 

JAJA1-RIPE 

BL7-RIPE 

inetnum: 

80.35.64.130 

Better if Using Role Object 

1. Create one person object for each technical contact 

2. Create one new role object for all technical contacts 

3. In all inetnums: change “tech-c:” to refer to role object 

4. Keep role object up-to-date 

... 

BL7-RIPE JAJA1-RIPE 


role: 

BL7-RIPE 

CD2-RIPE 

JAJA1-RIPE 

person: 

CD2-RIPE 

person: 

JAJA1-RIPE 


RIPE Database Protection 

• mntner holds the password / key for authorisation of updates 

of other objects 

• Include “mnt-by: NAME-MNT” in all objects! 

- for updates: include “password: bla” or sign 

• Authentication methods: 

- CRYPT-PW deprecated ! 

- MD5-PW 

• encryption web interface available 

- PGPKEY- 

- X509- 

• Forgot password? Go to RIPE DB > DB Support > Security 



Multiple Protection Illustrated 

person: John Brown 

mnt-by: ONE-MNT 

mnt-by: TWO-MNT 

mntner: ONE-MNT mntner: TWO-MNT 

auth: MD5-PW $glg87^&$%xy auth: MD5-PW $bla34^&$%bla. 

auth: PGPKEY-AE6FBBF7 

•In order to update this person object, need to have: 

– Either the first MD5-PW password 

– Or the second MD5-PW password 

– Or the PGP key 



Hierarchical Authorisation 

inetnum: 85.118.184.0/21 

status: ALLOCATED PA 

mnt-by: RIPE-NCC-HM-MNT 

mnt-lower: LIR-MNT 

inetnum: 85.118.186.0/24 

status: ASSIGNED PA 

mnt-by: LIR-MNT 


Allocation 

Assignment 


RIPE Database: Learning Points 

• Modify objects on-line 

• Easier administration with role objects 

• Protect data in all objects 

Questions? 


Spring 2007 


33

4. Making Assignments 

• Assignment process 

• Policy 

• Registering assignments in the DB 


Spring 2007 


34

Assignment Policies 

• Policies help LIR in finding compromise 

- End User wishes versus Registry System goals 

- Conservation versus aggregation 

• LIR’s responsibility to implement policies 

• If you don’t like current policies, you can change 

them! 



Get it Right 

• Before sending PA request, read: 

- FAQ, “Quick Tips” 

- “IPv4 Address Assignment and Allocation Policies” 

- “The LIR Handbook” 

• Request online via LIR Portal 

- or “PA Assignment Request Form” 

- or “PA Assignment Wizard” via LIR Portal 

• Not more than 5 requests at a time 



Assignment Process, AW=0 

LIR Collects Information 

LIR Evaluates Request 

LIR Chooses Addresses 

LIR Keeps Documentation 

LIR Registers in RIPE DB 


Approach RIPE NCC 

RIPE NCC 

evaluates 


Step 1: LIR Collects Information 

• Why? 

- To determine the operational need 

- To justify the decision 

• Info needed 

- Contact details 

- Network setup 

- Current address space usage 

- Address space requirements 

- Future plans 

• Confidential, local language 



Step 2: LIR Evaluates Request 

• Current address space 

• Returning addresses? 

– Renumbering encouraged! 

• All subnets classless 

• Planning of growth two years ahead maximum 

- utilisation: 25% now, 50% in one year 



Step 3: LIR Makes Decision 

• Size 

- Based on demonstrated need 

• For End User? For own Infrastructure? 

• Classless 

- “/23 & /25” or /27… not always /24 

• Range 

- Your choice 



Step 4: Request Form 

• General Information 

• Address Space User 

• Addressing Plan 

• Equipment description 

• Network description 

• Network diagram 

• Example of the completed form 

- for the small ISP Laika, customer of the LIR Bluelight 



Separate Request Forms for: 

• Each End User network 

• LIR’s own infrastructure 

- can be a single request form for the whole block 

- separate subnet for each type of usage 



Portal Communication 

Use the same 

ticket number 

Portal Request Form 

Real time syntax checks 

Ticket created 

Request queued 

LIR answers 

e-mail 

Human (analyst) 

e-mail 

yes 

Questions? 


no 

Approval 

RIPE NCC 

Evaluation 


Email Communication 

LIR fixes errors 

Use the same 

ticket number 

LIR answers 

PA Assignment 

Request Form 

 

yes 

Ticket created 

Syntax checks 

no 

correct? 

yes 

Request queued 

Human (analyst) 

Questions? 

no 

Approval 


Always include: 

-Reg-ID 

- your name 

RIPE NCC 

Evaluation 


RIPE NCC Evaluates Requests 

• Based on “IPv4 Address Policies” document 

- Dynamic assigning encouraged 

• not static 

- More than /20: usage statistics verification 

• Always-on technologies: xDSL, cable, GPRS… 

- Name-based virtual web hosting encouraged 

• not IP-based 

• exceptions: SSL, ftp & mail servers... 



Approval 

• RIPE NCC sends approval message to LIR 

- Size 

- “netname:” 

- Date 

• ticket closed 

• LIR keeps approval message 

• keep all original documents too 

• contract with customer 

• Next steps 

- LIR chooses addresses 

- LIR creates inetnum object 



Step 5: LIR Registers in RIPE DB 

• Validity 

• Uniqueness 

• Overview 

- range 

- netname 

• Contact info 

- admin-c 

- tech-c 

• inetnum must match internal documentation 



Registering End Users Separately 

• Obligatory. Benefits: 

- Abuse complaints can go directly to End User 

- Network operators can block End User prefix 

• Why? In case of attack by your End Users on 

other networks 



Making Assignments: Learning Points 

• Shown for AW=0 

• Evaluate End User needs 

• Always register End Users separately 

Questions? 


Spring 2007 


49

5. Assignment Window 

• AW Definition 

• Assignments above/within the AW 

• Assignments for LIR’s Infrastructure 


Spring 2007 


50

Assignment Window Concept 

• Maximum number of IP addresses the LIR can assign 

without approval from the RIPE NCC 

• For each End User, within any 12 months 

• New LIR, AW = zero 

• RIPE NCC increases AW gradually 

• What is my AW size? 

− LIR Portal 

− “reg” file 



Ask for Approval if… 

• Request is above AW: 

– This request and all previous assignments you made 

without the RIPE NCC to the same End User in the last 

12 months 

– New LIR’s AW=0 – need approval for every 

assignment! 



Assignment Process 

LIR Collects Information 

LIR Evaluates Request 

request > AW? 

no 

need 

2nd opinion? 

no 

yes 

LIR Chooses Addresses 

LIR Keeps Documentation 

LIR Registers in RIPE DB 


yes 

Approach RIPE NCC 

RIPE NCC 

evaluates 


Assignments within AW 

LIRs’ Responsibilities : 

• Evaluate all requests 

• No need for approval 

• Keep documentation for all assignments 

- RIPE NCC may ask for it later 

• Register all assigned networks in RIPE DB 

- choose netname 



Assignments for LIRs’ Infrastructure 

• LIR can make multiple assignments to own infrastructure. 

Each assignment = or < AW 

• In inetnum object: separate attribute: 

remarks: INFRA-AW 

• Only if assignment hasn’t been requested! 

• Cannot be merged 

• Keep documentation to justify assignments 

• Assignments > AW : send request to the RIPE NCC ! 



Infrastructure versus End User 

• LIR / ISP infrastructure 

• blocks for co-location: server housing, web hosting 

• blocks for connection to End Users (dial-up, P2P) 

- Within AW: assign and register as one block 

- Bigger than AW: request on one form 

• End User network 

• their equipment, their location (usually more than four IPs) 

- Within AW: assignment and inetnum for each End 

User 

- Bigger than AW: one request form for each End User 



Object Created but Invalid 

(for End User or LIR’s infrastructure) 

• RIPE Database syntax checks passed, but… 

• Assignment not valid if inetnum : 

- Bigger than AW, but not approved by the RIPE NCC 

- Overlapping 

- Not separate for separate organisations 

• Invalid assignments 

- delay AW increase, additional allocations 

- cause extra work 



When Is the AW Raised ? 

• Correct requests 

• Policies applied 

• Valid DB objects 

• AW = average size of requests 

• If you want the AW raised 

- approach RIPE NCC: 



Assignment Window: Learning Points 

• New LIR: AW=0 

• Assignment > AW: send request for approval 

• Assignment < AW: evaluate & assign yourself 

Questions? 


Spring 2007 


59

6. Managing Allocations 

• Choosing the address range 

• Managing RIPE Database data 

• Requesting new allocation 


Spring 2007 


60

Grouping and Splitting 

• Grouping assignments 

- Per service, location, customer size ? 

- Fragmentation ? 

• Splitting your allocation 

-status: SUB-ALLOCATED PA 

-status: LIR-PARTITIONED 

Customers 

20% 


Infrastructure 

POP 1 POP2 

p 

2 

p 

loops 


Sub-allocation Policy 

• From LIR to Downstream ISP 

- No approval needed 

• Up to four times AW 

- For each Downstream ISP within 12 months 

- Minimum /24; maximum /20 

• LIR registers inetnum 

- Use Downstream ISP’s maintainer in “mnt-lower:” 

• Assignments from sub-allocations 

– AW rules also apply 



Using Sub-allocation 

BlueLight’s Allocation 

Sub-allocation for 

ISP INOX and 

all its (future) 

customers 

INOX makes assignments for its own 

infrastructure and for its End Users from 

its sub-allocation 


status: ALLOCATED PA 

status: SUB-ALLOCATED PA 



Finding Assignments 

• RIPE DB: hierarchical (-m, -M, -l, -L) 

- More & less specific address ranges 

- Grouped by relevance (to group by type: use “-G”) 

• Email addresses in objects filtered 

- Use “-B” to show whole object 

• Not interested in person objects? 

- Use non-recursive lookup (“-r”) 

- Prevents being blocked for too many person object queries 

• Limiting search to inetnums? 

“-T inetnum” 

• Inverse lookups (-i) 



Need New IPv4 Allocation? 

• 80% used (assigned and sub-allocated)? 

- Or: large request pending 

• Assignment Window used correctly? 

- have documentation about assignments? 

- approved assignments still valid? 

• Correct RIPE Database objects? 

• Tools: asused and “Web Asused” 



Correcting Invalid Objects 

• Larger than AW, but not requested? 

- Send request for approval 

• and update the “changed:” line date 

• Not-matching approved “netname:”? 

- Ask to update the Reg file 

• “Subject:” original “ticket number” 

• “Changed:” line date before the approval date? 

- Update the "changed:" line date 

• Overlaps? Delete wrong inetnum 

• Assignment no longer in use? 

- Inform 

• “Subject:” original “ticket number” 

- Delete the inetnum 



Making New IPv4 Allocation 

• Inconsistencies? 

- LIR corrects data / agrees on deadline 

- RIPE NCC reviews AW 

• RIPE NCC allocates new block 

- and creates allocation inetnum 

- Size depends on previous usage rate 

• LIR can start announcing the whole new prefix 

- As one aggregate 

- LIR creates route object 



Managing Allocations: Learning Points 

• Choose the range carefully 

• Keep the RIPE Database tidy 

• “asused” 

Questions? 


Spring 2007 


68

7. PI Address Space 

• Definition 

• Requesting 

• Responsibilities 


Spring 2007 


69

PA versus PI Assignments 

• Provider Aggregatable assignments 

- LIR assigns to End User 

- Must renumber when changing providers 

- Only way to effectively scale the Internet! 

• Provider Independent assignments 

- RIPE NCC assigns to End User 

- Portable 

- Can be difficult to route 

- Next assignment not aggregatable 

- Affects yearly fee 

- Increases size of the routing tables 



Requesting PI Space 

• Explain consequences to End User 

• Create RIPE Database objects 

-person/role, mntner, organisation 

• Send request on behalf of End User 

- LIR Portal, 

- or “PI Assignment Request Form” 



Evaluation of PI requests 

• Additional questions 

- Why does End User want PI (and not PA)? 

- Requesting extra address space for routing? 

- Aware of consequences? 

• Same criteria as for PA assignments 

- Conservative estimates 

- Classless 

• Assignment is only valid as long as original criteria 

remain valid 



PI Responsibilities 

• RIPE NCC 

- Assigns to End User 

- Creates inetnum 

• LIR 

- Makes contracts with End Users 

- Helps End Users with reverse DNS, route objects 

- Helps End Users if changing provider 

• End User 

- Maintains objects 

- Must not assign further 



PI Address Space: Learning Points 

• PA recommended 

• LIR requests PI space for End User 

• Shared responsibilities 

Questions? 


Spring 2007 


74

8. IPv6 Address Space 




Spring 2007 


75

First IPv6 Allocation 

• If you 

- a) are an LIR 

- b) not an End Site 

- c) plan to provide IPv6 connectivity to aggregated 

‘customers’, who are assigned /48s 

- d) plan to assign 200 /48s within two years 

• Send us “IPv6 first allocation request form” 

• Minimum initial allocation size /32 

– Assignment policy being discussed 



IPv6 Assignments 

• Usual assignment size - /48 for each “site” 

- End User network 

- LIR infrastructure (per PoP) 

- No approval needed 

• Smaller size 

- /64 just one subnet 

- /128 just one device 

• Multiple /48 for very large End Users 

- Approval needed 



New IPv6 Allocation 

• HD ratio = 0.8 usage of previous allocation 

- 7132 /48s assignments in a /32 

• Correct registrations (all /48s registered) 

• New allocation’s size: the same as the first 

- Resulting in IPv6 prefix one bit shorter 

- Or bigger if justified (sufficient for two years) 



3 

IPv6 Format 

/23 

16 bits 

16 bits 

/32 /48 /64 


64 bits 

/128 


IPv6 Address Space: Learning Points 

• Allocation 

• Assignment 

Questions? 


Spring 2007 


80

9. Reverse DNS 


• Domain objects 



Spring 2007 


81

Why Reverse DNS? 

• Mapping IP numbers to domain names 

• Needed for applications (mail, IRC, ftp) 

- Troubleshooting (traceroute) 

• LIR’s responsibility 



inet(6)num and domain Objects 

inet6num: 2001:0888::/32 

status: ALLOCATED-BY-RIR 

mnt-by: RIPE-NCC-HM-MNT 

mnt-domains: LIR-MNT 

domain: 8.8.8.0.1.0.0.2.ip6.arpa 


inetnum: 85.118.190.0/24 



mnt-domains: END-USER-MNT 

domain: 190.118.85.in-addr.arpa 

mnt-by: END-USER-MNT 



Preparations 

• Decide on the address range 

- Whole allocation? Assignment? 

- IPv4: One or more /24, /16 

- IPv6: One or more /36, /32 

• Decide who will be responsible 

- LIR? 

- End User? (create mntner) 

• Allow hierarchical authorisation 

- Add appropriate mntner in the “mnt-domains:” of 

the inetnum object 



Set-up & Request 

• Configure DNS server for chosen zones 

- RFC 1912, RFC 2182 

• Find the secondary server 

- ns.ripe.net mandatory for IPv4 /16 

• Request = submit domain object to RIPE DB 

nserver: ns.bluelight.nl 

nserver: ns2.pinklight.de 



What Will Be Checked 

1. RIPE Database syntax 

2. Authentication 

- “mnt-domains:” in corresponding inetnum 

and 

- “mnt-by:” in domain 

3. Name servers setup 

• Errors / warnings: ask 

• Success: RIPE NCC updates parent zone 



Sizes Other than /24 

• Multiple /24 delegations 

- Can be requested as one domain object 

- Use “shorthand” notation for consecutive zones 

- Broken down & then registered as multiple objects 

• Smaller than /24 delegation 

- End User can run own primary nameserver 

- LIR requests delegation for whole /24 

- LIR uses CNAME (RFC 2317) 

- Reverse DNS for PI addresses done by the RIPE NCC 



Reverse DNS: Learning Points 

• Important service to End Users 

• Whole allocation in one go 

• Request = RIPE Database domain object 

Questions? 


Spring 2007 


88

10. Autonomous System Numbers 

• ASN 

• requesting 

• route object 


Spring 2007 


89

Autonomous System 

• RFC 1930: 

- “An AS is a connected group of … IP prefixes … which 

has a single and clearly defined routing policy.” 

• LIR can request an ASN 

- For own network, or for another organisation 

• Assignment criteria: multihomed 

- Unique routing policy 

- E-mail addresses of peers 



Multihomed Routing Policy 

First Peer 

AS64512 

ASNEW 


Second Peer 

AS64513 


aut-num in ASN Request Form 

aut-num: ASNEW 

as-name: Bluelight-ASN 

 

descr: 

org: 

import: 

export: to 

import: from 

export: to 

[... ] 



aut-num Object 

• RIPE NCC creates aut-num object 

-mnt-by: LIR-MNT 

-mnt-routes: End-User-MNT (or LIR) 

-org: “of whoever uses the ASN” 

• When the peering is established, LIR should 

update routing policy 

• AS Number assignment is only valid as long as 

the original criteria remain valid 



32 Bit AS Numbers 

• Problem: no more AS numbers available in 2012 

- Solution: 32 bit AS numbers 

• 2007-2008: 16 bit AS default, 32 bit AS on request 

• in 2009: 32 bit AS default, 16 bit AS on request 

• as of 2010: Only 32 bit AS numbers 

• Don’t wait until 2009! 

- Can you handle your new AS 1.5432 ? 



oute Object 

• route objects: part of Routing Registry 

• LIR creates route/route6 objects for any 

(new) allocations they announce 

- Both “route:” and “origin:” are primary key 

- Complex hierarchical authorisation for creation 

- Used for prefix filtering by some ISPs 



ASN: Learning Points 

• If you want to be multihomed 

• Describe your routing policy 

• Route object recommended 

Questions? 


Spring 2007 


96

11. RIPE and 

Policy Development Process 

• RIPE 

• PDP 

• Participation 


Spring 2007 


97

How RIPE Works 

• Open forum 

• Voluntary participation 

• Decisions by consensus 

• Working groups 

• Not a legal entity 

• Does not develop Internet standards 

• RIPE chair: 

• 



Come to the RIPE Meetings! 

• Two in a year / a week long 

• 300+ participants 

• Working group meetings 

• Plenary 

• RIPE NCC Services Centre 

• Long breaks / social events 

• 2 free tokens for new LIRs 

• Remote participation: webcast, jabber / irc 

• 



Bottom-up Process 



Policy Development Process 

• Proposal (from anyone) 

• Discussion in working group (WG) 

• Review by WG 

- Consensus? Chair announces decision 

• Concluding phase 

- last call for comments 



Your Participation is Needed! 

• What can you do? 

- propose new policy 

• we can help to draft it 

• RIPE NCC Policy Development Officer is your contact 

• filiz@ripe.net 

- comment on other proposals 

- check the drafts & recent changes web page 



Your Participation is Needed (2) 

• How to take part? 

- subscribe to mailing lists 

- come to the meetings 

• watch webcast and use jabber / irc 



Global IPv4 Usage, in /8s 

Available, 49 

~ 19% 

Public reserved, 1 

AfriNIC, 1 

Multicast, 16 

Experimental, 16 

LACNIC, 4 

APNIC, 24 

ARIN, 27 


Private reserved, 1 

Central Registry, 94 

RIPE NCC, 22 

Source: http://www.potaroo.net/ 


Growth of Global Routing Table 

Projected routing table 

growth without CIDR 


Rapid growth due to 

Large number of longer 

prefixes announced 

Deployment 

Period of CIDR 

But the routing 

table still grows 

ISPs 

tend to 

filter 

longer 

prefixes 

CIDR made it work for a while 

last updated 27 January 2005 


RIPE & PDP: Learning Points 

• RIPE is not the RIPE NCC 

• You can influence RIPE policies 

• Join the discussions 

Questions? 


Spring 2007 


106

LIR Training Course: Summary 


Spring 2007 


107

Do You Want to Host 

RIPE NCC Training Courses? 

• You will provide: 

- Location with lunch facilities 

- High speed Internet connection 

• The RIPE NCC will: 

- Provide the Training Course 

- Announce the Training Course at your location 

- Register the attendees 

- Send the training material to your location 

• The RIPE NCC will pay for: 

- Catering (Food and drink) 

- Travel and accommodation for the RIPE NCC trainers 

- Shipping the training material 

• http://www.ripe.net/training/hosting.html 



The End! 

ﺔﻳﺎﻬﻨﻟا 

Konec 

Lõpp 

Fine 

Fim 

Einde 

Kraj 

ף וסה 

დასასრული 

Соңы 

Ende 

Vége 

Endir 

Kрай 


Վերջ Fí 

Son 

Fund 

Sfârşit 

Конeц 

Pabaiga 

Liðugt 

An Críoch 

Slut 

نﺎﻳﺎﭘ 

Fin 

Amaia Loppu 

Tmiem 

Y Diwedd 

Finis 

Kiнець 

Slutt 

Kpaj 

Τέλος 

Koniec

What is an LIR?

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?