|
The following proposal was presented and accepted at the Public Forum. As part of the procedure, public comments will be received during a period of 45 days prior to its consideration on the part of LACNIC's Board of Directors for its final evaluation and possible implementation. Comments will begin to be received at the Public Policy List (politicas@lacnic.net) on Monday, April 12, 2004, and the closing day of this comments period will be Thursday, May 27, 2004.
Proposal for LACNIC's Policy Development Procedure
This proposal addresses the structure and general characteristics of the Policy Development Procedure.
The Policy Development Process may go through the following instances:
- Public Policy List
- Chairperson of the Public Forum
- Work Groups
- Public Forum
- LACNIC Board of Directors
- Member Assembly
Public Policy List
- Completely open list.
- Formal starting point and ending point for policy discussions.
- Policy proposals may be received at any time.
- Work Groups shall only be summoned through this list.
- Every summons must be supported by at least 5 members of the Public Policy List.
- Elections for appointing the Chairperson of the Public Forum shall be summoned through this List.
- Only those issues and subjects discussed at this List two weeks in advance of the Public Forum shall be presented at said Forum for their discussion and consensus.
Chairperson of the Public Forum
Functions of the Chairperson of the Public Forum
- To conduct discussions at the Public Forum, the Public Policy List and the Policy Development Process in general.
- To evaluate and suggest consensus in policy discussions.
- To suggest the finalization of the discussion on a specific subject at the Public Policy List.
- To summon the creation of Work Groups on the Public Policy List.
About the Chairperson of the Public Forum
- The Chairperson of the Public Forum shall not be part of LACNIC's staff.
- Honorary position.
- Elected at the Public Forum. Candidacies shall be presented at the Public Policy List.
- Must be a member of LACNIC or be supported by a member of LACNIC.
- Shall hold the position for two years.
Work Groups
- Work Groups shall be optional. Their goal will be to facilitate the discussion of a specific subject.
- Unlimited number of participants.
- Created at the summons of the Chairperson of the Public Forum, LACNIC's Board of Directors, or the Member Assembly.
- Work Group results must be published at the Public Policy List one month before the Public Forum is held. These results shall be considered as recommendations for the Public Policy List.
Public Forum
- Open to any person interested in the subject matter.
- Analysis of the discussions considered at the Public Policy List.
- Decisions based on consensus. Moderated by the Chairperson of the Public Forum.
- Approved policies shall later be published at the Public Policy List for the reception of public comments during a period of 45 days.
- Policies that are not approved shall be reported at the Public Policy List for their reconsideration on the part of the Internet community.
- Opportunities will be offered for presenting subjects of interest to the Public Forum.
LACNIC Board of Directors
During its first meeting after the 45-day period established for the reception of public comments, LACNIC's Board of Directors may:
- Accept the proposal. Analyze its implementation jointly with the staff and make the corresponding announcement.
- Reject the consensus and request the Public Policy List, through the Chairperson of the Public Forum, to continue their analysis and present a new proposal at the following Public Forum.
In addition
- The Board of Directors may summon the creation of Work Groups on the Public Policy List.
- The Board of Directors will be responsible for the election process for appointing the Chairperson of the Public Forum.
Member Assembly
- It may also summon the creation of Work Groups on the Public Policy List.
Comments
- During the Public Forum it was pointed out that the Member Assembly is the maximum authority within LACNIC's organizational structure. As such, it may decide any modification, including the suspension of a given policy's application. For this reason the following characteristic established for the Member Assembly was eliminated, as it was considered redundant: "This Assembly shall have the faculty of revising the consequences of the implementation of the policies and, should the Assembly find negative elements, it may suspend its application. In this case the Assembly shall notify LACNIC's Public List, through its Board of Directors."
- The document which was used as the basis for this discussion at the Public Forum may be found here
- The presentation of this proposal at the Public Forum may be found here
- As a result of this consensus, and if the modification is ratified by LACNIC's Board of Directors, it is anticipated that a more formal document will be prepared describing in detail the Policy Development Procedure; this document will be totally based on the characteristics which were discussed and agreed on at the Public Forum and the Public Policy List.
The following proposal was presented and accepted at the Public Forum. As part of the procedure, public comments will be received during a period of 45 days prior to its consideration on the part of LACNIC's Board of Directors for its final evaluation and possible implementation. Comments will begin to be received at the Public Policy List (politicas@lacnic.net) on Monday, April 12, 2004, and the closing day of this comments period will be Thursday, May 27, 2004.
Lame Delegation Policy Proposal
A DNS server is considered to have a lame delegation problem when this server appears registered in the regions for inverse resolution of IP address blocks and at the time of applying for a resolution this server does not respond authoritatively. The non authoritative answer of the DNS server is interpreted as a server configuration error and, according to LACNIC's standards, this DNS server shall be considered as having lame delegation problems.
The process for correction lame delegations within the IP address space administered by LACNIC follows the following stages:
- DETECTING LAME DELEGATIONS
- MONITORING DNS SERVERS WITH LAME DELEGATION PROBLEMS
- NOTIFYING THE RESPONSIBLE PARTY
- DEACTIVATING DNS SERVERS
- DNS SERVER ACTIVATION
DETECTING LAME DELEGATIONS
LACNIC shall periodically revise in-addr.arpa zone where there are DNS servers registered for inverse resolution of administered blocks allocated within the region covered by LACNIC.
A DNS server registered in LACNIC's system shall be considered to have Lame Delegation problems if a query of the SOA record of the DNS server does not provide an authoritative answer for said record.
The reviewing will be done for each in-addr.arpa zone delegated to each DNS server.
If there is no authoritative answer, the DNS server shall be catalogued as having Lame Delegation problems for the in-addr.arpa zone reviewed and therefore it will enter in a monitoring process.
MONITORING DNS SERVERS WITH LAME DELEGATION PROBLEMS
Prior to establishing that a DNS server has permanent Lame Delegation problems for in-addr.arpa zone, LACNIC shall monitor the DNS server for a period of seven days. If after this period the problems still persist, LACNIC shall notify those responsible for the IP address block.
If a DNS server that was originally detected as having Lame Delegation problems responds correctly for the in-addr.arpa zone before the phase of deactivating DNS server, the server shall be removed from the monitoring list for the correspondent zones.
NOTIFYING THE RESPONSIBLE PARTY
Firstly, the administrative contact of the affected block shall be notified, together with the technical contact if this information has been provided. Notifications shall be sent out every fifteen days over a period of sixty days. LACNIC reserves the right to investigate other types of contacts if during the first thirty days no answer is received from the administrative and/or technical contacts.
DEACTIVATING DNS SERVERS
Once the notification period defined above has ended, these servers shall be eliminated from LACNIC zones.
Only those in-addr.arpa zones where the DNS server has Lame Delegation problems will be affected by eliminating the register of the DNS server. Others DNS servers giving services for those zones will not be affected.
A comment shall be added to the block registry on the WHOIS database specifying that the DNS server registered for the inverse resolution for the in-addr.arpa zones for this block was deactivated due to Lame Delegation problems.
Monitoring and deactivation of DNS Server processes shall only consider segments directly delegated by LACNIC.
DNS SERVER ACTIVATION
DNS server activation shall follow the usual procedures already included in LACNIC's policy. Only the block's administrative or technical contact shall be able to activate new DNS servers through LACNIC's registration system. Any new DNS server registered at LACNIC must respond authoritatively to the block at the moment it is activated, otherwise server registration shall be rejected.
Comments
- The Public Forum considered it appropriate to add the following statement within the Monitoring and Deactivation Process for this Policy: "Monitoring and deactivation of DNS Server processes shall only consider segments directly delegated by LACNIC." In this way LACNIC limits its faculties to these blocks with their related in-addr.arpa zones.
- The document which was used as the basis for this discussion at the Public Forum may be found here
The following policy related presentations were made for information purposes only. They were not submitted for the consensus of the Public Forum, either because they had not been previously presented at the Public Policy List or because there was no prior widespread discussion which allowed the consideration of the subject at the Public Forum.
Because these presentations were for information purposes only, these subjects are open to analysis by any person who wishes to do so at the Public Policy List.
HD Ratio for IPv4
This presentation suggests an alternative for evaluating additional IPv4 address space requirements. Currently the main requirement necessary for LACNIC to grant additional IPv4 address space is that the applicant must have utilized at least 80% of the initially allocated space. This presentation offers a new alternative for this evaluation, one which uses a concept similar to the one used for IPv6 addresses. Among the main characteristics of this alternative is that it simplifies the evaluation of those organizations which already have a large IPv4 address block, reduces the percentage of utilization required as the size of the administered block increases, allows hierarchical management of IP address space, etc.
The details of this presentation can be found here
IPv6 Allocation to Private/Closed Networks
As part of the recent changes introduced in the policy for initial IPv6 address allocation within the region covered by LACNIC, among other requirements, it was established that those organizations that receive IPv6 address space must advertise a single block on the Internet inter-domain routing system, aggregating all IPv6 address allocations received, within a period of not more than 12 months. The result of this is that those organizations that require IPv6 addresses for internal networks that will not be advertised on the Internet cannot receive this resource from LACNIC. While some RIRs consider that these organizations can apply for an IPv6 address block, others have adopted the same criterion as LACNIC. This presentation was made in an effort to unify IPv6 address criteria among different Regional Internet Registries, reflecting APNIC's standpoint.
The details of this presentation can be found here
Minimum RIR Allocation
Currently the RIPE registry modified the minimum size for IPv4 address allocations, changing from a /20 block to a /21. Likewise, APNIC also considered this policy during its latest meeting, and the reduction to a /21 was approved. This change also implies a reduction of the minimum criteria that Internet Service Providers must satisfy in order to receive a portable IPv4 address block. This presentation reports policy changes in other regions.
The details of this presentation can be found here
Complete text in .doc format
|
