prop111-v004: Request-based expansion of IPv6 default allocation size, by Tomohiro Fujisaki [APNIC 38 / Policy SIG]

prop-111-v004:
Request-based expansion of
IPv6 default allocation size
Tomohiro Fujisaki
APNIC 38 Open Policy Meeting
18 September 2014

Abstract
This proposal tries to allow an
organization to receive an IPv6 allocation
up to a /29 (/32 - /29) by explaining how
the extended space up to /29 will be
used.
2

Problem statement
IPv6 minimum allocation size to LIRs is
defined as /32. It's better to expand this
minimum allocation size up to /29 (/32 - /29)
because of following reasons:
1. Address block usage
Before sparse allocation mechanism implemented
in late 2006, /29 was reserved for all /32. These
blocks might be kept unused in the future.
• 220 allocations in this block
3

Address space status before 2006
apnic|JP|ipv6|2001:cd0::|32|20021205|allocated|A9239A9B
apnic||ipv6|2001:cd1::|32||available|
apnic|TW|ipv6|2001:cd8::|32|20021209|allocated|A929C43A
apnic||ipv6|2001:cda::|31||available|
apnic||ipv6|2001:cdc::|30||available|
apnic|HK|ipv6|2001:ce0::|32|20021224|allocated|A9156D54
apnic||ipv6|2001:ce1::|32||available|
apnic|JP|ipv6|2001:ce8::|32|20030113|allocated|A92F4AF4
apnic||ipv6|2001:cea::|31||available|
apnic||ipv6|2001:cec::|30||available|
apnic|KR|ipv6|2001:cf0::|32|20030122|allocated|A9262127
apnic||ipv6|2001:cf1::|32||available|
4
Reserved and will be unused
From http://ftp.apnic.net/stats/apnic/delegated-apnic-extended-latest as of 17th Sep. 2014

Problem statement
1. Address block usage (cont.)
– Sparse allocation mechanism was implemented in late 2006
with a /12 allocation from the IANA.
– It is expected that allocation up to /29 is guaranteed for
consistency with allocations above. Based on the current
situation, contiguous allocation of /29 can still be
accommodated even under the sparse allocation mechanism
(Current /32 allocations from the /12 block can grow up to /24
at this stage).
5

Address space status in space alloc
apnic|AU|ipv6|2401:9300::|32|20110726|allocated|A918E80E
apnic||ipv6|2401:9301::|32||available|
apnic|PH|ipv6|2401:9400::|32|20090902|allocated|A91F73C7
apnic|PH|ipv6|2401:9500::|32|20110727|allocated|A9158547
6
Gap for expansion
Gap for expansion
Gap for expansion
From http://ftp.apnic.net/stats/apnic/delegated-apnic-extended-latest as of 17th Sep. 2014

Problem statement
2. Enable flexible network design
After amended HD Ratio (0.94) and base
calculation size (/56) was introduced (prop-031 and
prop-033), to obtain address blocks larger than /32
and to request additional address blocks became
harder especially for small and middle size ISPs.
7

Problem statement
3. Easier traffic control
For traffic control purpose, some LIRs announce
address blocks longer than /32 (e.g. /35). However,
some ISPs may set filters to block address size
longer than /32. If LIRs have multiple /32, they can
announce these blocks and its reachability will be
better than longer prefix.
– Some filtering guidelines recommend to filter
longer prefix than /32.
8

Problem statement
4. Less number of announced prefix
If an LIR needs address blocks larger than /32, LIRs may
tend to announce as a single prefix if a /29 is allocated
initially at once. i.e., total number of announced prefixes in
case 1 may be smaller than in case 2.
– case 1:
The LIR obtains /29 at the beginning of IPv6 network
construction.
– case 2:
The LIR obtains /32, and /31, /30 additionally with the
subsequent allocation mechanism.
9

Proposed policy solution 1/2
For initial allocation criteria:
• Change the text to "5.2.2 Minimum initial allocation size" of
current “IPv6 address allocation and assignment policy” as
below:
Organizations that meet the initial allocation criteria are eligible to
receive an initial allocation of /32. The organizations can receive
up to /29 by providing utilization information of the whole
address space.
• Change /32 to /29 in "5.2.3 Larger initial allocations”
Initial allocations larger than /29 may be justified if:
10

Proposed policy solution 2/2
For subsequent address allocation
• Add following text as 5.3.4
5.3.4 Extend existing allocations to /29
LIRs that hold one or more IPv6 allocations are able to
request extension of each of these allocations up to a /29
without meeting the utilization rate for subsequent allocation
by providing their network plan to show how the whole
address space will be used.
11

Situation in other regions
RIPE-NCC:
• The policy "Extension of IPv6 /32 to /29 on a per-allocation
vs per-LIR basis" is adopted in RIPE-NCC and LIRs in
RIPE region can get up to /29 by default.
• No other regions have same kind of policy.
12

Advantages / Disadvantages
• Advantages
• It is possible to utilize address blocks which is
potentially unused into the future.
• Organizations can design their IPv6 networks more
flexibly.
• It will be possible for LIRs to control traffic easier.
• Disadvantages
Some people may argue this will lead to inefficient utilization of IPv6
space since LIRs can obtain huge address size unnecessarily.
However, this will not happen because larger address size needs higher
cost to maintain that address block.
13

Impact on resource holders
• NO IMPACT on existing resource holders, and
new resource applicant if they do not need larger
address block.
• NIRs must implement this policy if it is
implemented by APNIC.
14

Main changes from prop-111-v002 1/2
At the last policy sig in Malaysia, concern about address
allocation without any constraint was expressed. This revised
proposal add the requirement to demonstrate need for both
initial and subsequent allocations.
– For initial allocation:
• v002:
– For allocations up to /29 no additional documentation
is necessary.
• v004:
– The organizations can receive up to /29 by providing
utilization information of the whole address space.
15

Main changes from prop-111-v002 2/2
– For subsequent allocation:
• v002:
– without meeting the utilization rate for
subsequent allocation and providing further
documentation.
• v004:
– without meeting the utilization rate for
subsequent allocation by providing their
network plan to show how the whole address
space will be used.
16

Discussion on nibble boundary allocation
There were several comments on nibble boundary
allocation (not /29, but /28) in the sig-policy mailing
list.
Advantages:
– ease of address masking and calculation (for filtering,
RPKI operation and so on)
– ease of DNS reverse delegation set up
Disadvantages:
– LIRs in legacy space cannot extend prefix to /28
– allocation size could be too huge (allocations after /28 will
be /24, /20..)
17

Summary
Propose to allow an organization to receive IPv6
allocation up to a /29 (/32 - /29) to utilize unallocated
space by explaining how the extended space up to /
29 will be used.
IPv6 Address Space Size
/32 /29
Request with HD Ratio Based
network usage
18

prop111-v004: Request-based expansion of IPv6 default allocation size, by Tomohiro Fujisaki [APNIC 38 / Policy SIG]

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (11)

Similar a prop111-v004: Request-based expansion of IPv6 default allocation size, by Tomohiro Fujisaki [APNIC 38 / Policy SIG]

Similar a prop111-v004: Request-based expansion of IPv6 default allocation size, by Tomohiro Fujisaki [APNIC 38 / Policy SIG] (20)

Más de APNIC

Más de APNIC (20)

Último

Último (17)

prop111-v004: Request-based expansion of IPv6 default allocation size, by Tomohiro Fujisaki [APNIC 38 / Policy SIG]