From owner-apnic-announce@lists.apnic.net Wed Jul 5 17:24:47 2000 Received: (from majordom@localhost) by whois.apnic.net (8.9.3/8.9.3) id RAA89465; Wed, 5 Jul 2000 17:24:42 +1000 (EST) Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by whois.apnic.net (8.9.3/8.9.3) with ESMTP id RAA89461 for ; Wed, 5 Jul 2000 17:24:40 +1000 (EST) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id RAA18865 for ; Wed, 5 Jul 2000 17:24:40 +1000 (EST) From: secretariat@apnic.net Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1) id xma018863; Wed, 5 Jul 00 17:24:29 +1000 Received: from compiler.staff.apnic.net (compiler.staff.apnic.net [192.168.1.39]) by hadrian.staff.apnic.net (8.9.3/8.9.3) with ESMTP id RAA00444 for ; Wed, 5 Jul 2000 17:24:25 +1000 (EST) Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST) X-Sender: paulg@compiler.staff.apnic.net To: apnic-announce@lists.apnic.net Subject: [apnic-announce] IPv6 Policy Document Revision Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apnic-announce@lists.apnic.net Precedence: bulk Reply-To: apnic-talk@apnic.net [Note "reply-to:" field] Summary Both ARIN and the RIPE NCC have had discussions with the Internet communities in their region concerning the size of address prefixes to be assigned to IPv6 end sites. APNIC is now seeking input from the community in the Asia Pacific region on this issue. If you care about this, please read on. Some background The existing IPv6 policy document 'Provisional IPv6 Assignment and Allocation Policy Document' was published in May 1999. Formal revision of the document commenced in October 1999. The existing document is available at: http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html Feedback on the existing document was collected from the Internet community at large facilitated through the regional processes of consultation by the RIRs as well as input from the membership of the 6bone and the IETF IPv6 working groups. The deadline for comments was 31st January 2000. On 29th March, the RIRs, chairs of the IPv6 related IETF working groups and 6bone particpants met in Adelaide. The purpose of the meeting was to expand and elaborate in person on the comments made by the IAB/IETF/6bone concerning the existing policy document. One of the issues of concern that had been previously raised by members is the size of the end-site prefix (the 'SLA ID', currently defined in rfc2374 as 16 bits at a /48). This includes *all* types of end-sites including a single device. A /48 is sufficient address space to create 64K of subnets. The technical motivation for the 16 bit SLA ID field and the 'one size fits all' principle was described in rfc2374 as: "The size of the Site-Level Aggregation Identifier field is 16 bits. This supports 65,535 individual subnets per site. The design goal for the size of this field was to be sufficient for all but the largest of organizations. Organizations which need additional subnets can arrange with the organization they are obtaining Internet service from to obtain additional site identifiers and use this to create additional subnets. The Site-Level Aggregation Identifier field was given a fixed size in order to force the length of all prefixes identifying a particular site to be the same length (i.e., 48 bits). This facilitates movement of sites in the topology (e.g., changing service providers and multi-homing to multiple service providers)." It is possible to imagine in future a variety of types of end-sites being connected to the Internet. Some of these devices will be part of routed networks and others will not. The question proposed is whether 'one size fits all' (the /48) is appropriate for all end-sites? Both the RIPE and ARIN communities have rejected this. APNIC has been asked to consult with the Internet community in the Asia Pacific on this issue. To date, there has been no consensus on what alternatives should be taken, but 3 different approaches have been identified in addition to the 16 bit SLA ID field specified in rfc2374. These are: 1) /64 for single devices (such as mobile phones), /48 for all other sites 2) /64 for single devices, /48 for large end sites which need more than 256 subnets, and /56 for other sites (eg small, domestic/home sites) 3) Assign what is needed for the forseeable needs of the site, as a variable-length prefix of between /48 and /64. (It is important to remember that for any site that becomes multi-homed it is necessary to use equal length prefixes from each provider even in the case where one provider has allocated more prefix space than the other). We are interested in your opinions, so that we may convey this to the other RIRs and to the IETF community. Please direct all follow up discussion and comments to . For details of how to subscribe to this mailing list, please visit our web site at: http://www.apnic.net/general.html#mailing-lists . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + APNIC Secretariat Tel: +61-7-3367-0490 Asia Pacific Network Information Centre (APNIC) Ltd Fax: +61-7-3367-0482 Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net * From owner-apnic-announce@lists.apnic.net Mon Jul 10 12:28:16 2000 Received: (from majordom@localhost) by whois.apnic.net (8.9.3/8.9.3) id MAA116173; Mon, 10 Jul 2000 12:28:11 +1000 (EST) Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by whois.apnic.net (8.9.3/8.9.3) with ESMTP id MAA116169 for ; Mon, 10 Jul 2000 12:28:10 +1000 (EST) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id MAA00393 for ; Mon, 10 Jul 2000 12:28:07 +1000 (EST) Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1) id xma000387; Mon, 10 Jul 00 12:27:50 +1000 Received: from wilson (wrk-20.staff.apnic.net [192.168.1.82]) by hadrian.staff.apnic.net (8.9.3/8.9.3) with SMTP id MAA12397 for ; Mon, 10 Jul 2000 12:27:50 +1000 (EST) From: "Paul Wilson" To: Subject: [apnic-announce] FW: [icann-announce] ICANN Update: Yokohama Meetings and At Large Elections Date: Mon, 10 Jul 2000 12:27:49 +1000 Message-ID: <006a01bfea16$70ef3c10$5201a8c0@wilson.staff.apnic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal X-MIME-Autoconverted: from 8bit to quoted-printable by hadrian.staff.apnic.net id MAA12397 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by whois.apnic.net id MAA116170 Sender: owner-apnic-announce@lists.apnic.net Precedence: bulk Reply-To: apnic-talk@apnic.net [Note "reply-to:" field] -----Original Message----- From: icann-announce@icann.org [mailto:icann-announce@icann.org] Sent: Sunday, 9 July 2000 12:01 To: ICANN Announcement List Subject: [icann-announce] ICANN Update: Yokohama Meetings and At Large Elections This update collects a number of new and noteworthy postings on the ICANN website, including info on the ICANN Yokohama meetings, the At Large election process, and ICANN 2001 meeting schedule. 1. YOKOHAMA MEETINGS (13 - 17 July, 2000) Now less than one week away from the start of the ICANN Yokohama meetings, there has been a lot of activity on the ICANN website: Updated schedule and agenda information has been posted at . Newcomers (and interested old-timers) are invited to the ICANN Orientation Workshop on 13 July (09:00-12:00). Hosted by ICANN and JPNIC, the Workshop will present a comprehensive introduction to the ICANN process, including ICANN's technical coordination responsibilities, structure, supporting organizations, at large membership, along with some of the issues on the agenda for Yokohama. The following agenda documents have been posted for public review and comment: * New Top-Level Domains * At Large Membership and Elections * ccTLD Delegation and Administration Policies * Definition of ICANN's Geographic Regions * Board Meeting Minutes and Updates These issues are on the agenda for the ICANN Public Forum on 16 July. Those unable to attend the Yokohama meetings in person will find webcast and remote participation information at . ICANN is honored to acknowledge the outstanding support and assistance of JPNIC and the ICANN Yokohama Host Committee. 2. AT LARGE ELECTIONS If you have received your PIN letter, please remember to visit the website at to activate your membership. ICANN's At Large membership pages have been translated and posted in the following languages: * English: * Chinese: * Français: * Deutsch: * Japanese: * Korean: * Português: * Español: Recent membership application statistics are posted at The currently proposed schedule for the At Large Election process is as follows: (a) Determination of the ballot (now - August 31) (i) Nominations by the Nominating Committee (now - July 31) (ii) Member-nomination process (August 1 - August 31) (b) Voter education/dialogue phase (September 1 - September 30) (c) Online vote (October 1 - October 10) (This schedule runs approximately 10 days later than what had previously been posted.) The Nominating Committee is seeking recommendations and expressions of interest from potential candidates for the At Large seats on the ICANN Board. The Election Committee has posted a number of proposals for the election process, including rules for member-nomination, voter education and dialogue, and monitoring and oversight . 3. 2001 MEETING SCHEDULE The ICANN meeting schedule for 2001 has been tentatively set: March 2001 South Asia/Pacific (possibly Australia) June 2001 Europe September 2001 Latin America/Caribbean November 2001 United States (West Coast), or Canada A call for local host proposals with detailed requirements has been posted at . For the March 2001 meeting, the deadline for proposals is July 31, 2000. * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net * From owner-apnic-announce@lists.apnic.net Thu Jul 27 16:28:48 2000 Received: (from majordom@localhost) by whois.apnic.net (8.9.3/8.9.3) id QAA86728; Thu, 27 Jul 2000 16:28:36 +1000 (EST) Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by whois.apnic.net (8.9.3/8.9.3) with ESMTP id QAA86432; Thu, 27 Jul 2000 16:22:56 +1000 (EST) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id QAA25951; Thu, 27 Jul 2000 16:22:51 +1000 (EST) Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1) id xma025938; Thu, 27 Jul 00 16:22:43 +1000 Received: from wilson (wilson.staff.apnic.net [192.168.1.36]) by hadrian.staff.apnic.net (8.9.3/8.9.3) with SMTP id QAA06511; Thu, 27 Jul 2000 16:22:43 +1000 (EST) From: "Paul Wilson" To: Cc: , "Apng-All" , Subject: [apnic-announce] Call for Nominations - Asia-Pacific AC Representatives Date: Thu, 27 Jul 2000 16:22:40 +1000 Message-ID: <006701bff793$111ade90$2401a8c0@wilson.staff.apnic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-apnic-announce@lists.apnic.net Precedence: bulk Reply-To: apnic-talk@apnic.net [Note "reply-to:" field] [with apologies for duplicates] Call for Nominations Asia-Pacific Representatives to the ASO Address Council ------------------------------------------------------- This is a call for nominations of individuals from the Asia Pacific region, to serve on the ASO Address Council. During October 2000, one Asia-Pacific Address Council seat will become vacant, and will be filled for the next three years by an individual nominated through this open call. The selection process will involve an open election to be held during the APNIC Open Policy Meeting, in Brisbane, Australia, from 25 to 27 October 2000. This document describes the functions of the ASO and the Address Council, as well as the nomination and selection processes. If you are interested in nominating an individual, or if you are interested in being nominated as a member of the Address Council, please read through this document carefully. 1. The Address Supporting Organisation -------------------------------------- The ASO was formed in August 1999 as a consensus-based advisory body within the ICANN Framework, though a Memorandum of Understanding (MoU) signed by the current Regional Internet Registries and ICANN. The ICANN Bylaws (http://www.icann.org/general/bylaws.htm#VI-A) assign to the ASO the responsibility for the development of global policies relating to the distribution and registration of Internet address space, inter-domain routing identifiers and that part of the DNS name space that is used to name these addresses and identifiers. More information about the ASO is available at: http://www.aso.icann.org 2. The Address Council ---------------------- The ASO Address Council co-ordinates the process of policy development in areas within the responsibility of the ASO, according to procedures defined within the MoU and by the AC itself. Specifically, these include the hosting of an annual open General Assembly meeting (the first of which was held in Budapest in May 2000), and attending regular meetings by teleconference or in person at which policy issues and submissions may be considered. The other major responsibility of the Address Council is the appointment of individuals to fill ASO seats on the ICANN Board of Directors, according to procedures defined within the MoU. More information on the Address Council is available at: http://www.aso.icann.org/ac/ 3. The Role of Members of the Address Council --------------------------------------------- Each member of the Address Council is expected to serve for a period of 3 years. The terms of appointment of the current initial AC members were staggered terms of 1, 2 and 3 years to allow one third of the Address Council to be replaced in each subsequent year. No member of the Address Council is entitled to any compensation from the ASO. No member of the Address Council can be indemnified by the ASO, nor can the ASO obtain insurance coverage relating to the liability of the actions of members of the Address Council. AC members do not represent any RIR, nor do they act as representatives of any other body. They are appointed in their individual capacity, and their membership cannot be proxied by any other individual or organisation. 4. Address Council Nominations Process -------------------------------------- One individual from the Asia Pacific Region will be selected to serve on the Address Council for three years, replacing Dr Hyunje Park who has served as an initial AC member for the past year. The selection will be made though an open election from the set of individuals who have been nominated within this process. Any individual may be nominated, with the exception of any staff member of any Regional Internet Registry. Self-nominations are permitted. Nominations should be sent by email to , by midnight GMT on 25 September 2000. The information included with the nomination is to be in English and should include: Name of Nominee: Country of residence: Organisation: Email Address: Postal Address: Biographical information: Motivation for nomination: Name of nominating individual: Organisation: Email Address: All nominees will be contacted via email to confirm their willingness to serve on the Address Council. If a nominee is not contactable via email, or does not respond, then their nomination will not be confirmed and they will not be eligible for election to the Address Council. All confirmed nominations will be listed on the APNIC web site after they are confirmed. All nominees will have the opportunity to submit a written statement in support of their nomination, for publication on the web site. In addition, others may express support for nominated individuals simply by completing and submitting the nomination form provided above. 5. Address Council Selection Process ------------------------------------ The process for selection of the nominee to serve on the Address Council will involve an open election to be held during the APNIC Open Policy Meeting, in Brisbane Australia, from 25 to 27 October 2000. While it is not necessary for nominees to attend this meeting in order to be elected, an opportunity will be provided for nominees who are present to address the meeting prior to the election and make a statement supporting their nomination. More information on this meeting is available at: http://www.apnic.net/meetings --- This announcement will be made available at: http://www.apnic.net/news --- * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net * From owner-apnic-announce@lists.apnic.net Thu Jul 27 16:40:57 2000 Received: (from majordom@localhost) by whois.apnic.net (8.9.3/8.9.3) id QAA86728; Thu, 27 Jul 2000 16:28:36 +1000 (EST) Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100]) by whois.apnic.net (8.9.3/8.9.3) with ESMTP id QAA86432; Thu, 27 Jul 2000 16:22:56 +1000 (EST) Received: (from mail@localhost) by guardian.apnic.net (8.9.3/8.9.3) id QAA25951; Thu, 27 Jul 2000 16:22:51 +1000 (EST) Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1) id xma025938; Thu, 27 Jul 00 16:22:43 +1000 Received: from wilson (wilson.staff.apnic.net [192.168.1.36]) by hadrian.staff.apnic.net (8.9.3/8.9.3) with SMTP id QAA06511; Thu, 27 Jul 2000 16:22:43 +1000 (EST) From: "Paul Wilson" To: Cc: , "Apng-All" , Subject: [apnic-announce] Call for Nominations - Asia-Pacific AC Representatives Date: Thu, 27 Jul 2000 16:22:40 +1000 Message-ID: <006701bff793$111ade90$2401a8c0@wilson.staff.apnic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-apnic-announce@lists.apnic.net Precedence: bulk Reply-To: apnic-talk@apnic.net [Note "reply-to:" field] [with apologies for duplicates] Call for Nominations Asia-Pacific Representatives to the ASO Address Council ------------------------------------------------------- This is a call for nominations of individuals from the Asia Pacific region, to serve on the ASO Address Council. During October 2000, one Asia-Pacific Address Council seat will become vacant, and will be filled for the next three years by an individual nominated through this open call. The selection process will involve an open election to be held during the APNIC Open Policy Meeting, in Brisbane, Australia, from 25 to 27 October 2000. This document describes the functions of the ASO and the Address Council, as well as the nomination and selection processes. If you are interested in nominating an individual, or if you are interested in being nominated as a member of the Address Council, please read through this document carefully. 1. The Address Supporting Organisation -------------------------------------- The ASO was formed in August 1999 as a consensus-based advisory body within the ICANN Framework, though a Memorandum of Understanding (MoU) signed by the current Regional Internet Registries and ICANN. The ICANN Bylaws (http://www.icann.org/general/bylaws.htm#VI-A) assign to the ASO the responsibility for the development of global policies relating to the distribution and registration of Internet address space, inter-domain routing identifiers and that part of the DNS name space that is used to name these addresses and identifiers. More information about the ASO is available at: http://www.aso.icann.org 2. The Address Council ---------------------- The ASO Address Council co-ordinates the process of policy development in areas within the responsibility of the ASO, according to procedures defined within the MoU and by the AC itself. Specifically, these include the hosting of an annual open General Assembly meeting (the first of which was held in Budapest in May 2000), and attending regular meetings by teleconference or in person at which policy issues and submissions may be considered. The other major responsibility of the Address Council is the appointment of individuals to fill ASO seats on the ICANN Board of Directors, according to procedures defined within the MoU. More information on the Address Council is available at: http://www.aso.icann.org/ac/ 3. The Role of Members of the Address Council --------------------------------------------- Each member of the Address Council is expected to serve for a period of 3 years. The terms of appointment of the current initial AC members were staggered terms of 1, 2 and 3 years to allow one third of the Address Council to be replaced in each subsequent year. No member of the Address Council is entitled to any compensation from the ASO. No member of the Address Council can be indemnified by the ASO, nor can the ASO obtain insurance coverage relating to the liability of the actions of members of the Address Council. AC members do not represent any RIR, nor do they act as representatives of any other body. They are appointed in their individual capacity, and their membership cannot be proxied by any other individual or organisation. 4. Address Council Nominations Process -------------------------------------- One individual from the Asia Pacific Region will be selected to serve on the Address Council for three years, replacing Dr Hyunje Park who has served as an initial AC member for the past year. The selection will be made though an open election from the set of individuals who have been nominated within this process. Any individual may be nominated, with the exception of any staff member of any Regional Internet Registry. Self-nominations are permitted. Nominations should be sent by email to , by midnight GMT on 25 September 2000. The information included with the nomination is to be in English and should include: Name of Nominee: Country of residence: Organisation: Email Address: Postal Address: Biographical information: Motivation for nomination: Name of nominating individual: Organisation: Email Address: All nominees will be contacted via email to confirm their willingness to serve on the Address Council. If a nominee is not contactable via email, or does not respond, then their nomination will not be confirmed and they will not be eligible for election to the Address Council. All confirmed nominations will be listed on the APNIC web site after they are confirmed. All nominees will have the opportunity to submit a written statement in support of their nomination, for publication on the web site. In addition, others may express support for nominated individuals simply by completing and submitting the nomination form provided above. 5. Address Council Selection Process ------------------------------------ The process for selection of the nominee to serve on the Address Council will involve an open election to be held during the APNIC Open Policy Meeting, in Brisbane Australia, from 25 to 27 October 2000. While it is not necessary for nominees to attend this meeting in order to be elected, an opportunity will be provided for nominees who are present to address the meeting prior to the election and make a statement supporting their nomination. More information on this meeting is available at: http://www.apnic.net/meetings --- This announcement will be made available at: http://www.apnic.net/news --- * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net *