From owner-apops Wed Jul 1 21:32:07 1998 Received: by teckla.apnic.net (8.9.0/8.9.0) id VAA14384 for apops-out; Wed, 1 Jul 1998 21:32:07 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by teckla.apnic.net (8.9.0/8.9.0) with ESMTP id VAA14374 for ; Wed, 1 Jul 1998 21:31:58 +0900 (JST) Received: from zed.isi.edu (zed.isi.edu [128.9.160.57]) by zephyr.isi.edu (8.8.7/8.8.6) with SMTP id FAA12393; Wed, 1 Jul 1998 05:34:48 -0700 (PDT) Posted-Date: Wed, 01 Jul 1998 07:25:33 -0500 Message-Id: <199807011230.AA08656@zed.isi.edu> Received: from lazy-boy.isi.edu by zed.isi.edu (5.65c/4.0.3-6) id ; Wed, 1 Jul 1998 05:30:57 -0700 X-Sender: bmanning@zephyr.isi.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 01 Jul 1998 07:25:33 -0500 To: pier@isi.edu From: bill manning Subject: [apops] really dead. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-apops@apnic.net Precedence: bulk Hi, It seems that the IETF has caught up with us and has formally shut down the PIER wg. I am aware that there were a couple of unfinished items and there have recently been some questions on renumbering documents that did not quite make it out of the pipeline before we were closed down. Also, there is apparently a move to view renumbering as a migration stratagy for IPv6. If there is enough interest in revisting what PIER has done or might do, esp. wrt. IPv6 migration and/or compliance w/ addressing registry or provider delegation policies, I'd appreciate hearing from you. --bill * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Wed Jul 1 21:32:59 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id VAA14424 for apops-out; Wed, 1 Jul 1998 21:32:59 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by teckla.apnic.net (8.9.0/8.9.0) with ESMTP id VAA14420 for ; Wed, 1 Jul 1998 21:32:55 +0900 (JST) Received: from zed.isi.edu (zed.isi.edu [128.9.160.57]) by zephyr.isi.edu (8.8.7/8.8.6) with SMTP id FAA12453; Wed, 1 Jul 1998 05:35:46 -0700 (PDT) Posted-Date: Wed, 01 Jul 1998 07:36:58 -0500 Message-Id: <199807011231.AA08707@zed.isi.edu> Received: from lazy-boy.isi.edu by zed.isi.edu (5.65c/4.0.3-6) id ; Wed, 1 Jul 1998 05:31:55 -0700 X-Sender: bmanning@zephyr.isi.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 01 Jul 1998 07:36:58 -0500 To: pier@isi.edu From: bill manning Subject: [apops] really dead. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-apops@apnic.net Precedence: bulk Hi, It seems that the IETF has caught up with us and has formally shut down the PIER wg. I am aware that there were a couple of unfinished items and there have recently been some questions on renumbering documents that did not quite make it out of the pipeline before we were closed down. Also, there is apparently a move to view renumbering as a migration stratagy for IPv6. If there is enough interest in revisting what PIER has done or might do, esp. wrt. IPv6 migration and/or compliance w/ addressing registry or provider delegation policies, I'd appreciate hearing from you. --bill * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Sat Jul 4 04:00:23 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id EAA16480 for apops-out; Sat, 4 Jul 1998 04:00:23 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.43.26]) by teckla.apnic.net (8.9.0/8.9.0) with SMTP id EAA16476 for ; Sat, 4 Jul 1998 04:00:17 +0900 (JST) Received: from cisco.com (localhost [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA20980; Fri, 3 Jul 1998 12:00:03 -0700 Message-Id: <199807031900.MAA20980@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 03 Jul 1998 12:00:03 -0700 From: Tony Bates Sender: owner-apops@apnic.net Precedence: bulk This is an auto-generated mail on Fri Jul 3 12:00:00 PDT 1998 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 03Jul98 0) General Status Table History ------------- Date Prefixes 190698 51379 200698 51329 210698 51500 220698 51541 230698 51362 240698 51537 250698 51460 260698 51523 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 2703 Number of ASes announcing only one prefix: 828 (0 cidr, 828 classful) Largest number of cidr routes: 0 announced by Largest number of classful routes: 1145 announced by AS701 1) Gains by aggregating at the origin AS level --- 03Jul98 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4293 452 247 205 45.4% IMCI AS2493 488 283 205 42.0% iSTAR Internet, Inc. AS3602 511 313 198 38.7% Sprint Canada Inc. AS701 1145 950 195 17.0% Alternet AS271 336 145 191 56.8% BCnet Backbone AS3749 218 70 148 67.9% TECNET AS174 725 587 138 19.0% Performance Systems International AS4755 106 32 74 69.8% Videsh Sanchar Nigam Ltd. India AS3218 78 7 71 91.0% AS-RSSI AS7046 218 148 70 32.1% UUNET-CUSTOMER AS3221 112 42 70 62.5% EENet Autonomous System AS6227 96 28 68 70.8% !nteract AS10928 107 42 65 60.7% UNKNOWN AS5668 116 54 62 53.4% Century Telephone Inc. AS3804 208 146 62 29.8% Bell Solutions AS4740 382 328 54 14.1% ASN-OZEMAIL (Ozemail Pty Ltd) AS3403 180 127 53 29.4% TIAC AS2685 133 83 50 37.6% IBM Global Network - US AS549 194 145 49 25.3% ONet Backbone AS8517 120 72 48 40.0% ULAKNET-ASN AS72 85 37 48 56.5% Schlumberger Information Network AS6335 68 20 48 70.6% NTRNET AS4539 73 25 48 65.8% NETROPOLIS AS4200 145 97 48 33.1% AGIS (Apex Global Information Ser AS1239 543 496 47 8.7% SprintLink Backbone AS719 449 405 44 9.8% LANLINK autonomous system AS852 158 116 42 26.6% AGT Advance Communication AS762 118 80 38 32.2% WELLFLEET-AS AS6181 65 28 37 56.9% FUSE-NET AS4763 109 72 37 33.9% Telstra New Zealand For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Sat Jul 11 06:13:53 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id EAA01860 for apops-out; Sat, 11 Jul 1998 04:00:39 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.43.26]) by teckla.apnic.net (8.9.0/8.9.0) with SMTP id EAA01854 for ; Sat, 11 Jul 1998 04:00:29 +0900 (JST) Received: from cisco.com (localhost [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA29526; Fri, 10 Jul 1998 12:00:03 -0700 Message-Id: <199807101900.MAA29526@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 10 Jul 1998 12:00:02 -0700 From: Tony Bates Sender: owner-apops@apnic.net Precedence: bulk This is an auto-generated mail on Fri Jul 10 12:00:01 PDT 1998 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 10Jul98 0) General Status Table History ------------- Date Prefixes 020798 51673 030798 51528 050798 51481 060798 51579 070798 52104 080798 52116 090798 52255 100798 52359 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 213.102.1.0 from AS3259 *** Bogus 214.0.0.0/8 from AS568 *** Bogus 215.0.0.0/9 from AS568 *** Bogus 216.0.0.0/14 from AS2548 *** Bogus 216.13.4.0/23 from AS6401 *** Bogus 216.13.32.0/19 from AS6401 *** Bogus 216.15.0.0/19 from AS10368 *** Bogus 216.15.128.0/19 from AS7393 *** Bogus 216.19.0.0/18 from AS4492 *** Bogus 216.214.0.0/18 from AS7194 AS Summary ---------- Number of ASes in routing system: 3726 Number of ASes announcing only one prefix: 1823 (952 cidr, 871 classful) Largest number of cidr routes: 353 announced by AS3561 Largest number of classful routes: 1139 announced by AS701 1) Gains by aggregating at the origin AS level --- 10Jul98 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS4293 461 253 208 45.1% IMCI AS3602 514 310 204 39.7% Sprint Canada Inc. AS2493 485 281 204 42.1% iSTAR Internet, Inc. AS701 1139 937 202 17.7% Alternet AS271 339 144 195 57.5% BCnet Backbone AS3749 223 66 157 70.4% TECNET AS174 727 587 140 19.3% Performance Systems International AS2685 267 162 105 39.3% IBM Global Network - US AS4755 114 39 75 65.8% Videsh Sanchar Nigam Ltd. India AS3221 112 42 70 62.5% EENet Autonomous System AS5668 120 51 69 57.5% Century Telephone Inc. AS7046 226 161 65 28.8% UUNET-CUSTOMER AS3804 216 153 63 29.2% Bell Solutions AS4740 394 334 60 15.2% ASN-OZEMAIL (Ozemail Pty Ltd) AS10928 102 45 57 55.9% UNKNOWN AS3403 181 127 54 29.8% TIAC AS549 205 152 53 25.9% ONet Backbone AS8517 123 72 51 41.5% ULAKNET-ASN AS6335 69 18 51 73.9% NTRNET AS72 85 37 48 56.5% Schlumberger Information Network AS4539 73 25 48 65.8% NETROPOLIS AS1239 543 496 47 8.7% SprintLink Backbone AS719 449 403 46 10.2% LANLINK autonomous system AS3218 70 24 46 65.7% AS-RSSI AS4200 140 95 45 32.1% AGIS (Apex Global Information Ser AS852 158 117 41 25.9% AGT Advance Communication AS7545 102 61 41 40.2% TPG Internet Pty Ltd AS762 118 80 38 32.2% WELLFLEET-AS AS1785 290 252 38 13.1% NYSERNet Backbone AS6181 65 28 37 56.9% FUSE-NET For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Tue Jul 14 19:33:13 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id TAA26760 for apops-out; Tue, 14 Jul 1998 19:29:52 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from psg.com (root@psg.com [147.28.0.62]) by teckla.apnic.net (8.9.0/8.9.0) with SMTP id TAA26734 for ; Tue, 14 Jul 1998 19:29:39 +0900 (JST) Received: from localhost (16121 bytes) by psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Tue, 14 Jul 1998 03:32:30 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Feb-8) Date: Tue, 14 Jul 1998 03:32:29 -0700 (PDT) From: "Steven G. Huter" X-Sender: sghuter@psg.com To: enredo@reacciun.ve, AFRIK-IT@LISTSERV.HEANET.IE, apops@apnic.net cc: iana@iana.org Subject: [apops] Implementation of a New IANA Organization (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apops@apnic.net Precedence: bulk I forward this for those of you in America Latina y el Caribe, Africa, and Asia who have an interest in the implementation of a new IANA organization, and how you can participate. As stated in the document below, "A critical issue is how to ensure that the Board is truly an international body that represents the various stakeholders around the world. ...... Suggestions on how to ensure that the Board is truly an international body are solicited." To keep the process respectful and productive, please be constructive with any comments or criticisms you would like to offer. Regards - Saludos - Amicalement, Steve Huter The Network Startup Resource Center (NSRC) http://www.nsrc.org/ ---------- Forwarded message ---------- Date: Mon, 13 Jul 1998 17:41:59 -0700 (PDT) From: Jon Postel To: iana-announce@ISI.EDU Cc: postel@ISI.EDU, iana@ISI.EDU Subject: Implementation of a New IANA Organization ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hello: The Internet Assigned Numbers Authority (IANA) is pleased to welcome you to this list of people with an interest in the formation of a new IANA. To help focus efforts and facilitate consensus towards the implementation of a new organization, we will be sending you various announcements and drafts for your review and comments. --jon. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPLEMENTATION OF A NEW INTERNET ASSIGNED NUMBERS AUTHORITY (IANA) I. Introduction This is an expanded version of IANA's earlier discussion draft posted on 26 June 1998 on the implementation of the new not-for-profit Corporation referred to in the U.S Government's white paper on "Management of Internet Names and Addresses." This draft reflects both a variety of input on earlier documents as well as reports from the Reston and Brussels meetings concerning this issue. This draft will continue to evolve as input is received through additional international meetings in Geneva and Singapore and from comments received directly at IANA. We emphasize that this paper is a compilation of ideas expressed by the Internet community and are explicitly intended to be discussed. We encourage everyone to comment. Our only request is that the comments be substantive, and that any criticisms be accompanied by specific suggestions for change or improvement. Comments on any part of this document are welcome and solicited, and can be sent via email to comments@iana.org. Comments concerning this draft will be posted at www.iana.org (click on "New IANA", then click on "Public Comments"). II. Purposes The purpose of the new Corporation should be maintaining the operational stability of the Internet by: (1) coordinating the assignment of Internet technical parameters as needed to maintain universal connectivity on the Internet; (2) managing and performing functions related to the coordination of the Internet address space; (3) managing and performing functions related to the coordination of the Internet domain name system; and (4) overseeing operation of the authoritative Internet root server system. III. Offices Given the historical functions performed in the United States, and the need to transition these functions to the new Corporation, incorporation as a non-profit corporation in the United States, and probably in California, is a logical step. The nature and character of the new Corporation's Board will be the true test of its ability to represent the interests of stakeholders around the world. There have been suggestions that point to the advantages of creating an additional office(s) outside of the U.S. Suggestions on the proposed responsibilities and location(s) of this office(s) are solicited. IV. Scope of Activities The Corporation should be dedicated to preserving the operational stability of the central coordinating functions of the global Internet for the public good. It should operate as a not-for-profit, cost-recovery, nonpartisan corporation for charitable and public purposes. V. Board 1. Powers The powers of the Corporation should be exercised, its property controlled and its business and affairs conducted, by or under the direction of the Board. Unless otherwise provided, the Board should act by a majority vote of Directors present at a meeting, subject to the quorum requirements. 2. Number and Qualification It is critical that the Corporation's Board meet several criteria: (1) represent the different interests of the various types of stakeholders; (2) represent relevant interests from around the world; (3) be able to function effectively. The Board should be comprised as follows: (a) Three (3) Directors nominated by the Address Supporting Organization; (b) Three (3) Directors nominated by the Domain Name Supporting Organization; (c) Three (3) Directors nominated by the Protocol Supporting Organization; and (d) Six (6) Directors nominated by the Industry/User Supporting Organization. The important condition is that the Board as ultimately constituted be representative of the diversity of stakeholders. A critical issue is how to ensure that the Board is truly an international body that represents the various stakeholders around the world. There are a variety of ways this might be accomplished, including (1) limiting the number of directors from any one country to no more than a specified percentage of the directors, or (2) requiring those persons nominated for the Board by the various nominating organizations to be persons of diverse nationality. Suggestions on how to ensure that the Board is truly an international body are solicited. Each Board member should represent the interests of the Internet community as a whole. Once he or she takes a Board seat, he or she should not be the representative of a specific group, country, or region, but rather a fiduciary for all those interested in and affected by the operation of the Internet. It is critical that the new Corporation be up and running sufficiently before September 30, 1998 so that it can undertake to manage, in conjunction with the Department of Commerce, the transition that is scheduled to take place at that time. Thus, the Initial Board will almost inevitably have to be a true consensus group, arising out of the various meetings and discussions between the various interested stakeholders. Such a group might consist of clearly qualified and respected senior figures who would not participate in the governance of this new Corporation past this initial period, and who could undertake to both manage the initial period and to develop consensus in the Internet community regarding further structural and operational details of the new Corporation. Such an Initial Board should serve for a relatively short time -- no more than one term -- and should be responsible for recognizing the Supporting Organizations that should be the source of regular Board nominations. To ensure an effective transition, and to maintain Internet stability throughout the transition, the Initial Board should probably not all be replaced at the same time. Suggestions on how to create an effective transition mechanism from the Initial Board to the Permanent Board are solicited. Because of the limited time available for a new Corporation to be created, and to minimize any transition difficulties, concrete suggestions as to who might be appropriate to serve on such an Initial Board should be made as soon as possible. Suggestions for Initial Board candidates are solicited. 3. Conflict of Interest Each Director should be responsible for disclosing to the Corporation any matter that could reasonably be perceived to make such Director an "interested director" or any relationship or other factor that could reasonably be perceived to be a conflict of interest. Board members should be required to recuse themselves from any decisions in which they have a direct interest. 4. Election and Term New Directors should be installed at each annual meeting of the Board to hold office until the end of their terms. Except for the Initial Board, the regular term of office of a Director elected should be three (3) years. Any Directors should be able to serve additional terms provided that the total years of continuous service does not exceed six (6). The Board should also arrange for the terms of the Directors to be staggered by providing that of the first Permanent Board elected, five Directors should serve an initial term of one (1) year, five Directors should serve an initial term of two (2) years, and five Directors should serve an initial term of three (3) years. Suggestions on how these staggered terms should be apportioned for the first Permanent Board are solicited. 5. Compensation The Directors should receive no compensation for their services as Directors. The Board may, however, authorize the reimbursement of actual and necessary expenses incurred by Directors performing duties as Directors. VI. Supporting Organizations 1. Powers The Supporting Organizations should serve as advisory bodies to the Board and should have such powers and duties as may be prescribed by the Board and the bylaws. The Board should be able to add additional, or remove existing, Supporting Organizations by a two-thirds (2/3) majority vote of all members of the Board. The Supporting Organizations should be responsible for nominating Directors to the Board and for recommending policies and procedures regarding the governance and operation of the Corporation as well as the general Internet infrastructure. The Board should approve or reject policies and procedures recommended by the Supporting Organizations subject to review for (1) compliance with the articles and bylaws, (2) fair and open process, and (3) absence of unresolved conflicts between Supporting Organizations. The Supporting Organizations also should constitute the primary funding sources for the Corporation in accordance with the policies established by the Board. In the interest of providing the framework for the organization before September 30, 1998, special arrangements should be made for the transitional period, focusing on unconditional corporate or charitable grants, with the permanent funding mechanism to be established by the Initial Board. Suggestions for initial funding are solicited. 2. Qualifications for Membership Minimal qualifications for membership in the Supporting Organizations should be established by the Board. Other than those minimal qualifications, however, each Supporting Organization should establish its own rules consistent with maintaining inclusive membership. The Board should also be able to prohibit unduly restrictive membership conditions. 3. Description and Responsibilities The bylaws should establish at least be the following Supporting Organizations: (a) The Address Supporting Organization should be composed of representatives from regional Internet address registries. Until such time as there are additional members in the Address Supporting Organization, Directors from this Supporting Organization should represent the American Registry for Internet Numbers ("ARIN"), the Asia Pacific Network Information Center ("APNIC") and Reseaux IP Europeens ("RIPE NCC"). The Address Supporting Organization should organize a committee called the Address Council to make recommendations to the Board regarding policies and procedures for the assignment of Internet addresses. (b) The Domain Name Supporting Organization should be composed of representatives from name registries and registrars of both generic/global and country-code top level domains ("TLDs") and other entities with interests in these issues (for example, entities interested in trademark and related issues). The Domain Name Supporting Organization should organize a committee called the Name Council to make recommendations to the Board regarding policies and procedures relating to top level (generic/global and country-code) domains, including operation, assignment, and management of the domain name system. (c) The Protocol Supporting Organization should be composed of representatives from the Internet protocol organizations. Until such time as there are additional members in the Protocol Supporting Organization, the Internet Architecture Board should act as the Protocol Supporting Organization. The Protocol Supporting Organization should organize a committee called the Protocol Council to make recommendations regarding policies and procedures regarding the management of protocol numbers, port numbers, and other technical parameters. (d) The Industry/User Supporting Organization should be composed of representatives of organizations that represent Internet users. The Industry/User Committee should organize a committee called the Industry/User Council to make recommendations regarding the advancement of the purposes and capabilities of the Internet, the needs of Internet users, and other matters concerning the use of the Internet. Suggestions on how the Industry/User Supporting Organization could be constituted, and whether it would be preferable to divide this Supporting Organization into two or more separate entities are solicited. VII. Officers The initial officers of the Corporation should be a Chairperson of the Board, a Chief Technology Officer (CTO), a President or Chief Executive Officer (CEO), and a Treasurer/Chief Financial Officer. The Board should be free to add additional officers as needed. VIII. Indemnification The Directors and staff of the Corporation should be indemnified by the Corporation from any personal liability or expense from developing, promulgating, or implementing the policies adopted by the Board. IX. Public Process The Corporation should engage independent auditors on an ongoing basis. The Corporation should operate to the maximum extent possible in an open and transparent manner at all levels. Board and Supporting Organization meetings should be open to the public, unless and except to the extent that executive sessions are expressly instituted for stated reasons, and minutes and other materials should be published and available on the Internet. X. Bylaws Any bylaws adopted by the Corporation should be altered, amended, or repealed and new bylaws adopted only upon action by two-thirds (2/3) majority vote of all members of the Board. The initial bylaws of the Corporation should be transitional in nature and aid in the initial governance of the Corporation. Consistent with this purpose, the initial bylaws should be reviewed and replaced as deemed necessary or appropriate by the Permanent Board within one (1) year after it is elected. However, the initial bylaws should remain in full force and effect until such time as they are amended or replaced. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you know someone who should be added to this list, please have them send a message to majordomo@iana.org with the line "subscribe iana-announce" as the body of the message. To remove yourself from this list, please send a message to majordomo@iana.org with the line "unsubscribe iana-announce" as the body of the message. ========================================================================= The Internet Assigned Numbers Authority (IANA) P.O. Box 12607 Marina del Rey, CA 90295-3607 "Dedicated to preserving the central coordinating functions of the global Internet for the public good." ========================================================================= * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Sat Jul 18 04:00:40 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id EAA11449 for apops-out; Sat, 18 Jul 1998 04:00:40 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.43.26]) by teckla.apnic.net (8.9.0/8.9.0) with SMTP id EAA11445 for ; Sat, 18 Jul 1998 04:00:34 +0900 (JST) Received: from cisco.com (localhost [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA29542; Fri, 17 Jul 1998 12:00:06 -0700 Message-Id: <199807171900.MAA29542@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 17 Jul 1998 12:00:02 -0700 From: Tony Bates Sender: owner-apops@apnic.net Precedence: bulk This is an auto-generated mail on Fri Jul 17 12:00:00 PDT 1998 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 17Jul98 0) General Status Table History ------------- Date Prefixes 100798 52359 110798 52365 120798 52291 130798 52391 140798 52359 150798 52389 160798 52656 170798 52681 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 213.102.1.0 from AS3259 *** Bogus 214.0.0.0/8 from AS568 *** Bogus 215.0.0.0/9 from AS568 *** Bogus 216.0.0.0/14 from AS2548 *** Bogus 216.13.0.0/19 from AS6401 *** Bogus 216.13.32.0/19 from AS6401 *** Bogus 216.15.0.0/19 from AS10368 *** Bogus 216.15.128.0/19 from AS7393 *** Bogus 216.16.0.0/19 from AS6304 *** Bogus 216.18.0.0/19 from AS6539 *** Bogus 216.19.0.0/18 from AS4492 *** Bogus 216.22.0.0/19 from AS7960 *** Bogus 216.23.0.0/19 from AS8079 *** Bogus 216.27.0.0 from AS7349 *** Bogus 216.214.0.0/18 from AS7194 AS Summary ---------- Number of ASes in routing system: 3750 Number of ASes announcing only one prefix: 1827 (964 cidr, 863 classful) Largest number of cidr routes: 360 announced by AS3561 Largest number of classful routes: 1143 announced by AS701 1) Gains by aggregating at the origin AS level --- 17Jul98 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS2493 485 278 207 42.7% iSTAR Internet, Inc. AS3602 516 311 205 39.7% Sprint Canada Inc. AS701 1143 941 202 17.7% Alternet AS271 340 144 196 57.6% BCnet Backbone AS4293 450 257 193 42.9% IMCI AS3749 223 66 157 70.4% TECNET AS174 731 589 142 19.4% Performance Systems International AS2685 266 161 105 39.5% IBM Global Network - US AS5668 135 49 86 63.7% Century Telephone Inc. AS2764 428 347 81 18.9% connect.com.au pty ltd AS4755 117 41 76 65.0% Videsh Sanchar Nigam Ltd. India AS3221 112 42 70 62.5% EENet Autonomous System AS3804 220 155 65 29.5% Bell Solutions AS7046 228 165 63 27.6% UUNET-CUSTOMER AS4740 401 344 57 14.2% ASN-OZEMAIL (Ozemail Pty Ltd) AS10928 102 45 57 55.9% UNKNOWN AS3403 179 127 52 29.1% TIAC AS8517 123 72 51 41.5% ULAKNET-ASN AS6335 68 19 49 72.1% NTRNET AS72 85 37 48 56.5% Schlumberger Information Network AS1239 540 493 47 8.7% SprintLink Backbone AS719 450 404 46 10.2% LANLINK autonomous system AS4539 71 26 45 63.4% NETROPOLIS AS4200 142 97 45 31.7% AGIS (Apex Global Information Ser AS852 157 116 41 26.1% AGT Advance Communication AS762 118 80 38 32.2% WELLFLEET-AS AS1785 287 249 38 13.2% NYSERNet Backbone AS6392 66 29 37 56.1% MidWest Communications, Inc. AS6181 65 28 37 56.9% FUSE-NET AS549 174 137 37 21.3% ONet Backbone For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Sat Jul 18 05:03:04 1998 Received: by teckla.apnic.net (8.9.0/8.9.0) id EAA11791 for apops-out; Sat, 18 Jul 1998 04:19:48 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by teckla.apnic.net (8.9.0/8.9.0) with ESMTP id EAA11786 for ; Sat, 18 Jul 1998 04:19:43 +0900 (JST) Received: (from bmanning@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id MAA21522; Fri, 17 Jul 1998 12:22:18 -0700 (PDT) From: Bill Manning Message-Id: <199807171922.MAA21522@zephyr.isi.edu> Subject: [apops] preliminary 3q98 results To: nanog@merit.edu, eof-list@ripe.net, apops@apnic.net, iepg@iepg.org Date: Fri, 17 Jul 1998 12:22:17 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-apops@apnic.net Precedence: bulk For your consideration. I appologise for duplicates. The 3rd quarter 1998 in-addr audit results. ------------------------------------------------------------------------- Refused are servers who refused to transfer the zone. Errors were generally related to the following conditions: - delegation to the host level e.g. 2.2.0.192.in-addr.arpa. This is also how the CNAME haq works for CIDR delegations so its hard to tell how much of an error this really is. - use of slashes e.g. 0/2.2.0.192.in-addr.arpa. An older method of doing bit-level delegation... - alpha strings e.g. test.2.0.192.in-addr.arpa. - other non-numberics e.g. #???.2.0.192.in-addr.arpa. - failure to fully qualify zones, e.g. the missing "." - event-horizon e.g. behind firewall Other failures seem to be related to server configuration or network reachability of either the end system or the nameservers used in generating the queries. The no-server number is the total of the refused, error, & other rows. inital zone runtime total# #correct no-svr refused error other 3q97 97667 657 h 380021 220030 57.9% 159991 26335 90832 42824 4q97 99587 654 h 478311 281368 58.8% 196861 26871 103108 66882 1q98 91555 372 h 500397 250107 50.1% 250210 54925 150114 45171 2q98 (1) 112 h 532504 253000 47.5% 279484 124626 31841 123017 3q98 100185 189 h 551631 277878 50.3% 273626 145592 (*) (*) (1) extrapolated from partial/overlapping data (corrupted disk) (*) intermediate results -- --bill * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net * From owner-apops Sat Jul 25 04:00:34 1998 Received: (from majordomo@localhost) by teckla.apnic.net (8.9.0/8.9.0) id EAA07421 for apops-out; Sat, 25 Jul 1998 04:00:34 +0900 (JST) X-Authentication-Warning: teckla.apnic.net: majordomo set sender to owner-apops@apnic.net using -f Received: from lovefm.cisco.com (lovefm.cisco.com [171.71.43.26]) by teckla.apnic.net (8.9.0/8.9.0) with SMTP id EAA07415 for ; Sat, 25 Jul 1998 04:00:27 +0900 (JST) Received: from cisco.com (localhost [127.0.0.1]) by lovefm.cisco.com (8.6.12/8.6.5) with ESMTP id MAA05304; Fri, 24 Jul 1998 12:00:03 -0700 Message-Id: <199807241900.MAA05304@lovefm.cisco.com> To: nanog@merit.edu cc: tbates@cisco.com, eof-list@ripe.net, apops@apnic.net, routing-wg@ripe.net Subject: [apops] The Cidr Report Date: Fri, 24 Jul 1998 12:00:02 -0700 From: Tony Bates Sender: owner-apops@apnic.net Precedence: bulk This is an auto-generated mail on Fri Jul 24 12:00:00 PDT 1998 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 24Jul98 0) General Status Table History ------------- Date Prefixes 170798 52681 180798 52642 190798 52713 200798 52774 210798 53149 220798 52850 230798 52922 240798 52857 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- AS Summary ---------- Number of ASes in routing system: 3754 Number of ASes announcing only one prefix: 1827 (958 cidr, 869 classful) Largest number of cidr routes: 353 announced by AS3561 Largest number of classful routes: 1137 announced by AS701 1) Gains by aggregating at the origin AS level --- 24Jul98 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS3602 525 313 212 40.4% Sprint Canada Inc. AS701 1137 934 203 17.9% Alternet AS271 344 144 200 58.1% BCnet Backbone AS4293 469 273 196 41.8% IMCI AS2493 432 254 178 41.2% iSTAR Internet, Inc. AS3749 223 66 157 70.4% TECNET AS174 723 586 137 18.9% Performance Systems International AS2685 267 162 105 39.3% IBM Global Network - US AS5668 134 50 84 62.7% Century Telephone Inc. AS3221 112 42 70 62.5% RIPE-ASNBLOCK4 AS4969 86 20 66 76.7% Net Access AS3804 220 155 65 29.5% Bell Solutions AS4755 114 50 64 56.1% Videsh Sanchar Nigam Ltd. India AS7046 228 165 63 27.6% UUNET-CUSTOMER AS4740 393 336 57 14.5% ASN-OZEMAIL (Ozemail Pty Ltd) AS10928 101 46 55 54.5% UNKNOWN AS3403 180 126 54 30.0% TIAC AS8517 122 72 50 41.0% UNKNOWN AS6335 68 19 49 72.1% NTRNET AS549 202 153 49 24.3% ONet Backbone AS72 85 37 48 56.5% Schlumberger Information Network AS1239 539 492 47 8.7% SprintLink Backbone AS719 452 406 46 10.2% LANLINK-AS AS4539 71 26 45 63.4% NETROPOLIS AS4200 144 99 45 31.2% AGIS (Apex Global Information Ser AS852 157 116 41 26.1% AGT Advance Communication AS1785 293 252 41 14.0% NYSERNet Backbone AS10459 48 7 41 85.4% WANSASN AS10921 57 19 38 66.7% KIHNETWORK AS762 117 80 37 31.6% WELLFLEET-AS For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report * APOPS: Asia Pacific Operations Forum * * To unsubscribe: send "unsubscribe" to apops-request@apnic.net *