Address policy FAQs
- Who sets the RIPE NCC policies and procedures?
- What do you mean by multi-homing?
- A new customer has address space from another
LIR and they request some IP space from me. Can I give them address
space from within my Assignment Window even though they have other space
from other providers ?
- How do I request addresses for small customers
(/30 and less) and how do I register them in the RIPE database?
- What happens when a small customer (/30 or less)
leaves? Can we reassign the addresses to another customer ?
- What is the Infrastructure Assignment
Window?
- How should I identify these assignments to RIPE
NCC in the RIPE Database?
Who sets the RIPE NCC policies and procedures?
The RIPE NCC policies and procedures are suggested by the RIPE NCC membership
and the RIPE community at large. Policies and procedures are discussed
in RIPE Working Groups (via email lists) and at RIPE meetings, both
open for participation to the public. Decisions are made using the consensus
model. All RIPE NCC policies and procedures are published and available
in the RIPE document
store.
More information about RIPE meetings and RIPE Working Groups can be found
at:
http://www.ripe.net/ripe
What do you mean by multi-homing?
Multi-homing means connecting your network to two or more separate upstream
providers and is a technique used by many organisations to provide redundancy
in their connectivity.
A new customer has address space from
another LIR and they request some IP space from me. Can I give them address
space from within my Assignment Window even though they have other space
from other providers ?
Yes you can. The Assignment Window (AW) only reflects the amount of address
space your LIR has given to a customer. So if you have never given them
any space before and its within your AW you can go ahead and assign the
addresses to them.
How do I request addresses for small
customers (/30 and less) and how do I register them in the RIPE database?
All requests that are /30 or less can be put into one
request form and when approved can be registered as one inetnum
object. It is the LIRs responsibility to differentiate customers in its
internal records. However, the RIPE Database does not require information
to be this specific. Small customers can be documented in one request
form by simply dividing them into their different types, ie. leased line,
dial-up, cable, DSL, frame relay etc. It is not required to mention each
and every customer in the addressing plan. Only indicate how many customers
you want to connect of each type.
What happens when a small customer (/30
or less) leaves? Can I reassign the addresses to another customer ?
If a customers leaves, you can re-assign the /30 to another customer of
the same size. You can continue to use the same address block for these
small customers (leased line, dial-up).
However, when the network being returned is larger than a /29 (and registered
in the RIPE database), you need to re-apply for these addresses if you
want to use them again.
What is the Infrastructure Assignment Window?
At the RIPE 40 meeting in Prague the Local
IR Working Group decided to allow Local Internet Registries (LIRs)
to make assignments to their own network infrastructure up to their Assignment
Window (AW) as many times as needed. This means that an LIR with a /25
AW can make numerous individual /25 assignments to its own network infrastructure
without having to send each request to the RIPE NCC. However, where a
single assignment would exceed a /25 the LIR would still need to send
an IP Request Form to hostmaster@ripe.net
as usual. All the requests you send to the RIPE NCC are considered when
evaluating your AW. Assignment Windows can go down as well as up. Please
see also the AW section of the LIR
training course material.
This policy change only affects assignments made by an LIR to its own
network infrastructure. There is no change in policy for assignments made
to organisations connecting to the LIR's network.
How should I identify these assignments
to the RIPE NCC in the RIPE Database?
By placing a remarks attribute in the inetnum object with a value of INFRA-AW.
It is important that a seprate remarks attribute is used for this line.
No comments should be placed before or after INFRA-AW in this attribute.
It is possible to have other remarks attributes, though. Here's an example:
inetnum: 192.168.3.128 - 192.168.3.255
netname: SOMECOMPANY-MAIL-SERVERS
descr: Inbound and Outbound SMTP mail clusters
and POP3 and IMAP front ends
country: EU
admin-c: HOHO-RIPE
tech-c: HOHO-RIPE
status: ASSIGNED PA
remarks: INFRA-AW
remarks: You can notify the MailTeam of
problems 24/7 by paging them at...
|
you are here: home -> Info, Stats and FAQs -> FAQs
