From RLFink@lbl.gov Fri Aug 1 02:46:50 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 31 Jul 1997 18:46:50 -0700 Subject: new 6bone backbone links diagram - version 26 Message-ID: new 6bone backbone links diagram - version 26 http://www.6bone.net/6bone-bblinks.html chg RIPng link to BGP4+ from CICNET/US to NWNET/US chg RIPng link to BGP4+ from DIGITAL-CA/US to NWNET/US Good pace converting from RIPng to BGP4+ these days! Thanks, Bob From RLFink@lbl.gov Fri Aug 1 02:44:07 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 31 Jul 1997 18:44:07 -0700 Subject: new 6bone diagram - version 82 Message-ID: new 6bone diagram - version 82 http://www.6bone.net/6bone-drawing.html add SWISS-TELECOM/CH to DIITAL-ETC/FR add FOGHEAD/US to NWNET/US add UW-CSE/US to NWNET/US Welcome to: Swiss Telecom Research & Development Bern Switzerland Foghead Consulting Seattle, Washington US Dept. of CSE, University of Washington Seattle, Washington US Thanks, Bob From bmanning@ISI.EDU Mon Aug 4 23:41:32 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Mon, 4 Aug 1997 15:41:32 -0700 (PDT) Subject: 6bone attachment In-Reply-To: <3.0.1.32.19970726220235.007a9270@pine.kangwon.ac.kr> from "=?iso-8859-1?Q?=BF=F8?= =?iso-8859-1?Q?_=B1=A4?=" at Jul 26, 97 10:02:35 pm Message-ID: <199708042241.AA17841@zed.isi.edu> > > 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 > Try, whchoi@cosmos.kaist.ac.kr or ipv6-ops@cosmos.kaist.ac.kr -- --bill From RLFink@lbl.gov Tue Aug 5 02:43:43 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 4 Aug 1997 18:43:43 -0700 Subject: 6bone Agenda for Munich - draft version of 4Aug97 Message-ID: Gentle 6bone folk, The current draft agenda for the 6bone session is shown below. Please send comments/add/changes/deletions to the mailer. As I still have little input from anyone on the agenda, thus I am choosing to eliminate some things and regroup others. Where no name is present I am still hoping to receive volunteers on that subject. If I receive none, the item will either be deleted or I will attempt to elicit input at the meeting, ad hoc. So...I need to hear from you! Remember that the 6bone activity is now part of ngtrans (along with "tools"). The ngtrans meetings are scheduled as shown below. Note that the 6bone portion of the meeting will be in two pieces. If we don't have sufficient content for the second hour we will adjourn. Thanks, Bob ============================================================================= TUESDAY, August 12, 1997 1415-1515 Afternoon Sessions II Lindau OPS ngtrans Next Generation Transition (Tools) WG 1515-1545 Break (Refreshments provided) - Congress Foyer 1545-1645 Afternoon Sessions III Lindau OPS ngtrans Next Generation Transition (6bone) WG <<<<<<<<<<<<< 1700-1800 Afternoon Sessions IV Lindau OPS ngtrans Next Generation Transition (6bone) WG <<<<<<<<<<<<< ================================================================================ ================================================================================ NGTRANS-6BONE Agenda - Munich IETF Tuesday, August 12, 1545-1800 1. Introduction & agenda - Bob Fink (10 mins) 2. Status of Action Items from Memphis - (20 mins) 2.1 CAIRN Backbone Proposal - Allison Mankin (update from Allison 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 (agenda item below) 2.4 I-D "Representing IPv6 Tunnels in RPSL" - David Meyer (maybe this is closed - Dave?) 2.5 New 6BONE registry - David Kessens (agenda item below) 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 (agenda item below) 3. New 6bone Registry, Overview and Issues - David Kessens (10 mins) 4. Backbone/Transit Planning - (20 minutes) 4.1 Just how much peering among backbone sites - 4.2 What makes a backbone site - 4.3 UK 6bone connectivity among the ISPs - Guy Davies 5. Test Plan for Aggregation-Based Addressing - (30 minutes) 5.1 The current plan - Bob Fink 5.2 G6 addressing plans - Alain Durand 5.3 Open issues for new addressing on the 6bone - 6. Operational issues on the 6bone - (20 minutes) 6.1 ip6.int versus icmp-based address lookup - 6.2 Any good new tool suggestions? - 6.3 When do we start testing scurity? - 7. Implementations in use on the 6bone - Bob Fink (10 mins) 8. Site (router) renumbering on the 6bone - (10 mins) -end From defaultuser@domain.com Tue Aug 5 09:04:43 1997 From: defaultuser@domain.com (Yann-Ju Chu) Date: Tue, 05 Aug 1997 16:04:43 +0800 Subject: How to get my ASN Message-ID: <33E6DE99.53017FD5@domain.com> I wish to join the 6Bone but I do not know how to get my ASN. Can you give me a suggestion? Thanks Chu From smurf@noris.de Tue Aug 5 11:38:36 1997 From: smurf@noris.de (Matthias Urlichs) Date: Tue, 5 Aug 1997 12:38:36 +0200 (Funky) Subject: How to get my ASN In-Reply-To: <33E6DE99.53017FD5@domain.com> from "Yann-Ju Chu" at Aug 5, 97 04:04:43 pm Message-ID: <19970805103837.3651.qmail@nova.noris.de> If you don't have your own ASN already, ask your provider. Yann-Ju Chu wrote: > > I wish to join the 6Bone but I do not know how to get my ASN. Can >you give me a >suggestion? > -- Matthias Urlichs noris network GmbH From qkim@pec.etri.re.kr Tue Aug 5 12:37:11 1997 From: qkim@pec.etri.re.kr (Yong-Woon Kim) Date: Tue, 05 Aug 1997 20:37:11 +0900 Subject: How to get my ASN In-Reply-To: <33E6DE99.53017FD5@domain.com> Message-ID: <3.0.3.32.19970805203711.007143c0@pec.etri.re.kr> $)C At 04:04 ?@HD 97-08-05 +0800, Yann-Ju Chu wrote: > I wish to join the 6Bone but I do not know how to get my ASN. Can >you give me a >suggestion? > >Thanks I'm very happy to give an answer in this mailing list. :) $ whois -h radb.ra.net YOUR-IP-address Good Luck. From jypark@comsun.chungnam.ac.kr Tue Aug 5 14:34:30 1997 From: jypark@comsun.chungnam.ac.kr (Juyoung Park) Date: Tue, 05 Aug 1997 22:34:30 +0900 Subject: How to get my ASN Message-ID: <3.0.32.19970805223429.007f43b0@comsun.chungnam.ac.kr> Dear Yann-Ju Refer to ftp://rs.internic.net/netinfo/asn.txt , and you can get your ASN.. of course you should know which IS you connected.. Hope this might be helpful .. $)C At 04:04 ?@HD 97-08-05 +0800, Yann-Ju Chu wrote: > I wish to join the 6Bone but I do not know how to get my ASN. Can >you give me a >suggestion? > >Thanks > >Chu > > > Ju Young Park --------------------------------- computer communications lab, Chungnam Nat. Univ. South KOREA +82-42-822-2577 ------------------------------------------------ From RLFink@lbl.gov Tue Aug 5 17:53:16 1997 From: RLFink@lbl.gov (Bob Fink) Date: Tue, 5 Aug 1997 09:53:16 -0700 Subject: IPv6 white paper In-Reply-To: <3.0.32.19970805121722.00695140@pobox> Message-ID: Dimitry, At 9:17 AM -0700 8/5/97, Dimitry Haskin wrote: ... >Please add the following link to 6bone home page. >This is a white paper on IPv6. > >http://www.baynetworks.com/Products/Routers/Protocols/2789.html Thanks for the pointer to this very nice white paper on the business case for IPv6. I have added a pointer to it near the top of the 6bone home page so others can come across it more easily. Thanks for submitting it. Bob From Alain.Durand@imag.fr Wed Aug 6 19:00:53 1997 From: Alain.Durand@imag.fr (Alain Durand) Date: Wed, 6 Aug 1997 20:00:53 +0200 Subject: G6 reachability Message-ID: <970806200053.ZM21847@rama.imag.fr> Due to a severe problem on a router, all RIPng routes to G6 are dead. We are still connected to the 6bone via 2 BGP4+ tunnels. I hope to recover soon.... Sorry for that, - Alain. From bmanning@ISI.EDU Wed Aug 6 22:37:54 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Wed, 6 Aug 1997 14:37:54 -0700 (PDT) Subject: New 6 bone site In-Reply-To: <199708061127.NAA00516@skil24.ce.chalmers.se> from "Florian-Daniel Otel via ST end dec97" at Aug 6, 97 01:27:07 pm Message-ID: <199708062137.AA25687@zed.isi.edu> Another site... ;; QUESTIONS: ;; 0.0.9.1.b.0.f.5.ip6.int, type = NS, class = IN ;; ANSWERS: 0.0.9.1.b.0.f.5.ip6.int. 129600 NS ns.ipv6.ce.chalmers.se. 0.0.9.1.b.0.f.5.ip6.int. 129600 NS skil26.ce.chalmers.se. 0.0.9.1.b.0.f.5.ip6.int. 129600 NS skil26-6bone.ipv6.ce.chalmers.se. 0.0.9.1.b.0.f.5.ip6.int. 129600 NS skil24.ce.chalmers.se. -- --bill From Alain.Durand@imag.fr Thu Aug 7 17:40:36 1997 From: Alain.Durand@imag.fr (Alain Durand) Date: Thu, 7 Aug 1997 18:40:36 +0200 Subject: G6 up again Message-ID: <970807184036.ZM2458@rama.imag.fr> Hi all G6 RIPng tunnels are now up & running. Many thanks to Robert Watson from digital. - Alain. From RLFink@lbl.gov Thu Aug 7 17:39:22 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 7 Aug 1997 09:39:22 -0700 Subject: 6bone operational luncheon Message-ID: 6bone folk, In Memphis we had a successful 6bone operational issues meeting over lunch so we didn't have to have unstructured converstion during the working group meeting. I would like to do this again, next Tuesday (August 12) at 11:15 AM, just after the last morning session (which I believe includes IDR). So...all those interested, please show up around the IETF reg desk and we can choose a place based on our size. Please send me some email that you intend to attend if you can. Thanks, Bob From JOIN Project Team Fri Aug 8 12:59:21 1997 From: JOIN Project Team (JOIN Project Team) Date: Fri, 8 Aug 1997 13:59:21 +0200 (MEZ) Subject: new JOIN ping statistic Message-ID: Hi, we have changed our 6bone ping statistic to fit the new RIPE style 6bone registry: Hourly the ping information for the 6bone backbone sites is received by whois queries to the ISI database and then a sequence of five pings is executed to these sites. Additionally DNS and reverse DNS is checked. You can click on the entries in the table to perform an additional ping or nslookup immediately (as soon as traceroute is available for the Solaris implementation we will use it instead of ping). If you like to be pinged hourly from our JOIN site please mail us. Then we add a further ping table for non-backbone sites. Hope this page is useful for you, all the best - Guido ------------------------------------------------------------------------------ JOIN -- IP Version 6 in the WiN Guido Wessendorf A project of DFN Westfaelische Wilhelms-Universitaet Muenster Project Team email: Universitaetsrechenzentrum join@uni-muenster.de Einsteinstrasse 60 http://www.join.uni-muenster.de D-48149 Muenster / Germany phone: +49 251 83 31639, fax: +49 251 83 31653, email: wessend@uni-muenster.de ------------------------------------------------------------------------------ From RLFink@lbl.gov Fri Aug 8 17:22:08 1997 From: RLFink@lbl.gov (Bob Fink) Date: Fri, 8 Aug 1997 09:22:08 -0700 Subject: new 6bone diagram - version 83 Message-ID: new 6bone diagram - version 83 http://www.6bone.net/6bone-drawing.html add new site NATA-BG/UK to UUNET/UK add new site NRS/UK to UUNET/UK Welcome to NRS of Hertford, UK NATA-BG/UK needs a registry entry. Thanks, Bob From bc@ecs.soton.ac.uk Fri Aug 8 21:56:26 1997 From: bc@ecs.soton.ac.uk (Ben Crosby) Date: Fri, 08 Aug 1997 21:56:26 +0100 Subject: New Vendor to Vendor BGP 4+ Peering ! Message-ID: <3.0.3.32.19970808215626.006ef414@diana.ecs.soton.ac.uk> Hi all, Just a quick note to say that USOT-ECS now has a BGP 4+ peering with TELEBIT/DK, running between a DECswitch 900EF router and a Telebit TBC2000. This joins our DEC <-> CISCO peering which was also recently established. My thanks to Herluf Hansen (TELEBIT) and Jitu Patel (DIGITAL) for their assistance. Ben. From RLFink@lbl.gov Sat Aug 9 00:37:11 1997 From: RLFink@lbl.gov (Bob Fink) Date: Fri, 8 Aug 1997 16:37:11 -0700 Subject: New Vendor to Vendor BGP 4+ Peering ! In-Reply-To: <3.0.3.32.19970808215626.006ef414@diana.ecs.soton.ac.uk> Message-ID: At 1:56 PM -0700 8/8/97, Ben Crosby wrote: >Hi all, > > Just a quick note to say that USOT-ECS now has a BGP 4+ peering with >TELEBIT/DK, running between a DECswitch 900EF router and a Telebit TBC2000. >This joins our DEC <-> CISCO peering which was also recently established. > > My thanks to Herluf Hansen (TELEBIT) and Jitu Patel (DIGITAL) for their >assistance. This is great...means we have at least three way inter-vendor bgp4+ working. Thanks, Bob From JOIN Project Team Mon Aug 11 10:59:16 1997 From: JOIN Project Team (JOIN Project Team) Date: Mon, 11 Aug 1997 11:59:16 +0200 (MEZ) Subject: added sites to 6bone stat Message-ID: Hi, we added some other 6bone sites to our ping statistic. Again: if you like to be included, please mail us. After IETF we also switch to BGP4+ - so hopefully our connectivity is better then ;-) - Guido From rlfink@lbl.gov Thu Aug 14 21:31:52 1997 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 14 Aug 1997 22:31:52 +0200 Subject: 6bone backbone planning & move to testing aggregation address format Message-ID: 6bone backbone planning meeting - 14 August 1997, Munich, DE. Alain Durand held a BOF for those interested in 6bone backbone planning under the new test aggregation address format. There were 27 people in attendance. Alain Durand (G6, FR) spoke on the need to minimize backone tunnels to clean up routing. There were comments for this, explaing the reasons why it is needed at this time, and comments as to why we shouldn't worry about this. Stephen Stuart (Digital-ca, US) spoke on reasons to cleanup peering, and to have multiple interconnect points for ISP TLA's. Matt Crawford showed various multi-prefix scenarios. There was a general consensus that there was a need to simplify the 6bone bacbone topology. Bob Fink (ESnet/LBNL, US) then led a discussion to generate a plan for readdressing and backbone restructuring. This discussion led to the following general agreements: 1. that we assign Testing pTLAs (i.e., pseudo TLAs assigned from the NLA1 field of the 6bone Test address allocation) from the Test Aggregation addressing I-D as follows: TELEBIT/DK 3FFE:0100::/24 SICS/SE 3FFE:0200::/24 G6/FR 3FFE:0300::/24 JOIN/DE 3FFE:0400::/24 WIDE/JP 3FFE:0500::/24 SURFNET/NL 3FFE:0600::/24 ESNET/US 3FFE:0700::/24 CICNET/US 3FFE:0800::/24 ISI-LAP/US 3FFE:0800::/24 NWNET/US 3FFE:0A00::/24 VIAGENIE/CA 3FFE:0B00::/24 CISCO/US 3FFE:0C00::/24 ANS/US 3FFE:0D00::/24 IFB/UK 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT/IT 3FFE:1000::/24 UUNET/UK 3FFE:1100::/24 DIGITAL-CA/US 3FFE:1200::/24 BAY/US 3FFE:1300::/24 UNI-C/DK 3FFE:1400::/24 Note: we started at 1 because Bob is nervous about using 0 :-) 2. that we establish October 1 as the start date for renumbering the backbone to testing aggregation addresses, with the goal of November 1 for coming online. 3. that all backbone sites will peer with BGP4+, and only BGP4+. 4. that the old testing addresses (RFC 1897) be discontinued on the backbone as early as October 1 (by sites already renumbered) and not later than November 1 when the newly addressed backbone is scheduled to be fully online. 5. that a call for new pTLA candidates be issued immediately, for inclusion in the October 1 renumbering/restructuring, where the criteria to be applied for inclusion is willingness and ability to actively participate in this timeframe, and demonstrated experience with IPv6 and the 6bone. 6. that a call for existing backbone sites (given a pTLA above) be made to decide themselves if they are able to participate in this renumbering/ resructuring effort, and be encouraged to give back their pTLA assignment for now if they aren't able to participate. (Note: any site doing this can easily reapply at a later time.) -end From rlfink@lbl.gov Thu Aug 14 21:32:23 1997 From: rlfink@lbl.gov (Bob Fink) Date: Thu, 14 Aug 1997 22:32:23 +0200 Subject: call for 6bone TLA participants for Oct. 1 renumbering of backbone Message-ID: Per the 6bone backbone ad hoc meeting in Munich, I am calling for those interested in being an early 6bone test pTLA (i.e., pseudo TLAs assigned from the NLA1 field of the 6bone Test address allocation) when the renumbering to the new Aggregation-based unicast address format is started on 1 October. Requirements are willingness and ability to actively participate in this timeframe, and demonstrated experience with IPv6 and the 6bone. Please send your requests to become a 6bone pTLA to the 6bone mail list with text sufficient to describe your interest and qualifications. I will assign test pTLAs to all reasonable request at this time. Thanks, Bob From crawdad@fnal.gov Fri Aug 15 08:10:09 1997 From: crawdad@fnal.gov (Matt Crawford) Date: Fri, 15 Aug 1997 02:10:09 -0500 Subject: call for 6bone TLA participants for Oct. 1 renumbering of backbone In-Reply-To: Your message of Thu, 14 Aug 1997 22:32:23 +0200. Message-ID: <199708150710.CAA23674@gungnir.fnal.gov> > Please send your requests to become a 6bone pTLA to the 6bone mail list I direct the chair's attention to my message of June 2. Please let me know if more supporting material is needed. From mwa@broadcom.ie Fri Aug 15 22:19:37 1997 From: mwa@broadcom.ie (mark waters) Date: Fri, 15 Aug 1997 14:19:37 -0700 Subject: Yet another IPv6 statistics page Message-ID: <33F4C7E9.E954E71F@broadcom.ie> This is a multi-part message in MIME format. --------------116B71C357F3080DF1D97F3D Content-Type: text/plain; charset=us-ascii Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Any suggestions or comments would be gratefully accepted... regards, Mk. Mark Waters Broadcom Eireann Reseach Dublin Ireland http://www-usru.broadcom.ie/ipv6/ --------------116B71C357F3080DF1D97F3D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Base: "http://www-usru.broadcom.ie/ipv6/" Broadcom's IPv6 related pages

