- Test - lists.nanog.org

attendee list from Oct 4-5 meeting
by mak 06 Oct '93

06 Oct '93

Hi. Here is the list of people who signed in at the meeting this week. I will attempt to produce a summary of the meeting, and also ask the presenters to provide electronic copies of their materials. Mark Adams, Andy Merit ala(a)merit.edu Aggarwal, Vikas GES aggarwal(a)nisc.jvnc.net Ali, Nisar ANS nia(a)noc.ans.net Almes, Guy ANS almes(a)ans.net Bayraktar, Serpil ANS sbb(a)noc.ans.net Becker, Jordan ANS becker(a)ans.net Belenky, David Merit belenky(a)merit.edu Bennett, Eric ANS reb(a)noc.ans.net Blair, Sue ANS bsb(a)noc.ans.net Blake-Hedges, Jennifer SURAnet jbh(a)sura.net Bostwick, Rebeca ESnet bostwick(a)es.net Boyer, Deb ANS djb(a)noc.ans.net Burgan, Jeff NASA jeff(a)nsipo.nasa.gov Calderon, Robert ANS calderon(a)pager.aa.ans.net Carroll, Eric CA*NET eric(a)enfm.utcc.utoronto.ca Chen, Enke Merit enke(a)merit.edu Christie, Tom ANS tfc(a)noc.ans.net Collet, Robert Sprint rcollet(a)icm1.icp.net Conto, Richard Merit rsc(a)merit.edu Cunningham, Steve PSC CUNNINGHAM(a)B.PSC.EDU Driscoll, Mark Merit jmd(a)merit.edu Easterday, Tom CICnet tom(a)cic.net El-Aawar, Nasser ANS nna(a)noc.ans.net Ferguson, Dennis ANS dennis(a)ans.net Ford, Peter Los Alamos peter(a)goshawk.lanl.gov Fredenburg, Chris DISA cfredenburg(a)dsac.dla.mil Fuller, Vince BARRnet vaf(a)Valinor.Stanford.EDU Garner, Chris WestNET cgarner(a)dozer.Colorado.EDU Gerich, Elise Merit epg(a)merit.edu Glinka, Sarah ANS glinka(a)ans.net Hares, Sue Merit skh(a)merit.edu Horvath, Susan Merit shorvath(a)merit.edu Jarrar, Saib MCI 0005684227(a)mcimail.com Johnson, Dale Merit dsj(a)merit.edu Joncheray, Laurent Merit lpj(a)merit.edu Kennedy, Sean NEARnet liam(a)nic.near.net Kives, Steve ANS sak(a)noc.ans.net Knopper, Mark Merit mak(a)merit.edu Kosters, Mark InterNIC markk(a)internic.net Labbe, John ANS jlabbe(a)noc.ans.net Labovitz, Craig Merit labovit(a)merit.edu Langford, David ANS djl(a)noc.ans.net Latta, Ken Merit klatta(a)merit.edu Lothbberg, Peter Sprint roll(a)bsd.stupi.se Manning, Bill Sesquinet bmanning(a)is.rice.edu Martin, Dave Merit David.C.Martin(a)um.cc.umich.edu McRobb, Daniel ANS dwm(a)noc.ans.net Metcalf, Stan ANS metcalf(a)ans.net Norton, Bill Merit wbn(a)merit.edu Nowak, Bill ANS wjn(a)noc.ans.net Nugent, Jay ANS jjn(a)noc.ans.net O'Neil, Michael ANS mjo(a)noc.ans.net Owen, Kraig CICnet tko(a)cic.net Parrish, Gartha Merit gsp(a)merit.edu Partan, Andrew UUNET asp(a)uunet.uu.net Philyaw, Anthony ANS atp(a)noc.ans.net Powell, Steve ANS sep(a)noc.ans.net Priestley, Selina ANS sfp(a)noc.ans.net Prue, Walt Los Nettos prue(a)ISI.EDU Repucci, Sheri Merit smr(a)merit.edu Riolo, Rick Merit rlr(a)merit.edu Satyam, Surekha ANS surekha(a)noc.ans.net Scudder, John Merit jgs(a)merit.edu Shih, Lo ANS kls(a)noc.ans.net Smith, Kim ANS kas(a)noc.ans.net Thomas, Joseph MSCNET jpt(a)msc.edu Topolcici, Claudio CNRI topolcic(a)CNRI.Reston.VA.US Veach, Ross CICnet rrv(a)chianti.cso.uiuc.edu Vollbrecht, John Merit jrv(a)merit.edu Ward, JoAnn Merit jaw(a)merit.edu Waters, Jack SURAnet waters(a)sura.net Widmayer, Steve Merit skw(a)merit.edu Williams, Jim Merit jimw(a)merit.edu Winkler, Linda Argonne lwinkler(a)anl.gov Wittbrodt, Cathy BARRnet cjw(a)magnolia.Stanford.EDU Wojcik, Jane BBN/Milnet jwojcik(a)BBN.COM Yazdian, Riaz ANS rty(a)merit.edu Yu, Jessica Merit jyy(a)merit.edu Zawada, Paul NCSA zawada(a)ncsa.uiuc.edu

1 0

Re: the NIC?
by henryc＠oar.net 06 Oct '93

06 Oct '93

>Have you requested a block and had trouble? Scott, Well, ummm, yeah. We recently asked for a 256 address block of Class C space and was told to go to ANS for addresses. We've currently got a 256 block that's about used up, plus we obtained another 256 block for a customer of ours who had burned their B. We were asked to prove that we had used up both blocks (and proving that we had) were then told to go to ANS. I can put in arguments here about supernetting, routing, and multihomed networks. It doesn't make sense to me for a network that is multihomed to have a portion of someone else's address space... We'd thought about just asking for a 1024 address block, but given our recent experiences (we really got grilled on the second 256 block ["are you using those numbers"]), we decided not to even try. henry

8 9

PRDB Minutes from Regional-Techs Meeting in Ann Arbor
by Dale S. Johnson 05 Oct '93

05 Oct '93

