APNIC Home APNIC Home
Info & FAQ |  Resource services |  Training |  Meetings |  Membership |  Documents |  Whois & Search |  Internet community

You're here:  Home  Mailing Lists sig-nir 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sig-nir] prop-054: NIR operational policy document revision



Do you have further comments on Terry's response, Shin?

Comments on other NIR are also welcome.

Feel free to express questions, comments, or  even a simple expression
of support is also a useful input :-).

izumi

Terry Manderson wrote:
> Hi Shin,
> 
>> Shin wrote:
>> - Do you support moving the technical descriptions of managing  
>> reverse DNS zone out of 'Operational policies for National Internet  
>> Registries in the APNIC region' and onto the APNIC website?
>> Currently I cannot find the equivalent part of section 3.4 of  
>> APNIC-103-v001 in the web page stated in the proposal:
>> http://www.apnic.net/services/dns_guide.html
>> Unless APNIC clearly describes all required procedures in the page  
>> before Policy SIG in APNIC 25, it is difficult to support this part.
>> The best I could bend backward is that APNIC posts the content of  
>> the addendum to the web page to this mailing list.
>> Without that, it could be blind approval for non-existent procedure.
> 
> I will endeavour to create a draft of that page, or furnish the  
> information that will be provided on that url to the list before the  
> meeting.
> 
> However you can expect that it would simply reflect the preferred  
> methods for updating the DNS, those being MyAPNIC and the XML/REST  
> API. We clearly need to be careful about releasing the API information  
> as it isn't yet a member wide service.
> 
>> In the Disadvantages: part in the Pros/Cons section, | To ensure  
>> that NIRs have enough time to adapt to the changes, | the APNIC  
>> Secretariat will commit to a six-month notice period | between  
>> announcing changes to the system and expected |      implementation  
>> by NIRs.
>> I prefer to change this to: To ensure that NIRs have enough time to  
>> adapt to the changes, the APNIC Secretariat will commit to at least  
>> six-month notice period  between announcing changes to the system  
>> and expected implementation by NIRs.
> 
> Given that our development process is transparent, such that we are  
> quite overt about upcoming work in the secretariat that may affect the  
> NIRs. I'm guessing that your concern directly relates to your ability  
> implement in 6 months assuming that you hadn't heard of it previously.  
> So in applying this to future (not already scheduled) changes..
> 
> How does this sound as an alternative?
> -----
> To ensure that NIRs have enough time to be both aware of the changes  
> and adapt their systems to the changes, the APNIC Secretariat will  
> commit to the following notice periods:
> 	1) Notification of development or work-in-progress of three(3) to  
> Six(6) months, prior to:
> 	2) A six(6) month notice period to implementation by the NIR.
> -----
> 
>> The notice period can be extended upon request  from APNIC or an NIR.
> 
> I think I would find this acceptable if the request came with  
> supporting reasons why the request needs to be extended, such that the  
> reason for extension is in the best interests of the common good for  
> continuous improvement or a direct conflict with another APNIC  
> operational change at that time.
> 
> Cheers
> Terry
> --
> Terry Manderson                         email:      terry@apnic.net
> Network Operations Manager, APNIC       sip:    info@voip.apnic.net
> http://www.apnic.net                    phone:      +61 7 3858 3100
> 
> 
> _______________________________________________
> sig-nir mailing list
> sig-nir@lists.apnic.net
> http://mailman.apnic.net/mailman/listinfo/sig-nir