From owner-apnic-talk Thu May 1 21:23:16 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id VAA09800 for apnic-talk-outgoing; Thu, 1 May 1997 21:23:16 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id VAA09795 for ; Thu, 1 May 1997 21:23:14 +0900 (JST) Received: by apnic-ttc.apnic.net; id VAA03648; Thu, 1 May 1997 21:11:11 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma003646; Thu, 1 May 97 21:10:55 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id VAA27748 for ; Thu, 1 May 1997 21:24:33 +0900 (JST) Message-Id: <199705011224.VAA27748@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: apnic-talk@apnic.net Subject: "No questions asked" policy draft Date: Thu, 01 May 1997 21:24:32 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, The following document formalizes a current policy of APNIC. I'd appreciate any comments you might have. Thanks, -drc -------- Introduction As the Internet is currently experiencing problems relating to the number of prefixes found in the routing system and these problems can have very significant impact on the operation of the Internet, APNIC has undertaken a policy to reduce the number of announced routing prefixes found within the blocks of addresses APNIC is responsible for. This document describes that policy. The "No Questions Asked" Return Policy While it should be stressed that for the Internet to scale, all organizations should obtain address space from their service provider, pragmatically speaking addresses which were allocated historically ("legacy prefixes") have advantages for those who make use of them. Specifically, because legacy prefixes are historically allocated, they are unlikely to be subject to prefix length filters, thereby providing long prefix provider independence. In many cases, an organization will have multiple legacy prefixes all of which require independent routing entries. In order to help reduce the strain resulting from the continued growth of the default free routing tables in routers on the Internet, APNIC will exchange existing provider independent prefixes for a single provider independent prefix of equal length or one bit shorter (to round up should the amount of space not work out to a CIDR boundary) given all of the following are true: - at least 3 prefixes are returned - the requestor can present documentation indicating they have been delegated the prefixes in question - all prefixes returned are provider independent All three of these requirements must be met for the exchange to take place. APNIC will ask no questions with respect to the usage of said address space -- more specifically, APNIC will waive the normal requirements for address space utilization for the new address space allocated in exchange for the discontiguous prefixes. The goal here is to trade off address conservation for routing table entry conservation given that the Internet operations community considers the latter to be a significantly scarcer resource. However, as always, it must be stressed that APNIC can make absolutely no guarantees that the newly allocated prefix will be routable on the Internet. Example Suppose ISP A has four discontiguous provider independent prefixes that are currently being routed, specifically 202.10.24.0/23, 202.12.113.0/24, 203.202.150.0/24, 203.224.18.0/24. If ISP A agrees to return those prefixes, APNIC will provide ISP A with a single /21 provider independent prefix rounding up to the next CIDR boundary. Conclusion The purpose of this policy is to attempt to help clean up the swamp. While it is true that the most appropriate course of action for an organization with multiple discontiguous prefixes would be for that organization to renumber into its service provider's address space, realistically speaking the likelihood of organizations renumbering into provider based space from routed provider independent space is assumed to be small. This proposal is consciously trading off address space for routing prefix space as the latter is considered more scarce than the former and is subject to revision should conditions within the Internet change. _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 2 10:15:56 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id KAA15458 for apnic-talk-outgoing; Fri, 2 May 1997 10:15:56 +0900 (JST) Received: from sable.nus.sg (sable.nus.edu.sg [137.132.1.21]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id KAA15453 for ; Fri, 2 May 1997 10:15:48 +0900 (JST) Received: from leonis.nus.sg (root@leonis.nus.sg [137.132.1.18]) by sable.nus.sg (8.8.4/8.6.9) with ESMTP id JAA22247 for ; Fri, 2 May 1997 09:18:11 +0800 (SST) Received: from yapcs-r2 (yapcs-r2.iscs.nus.sg [137.132.85.230]) by leonis.nus.sg (8.6.10/8.6.9/CNS-3.5) with SMTP id JAA00537 for ; Fri, 2 May 1997 09:18:10 +0800 Message-ID: <336940A0.6E6FCB31@iscs.nus.sg> Date: Fri, 02 May 1997 09:17:20 +0800 From: "Rahmat M. Samik-Ibrahim" Organization: Information Systems Research Center - DISCS - NUS X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.0 i586) MIME-Version: 1.0 To: apnic-talk@apnic.net Subject: Re: "No questions asked" policy draft References: <199705011224.VAA27748@palmtree.jp.apnic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apnic-talk@apnic.net Precedence: bulk > The "No Questions Asked" Return Policy Question #1: Does apply to APNIC member only ? Question #2: How about to add "Free prefix exchange" Eg. Ms. Someone "has" 202.1.0/24 ISP #1 "has" 202.1.1/24, 202.1.2/23, and 202.1.4/22 Ms. Someone can get a free replacement, and ISP#1 can get 202.1.0/21 tabe, -- Rahmat M. Samik-Ibrahim DISCS-NUS http://www.iscs.nus.sg/~samikibr ISO-9000:Write down what you do, do what you write down, verify it! _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 2 10:58:30 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id KAA15886 for apnic-talk-outgoing; Fri, 2 May 1997 10:58:30 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id KAA15880; Fri, 2 May 1997 10:58:28 +0900 (JST) Received: by apnic-ttc.apnic.net; id KAA05710; Fri, 2 May 1997 10:46:11 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma005706; Fri, 2 May 97 10:46:05 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id KAA28769; Fri, 2 May 1997 10:59:45 +0900 (JST) Message-Id: <199705020159.KAA28769@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: "Rahmat M. Samik-Ibrahim" cc: apnic-talk@apnic.net, davidc@apnic.net Subject: Re: "No questions asked" policy draft In-reply-to: Your message of "Fri, 02 May 1997 09:17:20 +0800." <336940A0.6E6FCB31@iscs.nus.sg> Date: Fri, 02 May 1997 10:59:45 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, >> The "No Questions Asked" Return Policy >Question #1: Does apply to APNIC member only ? No. Since it is no questions asked, the amount of processing it takes is minimal. As such, this is a service that can be provided to the Internet community at large... >Question #2: How about to add "Free prefix exchange" > > Eg. Ms. Someone "has" 202.1.0/24 > ISP #1 "has" 202.1.1/24, 202.1.2/23, and 202.1.4/22 > Ms. Someone can get a free replacement, and ISP#1 can get > 202.1.0/21 Sounds OK to me, what do other people think? Thanks, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Sun May 4 21:33:46 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id VAA02542 for apnic-talk-outgoing; Sun, 4 May 1997 21:33:46 +0900 (JST) Received: from pong3.pacific.net.sg (pong3.pacific.net.sg [203.120.90.69]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id VAA02536; Sun, 4 May 1997 21:33:40 +0900 (JST) From: hoou@pacific.net.sg Received: from lincoln (lincoln.pacific.net.sg [203.120.89.70]) by pong3.pacific.net.sg with SMTP id UAA29818; Sun, 4 May 1997 20:32:46 +0800 (SGT) Date: Sun, 4 May 1997 20:35:57 +0800 (SGT) X-Sender: hoou@lincoln To: "David R. Conrad" cc: "Rahmat M. Samik-Ibrahim" , apnic-talk@apnic.net Subject: Re: "No questions asked" policy draft In-Reply-To: <199705020159.KAA28769@palmtree.jp.apnic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apnic-talk@apnic.net Precedence: bulk On Fri, 2 May 1997, David R. Conrad wrote: > > >Question #2: How about to add "Free prefix exchange" > > > > Eg. Ms. Someone "has" 202.1.0/24 > > ISP #1 "has" 202.1.1/24, 202.1.2/23, and 202.1.4/22 > > Ms. Someone can get a free replacement, and ISP#1 can get > > 202.1.0/21 > > Sounds OK to me, what do other people think? Any problem in updating the whois database for such transfer? regards Hoou ;-) ################################################################# Wong Kok Hoou hoou@pacific.net.sg Network Operations Manager Main line: (65) 872-0322 Pacific Internet Pte Ltd Salesline: (65) 872-1455 89, Science Park Drive Help line: (65) 872-3330 #04-09/12 The Rutherford Fax line : (65) 773-6812 Singapore 118261 Web Site : www.pacific.net.sg _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Mon May 5 10:36:28 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id KAA06046 for apnic-talk-outgoing; Mon, 5 May 1997 10:36:28 +0900 (JST) Received: from nico.aarnet.edu.au (nico.telstra.net [139.130.204.16]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id KAA06037; Mon, 5 May 1997 10:36:23 +0900 (JST) Received: from sdup.telstra.net (geek.telstra.net [139.130.204.27]) by nico.aarnet.edu.au (8.6.10/8.6.10) with SMTP id LAA18983; Mon, 5 May 1997 11:38:36 +1000 Message-Id: <3.0.1.32.19970505112503.006c7bcc@nico.aarnet.edu.au> X-Sender: gih@nico.aarnet.edu.au X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 05 May 1997 11:25:03 +1000 To: "David R. Conrad" From: Geoff Huston Subject: Re: "No questions asked" policy draft Cc: apnic-talk@apnic.net In-Reply-To: <199705011224.VAA27748@palmtree.jp.apnic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-apnic-talk@apnic.net Precedence: bulk Two queries: 1 - does this (or is this intended to) apply to members and non-members of APNIC equally? 2 - Does this apply to any returned address prefix? regards, Geoff At 09:24 PM 1/5/97 +0900, David R. Conrad wrote: >Hi, > >The following document formalizes a current policy of APNIC. >I'd appreciate any comments you might have. > >Thanks, >-drc >-------- >Introduction > >As the Internet is currently experiencing problems relating to the >number of prefixes found in the routing system and these problems can >have very significant impact on the operation of the Internet, APNIC >has undertaken a policy to reduce the number of announced routing >prefixes found within the blocks of addresses APNIC is responsible >for. This document describes that policy. > >The "No Questions Asked" Return Policy > >While it should be stressed that for the Internet to scale, all >organizations should obtain address space from their service provider, >pragmatically speaking addresses which were allocated historically >("legacy prefixes") have advantages for those who make use of them. >Specifically, because legacy prefixes are historically allocated, they >are unlikely to be subject to prefix length filters, thereby providing >long prefix provider independence. > >In many cases, an organization will have multiple legacy prefixes all >of which require independent routing entries. In order to help reduce >the strain resulting from the continued growth of the default free >routing tables in routers on the Internet, APNIC will exchange >existing provider independent prefixes for a single provider >independent prefix of equal length or one bit shorter (to round up >should the amount of space not work out to a CIDR boundary) given all >of the following are true: > > - at least 3 prefixes are returned > > - the requestor can present documentation indicating they > have been delegated the prefixes in question > > - all prefixes returned are provider independent > >All three of these requirements must be met for the exchange to take >place. > >APNIC will ask no questions with respect to the usage of said address >space -- more specifically, APNIC will waive the normal requirements >for address space utilization for the new address space allocated in >exchange for the discontiguous prefixes. The goal here is to trade >off address conservation for routing table entry conservation given >that the Internet operations community considers the latter to be a >significantly scarcer resource. However, as always, it must be >stressed that APNIC can make absolutely no guarantees that the newly >allocated prefix will be routable on the Internet. > >Example > >Suppose ISP A has four discontiguous provider independent prefixes >that are currently being routed, specifically 202.10.24.0/23, >202.12.113.0/24, 203.202.150.0/24, 203.224.18.0/24. If ISP A agrees >to return those prefixes, APNIC will provide ISP A with a single /21 >provider independent prefix rounding up to the next CIDR boundary. > >Conclusion > >The purpose of this policy is to attempt to help clean up the swamp. >While it is true that the most appropriate course of action for an >organization with multiple discontiguous prefixes would be for that >organization to renumber into its service provider's address space, >realistically speaking the likelihood of organizations renumbering >into provider based space from routed provider independent space is >assumed to be small. This proposal is consciously trading off address >space for routing prefix space as the latter is considered more scarce >than the former and is subject to revision should conditions within >the Internet change. >_________________________________________________________________________ >| To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | >+-----------------------------------------------------------------------+ > > > _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Tue May 6 00:39:36 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id AAA09523 for apnic-talk-outgoing; Tue, 6 May 1997 00:39:36 +0900 (JST) Received: from owlsnest.com (owl@ns.owlsnest.com [206.112.60.212]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id AAA09518 for ; Tue, 6 May 1997 00:39:30 +0900 (JST) From: owl@owlsnest.com Received: (from owl@localhost) by owlsnest.com (8.7.4/8.7.3) id HAA19775; Mon, 5 May 1997 07:29:36 -0400 (EDT) Date: Mon, 5 May 1997 07:29:36 -0400 (EDT) Message-Id: <199705051129.HAA19775@owlsnest.com> To: local-ir@apnic.net Reply-To: owl@owlsnest.com Subject: Is Your Web Site A Secret? Sender: owner-apnic-talk@apnic.net Precedence: bulk Is your web site the best kept secret on the Internet? We'll promote it to 50 search engines and indexes for $85 and complete the job in 2 business days. Satisfaction is guaranteed! If you have a great product, but are not getting many inquiries from your Web site, you may not be adequately listed on the Web's search engines and indexes. Millions of viewers daily use these facilities to find the products and services they are looking for. But if your site is not listed, no one will see it. Listings on most of these services are free. However, locating and filling out the forms required to get a listing can take several days, and most people just don't have the time to do it. That is why we offer a web site promotion service. WHAT'S THE DEAL? We will submit your site to 50 indexes and search engines for $85. We will accept the return of this E-mail, with the form below filled out, as an order. We will bill you upon completion of the promotion. Our terms are net 15 days from date of invoice. Satisfaction guaranteed! HOW LONG WILL IT TAKE? Generally, we complete the submissions within 48 hours of receiving your order. It can take any individual search engine or index up to three weeks to process your submission, although most are much faster. WHAT SEARCH ENGINES AND INDEXES ARE INCLUDED IN THE PROMOTION? The list changes from time to time. This is our current list: Abaweb!, Alta Vista, Been There, BizWeb, Central Source Yellow Pages, Enterpreneurs on the Web, Excite, Four11, Galaxy, I-Network I-Systems Spiral Business Directory, I-World Web Pointer, Infoseek, Inktomi, Innovator's Network Yellow Pages, Internet Mall, Jayde Online Directory, Jumpcity, Jumper Hot Links, Linkmaster, Lycos, Magellan, Mega Mall, Net-Happenings, Net Navigator, Net Mall, NTG's List, NYNEX Big Yellow, One World Plaza, OnLine's WWWeb Index, Rex, Starting Point, Truenorth, URL Tree, Virtual Lynx, Web Point, WebCentral, Web Venture Hotlist, Webcrawler, Websurf, Win Mag/NetGuide Hotspots, WhatUSeek, Worldwide Announce Archive, WWW Business Yellow Pages, World Wide Yellow Pages, WWW Worm, YelloWWWeb. HOW WILL I KNOW THAT YOU HAVE PROMOTED MY SITE? When we have completed the promotion, we will send you an HTML file as an attachment to your E-mail bill. Save this file to your disk, and view it through your Web browser. It provides links to the search engine we submitted your site to, plus any comments we received from them when we did it. ARE THERE ANY GUARANTEES? We do not require prepayment. Your satisfaction is guaranteed or you don't pay the bill. WHO IS OWL'S EYE PRODUCTIONS? We are a web site promotion company located at: Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Phone: (914) 278-4933 Fax: (914) 278-4507 Email: owl@owlsnest.com HOW DO I ORDER? The easiest way to order is by e-mail. Just hit the REPLY button on your e-mail program and fill out the following information. (This information will be posted to the search engines/indexes): Your name: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: URL: http:// Site Title: Description (about 25 words): Key words (maximum of 25, in descending order of importance): Proofs (Where shall we e-mail proofs): If billing a different address, please complete the following: Addressee: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: We will bill via Email. (7504) Terms: By returning this document via Email, you agree as follows: You have the authority to purchase this service on behalf of your company. Terms are net 15 days. Accounts sent to collections will be liable for collection costs. You agree to protect and indemnify Owl's Eye Productions, Inc. in any claim for libel, copyright violations, plagiarism, or privacy and other suits or claims based on the content or subject matter of your site. WHAT HAPPENS NEXT? When we receive your order, we will input the information into our system, and send you a proof. After we process any corrections, we will run your promotion, capturing any comments from search engines as we go. We will incorporate these into an HTML-formatted report to you, which we will attach to your bill. ===Web Promotions=====Press Releases=====Link Exchanges========= Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Ph: 914-278-4933 Fx: 914-278-4507 E-mail: owlseye@owlsnest.com _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Tue May 6 14:22:21 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id OAA17400 for apnic-talk-outgoing; Tue, 6 May 1997 14:22:21 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id OAA17395 for ; Tue, 6 May 1997 14:22:09 +0900 (JST) Received: by apnic-ttc.apnic.net; id OAA20820; Tue, 6 May 1997 14:09:43 +0900 Received: from unknown(10.0.10.4) by apnic-ttc.apnic.net via smap (g3.0.3) id xma020811; Tue, 6 May 97 14:09:37 +0900 Received: from apnic.net (davidc@localhost) by moonsky.jp.apnic.net (8.8.5/8.7.1) with ESMTP id OAA02294; Tue, 6 May 1997 14:23:55 +0900 (JST) Message-Id: <199705060523.OAA02294@moonsky.jp.apnic.net> X-Authentication-Warning: moonsky.jp.apnic.net: davidc owned process doing -bs To: mark@aone.com.au, phong@inet.co.th, anto@inet.co.th, howdy@inet.co.th, danorton@chsw.com, root@craycom.co.nz, chris@connect.com.au cc: apnic-talk@apnic.net Subject: Whois database problems... Date: Tue, 06 May 1997 14:23:54 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, Due to an unexpected full disk situation (a mirror ran amok) during the APNIC database cleaning process Sunday night (Monday was a holiday here in JP), the APNIC database got truncated. We'll be restoring a backup made on Friday and going through the logs to apply whatever missing updates there might be. We apologies for any inconvenience. Regards, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Wed May 7 14:19:39 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id OAA24740 for apnic-talk-outgoing; Wed, 7 May 1997 14:19:39 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id OAA24724; Wed, 7 May 1997 14:16:42 +0900 (JST) Received: by apnic-ttc.apnic.net; id OAA25017; Wed, 7 May 1997 14:04:14 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma025014; Wed, 7 May 97 14:03:57 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id OAA03509; Wed, 7 May 1997 14:17:58 +0900 (JST) Message-Id: <199705070517.OAA03509@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: apnic-announce@apnic.net cc: apnic-talk@apnic.net Subject: Database back on line Date: Wed, 07 May 1997 14:17:58 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, Due to an over-active mirror script causing a disk full condition while the APNIC database was being indexed sometime around May 3, the APNIC whois database was truncated. I have restored the database from May 2 and have submitted all updates sent to APNIC from May 2 to today in the order they arrived. However, due to the fact that the log may have also been truncated (silently), it is possible an update you sent was not applied, even though you have received notification of a sucessful update. To be sure, please check the records in the APNIC database you have recently updated. If the information is not correct, please submit APNIC-044 updates as appropriate. Apologies for the inconvenience. Regards, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Wed May 7 16:49:26 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id QAA25744 for apnic-talk-outgoing; Wed, 7 May 1997 16:49:26 +0900 (JST) Received: from mucc.mahidol.ac.th (ccpsm@mucc.mahidol.ac.th [202.28.162.1]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id QAA25737 for ; Wed, 7 May 1997 16:49:17 +0900 (JST) Received: from localhost (ccpsm@localhost) by mucc.mahidol.ac.th (8.8.5/8.8.2) with SMTP id OAA06588; Wed, 7 May 1997 14:51:59 +0700 (GMT+0700) Date: Wed, 7 May 1997 14:51:58 +0700 (GMT+0700) From: Prem Sumetpong To: apnic-talk@apnic.net cc: apnic-talk@apnic.net Subject: unsubscribe In-Reply-To: <199705070517.OAA03509@palmtree.jp.apnic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apnic-talk@apnic.net Precedence: bulk _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Tue May 13 09:49:00 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id JAA07505 for apnic-talk-outgoing; Tue, 13 May 1997 09:49:00 +0900 (JST) Received: from marcie.socs.uts.EDU.AU (marcie.socs.uts.EDU.AU [138.25.9.4]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id JAA07500 for ; Tue, 13 May 1997 09:48:56 +0900 (JST) Received: from charlie.socs.uts.EDU.AU (lkhyi@charlie [138.25.9.2]) by marcie.socs.uts.EDU.AU (8.8.5/8.8.0) with ESMTP id KAA12122 for ; Tue, 13 May 1997 10:51:19 +1000 (EST) Received: from localhost (lkhyi@localhost) by charlie.socs.uts.EDU.AU (8.8.5/8.7.3) with SMTP id KAA26182 for ; Tue, 13 May 1997 10:51:18 +1000 (EST) X-Authentication-Warning: charlie.socs.uts.EDU.AU: lkhyi owned process doing -bs Date: Tue, 13 May 1997 10:51:18 +1000 (EST) From: Lawrence Kang Hie Yi X-Sender: lkhyi@charlie To: apnic-talk@apnic.net Subject: unsubscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-apnic-talk@apnic.net Precedence: bulk unsubscribe _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Tue May 13 12:19:14 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id MAA08618 for apnic-talk-outgoing; Tue, 13 May 1997 12:19:14 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id MAA08609 for ; Tue, 13 May 1997 12:19:12 +0900 (JST) Received: by apnic-ttc.apnic.net; id MAA17955; Tue, 13 May 1997 12:06:18 +0900 Received: from unknown(10.0.10.4) by apnic-ttc.apnic.net via smap (g3.0.3) id xma017952; Tue, 13 May 97 12:06:08 +0900 Received: from apnic.net (davidc@localhost) by moonsky.jp.apnic.net (8.8.5/8.7.1) with ESMTP id MAA05310 for ; Tue, 13 May 1997 12:20:53 +0900 (JST) Message-Id: <199705130320.MAA05310@moonsky.jp.apnic.net> X-Authentication-Warning: moonsky.jp.apnic.net: davidc owned process doing -bs To: apnic-talk@apnic.net Subject: APNIC Meeting Agenda Items Date: Tue, 13 May 1997 12:20:53 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, The next APNIC meeting is scheduled for June 22 from 10:30 AM to 5:30 PM at the Pan Pacific Hotel in Kuala Lumpur (continental breakfast and lunch will be provided, a US $50 attendance fee will be charged for non-APNIC members). THe following items are already on the agenda: - FY '96 Financial Summary - a summary of APNIC's FY '96 finances after the closing of our books. - Location of APNIC Cost Analysis -- discussion of the costs associated with operating APNIC in various locations as presented to the APNIC Executive Council. - FY '97 Revised Budget Discussions and Voting -- modifications to the projected budget with subsequent voting for approval. - Electronic Voting Proposals This note is to request additional topics for discussion. Please note that any topic that - By-Law Modification Proposals -- + requiring 4/5 majority instead of simple majority for approval of proposals + greater use of electronic voting to approve proposals + revision of election nomination mechanisms - APNIC Assignment Window Tutorial -- a short tutorial on the assignment window address allocation technique now in use by APNIC. Please provide any additional agenda items as soon as possible. Thanks, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Wed May 14 01:02:21 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id BAA14343 for apnic-talk-outgoing; Wed, 14 May 1997 01:02:21 +0900 (JST) Received: from mallow.singnet.com.sg (mallow.singnet.com.sg [165.21.1.11]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id AAA14306; Wed, 14 May 1997 00:59:59 +0900 (JST) From: laina@singnet.com.sg Received: from laina.singnet.com.sg (ts900-6109.singnet.com.sg [165.21.162.125]) by mallow.singnet.com.sg (8.8.5/8.8.5) with SMTP id XAA07242; Tue, 13 May 1997 23:54:11 +0800 (SST) Date: Tue, 13 May 97 23:27:49 Subject: Telecom Development Symposium To: apple@apnic.net X-PRIORITY: 3 (Normal) X-Mailer: Chameleon 5.0, TCP/IP for Windows, NetManage Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-apnic-talk@apnic.net Precedence: bulk TELECOM DEVELOPMENT SYMPOSIUM , organized by the International Telecommunications Union, during ASIA TELECOM’97 12-14th June, World Trade Center, Singapore For the first time during ASIA TELECOM, the International Telecommunications Union will be organizing in addition to their TELECOM Exhibition and Forum event, a Telecommunications Development Symposium, for a fee of CHF400. For no extra cost, you will also be entitled to attend the remaining Forum sessions and visit the Exhibition from the 12th-14th June. This Development Symposium stems from the success of the newly introduced Development Workshops that were organized by the ITU, first during TELECOM’95 and at then at AMERICAS TELECOM’96. The first Workshop was on "Human Resources and Technology", while the second was on "Rural Telecommunications Development." These Workshops were only open to invited participants from developing countries and was of great value to the participants. Given their success and the interest it has generated, the ITU has decided to promote these Workshops into a Symposium status. This first Development Symposium, with the theme of Interconnectivity will now be held during ASIA TELECOM’97, from the 12-14th June 1997, at the World Trade Center and will be open to the public. In addition, there will still be separate Interactive Group and Working Group sessions open only to invited national representatives, experts and sponsors to cater to more focussed development needs and issues. For more information about this Symposium, please check ITU's web page at http://www.itu.int under ASIA TELECOM. You could also contact GETIT Pte Ltd at Tel: 65-738 6929 or Fax: 65-738 7839 and we will fax you a detailed program. ------------------------------------- Please note that GETIT has recently been incorporated into GETIT Pte Ltd and has moved into new premises. Its new contact address is: 7th Storey, RELC Building 30, Orange Grove Road Singapore 258352 Name: Laina Raveendran Greene Managing Director, GETIT Pte Ltd E-mail: laina@getit.org http://www.getit.org Date: 5/13/97 Time: 11:27:49 PM This message was sent by Chameleon ------------------------------------- _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Thu May 22 02:56:18 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id CAA05705 for apnic-talk-outgoing; Thu, 22 May 1997 02:56:18 +0900 (JST) Received: from ispam.net (root@ispam.net [205.199.212.34]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id CAA05696 for ; Thu, 22 May 1997 02:56:10 +0900 (JST) From: exposure@savetrees.com Received: from --- CLOAKED! --- X-1: This email was sent by "Cyber-Bomber" ... Details at http://www.cyberpromo.com X-2: This server only relays mail from other sources. X-3: To report abuse, please send email to abuse@cyberpromo.com. X-4: Coming soon --> Master remove list implementation by I.E.M.M.C. Message-Id: <199705211658.MAA05737@ispam.net> To: exposure@savetrees.com Date: Wed, 21 May 97 10:45:15 EST Subject: Ukiah Software Reply-To: exposure@savetrees.com Sender: owner-apnic-talk@apnic.net Precedence: bulk \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Your email address was acquired from a targetted search of the WWW. If you've received this in error, please accept our apologies. This is a one- time mailing, and your address will not be given to anyone else. //////////////////////////////////////////////////////////////////////// Ukiah Software - http://www.ukiahsoft.com - is a developer of highly manageable, application level firewall for mixed IP and IPX networks. Our flagship product, NetRoad FireWALL is NCSA Certified , incorporates an IP firewall with Network Address Translation (NAT), plus an IPX/IP gateway. This is the only firewall in the market that is integrated with Novell's LDAP compliant Novell Directory Services (NDS), and is the only NCSA Certified Firewall for NetWare operating system. NetRoad FireWALL is also available for Windows NT. Key Features of NetRoad FireWALL · This product is two products in one: an IP firewall and an IPX/IP gateway. So it allows you to provide secure Internet or intranet access to both IP and IPX networks (or any combination of the two). Some key features: · Full application level security for all the key IP protocols: HTTP, Telnet, FTP, SMTP and more! No one's going to be hacking into your Web server with NetRoad FireWALL standing guard! · Full bi-directional control over network traffic, both inbound and outbound: not only can you keep hackers out, you can also keep your users from checking out some of those information "resources" out on the network you'd rather they stayed away from! · Full support for IP clients: whatever your client operating system, we'll provide firewall support for any IP client and the applications running on it. With our integrated support for NAT (network address translation), NO network address changes are required! · Full support for IPX clients: using the IPX/IP gateway component of our product, you can run any TCP or UDP application on IPX clients. No need to install an IP stack! Web browsers? No problem. News readers? Piece of cake. FTP client? Yup. Real Audio? A delight for the ears. In short, IPX clients need no longer be second class citizens when it comes to Internet or intranet access. And, it's very secure. · Integrated with NDS: NetRoad FireWALL appears as just another object in your NDS tree, and is configured and managed through an NWADMIN snap-in. You can take full advantage of your NDS database of users and groups, without having to re-enter all this information. Security events are logged with NDS. User authentication is handled through NDS (and you can also use other forms of authentication, such as One Time Passwords). You'll be managing your firewalls and your security policies through a management platform you already know and love -- without having to introduce yet another management system. · Server platform: Runs on NetWare 4.1 and later. Also runs on Windows NT 4.0. The two versions offer common functionality, and can even be managed through the same NDS console. Plus, if you purchase one of our Software Maintenance Contracts, you can even migrate from one platform to the other at no additional cost. · Your NetWare server is 3.x? Don't despair, we do have still another product called NetRoad FireWARE, which provides an IPX/IP gateway (not an IP-IP firewall) and runs as an NLM on 3.x. Supports both TCP and UDP applications. And it's very affordable. NetRoad NewsServer: This product allows you to provide full NNTP-compliant news service to your users -- fast! And on NetWare! So, instead of having to go out to the Internet to (sloooowly) access newsgroup messages, the network administrator configures your own private NetWare-based NewsServer to download the newsgroups that your organization's users are interested in. Since these newsgroups are then stored locally on your LAN, access to this information is much faster than over slow WAN links. Plus, you can maintain purely private newsgroups --in effect, your organization's private bulletin boards -- right on your own local NetWare server. So it's not only fast, it's also a very secure way to disseminate information. Some key features: · NNTP compliant, so it works with any standard newsreader, such as Netscape Navigator or Internet Explorer · Runs on NetWare 3.x and 4.x. · Enables both selective newsfeeds and comprehensive newsfeeds, so that you only get the newsgroups that your organization needs. · Configurable aging of messages, to ensure that the disk space requirement stays under control · High performance implementation makes it the fastest news server on the market! · Provides support for both IP and IPX newsreader clients, when used in conjunction with NetRoad FireWALL. For more information, please visit our Web site: http://www.ukiahsoft.com Thank you for your time! _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Thu May 29 22:36:11 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id WAA26265 for apnic-talk-outgoing; Thu, 29 May 1997 22:36:11 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id WAA26258 for ; Thu, 29 May 1997 22:35:57 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.8.5/8.8.5) id VAA08448 for apnic-talk@apnic.net; Thu, 29 May 1997 21:38:14 +0800 From: "Miguel A.L. Paraz" Message-Id: <199705291338.VAA08448@marikit.iphil.net> Subject: When the request gets big To: apnic-talk@apnic.net Date: Thu, 29 May 1997 21:38:14 +0800 (HKT) Content-Type: text Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, We have a customer who is currently using a /22, plus some other smaller networks, of our /19. They are now launching a wireless network that initially would fit within another /22. We don't have a contiguous /22 available, and it looks like this customer will grow even more. What are the pros and cons of them seeking their own APNIC membership? Is the fact that their upstream provider (us) is currently unable to fulfill their IP request a valid reason for getting their own provider- independent space? To keep our routing simple I would like them aggregated as a single network, and, it seems that renumbering these equipment which are located in remote sites will be hard. Thus we would like to start out with the proper IP networks. Any comments? Thanks, -- miguel a.l. paraz +63-2-893-0850 iphil communications, makati city, philippines _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 13:22:20 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id NAA02436 for apnic-talk-outgoing; Fri, 30 May 1997 13:22:20 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id NAA02430; Fri, 30 May 1997 13:22:17 +0900 (JST) Received: by apnic-ttc.apnic.net; id NAA04067; Fri, 30 May 1997 13:07:14 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma004065; Fri, 30 May 97 13:07:06 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id NAA13810; Fri, 30 May 1997 13:22:40 +0900 (JST) Message-Id: <199705300422.NAA13810@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: "Miguel A.L. Paraz" cc: apnic-talk@apnic.net, davidc@apnic.net Subject: Re: When the request gets big In-reply-to: Your message of "Thu, 29 May 1997 21:38:14 +0800." <199705291338.VAA08448@marikit.iphil.net> Date: Fri, 30 May 1997 13:22:40 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, >We don't have a contiguous >/22 available, and it looks like this customer will grow even more. If an ISP doesn't have sufficient address space to satisfy a particular customer request, the ISP can request additional space specifically for that customer. Assuming the request is justified, APNIC will allocate to the ISP for sub-allocation to the customer. >What are the pros and cons of them seeking their own APNIC membership? Pros: - provider independence - better aggregation Cons: - costs money - another global routing table entry >Is the fact that their upstream provider (us) is currently unable to >fulfill their IP request a valid reason for getting their own provider- >independent space? Nope -- the upstream can always get more space. Regards, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 16:19:59 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id QAA03320 for apnic-talk-outgoing; Fri, 30 May 1997 16:19:59 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id QAA03315 for ; Fri, 30 May 1997 16:19:57 +0900 (JST) Received: by apnic-ttc.apnic.net; id QAA04723; Fri, 30 May 1997 16:05:44 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma004720; Fri, 30 May 97 16:05:39 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id QAA14551 for ; Fri, 30 May 1997 16:21:14 +0900 (JST) Message-Id: <199705300721.QAA14551@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: apnic-talk@apnic.net Subject: APNIC June 22 Meeting: updated agenda Date: Fri, 30 May 1997 16:21:14 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, The next APNIC meeting is scheduled for June 22 from 9:30 AM to 5:00 PM at the Pan Pacific Hotel in Kuala Lumpur, continental breakfast and lunch will be provided. In order to defay costs, a US $50 attendance fee will be charged to non-members. 9:30 - 10:30 Registration and Continental Breakfast 10:30 - 10:45 FY '96 Financial Summary - a summary of APNIC's FY '96 finances after the closing of our books. 10:45 - 11:15 Confederation Proposals and Voting - Geoff Huston's flat rate proposal - David Conrad's usage based proposal with JPNIC modifications 11:15 - 11:30 Location of APNIC Cost Analysis -- discussion of the costs associated with operating APNIC in various locations as presented to the APNIC Executive Council. 11:30 - 12:00 FY '97 Revised Budget Discussions and Voting -- modifications to the projected budget with subsequent voting for approval. 12:00 - 1:30 Lunch (provided) 1:30 - 2:00 Electronic Voting Discussion - mechanisms to facilitate electronic voting - techniques to implement voting 2:00 - 2:30 By-Law Modifications Discussion - requiring 3/4 majority instead of simple majority for approval of proposals - greater use of electronic voting to approve proposals - revision of election nomination mechanisms 2:30 - 3:00 APNIC Assignment Window Mini-Tutorial 3:00 - 3:30 Break (refreshments provided) 3:30 - 5:00 Country Reports - all organizations wishing to provide a country report please notify me In addition, it has been suggested that APNIC host a meeting of TLD administrators in the Asia/Pacific Rim region to discuss TLD developments. We are willing to do this should there be interest. If you would like to attend such a meeting, say from 7:00 to 9:00 PM after the APNIC meeting, please let me know. Thanks, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 17:47:20 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id RAA04386 for apnic-talk-outgoing; Fri, 30 May 1997 17:47:20 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id RAA04380; Fri, 30 May 1997 17:47:10 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.8.5/8.8.5) id QAA32364; Fri, 30 May 1997 16:49:30 +0800 From: "Miguel A.L. Paraz" Message-Id: <199705300849.QAA32364@marikit.iphil.net> Subject: Re: APNIC June 22 Meeting: updated agenda To: davidc@apnic.net (David R. Conrad) Date: Fri, 30 May 1997 16:49:30 +0800 (HKT) Cc: apnic-talk@apnic.net In-Reply-To: <199705300721.QAA14551@palmtree.jp.apnic.net> from "David R. Conrad" at May 30, 97 04:21:14 pm Content-Type: text Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, David R. Conrad wrote: > The next APNIC meeting is scheduled for June 22 from 9:30 AM to 5:00 > PM at the Pan Pacific Hotel in Kuala Lumpur, continental breakfast and > lunch will be provided. In order to defay costs, a US $50 attendance > fee will be charged to non-members. How many member attendees come in for free: 1, 2, or 4 for small, medium and large members? Cheers, -- miguel a.l. paraz +63-2-893-0850 iphil communications, makati city, philippines _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 17:54:29 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id RAA04449 for apnic-talk-outgoing; Fri, 30 May 1997 17:54:29 +0900 (JST) Received: from marikit.iphil.net (map@marikit.iphil.net [203.176.0.4]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id RAA04441; Fri, 30 May 1997 17:54:05 +0900 (JST) Received: (from map@localhost) by marikit.iphil.net (8.8.5/8.8.5) id QAA32555; Fri, 30 May 1997 16:56:24 +0800 From: "Miguel A.L. Paraz" Message-Id: <199705300856.QAA32555@marikit.iphil.net> Subject: Re: When the request gets big To: davidc@apnic.net (David R. Conrad) Date: Fri, 30 May 1997 16:56:24 +0800 (HKT) Cc: apnic-talk@apnic.net In-Reply-To: <199705300422.NAA13810@palmtree.jp.apnic.net> from "David R. Conrad" at May 30, 97 01:22:40 pm Content-Type: text Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, David R. Conrad wrote: > If an ISP doesn't have sufficient address space to satisfy a > particular customer request, the ISP can request additional space > specifically for that customer. Assuming the request is justified, > APNIC will allocate to the ISP for sub-allocation to the customer. Assume our customer has the need for 1024 additional addresses. To simplify routing I would like to give them a /22, but I do not have any single /22 free. Can I request for more space on this grounds, or should I consume the 1024 addresses in 4 /24 chunks? With regards to routing table entries, we currently have a /19. If I'm not mistaken any additional allocation will be a totally different block and we won't be able to stretch our net to a /18? If that is the case then regardless of whether our customer gets their own APNIC membership or not, we inject another route into the default-free routers. BTW, what software do you use for keeping the registry running? I tried the APNIC FTP site and the RIPE web site but found nothing. I'm interested in running my own registry which customers can use, and can also create automatic updates for the APNIC database. I'm having a tough time with allocation history, and especially, projecting future growth. The best customers are those who don't know what IP space is... just give them a /30 :) Cheers, -- miguel a.l. paraz +63-2-893-0850 iphil communications, makati city, philippines _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 17:55:05 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id RAA04467 for apnic-talk-outgoing; Fri, 30 May 1997 17:55:05 +0900 (JST) Received: from mail.tm.net.my (janeway.tm.net.my [202.188.0.155]) by teckla.apnic.net (8.8.5/8.7.1) with ESMTP id RAA04461; Fri, 30 May 1997 17:55:02 +0900 (JST) From: tommi@mail.tm.net.my Received: from tommichen.asiapac.net ([202.188.0.91]) by mail.tm.net.my (8.8.5/8.8.4) with SMTP id QAA02670; Fri, 30 May 1997 16:55:14 +0800 (SGT) Date: Fri, 30 May 1997 16:55:14 +0800 (SGT) Message-Id: <1.5.4.16.19970530165058.50477722@mail.tm.net.my> X-Sender: tommi@mail.tm.net.my X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "David R. Conrad" , apnic-talk@apnic.net Subject: Re: APNIC June 22 Meeting: updated agenda Sender: owner-apnic-talk@apnic.net Precedence: bulk >In addition, it has been suggested that APNIC host a meeting of TLD >administrators in the Asia/Pacific Rim region to discuss TLD >developments. We are willing to do this should there be interest. >If you would like to attend such a meeting, say from 7:00 to 9:00 PM >after the APNIC meeting, please let me know. i'll attend tommi _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 18:07:28 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id SAA04624 for apnic-talk-outgoing; Fri, 30 May 1997 18:07:28 +0900 (JST) Received: from cs4.cs.ait.ac.th (root@cs4.cs.ait.ac.th [192.41.170.15]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id SAA04616; Fri, 30 May 1997 18:07:23 +0900 (JST) Received: from bazooka.cs.ait.ac.th (kk@bazooka.cs.ait.ac.th [192.41.170.2]) by cs4.cs.ait.ac.th (8.6.12/) with ESMTP id QAA23933; Fri, 30 May 1997 16:04:59 +0700 Received: (from kk@localhost) by bazooka.cs.ait.ac.th (8.6.12/8.6.12) id QAA08479; Fri, 30 May 1997 16:04:55 +0700 Date: Fri, 30 May 1997 16:04:55 +0700 From: Kanchana Kanchanasut Message-Id: <199705300904.QAA08479@bazooka.cs.ait.ac.th> To: davidc@apnic.net CC: apnic-talk@apnic.net In-reply-to: <199705300721.QAA14551@palmtree.jp.apnic.net> (davidc@apnic.net) Subject: Re: APNIC June 22 Meeting: updated agenda Sender: owner-apnic-talk@apnic.net Precedence: bulk In addition, it has been suggested that APNIC host a meeting of TLD administrators in the Asia/Pacific Rim region to discuss TLD developments. We are willing to do this should there be interest. If you would like to attend such a meeting, say from 7:00 to 9:00 PM after the APNIC meeting, please let me know. I will send someone to attend. Kanchana _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 18:32:03 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id SAA04994 for apnic-talk-outgoing; Fri, 30 May 1997 18:32:03 +0900 (JST) Received: from apnic-ttc.apnic.net (firewall-user@apnic-ttc.apnic.net [203.178.142.242]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id SAA04988; Fri, 30 May 1997 18:32:01 +0900 (JST) Received: by apnic-ttc.apnic.net; id SAA05226; Fri, 30 May 1997 18:16:44 +0900 Received: from unknown(10.0.10.5) by apnic-ttc.apnic.net via smap (g3.0.3) id xma005224; Fri, 30 May 97 18:16:30 +0900 Received: from apnic.net (davidc@localhost) by palmtree.jp.apnic.net (8.8.2/8.8.2) with ESMTP id SAA14795; Fri, 30 May 1997 18:32:06 +0900 (JST) Message-Id: <199705300932.SAA14795@palmtree.jp.apnic.net> X-Authentication-Warning: palmtree.jp.apnic.net: davidc owned process doing -bs To: "Miguel A.L. Paraz" cc: davidc@apnic.net (David R. Conrad), apnic-talk@apnic.net Subject: Re: When the request gets big In-reply-to: Your message of "Fri, 30 May 1997 16:56:24 +0800." <199705300856.QAA32555@marikit.iphil.net> Date: Fri, 30 May 1997 18:32:06 +0900 From: "David R. Conrad" Sender: owner-apnic-talk@apnic.net Precedence: bulk Hi, >Assume our customer has the need for 1024 additional addresses. To simplify >routing I would like to give them a /22, but I do not have any single /22 >free. Can I request for more space on this grounds, or should I consume >the 1024 addresses in 4 /24 chunks? Likely the latter -- if you have sufficient space but the space is discontiguous, it will probably be harder to justify the special allocation simply because it would make your routing easier... >If I'm not mistaken any additional allocation will be a totally different >block and we won't be able to stretch our net to a /18? All we guarantee is a /19, however we try to allow for larger blocks. >BTW, what software do you use for keeping the registry running? ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.0.4.tar.gz Regards, -drc _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+ From owner-apnic-talk Fri May 30 20:19:14 1997 Received: (from daemon@localhost) by teckla.apnic.net (8.8.5/8.7.1) id UAA06347 for apnic-talk-outgoing; Fri, 30 May 1997 20:19:14 +0900 (JST) Received: from hen.nca.or.kr (hen.nca.or.kr [202.30.65.7]) by teckla.apnic.net (8.8.5/8.7.1) with SMTP id UAA06341; Fri, 30 May 1997 20:19:00 +0900 (JST) Received: from ckp.nca.or.kr ([202.30.66.52]) by hen.nca.or.kr (8.6.12h2/8.6.9) with SMTP id UAA22459; Fri, 30 May 1997 20:20:38 +0900 Message-ID: <338EB8D4.637@nca.or.kr> Date: Fri, 30 May 1997 20:24:04 +0900 From: Chanki Park Reply-To: ckp@nca.or.kr Organization: NCA X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: "David R. Conrad" CC: apnic-talk@apnic.net Subject: Re: APNIC June 22 Meeting: updated agenda References: <199705300721.QAA14551@palmtree.jp.apnic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-apnic-talk@apnic.net Precedence: bulk David R. Conrad wrote: > In addition, it has been suggested that APNIC host a meeting of TLD > administrators in the Asia/Pacific Rim region to discuss TLD > developments. We are willing to do this should there be interest. > If you would like to attend such a meeting, say from 7:00 to 9:00 PM > after the APNIC meeting, please let me know. >From KRNIC, Chanki Park and Myongsub Oh will attend. _________________________________________________________________________ | To unsubscribe: send "unsubscribe" to apnic-talk-request@apnic.net | +-----------------------------------------------------------------------+