From RLFink@lbl.gov Wed Jul 2 16:44:18 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 2 Jul 1997 08:44:18 -0700 Subject: new 6bone backbone links diagram - version 21 Message-ID: new 6bone backbone links diagram - version 21 http://www.6bone.net/6bone-bblinks.html remove SURFNET tunnels to BAY, CISCO and DIGITAL-CA change UUNET/UK tunnels from RIPng to BGP4+ for TELEBIT and G6 Two things to note here: 1. The TELEBIT to UUNET BGP4+ peering is the first Cisco to non-Cisco BGP4+ peering that's been done on the 6bone (please correct me if this is wrong). 2. SURFNET cutting back extra links in the backbone mesh is a trend we should all follow to minimize links we don't need in a backbone. The purpose is NOT to fully conenct the backbone, rather to provide the links that are appropriate (don't ask me to define that one :-). Thanks, Bob From RLFink@lbl.gov Wed Jul 2 16:39:56 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 2 Jul 1997 08:39:56 -0700 Subject: new 6bone diagram - version 78 Message-ID: new 6bone diagram - version 78 http://www.6bone.net/6bone-drawing.html add JANET/UK to UUNET/UK add TELEDANMARK/DK to TELEBIT/DK add REDIRIS/ES (as transit) to SURFNET/NL add REDIRI-HQ/ES to REDIRIS/ES add IBBNET/NL to SURFNET/NL Welcome to the new sites. JANET is well known as a UK academic Internet. TELEDANMARK I know not of other than it is in Denmark. REDIRIS is a Spanish Academic and Research Network based in Madrid. IBBNET is in Utrecht, The Netherlands, and again I don't know what it does. It would be good for sites to use the descr. field in the registry to say what they are and a full name. Reminder that the hot links on the diagrams now point to the ISI ripe-style registry. Thanks, Bob From crawdad@fnal.gov Wed Jul 2 18:43:36 1997 From: crawdad@fnal.gov (Matt Crawford) Date: Wed, 02 Jul 1997 12:43:36 -0500 Subject: new 6bone backbone links diagram - version 21 In-Reply-To: "02 Jul 1997 08:44:18 PDT." <"v03102804afe026d41edb"@[128.3.9.22]> Message-ID: <199707021743.MAA21645@gungnir.fnal.gov> > 2. SURFNET cutting back extra links in the backbone mesh is a trend we > should all follow to minimize links we don't need in a backbone. The > purpose is NOT to fully conenct the backbone, rather to provide the links > that are appropriate (don't ask me to define that one :-). Is it too many links, or inappropriate default routes that makes the path from Fermilab to NIST go through France? (Or is it just bad DNS info? The embeded IPv4 prefix checks out.) I point default at ESNET, who defaults to Cisco. Cisco is routing these packets to DEC, so DEC is either defaulting to IMAG or selecting that route for some other reason. The return path is more hops, but it stays on this continent: NIST -> NRL -> CICNET -> CISCO -> ESNET -> FNAL. Tracing the route to ipng9.ipng.nist.gov (5F00:3100:8106:3300:0:C0:3302:5A) 1 5F01:2500::293:3152:1 56 msec * 56 msec 2 6bone-router-tun-esnet.cisco.inner.net (5F00:6D00:0:E:2::1) 84 msec * 88 msec 3 * 5F00:2100:CC7B:0:2:0:F842:1428 132 msec 132 msec 4 * 6bone-core.ipv6.imag.fr (5F06:B500:8158:1A00:0:800:2BB9:F33D) 300 msec 284 msec 5 luna-v6.ipv6.imag.fr (5F06:B500:8158:1A00:0:800:2075:24EA) 292 msec 320 msec 300 msec 6 * ipng9.ipng.nist.gov (5F00:3100:8106:3300:0:C0:3302:5A) 296 msec * Traceroute to 5f01:2500:83e1:0:5:40:b40:7cef: 1 ipng10.ipng.nist.gov (5f00:3100:8106:3300::f840:cde8) 2.991 ms 2.252 ms 2.196 ms 2 ipng9.ipng.nist.gov (::129.6.51.154) 3.458 ms * 3.404 ms 3 buzzcut.ipv6.nrl.navy.mil (5f00:3000:84fa:5a00::5) 14.900 ms 17.267 ms 15.834 ms 4 guar.ipv6.nrl.navy.mil (5f00:3000:84fa:5a00::3) 17.311 ms * 34.473 ms 5 6bone.chicago.cic.net (5f04:c900:8367:100:1:0:c8e:50c2) 239.570 ms 174.739 ms 232.363 ms 6 esnet-tun-endpoint.cisco.inner.net (5f00:6d00:0:e:2::2) 230.087 ms * * 7 5f01:2500::293:3152:2 (5f01:2500::293:3152:2) 307.000 ms 8 5f01:2500:83e1:0:ffff:800:2021:261e (5f01:2500:83e1:0:ffff:800:2021:261e) 316.757 ms * From RLFink@lbl.gov Wed Jul 2 18:47:16 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 2 Jul 1997 10:47:16 -0700 Subject: new 6bone backbone links diagram - version 21 In-Reply-To: <199707021743.MAA21645@gungnir.fnal.gov> References: "02 Jul 1997 08:44:18 PDT." <"v03102804afe026d41edb"@[128.3.9.22]> Message-ID: At 10:43 AM -0700 7/2/97, Matt Crawford wrote: >> 2. SURFNET cutting back extra links in the backbone mesh is a trend we >> should all follow to minimize links we don't need in a backbone. The >> purpose is NOT to fully conenct the backbone, rather to provide the links >> that are appropriate (don't ask me to define that one :-). > >Is it too many links, or inappropriate default routes that makes the >path from Fermilab to NIST go through France? (Or is it just bad DNS >info? The embeded IPv4 prefix checks out.) Good question. Makes no sense to me. Bob >I point default at ESNET, who defaults to Cisco. Cisco is routing >these packets to DEC, so DEC is either defaulting to IMAG or >selecting that route for some other reason. > >The return path is more hops, but it stays on this continent: >NIST -> NRL -> CICNET -> CISCO -> ESNET -> FNAL. > >Tracing the route to ipng9.ipng.nist.gov (5F00:3100:8106:3300:0:C0:3302:5A) >1 5F01:2500::293:3152:1 56 msec * 56 msec >2 6bone-router-tun-esnet.cisco.inner.net (5F00:6D00:0:E:2::1) 84 msec * >88 msec >3 * 5F00:2100:CC7B:0:2:0:F842:1428 132 msec 132 msec >4 * 6bone-core.ipv6.imag.fr (5F06:B500:8158:1A00:0:800:2BB9:F33D) 300 >msec 284 msec >5 luna-v6.ipv6.imag.fr (5F06:B500:8158:1A00:0:800:2075:24EA) 292 msec 320 >msec 300 msec >6 * ipng9.ipng.nist.gov (5F00:3100:8106:3300:0:C0:3302:5A) 296 msec * > > >Traceroute to 5f01:2500:83e1:0:5:40:b40:7cef: >1 ipng10.ipng.nist.gov (5f00:3100:8106:3300::f840:cde8) 2.991 ms >2.252 ms 2.196 ms >2 ipng9.ipng.nist.gov (::129.6.51.154) 3.458 ms * 3.404 ms >3 buzzcut.ipv6.nrl.navy.mil (5f00:3000:84fa:5a00::5) 14.900 ms >17.267 ms 15.834 ms >4 guar.ipv6.nrl.navy.mil (5f00:3000:84fa:5a00::3) 17.311 ms * >34.473 ms >5 6bone.chicago.cic.net (5f04:c900:8367:100:1:0:c8e:50c2) >239.570 ms 174.739 ms 232.363 ms >6 esnet-tun-endpoint.cisco.inner.net (5f00:6d00:0:e:2::2) >230.087 ms * * >7 5f01:2500::293:3152:2 (5f01:2500::293:3152:2) 307.000 ms >8 5f01:2500:83e1:0:ffff:800:2021:261e >(5f01:2500:83e1:0:ffff:800:2021:261e) 316.757 ms * From roque@cisco.com Wed Jul 2 20:49:48 1997 From: roque@cisco.com (Pedro Marques) Date: Wed, 2 Jul 1997 12:49:48 -0700 (PDT) Subject: new 6bone backbone links diagram - version 21 In-Reply-To: <199707021743.MAA21645@gungnir.fnal.gov> References: <"v03102804afe026d41edb"@[128.3.9.22]> <199707021743.MAA21645@gungnir.fnal.gov> Message-ID: <199707021949.MAA12979@pedrom-ultra.cisco.com> >>>>> "Matt" == Matt Crawford writes: >> 2. SURFNET cutting back extra links in the backbone mesh is a >> trend we should all follow to minimize links we don't need in a >> backbone. The purpose is NOT to fully conenct the backbone, >> rather to provide the links that are appropriate (don't ask me >> to define that one :-). Matt> I point default at ESNET, who defaults to Cisco. Cisco is Matt> routing these packets to DEC, so DEC is either defaulting to Matt> IMAG or selecting that route for some other reason. cisco will route through NRL if NRL does advertise those routes to us via BGP. Else we fall back to DEC's RIP annoucements. NIST should, imho, request that someone of their neighbors (and only one site) does advertise their routes into 6bone BGP. Matt> The return path is more hops, but it stays on this Matt> continent: NIST -> NRL -> CICNET -> CISCO -> ESNET -> FNAL. Nope... On the traceroute you see esnet-tun-endpoint.cisco.inner.net but this is an address on an ESnet router, not cisco. The path is NIST -> NRL -> CICNET -> ESNET -> FNAL. Routing usually works ok inside the BGP could... regards, Pedro. From Roger.Buttiens@vivaOSI.bro.dec.com Thu Jul 3 07:37:21 1997 From: Roger.Buttiens@vivaOSI.bro.dec.com (Roger Buttiens) Date: Thu, 3 Jul 1997 08:37:21 +0200 Subject: new 6bone diagram - version 78 Message-ID: <01BC878C.5438A1A0@guust.bro.dec.com> Bob, Just to announce a new site behind DIGITAL-BE : VUB-ULB, the = Universities of Brussels. =20 RIPE entries (new style) are created / updated for both ends of the = tunnel (STATIC). The DIGITAL-BE site is announcing the VUB-ULB site = via RIP to DIGITAL-CA (backbone site). It works since a couple of weeks, and I guess I can announce it now. = Please let me know if there is any problem with it. And maybe you can = include its presence on the next version of the drawing V 79 thanks and regards, Roger Buttiens, DIGITAL-BE =20 ipv6-site: DIGITAL-BE origin: AS1891 descr: Digital Equipment Corporation descr: Brussels, Belgium location: 50 45 54 N 04 25 10 E 800m country: BE prefix: 5F07:6300:C179:0:1::/80 application: ping kulderzipken.ipv6.digital.be=20 application: ping knoerifast.ipv6.digital.be=20 tunnel: IPv6 in IPv4 knoerifast.ipv6.digital.be -> = pax-6bone.pa-x.dec.com DIGITAL-CA RIPv6 tunnel: IPv6 in IPv4 knoerifast.ipv6.digital.be -> = earc-rtr.kar-x.dec.com DIGITAL-EARC RIPv6 tunnel: IPv6 in IPv4 knoerifast.ipv6.digital.be -> = vboipv6rtr.europe.digital.com DIGITAL-ETC RIPv6 tunnel: IPv6 in IPv4 knoerifast.ipv6.digital.be -> = 6bone-core.ipv6.imag.fr G6 RIPv6 tunnel: IPv6 in IPv4 knoerifast.ipv6.digital.be -> = asteurodemo1.ipv6.iihe.ac.be DIGITAL-BE STATIC contact: RB1-6BONE remarks: ipv6-site is operational since December, 12th 1996 remarks: kulderzipken (Alpha) runs Digital Unix V4.0B, IPv6 X6.0A remarks: knoerifast (RouteAbout Access EI-ISDN) runs IPv6 = #179,SW=3DT2.0-5 remarks: New tunnels added, RIP or static; send mail to contact notify: Roger.Buttiens@vivaOSI.bro.dec.com changed: Roger.Buttiens@bro.mts.dec.com 19970422 changed: auto-dbm@ISI.EDU 19970608 changed: Buttiens@mail.dec.com 19970609 changed: Roger.Buttiens@vivaOSI.bro.dec.com 19970702 source: 6BONE From pink@fsz.bme.hu Thu Jul 3 11:23:06 1997 From: pink@fsz.bme.hu (Szabolcs Szigeti (PinkPanther)) Date: Thu, 3 Jul 1997 12:23:06 +0200 (MET DST) Subject: Yet another ping-stat page and traceroute server In-Reply-To: <9706042117.AA27812@brind.isi.edu> Message-ID: Howdy, I'm happy to announce yet another 6bone ping statistics page at http://tracy.ipv6.fsz.bme.hu/pingstat/6bone-stats.html and a traceroute server at http://tracy.ipv6.fsz.bme.hu/tools/traceroute.html This is located at the Technical University of Budapest, Dept. of Process Control (BME-FSZ). -------------------------------------------------------------- | Szabolcs Szigeti | pink@fsz.bme.hu | | Electrical Engineer | http://www.fsz.bme.hu/~pink/ | | No woman, No Cray! | +3630218697 | -------------------------------------------------------------- From Alain.Durand@imag.fr Thu Jul 3 11:10:18 1997 From: Alain.Durand@imag.fr (Alain Durand) Date: Thu, 3 Jul 1997 12:10:18 +0200 Subject: new 6bone backbone links diagram - version 21 In-Reply-To: Matt Crawford "Re: new 6bone backbone links diagram - version 21" (Jul 2, 12:43pm) References: <199707021743.MAA21645@gungnir.fnal.gov> Message-ID: <970703121018.ZM3368@rama.imag.fr> On Jul 2, 12:43pm, Matt Crawford wrote: > Subject: Re: new 6bone backbone links diagram - version 21 > > 2. SURFNET cutting back extra links in the backbone mesh is a trend we > > should all follow to minimize links we don't need in a backbone. The > > purpose is NOT to fully conenct the backbone, rather to provide the links > > that are appropriate (don't ask me to define that one :-). > > Is it too many links, or inappropriate default routes that makes the > path from Fermilab to NIST go through France? (Or is it just bad DNS > info? The embeded IPv4 prefix checks out.) It's something a little bit different: I have a short prefix for a direct static tunnel to NIST that I'm re-advertising through RIPng The problem is a route aggregation one because NIST is advertising longer prefixes. Somewhere in the routing cloud, the aggregation is wrong. Things should be better when we'll be all runing an EGP. I'm in vacation now, when I'll return, I will also shut down many tunnels to simplify the routing in the 6-bone. - Alain. From marcus@cwi.net.au Thu Jul 3 14:50:23 1997 From: marcus@cwi.net.au (Marcus B) Date: Thu, 03 Jul 1997 23:50:23 +1000 Subject: Attach point Message-ID: <33BBAE1F.67B6B0B9@cwi.net.au> I am in Australia, to locate my exact point traceroute 203.62.165.1, whch is the router I hook into, which goes to telstra.net in Australia, I have two linux computers and I would like to get to know how IPv6 works so I will be setting these up on a mini-network. Will I have to setup BIND? if so I can do it on one computer. I will not have my computers on 7 days a week, but hopefully I will soon. From Dransfield@mail.dec.com Thu Jul 3 23:10:27 1997 From: Dransfield@mail.dec.com (Mike Dransfield) Date: Fri, 4 Jul 1997 08:10:27 +1000 Subject: Attach point Message-ID: Marcus, If you want to connect to the 6bone, then I have an IPV6 router connected to Telstra at ip6router.digital.com.au (I haven't updated the RIPE database yet) which you can connect to It is a good idea to setup BIND and most sites create an ipv6 domain (so with IPV6 addresses the above router is ip6router.ipv6.digital.com.au) Regards, Mike email: mike@stl.dec.com phone (02) 9561 5397 >---------- >From: Marcus B[SMTP:marcus@cwi.net.au] >Sent: Thursday, July 03, 1997 11:50 PM >To: 6bone@ISI.EDU >Subject: Attach point > >I am in Australia, to locate my exact point traceroute 203.62.165.1, >whch is the router I hook into, which goes to telstra.net in Australia, >I have two linux computers and I would like to get to know how IPv6 >works so I will be setting these up on a mini-network. >Will I have to setup BIND? if so I can do it on one computer. I will >not have my computers on 7 days a week, but hopefully I will soon. > From nunes@blader.com Mon Jul 7 15:28:28 1997 From: nunes@blader.com (Daniel Ferreira Nunes de Oliveira) Date: Mon, 07 Jul 1997 11:28:28 -0300 Subject: 6bone attachment point Message-ID: <33C0FD0C.7D3F@blader.com> Dear srs, We're running a small Linux based two-machines IPv6 network (alread using RFC1897 addresses) at USP (Sao Paulo University), southeast of Brazil, and it would be great to configure a router and tunnel to the 6bone. I'd like to know what's the best attachment point to join the 6bone and would apreciatte a lot your help. Thanks in advance and best regards Nunes, D. /----------------------------------------------------------------------\ |Daniel Nunes |home phone: +55 16 271-1976 | |Graduated student of Computer Science |home adress: R.Abrahao Joao,950| |ICMSC-USP - Universidade de Sao Paulo | Jd Bandeirantes | |daniel@lcad.icmsc.sc.usp.br | S.Carlos-SP.BRAZIL| |nunes@blader.com | 13562-150 | \----------------------------------------------------------------------/ From aness01@dcs.bbk.ac.uk Tue Jul 8 17:23:34 1997 From: aness01@dcs.bbk.ac.uk (Mr Nicholas George Dennison Ness MSc Comp 96ft ) Date: Tue, 8 Jul 1997 17:23:34 +0100 Subject: No subject Message-ID: <199707081623.RAA09154@zeus> Hi, I am looking for an entry point to the 6bone and would be very grateful for any advice you could give me on who I might approach. I am situated at Birkbeck College, Univesity of London. Many thanks N Ness From bmanning@ISI.EDU Tue Jul 8 18:23:06 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 8 Jul 1997 10:23:06 -0700 (PDT) Subject: delegation Message-ID: <199707081723.AA29251@zed.isi.edu> Enjoy. ;; QUESTIONS: ;; 0.0.4.6.c.0.f.5.IP6.INT, type = NS, class = IN ;; ANSWERS: 0.0.4.6.c.0.f.5.IP6.INT. 129600 NS archangel.ecs.soton.ac.uk. 0.0.4.6.c.0.f.5.IP6.INT. 129600 NS scorpio.ecs.soton.ac.uk. ... ;; QUESTIONS: ;; 0.0.0.3.2.0.f.5.ip6.int, type = NS, class = IN ;; ANSWERS: 0.0.0.3.2.0.f.5.ip6.int. 129600 NS birbal.iol.unh.edu. 0.0.0.3.2.0.f.5.ip6.int. 129600 NS sparky.iol.unh.edu. -- --bill From RLFink@lbl.gov Tue Jul 8 22:08:51 1997 From: RLFink@lbl.gov (Bob Fink) Date: Tue, 8 Jul 1997 14:08:51 -0700 Subject: In-Reply-To: <199707081623.RAA09154@zeus> Message-ID: Nicholas, At 9:23 AM -0700 7/8/97, aness01@dcs.bbk.ac.uk (Mr Nicholas George Dennison Ness ... >I am looking for an entry point to the 6bone and would be very grateful for >any advice you could give me on who I might approach. >I am situated at Birkbeck College, Univesity of London. Try either: duncan@nosc.ja.net of the JANET project or Guy.Davies@uunet.pipex.com of UUNET-UK Bob From RLFink@lbl.gov Wed Jul 9 18:42:20 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 9 Jul 1997 10:42:20 -0700 Subject: new 6bone backbone links diagram - version 22 Message-ID: new 6bone backbone links diagram - version 22 http://www.6bone.net/6bone-bblinks.html change link from TELEBIT/DK to SURFNET/NL from RIPng to BGP4+ add link from G6/FR to SURFNET/NL using BGP4+ Thanks, Bob From warlock@csuchico.edu Fri Jul 11 21:10:26 1997 From: warlock@csuchico.edu (John Kennedy) Date: Fri, 11 Jul 1997 13:10:26 -0700 Subject: multistack migration issues Message-ID: <199707112010.NAA25494@hircine.net.chico.ca.us> 07/11/97 @ 01:09:53 PM (Friday) Does anyone have a good feel for all of the issues involved in supporting applications across multistack (IPv4 & IPv6) platforms? For example, I've been hacking IPv6 support into 8.8.7.Beta2. Along with all the usual AF_INET -> AF_INET6 porting I ran into everyday situations like DNS lookups. For example, lets look at the typical "Received:" line: Received: from menkure.net.CSUChico.EDU (menkure.net.CSUChico.EDU [::ffff:132.241.66.6]) by hircine.net.chico.ca.us (8.8.7.Beta2+ipv6/8.8.7.Beta2) with ESMTP id MAA25407 for ; Fri, 11 Jul 1997 12:04:25 -0700 The first "menkure" is given to me in the EHLO. The ::ffff:132.241.66.6 I get from the socket, but the 2nd menkure I actually create while trying to verify if someone is forging or otherwise giving bad information. If this was just straight IPv4 or IPv6 you'd take the address, do a reverse-lookup, forward-lookup the result and make sure the address you started with matches one (of potentially many) from the forward-lookup. In this mixed environment, I was stuck. I didn't have a reverse-lookup for ::ffff:132.241.66.6 and, while I could bloat up DNS with all of my local addresses, that doesn't do anything for the rest of the world. In my port, I decided to try it and, if it failed and the non-IPv4 portion of ::ffff:132.241.66.6 was ::ffff:0, I'd try a regular IPv4 reverse-lookup on the hostname. Is that what everyone is expected to do? I guess I'm just afraid that ::ffff:0/96 will become "non-unique". IE, when the final crunch comes someone is going to grab some networks and there is going to be X's ::ffff:1.2.3.4 as well as Y's ::ffff:1.2.3.4 network out there, pretty much breaking IPv4/DNS as we know it. [By IPv4-DNS I mean DNS RRs made for the 32-bit world.] Give then ::ffff:0 is supposed to be a special address I don't think that will happen but designer mentality changes more rapidly than printed dead-tree (books). (: Most of what I read makes it sound as if IPv6-ignorant ::ffff:0 hosts will be proxy-bait. If they are proxy-bait, IPv4-DNS should continue to linger for as long as it's useful in its current capacity (no dupes). --- john From roque@cisco.com Sat Jul 12 00:22:51 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 11 Jul 1997 16:22:51 -0700 (PDT) Subject: multistack migration issues In-Reply-To: <199707112010.NAA25494@hircine.net.chico.ca.us> References: <199707112010.NAA25494@hircine.net.chico.ca.us> Message-ID: <199707112322.QAA24436@irp-view4.cisco.com> >>>>> "John" == John Kennedy writes: John> 07/11/97 @ 01:09:53 PM (Friday) Does anyone have a good feel John> for all of the issues involved in supporting applications John> across multistack (IPv4 & IPv6) platforms? John> For example, I've been hacking IPv6 support into John> 8.8.7.Beta2. Along with all the usual AF_INET -> AF_INET6 John> porting I ran into everyday situations like DNS lookups. John> For example, lets look at the typical "Received:" line: John> Received: from menkure.net.CSUChico.EDU John> (menkure.net.CSUChico.EDU [::ffff:132.241.66.6]) by John> hircine.net.chico.ca.us (8.8.7.Beta2+ipv6/8.8.7.Beta2) with John> ESMTP id MAA25407 for ; John> Fri, 11 Jul 1997 12:04:25 -0700 John> The first "menkure" is given to me in the EHLO. The John> ::ffff:132.241.66.6 I get from the socket, but the 2nd John> menkure I actually create while trying to verify if someone John> is forging or otherwise giving bad information. John> If this was just straight IPv4 or IPv6 you'd take the John> address, do a reverse-lookup, forward-lookup the result and John> make sure the address you started with matches one (of John> potentially many) from the forward-lookup. That is exactly what you should do. John> In this mixed environment, I was stuck. I didn't have a John> reverse-lookup for ::ffff:132.241.66.6 and, while I could John> bloat up DNS with all of my local addresses, that doesn't do John> anything for the rest of the world. In my port, I decided John> to try it and, if it failed and the non-IPv4 portion of John> ::ffff:132.241.66.6 was ::ffff:0, I'd try a regular IPv4 John> reverse-lookup on the hostname. A reverse lookup for ::ffff:132.241.66.6 can only be a query for 6.66.241.132.in-addr.arpa. John> Is that what everyone is expected to do? Use getnameinfo(). At least NRL's version does correctly recognize mapped addresses and makes the PTR query to the in-addr.arpa name space. Pedro. From W. Richard Stevens" [In your message of Jul 11, 1:10pm you write:] > > In this mixed environment, I was stuck. I didn't have a reverse-lookup > for ::ffff:132.241.66.6 and, while I could bloat up DNS with all of my > local addresses, that doesn't do anything for the rest of the world. In > my port, I decided to try it and, if it failed and the non-IPv4 portion > of ::ffff:132.241.66.6 was ::ffff:0, I'd try a regular IPv4 reverse-lookup > on the hostname. > > Is that what everyone is expected to do? Assuming a recent BIND with IPv6, gethostbyaddr() takes ::ffff:132.241.66.6 and does the right thing (an in-addr.arpa search). Paul Vixie documented this in draft-vixie-ipng-ipv4ptr-00.txt, and since this draft has expired he was going to submit a new version a week or so ago. BIND does these in-addr.arpa searches for IPv4-mapped and IPv4-compatible addresses. Rich Stevens From roque@cisco.com Sun Jul 13 23:43:30 1997 From: roque@cisco.com (Pedro Marques) Date: Sun, 13 Jul 1997 15:43:30 -0700 (PDT) Subject: rip routes Message-ID: <199707132243.PAA17689@pedrom-ultra.cisco.com> I ran a small script on cisco's 6bone-router RIP table trying to find out the average metrics on the RIP routes. Note that cisco doesn't receive all rip routes (we filter inbound all the prefixes we source into bgp and some other prefixes we have bgp routes to). As an heuristic i picked 5 as the maximum path length between cisco an any site trying to spot routes with a metric which is too high. This most likely falls in the category of useless statistics but what the heck... some of you even may find this interesting. Pedro. ------------------------------------------------------------------------------ metric routes percentage ------------------------------------------------------------------------------ 2 9 7.0% 3 44 34.4% 4 21 16.4% 5 14 10.9% 6 10 7.8% 7 7 5.5% 8 3 2.3% 9 1 0.8% 10 1 0.8% 12 1 0.8% 15 6 4.7% 16 11 8.6% total 134 100.0% ------------------------------------------------------------------------------ Possibly bogus RIP routes ------------------------------------------------------------------------------ route metric ------------------------------------------------------------------------------ 5F02:2F00::0/32 16 5F06:B500:8158:1A00::0/80 16 5F0B:2900::0/32 16 5F00:3100::0/32 16 5F02:3000::0/32 16 5F07:3D00:8DC9:200:2::0/80 16 5F0B:1700:C047:1400::0/64 16 5F06:B500:8158:1A00:1:0:8158:1A01/128 16 5F0C:B300::0/32 16 5F15:9100::0/32 16 5F00:3100:8106:3300::0/80 16 5F00:1000:0:F:C::0/80 15 5F00:1000:0:F:D::0/80 15 5F00:1000:0:F:F::0/80 15 5F03:1200:C13F:AF00::0/64 15 5F03:1200:C13F:AF01::0/64 15 5F03:1200:C13F::0/48 15 5F02:3000:8DFB:D101::0/64 12 5F09:F300:9842:4C00:4C:0:C067:7B99/128 10 5F02:3000:8DFB:D100::0/64 9 5F1A:6D00:C269:A600::0/64 8 5F0D:E900:80DF::0/48 8 5F0D:E900:9EA5::0/48 8 5F0C:DC00::0/32 7 5F0A:3600::0/32 7 5F07:5F00::0/32 7 5F0A:2F00:93AF:6300::0/80 7 5F0B:1700:C10A:4200::0/80 7 5F02:AD00::0/32 7 5F0B:1700:82EC::0/48 7 5F15:4100:839A:300::0/80 6 5F0C:BF00::0/32 6 5F07:2B00:82E1:F700:1A::0/80 6 5F00:1B00:8008::0/48 6 5F02:BD00:C626::0/48 6 5F07:2B00:82E1:F700:22::0/80 6 5F02:FE00::0/32 6 5F00:E000:81F0:1700::0/64 6 5F00:3000:C721:F800::0/64 6 5FFF:B400:C0E7:B00::0/64 6 total number of bogus routes: 40 percentage: 31% From chandra@usa.net Mon Jul 14 05:39:27 1997 From: chandra@usa.net (Chandra Shekar Nanjappa) Date: Mon, 14 Jul 1997 04:39:27 Subject: Reg. mails Message-ID: Hi, As I'm not interested in mails belonging to 6bone <6bone@isi.edu>, how to disconect myself from that? Chandra From RLFink@lbl.gov Mon Jul 14 15:37:42 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 14 Jul 1997 07:37:42 -0700 Subject: Reg. mails In-Reply-To: Message-ID: At 4:39 AM -0700 7/14/97, Chandra Shekar Nanjappa wrote: >Hi, >As I'm not interested in mails belonging to 6bone <6bone@isi.edu>, how >to disconect myself from that? >Chandra Per the 6bone mail list web page: To unsubscribe to the 6bone mail list, send a message to majordomo@isi.edu with the line unsubscribe 6bone as the contents of the message. Thanks, Bob From RLFink@lbl.gov Mon Jul 14 17:49:34 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 14 Jul 1997 09:49:34 -0700 Subject: sourcs of testing software Message-ID: A good suggestion from Mark Waters. Any comments or ideas on what is appropriate? Bob ================================== >Date: Mon, 14 Jul 1997 17:28:15 -0700 >From: mark waters >To: RLFink@lbl.gov >Subject: sourcs of testing software > >Hello, >After following the hypertext from the 6Bone tools site I was hoping >that there may some testing source code available... >As part of an experimental 6Bone project, source code would be >appreciated or even a pointer in the general direction of any available >code for retrieving statistics. >thanking you in advance, >Mark Waters > >Broadcom Eireann Research >Kestrel House >Clanwilliam Place >Dublin 2 >+353-1-6046014 > From RLFink@lbl.gov Mon Jul 14 18:45:21 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 14 Jul 1997 10:45:21 -0700 Subject: new 6bone backbone links diagram - version 23 Message-ID: new 6bone backbone links diagram - version 23 http://www.6bone.net/6bone-bblinks.html remove UUNET/UK link to NWNET/US to reduce backbone meshing Thanks, Bob From RLFink@lbl.gov Mon Jul 14 19:21:46 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 14 Jul 1997 11:21:46 -0700 Subject: new 6bone diagram - version 79 Message-ID: new 6bone diagram - version 79 http://www.6bone.net/6bone-drawing.html make DIGITAL/BE a transit and add new site VUB-ULB/BE add new site UNIMI/IT to POLITO/IT add new site IBN/IT to CSELT/IT add new site CABLEINET/UK to UUNET/UK add new site NETCOM/UK to UUNET/UK Welcome to: VUB-ULB/BE - Vrije Universiteit Brussel - Universite Libre de Bruxelles, Brussels, Belgium UNIMI/IT - Dipartimento Scienze dell'Informazione, Universita' degli Studi di Milano, Milano, Italia IBN/IT - IBN - Windmill Labs, Borgomanero, Novara, ITALY CABLEINET/UK - NO registry entry NETCOM/UK - NETCOM Internet (UK) Ltd., UK Thanks, Bob From bmanning@ISI.EDU Wed Jul 16 17:43:27 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Wed, 16 Jul 1997 09:43:27 -0700 (PDT) Subject: Welcome Message-ID: <199707161643.AA03599@zed.isi.edu> ;; QUESTIONS: ;; 0.0.b.3.0.2.f.5.ip6.int, type = NS, class = IN ;; ANSWERS: 0.0.b.3.0.2.f.5.ip6.int. 129600 NS ns1.elm.net. 0.0.b.3.0.2.f.5.ip6.int. 129600 NS ns2.elm.net. 0.0.b.3.0.2.f.5.ip6.int. 129600 NS ns2.cistron.nl. -- --bill From pouffary@taec.enet.dec.com Thu Jul 17 00:07:31 1997 From: pouffary@taec.enet.dec.com (Yanick) Date: Wed, 16 Jul 97 23:07:31 MET DST Subject: New DIGITAL OpenVMS node on the 6Bone Message-ID: <199707162106.XAA27615@vbormc.vbo.dec.com> Hi We are happy to announce a new addition to the DIGITAL IPv6 family on the 6bone, an OpenVMS Alpha running IPv6. IPv6 on DIGITAL OpenVMS is based on a port of the DIGITAL UNIX IPv6 stack. At the DIGITAL-ETC (Digital in Sophia) we now have - DIGITAL RouteAbout Access EI-ISDN /IPv6 (5F06:B500:C138:F00::F8A4:8428) running RtAbt Acces EW/IP IPv6 #1669,SW=T2.0-5 vboipv6rtr.ipv6.europe.digital.com - DIGITAL UNIX AlphaServer (5F06:B500:C138:F00::800:2B36:701E) running DIGITAL UNIX V4.0B, IPv6 X6.0A vboipv6unix.ipv6.europe.digital.com - DIGITAL OpenVMS AlphaServer (5F06:B500:C138:F00::F822:4C09) running DIGITAL TCP/IP services for OpenVMS Alpha Version V7.1, IPv6 X5.0A vboipv6ovms.ipv6.europe.digital.com See the digital-etc whois entry or http://www.digital.com/info/ipv6 for more details. Regards Yanick Pouffary DIGITAL TCP/IP services for OpenVMS IPv6 Kernel Team ------------------------ Yanick Pouffary pouffary@taec.enet.dec.com DIGITAL Equipment Corporation +33 (0)4.9295.6285 Centre Technique Europe, Sophia Antipolis France From bc@ecs.soton.ac.uk Thu Jul 17 14:04:08 1997 From: bc@ecs.soton.ac.uk (Ben Crosby) Date: Thu, 17 Jul 1997 14:04:08 +0100 Subject: Sites that are running statistics... Message-ID: <3.0.1.32.19970717140408.006a143c@152.78.114.70> Hi people, This is just a request for some answers to a few things. We're now officially using the RIPE style registry, so should the FTP records also be updated when we update our RIPE style entry? If the answer is no, and I hope it is =), then please, please could I urge those of you who are running any kind of statistics monitoring, e.g. ping, to update your scripts to use the RIPE style database. My site record was recently updated, yet the old IP addresses are still being bombarded with ICMP echo-requests.... =/ Thanks, Ben. From RLFink@lbl.gov Thu Jul 17 17:30:00 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 17 Jul 1997 09:30:00 -0700 Subject: Sites that are running statistics... In-Reply-To: <3.0.1.32.19970717140408.006a143c@152.78.114.70> Message-ID: Ben, At 6:04 AM -0700 7/17/97, Ben Crosby wrote: >Hi people, > > This is just a request for some answers to a few things. >We're now officially using the RIPE style registry, so should the FTP >records also be updated when we update our RIPE style entry? > >If the answer is no, and I hope it is =), then please, please could I urge >those of you who are running any kind of statistics monitoring, e.g. ping, >to update your scripts to use the RIPE style database. > >My site record was recently updated, yet the old IP addresses are still >being bombarded with ICMP echo-requests.... =/ Thanks for bringing this up. I will soon announce that we will remove the old ftp-based directory entirely so we can avoid this problem (hoping, of course, that folk convert their stuff as you request). Sooo...everyone should only be using the new ripe-based registry. Thanks, Bob From RLFink@lbl.gov Fri Jul 18 18:30:30 1997 From: RLFink@lbl.gov (Bob Fink) Date: Fri, 18 Jul 1997 10:30:30 -0700 Subject: 6bone Agenda for Munich - draft version of 18Jul97 Message-ID: Gentle 6bone folk, The following is my first draft of an agenda for the ngtrans 6bone session. Please comment, to the mailer, to make adds, changes and deletions, especially re the action items and items I need suggestions for. I'm sure I'm missing many items we should be talking about, so please let me know :-) Remember that the 6bone activity is now part of ngtrans, so you have to take care to attend the right ngtrans meeting. The ngtrans meetings are now scheduled as follows: >This is to confirm three 1-hour session for NGTRANS as follows: > > Tuesday, August 12 at 1415-1515 (opposite isn, bmwg, pppext, idmr > Tuesday, August 12 at 1545-1800 (opposite grip, run, tn3270e, poisson > ftpect, mobileip, mmusic) > >Combining the 1545-1645 and 1700-1800 sessions counts as one normal session. The first session is the old transition tools meeting, the combined 1545 session is for the 6bone. Thanks, Bob ================================================================================ ngtrans-6bone Agenda - Munich IETF Tuesday, August 12, 1545-1800 (with a cookie break at 1645 :-) 1. Introduction and agenda bashing - Bob Fink 2. Status of Action Items from Memphis 2.1. CAIRN Backbone Proposal - Allison Mankin (Allison should give an update on her proposal/plans) 2. 2. RFC1987 changes to use virtual IPv6 provider ID - Hsin Fang (are we abandoning or closing this - Hsin?) 2.3. Aggregation-Based Addressing Structure for 6bone - Bob Fink (will result in the overview Bob Fink will do shown below) 2.4. I-D "Representing IPv6 Tunnels in RPSL" - David Meyer (maybe this is closed - Dave?) 2.5. New 6BONE registry - David Kessens (David should give a report on this) 2.6. DNS for localized 6bone routing registry information - Bill Manning (maybe this is closed - Bill?) 2.7. Volunteers for I-D on requirements for new 6bone infrastructure - Bob Fink (Bob will give status) 2.8. Survey of host and router implementations on 6bone - Bob Fink (no progress, let's discuss what's appropriate to do - Bob Fink) 3. Backbone/Transit Planning 3.1. connectivity among backbone sites 3.2. policies for becoming a backbone site 3.3. 6bone connectivity planning in the UK 3.4. other?? 4. ip6.int versus icmp-based address lookup 4.1. do we continue with ip6.int or rely on the new icmp mechanism? (not promoting here, just wanting to have our direction clear - Bob) 4.2. other?? 5. Test Addressing Plan 5.1. Overview - Bob Fink 5.2. Assigning test addresses - XXXX 5.3. Making the conversion on the 6bone - XXXX 5.4. other?? 6. Testing site renumbering - need suggestions , if any 7. Applications - need suggestions , if any 8. New implementations - need suggestions , if any 9. New tools - need suggestions, if any -end From davidk@isi.edu Fri Jul 18 20:23:05 1997 From: davidk@isi.edu (davidk@isi.edu) Date: Fri, 18 Jul 1997 12:23:05 -0700 (PDT) Subject: 6bone site list? In-Reply-To: from "Mike Dransfield" at Jul 18, 97 05:02:09 pm Message-ID: <9707181923.AA17750@brind.isi.edu> [ CC'ed to the 6bone list since the message might be of general interest ] Hi Mike, Mike Dransfield writes: > > Is there a way to get a list of all the 6bone sites? > I couldn't find a way using the whois interface to get one. There is no support for this in the whois server for scalability reasons. However, every day a full dump of all the data in the registry is made available which you can use for this purpose. The dump is available from: ftp://whois.6bone.net/6bone/6bone.db.gz I hope this helps, David K. --- From emace@bcm.tmc.edu Tue Jul 22 16:38:41 1997 From: emace@bcm.tmc.edu (Scott Mace) Date: Tue, 22 Jul 1997 10:38:41 -0500 (CDT) Subject: connection to 6bone Message-ID: <199707221538.KAA12061@bandicoot.ssctr.bcm.tmc.edu> I am an engineer at Baylor College of Medicine. We are interested in connecting to the 6bone. We have a handful of sparcstations here running the Solaris ipv6 code. Thanks, Scott From RLFink@lbl.gov Tue Jul 22 17:24:30 1997 From: RLFink@lbl.gov (Bob Fink) Date: Tue, 22 Jul 1997 09:24:30 -0700 Subject: various 6bone web page changes Message-ID: I have finally caught up with additions to the "other v6 sites", "tools" and "stats" web pages. Please let me know if you have more. Thanks, Bob From zvezdi@plovdiv.uspc.bg Wed Jul 23 08:39:27 1997 From: zvezdi@plovdiv.uspc.bg (Zvezdelin Vladov) Date: Wed, 23 Jul 97 10:39:27 +0300 Subject: HI! Message-ID: Hello again from Bulgaria (southeastern Europe). I don't know if it is appropriate to write these things here, but if it is not, I beg you pardon me. You need about 5 minutes to read this. In few words, I'll try to explain two things: 1. Physical Structure of the Connections in Bulgaria 2. Logical Structure of the Internet Connections in Bulgaria. 3. Question - How can I get connected to 6BONE? 1. Physical Structure. Bulgarian Telecommunication Company (BTC) has the following structure deployed in the country, with the money from European Union. SDH/PDH as part of the SONET specification running at 155 Mb/s. The country is devied into 2 main regions -- eastern optical ring and western optical ring. The rings are from different vendors -- as far as I know - Alcatel and Northern Telecom. They are linked in two points thru getting down the 155 Mb/s in Nx2Mb/s links in two cities in the country. The BTC says that they already use the SDH for intracity phonecalls. The PDH is in the capital city (Sofia). There are firms which are deploying xDSL technologies in the capital and other cities. Internet has never been carried into this structure, because of small market for Internet services, and for problems from BTC. The BTC until recently could only give you 2Mb/s as the smallest link capacity throughout the country via the SDH. Until now, because it bought multyplexers for 2Mb/s=Nx64Kb/s. Still it is expensive, but if you want to have connection from some city to the capital, for example, in terms of capacity the only choice you would have is to do it the hard way -- which means you lease lines, as many as you need, but the only speed you could get per link, as maximum, is 28.8 Kb/s, thru analog connection from one city to the capital. Now are available, the digital links, but many people think that they are expensive. Also, thru the tactical move, called "try & buy" principle, IBM-Bulgaria has been able to install ATM testbed in one area of the capital city, though, for good or bad, officals from BTC say, that "why should we buy ATM, as we already have SDH deployed". We have offices of the major telecomunication companies --- AT&T, MCI, Northern Telecom. BTC these days said that it is going to buy 2Mb/s channel to the Internet from IBM, which is going to strike very hard the local ISPs which buy the way, sells at least 2,3,4 times the link capacity, and in this way it is close to impossible to use Internet. To the customer is presented the an offer of like this -- 60 USD inital tax for connecting and after this 25 USD per month for 60 hours of time online without limit for the data transfer, and the ISP have 33.6 Kb/s modems. 2. Logical Structure. The very first of the ISPs which came out in the market is called Digital Systems. This is one of the oldest one -- started operations about 1993. It is connected to EUNET in Amsterdam. It is the one who is maintaining the DNS database ( well, most of it ). Now, the company (its service) is unusable, because of overselling its structure. So, speeds like 30/40 bytes per second and even less are not unlikely to be seen. They don't have any customer service until recently. Their address is www.digsys.bg, www.eunet.bg. As someone can notice from its name, they could really dig you in the earth :)--DigSys:). There are other ISPs, most of the linked to EU structure, but there are few linked to US, as well, thru satellite dish and Global One and a little firm which is distributor of Digital Expres Net -- digex.net, called Spectrum PCT LTD--their web: www.spct.net (spct=spectrum Pct.net). 3. Question I have connection to resseler of Spectrum PCT. How Can I switch to 6BONE? You can assume that I have Linux BOX, and I have read most of the RFC dedicated to IPv6 except IPSEC RFC. So, I can configure my Linux box, to tunnel IPv6 into IPv4 packets. I can talk with Spectrum to make them think on moving into IPv6 area, if they haven't done this yet. Thanks for reading, and I am sorry, If I took too much of your time. Have a nice time. Zvezdelin Vladov --- /**************************************************************************** * Zvezdelin Vladov, Assistant, United States Peace Corps - Bulgaria * * Phones: 35932 226546; 35932 272009; fax: 35932 563382; City of Plovdiv * ****************************************************************************/ From zvezdi@plovdiv.uspc.bg Wed Jul 23 09:13:28 1997 From: zvezdi@plovdiv.uspc.bg (Zvezdelin Vladov) Date: Wed, 23 Jul 97 11:13:28 +0300 Subject: Additional Info on Bulgaria Connections! Message-ID: A qucik adding note to the previous description of Bulgaria's connections: 4. National Academic Network - domain name 'acad.bg' There is national academic network run with the support of many organizations, but right now it is a little bit slow. In the capital city, though, three of the biggest universities are conneted into an FDDI optical ring(100Mb/s). But for the other participiants from the country the links are no more than the usual analog one - 28.8 Kb/s to Sofia(the capital city). This network is mainly financed from TEMPUS --a European Union's project. 5. Public Data Networks -- Used mainly for hacking :( -- The last well know case -- a famous virus writer has became a hacker and thru X.25's country wide public data network and thru its connection to the outside world (the capacity of this outside link is in Kb/s range) has been able to get into the computers of one of the oldest state universities -- University of Sofia. He calls himself dav -- Dark Avanger. So, check out your /etc/passwd or similar file and if you find something like unknown user called 'dav' it is better to pull out you internet cable for couple of hours. This guy went to US thru X.25 and from there manipulating DNS protocol, and thru a bug in Talk Demon goes into your system into the root account. After this he creates user called dav. Check this out -- He got into the computers of the University of Sofia at the speed of 2400 b/s (2400 bits per second!) and has used some scripts to add himself to the /etc/passwd file. He's used also 'vi' to add himself to the /etc/passwd list. This thing happend about December 1996, and report has been generated to CERT. Sorry if this is too much info for you. Zvezdelin Vladov --- /**************************************************************************** * Zvezdelin Vladov, Assistant, United States Peace Corps - Bulgaria * * Phones: 35932 226546; 35932 272009; fax: 35932 563382; City of Plovdiv * ****************************************************************************/ From 6bone@snad.ncsl.nist.gov Wed Jul 23 13:29:39 1997 From: 6bone@snad.ncsl.nist.gov (Robert Glenn) Date: Wed, 23 Jul 1997 08:29:39 -0400 (EDT) Subject: Sites that are running statistics... Message-ID: <199707231229.IAA19582@snad.ncsl.nist.gov> The stats page here at NIST is now using the new registry to gather its data. I have noticed (as others will if they take a look at the page) that the "ping: ....." lines didn't carry to the new registry with the switch over. As a result, there are a large percentage of sites in the registry with "No Pingable Addresses" and will show up as such on the stats page until an "application: ping ...." entry is added to those particular entries. (I apologize if you have already seen this message). Rob G. rob.glenn@nist.gov 6bone Reachability Status From NIST URL: http://www.antd.nist.gov/~ipng/NIST-6bone-status.html From Ivano.Guardini@CSELT.IT Wed Jul 23 15:47:45 1997 From: Ivano.Guardini@CSELT.IT (Guardini Ivano) Date: Wed, 23 Jul 1997 16:47:45 +0200 Subject: New 6Bone stats from CSELT Message-ID: Hi all, I have updated the CSELT 6Bone statistics which are accessible at the following URL: http://carmen.stet.it/ipv6/stats/stats.html These statistics are collected according to the 6Bone topology in order to help the user to undestand the reason of a site unreachability (e.g. the unreachability of a leaf site could be due to the unreachability of its actual transit site or backbone site). In addition to some pages showing the IPv6 and IPv4 packet loss and RTT towards each known site, the new CSELT 6Bone statistics include a first page providig a reachability overview table reflecting the 6Bone topology: backbone sites in the first column, transit sites in the second column and leaf sites in the following columns. Each row represents a tree inside 6Bone rooted at a backbone site. If you find this work interesting or if you have some suggestions or comments please let me know. 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 Jul 23 16:07:16 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 23 Jul 1997 08:07:16 -0700 Subject: HI! In-Reply-To: Message-ID: Zvezdelin, At 12:39 AM -0700 7/23/97, Zvezdelin Vladov wrote: ... >3. Question >I have connection to resseler of Spectrum PCT. How Can I switch to 6BONE? >You can assume that I have Linux BOX, and I have read most of the RFC dedicated >to IPv6 except IPSEC RFC. So, I can configure my Linux box, to tunnel IPv6 >into IPv4 packets. I can talk with Spectrum to make them think on moving into >IPv6 area, if they haven't done this yet. It would seem that your best bet is to tunnel to SURFNET/NL as they have excellent connectivity in the Amsterdam area, and I see the route my site (which uses ESnet) takes to reach you is through the eu.net paths from the US thru Amsterdam and on to Sofia. Your contact at SURFNET would be Erik-Jan Bos: Erik-Jan.Bos@surfnet.nl Thanks for the interesting insight into telecomm/networking in Bulgaria. I hope to soon be able to add BG to the 6bone country list! Regards, Bob ======================= Monaco0000,0000,FFFFFind route from: 128.3.9.22 0000,0000,FFFF to: plovdiv.eunet.bg. (193.68.2.1), Max 30 hops, 40 byte packets 0000,0000,FFFFHost Names truncated to 320000,0000,FFFF bytes 1 ir30gw.lbl.gov. (128.3.9.1 ): 2ms 1ms 1ms 2 er1gw.lbl.gov. (131.243.128.11 ): 2ms 1ms 1ms 3 lbl-lc1-1.es.net. (198.128.16.11 ): 2ms 2ms 1ms 4 cebaf-atms.es.net. (134.55.24.7 ): 61ms 60ms 60ms 5 dccon-cebaf-mae-e.es.net. (134.55.24.166 ): 67ms 67ms 66ms 6 vienna2.va.us.eu.net. (192.41.177.120 ): 72ms 70ms 70ms 7 pennsauken1.nj.us.eu.net. (134.222.228.2 ): 72ms 70ms 70ms 8 amsterdam2.nl.eu.net. (134.222.228.121): 170ms 160ms 191ms 9 amsterdam3.nl.eu.net. (134.222.186.3 ): 197ms 170ms 165ms 10 sofia.bg.eu.net. (134.222.7.2 ): 783ms 575ms 1030ms 11FFFF,0000,0000 * 11 plovdiv.bg.eu.net. (193.68.0.249 ): 840ms FFFF,0000,0000 * 12 plovdiv.eunet.bg. (193.68.2.1 ): 934ms FFFF,0000,0000 * 1440ms 0000,0000,FFFF* Trace completed 7/23/97 7:45:11 AM * From fuchs@ebo.dec.com Wed Jul 23 15:55:12 1997 From: fuchs@ebo.dec.com (Fred Fuchs) Date: Wed, 23 Jul 1997 16:55:12 +0200 Subject: SWISS Telecom joins the 6Bone Message-ID: <33D61B50.F81@ebo.dec.com> Hi The Swiss Telecom is now connected to the 6BONE. The IPv4 Tunnel is connected to DIGITAL-ETC (Digital in Sophia). Until now we have three Nodes running with IPv6. 1:) Digital Routabout Access (RIPng) 5F02:2F00:C3B0:D700:B0D7:0800:2BB2:1D0F 2.) DIGITAL UNIX DECstation 3000-600 5f02:2f00:c3b0:d700:b0d7::f851:9547 3.) DIGITAL UNIX Alphastation 2000 5f02:2f00:c3b0:d700:b0d7:800:2b38:63c4 Those Systems should be up all the time. I hope everything is correct, if not please let me know. Regards Fred Fuchs PS: This mail was send on behalf of Andre Prim of the Swiss Telecom R&D The following information was entered on the FTP site. ipv6-site: SWISS-TELECOM origin: AS559 descr: Swiss Telecom Research & Development descr: Ostermundigenstr. 93 descr: 3000 Bern 29 descr: Switzerland country: CH prefix: 5F02:2F00:C3B0:D700::/64 application: ping gdvipv6.ctv6.vptt.ch application: ping aldebaran6.ctv6.vptt.ch application: ping deneb6.vptt.ch tunnel: IPv6 in IPv4 gdvipv6.ctv6.vptt.ch -> vboipv6rtr.europe.digital.com DIGITAL-ETC RIPv6 contact: HP1-6BONE contact: AF1-6BONE contact: AP148-RIPE remarks: ipv6-site is operational since 09-Jul-1997 remarks: remarks: DIGITAL RouteAbout Access /IPv6 (5F02:2F00:C3B0:D700:B0D7:0800:2BB2:1D0F) remarks: running RtAbt Acces EW/IP IPv6 #159,SW=T2.0-5 remarks: DIGITAL UNIX DECstation 3000-600 remarks: Name is aldebaran6 remarks: IPv6 address is 5f02:2f00:c3b0:d700:b0d7::f851:9547 remarks: running Digital Unix V4.0B, IPv6 X6.0A remarks: DIGITAL UNIX Alphastation 2000 remarks: Name is deneb6 remarks: IPv6 address is 5f02:2f00:c3b0:d700:b0d7:800:2b38:63c4 remarks: running Digital Unix V4.0B, IPv6 X6.0A remarks: notify: prim_a@vptt.ch notify: gisiger@vptt.ch notify: durand@ebo.dec.com notify: fuchs@ebo.dec.com changed: fuchs@ebo.dec.com 970709 source: 6BONE From RLFink@lbl.gov Wed Jul 23 16:35:03 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 23 Jul 1997 08:35:03 -0700 Subject: Out with the old, In with the new !! (registries that is) In-Reply-To: <199707231229.IAA19582@snad.ncsl.nist.gov> Message-ID: Rob Glenn makes a good point. All 6bone sites need to look at and clean up their automatically converted 6bone registry records. Also, all automatic process owners need to switch to the new registry as the old one will go away soon (I hope...read on). In fact, I propose that David Kessens arrange with RIPE-NCC staff to turn off the old ftp-style registry one month from today, 24 August. Does anyone see any problems doing that? Thanks, Bob ============================================= At 5:29 AM -0700 7/23/97, Robert Glenn wrote: >The stats page here at NIST is now using the new registry to gather >its data. I have noticed (as others will if they take a look >at the page) that the "ping: ....." lines didn't carry to the >new registry with the switch over. As a result, there are a large >percentage of sites in the registry with "No Pingable Addresses" >and will show up as such on the stats page until an "application: >ping ...." entry is added to those particular entries. > >(I apologize if you have already seen this message). > >Rob G. >rob.glenn@nist.gov > >6bone Reachability Status From NIST URL: >http://www.antd.nist.gov/~ipng/NIST-6bone-status.html From RLFink@lbl.gov Wed Jul 23 16:40:01 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 23 Jul 1997 08:40:01 -0700 Subject: connection to 6bone In-Reply-To: <199707221538.KAA12061@bandicoot.ssctr.bcm.tmc.edu> Message-ID: Scott, At 8:38 AM -0700 7/22/97, Scott Mace wrote: >I am an engineer at Baylor College of Medicine. We are interested >in connecting to the 6bone. We have a handful of sparcstations here >running the Solaris ipv6 code. Given Baylor's sesquinet connections I would suggest using CICNET for your 6bone tunnel endpoint. You can talk to Dorian Kim at: dorian@cic.net Thanks, Bob From Ivano.Guardini@CSELT.IT Wed Jul 23 17:27:43 1997 From: Ivano.Guardini@CSELT.IT (Guardini Ivano) Date: Wed, 23 Jul 1997 18:27:43 +0200 Subject: New 6Bone stats from CSELT Message-ID: Hi all, In the previous e-mail I gave a wrong URL. The right one is: http://carmen.cselt.it/ipv6/stats/stats.html I'm sorry for the mistake. 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 tomw@netrex.com Wed Jul 23 22:01:04 1997 From: tomw@netrex.com (Tom Wallace) Date: Wed, 23 Jul 1997 17:01:04 -0400 (EDT) Subject: Hello Message-ID: <199707232101.RAA11802@xerxes.netrex.com> Hi, I'm relatively new to the list and was wondering if there was a FAQ available describing software, connection points, advantages of IPv6... Thanks, Tom Wallace tomw@netrex.com From hinden@Ipsilon.COM Thu Jul 24 00:21:55 1997 From: hinden@Ipsilon.COM (Bob Hinden) Date: Wed, 23 Jul 1997 16:21:55 -0700 Subject: Hello In-Reply-To: <199707232101.RAA11802@xerxes.netrex.com> Message-ID: <3.0.3.32.19970723162155.0073332c@mailhost.ipsilon.com> Tom, > Hi, I'm relatively new to the list and was wondering if there was >a FAQ available describing software, connection points, advantages >of IPv6... Please see: http://playground.sun.com/ipng http://www.6bone.net/ Bob From zvezdi@plovdiv.uspc.bg Thu Jul 24 07:48:22 1997 From: zvezdi@plovdiv.uspc.bg (Zvezdelin Vladov) Date: Thu, 24 Jul 97 09:48:22 +0300 Subject: PLEASE, TAKE THIS INTO COUNT! TOO! Message-ID: Hey, guys, thank you for all the e-mails, but please notice the following: 1. The Spectrum PCT is connected to the Internet via Satallite Dish, directly to Digex.Net in US, so its addresses are part of the US net. One of the resellers of Spectrum is Techno-Link -- check this out www.techno-link.com -- it is in the top US domain. I know them well (Spectrum) and I could talk with them. 2. BUT, STILL the official Bulgarian Domain is '.bg' which is mainly maintained by Digital Systems -- www.digsys.bg, ns.digsys.bg, ns.eunet.bg; Until recently, all of the records in its Name Server, were available for listing, so I have all of their domain listed -- if someone is intrested, call. But the with them, is that United States Peace Corps have account there, and this is actually, the place I am at, right now, and I am using an old UUPC client, and it is at some point terible. There Technical Chief is someone you JUST can't find by phone. I'll do my Best to contact him, and make him think on switching into 6bone, but still, it is difficult. Remember, that the speed thru this provider (digsys-Digital System) is sometimes 20, 30, max 100 bytes per second. Very rarely is about 1000 bytes, and the last is estimated on 28.8 Kb/s line to them, when nobody is using it. Which means, the have overselled their structure, too much. 3. The speed, with Spectrum PCT, is almost always more than 1.5 KBYTES per second for 14.4 Kb/s line. Regards to all of you, and have a nice time, outthere. Zvezdelin Vladov --- /**************************************************************************** * Zvezdelin Vladov, Assistant, United States Peace Corps - Bulgaria * * "Internet Show" - Host & Author, Sunday 9am-10am, Radio Plovdiv, FM 103.1* ****************************************************************************/ From RLFink@lbl.gov Thu Jul 24 15:02:16 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 24 Jul 1997 07:02:16 -0700 Subject: THANKS FOR THE REPLY!!!! CHECK THIS OUT! In-Reply-To: References: Message-ID: Zvezdelin, If you are thinking that participating in the 6bone will somehow solve your Internet connectivity problems, it can't. As you are building a tunnel between IPv4 end points, you are going to have to use a path normally available to you by your available IPv4 connectivity in Bulgaria. You can best perform this search for a good 6bone connection point by doing it yourself, as you can run traceroute from your own system. Just try traceroutes to various 6bone backbone sites and look at the route and delays you get...then choose the one that looks best. Bob At 4:38 AM -0700 7/24/97, Zvezdelin Vladov wrote: >And what is your opinion on DigEx.Net -- >Digital Express Net --- www.digex.net ? > >See, we have at least three major connecting sites > >with U.S.: >1. Global One (204..... something ) net -- do ping www.bis.bg >and look for word 'gocis'=Global One Computer Information Service or something >like this. ( This is thru Sprint.si.net ) > >2. Spectrum PCT net -- www.spct.net -- thru digex.net ( digital express net ) > >with EUnet Amsterdam: >1. Academical Connectivity -- www.amigo.bg, www.unicom.bg, www.bgcict.bg >with the name server ns.acad.bg; It permits record list, so you can see >the whole area; www.aubg.bg, www.aubg.edu -- American University in Bulgaria > >2. Bussiness Conectivity -- www.naturella.com -- to EUnet London, you may >say that their speed is close to good. > >3. DigSys -- the diggers will almost dig you into the Earth, if you rely on >them -- check this out - in 00:00 o'clock in the night, I am the only >one and I am using a 28.8 Kb/s link to them, and with ftp, I can't get much >than 1000-1200 bytes per second. And this is the best possible. >They are official distributors of EUnet, and the pricing 3-4 times more >compared >the other ISP, connected to the same Area. www.digsys.bg > >These are everybody, I think, that operate in the area. Every other name of >ISP, are probablly ISPs connected to these root ISPs. > > > >Don't you think, that there should be a way, thru Digex.Net, I mean thru >this route, to connect to 6bone. Because it is much, much, much better. >Thank you. > >Have a nice time. >Zvezdelin Vladov >--- >/**************************************************************************** > * Zvezdelin Vladov, Assistant, United States Peace Corps - Bulgaria * > * "Internet Show" - Host & Author, Sunday 9am-10am, Radio Plovdiv, FM 103.1* > ****************************************************************************/ From roque@cisco.com Fri Jul 25 19:17:48 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 25 Jul 1997 11:17:48 -0700 (PDT) Subject: BGP MP_NLRI format update Message-ID: <199707251817.LAA24550@pedrom-ultra.cisco.com> Most sites will be upgrading it's routers Monday to a new BGP 4+ MP_NLRI attribute format (the one defined in the latest draft rev - 03). Cisco will upgrade it's router at aprox. 10 am PST (17h00 GMT). Pedro. From =?iso-8859-1?Q?=BF=F8?= Sat Jul 26 14:02:35 1997 From: =?iso-8859-1?Q?=BF=F8?= (=?iso-8859-1?Q?=BF=F8?=) Date: Sat, 26 Jul 1997 22:02:35 +0900 Subject: 6bone attachment Message-ID: <3.0.1.32.19970726220235.007a9270@pine.kangwon.ac.kr> Hi, I am looking for an entry point to the 6bone and would be very grateful for any advice you could give me on who I might approach. I am situated at kangwon uni. kangwondo, the Republic of Korea. Many thanks From stuart@pa.dec.com Tue Jul 29 18:30:32 1997 From: stuart@pa.dec.com (Stephen Stuart) Date: Tue, 29 Jul 97 10:30:32 -0700 Subject: DIGITAL-CA hosts might be unreachable for a short time Message-ID: <9707291730.AA31151@nsl-too.pa.dec.com> We're turning up some BGP4+ routing sessions, and some software upgrades are in the works. We should have everything back on-line by midnight PDT. Thanks, Stephen From davidk@ISI.EDU Tue Jul 29 19:43:09 1997 From: davidk@ISI.EDU (davidk@ISI.EDU) Date: Tue, 29 Jul 1997 11:43:09 -0700 (PDT) Subject: some 6bone registry questions for the list In-Reply-To: from "Guy Davies" at Jul 29, 97 04:23:31 pm Message-ID: <9707291843.AA18521@brind.isi.edu> Hi, I recently got a few remarks and wanted to know your opinion. The current draft for the registry describes that domain names should be used in the tunnel specification of the 'ipv6-site' objects. This has the advantage that it is very easy to derive the IPv4 *and* IPv6 address through DNS. I have changed the syntax checking recently in such way that it doesn't accept IPv4 numbers anymore but that it will help a bit by doing a reverse lookup. However, if nothing is found, a error is generated. Guy Davies told me that this might have gone a bit too far. Do you agree? Should I change it to a warning only or leave it as is with the strong syntax checking? In another question, it was pointed out to me that RIPng was the better protocol name instead of RIPv6. I plan to switch and convert to RIPng if nobody objects. It will hardly have any consequences for most people since I will alias RIPv6 to RIPng. David K. --- From davidk@ISI.EDU Tue Jul 29 21:16:33 1997 From: davidk@ISI.EDU (davidk@ISI.EDU) Date: Tue, 29 Jul 1997 13:16:33 -0700 (PDT) Subject: some 6bone registry questions for the list In-Reply-To: from "Guy Davies" at Jul 29, 97 09:10:22 pm Message-ID: <9707292016.AA20327@brind.isi.edu> Guy, Guy Davies writes: > > Maybe, David, you could reject entries with the IP address on the left > hand side of the -> but warn for entries with the IP address on the right > since the left hand side is the local side and totally under the control > of the organisation submitting the object? Perhaps that is just adding > more complexity than is really necessary. This sounds like a very reasonable solution to me. ir doesn't add much more complexity. I will fix it this way except if there are any objections by others, David K. --- From roque@cisco.com Wed Jul 30 04:27:33 1997 From: roque@cisco.com (Pedro Marques) Date: Tue, 29 Jul 1997 20:27:33 -0700 (PDT) Subject: some 6bone registry questions for the list In-Reply-To: <9707291843.AA18521@brind.isi.edu> References: <9707291843.AA18521@brind.isi.edu> Message-ID: <199707300327.UAA26052@pedrom-ultra.cisco.com> >>>>> "davidk" == davidk writes: davidk> Hi, davidk> I recently got a few remarks and wanted to know your davidk> opinion. davidk> The current draft for the registry describes that domain davidk> names should be used in the tunnel specification of the davidk> 'ipv6-site' objects. This has the advantage that it is davidk> very easy to derive the IPv4 *and* IPv6 address through davidk> DNS. davidk> I have changed the syntax checking recently in such way davidk> that it doesn't accept IPv4 numbers anymore but that it davidk> will help a bit by doing a reverse lookup. However, if davidk> nothing is found, a error is generated. Please don't do that. I don't think there is any reason why you should require tunnel end-points to have a DNS address. Remember tunnel end-points are supposed to be routers... routers don't always DNS records for all of it's addresses and even if they do, most of the times the IP address is much more significant as it is unique while the name may point at several addresses. davidk> Guy Davies told me that this might have gone a bit too davidk> far. Do you agree? Should I change it to a warning only davidk> or leave it as is with the strong syntax checking? I personally think you should just accept IP addresses... they are just much more reliable and meaningful to debug network problems. davidk> In another question, it was pointed out to me that RIPng davidk> was the better protocol name instead of RIPv6. Yap... RIPng is RIPv2 with support for IPv6 addresses if i'm not mistaken. So the name RIPv6 is, IMHO, misleading. Pedro. From RLFink@lbl.gov Wed Jul 30 19:47:03 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 30 Jul 1997 11:47:03 -0700 Subject: new 6bone backbone links diagram - version 24 Message-ID: new 6bone backbone links diagram - version 24 http://www.6bone.net/6bone-bblinks.html Change RIPng links to BGP4+ from DIGITAL-CA/US to CISCO/US and UUNET/UK This is great. BGP4+ interoperability between CISCO and DIGITAL! Bob PS: Minor 6bone diagram edits (version 80) From RLFink@lbl.gov Wed Jul 30 22:02:24 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 30 Jul 1997 14:02:24 -0700 Subject: corrections for a 6bone host/router implementations list Message-ID: 6bone folk, I'm trying to make a list of host and router implementations in use on the 6bone. The IETF IPng (Sun) web site lists 22 host and 9 client implementations as under development or complete. http://playground.sun.com/pub/ipng/html/ipng-implementations.2.html Looking at the above list, I'm guessing the following implemenations in use. Please forgive the use of a plain "BSD" as a generalization, or correct it as you will. Anyway, anyone able to correct this list for me? Thanks, Bob ============================================= host implementations in use on the 6bone are: Digital Unix FTP Software Windows95 IBM AIX Inria BSD Linux SICS HP-UX Sun Solaris UNH BSD NRL BSD WIDE BSD ============================================= router implementations in use on the 6bone are: Bay Cisco Digital Merit MRT Telebit ============================================= From RLFink@lbl.gov Thu Jul 31 03:40:35 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 30 Jul 1997 19:40:35 -0700 Subject: new 6bone backbone links diagram - version 25 Message-ID: new 6bone backbone links diagram - version 25 http://www.6bone.net/6bone-bblinks.html change RIPng link to BGP4+ from NWNET/US to ESNET/US add BGP4+ link from DIGITAL-CA/US to ESNET/US Thanks, Bob From RLFink@lbl.gov Thu Jul 31 03:38:44 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 30 Jul 1997 19:38:44 -0700 Subject: new 6bone diagram - version 81 Message-ID: new 6bone diagram - version 81 http://www.6bone.net/6bone-drawing.html add ANL/US, BNL/US and AMESLAB/US to ESNET/US Welcome to: Argonne National Laboratory, Chicago, IL Brookhaven National Laboratory, Long Island, NY Ames Laboratory, Iowa State Univ., Ames, Iowa Thanks, Bob PS: AMESLAB seems to need a 6bone Registry entry