This proposal suggests registering more detailed IP address assignment information in the WHOIS database to help network operators filter more precisely. It proposes adding port range details for IPv4 addresses and assignment prefix sizes for IPv6 addresses. This would allow operators to filter specific address ranges rather than entire allocations, avoiding over-filtering. The changes may require updating registration rules and database records. Some discussion is needed on user access control and hosting service registrations. The goal is providing information to support responsible filtering while maintaining security and operability.

1. A proposal for
prop-115: Registration of
detailed assignment
information in whois DB
* Ruri Hiromi (INTEC Inc.)
Tomohiro Fujisaki (NTT)
APNIC 39 Open Policy Meeting
Fukuoka, Japan
Thursday, 5 March 2015
http://www.apnic.net/policy/proposals/prop-115

2. Problem statement
• 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).
192.0.2.24/32 1-256 is for HomeA
257-511
is for HomeB
192.0.2.0/24 1-65536 is shared address of ISP-X
512-767
is for HomeB
768-1023
is for HomeB
Case1) Shared Address
Just filtered out HomeA

3. Problem statement(continued)
2001:db8:1::0/56 is for HomeA
2001:db8:1::/35 allocated for ISP-Y
Case2) address assignment size information in IPv6
Exact assignment size is not shown for Home Network
The IPv6 address assignment size may be different from ISP

4. Objective of policy change
• Lots of operators look a record when harmful behavior coming
to their network to identify its IP address confirming it can be
filtered or not.
• The goal is providing more specific information to support these
actions.

5. Situation in other regions
• No same regulation/discussion can be seen in other regions.
– AFRINIC
– ARIN
– LACNIC
– RIPE NCC

6. Proposed policy solution
• Provide accurate filtering information generated from whois DB.
• For IPv4, propose to add 'port range' information to IP address
entry.
inetnum: 219.118.96.0 - 219.118.111.255
netname: INetCore-CIDR-BLK-JP
descr: INTEC Inc.
remarks: Email address for spam or abuse complaints :
abuse@inetcore.com
country: JP
admin-c: IN011JP
tech-c: KN10198JP
remarks: This information has been partially mirrored by APNIC from
remarks: JPNIC. To obtain more specific information, please use the
remarks: JPNIC WHOIS Gateway at
remarks: http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks: whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks: defaults to Japanese output, use the /e switch for English
remarks: output)
changed: apnic-ftp@nic.ad.jp 20021008
changed: apnic-ftp@nic.ad.jp 20110519
source: JPNIC
No
modification
on the DB
record, no
additional
object
Using
“remarks”
object for
detailed info.

7. Proposed policy solution(continued)
• Provide accurate filtering information generated from whois DB.
• For IPv6, propose to provide 'assignment prefix size' information
for specific IPv6 address.
inet6num: 2403:2000::/32
netname: INetCore-CIDR-BLK-JP
descr: INTEC Inc.
remarks: Email address for spam or abuse complaints :
abuse@inetcore.com
country: JP
admin-c: IN011JP
tech-c: KN10198JP
remarks: This information has been partially mirrored by APNIC from
remarks: JPNIC. To obtain more specific information, please use the
remarks: JPNIC WHOIS Gateway at
remarks: http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks: whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks: defaults to Japanese output, use the /e switch for English
remarks: output)
changed: apnic-ftp@nic.ad.jp 20070627
changed: apnic-ftp@nic.ad.jp 20130517
source: JPNIC
No
modification
on the DB
record, no
additional
object
Using
“remarks”
object for
detailed info.

8. Advantages / Disadvantages
• Advantages
– 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.

9. Impact on APNIC
• This might be beyond the scope of using whois DB, need to
change policy of use, membership, guidance, or any other
related documents.
• Members need to update their records

10. 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.

11. Summary
• Our proposal is
– Detailed assignment information can be seen in whois DB for operators
– Operators can set filter with this detailed information and not goes to be
‘over-filter’ with whole allocation information

12. Questions?