These are notes from Monday's presentation at the Regional-Techs meeting in Ann Arbor. Merit will be compiling some kind of results from the meeting, but I'm about to be out on vacation for a couple of weeks and I'd like to get these to Regional-Techs before I leave. Apologies for the separate mailing. --Dale Status of Merit PRDB support of CIDR (and other assorted enhancements): --------- PRDB Support for CIDR: "CIDR-1" (The ability to accept and propogate aggregates): Finished; ready for testing & deployment when GateD is ready. (Includes NACR and auto-NACR updates, gated generation, reports, whois support). Input: Identical to old NACR, except that "x.x.x/len" is now supported where "x.x.x" used to be supported. The old format will still work: if the length is left off, this will be assumed to be a Class A, B, or C as appropriate. Output: In all published output, "x.x.x" is replaced by "x.x.x/len" . (Exception: nets.unl.now has the fields separately. The Right Thing is done within the GateD configuration files). "CIDR-2" (The ability for NSFNET to create aggregates on behalf of its peers): Targeted for mid-November, to be ready for BGP-4 in GateD. Input: Identical to the old NACR, with the addition of zero or more lines labelled "trigger"* following "netname": netnum: 193/8 [exact] netname: All_of_Europe trigger: 193.0.0/24 exact trigger: 193.1/16 refines If trigger lines are present, then the "netnum" line may contain an optional keywork "refines" or "exact" to modify the way this aggregate is exported from AS-690. The contents of the "trigger" line may be any classless IP address ("x.x.x/len") which is fully contained within netnum, followed by at most one of the words "refines" or "exact". Output: Aggregates created this way will be included with all other nets in all current reports of nets (whois and published files). All aggregates created this way will be automatically entered into the Aggregate Registry. This database will be searchable by whois, reports will be published (ftp, gopher), and an "exchange format" of the entire contents of the registry will be published. (See Aggregate Registry discussion later). A separate report of AS 690 Created Nets with their triggers and full definitions (flags) will be produced. --------- Other PRDB enhancements: Whois Server: All the functionality of the "dbshow" clients is now available via "whois -h prdb.merit.edu". "Whois help" for help. Nets reports: "nets.unl.now" ("unload" format) and "nets.tag.now" ("tagged format") are now published containing all information about nets. Home AS: Very soon accepted in NACRs, and published in nets reports. This inspired a lively discussion about how the community can encourage each other to fill in this information, since it is not required for NSFNET routing, and since we have about 13000 current networks registered without this information. But the PRDB software is ready and willing to be used. US State: Accepted in NACRs, and published in nets reports and in a new nets.by.state report. policy.as_690: Modified/expanded RIPE format of AS 690 AS policy, published for automatic updating of RIPE database. Shared Whois project: negotiations currently underway to modify our Organization Address fields to be compatible with the NIC, RIPE, and others. Then, to compare and update each others' data. (See SWIP presentation). CLNP Support: We have a preliminary schema and some initial forms and report formats for supporting CLNP in the PRDB. Nodes and Applications (with their addresses), RDIs, and contacts are included. Gated will be generated; information will be available via whois, ftp, and gopher. Motif Support: We are looking for ways to speed development, and are experimenting with a Motif GUI builder. Is there an X-based application that would be most useful to you that we should experiment on first? (Anyone want to trade notes on GUI builders?) --------- Aggregate Registry Development (Non-NSFNET Specific): We spent quite a bit of time on this; details to follow. The "Aggregate Registry" concept of RFC 1482 will be split into an AS-based "Routing Registry" and a separate "Routed Net Registry", which will include not only Aggregates but also any other "Classless Net" that needs registration. (Possibly every net on the connected Internet?). All such nets will be entered only by their Home AS or their creators (in the case of aggregates); not by everyone who announces them. If other organizations build similar registries, this one will exchange information with them on a peer basis or otherwise simulate a full distributed database solution. -------- Upcoming non-backward-compatible changes: It is likely that the format of the Organization Address field in the new nets.unl.now and nets.tag.now reports may change as a result of the SWIP ("Shared Whois") project reconciling Organization Address schemas between Merit, the InterNic, RIPE, and others. Merit's single field will lilely be broken into multiple independent subfields within the current single field. The format of all AS 690 announcement lists in all PRDB input and output everywhere *might* have to change as a result of supporting multiple gateways to single ASs. (E.g. a syntax something like: 1:200(NSS1) 2:200(NSS2) ). Then again, maybe not. Your opinions on ways to minimize disruption in the reports are welcome. Many Net reports are scheduled to go away Nov 1. See the file nic.merit.edu:nsfnet/announced.networks/reports.summary for details.

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 05 Oct '93

05 Oct '93

