APNIC Home APNIC Home
Info & FAQ |  Resource services |  Training |  Meetings |  Membership |  Documents |  Whois & Search |  Internet community

You're here:  Home  Mailing Lists global-v6 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GLOBAL-V6] Consensus in AP region



Hi,

Policy amendment was proposed in the APNIC Address Policy SIG
from the global IPv6 policy editorial team and the current
draft (dated 12/22) with this amendment was supported 
as AP region consensus.

In the meeting, three issues were identified through efforts
to summarize continuing discussion in RIPE41 and the global 
mailing list. Those were;

1) Initial allocation criteria
2) Do we continue to use HD-Ratio?
3) Are requirements of LIR's sub-allocation appropriate?

Regarding 1), the editorial team proposed an amendment
which would replace Section 5.2.1 of the original draft. 
See the below in this mail.

We spent one and a half hour for discussion.
During discussion, more issues other than these were raised
but finally they were withdrawn, considering the priority 
for moving forward.

To the end, each of the issues was supported by the show of hands.
More clearly,

Consensus 1) the amendment below was accepted
Consensus 2) Yes, HD-ratio should be used as the draft shows
Consensus 3) Yes, requirements in the draft are okay.

Finally, I, as the chair, asked participants for voting
the whole draft with the amendment and found this reached 
the consensus of AP region consensus.

I hope quick resolution with good discussion 
in both ARIN and RIPE meeting (of course as well as in
the mailing list) would be appreciated.

Please review the following and give any feedback. Thanks.

Regards,
Takashi Arano
---------------------------------


Start of proposed text
================

5.2.1.  Initial allocation criteria

In order to reduce address space fragmentation and increase the
likelyhood that routes can be aggregated, end sites should obtain
address space from their connectivity providers as opposed to directly
from RIR/NIRs. Having RIR/NIRs assign address space directly to end
sites in general is known to lead to unscalable routing, since the
routes to those end sites will not aggregate. Thus, allocations of
large address blocks (i.e., much larger than /48s) are made to
organizations that assign /48s to organizations other than itself, and
also provide connectivity for those organizations. Specifically:

- Organizations requesting address space must be an LIR. (see Section
   2.6).

- Organizations requesting address space must not be end sites.

- Organizations requesting address space will provide connectivity for
   the organizations it has assigned /48s to by advertising such
   connectivity through the single aggregate allocated to that
   organization.

- Organizations requesting address space have a plan for assigning
   address space (e.g., /48s) to other organizations, with the number
   of such assignments likely to result in at least 200 such
   assignments over the next two years.

- Organizations who are granted initial allocations, but after two
   years no longer satisfy the requirements above, are subject to
   having their allocations revoked.

================
End proposed text

Note: Section 2.6 defines LIR as follows:

2.6.  Local Internet Registry (LIR)

    A Local Internet Registry (LIR) is an IR that primarily assigns
    address space to the users of the network services that it provides.
    LIRs are generally ISPs, whose customers are primarily end users and
    possibly other ISPs.

-------------------------------------------

-
- This list (global-v6) is handled by majordomo@lists.apnic.net