[sig-policy] Summary of discussion: Resource Management System WG

[Shin Yamasaki <yamasaki@nic.ad.jp>]

Dear Policy SIG participants,

As a mid-term report, please let me share the summary of the resource
management system working group as follows.

I need more participants for the working group (WG) mailing list (ML)
from now on until the APNIC 23.  Please join and give your opinions!

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

1. Co-chair resignation

Terry Manderson stepped down from the co-chair position due to his
concern about his status as secretariat.  However, he is an active
participant to the WG ML.

Nobody has offered him/herself as a candidate yet.  Please let the chair
know or post to the WG ML if anyone would like to take the role.


2. E-mail deprecation proposal (prop-037)

The URL of the proposal can be found at:

http://www.apnic.net/docs/policy/proposals/prop-037-v001.html


2.1. Pro opinions for prop-037

- This kind of discussion may take for a long time.
- Considering new technologies such as DNSSEC and resource
certification, increasing security for bulk updating method for APNIC
RMS would be good idea.
- E-mail registration interface isn't user-friendly.
- MyAPNIC doesn't address secure automated registration.  The new
proposed XML interface solves this.
- Longer term cost reduction to both members and APNIC.
- Faster updates


2.2. Con opinion for prop-037

- This affects existing in-house IT systems which are optimized for
current e-mail application.  This could be pressure cost-wise for small
LIRs.
- MyAPNIC already exists for who prefer secure registration.


2.3. Proposed implementation schedule for prop-037

In the proposal, the implementation periods as follows:

    -  4 months after adoption:     Stop accepting email updates for
                                    domain objects
    -  8 months after adoption:     Stop accepting email updates for
                                    inetnum, inet6num, and aut-num
                                    objects
    -  12 months after adoption:    Stop accepting email update for the
                                    remaining object types

The secretariat asked if these periods are appropriate.


2.4. Alternative/Counter proposed schedule for prop-037

An alternative implementation schedule for 2.3. has been proposed from a
participant:

(period      (action)
after
adoption)
-  6 months: Start accepting all objects via new method
- 10 months: Stop accepting domain objects via email
- 14 months: Stop accepting inetnum, inet6num, and autnum
             objects
- 18 months: Stop accepting all remaining objects.


Then, APNIC secretariat suggested the following schedule:

(period      (action)
after
adoption)
-  6 months: Prototype available that accepts all objects via new method
- 10 months: production system stop accepting domain objects
             via email and start accepting domain objects via new method
- 14 months: production system stop accepting inetnum, inet6num,
             autnum objects via email, and start accepting inetnum,
             inet6num, autnum objects via new method
- 18 months: production system stop accepting remaining RPSL objects
             via email and start accepting remaining RPSL object
             via new method

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




Cheers,
Shin

-- 
Shin Yamasaki
Japan Network Information Center (JPNIC)