------------------------------------------------------------------------------ NOTICE: Based on the NSFNET Reports Survey results from this summer, some current NSFNET reports are scheduled to be deleted November 1. Details below. ------------------------------------------------------------------------------ The following additions have been made to the NSFNET policy-based routing database and will be installed on the backbone by 08:00 EDT: Total = Class A+Class B+Class C Configured Networks 16898 = 27 3998 12873 Added Networks 113 = 0 4 109 Deleted Networks 0 = 0 0 0 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 134.113 IMF C:US D:10/05/93 1:1800 2:1240 145.227 ICL C:GB D:10/05/93 1:701 2:702 3:1800 160.43 BLOOMBERG C:US D:10/05/93 1:2149 2:174 164.153 COAT C:US D:10/05/93 1:1800 2:1240 192.12.208 TSASA-NET C:US D:10/05/93 1:291 2:293 192.16.21 LANL-TS-SDSC-NET C:US D:10/05/93 1:195 192.31.194 REMTECH C:US D:10/05/93 1:279 2:86 192.31.246 MARBLE-NET C:US D:10/02/93 1:1800 2:1240 3:281 4:701 192.104.79 TYBHSV C:US D:10/05/93 1:279 2:86 192.129.34 PANASONIC-C-129-34 C:DE D:10/05/93 1:1324 192.157.148 INFOLAN26 C:US D:10/05/93 1:2149 2:174 192.216.83 BARRNET-216-83 C:US D:10/05/93 1:200 2:201 192.220.218 UPS8-NET3 C:US D:10/05/93 1:685 2:73 3:101 192.239.212 SURA-SO-CONF C:US D:10/05/93 1:279 2:86 192.245.82 AGAMES-1 C:US D:10/05/93 1:2551 192.245.83 AGAMES-2 C:US D:10/05/93 1:2551 192.245.84 AGAMES-3 C:US D:10/05/93 1:2551 192.245.85 AGAMES-4 C:US D:10/05/93 1:2551 193.4.180 IS-LANNET C:IS D:10/05/93 1:1800 2:1133 3:1240 193.40.5 CCU-UT C:EE D:10/05/93 1:1800 2:1133 3:1240 193.40.7 UT-NET C:EE D:10/05/93 1:1800 2:1133 3:1240 193.40.246 PLD-NET C:EE D:10/05/93 1:1800 2:1133 3:1240 193.40.247 TTU-NET-5 C:EE D:10/05/93 1:1800 2:1133 3:1240 193.48.188 FRIFRESINET C:FR D:10/05/93 1:1800 2:1240 193.51.52 FR-EC-LILLE C:FR D:10/05/93 1:1800 2:1240 193.52.216 EARNOFFICE C:FR D:10/05/93 1:1800 2:1240 193.55.87 FR-CNRS-A16 C:FR D:10/05/93 1:1800 2:1240 193.55.160 FR-ENSMA-01 C:FR D:10/05/93 1:1800 2:1240 193.55.161 FR-ENSMA-02 C:FR D:10/05/93 1:1800 2:1240 193.55.162 FR-ENSMA-03 C:FR D:10/05/93 1:1800 2:1240 193.55.163 FR-ENSMA-04 C:FR D:10/05/93 1:1800 2:1240 193.55.164 FR-ENSMA-05 C:FR D:10/05/93 1:1800 2:1240 193.55.165 FR-ENSMA-06 C:FR D:10/05/93 1:1800 2:1240 193.55.240 FR-RENATER-D1 C:FR D:10/05/93 1:1800 2:1240 193.59.9 BIAL-NET-2 C:PL D:10/05/93 1:1800 2:1133 3:1240 193.59.10 BIAL-NET-3 C:PL D:10/05/93 1:1800 2:1133 3:1240 193.59.11 BIAL-NET-4 C:PL D:10/05/93 1:1800 2:1133 3:1240 193.84.84 FARM-C-84-84 C:CZ D:10/05/93 1:1133 2:1800 3:1240 193.84.85 FARM-C-84-85 C:CZ D:10/05/93 1:1133 2:1800 3:1240 193.84.86 FARM-C-84-86 C:CZ D:10/05/93 1:1133 2:1800 3:1240 193.84.87 FARM-C-84-87 C:CZ D:10/05/93 1:1133 2:1800 3:1240 193.104.196 FR-RGIM3-2 C:FR D:10/05/93 1:1800 2:1240 193.129.162 PHILIP-UK C:GB D:10/05/93 1:701 2:702 3:1800 193.145.32 UPFNET-C-145-32 C:ES D:10/05/93 1:1133 2:1800 193.145.33 UPFNET-C-145-33 C:ES D:10/05/93 1:1133 2:1800 193.145.34 UPFNET-C-145-34 C:ES D:10/05/93 1:1133 2:1800 193.145.35 UPFNET-C-145-35 C:ES D:10/05/93 1:1133 2:1800 193.145.36 UPFNET-C-145-36 C:ES D:10/05/93 1:1133 2:1800 193.145.37 UPFNET-C-145-37 C:ES D:10/05/93 1:1133 2:1800 193.145.38 UPFNET-C-145-38 C:ES D:10/05/93 1:1133 2:1800 193.145.39 UPFNET-C-145-39 C:ES D:10/05/93 1:1133 2:1800 193.145.40 UPFNET-C-145-40 C:ES D:10/05/93 1:1133 2:1800 193.145.41 UPFNET-C-145-41 C:ES D:10/05/93 1:1133 2:1800 193.145.42 UPFNET-C-145-42 C:ES D:10/05/93 1:1133 2:1800 193.145.43 UPFNET-C-145-43 C:ES D:10/05/93 1:1133 2:1800 193.145.44 UPFNET-C-145-44 C:ES D:10/05/93 1:1133 2:1800 193.145.45 UPFNET-C-145-45 C:ES D:10/05/93 1:1133 2:1800 193.145.46 UPFNET-C-145-46 C:ES D:10/05/93 1:1133 2:1800 193.145.47 UPFNET-C-145-47 C:ES D:10/05/93 1:1133 2:1800 193.145.48 UPFNET-C-145-48 C:ES D:10/05/93 1:1133 2:1800 193.145.49 UPFNET-C-145-49 C:ES D:10/05/93 1:1133 2:1800 193.145.50 UPFNET-C-145-50 C:ES D:10/05/93 1:1133 2:1800 193.145.51 UPFNET-C-145-51 C:ES D:10/05/93 1:1133 2:1800 193.145.52 UPFNET-C-145-52 C:ES D:10/05/93 1:1133 2:1800 193.145.53 UPFNET-C-145-53 C:ES D:10/05/93 1:1133 2:1800 193.145.54 UPFNET-C-145-54 C:ES D:10/05/93 1:1133 2:1800 193.145.55 UPFNET-C-145-55 C:ES D:10/05/93 1:1133 2:1800 193.145.56 UPFNET-C-145-56 C:ES D:10/05/93 1:1133 2:1800 193.145.57 UPFNET-C-145-57 C:ES D:10/05/93 1:1133 2:1800 193.145.58 UPFNET-C-145-58 C:ES D:10/05/93 1:1133 2:1800 193.145.59 UPFNET-C-145-59 C:ES D:10/05/93 1:1133 2:1800 193.145.60 UPFNET-C-145-60 C:ES D:10/05/93 1:1133 2:1800 193.145.61 UPFNET-C-145-61 C:ES D:10/05/93 1:1133 2:1800 193.145.62 UPFNET-C-145-62 C:ES D:10/05/93 1:1133 2:1800 193.145.63 UPFNET-C-145-63 C:ES D:10/05/93 1:1133 2:1800 193.170.72 TUNET-S6 C:AT D:10/05/93 1:1133 2:1800 3:1240 198.4.188 NET-ELBOWS-1 C:US D:10/05/93 1:701 2:702 198.30.145 OAR145 C:US D:10/05/93 1:600 198.49.190 MONMTH-CSS C:US D:10/05/93 1:19 2:568 198.51.209 DRS C:US D:10/05/93 1:97 198.59.157 NM-MUSEUM C:US D:10/05/93 1:209 2:210 198.59.160 RESPEC-NM C:US D:10/05/93 1:209 2:210 198.59.161 ROS-NM C:US D:10/05/93 1:209 2:210 198.59.162 ENGR-INTRNL C:US D:10/05/93 1:209 2:210 198.85.78 MRL1-NET C:US D:10/05/93 1:81 198.86.18 FORVUS1-NET C:US D:10/05/93 1:81 198.97.180 BG-NET1 C:US D:10/05/93 1:19 2:568 198.98.155 C2DELLINK C:US D:10/05/93 1:19 2:568 198.99.146 INDIRECT C:US D:10/05/93 1:1740 198.102.218 OASH-HUB C:US D:10/05/93 1:86 2:279 198.120.11 NSI-C-120-11 C:US D:10/05/93 1:1262 2:372 3:297 198.133.87 SQ-SLC C:US D:10/05/93 1:1240 2:1800 198.136.167 INFOR C:US D:10/02/93 1:1800 2:1240 3:281 4:701 198.138.51 DRS-1 C:US D:10/05/93 1:97 198.138.52 DRS-2 C:US D:10/05/93 1:97 198.147.227 THECB1 C:US D:10/05/93 1:280 198.147.228 THECB2 C:US D:10/05/93 1:280 198.175.10 PAGESAT-C3 C:US D:10/05/93 1:1740 198.182.225 ATI C:US D:10/05/93 1:2551 198.182.240 PSUNET-C1 C:US D:10/05/93 1:93 198.182.241 PSUNET-C2 C:US D:10/05/93 1:93 198.182.242 PSUNET-C3 C:US D:10/05/93 1:93 198.182.243 PSUNET-C4 C:US D:10/05/93 1:93 198.187.0 WA-DIS2-NET1 C:US D:10/05/93 1:685 2:73 3:101 198.187.1 WA-DIS2-NET2 C:US D:10/05/93 1:685 2:73 3:101 198.187.2 WA-DIS2-NET3 C:US D:10/05/93 1:685 2:73 3:101 198.187.3 WA-DIS2-NET4 C:US D:10/05/93 1:685 2:73 3:101 198.233.31 SERSOL-NET C:US D:10/05/93 1:209 2:210 198.233.39 RIA-NET C:US D:10/05/93 1:209 2:210 199.0.52 MONSECBAN C:US D:10/05/93 1:1800 2:1240 200.0.86 CEFET-ANMG1 C:BR D:10/05/93 1:293 2:291 200.9.71 LAC-ANPR C:BR D:10/05/93 1:293 2:291 200.9.125 LCCUFMG-ANMG C:BR D:10/05/93 1:293 2:291 ------------------------------------------------------------ ATI, 2256 Fairhill Lane, San Jose, CA 95125, USA 1:2551 NETCOM ----------- 198.182.225 ATI (US) Atari Games, Corporation, 675 Sycamore Drive, Milpitas, CA 95035, USA 1:2551 NETCOM ---------- 192.245.82 AGAMES-1 (US) 192.245.83 AGAMES-2 (US) 192.245.84 AGAMES-3 (US) 192.245.85 AGAMES-4 (US) BARRNet, Pine Hall 115, Stanford, CA 94305-4122, USA 1:200 BARRNet 2:201 BARRNet ---------- 192.216.83 BARRNET-216-83 (US) Bloomberg LP, 100 Business Park Drive, Princeton, NJ 08542-0888, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ------ 160.43 BLOOMBERG (US) Burlington Coat Factory, 1380 Route 130 North, Burlington, NJ 08016, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------- 164.153 COAT (US) CDR USACECOM, AMSEL-RD-SE-SY-CC-CSS(LaRocca), Ft Monmouth, NJ 07703, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 198.49.190 MONMTH-CSS (US) Centre National de la Recherche Sientifique - Siege, 15 quai A. France 75700 Paris CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific --------- 193.55.87 FR-CNRS-A16 (FR) Centro Federal de Educacao Tecnologica de Minas Gerais, Av. Amazonas, 5253 30480-000 - Belo Horizonte -, MG BRAZIL, Belo Horizonte, Minas Gerais, 31270-010, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------- 200.0.86 CEFET-ANMG1 (BR) Charles University, Hradec Kralove, 501 65, CZECH REPUBLIC 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific --------- 193.84.84 FARM-C-84-84 (CZ) 193.84.85 FARM-C-84-85 (CZ) 193.84.86 FARM-C-84-86 (CZ) 193.84.87 FARM-C-84-87 (CZ) Computing Centre, Tartu University, J. Liivi 2, EE2400 Tartu, ESTONIA 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific -------- 193.40.5 CCU-UT (EE) DOIM, Bldg. 218, Lexington, KY 40511-5109, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 198.97.180 BG-NET1 (US) DRS - Diagnostic Retrivial Systems, 16 Thorton Road, Oakland, NJ 07436, USA 1:97 JvNCnet Regional Network ---------- 198.138.51 DRS-1 (US) 198.138.52 DRS-2 (US) 198.51.209 DRS (US) Defense Information Systems Agency, DISA/TFDC, 3701 N. Fairfax Drive, Arlington, VA 22203-1713, USA 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) ---------- 198.98.155 C2DELLINK (US) Department of Physics, University of Tartu, Tahe 4 - 409, EE2400 Tartu, ESTONIA 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific -------- 193.40.7 UT-NET (EE) Ecole Centrale de Lille, BP 48, 59651 Villeneuve d'Ascq CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific --------- 193.51.52 FR-EC-LILLE (FR) Ecole Nationale Superieure de Mecanique & Aeronautique, Laboratoire d'Aerodynamique, rue Guillaume VII le Troubadour, 86034 Poitiers CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 193.55.160 FR-ENSMA-01 (FR) 193.55.161 FR-ENSMA-02 (FR) 193.55.162 FR-ENSMA-03 (FR) 193.55.163 FR-ENSMA-04 (FR) 193.55.164 FR-ENSMA-05 (FR) 193.55.165 FR-ENSMA-06 (FR) Ehitajate Road 5, Tallinn Technical University, Dep. of Computer Electronic, Tallinn, ESTONIA 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific ---------- 193.40.246 PLD-NET (EE) Engineering International, 2313 Headingly N.W., Albuquerque, NM 87107, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.59.162 ENGR-INTRNL (US) European Academic & Reasearch Network, EARN CIRCE BP 167, F-91403 Orsay CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 193.52.216 EARNOFFICE (FR) Forvus Research, Inc., 5205 Capital Boulevard, Raleigh, NC 27604, USA 1:81 CONCERT --------- 198.86.18 FORVUS1-NET (US) ICL, Cavendish Road, Stevenage, Hertfordshire, England, UNITED KINGDOM 1:701 Alternet 2:702 Alternet 3:1800 ICM-Atlantic ------- 145.227 ICL (GB) IFRESI - Institut Federatif de Recherche sur les Economies et les Societes Industrielles, 2 rue de Canonniers, F-59800 Lille, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 193.48.188 FRIFRESINET (FR) INSERM U91, Hopital Henry Mondor, 94010 Creteil CEDEX, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ----------- 193.104.196 FR-RGIM3-2 (FR) Infonet, 2100 E. Grand Avenue, El Segundo, CA 90245, USA 1:2149 PSINET-2 2:174 NYSERNet Regional Network / PSI ----------- 192.157.148 INFOLAN26 (US) Inforonics, Inc., 550 Newtown Road, P. O. Box 458, Littleton, MA 01460, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:281 NEARnet Regional Network 4:701 Alternet ----------- 198.136.167 INFOR (US) Institute of Computer Science, Bialystok Technical University, ul. Wiejska 45 a, 15-351 Bialystok, POLAND 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific --------- 193.59.10 BIAL-NET-3 (PL) 193.59.11 BIAL-NET-4 (PL) 193.59.9 BIAL-NET-2 (PL) Institute of Cybernetics, Akadeemia tee 21, EE0108 Tallinn, ESTONIA 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific ---------- 193.40.247 TTU-NET-5 (EE) International Monetary Fund, 700 19th Street N.W., Washington, DC 20431, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ------- 134.113 IMF (US) Internet Direct, Inc., 1366 E. Thomas Road, Suite 210, Phoenix, AZ 85014, USA 1:1740 CERFnet ---------- 198.99.146 INDIRECT (US) Laboratorio Central de Eletrotecnica e Eletronica-LAC, Rua Coronel Dulcidio, 800, Curitiba, Parana, 80230-170, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) -------- 200.9.71 LAC-ANPR (BR) Laboratorio de Computacao Cientifica Universidade Federal de Minas Gerais, Av. Antonio Carlos 6627-Pampulha, Belo Horizonte, Minas Gerais, 31270-010, BRAZIL 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) --------- 200.9.125 LCCUFMG-ANMG (BR) Laugavegur 77, 101 Reykjavik, ICELAND 1:1800 ICM-Atlantic 2:1133 CERN-EBONE 3:1240 ICM-Pacific --------- 193.4.180 IS-LANNET (IS) Los Alamos National Laboratory, TA-0, Los Alamos, NM 87545, USA 1:291 Energy Science Network (FIX-West) 2:293 Energy Science Network (FIX-East) ---------- 192.12.208 TSASA-NET (US) Marble Associates, Inc., 200 North Great Road, Lincoln, MA 01773, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific 3:281 NEARnet Regional Network 4:701 Alternet ---------- 192.31.246 MARBLE-NET (US) McMahan Electro-Optics, 79 T.W. Alexander Dr., Bldg. 4201, P.O. Box 14026, Research Triangle Park, NC 27709-4026, USA 1:81 CONCERT --------- 198.85.78 MRL1-NET (US) Monarch Security Bancorp, 2516 Highway 35, Manasquan, NJ 08736, USA 1:1800 ICM-Atlantic 2:1240 ICM-Pacific -------- 199.0.52 MONSECBAN (US) NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA 1:1262 Nasa Science Network (Boulder, CO) 2:372 Nasa Science Network (FIX-West) 3:297 Nasa Science Network (FIX-East) ---------- 198.120.11 NSI-C-120-11 (US) NETWORK OPERATIONS CENTER Los Alamos National Laboratory, Network Engineering, MS B255, Los Alamos, NM 87545, USA 1:195 SDSC Regional network --------- 192.16.21 LANL-TS-SDSC-NET (US) New Mexico Technet, Inc., 1801 Mountain Rd. N.W., Albuquerque, NM 87104-1375, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.59.157 NM-MUSEUM (US) New Mexico Technet, Inc., 4100 Osuna Blvd, N.E. Suite 103 Albuquerque, NM 87109, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.59.160 RESPEC-NM (US) 198.59.161 ROS-NM (US) OARnet, 1224 Kinnear Road, Columbus, OH 43212, USA 1:600 OARNET, Cleveland, OH ---------- 198.30.145 OAR145 (US) PANASONIC, European Research and Development Center, Monza Str. 4c, D-63225 Langen, GERMANY 1:1324 ANS New York City - DNSS 35 ---------- 192.129.34 PANASONIC-C-129-34 (DE) Pagesat Inc., 992 San Antonio Road, Palo Alto, CA 94303, USA 1:1740 CERFnet ---------- 198.175.10 PAGESAT-C3 (US) Philips Research Labs, Cross Oak Lane, Salfords, Redhill, Surrey, England, RH1 5HA, UNITED KINGDOM 1:701 Alternet 2:702 Alternet 3:1800 ICM-Atlantic ----------- 193.129.162 PHILIP-UK (GB) Pittsburg State University, Office of Information Systems, Pittsburg State University, 1701 S. Broadway, Pittsburg, KS 66762, USA 1:93 MIDnet ----------- 198.182.240 PSUNET-C1 (US) 198.182.241 PSUNET-C2 (US) 198.182.242 PSUNET-C3 (US) 198.182.243 PSUNET-C4 (US) RENATER GIP, Tour 26-16 5 eme Etage, 4 place Jussieu, 75252 Paris CEDEX 05, FRANCE 1:1800 ICM-Atlantic 2:1240 ICM-Pacific ---------- 193.55.240 FR-RENATER-D1 (FR) Remtech Inc., 3304 Westmill Drive, Huntsville, AL 35805, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ---------- 192.31.194 REMTECH (US) Resource Integration Associates, Inc., 633 17th St., Ste. 2390, Denver, CO 80202, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.233.39 RIA-NET (US) SURAnet, 8400 Baltimore Blvd. Suite 101, College Park, MD 27040, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ----------- 192.239.212 SURA-SO-CONF (US) Serendipitous Solutions, 475 Atkinson Dr., Ste. 1701, Honolulu, HI 96814, USA 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 ---------- 198.233.31 SERSOL-NET (US) State of Washington, DIS/TSD MS 2450, Olympia, WA 98504-2450, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network --------- 198.187.0 WA-DIS2-NET1 (US) 198.187.1 WA-DIS2-NET2 (US) 198.187.2 WA-DIS2-NET3 (US) 198.187.3 WA-DIS2-NET4 (US) Sunquest Information Systems - SLC Office, 4525 S. Wasatch Blvd., Suite 335, Salt Lake City, UT 84124, USA 1:1240 ICM-Pacific 2:1800 ICM-Atlantic ---------- 198.133.87 SQ-SLC (US) TYBRIN Corporation, 4900 University Square, Huntsville, AL 35816, USA 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) ---------- 192.104.79 TYBHSV (US) Texas Higher Education Coordinating Board, PO Box 12788, Austin, TX 78711, USA 1:280 SESQUINET Regional Network ----------- 198.147.227 THECB1 (US) 198.147.228 THECB2 (US) The Elbows Association, 11715 Fireside Place, Suite J, Reston, VA 22090, USA 1:701 Alternet 2:702 Alternet --------- 198.4.188 NET-ELBOWS-1 (US) U.S. Public Health Service/Office of the Assistant Secretary for Health, 5600 Fishers Lane, Room 17-69, Rockville, MD 20857, USA 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) ----------- 198.102.218 OASH-HUB (US) Universitat Pompeu Fabra, Placa de la Merce, 12, Barcelona - 08002, SPAIN 1:1133 CERN-EBONE 2:1800 ICM-Atlantic ---------- 193.145.32 UPFNET-C-145-32 (ES) 193.145.33 UPFNET-C-145-33 (ES) 193.145.34 UPFNET-C-145-34 (ES) 193.145.35 UPFNET-C-145-35 (ES) 193.145.36 UPFNET-C-145-36 (ES) 193.145.37 UPFNET-C-145-37 (ES) 193.145.38 UPFNET-C-145-38 (ES) 193.145.39 UPFNET-C-145-39 (ES) 193.145.40 UPFNET-C-145-40 (ES) 193.145.41 UPFNET-C-145-41 (ES) 193.145.42 UPFNET-C-145-42 (ES) 193.145.43 UPFNET-C-145-43 (ES) 193.145.44 UPFNET-C-145-44 (ES) 193.145.45 UPFNET-C-145-45 (ES) 193.145.46 UPFNET-C-145-46 (ES) 193.145.47 UPFNET-C-145-47 (ES) 193.145.48 UPFNET-C-145-48 (ES) 193.145.49 UPFNET-C-145-49 (ES) 193.145.50 UPFNET-C-145-50 (ES) 193.145.51 UPFNET-C-145-51 (ES) 193.145.52 UPFNET-C-145-52 (ES) 193.145.53 UPFNET-C-145-53 (ES) 193.145.54 UPFNET-C-145-54 (ES) 193.145.55 UPFNET-C-145-55 (ES) 193.145.56 UPFNET-C-145-56 (ES) 193.145.57 UPFNET-C-145-57 (ES) 193.145.58 UPFNET-C-145-58 (ES) 193.145.59 UPFNET-C-145-59 (ES) 193.145.60 UPFNET-C-145-60 (ES) 193.145.61 UPFNET-C-145-61 (ES) 193.145.62 UPFNET-C-145-62 (ES) 193.145.63 UPFNET-C-145-63 (ES) University of Puget Sound, 1500 N. Warner, Tacoma, WA 98416, USA 1:685 NorthWestNet Regional Network 2:73 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network ----------- 192.220.218 UPS8-NET3 (US) University of Technology, Wiedner Hauptstrasse 8-10/020, A-1040 Wien, AUSTRIA 1:1133 CERN-EBONE 2:1800 ICM-Atlantic 3:1240 ICM-Pacific ---------- 193.170.72 TUNET-S6 (AT) ------------------------------------------------------------ The following Midlevel/Regional peering sessions have also been added: AS 279 - SURANET Regional Network (Georgia Tech) (US) - ENSS 138 Peer: 192.221.26.2 - SURANET, University of Maryland, Computer Science Center, College Park, MD 20742, USA - git.sura.net AS 1838 - CERFNET-2 - ENSS 135 Peer: 198.17.47.153 - CERFnet, P.O. Box 85608, San Diego, CA 92186-9784, USA - route-server.cerf.net AS 2548 - DIGEX-AS - ENSS 230 Peer: 164.109.20.15 - Digital Express Group, Inc., 6006 Greenbelt Road, #228, Greenbelt, MD 20770, USA - nitrous.digex.net ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nic.merit.edu by 08:00 EDT: configuration reports -- nic.merit.edu:nsfnet/announced.networks: as-as.now as-gw.now ans_core.now country.now net-comp.now nets.doc nets.tag.now nets.unl.now NSS routing software configuration files -- nic.merit.edu:nsfnet/backbone.configuration: nss<NSS number>.t3p --------------------------------------------------------------- THE FOLLOWING REPORTS ARE STILL PRODUCED, but these reports are scheduled to be deleted on November 1 as a result of the NSFNET Reports Survey last summer. The current versions of these reports are stamped with a message describing this change, and describing how Merit would like your input if these reports continue to be necessary to you. More text about this subject is included in the file "survey.results" on the announced.networks directory. as-site.now gate-gw.now nets.as_<AS_Number> net-ter.now net-net.now netcount.now non-us.now nss-as.now nss-gw.now --------------------------------------------------------------- Please send all requests for configuration changes to nsfnet-admin(a)merit.edu using the NSFNET configuration forms. The forms are available on-line from the nic.merit.edu machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files template.net, template.net.README, template.gate, and template.as. NOTE: In order to more efficiently process your requests, we have moved to a system which requires the use of template.net (NACR) version 7.0 ******************************* --Steve Widmayer Merit/NSFNET skw(a)merit.edu --Enke Chen Merit/NSFNET enke(a)merit.edu --Steven J. Richardson Merit/NSFNET sjr(a)merit.edu

