From bound@zk3.dec.com Wed Apr 1 16:12:06 1998 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Wed, 01 Apr 1998 11:12:06 -0500 Subject: DIGITAL-BE Site Route Problems Message-ID: <199804011612.AA22199@wasted.zk3.dec.com> Folks, This site was causing router problems and it has been reported. The person maintaining this site has left the company and things got messed up. Digital is fixing this one way or the other now. For the future on the 6bone Cabletron and Digital are now separate eng'g groups for this kind of testing. So if your running a Cabletron Routabout please make sure you have connection to them. It is the same folks, just the name has changed. Also our backbone site at DIGITAL-CA is running a Cisco for IPv6 Routing. thanks /jim From romanp@wuppy.rcs.ru Thu Apr 2 10:41:10 1998 From: romanp@wuppy.rcs.ru (Roman V. Palagin) Date: Thu, 2 Apr 1998 14:41:10 +0400 (MSD) Subject: How I can Join 6BONE? Message-ID: Hello. I just read 'How to join the 6bone' page, and 'steel unclear about anything' :). I've only one question - where i can find step-by-step guide about joining 6BONE? What should I do first? Thanx. ----------------------------------------------------------------------------- Roman V. Palagin Network Administrator - RP40-RIPE ----------------------------------------------------------------------------- FreeBSD 3.0-CURRENT #21: Thu Apr 2 13:02:16 MSD 1998 From lalle@sics.se Thu Apr 2 13:07:13 1998 From: lalle@sics.se (Lars Albertsson) Date: 02 Apr 1998 15:07:13 +0200 Subject: How I can Join 6BONE? In-Reply-To: "Roman V. Palagin"'s message of Thu, 2 Apr 1998 14:41:10 +0400 (MSD) References: Message-ID: > Hello. > > I just read 'How to join the 6bone' page, and 'steel unclear about > anything' :). I've only one question - where i can find step-by-step guide > about joining 6BONE? What should I do first? Hi Roman You should find a 6bone provider willing to connect to you. The provider will give you an address space and a router to which you can tunnel your packets. If you want, we are willing to host you, although the connection is bad (40-50% packet loss, avg rtt 3-4s). If you have better connectivity to other 6bone sites, you should probably get a 6bone connection elsewhere. Regards Lalle From romanp@wuppy.rcs.ru Thu Apr 2 14:26:52 1998 From: romanp@wuppy.rcs.ru (Roman V. Palagin) Date: Thu, 2 Apr 1998 18:26:52 +0400 Subject: Using FreeBSD-current on 6BONE Message-ID: <006001bd5e43$6195d0f0$fd01a8c0@r49s.wuppy.rcs.ru> HELP!!! Can somebody send me sample configuration files for INRIA IPv6 with _detailed_ explanations how to setup IPv6-IPv4 tunnel. Thanx From sdaknis@CS.WM.EDU Thu Apr 2 16:13:15 1998 From: sdaknis@CS.WM.EDU (Steven Daknis) Date: Thu, 02 Apr 1998 11:13:15 -0500 Subject: How I can Join 6BONE? In-Reply-To: Your message of "Thu, 02 Apr 1998 14:41:10 +0400." Message-ID: <199804021613.LAA00261@tx.cs.wm.edu> I echo Roman Palagin's question. Does a step by step guide exist for us newbies??? thank -- STEVE DAKNIS SENDS sdaknis@cs.wm.edu or daknii@compuserve.com http://www.cs.wm.edu/~sdaknis/sdaknis.html From WatsonROB@mail.dec.com Thu Apr 2 16:26:16 1998 From: WatsonROB@mail.dec.com (Robert Watson - VBE) Date: Thu, 2 Apr 1998 17:26:16 +0100 Subject: DIGITAL-BE Site Route Problems Message-ID: <199804021812.NAA12106@mail12.digital.com> Jim, 6bone folks I've been working on the routing problem caused by the DIGITAL-BE site. Both the routers at DIGITAL-BE (from different vendors) seemed to have incorrect config's which were allowing routes they received from my site at DIGITAL-ETC and other places to leak back out to the 6Bone via SURFNET. Both these config's have been changed (thanks BB for your help there). One was done yesterday (1st April) and the other this morning at about 0930 CET. Hopefully the changes will be reflected in tomorrow's report from Merit. Looking at the routing tables today via the G6 and CSELT web sites it appears the errant routes have disappeared. It took some time to purge them out of the system but I cannot see any now. I'll check tomorrow morning when the new merit report comes out. Sorry for the delay in getting to fix this. The owner for the DIGITAL-BE site is Guido.Remans@digital.com . Guido has only taken over recently but is now running things. Apologies to all for the bother - I guess this is what "test" networks are for... Bob Robert (Bob) Watson Internet: WatsonRob@digital.com DTN: 828-5142 Extn: +33 (0)4 92 95 5142 Fax: +33 (0)4 92 95 6235 Home: +33 (0)4 93 44 0410 Mobile: +33 (0)6 14 73 3881 Digital Equipment European Technical Center 950, Route des Colles - BP027 - 06901 Sophia Antipolis CEDEX - FRANCE ---------- From: bound@zk3.dec.com [SMTP:bound@zk3.dec.com] Sent: 01 April 1998 18:12 To: 6bone@ISI.EDU Subject: DIGITAL-BE Site Route Problems Folks, This site was causing router problems and it has been reported. The person maintaining this site has left the company and things got messed up. Digital is fixing this one way or the other now. For the future on the 6bone Cabletron and Digital are now separate eng'g groups for this kind of testing. So if your running a Cabletron Routabout please make sure you have connection to them. It is the same folks, just the name has changed. Also our backbone site at DIGITAL-CA is running a Cisco for IPv6 Routing. thanks /jim From PAUL.V.MAGGITTI@cdev.com Thu Apr 2 18:44:00 1998 From: PAUL.V.MAGGITTI@cdev.com (Paul V Maggitti) Date: 02 Apr 1998 12:44:00 -0600 Subject: Request for using FreeBSD-current with IPv6/IPv4 tunneling Message-ID: <"069523523DC70001*/c=us/admd= /prmd=ceridian/o=cdev/ou=cc-lan/ou=cchsgate/s=MAGGITTI/g=PAUL/i=V/"@MHS> --PART.BOUNDARY.quasar.6953.3523dc71.0001 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline If somebody answers the e-mail below, please send me the same configuration files. Thanks. Paul Maggitti ---------------------- Forwarded by Paul V Maggitti/CDev/Ceridian on 04/02/98 12:42 PM --------------------------- (Embedded image moved to file: PIC001.PCX) romanp @ wuppy.rcs.ru at Internet on 04/02/98 11:51:00 AM To: 6bone @ ISI.EDU at Internet@CCMAILEXCHANGE cc: (bcc: Paul V Maggitti/CDev/Ceridian) Subject: Using FreeBSD-current on 6BONE HELP!!! Can somebody send me sample configuration files for INRIA IPv6 with _detailed_ explanations how to setup IPv6-IPv4 tunnel. Thanx --PART.BOUNDARY.quasar.6953.3523dc71.0001 Content-Type: application/octet-stream Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=PIC001.PCX Content-Description: PIC001.PCX FTBP-Modification-Date: 02 Apr 1998 18:43:00 Z FTBP-Object-Size: 2427 CgUBCAAAAABoACwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAABaQABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAD1E9sTzRPHE8MTwhP1E9sTzRPHE8MTwhP1E9sTzRPHE8MT whP1E9sTzRPHE8MTwhP1E9sTzRPHE8MTwhP1E9sTzRPHE8MTwhP1E9sTzRPHE8MTwhP1E9sT zRPHE8MTwhP1E9sTzRPHE8MTwhPwEwzIBgzYE8wTxhPDE8IT7hPOBtcTzBPGE8MTE+wTwgbC BwbCEgbCEgbCEsUG1hPLE8YTwxMT6hMMwgYHwgLCAwISwgfEEsMCwwbVE8sTxRPDExPpE8MG AwcCBwMCwhLDB8ISwgISwgLDBtUTyhPFE8MTE+gTwgIHA8ICEw4DDgLDE8USwwLCEMIG1BPK E8UTwxMT5xMCAwcDAg4TDgITwgISD8ISD8ISBRICEcICwwbUE8oTxRPCExPmEwYCBwMCDgIO wgLDExITEhPCEg8GxgLDBtMMDAfJE8QTwhMT5hMGwwITBgMCDhLFEw8SE8ISBgIDwhIDEsMG B9MDxwwHxRPDExPlEwYHAhESAg8CwhMPwhMPxBMPxRIQwgIDAgMCBtMDxwPEDAfDE8IT4RMH wwzCBgLCEhMCDxLIE8MSD8MSwwIQAwIDBgfSDMkDwgPCDAfCExPbEwfGDMIDDAIHERITEhMS wxMPwxMPwxPDEgIDAgMCwwMCBgzREwfHDMYDDMITE9YTB8UMyAMGB8ICBhLDAsYTEhMSExIP whIHAgcCAwUQAgYRBgfSE8UTB8QMwgMMwhMT0hMHxAzLA8IMBsISDxESExITAw4DxBMSExIT wxICBwPCAsMDDMIGB9ITyRMHwwzCExPPEwfDDMkDxQwHwhMGBxITAhECEwMOAg7DExITDxMP wxIDAgMCBwMCDAYRBgfSE8kTwhPCDMITE8wTB8MMxwPEDMIHxxMGxBLDAg4DDgIGwg/IEgID wgIDAgwCEMIGB9ITyRMHDAcMwhMTyhMHwgzGA8MMwgfMEwYHwhLCEAIOAg4CDhDDAhIPxhIF AgXDAgUCEQYH0hPHEwfCDAcPDMITE8gTB8IMxQPDDAfQEwbDEhDEAhAOEA4QwgLGEgcSBhIG BcMCBcIGB9ATB8UMEwfCDA8HDwwHwhMTxhMHwgzEA8MMB9MTBgfCEhADEMICDhAOEMICEQID xxIGBwbCAgUCEQYHyxMHxAwHwhMHEwzCEwcPBw8MB8MTE8UTBwzEA8IMB9YTBsQSEAMCA8UC EQIDAgPDEgcSBgfCBgUQAhDCBgfGEwfEDAfGE8INEwzCEw8HwgwHwxPCE8QTBwzDA8IMB9gT BgfEEhACEMYCEQIDAsQSBhLDBsICEALCBgfCEwfDDAfKEwfCDRMHwhPCDAfEE8ITE8MTBwzC A8IMB9oTDBIHwxLDDBEDxQIDAgPDEgYSBgfCBgIQAhAGDAfCEwzDE8MHyRMHwhPCBxMHxRPD ExPDEwzCAwwH3RMGxxICEQPDAgMCA8MSBhIGBwYMBhACEAIGDMMTDBPCB8YTwwfHEwfGE8MT whPDEwwDDAfeEwYHxxICEQPDAgMCwhIGEgYHBgwGEAIQAsIGB8MTDMYTwwfKEwzGE8MTwhPD E8IMB98TDBLCB8USAgMRxAISB8ISBgcGDAYQBhAGEAYMB8MMB8kTwwfHEwzGE8MTwhPDEwwP wgzfEwYSB8ISB8ISAhECAwIDEgcSBwYHBgwGEAYQxgzDD8IHxRPDB8kTBwzGE8MTwhPDEwzD D8QM3BPCBhIGwxIGAhECAwIHBgcGyAzJDxMHzRMHwwwHxxPDE8ITwxMHDMYPxwwH1BMGEgYS BhLLDM4PwwwTDMcTwgfEDAfJE8QTwhMTxBMHwgzLD9sM0w/GDAfDEwzDEwfEDAfLE8YTwxMT xhMHxAztD8gMBgfIE8QMB84TxxPDE8ITyhMHxwzbD8sMEAUMBcIMwgYH1RPKE8UTwxMT0RMH 2wwGEAYQBhACBQwFDAUMBgwHBgfWE8sTxRPDExPuEwYMBhAGEAIGDAYMwwYH1xPLE8YTwxMT 8BPKBgfYE8wTxhPDExP1E9sTzRPHE8MTwhP1E9sTzRPHE8MTwhMMAAAAgAAAAIAAgIAAAACA gACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAA gIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAA gAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP// ////AAAAgAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD/ /wD/AP//////AAAAgAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A //8AAAD//wD/AP//////AAAAgAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA /wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vw oKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAAgIAAAACAgACAAICAwMDAwNzA psrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAAgIAAAACAgACAAICA wMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAAgIAAAACA gACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAAgAAAAIAA gIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP//////AAAA gAAAAIAAgIAAAACAgACAAICAwMDAwNzApsrw//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP// ////AAAAgAAAAIAAgIAAAACAgACA//vwoKCkgICA/wAAAP8A//8AAAD//wD/AP////// --PART.BOUNDARY.quasar.6953.3523dc71.0001-- From jan.novak@aliatel.cz Fri Apr 3 07:59:55 1998 From: jan.novak@aliatel.cz (Jan Novak) Date: Fri, 3 Apr 1998 09:59:55 +0200 Subject: How I can Join 6BONE? Message-ID: <01BD5EE7.4284D5E0@novak_j.eng.aliatel.cz> I do not see to be problem to find people willing to connect somebody to 6bone, but, PLEASE, where is somebody knowing somewhat about IPv6 software to Cisco routers - I contacted local distributors of Cisco, they contacted TAC Brussels, I contacted directly Cisco according to 6bone www page contacts without any response yet...... Any hints appreciated -) ... Thanks Jan > Hello. > > I just read ?How to join the 6bone' page, and ?steel unclear about > anything' :). I've only one question - where i can find step-by-step guide > about joining 6BONE? What should I do first? Hi Roman You should find a 6bone provider willing to connect to you. The provider will give you an address space and a router to which you can tunnel your packets. If you want, we are willing to host you, although the connection is bad (40-50% packet loss, avg rtt 3-4s). If you have better connectivity to other 6bone sites, you should probably get a 6bone connection elsewhere. Regards Lalle From chk@eng.bellsouth.net Fri Apr 3 20:29:47 1998 From: chk@eng.bellsouth.net (Christian Kuhtz) Date: Fri, 3 Apr 1998 15:29:47 -0500 Subject: UUNET contact for 6bone Message-ID: <19980403152947.55761@delirium.eng.bellsouth.net> Hello: I was wondering whether the 6bone contact for UUNET happens to be listening and would mind getting in touch with me.. Any pointers to designated stuckies welcome as well. ;-) Thanks in advance! Best regards, Chris -- Christian Kuhtz (770) 522-4000 BellSouth.net Sr. Network Architect I speak only for myself, and my opinion belongs to me. Atlanta, GA, U.S. From rlfink@lbl.gov Fri Apr 3 21:30:49 1998 From: rlfink@lbl.gov (Bob Fink) Date: Fri, 03 Apr 1998 13:30:49 -0800 Subject: UUNET contact for 6bone In-Reply-To: <19980403152947.55761@delirium.eng.bellsouth.net> Message-ID: <1320512211-13535945@cnrmail.lbl.gov> Christian, At 03:29 PM 4/3/98 -0500, Christian Kuhtz wrote: > >Hello: > >I was wondering whether the 6bone contact for UUNET happens to be listening >and would mind getting in touch with me.. > >Any pointers to designated stuckies welcome as well. ;-) Use the 6bone registry whois service for uunet-uk, and you will see the following person record: person: Guy Davies address: UUNET (UK) address: Internet House address: 332 Cambridge Science Park address: Milton Road address: Cambridge address: CB4 4BZ address: UK phone: +44 1223 250122 fax-no: +44 1223 250133 e-mail: guyd@uk.uu.net nic-hdl: GD31-RIPE mnt-by: AS1849-MNT changed: guyd@uunet.pipex.com 960715 changed: guyd@uk.uu.net 19970609 source: RIPE Bob From rlfink@lbl.gov Mon Apr 6 17:13:27 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 06 Apr 1998 09:13:27 -0700 Subject: pTLA request from Greek Research NETwork Message-ID: <1320268432-27985338@cnrmail.lbl.gov> 6bone folk: I have received the following pTLA request from Yiorgos Adamopoulos representing the Greek Research NETwork (GR-NET). They have responded to all my pTLA rules and I am thus soliciting comments from the list before assigning this pTLA. It appears to me to be a fully qualified request and am inclined to issue the pTLA unless hearing sound reasons to the contrary. Anyway, please respond to either me or the list with any comments prior to close of business April 10. Thanks, Bob ==================================== Date: Thu, 2 Apr 1998 18:47:07 +0300 From: Yiorgos Adamopoulos To: rlfink@lbl.gov Cc: Yiorgos Adamopoulos , Costas Troulos , Dimitris Kalogeras , pssara@duth.gr Subject: pTLA request Dear Bob, Reagrding the assignment of a pTLA, I hereby send you the answers for your questions, on behalf of the GRNET-NOC. -- 1. Must have experience with IPv6 in the 6bone, at least as a leaf site and preferably as an NLA transit under a pTLA. I am writing this letter to request a pTLA. The Greek Research NETwork (GR-NET hereafter) through its member the Demokritos University of Thrace (duth.gr) has served as a leaf node. Major experience was gained through constant interaction with various aspects of IPv6 (tunnelling, routing etc.). We will use Cisco routers, Sun and HP workstation, and PCs with various Unix flavors. GR-NET intends to deploy a large base of IPv6 networks in major (~ 25) Greek universities and technical education institutes. The appropriate funds have been granted through a research programme of ministry of education. We will build two tunnels, one with Cselt/IT and the other with BTLABS/UK thus utilizing our Internet connections (10 Mbps with TEN-34 @ Italy and 2 Mbps with BT @ NL). 2. Must have the ability and intent to provide "production-like" 6bone backbone service to provide a robust and operationally reliable 6bone backbone. GR-NET is the Greek National Research & Technology Network, providing Internet services to the Academic and Research community. It is a project recently launched by the General Secretariat for Research and Technology (GSRT), the government agency responsible for the coordination and development of research and technology activities in Greece. Co-funded by the European Union, GR-NET is included in the 2nd Framework Support Programme, with a budget of 5.000.000 ECUs for 3 years. GR-NET interconnects Universities and Research Centers in Greece, as well as the Research Departments of relevant organisations. It provides high-speed reliable interconnection among the above as well as international Internet connectivity via two lines: · a 10 Mbps line to Italy (IP over ATM), · a 2 Mbps line to Amsterdam, GR-NET participates in the European Organisation DANTE that interconnects European academic and research networks as well as in the TEN-34 project. TEN-34, is a consortium of European Union research networks funded by the Telematics Applications Programme and Information Technologies of DG XIII that interconnects European academic and research networks at high speeds (from 10 Mbps to 34 Mbps). GR-NET topology includes, at the first phase, network nodes in 6 major greek cities, that is, Athens, Thessaloniki, Patras, Ioannina, Xanthi and Heraklion. The main gateway is located in the greek PTT's building in Athens, consisting of two interconnected routers. GR-NET also administers the Athens Internet eXchange (AIX) which interconnects the major ISPs of Greece. In this way GR-NET can expose the Greek Internet community (except from the academic one) to the new era of IPv6. GR-NET is also a regional (Southeast branch of Europe and Mediterranean) provider by interconnecting the academic Bulgarian and Cyprus networks. Israel, Lebanon and other national academic research networks are about to get connected. 3. Must have a potential "user community" that would be served by becoming a pTLA, e.g., the requester is a major player in a region, country or focus of interest. GR-NET interconnects the academic communities of Greece, Cyprus and Bulgaria. The user community currently served is about 500.000 students and researchers in Greece only. (data taken from a recent survey ). 4. Must commit to abide by whatever the 6bone backbone operational rules and policies are . We state that GR-NET will commit to the operational rules of IPv6 now and in the future. GR-NET as Local Internet Registry (LIR) assigned from RIPE follows the principles of Internet Registry (cautious management of Internet resources i.e. addresses and route aggregation). Through this activity GRNET has increased interaction with the academic community. GR-NET will inform the academic community about the current and future principles of IPv6 (i.e address allocation). -- If you need any futher clarification on any of the above (or even other) questions, we'd be more than happy to answer them. This email is also sent to: Dr. Dimitrios Kalogeras (GRNET-NOC routing / Network Manager) Mr. Costas Troulos (GRNET / NTUA NOC IPv6 contact) Mr. Panagiotis S. Saragiotis (DUTH Network Manager) Relevant URLs that can serve as apendices to this application are: http://www.grnet.gr/ http://www.grnet.gr/aix/ http://www.gsrt.gr/ http://www.duth.gr/ On behalf of the GRNET-NOC, -- Yiorgos Adamopoulos -- #include mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE -end From rlfink@lbl.gov Mon Apr 6 17:18:48 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 06 Apr 1998 09:18:48 -0700 Subject: How I can Join 6BONE? In-Reply-To: <01BD5EE7.4284D5E0@novak_j.eng.aliatel.cz> Message-ID: <1320268111-28004648@cnrmail.lbl.gov> Jan, At 09:59 AM 4/3/98 +0200, Jan Novak wrote: >I do not see to be problem to find people willing to connect somebody to 6bone, but, PLEASE, >where is somebody knowing somewhat about IPv6 software to Cisco routers - I contacted >local distributors of Cisco, they contacted TAC Brussels, I contacted directly Cisco according >to 6bone www page contacts without any response yet...... It is my understanding that Cisco is limiting their current field test version of IPv6 to certain established large sites and their collaborators. Thus it seems the way to get this code for 6bone use it to find one of these sites and become a collaborator with them so they arrange for you to get the code. I would appreciate any comment from a knowledgeable Cisco IPv6 site on this issue. Thanks, Bob From seidmann@dcs.elf.stuba.sk Tue Apr 7 11:20:07 1998 From: seidmann@dcs.elf.stuba.sk (Thomas Seidmann) Date: Tue, 07 Apr 1998 12:20:07 +0200 Subject: New country Message-ID: <3529FDD7.570A940@dcs.elf.stuba.sk> Hello, I am pround to announce the presence of a new country on the 6bone - Czech Republic. The site CODALAN is connected through STUBA for now and its ipv6-site object is already in the 6bone registry under the same name. Regards, Thomas -- ========================================================== Dipl.-Ing. Thomas Seidmann Department of Computer Science and Engineering Slovak University of Technology in Bratislava mailto:seidmann@dcs.elf.stuba.sk Tel +421.7.60291153 ========================================================== From rlfink@lbl.gov Tue Apr 7 15:52:26 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 07 Apr 1998 07:52:26 -0700 Subject: New country In-Reply-To: <3529FDD7.570A940@dcs.elf.stuba.sk> Message-ID: <1320186893-32890787@cnrmail.lbl.gov> Thnomas, At 12:20 PM 4/7/98 +0200, Thomas Seidmann wrote: >Hello, > >I am pround to announce the presence of a new country on the 6bone - >Czech Republic. The site CODALAN is connected through STUBA for now and >its ipv6-site object is already in the 6bone registry under the same >name. Good news indeed! I have added CZ to the country code list on the country web page. Tomorrows country scan of the 6bone registry should see CZ appear in the actual discovered country list. Thanks for letting us know, and welcome to CODALAN and CZ. Bob From lee_y@cs.unr.edu Tue Apr 7 20:40:49 1998 From: lee_y@cs.unr.edu (Yajie Lee) Date: Tue, 7 Apr 1998 12:40:49 -0700 (PDT) Subject: V6 address Message-ID: Anybody there can tell me his/her host's v6 address(es) so I can use them to test my machines? Or where I can find that information? thanks, Yajie From rlfink@lbl.gov Tue Apr 7 22:01:39 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 07 Apr 1998 14:01:39 -0700 Subject: V6 address In-Reply-To: Message-ID: <1320164737-34223579@cnrmail.lbl.gov> Yajie, At 12:40 PM 4/7/98 -0700, Yajie Lee wrote: > > >Anybody there can tell me his/her host's v6 address(es) so I can use them >to test my machines? Or where I can find that information? If you want to join the 6bone you will eventually be able to participate in IPv6 testing, but as a generality you don't just get an address to test to the way you seen to be asking. Bob From lalle@sics.se Wed Apr 8 09:59:15 1998 From: lalle@sics.se (Lars Albertsson) Date: 08 Apr 1998 10:59:15 +0200 Subject: New country In-Reply-To: Bob Fink's message of Tue, 07 Apr 1998 07:52:26 -0700 References: <1320186893-32890787@cnrmail.lbl.gov> Message-ID: Speaking of new countries, we have a tunnel to Lithuania, although I don't think they have registred in the 6bone registry yet. Lalle > >I am pround to announce the presence of a new country on the 6bone - > >Czech Republic. The site CODALAN is connected through STUBA for now and > >its ipv6-site object is already in the 6bone registry under the same > >name. > > Good news indeed! I have added CZ to the country code list on the country > web page. Tomorrows country scan of the 6bone registry should see CZ > appear in the actual discovered country list. > > > Thanks for letting us know, and welcome to CODALAN and CZ. > > Bob > From rlfink@lbl.gov Thu Apr 9 22:39:43 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 09 Apr 1998 14:39:43 -0700 Subject: draft minutes of ngtrans wg meeting at LA IETF - 9Apr98 version Message-ID: 6bone & ngtrans folk, Here is our first draft of the ngtrans minutes from the LA IETF. Please send me any comments by the 20th. Thanks, Bob ________________________________________________________________________ ________________________________________________________________________ ngtrans WG meeting March 31, 1988 Los Angeles, CA IETF Chairs:       Bob Fink rlfink@lbl.gov               Robert Gilligan gilligan@freegate.com               Tony Hain tonyhain@microsoft.com Reported by Bob Gilligan, Alain Durand and Bob Fink ________________________________________________________________________ ngtrans tools portion of meeting, chaired by Tony Hain Discussion:   ngtrans@sunroof.eng.sun.com Subscribe:    majordomo@sunroof.eng.sun.com  "subscribe ngtrans" Archive: ftp://playground.sun.com/pub/ngtrans> ftp://playground.sun.com/pub/ngtrans Web site: http://www.6bone.net/ngtrans.html>http://www.6bone.net/ngtrans.html ____ AIIH I-D- Jim Bound Jim Bound gave an overview on his new Internet-Draft titled "Assignment of IPv4 Global Addresses to IPv6 hosts (AIIH)".  Note that the acronym for this proposal has changed from NNAT to AIIH.  This Internet-Draft replaces the earlier NNAT I-D. The general objective of this proposal is to allow IPv6/IPv4 dual hosts configured with permanent global IPv6 and get temporary assignments of IPv4 global addresses to use when communicating with IPv4 hosts.  This conserves the IPv4 address space since a small pool of global IPv4 addresses can be used by a larger number of IPv6/IPv4 hosts.  This proposal does NOT employ header translation. The proposal uses an "AIIH server" situated at the boundary between an IPv4 and an IPv6 cloud which operates both as a DNS and DHCP server. The AIIH server handles IPv4 DNS queries for IPv6/IPv4 hosts; assigns temporary IPv4 addresses to IPv6/IPv4 hosts, and manages tunnels to IPv6/IPv4 hosts.  The IPv6/IPv4 hosts use DHCP to acquire their temporary IPv4 addresses.  Two cases of communication are handled:    1)   IPv6/IPv4 host initiating communication with an IPv4 host.    2)   IPv4 host initiating communication with an IPv6/IPv4 host. IPv4 packets between the IPv6/IPv4 host and the AIIH server can be carried in three forms:    1)   Tunneled in IPv6.    2)   Tunneled in IPv4.    3)   Carried as native IPv4 packets. More details on this proposal can be found in Jim's slides are located at: ftp://sipper.zk3-x.dec.c om/pub/aatn_aiih_0498.zip ftp://sipper.zk3-x.de c.com/pub/ngtrans_aiih_0498.zip A few questions were raised in the discussion of this proposal:    -    Someone asked what specific changes an IPv6 host implementation         would need to make in order to implement AIIH.  Jim said that         the primary change would be adding the facility to acquire an         IPv4 address via DHCP when needed. Jim would like feedback on this proposal now.  He plans on releasing an updated version of this document before the Chicago IETF meeting. ____ NAT-PT I-D- George Tsirtsis & Pyda Srisuresh George Tsirtsis presented his new Internet-Draft titled "Network Address Translation - Protocol Translation (NAT-PT)".  This is a revision of his earlier I-D of the same name.  This draft adds a lot of new material and is about 3 times larger than the old version. The general objective of this proposal is to allow areas of IPv6-only nodes, or IPv6/IPv4 dual nodes using only IPv6 addresses (no IPv4 addresses), to be deployed.  This would allow sites to achieve the benefits of converting a site completely to IPv6, avoiding the need to maintain and administer IPv4 throughout the site. The proposal employs techniques analogous to IPv4 NAT and port translation to allow IPv6 nodes to communicate with IPv4 nodes.  It envisions NAT-PT translator nodes being deployed at the borders of IPv6 networks.  The same technique could be used for stub dual IPv6/IPv4 networks, or stub IPv4 networks. The NAT-PT translator nodes perform stateful header translation between IPv4 and IPv6, basing the translation on mappings between IPv6 addresses and IPv4 addresses that are generated on the fly (in response to traffic) or in response to DNS queries.  The translators may manage pools of IPv4 addresses that are used for these mappings. Additionally, they may intercept and translate DNS queries and replies. Changes to the I-D in this version include:    -    Extended to allow the use of any prefix    -    Added some new DNS interactions    -    Added support for port translation    -    Merged in the header translation mechanisms from Erik Nordmark's         SIIT Internet-Draft The presentation walked through three different scenarios: one case of an IPv6 node initiating communication with an IPv4 node, and two cases of an IPv4 node initiating communication with an IPv6 node. More details of the proposal can be found in George's slides at: ftp://ftp.labs.bt.com/ pub/tsirtsg/41-IETF-NATPT.zip Several issues were raised in the discussion that followed:    -    Tony Hain pointed out that the document needs to discuss         applicability of this technique (what types of sites could use         it, what types should not), and also needs to discuss scaling         issues.    -    Brian Carpenter suggested that the group needs to consider how         this technique would combine with the various other transition         techniques, and API issues it raises.    -    Concern was raised about the translation of DNS queries and         replies.  It was not clear whether this could be made to work         with signed DNS queries/replies. ____ SMTP issues in IPv4/v6 environment - Kazuhiko Yamamoto A presentation of SMTP use in dual-stack environments was given by Kazu Yamamoto of the WIDE project.  The WIDE project now has dual IPv4/IPv6 stack MTAs ready for testing, and thus experimented with registering MX records for IPv6 MTAs and what happens to IPv4 only MTA servers. Results were that IPv4-only Sendmail/Bind has no problem with AAAA records(Sendmail 5.61 or later and Bind 4.8.3 or later), but when MX records were used which refer to A and AAAA records there were problems.  Further experimentation is planned and will be reported as appropriate. (chair's note:  this work probably falls more under the 6bone rather than the tools portion of ngtrans, thus will be scheduled there in the future.) ________________________________________________________________________ ngtrans 6bone portion of meeting, chaired by Bob Fink Discussion:   6bone@isi.edu (6BONE Mailer) Subscribe:    majordomo@isi.edu "subscribe 6bone" Archive:      http://www.ipv6.nas.nasa.gov/6bone/ Web site:     http://www.6bone.net ____ 6bone Status report - Bob Fink & David Kessens A brief status of the 6bone was given by Bob Fink of ESnet and David Kessens of ISI.     240 sites in 32 countries     14 host and 14 router implementations (probably more at this time)     45 sites participating in the 6bone backbone     site, routing and address delegation done thru 6bone registry at ISI       courtesy of David Kessensof ISI       some new RPSL features in use on the registry     maps and many statistics automatically made up from 6bone registry       courtesy of Andrew Scott of Lancaster Univ.     reverse DNS registry courtesy of Bill Manning of ISI ____ 6bone routing issues I-D - Bertrand Buclin & Alain Durand A presentation was made of was made.  This I-D is based on the following routing principles: The 6bone is a hierarchical network with     backbone sites acting as pseudo TLAs (pTLAs)     pseudo NLAs (pNLAs) providing transit services below pTLAs     leaf sites pTLAs MUST use BGP4+ between them Multihomed sites SHOULD use BGP4+ Leaf sites MAY use default routing Aggregation MUST be performed by border routers     Specially true for pTLAs There are a set of rules for     Link Local prefixes     Site Local prefixes     Special case prefixes     Multicast prefixes     IPv4 mapped prefixes     IPv4 compatible prefixes     Undefined Unicast prefixes     Default routes     Aggregation and advertisement issues     Inter site links This document will be revised based on minor comments and recirculated. ____ 6bone routing reports and related issues - Masaki Hirabaru A presentation of the new Merit 6bone Routing Reports was given by Masaki Hirabaru of Merit.  These reports are collected by an MRT routing daemon and processed with the IPMA statistics tool.  An email list for the daily reports is available that gives the size of the 6bone routing table, how many unique AS's are in use, how many BGP4+ announcements, withdrawals and unique routes there are, a list of the most poorly aggregated announcments and the top five most active prefixes.  A route flap graph is also available. Initial use of the tool shows too many routing changes for so few routes, thus indicating possible routing software/protocol problems.  The reports can also be used to encourage aggregation and detect incorrect configurations. Feedback on, and use of, these reports is encouraged. The reports can be subscribed to by sending email to majordomo@merit.edu with "subscribe 6bone-routing report" in the message.  A hypemail archive is available at:     http://www.mer it.edu/mail.archives/html/6bone-routing-report The Rout Flap Graph is at:     http://www.mer it.edu/mail.archives/~ipma/java/FlapGraph.html ____ Multihomed routing domain issues for IPv6 aggregatable scheme I-D - Francis Dupont A presentation was made of current ideas for handling IPv6 site multihoming by Francis Dupont of Inria.  A one hour session on this topic was held in the hour preceding this ngtrans meeting.  There are several different approaches possible to this problem, several of which share problems and solutions with IPv4. Bob Fink noted that this work may best be done under the Routing Area to encourage wider participation in the discussion and solutions for site multihoming, a path he has agreed to pursue with the head of the Routing Area. ____ 6bone transit through CAIRN - Maryann Maher A brief overview was given of Allison Mankin's CAIRN native IPv6 6bone backbone proposal by Maryann Maher of ISI-East.  In brief, the CAIRN project is willing to provide native IPv6 backbone service across the US, on a testing use basis, from CAIRN's points of prescence at LBL, ISI-West, MCI, ISI-East and UCL. ____ IPSEC proposition - Maryann Maher Maryann maher of ISI-East presented Allison Mankin's request to the 6bone project that IPSEC AUTH functionality be required in 6bone routers by the end of the year. Though there was a sense of agreement that it was appropriate for the 6bone to push the development and testing of security for routers, there was also a bit of confusion of just what was meant by this proposal.  Bob Fink will request Allison to make a specific proposal that can be considered on the mail list. ____ Win-NT IPv6 public source - Richard Draves A short presentation of the new Windows NT IPv6 implementation by Microsoft Research was given by Richard Draves of Microsoft.  He noted that this work was also being supported by Allison Mankin's group at ISI-East. The source and binary release was made on March 24, 1988, and can be retrieved from:     http://www.research.microsoft.com /msripv6 It is being released to promote research, education and testing, and is not intended for commercial use.  There is no support for Windows 95 or 98.  It is copyrighted and distributed under a license.  Richard specifically encouraged those with troubles agreeing to the license to contact him to see if something mututally agreeable can be arranged. Richard noted that, although it was released for NT version 4, he had been able to easily run it on NT version 5 as well, though he needed to make an installation procedure change. Initially the following works: BaSic IPv6 header processing Neighbor Discovery Stateless autoconfiguration Partial ICMPv6 (basically ping support, but not error messages) Partial Multicast Listener Discovery Automatic and configure tunnels IPv6 over IPv4 per the Carpenter/Jung draft UDP and TCP over IPv6 ping, traceroute, ttcp, ftp/ftpd, NetMon What's missing: Security and Auth headers Mobility support Routing Applications as follows   Web client/server   File client/server (i.e., Microsoft Networking)   DNS client/server v6/v4 translation ____ pTLA asignment rules - Bob Fink Delayed to an informal lunchtime meeting the day after the ngtrans meeting. When presented to the lunchtime group, there was no further comment on the pTLA assignment rules presented by Bob Fink of ESnet, other than that some folk are unwilling to say a site cannot do something.  Bob noted that these rules have been presented before on the 6bone list and that he will continue to require new pTLA requestors to respond to the four criteria, to the list, so general sentiment can be heard.  He will then make a decision based on the requestor's response and the sentiment expressed. Bob encouraged those that do not like any particular policy he is enforcing to comment to him directly or to the list. ____ steps to clean up the backbone - Bob Fink Delayed to an informal lunchtime meeting the day after the ngtrans meeting. Bob Fink of ESnet presented some of his problems and possible solutions about the 6bone backbone and its general cleanup: Various problems – reliability – old addresses in use – invalid tunnels – routing loops – non BGP4+ peering – incomplete registry info – no address delegation through the registry Various solutions – enforcing registry rules (e.g., if no correct entry no listing shown) – pulling pTLAs for sites not providing good service or incomplete and inaccurate registry entry – publish top ten “worst site” list – various tools to show what doesn’t work Alain Durand then spoke in favor of terminating pTLA sites that were not following various rules as expressed in the 6bone routing issues I-D.  Several folk (Bertrand Buclin, Guy Davies and others) spoke against the harsh enforcement of rules as being inappropriate for the 6bone and its testing nature. The general consensus seemed to be that report-based enforcement was more appropriate for the 6bone.  Thus a set of rules would be agreed upon (say the Buclin/Durand draft) and reports would target those not complying. It was also agreed that a 6bone-ops list made up of 6bone registry contacts would be a better place for reports than the main 6bone list.  This would also help enforce the use of the registry for participating sites. Bob agreed to publish to the 6bone list a general proposal for a way to start the cleanup process based on discussions from this session. ____ tools to help clean up the backbone - Ivano Guardini - 10 mins Delayed to an informal lunchtime meeting the day after the ngtrans meeting.  Ivano Guardini of CSELT gave a presentation of the new ASpath-tree tool that monitors BGP4+ routing, resulting from work of both Ivano and Paolo Fasano also of CSELT.  This tool provides a graphical view of the BGP4+ routing tree towards the 6bone.  The results are obtained by elaborating the AS path information available in the BGP4+ routing table of an IPv6 border router terminating BGP4+ capable tunnels.  Results are presented automatically as html pages.  See:     http://carmen.cselt.it/ipv6/bgp/ index.html The tools was developed as a set of unix scripts in Perl 5.0, and tested on a Solaris 2.5.1 workstation.  BGP4+ routes are collected using rsh commands, and the current script handles Cisco routers.  Required inputs for the program are:     the 6bone registry database     the 6bone pTLA list Ivano then showed various sample results from a CSELT viewpoint using ASpath-tree.  For future work the following was given:     Automatic detection of BGP4+ routing anomolies       unaggregatedprefixes, wrong prefix advertisements ...     Provide information on BGP4+ routing stability     Use of SNMP for data acquisition     ...and the desire for suggestions from the 6bone community Ivano asked that other pTLA sites install the code, which is available at:     ftp://carmen/cselt.it/pub/ASpath-tree.tar.gz -end From yan@nangka.usc.edu.ph Mon Apr 13 14:39:25 1998 From: yan@nangka.usc.edu.ph (Ryan F. Go) Date: Mon, 13 Apr 1998 21:39:25 +0800 (PST) Subject: V6 address In-Reply-To: <1320164737-34223579@cnrmail.lbl.gov> Message-ID: How do i join 6bone? What will i need ? On Tue, 7 Apr 1998, Bob Fink wrote: > Yajie, > > At 12:40 PM 4/7/98 -0700, Yajie Lee wrote: > > > > > >Anybody there can tell me his/her host's v6 address(es) so I can use them > >to test my machines? Or where I can find that information? > > If you want to join the 6bone you will eventually be able to participate in > IPv6 testing, but as a generality you don't just get an address to test to > the way you seen to be asking. > > > Bob > --- Ryan F. Go Unix/Linux Systems Administrator Center for Network Management and Services http://cnms.usc.edu.ph University of San Carlos http://www.usc.edu.ph Tel: +(6332)-3466268 Fax: +(6332)-3466265 ~~~~~~~~ "Though UNIX is somewhat challenging... at least we are not WIMPS!" ~~~~~~~~ From rlfink@lbl.gov Mon Apr 13 15:13:30 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 13 Apr 1998 07:13:30 -0700 Subject: V6 address In-Reply-To: References: <1320164737-34223579@cnrmail.lbl.gov> Message-ID: <1319670867-63933681@cnrmail.lbl.gov> Ryan, At 09:39 PM 4/13/98 +0800, Ryan F. Go wrote: > > How do i join 6bone? What will i need ? Have you read the 6bone pages? http://www.6bone.net/ If you have, please ask me what is not obvious (I am trying to rewrite the hookup information you see referenced on the 6bone home page): http://www.6bone.net/6bone_hookup.html Regards, Bob From kravietz@ceti.com.pl Mon Apr 13 18:13:20 1998 From: kravietz@ceti.com.pl (Pawel Krawczyk) Date: Mon, 13 Apr 1998 19:13:20 +0200 (MET DST) Subject: V6 address In-Reply-To: Message-ID: On Mon, 13 Apr 1998, Ryan F. Go wrote: > How do i join 6bone? Take a look at www.6bone.net > What will i need ? This depends mostly on what system you are using. For linux there are two excellent HOWTOs: http://www.terra.net/ipv6/ http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html -- Pawel Krawczyk, CETI internet, Krakow. http://www.ceti.com.pl/ info: oferta@ceti.com.pl. Home: http://ceti.com.pl/~kravietz/ From matts@datalight.com Mon Apr 13 18:48:13 1998 From: matts@datalight.com (Matthew Schlegel) Date: Mon, 13 Apr 1998 10:48:13 -0700 Subject: V6 address Message-ID: <002001bd6704$5567d480$029d95cf@matts.datalight.com> From: Bob Fink >Ryan, > >At 09:39 PM 4/13/98 +0800, Ryan F. Go wrote: >> >> How do i join 6bone? What will i need ? > >Have you read the 6bone pages? > > http://www.6bone.net/ > >If you have, please ask me what is not obvious (I am trying to rewrite the >hookup information you see referenced on the 6bone home page): > > http://www.6bone.net/6bone_hookup.html > > >Regards, > >Bob One thing that would be beneficial to add, is links to some of the FAQ and HowTo documents that have been written for the 6bone. I found much of the information provided in the Linux IP6 HowTo documents crucial to getting online. Just a thought, Matthew Schlegel From rlfink@lbl.gov Mon Apr 13 18:58:34 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 13 Apr 1998 10:58:34 -0700 Subject: V6 address In-Reply-To: References: Message-ID: <1319657362-64746001@cnrmail.lbl.gov> Pawel, At 07:13 PM 4/13/98 +0200, Pawel Krawczyk wrote: >On Mon, 13 Apr 1998, Ryan F. Go wrote: > >> How do i join 6bone? > >Take a look at www.6bone.net > >> What will i need ? > >This depends mostly on what system you are using. For linux there >are two excellent HOWTOs: > >http://www.terra.net/ipv6/ >http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html Thanks for letting me know about these. As I redo the 6bone hookup pages I'll add pointers to various sites like this. If anyone knows of others, please let me know. Thanks, Bob From lf@elemental.net Mon Apr 13 20:12:19 1998 From: lf@elemental.net (Lars Fenneberg) Date: Mon, 13 Apr 1998 21:12:19 +0200 Subject: V6 address In-Reply-To: <1319657362-64746001@cnrmail.lbl.gov>; from Bob Fink on Mon, Apr 13, 1998 at 10:58:34AM -0700 References: <1319657362-64746001@cnrmail.lbl.gov> Message-ID: <19980413211219.25913@gimli.elemental.net> Hi all! Quoting Bob Fink (rlfink@lbl.gov): > >http://www.terra.net/ipv6/ If you include this URL on the 6bone pages (at all), please tag it as outdated (last revision was 7/14/97). It contains some good information, but Peter's HOWTO below is much more useful because it almost always reflects the lastest in kernel and application development. > >http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO.html There even is a Japanese and a French translation available! Lars. -- Lars Fenneberg, lf@elemental.net (private), lf@cityline.net (work) pgp fingerprint D1 28 F1 FF 3C 6B C0 27 CC 9C 6C 09 34 0A 55 18 From peterdd@gto.net.om Tue Apr 14 15:40:57 1998 From: peterdd@gto.net.om (peter dawson) Date: Tue, 14 Apr 1998 20:10:57 +0530 Subject: V6 address References: <1320164737-34223579@cnrmail.lbl.gov> <1319670867-63933681@cnrmail.lbl.gov> Message-ID: <35337578.4147E06D@gto.net.om> hi 6bone Folks : Bob Fink wrote: If you have, please ask me what is not obvious (I am trying to rewrite the > hookup information you see referenced on the 6bone home page): > > http://www.6bone.net/6bone_hookup.html > > As the question was asked , I think the following should be included as part of the how to join page, and while being on the subject, as well as part of the 6bone site ! 1) Requirments Spec’s A page dedicated to the RFC listing, both standards and drafts, which basically would be good starting place for interested 6bone implementors/users. I think, one SHOULD do their home work first, but listing is needed !! The 6bone is after all an experimental test bed. 2) Who is providing and howto pointers Links to Vendors email lists/pages who are developing /providing 6bone products/services. An important note, should highlight, that vendor specific enquires should be addressed to those email/vendors AND NOT the 6bone listing. I have seen vendor specific inquires which are not related to the core aspects of 6bone, popping up on this list. 3) Tunnel requisitions , Registry entry , ASN etc how to go about it !! Requirements for setting up Tunnels, (i.e nearest Endpoint with 6bone connectivity, packet loss , avg RTT blah blah blah..etc ). Also, how to refer to the 6bone map to locate the closest endpoint and where to find the lastest 6bone map !, I think that the current how to page is having some info on the registry process, but tunneling is also required. 4) criteria Requirements for obtaining pTLA Correct me if I’m wrong, there are the 3 criteria which make the baseline for obtaining the pTLA. This SHOULD be included somewhere , on the ‘How to join page’ !!! 5) Last but not least, the 6bone mail archive should be updated, the last entry on this list is sometime in Dec of 97 , if I'm not mistaken !! Thats it, for now :)) Pete From rlfink@lbl.gov Tue Apr 14 17:00:34 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 14 Apr 1998 09:00:34 -0700 Subject: V6 address In-Reply-To: <35337578.4147E06D@gto.net.om> References: <1320164737-34223579@cnrmail.lbl.gov> <1319670867-63933681@cnrmail.lbl.gov> Message-ID: <1319575195-69689086@cnrmail.lbl.gov> Peter, At 08:10 PM 4/14/98 +0530, peter dawson wrote: ... > As the question was asked , I think the following should be >included as part of the how to join page, and while being on the >subject, as well as part of the 6bone site ! > > >1) Requirments Spec’s >A page dedicated to the RFC listing, both standards and drafts, >which basically would be good starting place for interested 6bone >implementors/users. I think, one SHOULD do their home work >first, but listing is needed !! The 6bone is after all an >experimental test bed. This is on the official IPng pages and should be the one place this list is kept up. It is referenced on the 6bone web page. >2) Who is providing and howto pointers >Links to Vendors email lists/pages who are developing /providing >6bone products/services. An important note, should highlight, >that vendor specific enquires should be addressed to those >email/vendors AND NOT the 6bone listing. I have seen vendor >specific inquires which are not related to the core aspects of >6bone, popping up on this list. Some of this is also on the IPng pages, some not. I'll think on this one. >3) Tunnel requisitions , Registry entry , ASN etc how to go about >it !! >Requirements for setting up Tunnels, (i.e nearest Endpoint with >6bone connectivity, packet loss , avg RTT blah blah blah..etc ). >Also, how to refer to the 6bone map to locate the closest >endpoint and where to find the lastest 6bone map !, I think that >the current how to page is having some info on the registry >process, but tunneling is also required. Good ideas. I'll factor it in. >4) criteria Requirements for obtaining pTLA >Correct me if I’m wrong, there are the 3 criteria which make the >baseline for obtaining the pTLA. This SHOULD be included >somewhere , on the ‘How to join page’ !!! This is already on my list for inclusion. >5) Last but not least, the 6bone mail archive should be updated, >the last entry on this list is sometime in Dec of 97 , if I'm not >mistaken !! I've asked the NASA guys about this, but no response yet. Meanwhile the ISI mail archive at: ftp://ftp.isi.edu/6bone/6bone.mail is up to date (albeit a large flat file). Thanks for your comments, glad to see someone looks at this stuff :-) Bob From rlfink@lbl.gov Tue Apr 14 19:47:31 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 14 Apr 1998 11:47:31 -0700 Subject: cleanup of 6bone homepage Message-ID: <1319568039-70119241@cnrmail.lbl.gov> 6bone Folk, I have changed the format of the 6bone home page only. This is to accommodate future changes below this page, but for now no content below has been changed. A few links that were getting obsolete are gone. If you have a problem, please let me know. http://www.6bone.net/ (and do a refresh) Thanks, Bob From Yajie Lee Wed Apr 15 04:42:38 1998 From: Yajie Lee (Yajie Lee) Date: Tue, 14 Apr 1998 20:42:38 -0700 (PDT) Subject: Current status or FAQ? In-Reply-To: <9804141327.ZM28019@monkey> Message-ID: Hi Ben, I think you asked some very interesting and important questions which may have a general concern. So I forward it to the 6bone mailing list. Yajie Lee On Tue, 14 Apr 1998, Ben Greear wrote: > > I'm doing some research for my company on IPv6. From what I can tell, > almost everyone has beta versions, but few if any have a fully > functional IPv6 implementation. However, many of the pages I've > been able to find are somewhat dated... > > Does anyone know what version of Solaris will offer built in support > for IPv6 (ie don't have to go download and install something on top > of a current installation..) > > When do you see IPv6 becoming widespread. With the QOS it could > be useful for those trying to do real-time communications, such > as IP telephony etc.... However, unless I misunderstand, it seems > that while IPv6 will work indefinately with IPv4, we will not get > many of the benefits (QOS) untill most or all of the routers > come up to spec. > > Any pointers to any other information would be welcome... > > Thanks, > Ben Greear > From Vince_Grimaldi@BayNetworks.COM Wed Apr 15 17:12:48 1998 From: Vince_Grimaldi@BayNetworks.COM (Vince Grimaldi) Date: Wed, 15 Apr 1998 09:12:48 -0700 Subject: Current status or FAQ? Message-ID: <3.0.32.19980415091247.00a10c8c@sc-mail2.corpwest.baynetworks.com> Yajie, I believe that the version of Solaris where IPv6 is built in is "2.8" At 08:42 PM 4/14/98 -0700, you wrote: > >Hi Ben, > >I think you asked some very interesting and important questions which may >have a general concern. So I forward it to the 6bone mailing list. > > >Yajie Lee > > > >On Tue, 14 Apr 1998, Ben Greear wrote: > >> >> I'm doing some research for my company on IPv6. From what I can tell, >> almost everyone has beta versions, but few if any have a fully >> functional IPv6 implementation. However, many of the pages I've >> been able to find are somewhat dated... >> >> Does anyone know what version of Solaris will offer built in support >> for IPv6 (ie don't have to go download and install something on top >> of a current installation..) >> >> When do you see IPv6 becoming widespread. With the QOS it could >> be useful for those trying to do real-time communications, such >> as IP telephony etc.... However, unless I misunderstand, it seems >> that while IPv6 will work indefinately with IPv4, we will not get >> many of the benefits (QOS) untill most or all of the routers >> come up to spec. >> >> Any pointers to any other information would be welcome... >> >> Thanks, >> Ben Greear >> > > > > Vince Grimaldi Bay Networks Corporate System Engineer - Santa Clara 408 495 2415 (Voice) 408 495 1023 (Fax) From rlfink@lbl.gov Fri Apr 17 16:16:12 1998 From: rlfink@lbl.gov (Bob Fink) Date: Fri, 17 Apr 1998 08:16:12 -0700 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <3.0.2.32.19980417131029.009c5460@dokka.kvatro.no> Message-ID: <1319321491-84951535@cnrmail.lbl.gov> Harald, At 01:10 PM 4/17/98 +0200, Harald Tveit Alvestrand wrote: >Here's a short probe to the list, to see what's going on here.... > >I just did (just for fun) a zone transfer of the reverse lookup tree >under ip6.int. >The result was interesting. > >It didn't take long, and it gave me a number..... 1254 PTR records >in 149 successfully transferred zones. >(About 138 zones failed to transfer) > >Is this a fair ballpark figure for the number of people playing with >IPv6 on the open Internet? There are 249 sites on the 6bone (see http://www.cs-ipv6.lancs.ac.uk/ipv6/6Bone/Whois/) as of yesterday. There are also a fair no. of sites not registered directly with the 6bone registry that are associated with projects like JOIN, G6, WIDE etc, that would have to have reverse entries. This may be another 50 sites (purely my guess). So your nos. aren't far off. As for the large nos. of not responding sites it seems to be the case that people join up to prove they can do it, do a few simple tests, then go inactive. We don't try to discourage this, tho it can be annoying. >(BTW, anyone who wants a list of the 138 zones that I was unable to >zone transfer is welcome to ask...) I would appreciate seing the list of both sets (those that responded and those that didn't). I'm in the process of hardening the 6bone backbone, which mainly consists of getting agreement from backbone sites (see http://www.6bone.net/6bone_pTLA_list.html) to self police based on certain metrics, e.g., routing flaps (merit has some neat reports for us at http://www.merit.net/mail.archives/html/6bone-routing-report/). So I'm always looking for, and at, data such as you just collected. (As an aside we keep the 6bone operational stuff on the 6bone list, but it really doesn't matter as I think that most involved folk are on both.} Thanks, Bob From bc@ecs.soton.ac.uk Fri Apr 17 20:46:14 1998 From: bc@ecs.soton.ac.uk (Ben Crosby) Date: Fri, 17 Apr 1998 20:46:14 +0100 (BST) Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <1319321491-84951535@cnrmail.lbl.gov> Message-ID: > >It didn't take long, and it gave me a number..... 1254 PTR records > >in 149 successfully transferred zones. > >(About 138 zones failed to transfer) How many people prevent unknown AXFR from their DNS ? I guess that my site will be one of those that failed, but we do have correctly registered addresses. Just curious. Ben. From rlfink@lbl.gov Mon Apr 20 15:20:07 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 20 Apr 1998 07:20:07 -0700 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <3.0.2.32.19980420103715.012ffe40@dokka.kvatro.no> References: <1319321491-84951535@cnrmail.lbl.gov> <3.0.2.32.19980417131029.009c5460@dokka.kvatro.no> Message-ID: <1319065649-100342660@cnrmail.lbl.gov> Harald, At 10:37 AM 4/20/98 +0200, Harald Tveit Alvestrand wrote: >OK - the display of data is at http://www.alvestrand.no/ietf/ipv6.html Thanks for making the page, it is easy to look at. >I'm currently refetching the data for the failed zones, which means >that the number of "failed" zones in the listing is low - this will be >OK again within a couple of hours. OK. >Once I find out how I'll include the difference between "failed" sites >and "refusing to AXFR" sites too. Good. Do you mind if I post this via our 6bone pages to help finger point? This might be a good routing sanity check for the 6bone to do daily or weekly or something like that. >Have fun! Always do :-) Thanks, Bob From kml@nas.nasa.gov Mon Apr 20 19:56:12 1998 From: kml@nas.nasa.gov (Kevin M. Lahey) Date: Mon, 20 Apr 1998 11:56:12 -0700 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: Your message of "Mon, 20 Apr 1998 07:20:07 PDT." <1319065649-100342660@cnrmail.lbl.gov> Message-ID: <199804201856.LAA19571@gecko.nas.nasa.gov> In message <1319065649-100342660@cnrmail.lbl.gov>Bob Fink writes >At 10:37 AM 4/20/98 +0200, Harald Tveit Alvestrand wrote: >>OK - the display of data is at http://www.alvestrand.no/ietf/ipv6.html > >Thanks for making the page, it is easy to look at. Yow, should any of the 5fxx: zones still be there? I thought they were retired six months ago, at least. That'd take care of about half of your failed transfers... Do I need to ask to have our entry (5f01:2900::) removed, or will they be removed en mass soon? Thanks, Kevin kml@nas.nasa.gov From bmanning@ISI.EDU Mon Apr 20 20:12:39 1998 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Mon, 20 Apr 1998 12:12:39 -0700 (PDT) Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <199804201856.LAA19571@gecko.nas.nasa.gov> from "Kevin M. Lahey" at Apr 20, 98 11:56:12 am Message-ID: <199804201912.AA25323@zed.isi.edu> > > In message <1319065649-100342660@cnrmail.lbl.gov>Bob Fink writes > >At 10:37 AM 4/20/98 +0200, Harald Tveit Alvestrand wrote: > >>OK - the display of data is at http://www.alvestrand.no/ietf/ipv6.html > > > >Thanks for making the page, it is easy to look at. > > Yow, should any of the 5fxx: zones still be there? I thought > they were retired six months ago, at least. That'd take care > of about half of your failed transfers... > > Do I need to ask to have our entry (5f01:2900::) removed, > or will they be removed en mass soon? > > Thanks, > > Kevin > kml@nas.nasa.gov I'll take that as a request for removal of your zone. -- --bill From 6bone-staff@surfsouth.com Mon Apr 20 20:49:03 1998 From: 6bone-staff@surfsouth.com (6bone-staff@surfsouth.com) Date: Mon, 20 Apr 1998 15:49:03 -0400 Subject: connection request In-Reply-To: <1319065649-100342660@cnrmail.lbl.gov>; from Bob Fink on Mon, Apr 20, 1998 at 07:20:07AM -0700 References: <1319321491-84951535@cnrmail.lbl.gov> <3.0.2.32.19980417131029.009c5460@dokka.kvatro.no> <3.0.2.32.19980420103715.012ffe40@dokka.kvatro.no> <1319065649-100342660@cnrmail.lbl.gov> Message-ID: <19980420154903.19195@surfsouth.com> Hi, all. I'd like to connect to the 6bone. I need the usual: a tunnel attachment, address space (128 addresses or so?), and a mentor. Here's my bio: I neighbor MCI at Pompano Beach and BBN/GTE at Atlanta. I'll be using Cisco equipment for the tunnel endpoint. My AS is 7254, if'n you need it. The machines for tunnel connection would be either 204.70.231.106 (MCI) or 192.221.25.134 (BBN), at your option. Thanks, Chad Miller Surf South NetOps cmiller@surfsouth.com From Harald.Alvestrand@maxware.no Tue Apr 21 08:48:50 1998 From: Harald.Alvestrand@maxware.no (Harald Tveit Alvestrand) Date: Tue, 21 Apr 1998 09:48:50 +0200 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <1319065649-100342660@cnrmail.lbl.gov> References: <3.0.2.32.19980420103715.012ffe40@dokka.kvatro.no> <1319321491-84951535@cnrmail.lbl.gov> <3.0.2.32.19980417131029.009c5460@dokka.kvatro.no> Message-ID: <3.0.2.32.19980421094850.00982600@dokka.kvatro.no> At 07:20 20.04.98 -0700, Bob Fink wrote: > >Do you mind if I post this via our 6bone pages to help finger point? > >This might be a good routing sanity check for the 6bone to do daily or >weekly or something like that. actually I wonder if I should ship you the scripts (there are 2 now, a zonewalker script and a report generator) and have you put them into a cron job at one of the 6bone-related machines. For me this was a one-shot (I was curious); for you this might be useful as a permanent "health check" - perhaps so much so that the people who've blocked zone transfers to me could be convinced to open up the access to you? What do you think? Harald A -- Harald Tveit Alvestrand, Maxware, Norway Harald.Alvestrand@maxware.no From rlfink@lbl.gov Tue Apr 21 16:32:40 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 21 Apr 1998 08:32:40 -0700 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <3.0.2.32.19980421094850.00982600@dokka.kvatro.no> References: <1319065649-100342660@cnrmail.lbl.gov> <3.0.2.32.19980420103715.012ffe40@dokka.kvatro.no> <1319321491-84951535@cnrmail.lbl.gov> <3.0.2.32.19980417131029.009c5460@dokka.kvatro.no> Message-ID: <1318968893-106163468@cnrmail.lbl.gov> Harald, At 09:48 AM 4/21/98 +0200, Harald Tveit Alvestrand wrote: >At 07:20 20.04.98 -0700, Bob Fink wrote: >> >>Do you mind if I post this via our 6bone pages to help finger point? >> >>This might be a good routing sanity check for the 6bone to do daily or >>weekly or something like that. > >actually I wonder if I should ship you the scripts (there are 2 now, >a zonewalker script and a report generator) and have you put them into >a cron job at one of the 6bone-related machines. >For me this was a one-shot (I was curious); for you this might be >useful as a permanent "health check" - perhaps so much so that the >people who've blocked zone transfers to me could be convinced to open >up the access to you? > >What do you think? Yeah, why not send them. Thanks, Bob From MOSTHAVM@plcman.siemens.co.uk Tue Apr 21 10:18:45 1998 From: MOSTHAVM@plcman.siemens.co.uk (MOSTHAVM@plcman.siemens.co.uk) Date: Tue, 21 Apr 1998 10:18:45 +0100 Subject: Registry Message-ID: Hi all, this might be a stupid question, but I am wondering what I have to do to register with the 6Bone. I am already tunneling throug to Netcom UK for a couple of months. My range is 3ffe:1f00:2::0/48 and the entry should be for SIEMENS plc UK. Regards, Marc Mosthav From rlfink@lbl.gov Tue Apr 21 19:13:40 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 21 Apr 1998 11:13:40 -0700 Subject: Registry In-Reply-To: Message-ID: <1318965246-106382752@cnrmail.lbl.gov> At 10:18 AM 4/21/98 +0100, MOSTHAVM@plcman.siemens.co.uk wrote: >Hi all, > >this might be a stupid question, but I am wondering what I have to do to >register with the 6Bone. I am already tunneling throug to Netcom UK for >a couple of months. My range is 3ffe:1f00:2::0/48 and the entry should >be for SIEMENS plc UK. Read: http://www.6bone.net/RIPE-registry.html#anchor11267048 and http://www.6bone.net/RIPE-registry.html#anchor11274982 Bob From rlfink@lbl.gov Tue Apr 21 22:07:15 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 21 Apr 1998 14:07:15 -0700 Subject: minutes of ngtrans wg meeting at LA IETF - final version Message-ID: ngtrans WG meeting March 31, 1988 Los Angeles, CA IETF Chairs:       Bob Fink rlfink@lbl.gov               Robert Gilligan gilligan@freegate.com               Tony Hain tonyhain@microsoft.com Reported by Bob Gilligan, Alain Durand and Bob Fink ________________________________________________________________________ ngtrans tools portion of meeting, chaired by Tony Hain Discussion:   ngtrans@sunroof.eng.sun.com Subscribe:    majordomo@sunroof.eng.sun.com  "subscribe ngtrans" Archive: ftp://playground.sun.com/pub/ngtrans Web site: http://www.6bone.net/ngtrans.html ____ AIIH I-D- Jim Bound Jim Bound gave an overview on his new Internet-Draft titled "Assignment of IPv4 Global Addresses to IPv6 hosts (AIIH)".  Note that the acronym for this proposal has changed from NNAT to AIIH.  This Internet-Draft replaces the earlier NNAT I-D. The general objective of this proposal is to allow IPv6/IPv4 dual hosts configured with permanent global IPv6 and get temporary assignments of IPv4 global addresses to use when communicating with IPv4 hosts.  This conserves the IPv4 address space since a small pool of global IPv4 addresses can be used by a larger number of IPv6/IPv4 hosts.  This proposal does NOT employ header translation. The proposal uses an "AIIH server" situated at the boundary between an IPv4 and an IPv6 cloud which operates both as a DNS and DHCP server. The AIIH server handles IPv4 DNS queries for IPv6/IPv4 hosts; assigns temporary IPv4 addresses to IPv6/IPv4 hosts, and manages tunnels to IPv6/IPv4 hosts.  The IPv6/IPv4 hosts use DHCP to acquire their temporary IPv4 addresses.  Two cases of communication are handled:    1)   IPv6/IPv4 host initiating communication with an IPv4 host.    2)   IPv4 host initiating communication with an IPv6/IPv4 host. IPv4 packets between the IPv6/IPv4 host and the AIIH server can be carried in three forms:    1)   Tunneled in IPv6.    2)   Tunneled in IPv4.    3)   Carried as native IPv4 packets. More details on this proposal can be found in Jim's slides are located at: ftp://sipper.zk3-x.dec.c om/pub/aatn_aiih_0498.zip ftp://sipper.zk3-x.de c.com/pub/ngtrans_aiih_0498.zip A few questions were raised in the discussion of this proposal:    -    Someone asked what specific changes an IPv6 host implementation         would need to make in order to implement AIIH.  Jim said that         the primary change would be adding the facility to acquire an         IPv4 address via DHCP when needed. Jim would like feedback on this proposal now.  He plans on releasing an updated version of this document before the Chicago IETF meeting. ____ NAT-PT I-D- George Tsirtsis & Pyda Srisuresh George Tsirtsis and Pyda Srisuresh presented theirnew Internet-Draft titled "Network Address Translation - Protocol Translation (NAT-PT)".  This is a revision of his earlier I-D of the same name.  This draft adds a lot of new material and is about 3 times larger than the old version. The general objective of this proposal is to allow areas of IPv6-only nodes, or IPv6/IPv4 dual nodes using only IPv6 addresses (no IPv4 addresses), to be deployed.  This would allow sites to achieve the benefits of converting a site completely to IPv6, avoiding the need to maintain and administer IPv4 throughout the site. The proposal employs techniques analogous to IPv4 NAT and port translation to allow IPv6 nodes to communicate with IPv4 nodes.  It envisions NAT-PT translator nodes being deployed at the borders of IPv6 networks.  The same technique could be used for stub dual IPv6/IPv4 networks, or stub IPv4 networks. The NAT-PT translator nodes perform stateful header translation between IPv4 and IPv6, basing the translation on mappings between IPv6 addresses and IPv4 addresses that are generated on the fly (in response to traffic) or in response to DNS queries.  The translators may manage pools of IPv4 addresses that are used for these mappings. Additionally, they may intercept and translate DNS queries and replies. Changes to the I-D in this version include:    -    Extended to allow the use of any prefix    -    Added some new DNS interactions    -    Added support for port translation    -    Merged in the header translation mechanisms from Erik Nordmark's         SIIT Internet-Draft The presentation walked through three different scenarios: one case of an IPv6 node initiating communication with an IPv4 node, and two cases of an IPv4 node initiating communication with an IPv6 node. More details of the proposal can be found at: ftp://ftp.labs.bt.com/pub/tsirtsg/41-IETF-NATPT.zip http://www.livingston.com/Tech/IETF/natpt Several issues were raised in the discussion that followed:    -    Tony Hain pointed out that the document needs to discuss         applicability of this technique (what types of sites could use         it, what types should not), and also needs to discuss scaling         issues.    -    Brian Carpenter suggested that the group needs to consider how         this technique would combine with the various other transition         techniques, and API issues it raises.    -    Concern was raised about the translation of DNS queries and         replies.  It was not clear whether this could be made to work         with signed DNS queries/replies. ____ SMTP issues in IPv4/v6 environment - Kazuhiko Yamamoto A presentation of SMTP use in dual-stack environments was given by Kazu Yamamoto of the WIDE project.  The WIDE project now has dual IPv4/IPv6 stack MTAs ready for testing, and thus experimented with registering MX records for IPv6 MTAs and what happens to IPv4 only MTA servers. Results were that IPv4-only Sendmail/Bind has no problem with AAAA records(Sendmail 5.61 or later and Bind 4.8.3 or later), but when MX records were used which refer to A and AAAA records there were problems.  Further experimentation is planned and will be reported as appropriate. (chair's note:  this work probably falls more under the 6bone rather than the tools portion of ngtrans, thus will be scheduled there in the future.) ________________________________________________________________________ ngtrans 6bone portion of meeting, chaired by Bob Fink Discussion:   6bone@isi.edu (6BONE Mailer) Subscribe:    majordomo@isi.edu "subscribe 6bone" Archive:      http://www.ipv6.nas.nasa.gov/6bone/ Web site: http://www.6bone.net ____ 6bone Status report - Bob Fink & David Kessens A brief status of the 6bone was given by Bob Fink of ESnet and David Kessens of ISI.     240 sites in 32 countries     14 host and 14 router implementations (probably more at this time)     45 sites participating in the 6bone backbone     site, routing and address delegation done thru 6bone registry at ISI       courtesy of David Kessensof ISI       some new RPSL features in use on the registry     maps and many statistics automatically made up from 6bone registry       courtesy of Andrew Scott of Lancaster Univ.     reverse DNS registry courtesy of Bill Manning of ISI ____ 6bone routing issues I-D - Bertrand Buclin & Alain Durand A presentation was made of was made.  This I-D is based on the following routing principles: The 6bone is a hierarchical network with     backbone sites acting as pseudo TLAs (pTLAs)     pseudo NLAs (pNLAs) providing transit services below pTLAs     leaf sites pTLAs MUST use BGP4+ between them Multihomed sites SHOULD use BGP4+ Leaf sites MAY use default routing Aggregation MUST be performed by border routers     Specially true for pTLAs There are a set of rules for     Link Local prefixes     Site Local prefixes     Special case prefixes     Multicast prefixes     IPv4 mapped prefixes     IPv4 compatible prefixes     Undefined Unicast prefixes     Default routes     Aggregation and advertisement issues     Inter site links This document will be revised based on minor comments and recirculated. ____ 6bone routing reports and related issues - Masaki Hirabaru A presentation of the new Merit 6bone Routing Reports was given by Masaki Hirabaru of Merit.  These reports are collected by an MRT routing daemon and processed with the IPMA statistics tool.  An email list for the daily reports is available that gives the size of the 6bone routing table, how many unique AS's are in use, how many BGP4+ announcements, withdrawals and unique routes there are, a list of the most poorly aggregated announcments and the top five most active prefixes.  A route flap graph is also available. Initial use of the tool shows too many routing changes for so few routes, thus indicating possible routing software/protocol problems.  The reports can also be used to encourage aggregation and detect incorrect configurations. Feedback on, and use of, these reports is encouraged. The reports can be subscribed to by sending email to majordomo@merit.edu with "subscribe 6bone-routing report" in the message.  A hypemail archive is available at:     http://www.merit.edu/mail.archives/html/6bone-routing-report The Rout Flap Graph is at:     http://www.merit.edu/mail.archives/~ipma/java/FlapGraph.html ____ Multihomed routing domain issues for IPv6 aggregatable scheme I-D - Francis Dupont A presentation was made of current ideas for handling IPv6 site multihoming by Francis Dupont of Inria.  A one hour session on this topic was held in the hour preceding this ngtrans meeting.  There are several different approaches possible to this problem, several of which share problems and solutions with IPv4. Francis Dupont can provide multiprovider presentations in FIG, PostScript (A4) and GIF formats upon request: Francis Dupont Bob Fink noted that this work may best be done under the Routing Area to encourage wider participation in the discussion and solutions for site multihoming, a path he has agreed to pursue with the head of the Routing Area. ____ 6bone transit through CAIRN - Maryann Maher A brief overview was given of Allison Mankin's CAIRN native IPv6 6bone backbone proposal by Maryann Maher of ISI-East.  In brief, the CAIRN project is willing to provide native IPv6 backbone service across the US, on a testing use basis, from CAIRN's points of prescence at LBL, ISI-West, MCI, ISI-East and UCL. More information can be gotten from: http://www.cairn.net/ ____ IPSEC proposition - Maryann Maher Maryann maher of ISI-East presented Allison Mankin's request to the 6bone project that IPSEC AUTH functionality be required in 6bone routers by the end of the year. Though there was a sense of agreement that it was appropriate for the 6bone to push the development and testing of security for routers, there was also a bit of confusion of just what was meant by this proposal.  Bob Fink will request Allison to make a specific proposal that can be considered on the mail list. ____ Win-NT IPv6 public source - Richard Draves A short presentation of the new Windows NT IPv6 implementation by Microsoft Research was given by Richard Draves of Microsoft.  He noted that this work was also being supported by Allison Mankin's group at ISI-East. The source and binary release was made on March 24, 1988, and can be retrieved from:     http://www.research.microsoft.com /msripv6 It is being released to promote research, education and testing, and is not intended for commercial use.  There is no support for Windows 95 or 98.  It is copyrighted and distributed under a license.  Richard specifically encouraged those with troubles agreeing to the license to contact him to see if something mututally agreeable can be arranged. Richard noted that, although it was released for NT version 4, he had been able to easily run it on NT version 5 as well, though he needed to make an installation procedure change. Initially the following works: BaSic IPv6 header processing Neighbor Discovery Stateless autoconfiguration Partial ICMPv6 (basically ping support, but not error messages) Partial Multicast Listener Discovery Automatic and configure tunnels IPv6 over IPv4 per the Carpenter/Jung draft UDP and TCP over IPv6 ping, traceroute, ttcp, ftp/ftpd, NetMon What's missing: Security and Auth headers Mobility support Routing Applications as follows   Web client/server   File client/server (i.e., Microsoft Networking)   DNS client/server v6/v4 translation ____ pTLA asignment rules - Bob Fink Delayed to an informal lunchtime meeting the day after the ngtrans meeting. When presented to the lunchtime group, there was no further comment on the pTLA assignment rules presented by Bob Fink of ESnet, other than that some folk are unwilling to say a site cannot do something.  Bob noted that these rules have been presented before on the 6bone list and that he will continue to require new pTLA requestors to respond to the four criteria, to the list, so general sentiment can be heard.  He will then make a decision based on the requestor's response and the sentiment expressed. Bob encouraged those that do not like any particular policy he is enforcing to comment to him directly or to the list. ____ steps to clean up the backbone - Bob Fink Delayed to an informal lunchtime meeting the day after the ngtrans meeting. Bob Fink of ESnet presented some of his problems and possible solutions about the 6bone backbone and its general cleanup: Various problems – reliability – old addresses in use – invalid tunnels – routing loops – non BGP4+ peering – incomplete registry info – no address delegation through the registry Various solutions – enforcing registry rules (e.g., if no correct entry no listing shown) – pulling pTLAs for sites not providing good service or incomplete and inaccurate registry entry – publish top ten “worst site” list – various tools to show what doesn’t work Alain Durand then spoke in favor of terminating pTLA sites that were not following various rules as expressed in the 6bone routing issues I-D.  Several folk (Bertrand Buclin, Guy Davies and others) spoke against the harsh enforcement of rules as being inappropriate for the 6bone and its testing nature. The general consensus seemed to be that report-based enforcement was more appropriate for the 6bone.  Thus a set of rules would be agreed upon (say the Buclin/Durand draft) and reports would target those not complying. It was also agreed that a 6bone-ops list made up of 6bone registry contacts would be a better place for reports than the main 6bone list.  This would also help enforce the use of the registry for participating sites. Bob agreed to publish to the 6bone list a general proposal for a way to start the cleanup process based on discussions from this session. ____ tools to help clean up the backbone - Ivano Guardini - 10 mins Delayed to an informal lunchtime meeting the day after the ngtrans meeting.  Ivano Guardini of CSELT gave a presentation of the new ASpath-tree tool that monitors BGP4+ routing, resulting from work of both Ivano and Paolo Fasano also of CSELT.  This tool provides a graphical view of the BGP4+ routing tree towards the 6bone.  The results are obtained by elaborating the AS path information available in the BGP4+ routing table of an IPv6 border router terminating BGP4+ capable tunnels.  Results are presented automatically as html pages.  See:     http://carmen.cselt.it/ipv6/bgp/ index.html The tools was developed as a set of unix scripts in Perl 5.0, and tested on a Solaris 2.5.1 workstation.  BGP4+ routes are collected using rsh commands, and the current script handles Cisco routers.  Required inputs for the program are:     the 6bone registry database     the 6bone pTLA list Ivano then showed various sample results from a CSELT viewpoint using ASpath-tree.  For future work the following was given:     Automatic detection of BGP4+ routing anomolies       unaggregatedprefixes, wrong prefix advertisements ...     Provide information on BGP4+ routing stability     Use of SNMP for data acquisition     ...and the desire for suggestions from the 6bone community Ivano asked that other pTLA sites install the code, which is available at:     ftp://carmen/cselt.it/pub/ASpath-tree.tar.gz -end From Ivano.Guardini@CSELT.IT Wed Apr 22 13:46:57 1998 From: Ivano.Guardini@CSELT.IT (Guardini Ivano) Date: Wed, 22 Apr 1998 14:46:57 +0200 Subject: Unaggregated prefixes in the BGP4+ cloud Message-ID: Hi all, as many of you probably already know, at CSELT we are making available a set of html pages (http://carmen.cselt.it/ipv6/bgp/index.html) showing the BGP4+ routing tree from CSELT to the whole 6Bone and from CSELT to the 6Bone backbone. These pages are updated every 5 min and looking at the most recent results (http://carmen.cselt.it/ipv6/bgp/bgp-page-complete.html) I have observed that I am receiving several BGP4+ routes towards excessive long prefixes (/124 and longer!). In addition some of these routes are associated to excessive long AS paths (from 10 to 15 hops!). I could easily solve the problem placing some BGP4+ input filters on my IPv6 border routers (e.g. blocking all the prefixes longer than /64 should be enough to clean up my routing tables). But before doing that I would like to know if somebody else is already adopting this kind of policy inside the 6Bone. I am wondering if the correct way to solve the problem is to place filters on the routers or to send e-mails in order to help every BGP4+ speaker to perform correct advertisements. Opinions would be appreciated. Bye Ivano --------------------------------------------------- Ivano Guardini CSELT SpA via G. Reiss Romoli 274 Torino (Italy) Tel. +39 11 228 5424 Fax. +39 11 228 5069 e-mail: ivano.guardini@cselt.it --------------------------------------------------- From rlfink@lbl.gov Wed Apr 22 12:44:26 1998 From: rlfink@lbl.gov (Bob Fink) Date: Wed, 22 Apr 1998 04:44:26 -0700 Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <199804221246.OAA02833@horus.imag.fr> References: Message-ID: <1318893354-110707591@cnrmail.lbl.gov> Jean-Luc, I noticed this yesterday and sent a request to David Kessens at ISI to look at the problem. No repsonse yet. Thanks, Bob At 02:46 PM 4/22/98 +0200, Jean-Luc Richier wrote: >Follwing the current IPng discussion, I tried to control the entris in the >database for the members of the G6 group. >I have a problem to contact whois.6bone.net >traceroute points to a routing loop inside the isi.edu domain >Can you do something > >Thanks > >horus.imag.fr(47) traceroute whois.6bone.net >traceroute to whois1.avalon.rs.net (198.32.4.102), 30 hops max, 40 byte packets > 1 imag-campus (129.88.38.254) 9 ms 6 ms 5 ms > 2 r-ujf.grenet.fr (193.54.185.126) 10 ms 5 ms 5 ms > 3 aramis-ft.grenet.fr (193.54.184.2) 10 ms 19 ms 5 ms > 4 194.199.224.121 (194.199.224.121) 66 ms 42 ms 32 ms > 5 grenoble.renater.ft.net (194.199.224.114) 63 ms 39 ms 24 ms > 6 stamand1.renater.ft.net (195.220.180.5) 31 ms 48 ms 59 ms > 7 rbs1.renater.ft.net (195.220.180.50) 34 ms 56 ms 52 ms > 8 raspail.renater.ft.net (195.220.180.217) 31 ms 37 ms 19 ms > 9 bagnolet-eurogate.renater.ft.net (195.220.180.225) 108 ms 75 ms * >10 193.55.152.66 (193.55.152.66) 112 ms 133 ms 128 ms >11 sl-pennsauken-hssi.eurogate.net (194.206.207.34) 180 ms * 210 ms >12 * sl-bb10-pen-0-2.sprintlink.net (144.232.5.13) 186 ms 142 ms >13 144.232.5.62 (144.232.5.62) 175 ms * 129 ms >14 f2.peer1.nyc1.genuity.net (192.157.69.49) 136 ms 161 ms 132 ms >15 core1.lax1.genuity.net (207.240.0.5) 213 ms 270 ms 229 ms >16 fe-6-0.peer1.lax1.genuity.net (207.240.1.30) 297 ms 194 ms * >17 198.32.146.10 (198.32.146.10) 298 ms 175 ms 220 ms >18 * bah.isi.edu (128.9.160.26) 239 ms 220 ms >19 lngw2.isi.edu (128.9.160.249) 212 ms 204 ms * >20 * bah.isi.edu (128.9.160.26) 221 ms * >21 lngw2.isi.edu (128.9.160.249) 199 ms 218 ms 260 ms >22 * * * >23 lngw2.isi.edu (128.9.160.249) 193 ms 195 ms 371 ms >24 bah.isi.edu (128.9.160.26) 274 ms^C > >-- >Jean-Luc RICHIER (Jean-Luc.Richier@Imag.Fr richier@imag.fr) >Laboratoire Logiciels, Systemes et Reseaux (LSR-IMAG) >IMAG-CAMPUS, BP 72, F-38402 St Martin d'Heres Cedex >Tel : +33 4 76 82 72 32 Fax : +33 4 76 82 72 87 > From bmanning@ISI.EDU Wed Apr 22 18:39:23 1998 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Wed, 22 Apr 1998 10:39:23 -0700 (PDT) Subject: 6bone registry access restored Message-ID: <199804221739.AA03657@zed.isi.edu> The cable that connects the network segment wherein the 6bone registry machine resides was reseated. It was apparently knocked loose when someone decided to use the facility for empty box storage. sandbox>ping whois.6bone.net Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 198.32.4.102, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms sandbox> --bill From bmanning@ISI.EDU Wed Apr 22 19:45:20 1998 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Wed, 22 Apr 1998 11:45:20 -0700 (PDT) Subject: (ngtrans) Number of IPv6 hosts In-Reply-To: <1318893354-110707591@cnrmail.lbl.gov> from "Bob Fink" at Apr 22, 98 04:44:26 am Message-ID: <199804221845.AA03972@zed.isi.edu> Bob, see the earlier note about the restoral of service. > > Jean-Luc, > > I noticed this yesterday and sent a request to David Kessens at ISI to look > at the problem. No repsonse yet. > > > Thanks, > > Bob > > At 02:46 PM 4/22/98 +0200, Jean-Luc Richier wrote: > >Follwing the current IPng discussion, I tried to control the entris in the > >database for the members of the G6 group. > >I have a problem to contact whois.6bone.net > >traceroute points to a routing loop inside the isi.edu domain > >Can you do something > > > >Thanks > > > >horus.imag.fr(47) traceroute whois.6bone.net > >traceroute to whois1.avalon.rs.net (198.32.4.102), 30 hops max, 40 byte > packets > > 1 imag-campus (129.88.38.254) 9 ms 6 ms 5 ms > > 2 r-ujf.grenet.fr (193.54.185.126) 10 ms 5 ms 5 ms > > 3 aramis-ft.grenet.fr (193.54.184.2) 10 ms 19 ms 5 ms > > 4 194.199.224.121 (194.199.224.121) 66 ms 42 ms 32 ms > > 5 grenoble.renater.ft.net (194.199.224.114) 63 ms 39 ms 24 ms > > 6 stamand1.renater.ft.net (195.220.180.5) 31 ms 48 ms 59 ms > > 7 rbs1.renater.ft.net (195.220.180.50) 34 ms 56 ms 52 ms > > 8 raspail.renater.ft.net (195.220.180.217) 31 ms 37 ms 19 ms > > 9 bagnolet-eurogate.renater.ft.net (195.220.180.225) 108 ms 75 ms * > >10 193.55.152.66 (193.55.152.66) 112 ms 133 ms 128 ms > >11 sl-pennsauken-hssi.eurogate.net (194.206.207.34) 180 ms * 210 ms > >12 * sl-bb10-pen-0-2.sprintlink.net (144.232.5.13) 186 ms 142 ms > >13 144.232.5.62 (144.232.5.62) 175 ms * 129 ms > >14 f2.peer1.nyc1.genuity.net (192.157.69.49) 136 ms 161 ms 132 ms > >15 core1.lax1.genuity.net (207.240.0.5) 213 ms 270 ms 229 ms > >16 fe-6-0.peer1.lax1.genuity.net (207.240.1.30) 297 ms 194 ms * > >17 198.32.146.10 (198.32.146.10) 298 ms 175 ms 220 ms > >18 * bah.isi.edu (128.9.160.26) 239 ms 220 ms > >19 lngw2.isi.edu (128.9.160.249) 212 ms 204 ms * > >20 * bah.isi.edu (128.9.160.26) 221 ms * > >21 lngw2.isi.edu (128.9.160.249) 199 ms 218 ms 260 ms > >22 * * * > >23 lngw2.isi.edu (128.9.160.249) 193 ms 195 ms 371 ms > >24 bah.isi.edu (128.9.160.26) 274 ms^C > > > >-- > >Jean-Luc RICHIER (Jean-Luc.Richier@Imag.Fr richier@imag.fr) > >Laboratoire Logiciels, Systemes et Reseaux (LSR-IMAG) > >IMAG-CAMPUS, BP 72, F-38402 St Martin d'Heres Cedex > >Tel : +33 4 76 82 72 32 Fax : +33 4 76 82 72 87 > > > -- --bill From Nikos Mouat Thu Apr 23 06:53:54 1998 From: Nikos Mouat (Nikos Mouat) Date: Thu, 23 Apr 1998 00:53:54 -0500 (CDT) Subject: 0::0 Message-ID: Hi, Should I be seeing these routes?? I just noticed after an upgrade to 11.3(19980421:205904) [raj-ipv6 111] but wasn't looking before that so they may have been there.. nm BGP IPv6 table version is 320, local router id is 206.129.255.20 Status codes: * - valid, > - best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete 0::0/32 * 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 3274 5539 1273 1835 3263 2839 1103 1275 1225 5609 1849 786 109 5623 1717 137 ? *> 3FFE:C00:E:7::1 FE80::60:3E11:6770:22 Tunnel1 109 5623 1717 137 ? 0::0/21 *> 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 i * 3FFE:C00:E:7::1 FE80::60:3E11:6770:22 Tunnel1 109 5623 1849 3582 i 0::0/7 *> 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 293 137 ? * 3FFE:C00:E:7::1 FE80::60:3E11:6770:22 Tunnel1 109 5623 1717 137 ? 0::0/3 *> 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 293 137 ? * 3FFE:C00:E:7::1 FE80::60:3E11:6770:22 Tunnel1 109 5623 559 137 ? 0::0/1 * 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 3274 5539 1273 1835 3263 2839 1103 1275 1225 5609 1849 786 109 5623 1717 137 ? *> 3FFE:C00:E:7::1 FE80::60:3E11:6770:22 Tunnel1 109 5623 1717 137 ? 0::0/0 *> 3FFE:1500::FFFE:0:0:25 FE80::C5A:CB51:17 Tunnel3 3582 1225 109 i From richdr@microsoft.com Sun Apr 26 21:09:01 1998 From: richdr@microsoft.com (Richard Draves) Date: Sun, 26 Apr 1998 13:09:01 -0700 Subject: 04/24/98 6Bone Routing Report Message-ID: <4D0A23B3F74DD111ACCD00805F31D8100583214D@red-msg-50.dns.microsoft.com> I've been watching these reports for several weeks now... I've seen the number of announcements vary by two orders of magnitude. I assume that when it is very high (as in the report below), that means there is something broken? Is there anyone out there who takes an interest in ferreting out these problems? Just curious, Rich > -----Original Message----- > From: owner-6bone-routing-report@merit.edu > [SMTP:owner-6bone-routing-report@merit.edu] > Sent: Friday, April 24, 1998 11:14 PM > To: 6bone-routing-report@merit.edu > Subject: 04/24/98 6Bone Routing Report > > See http://www.merit.edu/ipma for a more detailed report on > routing problems and recommendations on ways service providers can > limit the spread of invalid routing information. > Send comments and questions to ipma-support@merit.edu > > To unsubscribe from this list, send mail to > 6bone-routing-report-request@merit.edu. > A hypermail archive is available at > http://www.merit.net/mail.archives/html/6bone-routing-report/ > > Also see http://www.caida.org for more information about Internet > statistics > collection research efforts. > > --------------------------------------------- > This report is for 04/24/98. > --------------------------------------------- > > Size of 6Bone Routing Table: > Max = 124, Min = 107, Average = 116 > 40 Unique Autonomous System (AS) numbers > > BGP4+ Traffic Summary: > Announcements=1046901 Withdraws=184825 Unique Routes=159 > > Poorly Aggregated Announcements: > -------------------------------- > 20:53:49 3ffe:2101:0:ffff::ffff:ffff/127 from 3ffe:c00:e:b::1 (109) > 00:07:51 3ffe:1500::fffe:0:0:10/126 from 3ffe:1c00:0:60::153 (237) > 00:05:49 3ffe:1500::fffe:0:0:11/126 from 3ffe:900:0:3::1 (1225) > 00:07:51 3ffe:1500::fffe:0:0:c/126 from 3ffe:1c00:0:60::153 (237) > 00:05:49 3ffe:1500::fffe:0:0:d/126 from 3ffe:900:0:3::1 (1225) > 00:07:51 3ffe:1500::fffe:0:0:14/126 from 3ffe:1c00:0:60::153 (237) > 00:05:50 3ffe:1500::fffe:0:0:15/126 from 3ffe:900:0:3::1 (1225) > 02:43:31 3ffe:2000:0:1:ffff:ffff:ffff:fff0/124 from 3ffe:900:0:3::1 > (1225) > 00:08:01 3ffe:2101:0:ffff::2/127 from 3ffe:c00:e:b::1 (109) > 00:07:51 3ffe:1500::fffe:0:0:18/126 from 3ffe:1c00:0:60::153 (237) > 00:05:50 3ffe:1500::fffe:0:0:19/126 from 3ffe:900:0:3::1 (1225) > 14:08:28 3ffe:1500:fffe::c/126 from 3ffe:1c00:0:60::153 (237) > 00:07:59 3ffe:f01:0:ffff::6/127 from 3ffe:c00:e:b::1 (109) > 00:07:42 3ffe:f01:0:ffff::7/127 from 3ffe:900:0:3::1 (1225) > 00:08:01 3ffe:2000:0:1::60/124 from 3ffe:c00:e:b::1 (109) > 00:07:51 3ffe:1500::fffe:0:0:1/126 from 3ffe:1c00:0:60::153 (237) > 00:07:51 3ffe:1500::fffe:0:0:4/126 from 3ffe:1c00:0:60::153 (237) > 00:07:24 3ffe:1001:1:ffff::/126 from 3ffe:c00:e:b::1 (109) > 13:21:56 3ffe:700:20:2::a/126 from 3ffe:900:0:3::1 (1225) > 00:05:49 3ffe:1500::fffe:0:0:5/126 from 3ffe:900:0:3::1 (1225) > 00:07:51 3ffe:1500::fffe:0:0:8/126 from 3ffe:1c00:0:60::153 (237) > 00:07:51 3ffe:c00:8004:1::/80 from 3ffe:1c00:0:60::153 (237) > 21:16:50 3ffe:2000:0:ff:ffff:ffff:ffff:ffff/124 from 3ffe:c00:e:b::1 > (109) > 00:05:49 3ffe:1500::fffe:0:0:9/126 from 3ffe:900:0:3::1 (1225) > 00:08:01 3ffe:302:11:2:0:2:0:50/124 from 3ffe:c00:e:b::1 (109) > 18:11:44 3ffe:700:20:2:ff:ffff:ffff:ffff/126 from 3ffe:900:0:3::1 (1225) > 14:08:28 3ffe:1c00::3/128 from 3ffe:1c00:0:60::153 (237) > 00:05:11 3ffe:1500:0:0:fffe::/126 from 3ffe:900:0:3::1 (1225) > 04:21:13 3ffe:302:ffff:ffff:ffff:ffff:ffff:ffff/124 from 3ffe:900:0:3::1 > (1225) > 10:11:20 3ffe:1500::fffe:0:ffff:ffff/126 from 3ffe:1c00:0:60::153 (237) > 00:07:51 3ffe:1500::fffe:0:0:20/126 from 3ffe:1c00:0:60::153 (237) > 00:05:50 3ffe:1500::fffe:0:0:21/126 from 3ffe:900:0:3::1 (1225) > 11:17:45 3ffe:1001:1:ffff::1/126 from 3ffe:900:0:3::1 (1225) > 00:07:51 3ffe:1500::fffe:0:0:24/126 from 3ffe:1c00:0:60::153 (237) > 00:05:50 3ffe:1500::fffe:0:0:25/126 from 3ffe:900:0:3::1 (1225) > 06:37:44 3ffe:1500:ff:ffff:ffff:ffff:ffff:ffff/126 from 3ffe:900:0:3::1 > (1225) > 00:08:01 3ffe:700:20:2::8/126 from 3ffe:c00:e:b::1 (109) > 14:08:15 3ffe:dfe:fffe::8/126 from 3ffe:1c00:0:60::153 (237) > 00:07:51 3ffe:1500::fffe:0:0:1c/126 from 3ffe:1c00:0:60::153 (237) > 00:05:50 3ffe:1500::fffe:0:0:1d/126 from 3ffe:900:0:3::1 (1225) > 22:15:25 3ffe:2101:0:ffff:0:ff:ffff:ffff/127 from 3ffe:c00:e:b::1 (109) > > > > The top five most active prefixes: > ---------------------------------- > 1. 3ffe:2101:0:ffff::2/127 had 33502 BGP+ Updates (1568 unique aspaths) > 3263 1275 1717 5623 1849 5609 48 1752 > 1225 109 5623 5609 48 1752 > 109 1225 1849 2839 1103 1717 5623 5609 48 1752 > 1225 1103 1275 1717 1835 1849 5609 48 1752 > 1673 1103 786 1717 5623 1225 109 1849 5609 48 1752 > 3263 1103 1275 559 1717 5623 1225 48 1752 > 1673 1103 786 1849 1225 5609 48 1752 > 1225 5609 5623 1717 1103 293 1849 109 48 1752 > 109 1225 1103 293 1849 1752 > 109 5623 1225 5609 1849 1752 > 1673 1103 1275 559 5623 109 48 1752 > ...Truncated... > > 2. 3ffe:700::/24 had 33265 BGP+ Updates (217 unique aspaths) > 1673 1103 1835 3263 1275 293 > 109 5623 1225 1673 293 > 109 33 1225 1849 1103 293 > 1225 33 109 1849 1103 293 > 109 1849 33 2914 293 > 109 1849 4555 1103 293 > 109 1225 1103 293 > 109 33 1849 1835 1103 293 > 1225 48 109 1849 33 293 > 1225 1849 109 33 2914 293 > 1225 48 109 293 > ...Truncated... > > 3. 3ffe:2c00::/24 had 32097 BGP+ Updates (1529 unique aspaths) > 109 33 5623 1717 1835 1849 1225 5609 48 1752 > 109 1225 1103 1275 1717 1835 1273 5539 1849 5609 48 1752 > 1673 1103 786 1717 1835 1849 5609 48 1752 > 1225 109 5623 5609 48 1752 > 1225 1103 1275 1717 1835 1849 5609 48 1752 > 1673 1103 786 1717 5623 1225 109 1849 5609 48 1752 > 109 33 1225 5609 5623 1717 1103 293 1849 1752 > 1225 33 1849 2839 1103 293 4555 109 48 1752 > 1673 1103 786 1849 1225 5609 48 1752 > 1673 1103 1717 5623 5609 1849 33 1225 48 1752 > 109 1225 1103 293 1849 1752 > ...Truncated... > > 4. 3ffe:1a00::/24 had 31414 BGP+ Updates (1551 unique aspaths) > 109 1225 1103 1835 1849 5609 48 7081 > 1225 33 5623 1717 786 1103 1849 5609 48 7081 > 1673 1103 1225 109 1849 5609 48 7081 > 1673 1103 786 1849 5609 48 7081 > 1225 33 1849 2839 1103 1275 559 3303 5623 109 48 7081 > 1225 5609 5623 1717 1103 2839 1849 109 48 7081 > 1225 1673 1103 1275 1717 5623 109 48 7081 > 1225 5623 1717 1103 1835 1849 5609 48 7081 > 109 4555 1849 1835 1103 1717 5623 5609 48 7081 > 1225 109 33 5623 1717 1103 2839 1849 5609 48 7081 > 1673 1103 1275 559 3303 5623 33 1225 48 7081 > ...Truncated... > > 5. 3ffe:2101:0:900::/64 had 30501 BGP+ Updates (1189 unique aspaths) > 109 1225 5609 5623 1717 1103 1835 1849 1752 3185 > 109 5623 1717 1835 1273 5539 1849 1752 3185 > 1225 1849 1103 1717 5623 5609 48 1752 3185 > 1673 1103 1275 559 3303 5623 109 48 1752 3185 > 3263 1275 1717 1835 1849 1225 48 1752 3185 > 1225 1103 2839 3263 1849 109 48 1752 3185 > 109 48 5609 1225 1103 293 4555 1849 1752 3185 > 1673 1103 1849 5609 1225 109 48 1752 3185 > 1673 1103 1717 5623 109 1849 5609 1225 48 1752 3185 > 1673 1103 1275 559 1717 5623 5609 1225 48 1752 3185 > 109 4555 1103 1275 559 3303 5623 1225 48 1752 3185 > ...Truncated... From masaki@merit.edu Mon Apr 27 16:07:24 1998 From: masaki@merit.edu (Masaki Hirabaru) Date: Mon, 27 Apr 1998 11:07:24 -0400 Subject: 04/24/98 6Bone Routing Report In-Reply-To: Your message of "Sun, 26 Apr 1998 13:09:01 PDT." <4D0A23B3F74DD111ACCD00805F31D8100583214D@red-msg-50.dns.microsoft.com> Message-ID: <199804271507.LAA17299@merit.edu> > I've been watching these reports for several weeks now... I've seen the > number of announcements vary by two orders of magnitude. I assume that when > it is very high (as in the report below), that means there is something > broken? Is there anyone out there who takes an interest in ferreting out > these problems? > > Just curious, > Rich Hi. Rich, At least, I'm watching this report and trying to find a clue what causes this route flapping. I recently added a couple of BGP4+ connections to peek more data. (Merit announces its prefix only to most of them not to contribute to the flapping.) There could have been configuration errors and link outages, but I'd like to make sure that there are no other problems like an inappropriate BGP4+ implementation before a strong route filtering and route dampening will be introduced. If your site would like to be investigated directly :-) or if you are running your original BGP4+ implementation, please let me know. I'd like to add a few more BGP4+ connections with non-cisco routers to find a clue and keep watching our 6bone routing. Thanks, Masaki > > > -----Original Message----- > > From: owner-6bone-routing-report@merit.edu > > [SMTP:owner-6bone-routing-report@merit.edu] > > Sent: Friday, April 24, 1998 11:14 PM > > To: 6bone-routing-report@merit.edu > > Subject: 04/24/98 6Bone Routing Report > > > > See http://www.merit.edu/ipma for a more detailed report on > > routing problems and recommendations on ways service providers can > > limit the spread of invalid routing information. > > Send comments and questions to ipma-support@merit.edu > > > > To unsubscribe from this list, send mail to > > 6bone-routing-report-request@merit.edu. > > A hypermail archive is available at > > http://www.merit.net/mail.archives/html/6bone-routing-report/ > > > > Also see http://www.caida.org for more information about Internet > > statistics > > collection research efforts. > > > > --------------------------------------------- > > This report is for 04/24/98. > > --------------------------------------------- > > > > Size of 6Bone Routing Table: > > Max = 124, Min = 107, Average = 116 > > 40 Unique Autonomous System (AS) numbers > > > > BGP4+ Traffic Summary: > > Announcements=1046901 Withdraws=184825 Unique Routes=159 > > > > Poorly Aggregated Announcements: > > -------------------------------- > > 20:53:49 3ffe:2101:0:ffff::ffff:ffff/127 from 3ffe:c00:e:b::1 (109) > > 00:07:51 3ffe:1500::fffe:0:0:10/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:49 3ffe:1500::fffe:0:0:11/126 from 3ffe:900:0:3::1 (1225) > > 00:07:51 3ffe:1500::fffe:0:0:c/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:49 3ffe:1500::fffe:0:0:d/126 from 3ffe:900:0:3::1 (1225) > > 00:07:51 3ffe:1500::fffe:0:0:14/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:50 3ffe:1500::fffe:0:0:15/126 from 3ffe:900:0:3::1 (1225) > > 02:43:31 3ffe:2000:0:1:ffff:ffff:ffff:fff0/124 from 3ffe:900:0:3::1 > > (1225) > > 00:08:01 3ffe:2101:0:ffff::2/127 from 3ffe:c00:e:b::1 (109) > > 00:07:51 3ffe:1500::fffe:0:0:18/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:50 3ffe:1500::fffe:0:0:19/126 from 3ffe:900:0:3::1 (1225) > > 14:08:28 3ffe:1500:fffe::c/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:59 3ffe:f01:0:ffff::6/127 from 3ffe:c00:e:b::1 (109) > > 00:07:42 3ffe:f01:0:ffff::7/127 from 3ffe:900:0:3::1 (1225) > > 00:08:01 3ffe:2000:0:1::60/124 from 3ffe:c00:e:b::1 (109) > > 00:07:51 3ffe:1500::fffe:0:0:1/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:51 3ffe:1500::fffe:0:0:4/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:24 3ffe:1001:1:ffff::/126 from 3ffe:c00:e:b::1 (109) > > 13:21:56 3ffe:700:20:2::a/126 from 3ffe:900:0:3::1 (1225) > > 00:05:49 3ffe:1500::fffe:0:0:5/126 from 3ffe:900:0:3::1 (1225) > > 00:07:51 3ffe:1500::fffe:0:0:8/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:51 3ffe:c00:8004:1::/80 from 3ffe:1c00:0:60::153 (237) > > 21:16:50 3ffe:2000:0:ff:ffff:ffff:ffff:ffff/124 from 3ffe:c00:e:b::1 > > (109) > > 00:05:49 3ffe:1500::fffe:0:0:9/126 from 3ffe:900:0:3::1 (1225) > > 00:08:01 3ffe:302:11:2:0:2:0:50/124 from 3ffe:c00:e:b::1 (109) > > 18:11:44 3ffe:700:20:2:ff:ffff:ffff:ffff/126 from 3ffe:900:0:3::1 (1225) > > 14:08:28 3ffe:1c00::3/128 from 3ffe:1c00:0:60::153 (237) > > 00:05:11 3ffe:1500:0:0:fffe::/126 from 3ffe:900:0:3::1 (1225) > > 04:21:13 3ffe:302:ffff:ffff:ffff:ffff:ffff:ffff/124 from 3ffe:900:0:3::1 > > (1225) > > 10:11:20 3ffe:1500::fffe:0:ffff:ffff/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:51 3ffe:1500::fffe:0:0:20/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:50 3ffe:1500::fffe:0:0:21/126 from 3ffe:900:0:3::1 (1225) > > 11:17:45 3ffe:1001:1:ffff::1/126 from 3ffe:900:0:3::1 (1225) > > 00:07:51 3ffe:1500::fffe:0:0:24/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:50 3ffe:1500::fffe:0:0:25/126 from 3ffe:900:0:3::1 (1225) > > 06:37:44 3ffe:1500:ff:ffff:ffff:ffff:ffff:ffff/126 from 3ffe:900:0:3::1 > > (1225) > > 00:08:01 3ffe:700:20:2::8/126 from 3ffe:c00:e:b::1 (109) > > 14:08:15 3ffe:dfe:fffe::8/126 from 3ffe:1c00:0:60::153 (237) > > 00:07:51 3ffe:1500::fffe:0:0:1c/126 from 3ffe:1c00:0:60::153 (237) > > 00:05:50 3ffe:1500::fffe:0:0:1d/126 from 3ffe:900:0:3::1 (1225) > > 22:15:25 3ffe:2101:0:ffff:0:ff:ffff:ffff/127 from 3ffe:c00:e:b::1 (109) > > > > > > > > The top five most active prefixes: > > ---------------------------------- > > 1. 3ffe:2101:0:ffff::2/127 had 33502 BGP+ Updates (1568 unique aspaths) > > 3263 1275 1717 5623 1849 5609 48 1752 > > 1225 109 5623 5609 48 1752 > > 109 1225 1849 2839 1103 1717 5623 5609 48 1752 > > 1225 1103 1275 1717 1835 1849 5609 48 1752 > > 1673 1103 786 1717 5623 1225 109 1849 5609 48 1752 > > 3263 1103 1275 559 1717 5623 1225 48 1752 > > 1673 1103 786 1849 1225 5609 48 1752 > > 1225 5609 5623 1717 1103 293 1849 109 48 1752 > > 109 1225 1103 293 1849 1752 > > 109 5623 1225 5609 1849 1752 > > 1673 1103 1275 559 5623 109 48 1752 > > ...Truncated... > > > > 2. 3ffe:700::/24 had 33265 BGP+ Updates (217 unique aspaths) > > 1673 1103 1835 3263 1275 293 > > 109 5623 1225 1673 293 > > 109 33 1225 1849 1103 293 > > 1225 33 109 1849 1103 293 > > 109 1849 33 2914 293 > > 109 1849 4555 1103 293 > > 109 1225 1103 293 > > 109 33 1849 1835 1103 293 > > 1225 48 109 1849 33 293 > > 1225 1849 109 33 2914 293 > > 1225 48 109 293 > > ...Truncated... > > > > 3. 3ffe:2c00::/24 had 32097 BGP+ Updates (1529 unique aspaths) > > 109 33 5623 1717 1835 1849 1225 5609 48 1752 > > 109 1225 1103 1275 1717 1835 1273 5539 1849 5609 48 1752 > > 1673 1103 786 1717 1835 1849 5609 48 1752 > > 1225 109 5623 5609 48 1752 > > 1225 1103 1275 1717 1835 1849 5609 48 1752 > > 1673 1103 786 1717 5623 1225 109 1849 5609 48 1752 > > 109 33 1225 5609 5623 1717 1103 293 1849 1752 > > 1225 33 1849 2839 1103 293 4555 109 48 1752 > > 1673 1103 786 1849 1225 5609 48 1752 > > 1673 1103 1717 5623 5609 1849 33 1225 48 1752 > > 109 1225 1103 293 1849 1752 > > ...Truncated... > > > > 4. 3ffe:1a00::/24 had 31414 BGP+ Updates (1551 unique aspaths) > > 109 1225 1103 1835 1849 5609 48 7081 > > 1225 33 5623 1717 786 1103 1849 5609 48 7081 > > 1673 1103 1225 109 1849 5609 48 7081 > > 1673 1103 786 1849 5609 48 7081 > > 1225 33 1849 2839 1103 1275 559 3303 5623 109 48 7081 > > 1225 5609 5623 1717 1103 2839 1849 109 48 7081 > > 1225 1673 1103 1275 1717 5623 109 48 7081 > > 1225 5623 1717 1103 1835 1849 5609 48 7081 > > 109 4555 1849 1835 1103 1717 5623 5609 48 7081 > > 1225 109 33 5623 1717 1103 2839 1849 5609 48 7081 > > 1673 1103 1275 559 3303 5623 33 1225 48 7081 > > ...Truncated... > > > > 5. 3ffe:2101:0:900::/64 had 30501 BGP+ Updates (1189 unique aspaths) > > 109 1225 5609 5623 1717 1103 1835 1849 1752 3185 > > 109 5623 1717 1835 1273 5539 1849 1752 3185 > > 1225 1849 1103 1717 5623 5609 48 1752 3185 > > 1673 1103 1275 559 3303 5623 109 48 1752 3185 > > 3263 1275 1717 1835 1849 1225 48 1752 3185 > > 1225 1103 2839 3263 1849 109 48 1752 3185 > > 109 48 5609 1225 1103 293 4555 1849 1752 3185 > > 1673 1103 1849 5609 1225 109 48 1752 3185 > > 1673 1103 1717 5623 109 1849 5609 1225 48 1752 3185 > > 1673 1103 1275 559 1717 5623 5609 1225 48 1752 3185 > > 109 4555 1103 1275 559 3303 5623 1225 48 1752 3185 > > ...Truncated... From rlfink@lbl.gov Mon Apr 27 16:41:01 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 27 Apr 1998 08:41:01 -0700 Subject: 04/24/98 6Bone Routing Report In-Reply-To: <4D0A23B3F74DD111ACCD00805F31D8100583214D@red-msg-50.dns.mi crosoft.com> Message-ID: <1318456007-137017342@cnrmail.lbl.gov> Rich, At 01:09 PM 4/26/98 -0700, Richard Draves wrote: >I've been watching these reports for several weeks now... I've seen the >number of announcements vary by two orders of magnitude. I assume that when >it is very high (as in the report below), that means there is something >broken? Is there anyone out there who takes an interest in ferreting out >these problems? Darn good question. These announcements (it they are real) have reached crazy and unreal size. I saw the follopwing : >--------------------------------------------- >This report is for 04/24/98. >--------------------------------------------- > > >Size of 6Bone Routing Table: > Max = 124, Min = 107, Average = 116 > 40 Unique Autonomous System (AS) numbers > > >BGP4+ Traffic Summary: > Announcements=1046901 Withdraws=184825 Unique Routes=159 This is over 1 million announcements in 24 hours. My frustration is that too date when I ask specific sites about their high count I get a "no problem I can see here" type of response. Clearly something is either wrong with some routing or with the reports. Can some expert(s) in this area try to explain (or look into) what may be going on? Thanks, Bob From richdr@microsoft.com Mon Apr 27 17:23:00 1998 From: richdr@microsoft.com (Richard Draves) Date: Mon, 27 Apr 1998 09:23:00 -0700 Subject: 04/24/98 6Bone Routing Report Message-ID: <4D0A23B3F74DD111ACCD00805F31D81005832156@red-msg-50.dns.microsoft.com> > If your site would like to be investigated directly :-) or if you > are running your original BGP4+ implementation, please let me > know. I'd like to add a few more BGP4+ connections with > non-cisco routers to find a clue and keep watching our 6bone > routing. > [Richard Draves] Hi Masaki, I appreciate your offer but my site is a mere leaf node (connected via a static tunnel to NWNET). Our MSR IPv6 implementation does not (at least, not yet) support routing or BGP4+. I have a very very limited understanding of BGP. For us interested bystanders, it would be nice to see occasional mail from the people investigating the 6bone's problems - even fairly mundane progress or status reports are interesting. It might also get the community more involved. Thanks, Rich From rlfink@lbl.gov Mon Apr 27 18:39:30 1998 From: rlfink@lbl.gov (Bob Fink) Date: Mon, 27 Apr 1998 10:39:30 -0700 Subject: new pTLA and welcome to GRNET/GR Message-ID: <1318448897-137445074@cnrmail.lbl.gov> I would like to announce the assignment of a new pTLA (3FFE:2D00::/24) to GRNET/GR, and to welcome them. GRNET/GR is the Greek Research and Technology Network. Bob From rlfink@lbl.gov Tue Apr 28 14:35:02 1998 From: rlfink@lbl.gov (Bob Fink) Date: Tue, 28 Apr 1998 06:35:02 -0700 Subject: ETRI/KR pTLA request Message-ID: 6bone Folk, ETRI (the Korean Electronics and Telecommunications Research Institute) is requesting a pTLA on behalf of the 6Bone-KR(Korea) Project. Following are their answers to our generic requirements. Please send your comments for or against either directly to me or to the mailer. I would like to process this by 11 May (I am out of town next week). Thanks, Bob ------------------------------- 1. Must have experience with IPv6 in the 6Bone, at least as a leaf site and preferably as an NLA transit under a pTLA. We have collaborated IPv6 project with Soongsil Univ.(SSU)(one of the members of the 6Bone-KR) and implemented IP version 6 for freeBSD. This system is attached to CISCO as a leaf site using the NLA address from CISCO since February 1997. We have participated in most of 6Bone proceeding from initial phases. 6Bone-KR intends to deploy a large base of IPv6 networks in major Korean universities and research institutes. ETRI (Electronics and Telecommunications Research Institute), a government sponsored research institute, has played an important role in development and deployment of advanced technologies in Korea. As a NOC of 6Bone-KR, we have IPv6-tunneling, routing experiences using SSU as a NLA transit node with several universities in Korea(SSU, Chungnam National University, KAIST, Hanyang University, etc.). 2. Must have the ability and intent to provide "production-like" 6bone backbone service to provide a robust and operationally reliable 6bone backbone. 6Bone-KR is the Korea research network providing IPv6 interconnection services to the Academic and Research community in Korea. It provides IPv6 connection using Tunneling and will provide high-speed( up to 150Mbps) ATM interconnection service using AISN(Advanced Information Superhighway Network), Korea ATM backbone network. Seoul and R&D park at Daejeon are initial nodes' sites and other major cities will be connected using AISN. The main router(Cisco and PC-platform) is located in the ETRI(NOC of 6Bone-KR) at Daejeon. This project including related technolgies development was launched by government with a budget of $1,000,000 for 3 years. 6Bone-KR is also a member of APAN(Asia Pacific Advanced Network) as a representative of Korea for APAN IPv6 network construction. 3. Must have a potential "user community" that would be served by becomming a pTLA, e.g., the requester is a major player in a region, country or focus of interest. 6Bone-KR interconnects the academic and research community of Korea and currently 6 institutes and universities, more than 200 students and researchers are served. After receiving a pTLA, all members of AISN (more than 30 institutes and universities, more than 3,000 students and researchers) will be interconnected using 6Bone for IPv6 services. 4. Must commit to abide by whatever the 6bone backbone operational rules and policies are (currently there are no formal ones, but the Alain Durand draft is a start in trying to defined some). We, 6Bone-KR, will fully commit to the operational rules of IPv6 now and in the future. If you need any further clarification on any of the above questions, we'd be more than happy to answer them. This email is also sent to: Dr. Young-Han Kim, yhkim@dcn.soongsil.ac.kr (SSU NOC IPv6 contact) Mr. Yong-Woon Kim, qkim@pec.etri.re.kr (ETRI NOC IPv6 contact) Best Regards, Myung-Ki Shin ---- ETRI Address : 161 Kajong-Dong, Yusong-Gu, Daejeon, 305-350, KOREA Tel : +82-42-860-4847 Fax : +82-42-861-5404 E-mail : mkshin@pec.etri.re.kr WWW : http://pec.etri.re.kr -end From Aad.van.der.Zanden@nc3a.nato.int Wed Apr 29 08:20:21 1998 From: Aad.van.der.Zanden@nc3a.nato.int (Aad van der Zanden) Date: Wed, 29 Apr 1998 09:20:21 +0200 Subject: IPv6 analysers Message-ID: <199804290707.AA14639@nc3a.nato.int> Dear 6bone folks How do you feel about creating a list of tested Ipv6 analyser software/hardware? I see there is no such thing available right now and is probably one of the first items one wants to have when you want to have an idea whats happening on the network. Or do you all feel happy with snoop? I think a referal on the 6bone page would not misfit. Or this this maybe not relevant ? What do you think? Regards Aad ==================================================================== // Aad van der Zanden. | POSTAL ADDRESS: // Communications Systems Division // NATO C3 Agency | NATO C3 Agency // Email : Aad.van.der.Zanden@nc3a.nato.int | P.O. BOX 174 // Phone : +31 (0)70 3142440 | 2501 CD The Hague // Fax : +31 (0)70 3142176 | The Netherlands ==================================================================== From jane@ifi.uio.no Wed Apr 29 13:54:26 1998 From: jane@ifi.uio.no (Jan Marius Evang) Date: 29 Apr 1998 14:54:26 +0200 Subject: Questions about RIPE registry Message-ID: How Should I indicate that two sites are connected, not by a tunnel, but by an ATM link? Marius -- -O /\/\ | Jan Marius Evang | Røyskatt 0 0 \| Greve av Ling | Det er deilig aa vaere grevling \ /\ | /In Aurum Veritas/ | i Danmark From rlfink@lbl.gov Wed Apr 29 15:10:36 1998 From: rlfink@lbl.gov (Bob Fink) Date: Wed, 29 Apr 1998 07:10:36 -0700 Subject: Questions about RIPE registry In-Reply-To: Message-ID: <1318288652-147084926@cnrmail.lbl.gov> Marius, At 02:54 PM 4/29/98 +0200, Jan Marius Evang wrote: >How Should I indicate that two sites are connected, not by a tunnel, >but by an ATM link? Goos question. The ipv6-site description: http://www.ISI.EDU/~davidk/6bone/draft-ietf-ngtrans-6bone-registry-02.txt doesn't seem to have anything specified but tunnels for links. I've cc'd David Kessens on this, maybe he has a a good idea how to do this (time for an addition to the ipv6-site object?). Thanks, Bob From davidk@ISI.EDU Wed Apr 29 22:31:01 1998 From: davidk@ISI.EDU (davidk@ISI.EDU) Date: Wed, 29 Apr 1998 14:31:01 -0700 (PDT) Subject: Questions about RIPE registry In-Reply-To: <1318288652-147084926@cnrmail.lbl.gov> from "Bob Fink" at Apr 29, 98 07:10:36 am Message-ID: <199804292131.OAA13619@brind.isi.edu> Bob, Marius, Bob Fink writes: > > At 02:54 PM 4/29/98 +0200, Jan Marius Evang wrote: > >How Should I indicate that two sites are connected, not by a tunnel, > >but by an ATM link? > > Goos question. The ipv6-site description: > > http://www.ISI.EDU/~davidk/6bone/draft-ietf-ngtrans-6bone-registry-02.txt > > > doesn't seem to have anything specified but tunnels for links. > > I've cc'd David Kessens on this, maybe he has a a good idea how to do this > (time for an addition to the ipv6-site object?). So far, we have gotten around this by doing something that is strictly not correct, but works for now ... : use 'IPv6 in IPv6' as the encapsulation in a tunnel attribute I do think that this should be fixed. However, fixing this probaly opens up a can of worms since we will find all kind of other problems that needs fixing too. In the end we will find that we most likely need to move to RPSL. RPSL has much more power to specify what you want. Although I would like it to be different, I am not entirely ready to introduce the full power of RPSL right now (we are currently busy with the transition to RPSL for the IPv4 world) and therefore it might be best to use the 'IPv6 in IPv6' trick for the coming months. I am willing to do a quick fix if people indicate that that is preferred, but I would rather go for a more consistent solution that will take a bit more waiting time from you, David K. --- From rlfink@lbl.gov Thu Apr 30 02:20:39 1998 From: rlfink@lbl.gov (Bob Fink) Date: Wed, 29 Apr 1998 18:20:39 -0700 Subject: Questions about RIPE registry In-Reply-To: <199804292131.OAA13619@brind.isi.edu> References: <1318288652-147084926@cnrmail.lbl.gov> Message-ID: <1318248454-149503159@cnrmail.lbl.gov> David, At 02:31 PM 4/29/98 -0700, davidk@ISI.EDU wrote: > >Bob, Marius, > >Bob Fink writes: >> >> At 02:54 PM 4/29/98 +0200, Jan Marius Evang wrote: >> >How Should I indicate that two sites are connected, not by a tunnel, >> >but by an ATM link? >> >> Goos question. The ipv6-site description: >> >> http://www.ISI.EDU/~davidk/6bone/draft-ietf-ngtrans-6bone-registry-02.txt >> >> >> doesn't seem to have anything specified but tunnels for links. >> >> I've cc'd David Kessens on this, maybe he has a a good idea how to do this >> (time for an addition to the ipv6-site object?). > >So far, we have gotten around this by doing something that is strictly not >correct, but works for now ... : > >use 'IPv6 in IPv6' as the encapsulation in a tunnel attribute > >I do think that this should be fixed. However, fixing this probaly >opens up a can of worms since we will find all kind of other problems >that needs fixing too. In the end we will find that we most likely >need to move to RPSL. RPSL has much more power to specify what you >want. > >Although I would like it to be different, I am not entirely ready to >introduce the full power of RPSL right now (we are currently busy with >the transition to RPSL for the IPv4 world) and therefore it might be >best to use the 'IPv6 in IPv6' trick for the coming months. > >I am willing to do a quick fix if people indicate that that is >preferred, but I would rather go for a more consistent solution that >will take a bit more waiting time from you, I think we should take your advice... stick to the 'IPv6 in IPv6' trick until you can do a conversion to RPSL sometime in the future as appropriate. Thanks for the quick answer. Bob From jane@ifi.uio.no Thu Apr 30 08:52:26 1998 From: jane@ifi.uio.no (Jan Marius Evang) Date: 30 Apr 1998 09:52:26 +0200 Subject: Questions about RIPE registry In-Reply-To: Bob Fink's message of Wed, 29 Apr 1998 18:20:39 -0700 References: <1318288652-147084926@cnrmail.lbl.gov> <1318248454-149503159@cnrmail.lbl.gov> Message-ID: >> Bob Fink writes: BF> I think we should take your advice... stick to the 'IPv6 in BF> IPv6' trick until you can do a conversion to RPSL sometime in BF> the future as appropriate. BF> Thanks for the quick answer. Yes, Thanks. Marius -- -O /\/\ | Jan Marius Evang | Røyskatt 0 0 \| Greve av Ling | Det er deilig aa vaere grevling \ /\ | /In Aurum Veritas/ | i Danmark From bmanning@ISI.EDU Thu Apr 30 15:23:00 1998 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Thu, 30 Apr 1998 07:23:00 -0700 (PDT) Subject: d.2.e.f.f.3.ip6.int. delegation Message-ID: <199804301423.AA07918@zed.isi.edu> The GRnet delegation has been processed: ;; QUERY SECTION: ;; d.2.e.f.f.3.ip6.int, type = NS, class = IN ;; ANSWER SECTION: d.2.e.f.f.3.ip6.int. 1d12h IN NS foo.grnet.gr. d.2.e.f.f.3.ip6.int. 1d12h IN NS nic.grnet.gr. -- --bill From rlfink@lbl.gov Thu Apr 30 19:21:03 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 30 Apr 1998 11:21:03 -0700 Subject: some 6bone backbone cleanup recommendations Message-ID: 6bone Folk, Per the 6bone backbone cleanup discussions at the LA IETF I have generated a first pass set of recommendations on how to proceed. The first basic rule to note is that there was almost complete consensus to avoid hard rule enforcement that forced a pTLA site off the 6bone backbone with no discourse or allowance for a site to try to clean up their act. In fact, it was recommended that we be driven to the greatest extent possible, by reports that point out the problems (a bit of public exposure and humiliation so to speak). Then arbitrate. Various ideas: Setup a 6bone-ops list consisting of only mail handles registered in the 6bone registry: should include email handles from: (David Kessens has volunteered to do this list) the person: object, e-mail: field the mntner: object, mnt-nfy: field remove duplicates all 6bone sites, not just backbone pTLAs Use the current version of Buclin/Durand I-D on "IPv6 routing issues" as policy: should rename this draft "6bone routing practices" (Bertrand is doing this) publish reports of variance with them, per pTLA Require a minimum amount of peering for robustness sake: say 3-5 other pTLAs, but not too many Publish daily lists of following information: as above, publish reports of variance with the I-D rules, per pTLA pTLA routes longer than /24 those pTLAs not carrying all routes (not so easy without special effort/tools) those pTLA tunnels not using BGP4+ (already covered above) those pTLAs having too many flaps (publish the Merit 6bone routing report) the CSELT ASpath-tree results ping tests across all tunnels Directed email to offending sites, especially those significantly affecting much of the 6bone So... comments and volunteers for bits of the work appreciated. Thanks, Bob From rlfink@lbl.gov Thu Apr 30 23:33:09 1998 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 30 Apr 1998 15:33:09 -0700 Subject: some 6bone backbone cleanup recommendations In-Reply-To: <199804302223.WAA06647@inner.net> References: Message-ID: <1318172105-154096108@cnrmail.lbl.gov> Craig, You make several good points. I'm not totally convinced about not doing anything, but it is an option. I do think that the routing practices draft is a good guide (or will be as it gets further cleanup/editing). Let's see what comments we collect. Thanks, Bob === At 06:23 PM 4/30/98 -0300, Craig Metz wrote: >In message , you write: >>So... comments and volunteers for bits of the work appreciated. > > I believe that there isn't currently a need for a separate mailing list, >since the set of people who would be on that list should already be on the >6Bone list and the all people who are currently on the 6Bone list should be >interested in operational issues. If the 6Bone has a massive increase in the >number of leaves and end users, this might change. The MBONE provides a good >example for us. > > I think that many of the active monitoring methods proposed are either >overkill or likely to misinterpret certain failures. I have long expressed a >concern that the volume of diagnostic traffic on the 6Bone is an order of >magnitude higher than the volume of real usage. More diagnostic traffic is not >the answer. > > I really think that the best possible way to clean up the 6Bone is to add >more leaf/end users. Why? Because most of the problems that get found and >fixed get found and fixed when somebody is trying to do something but not >succeeding. If I get a dozen emails a day warning me of possible problems and >I'm busy, it's going to wait. If one of my co-workers walks down to my office >and says "hey, can you look at this", it's getting fixed. > > Also, I'd hope that nobody here would consider trying to generate more >interest in IPv6 and more actual IPv6 users to be a bad thing. > > -Craig >