| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 15 Jul 2025 02:58:43 GMT
content-type: text/html; charset=utf-8
cf-ray: 95f5ffebb939c177-BLR
cf-cache-status: DYNAMIC
last-modified: Tue, 30 Jul 2024 05:42:14 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
strict-transport-security: max-age=15552000; preload
server: cloudflare
content-encoding: gzip
[sig-policy] [New Problem Statement] prop-115: Registration of detailed
[sig-policy] [New Problem Statement] prop-115: Registration of detailed
- To: sig-policy at lists dot apnic dot net
- Subject: [sig-policy] [New Problem Statement] prop-115: Registration of detailed assignment
- From: Masato Yamanishi <myamanis at gmail dot com>
- Date: Tue, 3 Feb 2015 12:00:19 -0600
- Delivered-to: sig-policy at mailman dot apnic dot net
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=deiT4LC4BZwMRPxIC+fG9mb4pZnVD/OMWpoSoDET9+E=; b=Cjz6lczaOLOS/oTZeE/dYAgG8Ur8qCke/1aF6xDtXXkYbGBCvjxjn5C0JObUe/3xQ4 Yi1t1je5dOvsem3GSPa96g0mFkyPo3QxVD43ks/olQYaRTYKlX5AtmSr2VcVROlHn4HV IjBbmOZpcWOjGXNDFCAUHigah47nUwSyx1Q/bTOahUegEVcgg8S4Y/ytPMDg2VhytYKz xdk5H5CqTQekAr5G8laifK3gWHnWwetHtQzi6JH9I1vQZGd5yCpnFyU9r1aq96mhaqbh eriaE30lfwqQvTD2LSJYdRW4iJAXZulrmcwmBJWVaA08w9+x5Lcmn70kiGDPwyYteG8l NQhw==
- List-archive: <https://mailman.apnic.net/mailing-lists/sig-policy/>
- List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:sig-policy@lists.apnic.net>
- List-subscribe: <https://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>
- Prev by Date: [sig-policy] [New Policy Proposal] prop-114: Modification in the ASN eligibility criteria
- Previous by Thread: [sig-policy] [New Policy Proposal] prop-114: Modification in the ASN eligibility criteria
- Index(es):
Dear SIG members
A Problem Statement, identified as "prop-115: Registration of detailed
assignment information in whois DB" has been sent to the Policy SIG for
review and further discussion, or development by the community.
It will be presented at the Open Policy Meeting at APNIC 39 in Fukuoka,
Japan on Thursday, 5 March 2015.
We invite you to review and comment on the proposal on the mailing list
before the meeting.
The purpose of submitting a Problem Statement is to reflect that the
author(s) are unsure exactly what policy changes are required to
Resolve the stated problem.
It is an invitation to discuss the severity of the problem and to discuss
possible solutions, whether they are through policy changes, or some
other mechanism.
I would encourage those who share the author’s view that this problem
should be resolved to participate in the discussion by posting their views
and suggestions to the list.
Regards,
Masato
-----------------------------------------------------------------
prop-115-v001: Registration of detailed assignment information in
whois DB
-----------------------------------------------------------------
Proposer: Ruri Hiromi
hiromi at inetcore dot com
Tomohiro Fujisaki
fujisaki at syce dot net
1. Problem statement
--------------------
Current information in Whois DB does not have enough, detailed
record if operator in an network use it for filtering.
To cover this, we propose modification towards whois DB.
1) IPv4 address assignment information has "minimum assignment
network space/or declare shared address" and "port number" which
for shared address space.
ex) 192.0.1.24/32 1-256 is for HomeA
192.0.1.24/32 257-511 is for HomeB
2) IPv6 address assignment information also has "minimum assignment
network space"
ex) 2001:db8:1::0/56 is for HomeA
2001:db8:2::0/48 is for HomeB
3) for the security reason, this detailed records may be able to
see only operators.(some kind of user control is needed)
2. Objective of policy change
-----------------------------
Under community development
3. Situation in other regions
-----------------------------
Under community development
4. Proposed policy solution
---------------------------
Under community development
5. Advantages / Disadvantages
-----------------------------
Advantages:
Under community development
Disadvantages:
Under community development
6. Impact on resource holders
-----------------------------
Under community development
7. References
-------------
A Problem Statement, identified as "prop-115: Registration of detailed
assignment information in whois DB" has been sent to the Policy SIG for
review and further discussion, or development by the community.
It will be presented at the Open Policy Meeting at APNIC 39 in Fukuoka,
Japan on Thursday, 5 March 2015.
We invite you to review and comment on the proposal on the mailing list
before the meeting.
The purpose of submitting a Problem Statement is to reflect that the
author(s) are unsure exactly what policy changes are required to
Resolve the stated problem.
It is an invitation to discuss the severity of the problem and to discuss
possible solutions, whether they are through policy changes, or some
other mechanism.
I would encourage those who share the author’s view that this problem
should be resolved to participate in the discussion by posting their views
and suggestions to the list.
Regards,
Masato
-----------------------------------------------------------------
prop-115-v001: Registration of detailed assignment information in
whois DB
-----------------------------------------------------------------
Proposer: Ruri Hiromi
hiromi at inetcore dot com
Tomohiro Fujisaki
fujisaki at syce dot net
1. Problem statement
--------------------
Current information in Whois DB does not have enough, detailed
record if operator in an network use it for filtering.
To cover this, we propose modification towards whois DB.
1) IPv4 address assignment information has "minimum assignment
network space/or declare shared address" and "port number" which
for shared address space.
ex) 192.0.1.24/32 1-256 is for HomeA
192.0.1.24/32 257-511 is for HomeB
2) IPv6 address assignment information also has "minimum assignment
network space"
ex) 2001:db8:1::0/56 is for HomeA
2001:db8:2::0/48 is for HomeB
3) for the security reason, this detailed records may be able to
see only operators.(some kind of user control is needed)
2. Objective of policy change
-----------------------------
Under community development
3. Situation in other regions
-----------------------------
Under community development
4. Proposed policy solution
---------------------------
Under community development
5. Advantages / Disadvantages
-----------------------------
Advantages:
Under community development
Disadvantages:
Under community development
6. Impact on resource holders
-----------------------------
Under community development
7. References
-------------