1 0

NIC Fest '93 Announcement, Second Mailing, Updated
by susan calcari 04 Oct '93

04 Oct '93

Please forward this to any NIC personnel or others who support Internet users. Thanks. ----------------------------------------------------------------- NIC Fest '93 November 6, 1993 San Diego, California Apologies to those who may be seeing this twice. Included in this second mailing is additional information about the individual sessions at NIC Fest and the name of our closing speaker: Alan Emtage, Vice President of Research and Development, Bunyip Information Systems, and co-developer of Archie. Other speakers include: Jane Smith, Assistant Director, Clearinghouse for Networked Information Discovery and Retrieval (CNIDR) Joyce Reynolds, Technical Staff, ISI; Area Director, IETF User Services (Internet Engineering Task Force) The InterNIC Team: Susan Calcari, InterNIC Information Services Subu Subramanian, InterNIC Directory and Database Services Scott Williamson, InterNIC Registration Services Send in the registration form below soon to hold your place since attendance is expected to be high. ------------------------------------------------------------------ NIC Fest '93 The Workshop for Network Information Center Staff Wondering what are the most current network services and if you're taking full advantage of them in providing support to your Internet users? Interested in what current projects are underway to develop new Internet documentation and tools? Wondering if there are other groups who would like to collaborate on projects you'd like to see completed? Want to know what's just around the corner in the way of networked information and services? Then attend NIC Fest '93 and have all of these questions answered by leading Internet experts. Meet your colleagues from around the country and discuss common issues while getting to know the person attached to the email addresses you know so well. Join us for a day-long workshop specifically designed for network information center (NIC) management, staff, and anyone responsible for supporting Internet users. In addition to a day full of useful information and interaction, you'll receive a free copy of the first issue of NICLink, a CD-ROM based collection of Internet reference materials. (see below) NIC Fest '93, sponsored by InterNIC Information Services will be held on Saturday, November 6, 1993 in San Diego, California. NIC Fest '93 is being held in conjunction with the ACM SIGUCCS '93 conference by invitation of the SIGUCCS Networking Task Force. The SIGUCCS conference is being held in San Diego on November 7-10. For more information on the ACM SIGUCCS conference, FTP to ftp.csus.edu or send mail to siguccs(a)csus.edu. NIC Fest will offer interactive tutorials and discussions on topics of immediate relevance to NIC personnel. Our goal is to leave you informed and up-to-date on NIC tools, projects, and futures. Instructors include leading NIC staffers from around the Internet, representing InterNIC Information Services, Directory and Database Services, Registration Services, the Clearinghouse for Networked Information Discovery and Retrieval (CNIDR), the IETF User Services Working Group, and Bunyip Information Systems. Sessions, all plenary: * The InterNIC - what it is and what it can do for you. A major goal of the InterNIC is to provide services for midlevel and campus NICs. Therefore the first session of the day will be two- way exchange between the InterNIC and attendees to discuss current and future InterNIC projects. Input to the InterNIC staff will be encouraged during this session and throughout the workshop. Moderators: Susan Calcari, Subu Subramanian, and Scott Williamson. * Network Tools - The latest methods for information retrieval, organization, and display, how they work. Gopher, freeWAIS, Archie, Whois++: integration issues and pros and cons discussed from the service provider's perspective. Current status and near future (6 months) developments on all your favorite tools. Instructor: Jane Smith of the Clearinghouse for Network Information Discovery and Retrieval (CNIDR). * NIC Projects BOF - IETF Working Groups. Designed as a "Birds of a Feather", a meeting where everyone with ideas about a given topic gathers to discuss their ideas, interact, learn from each other, and move new projects forward. This first BOF will discuss projects underway in the IETF User Services Working Groups to improve the use and management of networked information. The IETF (Internet Engineering Task Force) Working Groups are a major force in international cooperation to produce documents very useful to end users and network information centers, such as the FYI series of RFC's. BOF Leader: Joyce Reynolds, IETF Area Director, User Services * NIC Projects BOF - Europe and Asia-Pacific. A continuation of NIC Projects discussions with an emphasis on European organizations such as EARN, RIPE, and the RIPE NCC. A new network information center being established to serve the Asia-Pacific community will also be discussed. BOF Leader: Joyce Reynolds * NIC Fest Forum. Attendee participation and two-way communications will be encouraged throughout NIC Fest. However at the end of the day an open forum will be held to give attendees an opportunity to describe their own projects, and for continued discussions of the days topics. Beliefs, convictions, and opinions will be especially welcome during this session. * Upcoming Developments in Cyberspace. Future (1 year) developments in the world of networked information. Will include eye-witness account of the Frankfurt Book Fair, largest book publisher's meeting in the world. (the vision thing :-) Alan Emtage, Vice President of Research and Development, Bunyip A free copy of a special introductory issue of NICLink will be distributed to all NIC Fest attendees. NICLink, issued quarterly, is a CD-ROM subscription service. The NICLink CD will contain the InfoSource, theInformation Services online information database that highlights the information resources of the Internet. Additional information, images, electronic books, and software from the Internet will be included in future issues. The CD-ROM will be compatible with Macintosh, PC Windows, and some UNIX configurations. The software used to present the data is Interleaf's WorldView Press, which incorporates full database search functions as well as hypertext linking capabilities to provide a powerful, easy-to-use interface. Attendance at the NIC Fest is encouraged for all attendees of SIGUUCS and all network information center management, staff, and anyone responsible for supporting Internet users from campus, government, corporate, and network service providers locations. Individuals not responsible for supporting users are welcome to attend; however, basic knowledge of the Internet and Internet terms will be assumed, and the topics will be approached from the providers point of view. If you're attending SIGUCCS, come out early for a Saturday night stay-over and a weekend in San Diego. NIC Fest will be held at the Doubletree Inn (619.239.2200) in downtown San Diego, just two blocks from the Pan Pacific hotel, site of SIGUCCS. Room price will be just $89.00 if you state that your with NIC Fest. Even if you're not attending SIGUCCS, don't miss this chance to hear some of the leaders in information services for the low price of $89. NIC Fest will begin at 9:30 a.m and end at 6:00 p.m. Register soon - a high response to the workshop is expected. A registration form is included below for your convenience. Additional information will be sent later. Please complete the attendee profile whenyou register so that we can best tailor NIC Fest to your specific needs. Send this form or additional questions about NIC Fest to nicfest(a)is.internic.net, or call us at 1.800.444.4345. The registration form can also be faxed or mailed: Barbara Wicklein InterNIC Seminar Coordinator 9-207L General Atomics P.O. Box 85608 San Diego, CA. 92186-9784 FAX: 619.455.4640 See you in November. Until then, see you on the net. ----------------------------------------------------------------- Registration Form Name: Title: Affiliation: Address: Phone: Fax: E-mail: Method of payment: ______check: make payable to General Atomics ______MasterCard _______Visa Name on Credit Card: Credit Card Number:______________ Expiration Date:______________ Attendee Profile -------------------- In order to tailor the NIC Fest agenda and presentations as closely as possible to your needs, we would like input on your level of expertise and job responsibilities. Please take a moment to check the boxes which apply to you. Networking level of expertise: _____intermediate _____advanced _____years using the Internet Responsibilities: _____NIC help desk staff _____NIC help desk supervisor _____network documentation _____network training _____system administration _____Another position, in addition to which you support Internet users ; That position:____________________________________________ Type of users you support: beginners _______intermediate _______advanced _____research _______education _______commercial ______other Please add any details you wish, including particular topics you would like to see covered or issues addressed.

