Version 3 of prop-115: Registration of detailed assignment information in whois DB, did not reach consensus at the APNIC 40 Open Policy Meeting.
The Policy SIG Chair requested the Secretariat conduct further research into the problem statement and returned the proposal to the authors for further consideration.
Proposal details ----------------
This proposal seeks to require LIRs to register accurate filtering information, such as IPv4 port-range information and IPv6 assignment prefix size.
Proposal details, including the full text of the proposal, history, and links to the APNIC 40 meeting archive, are available at:
------------------------------------------------------------------------ prop-115-v003: Registration of detailed assignment information in whois DB ------------------------------------------------------------------------
Recently, there are some cases need to get IP address assignment information in more detail to specify user IP address.
Without this information, operators cannot filter out specific address range, and it might lead to 'over-filter' (i.e. filtering whole ISP's address range).
For example:
1) 'Port' range information in IPv4
ISPs are using 'CGN' or other kinds of IPv4 address sharing technology with assignment of IP address and specified port range to their users.
In this case, port information is necessary to specify one user.
- operators can set filtering by IP address based on correct assignment information base.
- users who share same address space can be avoid to be including bulk filtering.
Disadvantages:
- registration rule will move to more strict manner.
- strict watch and control in registration of database records.
- additional record or option will be considered.
- privilege for withdrawing detailed information will be set for these records.
6. Impact on APNIC ------------------
This might be beyond the scope of using whois DB and appropriate changes in policy document or guidance to whois DB will be needed.
Some kind of modification cost in whois DB might be needed to set access privilege to the detailed information.
Some kind of modification cost in whois DB might be needed in Help message/Warning/Alert when whois DB has non-privileged access.
Some kind of promotion cost might be needed in announcing.
Need cooperation and support from members(ISPs).
7. Other Consideration ----------------------
For the security reason, this detailed records may be able to see only by operators.(some kind of user control/privilege setting is needed)
For hosting services, /32 in IPv4 and /128 in IPv6 registration should be discussed based on its operability and possibility. But a harmful activities to filter by IP addresses are coming from hosting services as well. Here it seemed to be some demands.
Some ISP use IRR DB to notice their filter policy towards BGP community with "remarks" filed in aut-num record. Need more discussion among APNIC members on using whois DB versus IRR DB.
Start a pilot project for research its demands and effectiveness in APNIC region. APNIC is a worthy body to lead this pilot project.
There are some opinions that it is not suitable to handle those issues at the Internet Registries (IRs), but we think it should be registered in the IRs database since that is part of assignment information.