Information that is currently available from this site include:

This page was last updated on 08/15/97 and is maintained by Broadcom's User Services Research Unit.

--------------116B71C357F3080DF1D97F3D-- From qv@3com.com Sat Aug 16 02:42:57 1997 From: qv@3com.com (Quaizar Vohra) Date: Fri, 15 Aug 1997 18:42:57 -0700 (PDT) Subject: call for 6bone TLA participants for Oct. 1 renumbering of backbone In-Reply-To: References: Message-ID: <199708160142.SAA02086@lookout.nsd.3com.com> Hi Bob, I would like to request a test pTLA on behalf of 3com. We have just finished development of IPv6 on a 3com router and have tested its interoperability at UNH. My qualifications include development of IPv6 on NetBSD as well as on 3com routers. I had initiated the UNH 6bone site and had maintained it for a while. We at UNH had successfully provided 6bone connectivity to other sites. Enough of bragging :-). My main interest would be to test the interoperability of 3com router (being a backbone router would stress it to). Hopefully this will send a positive message that there are enough router and host vendors interoperating well on the 6bone to start native deployment. I will try my best to provide 6bone connectivity to any other sites. Please feel free to send me questions, comments. Thanks Quaizar > Per the 6bone backbone ad hoc meeting in Munich, I am calling for those > interested in being an early 6bone test pTLA (i.e., pseudo TLAs assigned > from the NLA1 field of the 6bone Test address allocation) when the > renumbering to the new Aggregation-based unicast address format is started > on 1 October. > > Requirements are willingness and ability to actively participate in this > timeframe, and demonstrated experience with IPv6 and the 6bone. > > Please send your requests to become a 6bone pTLA to the 6bone mail list > with text sufficient to describe your interest and qualifications. > > I will assign test pTLAs to all reasonable request at this time. > > Thanks, > > Bob > From leewb@dcn.soongsil.ac.kr Mon Aug 18 02:53:30 1997 From: leewb@dcn.soongsil.ac.kr (Lee Wangbong) Date: Mon, 18 Aug 1997 10:53:30 +0900 Subject: about link local address Message-ID: <3.0.1.32.19970818105330.006a446c@dcn.soongsil.ac.kr> Hi! I have one question about link local address. That is, I wonder about whether IPv6 hosts can communicate with link-local address or not. examples) telnet fe80::20:ad30:1200 or ping fe80::20:ad30:1200 or ftp fe80::20:ad30:1200 or somthing like that. I think it is possible. Am I right ? Lee Wangbong. DCN-SSU-KOREA From kjum@hyuee.hanyang.ac.kr Mon Aug 18 09:54:11 1997 From: kjum@hyuee.hanyang.ac.kr (Uhm, Ki Jong) Date: Mon, 18 Aug 1997 17:54:11 +0900 Subject: about link local address References: <3.0.1.32.19970818105330.006a446c@dcn.soongsil.ac.kr> Message-ID: <33F80DB3.6DC7@hyuee.hanyang.ac.kr> Lee Wangbong wrote: > > Hi! > > I have one question about link local address. > > That is, > > I wonder about whether IPv6 hosts can communicate with link-local address > or not. > > examples) > telnet fe80::20:ad30:1200 > or ping fe80::20:ad30:1200 > or ftp fe80::20:ad30:1200 or somthing like that. > > I think it is possible. > > Am I right ? > > Lee Wangbong. > DCN-SSU-KOREA Yes, if they are in the same link. I have tested that at my machines. From bmanning@ISI.EDU Mon Aug 18 22:51:03 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Mon, 18 Aug 1997 14:51:03 -0700 (PDT) Subject: 6bone backbone planning & move to testing aggregation address In-Reply-To: from "Bob Fink" at Aug 14, 97 10:31:52 pm Message-ID: <199708182151.AA07583@zed.isi.edu> > 1. that we assign Testing pTLAs (i.e., pseudo TLAs assigned from the NLA1 > field of the 6bone Test address allocation) from the Test Aggregation > addressing I-D as follows: > > 3FFE::0/16 Yo Bob, What name servers do you want for this prefix? You'll have to take care of performing each of the sub-delegations and each site will have to agree to perform the subdelegations under them... (ad nausua). Which is much the same as today, as is seen w/ JANET and the DoE/NERSC prefixes. -- --bill From emace@bcm.tmc.edu Tue Aug 19 17:50:32 1997 From: emace@bcm.tmc.edu (Scott Mace) Date: Tue, 19 Aug 1997 11:50:32 -0500 (CDT) Subject: 6bone hookup Message-ID: <199708191650.LAA02804@bandicoot.ssctr.bcm.tmc.edu> Baylor College of Medicine is interested in connecting to the 6bone. We will be using cisco equipment and would like to do bgp4+. It was suggested a while back that we connect via cicnet, Dorian? We will be ready to to the actual tunnel in about 1 week. Scott From bmanning@ISI.EDU Tue Aug 19 18:21:58 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 19 Aug 1997 10:21:58 -0700 (PDT) Subject: 6bone backbone planning & move to testing aggregation address In-Reply-To: <970819143800.ZM14257@rama.imag.fr> from "Alain Durand" at Aug 19, 97 02:38:00 pm Message-ID: <199708191721.AA22305@zed.isi.edu> > > On Aug 18, 2:51pm, bmanning@ISI.EDU wrote: > > > > 3FFE::0/16 > > > > Yo Bob, > > What name servers do you want for this prefix? You'll have to > > take care of performing each of the sub-delegations and each site will have > > to agree to perform the subdelegations under them... (ad nausua). > > > > I'm willing to be secondary Name Server fro E.F.F.3.ip6.int if needed. > (I'm already secondary of ip6.int) > > - Alain. > Done... ; ID (aggregatable addresses) Munich IETF BOF e.f.f.3.ip6.int. in ns ns.isi.edu. in ns imag.imag.fr. ; -- --bill From bmanning@ISI.EDU Tue Aug 19 18:31:24 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 19 Aug 1997 10:31:24 -0700 (PDT) Subject: three letter acronyms (TLAs) Message-ID: <199708191731.AA22465@zed.isi.edu> Hi, Will the good folks at these sites contact me w/ the (min) two nameservers that will be used for the TLA delegations? TELEBIT/DK 3FFE:0100::/24 SICS/SE 3FFE:0200::/24 G6/FR 3FFE:0300::/24 JOIN/DE 3FFE:0400::/24 WIDE/JP 3FFE:0500::/24 SURFNET/NL 3FFE:0600::/24 ESNET/US 3FFE:0700::/24 CICNET/US 3FFE:0800::/24 ISI-LAP/US 3FFE:0800::/24 NWNET/US 3FFE:0A00::/24 VIAGENIE/CA 3FFE:0B00::/24 CISCO/US 3FFE:0C00::/24 ANS/US 3FFE:0D00::/24 IFB/UK 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT/IT 3FFE:1000::/24 UUNET/UK 3FFE:1100::/24 DIGITAL-CA/US 3FFE:1200::/24 BAY/US 3FFE:1300::/24 UNI-C/DK 3FFE:1400::/24 I'll have the ISI-LAP site up shortly. -- "When in doubt, Twirl..." -anon From bmanning@ISI.EDU Tue Aug 19 18:42:09 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 19 Aug 1997 10:42:09 -0700 (PDT) Subject: tla delegations Message-ID: <199708191742.AA22629@zed.isi.edu> 34% dig @ns e.f.f.3.ip6.int. ns ; <<>> DiG 2.0 <<>> @ns e.f.f.3.ip6.int. ns ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 13 ;; flags: qr aa rd ra ; Ques: 1, Ans: 2, Auth: 0, Addit: 2 ;; QUESTIONS: ;; e.f.f.3.ip6.int, type = NS, class = IN ;; ANSWERS: e.f.f.3.ip6.int. 129600 NS imag.imag.fr. e.f.f.3.ip6.int. 129600 NS ns.isi.edu. .... 35% dig @ns 0.0.8.0.e.f.f.3.ip6.int. ns ; <<>> DiG 2.0 <<>> @ns 0.0.8.0.e.f.f.3.ip6.int. ns ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 10 ;; flags: qr aa rd ra ; Ques: 1, Ans: 2, Auth: 0, Addit: 2 ;; QUESTIONS: ;; 0.0.8.0.e.f.f.3.ip6.int, type = NS, class = IN ;; ANSWERS: 0.0.8.0.e.f.f.3.ip6.int. 129600 NS orb.isi.edu. 0.0.8.0.e.f.f.3.ip6.int. 129600 NS NS.isi.edu. .... 36% dig @ns 0.0.f.0.e.f.f.3.ip6.int. ns ; <<>> DiG 2.0 <<>> @ns 0.0.f.0.e.f.f.3.ip6.int. ns ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 11 ;; flags: qr rd ra ; Ques: 1, Ans: 2, Auth: 0, Addit: 2 ;; QUESTIONS: ;; 0.0.f.0.e.f.f.3.ip6.int, type = NS, class = IN ;; ANSWERS: 0.0.f.0.e.f.f.3.ip6.int. 129600 NS avarice.inner.net. 0.0.f.0.e.f.f.3.ip6.int. 129600 NS buzzcut.ipv6.nrl.navy.mil. .... Next? -- "When in doubt, Twirl..." -anon From crawdad@fnal.gov Tue Aug 19 20:47:24 1997 From: crawdad@fnal.gov (Matt Crawford) Date: Tue, 19 Aug 1997 14:47:24 -0500 Subject: tla delegations In-Reply-To: Your message of Tue, 19 Aug 1997 10:42:09 PDT. <199708191742.AA22629@zed.isi.edu> Message-ID: <199708191947.OAA04202@gungnir.fnal.gov> > 0.0.8.0.e.f.f.3.ip6.int. 129600 NS orb.isi.edu. > 0.0.8.0.e.f.f.3.ip6.int. 129600 NS NS.isi.edu. > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS avarice.inner.net. > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS buzzcut.ipv6.nrl.navy.mil. Whoa! Too many zeros! These are supposed to be /24's you're delegating. Matt From bmanning@ISI.EDU Wed Aug 20 00:02:36 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Tue, 19 Aug 1997 16:02:36 -0700 (PDT) Subject: three letter acronyms (TLAs) (fwd) Message-ID: <199708192302.AA27192@zed.isi.edu> > From: "Rebecca L. Nitzan" > > >Hi, > > Will the good folks at these sites contact me w/ the (min) two > >nameservers that will be used for the TLA delegations? > > > >CICNET/US 3FFE:0800::/24 > >ISI-LAP/US 3FFE:0800::/24 > ^^ typo? > >NWNET/US 3FFE:0A00::/24 > >VIAGENIE/CA 3FFE:0B00::/24 > >CISCO/US 3FFE:0C00::/24 > >ANS/US 3FFE:0D00::/24 > >IFB/UK 3FFE:0E00::/24 > >NRL/US 3FFE:0F00::/24 > >CSELT/IT 3FFE:1000::/24 > >UUNET/UK 3FFE:1100::/24 > >DIGITAL-CA/US 3FFE:1200::/24 > >BAY/US 3FFE:1300::/24 > >UNI-C/DK 3FFE:1400::/24 and Matt Crawford points out that we have too many zeros here for /24s. So, IMHO, I'll move CICnet/US to 3FFE:1500:: or CICnet/US to 3FFE:0900:: and ask if we are going on /32 bounds or not. Your feedback is appreciated. -- "When in doubt, Twirl..." -anon From sean@ntr.net Wed Aug 20 02:25:20 1997 From: sean@ntr.net (Sean McPherson) Date: Tue, 19 Aug 1997 21:25:20 -0400 (EDT) Subject: Getting Started Message-ID: <199708200125.VAA11095@ha1.ntr.net> Hello All! My name is Sean McPherson, and I'm a systems admin for NTR.Net Corporation. We're a national ISP based in louisville, Kentucky, US. We try to stay on top of everything, so I've been reading everything I can about IPV6. And before you ask, no it's not a passing fad or something I've been assigned at work :) The first practical experience I had w/ IPV6 was w/ the development kernels on my linux boxi, and since I'd heard so much uproar about it for the past few years, I got really interested. Now, I'm trying to find out how to go about setting up a decent site to connect thru 6bone. I've read thru the web site, most of the RFC's, and some of the other things I've found, but I expect this is a bit touch and go at this point. I have a few questions that I haven't been able to find answers on, so I'll try to be as precise as possible. We presently route thru UUNET and GRIDNET, and our routing hardware consists of Cisco 7500's. I know Cisco has quite a bit going w/ 6bone, so I'm hoping for some pointers for more info on what I'll need to do to even get packets thru :) As far as software/OS's go, I'm using a few linux boxi (they make great test machines, even if we don't use them for production purposes) and SGI indy's to try this out. I have the linux boxes pretty well configures so far as the actual IPV6 goes, but after that I expect all the rules of IP and routing to change (I've read enuff of the RFC's and seen the 6bone network layout to expect at least some weirdness). 1) What kind of Cisco's presently work well w/ IPV6? If I need a revision for the 7500, what patch level should I be at? 2) Who do I contact for the network addressing specs 6bone is using, and/or apply for an IP header block for this testing? 3) What kind of official channels should I be going thru? :) Thanks in advance for any help you can offer, and I am really looking forward to seeing what happens. After all, when there are enuff IP's for every electrical device in my apartment, what can be wrong???!!! -- Sean McPherson sean@ntr.net Systems Administration NTR.Net Corporation -- REALITY.SYS corrupted. Reboot universe? [Y n] From Alain.Durand@imag.fr Wed Aug 20 08:16:08 1997 From: Alain.Durand@imag.fr (Alain Durand) Date: Wed, 20 Aug 1997 09:16:08 +0200 Subject: three letter acronyms (TLAs) (fwd) In-Reply-To: bmanning@ISI.EDU "Re: three letter acronyms (TLAs) (fwd)" (Aug 19, 4:02pm) References: <199708192302.AA27192@zed.isi.edu> Message-ID: <970820091608.ZM15716@rama.imag.fr> On Aug 19, 4:02pm, bmanning@ISI.EDU wrote: > Subject: Re: three letter acronyms (TLAs) (fwd) > > >DIGITAL-CA/US 3FFE:1200::/24 > > >BAY/US 3FFE:1300::/24 > > >UNI-C/DK 3FFE:1400::/24 > > and Matt Crawford points out that we have too many zeros here for /24s. > > So, > IMHO, I'll move CICnet/US to 3FFE:1500:: > or CICnet/US to 3FFE:0900:: > > and ask if we are going on /32 bounds or not. > > > Your feedback is appreciated. On Aug 19, 2:47pm, Matt Crawford wrote: > Subject: Re: tla delegations > > 0.0.8.0.e.f.f.3.ip6.int. 129600 NS orb.isi.edu. > > 0.0.8.0.e.f.f.3.ip6.int. 129600 NS NS.isi.edu. > > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS avarice.inner.net. > > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS buzzcut.ipv6.nrl.navy.mil. > > Whoa! Too many zeros! These are supposed to be /24's you're delegating. > > Matt >-- End of excerpt from Matt Crawford The pTLA (pseudo TLA) are /24. Their correct representation as prefixes is for example 3ffe:0300::/24 But when you delegate the reverse for DNS, it should be: 3.0.e.f.f.3.ip6.int. - Alain. From erik-jan.bos@surfnet.nl Wed Aug 20 17:34:42 1997 From: erik-jan.bos@surfnet.nl (Erik-Jan Bos) Date: Wed, 20 Aug 1997 18:34:42 +0200 Subject: tla delegations In-Reply-To: Your message of Tue, 19 Aug 1997 10:42:09 -0700. Message-ID: <17852.872094882@surfnet.nl> Bill, > 36% dig @ns 0.0.f.0.e.f.f.3.ip6.int. ns > > ; <<>> DiG 2.0 <<>> @ns 0.0.f.0.e.f.f.3.ip6.int. ns > ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 11 > ;; flags: qr rd ra ; Ques: 1, Ans: 2, Auth: 0, Addit: 2 > ;; QUESTIONS: > ;; 0.0.f.0.e.f.f.3.ip6.int, type = NS, class = IN > > ;; ANSWERS: > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS avarice.inner.net. > 0.0.f.0.e.f.f.3.ip6.int. 129600 NS buzzcut.ipv6.nrl.navy.mil. > > .... > > Next? 6.0.e.f.f.3.ip6.int. IN NS zesbot.ipv6.surfnet.nl. 6.0.e.f.f.3.ip6.int. IN NS ns1.surfnet.nl. Next? __ Erik-Jan. From b20gross@isbe.ch Fri Aug 22 03:45:15 1997 From: b20gross@isbe.ch (WALTER GROSSENBACHER) Date: Thu, 21 Aug 1997 19:45:15 -0700 Subject: Where do I find my most appropriate attachment point on the 6bone ? Message-ID: <33FCFD3B.5788@isbe.ch> Hi ! We are a Swiss Engineer School and we would like to participate the 6bone for test reasons. One of our problems is, that we need to know where we can connect the 6bone. An other problem we've got is, that we don't know which ASN number we have to use (is it AS559 for SWITCH ?). And last but not least : Where and how do we got to register our IPv6 addresses? I thank you for your assistance ! Best regards Walter Grossenbacher From Alain.Durand@imag.fr Thu Aug 21 20:58:56 1997 From: Alain.Durand@imag.fr (Alain Durand) Date: Thu, 21 Aug 1997 21:58:56 +0200 Subject: Where do I find my most appropriate attachment point on the 6bone ? In-Reply-To: WALTER GROSSENBACHER "Where do I find my most appropriate attachment point on the 6bone ?" (Aug 21, 7:45pm) References: <33FCFD3B.5788@isbe.ch> Message-ID: <970821215856.ZM18405@rama.imag.fr> Ask Simon.Leinen@switch.ch from SWITCH. He already has a 6bone site. On Aug 21, 7:45pm, WALTER GROSSENBACHER wrote: > Subject: Where do I find my most appropriate attachment point on the 6bone > Hi ! > We are a Swiss Engineer School and we would like to participate the > 6bone for test reasons. > One of our problems is, that we need to know where we can connect the > 6bone. > An other problem we've got is, that we don't know which ASN number we > have to use (is it AS559 for SWITCH ?). > And last but not least : Where and how do we got to register our IPv6 > addresses? > I thank you for your assistance ! > > Best regards > > Walter Grossenbacher >-- End of excerpt from WALTER GROSSENBACHER From bmanning@ISI.EDU Thu Aug 21 23:34:20 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Thu, 21 Aug 1997 15:34:20 -0700 (PDT) Subject: Where do I find my most appropriate attachment point on the 6bone ? In-Reply-To: <33FCFD3B.5788@isbe.ch> from "WALTER GROSSENBACHER" at Aug 21, 97 07:45:15 pm Message-ID: <199708212234.AA05453@zed.isi.edu> > Hi ! > One of our problems is, that we need to know where we can connect the > 6bone. > An other problem we've got is, that we don't know which ASN number we > have to use (is it AS559 for SWITCH ?). > And last but not least : Where and how do we got to register our IPv6 > addresses? > I thank you for your assistance ! > > Best regards > > Walter Grossenbacher A couple of pointers might help. RFC 1897 is useful www.6bone.net is very helpful -- --bill From bmanning@ISI.EDU Fri Aug 22 18:46:06 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 22 Aug 1997 10:46:06 -0700 (PDT) Subject: moving on.... Message-ID: <199708221746.AA20715@zed.isi.edu> ;; ANSWERS: 6.0.e.f.f.3.ip6.int. 129600 NS ns1.surfnet.nl. 6.0.e.f.f.3.ip6.int. 129600 NS zesbot.ipv6.surfnet.nl. ;; ADDITIONAL RECORDS: ns1.surfnet.nl. 345365 A 192.87.106.101 zesbot.ipv6.surfnet.nl. 16268 28 ??? zesbot.ipv6.surfnet.nl. 16268 28 ??? zesbot.ipv6.surfnet.nl. 16268 A 192.87.110.60 ... ;; ANSWERS: 1.1.e.f.f.3.ip6.int. 129600 NS ns1.pipex.net. 1.1.e.f.f.3.ip6.int. 129600 NS ns0.pipex.net. ;; ADDITIONAL RECORDS: ns1.pipex.net. 368620 A 158.43.192.7 ns0.pipex.net. 408840 A 158.43.128.8 ns0.pipex.net. 27036 A 158.43.192.7 (whos that using AAAA records!) --bill From lzs@pobox.com Fri Aug 22 22:13:30 1997 From: lzs@pobox.com (Lai Zit Seng) Date: Sat, 23 Aug 1997 05:13:30 +0800 (SGT) Subject: call for 6bone TLA participants for Oct. 1 renumbering of backbone In-Reply-To: Message-ID: Hello, I would like to request a pTLA for the National University of Singapore (NUS). We already have a 6bone gateway running on an IPv6 capable router doing BGPv4 with IPv6 extensions. We also have IPv6 routers running on FreeBSD, Linux and Solaris on our internal network. We currently connect to CISCO and provide IPv6 connectivity to several islands in NUS. We have several projects dealing with IPsec, RSVP, mobile IPv6 and OSPF in progress. We will be very happy to be directly involved in 6bone backbone operations to provide a better testbed for our projects as well as to gain operation experience. We can manage with this transition and beyond. We will be glad to provide 6bone connectivity to other sites, especially for those in this region. If you have any questions regarding our application, please direct them to me. Regards, .lzs On Thu, 14 Aug 1997, Bob Fink wrote: > Per the 6bone backbone ad hoc meeting in Munich, I am calling for those > interested in being an early 6bone test pTLA (i.e., pseudo TLAs assigned > from the NLA1 field of the 6bone Test address allocation) when the > renumbering to the new Aggregation-based unicast address format is started > on 1 October. > > Requirements are willingness and ability to actively participate in this > timeframe, and demonstrated experience with IPv6 and the 6bone. > > Please send your requests to become a 6bone pTLA to the 6bone mail list > with text sufficient to describe your interest and qualifications. > > I will assign test pTLAs to all reasonable request at this time. > > Thanks, > > Bob > > > > From RLFink@lbl.gov Mon Aug 25 16:22:05 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 25 Aug 1997 08:22:05 -0700 Subject: returning from travel and pTLAs Message-ID: I have just returned to the office after two weeks of travel in Europe for IETF and other business. Sorry to have been unresponsive to the backbone activity while I was gone, I'll send email to the list on new pTLAs etc. later today. Thanks, Bob From halacha@montgomerybell.com Mon Aug 25 18:10:10 1997 From: halacha@montgomerybell.com (Alan Halachmi) Date: Mon, 25 Aug 1997 12:10:10 -0500 (CDT) Subject: Connection Message-ID: Hey, I'm looking for a 6bone connection for an ISP and their "intern" program. The ISP is called Telalink and is a medium sized ISP running 4 out-bound T's. We are located in Nashville, TN and would like to get connected to the 6bone as soon as we can. Everyone here is excited to get connected and begin learning about this exciting new technology. If there is anyone who could help us connect (we need a connection point) we'd really appreciate that. Alan Halachmi mailto:HalachA@MontgomeryBell.com From masaki@merit.edu Mon Aug 25 18:52:21 1997 From: masaki@merit.edu (Masaki Hirabaru) Date: Mon, 25 Aug 1997 13:52:21 -0400 Subject: call for 6bone TLA participants for Oct. 1 renumbering of backbone In-Reply-To: Your message of "Thu, 14 Aug 1997 22:32:23 +0200." Message-ID: <199708251752.NAA09812@merit.edu> Bob and 6bone folks, We would like to be one of early 6bone test pTLAs. Interests: Our immediate interests are in implementing IPv6 routing protocols on MRT (see details at http://www.merit.edu/~mrt/), expanding our tools in MRT with IPv6, and also analyzing the early 6bone with the tools to provide useful information for developing IPv6/6bone. We are also going to have an early IPv6 experience with our operational staffs in managing our 6bone connection, participating in early trials, and also providing an application over the 6bone. Qualifications: We have implemented RIPng on MRT and tested it over 6bone with a couple of implementations. We have ported our code on IPv6 kernels developed by Sun, INRIA, Linux, NRL and WIDE, and are keeping cooperative with these developers by developing on their kernels, as well as other router vendors by testing interoperability over the 6bone. Now we are finalizing an implementation of BGP4+ available on MRT, which includes a couple of BGP4+ tools to help a test and analysis on routing. We are also planing to move our 6bone router to our NOC where we can manage it well to provide a more stable 6bone connection for our neighborhood who wants to join the 6bone. I'm now working on MRT and 6bone at Merit, and can actively participate in this transition with our team members and of other Merit projects, GateD and so on. Thank you, Masaki Hirabaru Merit Network, Inc. > Date: Thu, 14 Aug 1997 22:32:23 +0200 > To: 6bone@ISI.EDU (6BONE Mailer) > From: Bob Fink > Subject: call for 6bone TLA participants for Oct. 1 renumbering of > backbone > Cc: RLFink@lbl.gov (Bob Fink LBNL) > Sender: owner-6bone@ISI.EDU > Precedence: bulk > > Per the 6bone backbone ad hoc meeting in Munich, I am calling for those > interested in being an early 6bone test pTLA (i.e., pseudo TLAs assigned > from the NLA1 field of the 6bone Test address allocation) when the > renumbering to the new Aggregation-based unicast address format is started > on 1 October. > > Requirements are willingness and ability to actively participate in this > timeframe, and demonstrated experience with IPv6 and the 6bone. > > Please send your requests to become a 6bone pTLA to the 6bone mail list > with text sufficient to describe your interest and qualifications. > > I will assign test pTLAs to all reasonable request at this time. > > Thanks, > > Bob > > From RLFink@lbl.gov Tue Aug 26 02:47:30 1997 From: RLFink@lbl.gov (Bob Fink) Date: Mon, 25 Aug 1997 18:47:30 -0700 Subject: pTLA assignments Message-ID: I have sorted thru the various pTLA requests and am assigning more below. First, the corrected original list (ISI-LAP was 0800, should have been 0900) of original pTLA assignments is: TELEBIT/DK 3FFE:0100::/24 SICS/SE 3FFE:0200::/24 G6/FR 3FFE:0300::/24 JOIN/DE 3FFE:0400::/24 WIDE/JP 3FFE:0500::/24 SURFNET/NL 3FFE:0600::/24 ESNET/US 3FFE:0700::/24 CICNET/US 3FFE:0800::/24 ISI-LAP/US 3FFE:0900::/24 NWNET/US 3FFE:0A00::/24 VIAGENIE/CA 3FFE:0B00::/24 CISCO/US 3FFE:0C00::/24 ANS/US 3FFE:0D00::/24 IFB/UK 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT/IT 3FFE:1000::/24 UUNET/UK 3FFE:1100::/24 DIGITAL-CA/US 3FFE:1200::/24 BAY/US 3FFE:1300::/24 UNI-C/DK 3FFE:1400::/24 And the new pTLAs are: UO 3FFE:1500::/24 NUS 3FFE:1600::/24 MREN 3FFE:1700::/24 INTEROP 3FFE:1800::/24 3COM 3FFE:1900::/24 CAIRN 3FFE:1A00::/24 VERIO 3FFE:1B00::/24 MERIT 3FFE:1C00::/24 And as Craig Metz is willing to test pTLA 0: INNER 3FFE:0000::/24 Thanks, Bob From RLFink@lbl.gov Tue Aug 26 18:07:55 1997 From: RLFink@lbl.gov (Bob Fink) Date: Tue, 26 Aug 1997 10:07:55 -0700 Subject: update pTLA list Message-ID: Missed the ATT-LABS-EUROPE folk on the last list: INNER 3FFE:0000::/24 INNER 3FFE:0000::/24 SICS/SE 3FFE:0200::/24 G6/FR 3FFE:0300::/24 JOIN/DE 3FFE:0400::/24 WIDE/JP 3FFE:0500::/24 SURFNET/NL 3FFE:0600::/24 ESNET/US 3FFE:0700::/24 CICNET/US 3FFE:0800::/24 ISI-LAP/US 3FFE:0900::/24 NWNET/US 3FFE:0A00::/24 VIAGENIE/CA 3FFE:0B00::/24 CISCO/US 3FFE:0C00::/24 ANS/US 3FFE:0D00::/24 IFB/UK 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT/IT 3FFE:1000::/24 UUNET/UK 3FFE:1100::/24 DIGITAL-CA/US 3FFE:1200::/24 BAY/US 3FFE:1300::/24 UNI-C/DK 3FFE:1400::/24 UO 3FFE:1500::/24 NUS 3FFE:1600::/24 MREN 3FFE:1700::/24 INTEROP 3FFE:1800::/24 3COM 3FFE:1900::/24 CAIRN 3FFE:1A00::/24 VERIO 3FFE:1B00::/24 MERIT 3FFE:1C00::/24 ATT-LABS-EUROPE 3FFE:1D00::/24 Thanks, Bob From RLFink@lbl.gov Wed Aug 27 15:37:34 1997 From: RLFink@lbl.gov (Bob Fink) Date: Wed, 27 Aug 1997 07:37:34 -0700 Subject: current pTLA list - 27Aug97 Message-ID: Have added SWISS-TELECOM to the list. Also note that I'm now using the 6bone registry name for the allocation name, and have noted where there is no 6bone registry entry yet. Also, the 6bone home page now has a pointer to the pTLA list: http://www.6bone.net/6bone_pTLA_list.html INNER 3FFE:0000::/24 TELEBIT 3FFE:0100::/24 SICS 3FFE:0200::/24 G6 3FFE:0300::/24 JOIN 3FFE:0400::/24 WIDE 3FFE:0500::/24 SURFNET 3FFE:0600::/24 ESNET 3FFE:0700::/24 CICNET 3FFE:0800::/24 ISI-LAP 3FFE:0900::/24 NWNET 3FFE:0A00::/24 VIAGENIE 3FFE:0B00::/24 CISCO 3FFE:0C00::/24 ANS 3FFE:0D00::/24 IFB 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT 3FFE:1000::/24 UUNET 3FFE:1100::/24 DIGITAL-CA 3FFE:1200::/24 BAY 3FFE:1300::/24 UNI-C 3FFE:1400::/24 UO 3FFE:1500::/24 NUS-IRDU 3FFE:1600::/24 MREN 3FFE:1700::/24 (no 6bone registry entry) INTEROP 3FFE:1800::/24 3COM 3FFE:1900::/24 (no 6bone registry entry) CAIRN 3FFE:1A00::/24 VERIO 3FFE:1B00::/24 (no 6bone registry entry) MERIT 3FFE:1C00::/24 ATT-LABS-EUROPE 3FFE:1D00::/24 SWISS-TELECOM 3FFE:1E00::/24 Thanks, Bob From davidk@ISI.EDU Wed Aug 27 23:58:47 1997 From: davidk@ISI.EDU (davidk@ISI.EDU) Date: Wed, 27 Aug 1997 15:58:47 -0700 (PDT) Subject: ftp registry removed Message-ID: <9708272258.AA09145@brind.isi.edu> Hi, As agreed earlier, the old ftp registry at RIPE has been removed and cannot be updated anymore. In case you have a need to review the old data, it will continue to be available in a tar archive at: ftp://whois.6bone.net/6bone/old_RIPE_ftp_registry.tar.gz You can find a dump of the full dataset of the new registry at the same location. I hope this helps, David K. --- From RLFink@lbl.gov Thu Aug 28 14:29:47 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 28 Aug 1997 06:29:47 -0700 Subject: ftp registry removed In-Reply-To: <9708272258.AA09145@brind.isi.edu> Message-ID: David, At 3:58 PM -0700 8/27/97, davidk@ISI.EDU wrote: >Hi, > >As agreed earlier, the old ftp registry at RIPE has been removed and >cannot be updated anymore. > >In case you have a need to review the old data, it will continue to be >available in a tar archive at: > >ftp://whois.6bone.net/6bone/old_RIPE_ftp_registry.tar.gz > >You can find a dump of the full dataset of the new registry at the same >location. > >I hope this helps, Thanks for closing this out. I have changed the 6bone home page pointer to the old registry to now point to this tar file (it's at the very bottom of the page). Thanks, Bob From RLFink@lbl.gov Thu Aug 28 14:48:57 1997 From: RLFink@lbl.gov (Bob Fink) Date: Thu, 28 Aug 1997 06:48:57 -0700 Subject: current pTLA list - 28Aug97 Message-ID: Have added NETCOM-UK and SWITCH to the list. http://www.6bone.net/6bone_pTLA_list.html INNER 3FFE:0000::/24 TELEBIT 3FFE:0100::/24 SICS 3FFE:0200::/24 G6 3FFE:0300::/24 JOIN 3FFE:0400::/24 WIDE 3FFE:0500::/24 SURFNET 3FFE:0600::/24 ESNET 3FFE:0700::/24 CICNET 3FFE:0800::/24 ISI-LAP 3FFE:0900::/24 NWNET 3FFE:0A00::/24 VIAGENIE 3FFE:0B00::/24 CISCO 3FFE:0C00::/24 ANS 3FFE:0D00::/24 IFB 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT 3FFE:1000::/24 UUNET 3FFE:1100::/24 DIGITAL-CA 3FFE:1200::/24 BAY 3FFE:1300::/24 UNI-C 3FFE:1400::/24 UO 3FFE:1500::/24 NUS-IRDU 3FFE:1600::/24 MREN 3FFE:1700::/24 (no 6bone registry entry) INTEROP 3FFE:1800::/24 3COM 3FFE:1900::/24 (no 6bone registry entry) CAIRN 3FFE:1A00::/24 VERIO 3FFE:1B00::/24 (no 6bone registry entry) MERIT 3FFE:1C00::/24 ATT-LABS-EUROPE 3FFE:1D00::/24 SWISS-TELECOM 3FFE:1E00::/24 NETCOM-UK 3FFE:1F00::/24 SWITCH 3FFE:2000::/24 Thanks, Bob From andrea.chierici@cnaf.infn.it Fri Aug 29 09:40:13 1997 From: andrea.chierici@cnaf.infn.it (Andrea Chierici) Date: Fri, 29 Aug 1997 10:40:13 +0200 (MET DST) Subject: A question about TLA assignment Message-ID: Hi folks, during the 6bone backbone meeting in Munich it was told to me from Bob that the 20 already assigned TLA had to be the only one for the transition period... Now I see that a lot of new sites are joining the group and I wonder why. Thanks, Andrea ----------------------------------------- Andrea Chierici, Computer Science Student INFN-CNAF Bologna ITALY ----------------------------------------- From RLFink@lbl.gov Fri Aug 29 15:05:14 1997 From: RLFink@lbl.gov (Bob Fink) Date: Fri, 29 Aug 1997 07:05:14 -0700 Subject: A question about TLA assignment In-Reply-To: Message-ID: Andrea, At 1:40 AM -0700 8/29/97, Andrea Chierici wrote: >Hi folks, >during the 6bone backbone meeting in Munich it was told to me from Bob >that the 20 already assigned TLA had to be the only one for the transition >period... Now I see that a lot of new sites are joining the group and I >wonder why. At the backbone meeting it was agreed to NOT close off the list of those participating as it could lead to a better structured backbone from the start. See the minutes below. Thanks, Bob ======== X-Sender: (Unverified) Mime-Version: 1.0 Date: Thu, 14 Aug 1997 22:31:52 +0200 To: 6bone@isi.edu (6BONE Mailer) From: Bob Fink Subject: 6bone backbone planning & move to testing aggregation address format Cc: RLFink@lbl.gov (Bob Fink LBNL) 6bone backbone planning meeting - 14 August 1997, Munich, DE. Alain Durand held a BOF for those interested in 6bone backbone planning under the new test aggregation address format. There were 27 people in attendance. Alain Durand (G6, FR) spoke on the need to minimize backone tunnels to clean up routing. There were comments for this, explaing the reasons why it is needed at this time, and comments as to why we shouldn't worry about this. Stephen Stuart (Digital-ca, US) spoke on reasons to cleanup peering, and to have multiple interconnect points for ISP TLA's. Matt Crawford showed various multi-prefix scenarios. There was a general consensus that there was a need to simplify the 6bone bacbone topology. Bob Fink (ESnet/LBNL, US) then led a discussion to generate a plan for readdressing and backbone restructuring. This discussion led to the following general agreements: 1. that we assign Testing pTLAs (i.e., pseudo TLAs assigned from the NLA1 field of the 6bone Test address allocation) from the Test Aggregation addressing I-D as follows: TELEBIT/DK 3FFE:0100::/24 SICS/SE 3FFE:0200::/24 G6/FR 3FFE:0300::/24 JOIN/DE 3FFE:0400::/24 WIDE/JP 3FFE:0500::/24 SURFNET/NL 3FFE:0600::/24 ESNET/US 3FFE:0700::/24 CICNET/US 3FFE:0800::/24 ISI-LAP/US 3FFE:0800::/24 NWNET/US 3FFE:0A00::/24 VIAGENIE/CA 3FFE:0B00::/24 CISCO/US 3FFE:0C00::/24 ANS/US 3FFE:0D00::/24 IFB/UK 3FFE:0E00::/24 NRL/US 3FFE:0F00::/24 CSELT/IT 3FFE:1000::/24 UUNET/UK 3FFE:1100::/24 DIGITAL-CA/US 3FFE:1200::/24 BAY/US 3FFE:1300::/24 UNI-C/DK 3FFE:1400::/24 Note: we started at 1 because Bob is nervous about using 0 :-) 2. that we establish October 1 as the start date for renumbering the backbone to testing aggregation addresses, with the goal of November 1 for coming online. 3. that all backbone sites will peer with BGP4+, and only BGP4+. 4. that the old testing addresses (RFC 1897) be discontinued on the backbone as early as October 1 (by sites already renumbered) and not later than November 1 when the newly addressed backbone is scheduled to be fully online. 5. that a call for new pTLA candidates be issued immediately, for inclusion in the October 1 renumbering/restructuring, where the criteria to be applied for inclusion is willingness and ability to actively participate in this timeframe, and demonstrated experience with IPv6 and the 6bone. 6. that a call for existing backbone sites (given a pTLA above) be made to decide themselves if they are able to participate in this renumbering/ resructuring effort, and be encouraged to give back their pTLA assignment for now if they aren't able to participate. (Note: any site doing this can easily reapply at a later time.) -end From roque@cisco.com Fri Aug 29 16:43:08 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 08:43:08 -0700 (PDT) Subject: A question about TLA assignment In-Reply-To: References: Message-ID: <199708291543.IAA08371@pedrom-ultra.cisco.com> >>>>> "Andrea" == Andrea Chierici writes: Andrea> Hi folks, during the 6bone backbone meeting in Munich it Andrea> was told to me from Bob that the 20 already assigned TLA Andrea> had to be the only one for the transition period... Now I Andrea> see that a lot of new sites are joining the group and I Andrea> wonder why. Don't worry. Just ask for one. There are still 224 availiable. Pedro. From roque@cisco.com Fri Aug 29 19:34:03 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 11:34:03 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: References: Message-ID: <199708291834.LAA08399@pedrom-ultra.cisco.com> >>>>> "Bob" == Bob Fink writes: Bob> CISCO 3FFE:0C00::/24 Bob, I'd like to carve addresses from a separate TLA for interconnects (i.e. a TLA not associated with any site). It would be nice if somebody will step in and administer such a thing... if not i guess i'll have to volunteer. Pedro. From bmanning@ISI.EDU Fri Aug 29 22:17:15 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 29 Aug 1997 14:17:15 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708291834.LAA08399@pedrom-ultra.cisco.com> from "Pedro Marques" at Aug 29, 97 11:34:03 am Message-ID: <199708292117.AA07153@zed.isi.edu> > > >>>>> "Bob" == Bob Fink writes: > > Bob> CISCO 3FFE:0C00::/24 > > Bob, > > I'd like to carve addresses from a separate TLA for interconnects (i.e. a > TLA not associated with any site). It would be nice if somebody will step > in and administer such a thing... if not i guess i'll have to volunteer. > > Pedro. I was sort of hoping to use the 0000 range for this but craig beat us to it. -- --bill From roque@cisco.com Fri Aug 29 22:30:02 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 14:30:02 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708292117.AA07153@zed.isi.edu> References: <199708291834.LAA08399@pedrom-ultra.cisco.com> <199708292117.AA07153@zed.isi.edu> Message-ID: <199708292130.OAA08628@pedrom-ultra.cisco.com> >>>>> "bmanning" == bmanning writes: >> >>>>> "Bob" == Bob Fink writes: >> Bob> CISCO 3FFE:0C00::/24 >> Bob, >> >> I'd like to carve addresses from a separate TLA for >> interconnects (i.e. a TLA not associated with any site). It >> would be nice if somebody will step in and administer such a >> thing... if not i guess i'll have to volunteer. >> >> Pedro. bmanning> I was sort of hoping to use the 0000 range for this but bmanning> craig beat us to it. Does that mean you volunteer to administer the interconnect space ? Good. How will you delegate it ? I believe the best plan is to just assign /12[6-7] subnets sequentially... I'm in need of 14 subnets... Pedro. From bmanning@ISI.EDU Fri Aug 29 22:42:03 1997 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 29 Aug 1997 14:42:03 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708292130.OAA08628@pedrom-ultra.cisco.com> from "Pedro Marques" at Aug 29, 97 02:30:02 pm Message-ID: <199708292142.AA07519@zed.isi.edu> Only if Bob sets aside a Ptla for this... or everyone can get their numbers from me! -- --bill From roque@cisco.com Fri Aug 29 22:47:25 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 14:47:25 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708292142.AA07519@zed.isi.edu> References: <199708292130.OAA08628@pedrom-ultra.cisco.com> <199708292142.AA07519@zed.isi.edu> Message-ID: <199708292147.OAA08650@pedrom-ultra.cisco.com> >>>>> "bmanning" == bmanning writes: bmanning> Only if Bob sets aside a Ptla for this... or everyone bmanning> can get their numbers from me! I don't see why he shouldn't... And since the whole idea is to have that space independent of a particular site getting numbers from you isn't a proper replacement, imgo... I've no lack of addressing space either :-) Pedro. From crawdad@fnal.gov Fri Aug 29 23:17:22 1997 From: crawdad@fnal.gov (Matt Crawford) Date: Fri, 29 Aug 1997 17:17:22 -0500 Subject: current pTLA list - 28Aug97 In-Reply-To: Your message of Fri, 29 Aug 1997 11:34:03 PDT. <199708291834.LAA08399@pedrom-ultra.cisco.com> Message-ID: <199708292217.RAA12729@gungnir.fnal.gov> > I'd like to carve addresses from a separate TLA for interconnects (i.e. a > TLA not associated with any site). It would be nice if somebody will step > in and administer such a thing... if not i guess i'll have to volunteer. Pedro, Y'know, I've been wondering about the scalability of assigning a TLA per exchange. Since a gigapop is expected to have no more than 10-100 members, if a gigapop is an exchange of the sort that gets a TLA, it just isn't going to fly. Ergo, I'm going to set up my MREN exchange with an pNLA1 of my pTLA while I think about the implications of having disconnected sets of exchanges sharing a TLA. If you want to do likewise and use the same pTLA (I'm willing to do the record keeping), then one of us can become the first to give back a pTLA. Matt From crawdad@fnal.gov Fri Aug 29 23:35:02 1997 From: crawdad@fnal.gov (Matt Crawford) Date: Fri, 29 Aug 1997 17:35:02 -0500 Subject: current pTLA list - 28Aug97 In-Reply-To: Your message of Fri, 29 Aug 1997 15:24:36 PDT. <199708292224.PAA08675@pedrom-ultra.cisco.com> Message-ID: <199708292235.RAA12786@gungnir.fnal.gov> > I wasn't thinking about a TLA per exchange but about a TLA from which > to allocate addresses to use in exchanges... > > Needless to say nobody should annouce routes for that TLA... Oh, right, we ran into this same communication difficulty in the last WG meeting. You're thinking about exchanges where ISP's peer, and I'm thinking about exchanges where a bunch of sites band together and buy their long-haul services from one or more carriers. The latter sort of exchange would be expected to issue globally-routable addresses to its members. Matt From roque@cisco.com Fri Aug 29 23:24:36 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 15:24:36 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708292217.RAA12729@gungnir.fnal.gov> References: <199708291834.LAA08399@pedrom-ultra.cisco.com> <199708292217.RAA12729@gungnir.fnal.gov> Message-ID: <199708292224.PAA08675@pedrom-ultra.cisco.com> >>>>> "Matt" == Matt Crawford writes: >> I'd like to carve addresses from a separate TLA for >> interconnects (i.e. a TLA not associated with any site). It >> would be nice if somebody will step in and administer such a >> thing... if not i guess i'll have to volunteer. Matt> Pedro, Matt> Y'know, I've been wondering about the scalability of Matt> assigning a TLA per exchange. Matt, I wasn't thinking about a TLA per exchange but about a TLA from which to allocate addresses to use in exchanges... Needless to say nobody should annouce routes for that TLA... Pedro. From roque@cisco.com Sat Aug 30 00:05:19 1997 From: roque@cisco.com (Pedro Marques) Date: Fri, 29 Aug 1997 16:05:19 -0700 (PDT) Subject: current pTLA list - 28Aug97 In-Reply-To: <199708292251.WAA03246@inner.net> References: <199708291834.LAA08399@pedrom-ultra.cisco.com> <199708292251.WAA03246@inner.net> Message-ID: <199708292305.QAA08828@pedrom-ultra.cisco.com> >>>>> "Craig" == Craig Metz writes: Craig> In message <199708291834.LAA08399@pedrom-ultra.cisco.com>, Craig> you write: >> I'd like to carve addresses from a separate TLA for >> interconnects (i.e. a TLA not associated with any site). It >> would be nice if somebody will step in and administer such a >> thing... if not i guess i'll have to volunteer. Craig> I can do this if we decide that it's a good thing to Craig> do. Craig> However, I'm not sure that it's a good thing to Craig> do. The question here is whether the addresses associated Craig> with tunnels should be globally reachable or not. Absolutely. Craig> I would Craig> suggest that they should be, in which case they should come Craig> out of the prefix of one of the two sides of the tunnel. It has been done this way until now and it works... The only pontential problem is that when one site renumbers (and i really don't want to discuss if renumbering is a good idea) you "loose" the prefix. Craig> This would all be *a lot* simpler IMO if Craig> implementations had a mode where the global and/or Craig> link-local Link locals cannot be used. Craig> off some other interface could be stolen for BGP Craig> neighbor purposes instead of treating a tunnel as a Craig> bi-directional point-to-point link with both global and Craig> link local addresses. That can be done with global addresses. There are however good reasons to do BGP over bi-directional point-to-point links, simplicity being one of them. Pedro.