1 0

BGP problem 'lost middleman'
by aggarwal＠nisc.jvnc.net 04 Oct '93

04 Oct '93

Dunno if this has happened to others before, but in case not: I have a setup where 3 routers (ciscos, running 9.1.x if that's important) are running IBGP. A---------B-----------C | ext-net Router-A peers with 'B' & 'C', Router-B peers with B & C and C with B&A (a full IBGP mesh). Router A is an exit/border router. In addition to BGP, the routers run IGRP. The BGP routes are kept separate from the IGRP routes. For whatever reason (not a configuration error), the BGP session between A-B died but not between A-C, B-C. The result was that C 'knew' via the BGP session with A, that to get to external network 'ext-net', it should send traffic to A. It does the IGRP lookup to get to A, and sends the traffic to 'B'. However, since B did not have a BGP session with A, it did not know how to get to the ext-net (in the real case, B was sending traffic back to C since the default route was via C). A potential disaster!! I realize that the problem was the unexpected 'lost' BGP session between A-B, but are we sure that in a more complicated topology, something similar cannot happen ? What really make me worried is that there doesn't seem to be way to detect this kind of a problem easily.. how do others monitor their BGP sessions ? -vikas vikas(a)jvnc.net

4 5

Re: strawman for discussion in Ann Arbor
by Thomas Hutton 04 Oct '93

04 Oct '93

I am also in favor of this change. Sounds good to me. Tom Hutton

1 0

Re: strawman for discussion in Ann Arbor
by Peter Lothberg 04 Oct '93

04 Oct '93

In general the idea is good. Within Ripe a new working group called the "EEPG" was started at the last Ripe meeting, and this group has a very simular agenda. Chairman is Bernhard Stockman. To Peter F's proposal I have a comment; > Interexchange coordination (e.g. Mae-East, etc.) > (network operators as customers of NSFNET NAPs) As the 'GIX-part' of MAE-east servers the Universe, not only one part of the global Internet, I would stress that is one of the tasks of the IEPG, if we all agree on that the IEPG is the place where the regional coordinating bodys meet. As the US side has NAP's and Europe has IXF's, and they are different, It makes sence to put them on the regional agenda. -Peter > cheers and see you in A**2, This message is brought to you from Holiday Inn, AA... -Peter (L)

4 3

Re: strawman for discussion in Ann Arbor
by Mark Knopper 04 Oct '93

04 Oct '93

Hi Bill, Glad you can make it. From the holiday inn, turn left of the parking lot so that you will be going west on Plymouth Road. The first light will be Green Road--turn left on Green. After a half mile or so turn right on Hubbard Road. Proceed straight past the light at Huron Parkway. There is a curve to the left and a stop sign. Proceed straight. At the stop sign at Beal Ave., turn left. Then, turn right at the stop sign at Bonisteel Blvd. The Chrysler Parking lot is on the right side, just past the Cooley Labs building. If you get lost, call our offices at 936-3335. Mark > From: bmanning(a)is.rice.edu (William Manning) > To: mak(a)merit.edu (Mark Knopper) > Hi Mark, > I just found my way into town and would like directions from the > Holiday Inn to the Crysler building. Can you forward ASCII directions? > > -- > Regards, > Bill Manning bmanning(a)rice.edu PO Box 1892 > 713-285-5415 713-527-6099 Houston, Texas > R.U. (o-kome) 77251-1892

2 1

Re: strawman for discussion in Ann Arbor
by peter＠goshawk.lanl.gov 04 Oct '93

04 Oct '93

I think the critical component for any successful forum is whether or not the agenda is relevent to the people participating in the forum. As such there are really few technical and operational differences between GIX and NAP issues. It is really just an incidental difference in where you are operating in the global Internet mesh. Currently there is a single root (the mesh is at this point is close to a tree and the GIX is very close to being the root), but over time this will diffuse, and each party will probably root a hierarchical routing tree out of the mesh by logically pulling themselves up to the root. In this sense the nature of regionally defined vrs globally defined boundaries in terms of GIX/NAP and IEPG/{RIPE, US-NOGIN, PAC-NOGIN, LATIN-NOGIN, etc.} are somewhat artificial. They are still useful since they provide a mechanism for reasonable meeting sizes and scoping of discussions, containment of costs for participating in meetings (e.g. travel), and allows for taking advantage of regional initiatives (U.S. NII, European CEC, etc.) and regional differences in terms of operational context. I would think it best if the boundaries between global and regional NOGINs are kept in an ad-hoc manner. cheers, peter

3 2