From postel@ISI.EDU Tue Mar 19 23:40:42 1996 From: postel@ISI.EDU (postel@ISI.EDU) Date: Tue, 19 Mar 1996 15:40:42 -0800 Subject: test 1 Message-ID: <199603192340.AA10932@zen.isi.edu> Hello. --jon. From kemp@isi.edu Wed Mar 20 00:06:00 1996 From: kemp@isi.edu (Joe Kemp) Date: Tue, 19 Mar 96 16:06:00 PST Subject: Test 1 Message-ID: <199603200006.AA13524@zephyr.isi.edu> This is a test.... --JK From carlton@isi.edu Wed Mar 20 00:07:43 1996 From: carlton@isi.edu (Mike Carlton) Date: Tue, 19 Mar 96 16:07:43 PST Subject: test 2 Message-ID: <199603200007.AA13703@zephyr.isi.edu> test 2 cheers, --mike From carlton@isi.edu Wed Mar 20 00:45:39 1996 From: carlton@isi.edu (Mike Carlton) Date: Tue, 19 Mar 96 16:45:39 PST Subject: Welcome to the 6bone mailing list Message-ID: <199603200045.AA26068@darkstar.isi.edu> The 6bone mailing list is now up and running; you have already been added to it. Currently the list is open, i.e. anyone may join; however only people on the list may send mail to the list. To send mail to the list, send it to <6bone@isi.edu>. If you experience any problems with the list, please let me know and I'll make sure they get resolved. I apologize for the delay in getting this up; I think we have the kinks worked out now. If you want to unsubscribe, send a message to with the line unsubscribe 6bone as the contents of the message. Some other useful commands that majordomo understands are 'help', 'info 6bone' and 'who 6bone'. cheers, --mike carlton@isi.edu From bound@zk3.dec.com Sun Mar 24 18:59:55 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Sun, 24 Mar 96 13:59:55 -0500 Subject: Welcome to the 6bone mailing list In-Reply-To: Your message of "Tue, 19 Mar 96 16:45:39 PST." <199603200045.AA26068@darkstar.isi.edu> Message-ID: <9603241859.AA20741@fwasted.zk3.dec.com> Thanks Mike I will send message out shortly. p.s. Mike Collins can you send me privately your email addr thanks.. /jim From bound@zk3.dec.com Sun Mar 24 19:27:41 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Sun, 24 Mar 96 14:27:41 -0500 Subject: Objective / Tasks / Next Steps ..... Message-ID: <9603241927.AA24685@fwasted.zk3.dec.com> Hi, Sorry I am a bit late. Day job is getting very IPv6 intensive for me. Per our meeting at the IETF L.A. meeting. This is a draft and can we have some discussion. Once we get this past a draft stage we can send out to folks to enhance our mail list and to the IPv6 implementors list. Can we get a volunteer to write up the charter of the 6Bone ????? ************** DRAFT 6Bone ******************* Objective: To establish an Internet 6Bone network to foster the development and communications of IPv6. The model will be based from the experience based on the Mbone. Three initial core geographic areas will be established with focused DRIs: - Asia (Jun Murai - via WIDE) - U.S. (ISI seems to be the right place Mike Carlton ??) - Europe (Brian Carpenter to suggest names. This is done Brian sent me some names I will contact.) These DRIs would coordinate the 6Bone effort in each geography and verify persons or entities would log their participation on the 6Bone. Name - Two different names suggested: Globabl IPv6 Infrastructure (GII).. Not politically good. But this is the one I gave Jun for his Miti proposal for now. Information IPv6 Infrastructure (or I-Cubed).... Can we resolve this now ????? Hardware/Software: Initially use existing IPv6 implementors to get started and existing IPv6 Tunnel networks today. We need to get a commit from vendors to donate or provide at a reduced cost Hardware and Software for IPv6 Hosts and Routers. Need solid spec for RIPv6 to get the initial routing underway. A public domain RIPv6 would be nice ???? Jun Murai will attempt funding to set up IPv6 first in WIDE and then in Asia. ES-NET and WIDE may be able to connect via same T1 link in SanFrancisco provider. Need a list of public domain software pointers. Need a WEB page or added words to IPng page. Need to have White Board/VAT running on IPv6. Network Topology: Need to define IPv6 legs and tunnels in each geography so we can get an idea of how this can work. Tasks: 1. Select a name. (This List) 2. 6bone Charter and Announcment (Volunteer Needed ???) 3. Asia Logistics (Jun Murai In Process) 4. U.S. Logistics (Mike Carlton Need to know if ISI can take this on) 5. European Logistics (Brian Carpenter/Jim Bound In Process) 6. Network Topology of 6Bone INIT (This list working with geography contacts) o Links between Asia-U.S. / Europe-U.S. o DNS Root Name Servers and Secondaries o IPv6 Routing Legs o Required Software for Legs and Tunnels 7. Determine use and applicaitons for 6bone (This list) 8. Message to IPv6 Implementors, ISPs, NAPs, etc.. (This list but above tasks should be pretty much complete). What else do we need to discuss or add to the above? thanks /jim From brian@dxcoms.cern.ch Mon Mar 25 13:13:22 1996 From: brian@dxcoms.cern.ch (Brian Carpenter CERN-CN) Date: Mon, 25 Mar 1996 14:13:22 +0100 (MET) Subject: Objective / Tasks / Next Steps ..... In-Reply-To: <9603241927.AA24685@fwasted.zk3.dec.com> from "bound@zk3.dec.com" at Mar 24, 96 02:27:41 pm Message-ID: <9603251313.AA12541@dxcoms.cern.ch> > > Name - Two different names suggested: > > Globabl IPv6 Infrastructure (GII).. Not politically good. But > this is the one I gave Jun for his Miti proposal for now. > > Information IPv6 Infrastructure (or I-Cubed).... > I suggest "GI6" as a compromise - it has the "G" for Global, the "I" for everything, and "6" for luck. Brian From bound@zk3.dec.com Mon Mar 25 13:51:00 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Mon, 25 Mar 96 08:51:00 -0500 Subject: Objective / Tasks / Next Steps ..... In-Reply-To: Your message of "Mon, 25 Mar 96 14:13:22 +0100." <9603251313.AA12541@dxcoms.cern.ch> Message-ID: <9603251351.AA28322@fwasted.zk3.dec.com> >> Name - Two different names suggested: >> >> Globabl IPv6 Infrastructure (GII).. Not politically good. But >> this is the one I gave Jun for his Miti proposal for now. >> >> Information IPv6 Infrastructure (or I-Cubed).... >> > >I suggest "GI6" as a compromise - it has the "G" for Global, >the "I" for everything, and "6" for luck. Brian, good compromise. I like it. Others ???? I really like having the "6" in it most of all. /jim From RLFink@lbl.gov Tue Mar 26 17:17:57 1996 From: RLFink@lbl.gov (Bob Fink LBNL) Date: Tue, 26 Mar 1996 09:17:57 -0800 Subject: The 6bone name issue In-Reply-To: <9603241927.AA24685@fwasted.zk3.dec.com> Message-ID: I will make one attempt to influence this naming issue, and then go with the flow as I don't want to turn this into a silly naming argument. That is not my point. My point is, that by choosing an all encompassing high profile name such as GI6, we are not only getting away from our purpose, but run the risk of alienating many who might otherwise help us. I believe that the name 6bone accurately reflects our mbone-like mission of deploying infrastructure for IPv6 prior to it being deployed fully in the global Internet infrastructure. In theory, it seems to me, our job is to enable all the appropriate tunnels, and set related policies and practices for an IPv6 backbone infrastructure. Then our role will drop away as IPv6 is implemented in production routers and normal operating policies and practices for the "global" Internet take over. So, my vote is to stay with 6bone - it's quite descriptive and has reasonable name recognition due to the mbone. Everyone would then easily recognize us as a necessary, but yet interim, piece of the the evolution of the Internet...not a threat. Now I'll shut up. Bob From bound@zk3.dec.com Tue Mar 26 18:30:51 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Tue, 26 Mar 96 13:30:51 -0500 Subject: The 6bone name issue In-Reply-To: Your message of "Tue, 26 Mar 96 09:17:57 PST." Message-ID: <9603261830.AA27763@fwasted.zk3.dec.com> Bob, You made a very valid point IMHO. Folks I don't care one way or the other. /jim From deering@parc.xerox.com Tue Mar 26 18:34:49 1996 From: deering@parc.xerox.com (Steve Deering) Date: Tue, 26 Mar 1996 10:34:49 PST Subject: The 6bone name issue In-Reply-To: RLFink's message of Tue, 26 Mar 96 09:17:57 -0800. Message-ID: <96Mar26.103504pst.75270@digit.parc.xerox.com> Even though I was the one advocating "GII", on further reflection I agree with Bob Fink. Picking a gradiose name is liable just to cause confusion and/or ill will in some quaters. Also, being superstitious, I think it would bring bad luck upon us to pick a name that assumes eventual World Domination. Better to pick a humble name like 6Bone. Also, as Bob said, the name 6Bone benefits from the analogy to the MBone, which is a succesful example of exactly what we are trying to accomplish. Steve From hinden@ipsilon.com Tue Mar 26 22:59:25 1996 From: hinden@ipsilon.com (Bob Hinden) Date: Tue, 26 Mar 1996 14:59:25 -0800 Subject: The 6bone name issue Message-ID: After more consideration, I too think that 6bone is the best name. Unless, of course, we wanted to call it something like "Internet Pro" given the industry naming trend. :-) Bob From jun@wide.ad.jp Tue Mar 26 23:34:42 1996 From: jun@wide.ad.jp (Jun Murai) Date: Wed, 27 Mar 1996 08:34:42 +0900 Subject: The 6bone name issue Message-ID: <199603262334.IAA10848@shonan.sfc.wide.ad.jp> folks, I also agree with Bob Fink. I already mentioned the points in LA on the possibility to lose some of the help. Even I am thinking that some parts of the 6bone should be physical test nets instead of logical ones with tunnels, I vote for 6bone. When we will be over with 6bone purpose, we can change the name then. jun From brian@dxcoms.cern.ch Wed Mar 27 06:55:25 1996 From: brian@dxcoms.cern.ch (Brian Carpenter CERN-CN) Date: Wed, 27 Mar 1996 07:55:25 +0100 (MET) Subject: The 6bone name issue In-Reply-To: <9603261830.AA27763@fwasted.zk3.dec.com> from "bound@zk3.dec.com" at Mar 26, 96 01:30:51 pm Message-ID: <9603270655.AA03423@dxcoms.cern.ch> Sure, let's stay with 6bone. I only came up with GI6 because Jim asked the question. Brian From bound@zk3.dec.com Wed Mar 27 15:41:27 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Wed, 27 Mar 96 10:41:27 -0500 Subject: The 6bone name issue In-Reply-To: Your message of "Tue, 26 Mar 96 14:59:25 PST." Message-ID: <9603271541.AA16624@fwasted.zk3.dec.com> I am for 6bone. One thing I have learned about temporary functions is to make sure in an organization all know they are temporary I think the name 6bone does that? Are we getting consensus???? /jim From bound@zk3.dec.com Wed Mar 27 18:50:53 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Wed, 27 Mar 96 13:50:53 -0500 Subject: Mbone Charter/Objective/????? Doc Message-ID: <9603271850.AA30638@fwasted.zk3.dec.com> I think we have our name ---> 6bone.... (not bone heads)... Not getting any volunteers to write up a charter etc... so here is what I will do .... As I recall there was an Mbone FAQ and how to use it etc... Is there something in there I can hack up and plagarize to get this done????? Anywhere on the net???? /jim From RLFink@lbl.gov Wed Mar 27 23:10:09 1996 From: RLFink@lbl.gov (Bob Fink LBNL) Date: Wed, 27 Mar 1996 15:10:09 -0800 Subject: Mbone Charter/Objective/????? Doc In-Reply-To: <9603271850.AA30638@fwasted.zk3.dec.com> Message-ID: Jim, >Not getting any volunteers to write up a charter etc... so here is what >I will do .... As I recall there was an Mbone FAQ and how to use it >etc... Is there something in there I can hack up and plagarize to get >this done????? Anywhere on the net???? I was just about to do this myself. The current MBONE pages are: http://www.best.com/~prince/techinfo/mbone.html If you can wait till tomorrow morning (before my meetings for the day start :-) I'll try hacking something together and then you can do with it as you will. Thanks, Bob From bound@zk3.dec.com Thu Mar 28 03:11:47 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Wed, 27 Mar 96 22:11:47 -0500 Subject: Mbone Charter/Objective/????? Doc In-Reply-To: Your message of "Wed, 27 Mar 96 15:10:09 PST." Message-ID: <9603280311.AA11510@fwasted.zk3.dec.com> Bob, This sounds great... I can wait a week at this end. Thanks... So all know why I push on this write-up. Its our init sales tool to get folks started. Yes we need to locate folks to do things and even folks to own some admin, but like anything else we need to sell them on it. I think in this case its just telling folks what we are trying to do. With the work in the IETF, Vendor IPv6 Noise, Address Space Crunch, Researchers chomping at the bit to use V6 with Flows (at least the ones I speak with), Implementor Bake-Offs who can provide binaries for existing equipment, Several router type vendors doing V6, and Customers actually asking do I need to worry about IPv6 I think there is enough momentum for general interest. But they will need to know how they can participate and what the technical strategy is to proceed. thanks again, /jim From bound@zk3.dec.com Sun Mar 31 04:11:58 1996 From: bound@zk3.dec.com (bound@zk3.dec.com) Date: Sat, 30 Mar 96 23:11:58 -0500 Subject: Draft of "what is the 6bone" Message-ID: <9603310411.AA15292@fwasted.zk3.dec.com> Hi, Bob Fink sent this to me and did a nice job. I think its on target. What do others think? p.s. thanks Bob... /jim ================= What is the 6BONE? The 6BONE is an outgrowth of the IETF IPng project that resulted in the creation of the IPv6 protocols that will eventually replace the current Internet network layer protocols known as IPv4. One essential part in the transition from IPv4 to IPv6 is the development of an Internet-wide IPv6 backbone infrastructure that can transport IPv6 packets. As with the existing IPv4 Internet backbone, the IPv6 backbone infrastructure will be composed of many Internet Service Providers (ISPs) and user networks linked together to provide the world-wide Internet. Until the IPv6 protocols are widely implemented and fully tested for interoperability, production ISP and user network routers will not readily place production Internet (IPv4) routers at risk. Thus a way is needed to provide Internet-wide IPv6 transport in an organized and orderly way for early testing and early use. The 6BONE is a virtual network layered on top of portions of the physical IPv4-based Internet to support routing of IPv6 packets, as that function has not yet been integrated into many production routers. The network is composed of islands that can directly support IPv6 packets, linked by virtual point-to-point links called "tunnels". The tunnel endpoints are typically workstation-class machines having operating system support for IPv6. Over time as confidence builds to allow production routers to carry native IPv6 packets, it is expected that the 6BONE would disappear by agreement of all parties. It would be replaced in a transparent way by production ISP and user network IPv6 Internet-wide transport. The 6BONE is thus focused on providing the early policy and procedures necessary to provide IPv6 transport in a reasonable fashion so testing and experience can be carried out. It would not attempt to provide new network interconnect architectures, procedures and policies that are clearly the purview of ISP and user network operators. In fact, it is the desire to include as many ISP and user network operators in the 6BONE process as possible to guarantee as seamless a transition to IPv6 as possible. =================