FAQ: Address Policy
- 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:
- 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.
- 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 _at_ ripe _dot_ 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
descr: Inbound and Outbound SMTP mail clusters
and POP3 and IMAP front ends
status: ASSIGNED PA
remarks: You can notify the MailTeam of
problems 24/7 by paging them at...