The Problem statement "Registration of detailed assignment information in whois DB" has been assigned a Policy Proposal number following the submission of a new version sent to the Policy SIG for consideration.
The proposal, "prop-115-v001: Registration of detailed assignment information in whois DB" now includes an objective and proposed solution.
Information about this and earlier versions is available from:
You are encouraged you to express your views on the proposal:
- Do you support or oppose this proposal? - Does this proposal solve a problem you are experiencing? If so, tell the community about your situation. - Do you see any disadvantages in this proposal? - Is there anything in the proposal that is not clear? - What changes could be made to this proposal to make it more effective?
Regards,
Masato
------------------------------------------------------------------------ prop-115-v001: 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.
With out 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.
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.
