From ksbn@kt.co.kr Mon May 3 13:44:20 1999 From: ksbn@kt.co.kr (ksb) Date: Mon, 03 May 1999 12:44:20 +0000 Subject: cisco document Message-ID: <372D9A24.750ED256@kt.co.kr> Dear members, I'm looking for some documents or manuals for IOS(Cisco Router/IPv6 version). If you have some information, please let me know about that. Thank you. -- Kim, Sahng-Beom / Korea Telecom TEL : +82-42-870-8322 FAX : +82-42-870-8329 E-mail : ksbn@kt.co.kr -- From ksbn@kt.co.kr Mon May 3 15:49:56 1999 From: ksbn@kt.co.kr (ksb) Date: Mon, 03 May 1999 14:49:56 +0000 Subject: cisco document References: Message-ID: <372DB794.D9B30C16@kt.co.kr> Dear Sir, I could not open the web site that you wrote. I use the Nescape 4.5.1. then the browser showed me 'Application Error'. Would you like to send me another method to catch the information? Thank you. Smirk35@aol.com wrote: > IPv6 commands could be a start for you. See attached text file from this link > > http://www.cisco.com/cgi-bin/tablebuild.pl > requires a Cisco login > access code is 'galing'. -- Kim, Sahng-Beom / Korea Telecom TEL : +82-42-870-8322 FAX : +82-42-870-8329 E-mail : ksbn@kt.co.kr -- From fink@es.net Mon May 3 15:44:44 1999 From: fink@es.net (Bob Fink) Date: Mon, 03 May 1999 07:44:44 -0700 Subject: new pTLAs for ABILENE/US and FIBERTEL/AR Message-ID: <4.1.19990503073046.00a7eca0@imap2.es.net> I would like to announce the assignment of two pTLAs based on review comments and follow up analysis. --- ABILENE/US - the University Corporation for Advanced Internet Development (UCAID) high performance network backbone project to serve the Internet2 community (as does vBNS already): inet6num: 3FFE:3700::/24 netname: ABILENE --- FIBERTEL/AR - a cable network Internet Service Provider in Argentina: inet6num: 3FFE:3800::/24 netname: FIBERTEL --- Welcome to both networks to the 6bone backbone! Bob From fink@es.net Mon May 3 17:28:12 1999 From: fink@es.net (Bob Fink) Date: Mon, 03 May 1999 09:28:12 -0700 Subject: cisco document In-Reply-To: <372D9A24.750ED256@kt.co.kr> Message-ID: <4.1.19990503092445.00b00680@imap2.es.net> KSBN, At 12:44 PM 5/3/99 +0000, ksb wrote: >Dear members, > >I'm looking for some documents or manuals >for IOS(Cisco Router/IPv6 version). >If you have some information, >please let me know about that. Did you know of the Cisco routing book on v6? Internetworking Ipv6 With Cisco Routers (Computer Communications) by Silvano Gai Bob From fink@es.net Wed May 5 18:34:16 1999 From: fink@es.net (Bob Fink) Date: Wed, 05 May 1999 10:34:16 -0700 Subject: 6bone Prequalification for Sub-TLA assignment - draft 3, May 4, 1999 Message-ID: <4.1.19990504074535.00ad8600@imap2.es.net> 6bone Folk, The 6bone has finished a review of the 2nd draft of the "6bone Prequalification for Sub-TLA assignment", with mostly commentary about the issues of how tough or easy to be in handing out addresses, whether one should use the existing registries, whether the price is fair, etc. Nothing in these comments has suggested any specific changes to the draft (please correct me if I'm wrong). Below is the 3rd draft of the 6bone Prequalification for sub-TLA assignment. I have fixed the time lines and number of participating sites, and cleaned up the text to make it more like a finalized procedure. At this stage, I would like to let this draft wait until we see the finalization of the "IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT" and have to institute our 6bone prequalification process in fact (presumably as some existing pTLAs ask for 6bone fitness reports supporting their requests for sub-TLA allocations from the RIRs). In addition, the "IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT" (5th draft 16 April 1999) was released that refers to the use of the 6bone for a "4.2.2 Criteria for sub-TLA Allocations in Transitional "Bootstrap" Phase" which I have copied here: >OR d. The requesting organization must demonstrate that it has experience >with IPv6 through active use of a pseudo-TLA (pTLA) registered to it for at >least six months prior to requesting a sub-TLA. The regional IRs may require >documentation of acceptable 6Bone routing policies and practice from the >requesting organization. I have requested they change this as follows: >Maybe it should be "The requesting organization must demonstrate that it has >experience with IPv6 through active participation in the 6bone for 6 months, >with at least 3 months of that operating as a pseudo-TLA (pTLA), prior to >being allocated a sub-TLA." to be consistent with the current 6bone prequal >process we have agreed on so far. Thanks, Bob ------------------ 6bone Prequalification for Sub-TLA Assignment - 3rd draft 2, May 4, 1999 - Bob Fink The following describes how the 6bone is used as a prequalification step during the "bootstrap" phase of sub-TLA assignment by the Regional Internet Registries (RIRs): It is predicated on the following facts: F1. The 6bone community represents the world-wide IPv6 operational networking community as of early 1999, including all existing IPv6 providers and users in the world, operating under the only IPv6 address allocation and authority in place at that time, i.e., the 3FFE::/16 allocation to the 6bone under RFC 2471 ("IPv6 Testing Address Allocation") . F2. The 6bone has a well defined address structure underneath the RFC 2471 allocation for high-level (top tier) transit service providers, known as a Pseudo-TLA (pTLA), that all the known top level IPv6 transit providers are part of. See for documentation of the pTLA structure. F3. The 6bone process for becoming a Pseudo-TLA (pTLA) is well defined and accepted by the 6bone community. See Informational RFC 2546 Section 7 for current Guidelines for 6Bone pTLA sites. F4. The 6bone community as a whole is willing to provide their knowledge, experience and opinions as part of a process to help "bootstrap" the sub-TLA address allocation process for the RIRs. === 6bone Prequalification for sub-TLAs S1. The sub-TLA requestor (sTR) places their sub-TLA request with the appropriate RIR and declares that they intend to use the 6bone prequalification process (6PP). (Optional, based on RIR policy.) S2. The sTR notifies the 6bone list of their intent to use the 6PP. (This assists the 6bone in establishing the time of first contact starting the process, but does not constitute the actual start of participation in the 6bone.) S3. The sTR follows the published process for becoming a pTLA. This process is documented by [RFC 2546] Section 7. The minimum time from first joining the 6bone as an end-site network to becoming a pTLA is set as 3 months. S4. After the sTR has been approved as a pTLA, and operating as a pTLA for at least 3 months with at least 3 customers (either lower level transits or end-sites), the pTR petitions the 6bone mailing list for support of its request for a sub-TLA based on its performance as a pTLA, providing relevant proof or statement of how and/or why they believe they have met current 6bone backbone practices (currently as in RFC 2546). S5. A 6bone steering group (consisting of 3-5 persons established by 6bone participant consensus) prepares a short 6bone fitness report (6FR) based on input received from 6bone participants, and factual information of compliance with established pTLA rules extant at the time (currently RFC 2546). It then submits the 6FR to the appropriate regsitry. Note that 6bone participant means members of pTLA, pNLA or end-site organizations, not mailing list subscribers. S6. If after two months of petitioning the 6bone mailing list (S4. above) for support of its sub-TLA request with no response, the sTR may notify the appropriate RIR of 6bone non-responsiveness and ask for the RIR to proceed without a 6FR. (It is up to the RIR to decide what to do next, including the decision that the sTR's experience with the 6bone qualifies it for a sTLA allocation.) S7. After assignment of an sub-TLA to the sTR (by the RIR), the sTR may optionally renumber from the 6bone pTLA prefeix to the sub-TLA prefix, or continue use of their pTLA. If the pTLA space becomes over subscribed, the most likely networks to be asked to surrender their pTLA would be those holding production TLA/sub-TLA prefix space. === Misc. Notes: N1. Currently the RFC 2546 doc is being reworked under the 6bone hardening process now underway, which will almost certainly yield a stronger set of rules on what it takes to operate as a pTLA. N2. The current RFC 2546 doc does not specify a prequalification time as a pNLA or end-site 6bone site prior to requesting a pTLA. Thus these prequalification rules have established the minimum time of 3 months from first joining the 6bone as an end-site network to becoming a pTLA. N3. In S6. above, the total time from start of the 6PP until a protest could be made to the RIR, would be in the 8 months minimum (3 mos. while becoming a pTLA, 3 mos. while a pTLA, plus 2 mos.). N4. Some existing pTLA sites should not be allocated a sub-TLA as they are not production networks, rather they were created to "bootstrap" the 6bone or help a specific testing user community. The decision on what pTLA may or may not qualify for a sub-TLA is left to the process outlined above, and the RIR processes for allocating sub-TLAs. -end From latif.ladid@tbit.dk" I guess everybody is missing the famous emails from Jim these days! I just wanted to let you know that Jim had to undergo a light operation ( Appendix removal ) two weeks ago and would need a bit of time to recover. Let's wish Jim quick recovery as the deployment momentum needs him to pick it up again where he left it! /Latif From fink@es.net Thu May 6 00:27:44 1999 From: fink@es.net (Bob Fink) Date: Wed, 05 May 1999 16:27:44 -0700 Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?) version Message-ID: <4.1.19990505151055.00b08270@imap2.es.net> 6bone Folk, I recently proposed changing the pTLA 3FFE:/16 usage to allow future growth as the 6bone becomes used more for production. The current usage specifices an 8-bit pTLA (prefix 3FFE:xx00::/24), thus only providing for 256 pTLAs, of which 57 are currently in use. The proposed change was to leave the lower half of the space usage as is (at least for now): 3FFE:0000::/24 thru 3FFE:7F00::/24 old 8-bit pTLA space and starting at this point change to a 13-bit pTLA: 3FFE:8000::/29 thru 3FFE:FFF8::/29 new 13-bit pTLA space Also, concern had been expressed about the odd bit size of the /29 in terms of implementing the reverse DNS path, so there was the possibility of making the new space fall on an nibble bit size boundary, say a /28 or /32. Comments generally seem to favor setting the new pTLA space at /28 on the grounds that 2048 pTLAs (half of a 12-bit pTLA space) is big enough, and that it makes the reverse path easier to specify for now. There was also a comment requesting that we don't require 8-bit pTLAs to convert to the newer pTLA space. Thus I would like to change the proposal as follows. The old 8-bit pTLA space will be reduced to use of the lower half of the space: 3FFE:0000::/24 thru 3FFE:7F00::/24 old 8-bit pTLA space and starting at this point change to a 12-bit pTLA: 3FFE:8000::/28 thru 3FFE:FFF0::/28 new 12-bit pTLA space I would also like to leave existing 8-bit pTLAs in place for the indefinite future. This issue can be reconsidered in the future as usage of the new 12-bit space dictates. It should also be noted that there is no planned policy at this time for requiring pTLA holders that acquire a TLA or sub-TLA allocation to renumber out of their pTLA. This issue can also be reconsidered in the future as usage of the new 12-bit space dictates. I would like to cease the allocation of /24 8-bit pTLAs at this time, and move to the new /28 space. Hearing no convincing arguments to the contrary, I will assign the next pTLA as a /28. As there are no outstanding pTLA requests in the queue, it makes at least a two week delay in implementing this. Comments to the list please. Thanks, Bob From platini@fibertel.com.ar Thu May 6 05:37:37 1999 From: platini@fibertel.com.ar (Patricio Latini) Date: Thu, 6 May 1999 01:37:37 -0300 Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?) version Message-ID: <005f01be977a$2b3265c0$1000e818@fibertel.com.ar> I think that it is a good idea to decrease the network size for the new pTLAs, it gives the opportunity to more organizations can be pTLA. I think that it's ok. Patricio Latini Fibertel TCI2 ----- Original Message ----- From: Bob Fink To: 6BONE List <6bone@ISI.EDU> Sent: Miércoles 5 de Mayo de 1999 20:27 Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?) version >6bone Folk, > >I recently proposed changing the pTLA 3FFE:/16 usage to allow future growth as the 6bone becomes used more for production. The current usage specifices an 8-bit pTLA (prefix 3FFE:xx00::/24), thus only providing for 256 pTLAs, of which 57 are currently in use. > >The proposed change was to leave the lower half of the space usage as is (at least for now): > > 3FFE:0000::/24 thru 3FFE:7F00::/24 old 8-bit pTLA space > >and starting at this point change to a 13-bit pTLA: > > 3FFE:8000::/29 thru 3FFE:FFF8::/29 new 13-bit pTLA space > >Also, concern had been expressed about the odd bit size of the /29 in terms of implementing the reverse DNS path, so there was the possibility of making the new space fall on an nibble bit size boundary, say a /28 or /32. > > >Comments generally seem to favor setting the new pTLA space at /28 on the grounds that 2048 pTLAs (half of a 12-bit pTLA space) is big enough, and that it makes the reverse path easier to specify for now. There was also a comment requesting that we don't require 8-bit pTLAs to convert to the newer pTLA space. > > >Thus I would like to change the proposal as follows. > >The old 8-bit pTLA space will be reduced to use of the lower half of the space: > > 3FFE:0000::/24 thru 3FFE:7F00::/24 old 8-bit pTLA space > >and starting at this point change to a 12-bit pTLA: > > 3FFE:8000::/28 thru 3FFE:FFF0::/28 new 12-bit pTLA space > >I would also like to leave existing 8-bit pTLAs in place for the indefinite future. This issue can be reconsidered in the future as usage of the new 12-bit space dictates. > >It should also be noted that there is no planned policy at this time for requiring pTLA holders that acquire a TLA or sub-TLA allocation to renumber out of their pTLA. This issue can also be reconsidered in the future as usage of the new 12-bit space dictates. > > >I would like to cease the allocation of /24 8-bit pTLAs at this time, and move to the new /28 space. Hearing no convincing arguments to the contrary, I will assign the next pTLA as a /28. As there are no outstanding pTLA requests in the queue, it makes at least a two week delay in implementing this. Comments to the list please. > > >Thanks, > >Bob > > From latif.ladid@tbit.dk" Call for Papers The 5th European Union Framework Programme is organizing in conjunction with IDC ' 99 and Telework 99 the 4th International Distributed Conference - Sep 22-23 - in Madrid the program chair is Dr. Sathya Rao. Please contact Sathya directly if you wish to contribute, see also www.telscom.ch/IDC99 R, /Latif From kunihiro@zebra.org Thu May 6 19:10:01 1999 From: kunihiro@zebra.org (Kunihiro Ishiguro) Date: Fri, 07 May 1999 03:10:01 +0900 Subject: GNU Zebra -- Free Routing Software for IPv6 Message-ID: <14129.56057.489599.72159A@pj.zebra.org> Hi, this is Kunihiro Ishiguro of Digital Magic Labs, Inc. I hereby announce the development of `GNU Zebra' is going on. Zebra is the one of the official component of the GNU System and distributed under GNU General Public License. Some organizations are already connecting to 6bone using Zebra. Zebra features are listed below: o Zebra is a routing software which is made from collection of daemons such as `zebra',`ripd',`ripngd',`ospfd',`ospf6d',`bgpd'. `zebra' is kernel dependent routine daemon. Others are for routing protocol management. o Zebra has (very) CISCO like configuration file. So you may can configure it easily ;-). o Terminal interface has Emacs like command line editing, history, exelent completion and help. o `access-list', `distribute-list', `ip prefix-list', `route-map' are supported. o All configuration can be dynamically changed from terminal interface. o You can make new routing protocol daemen very easily by using Zebra protocol and library. o Off course IPv6 routing protocols supported. Currently Zebra runs on below platforms: GNU/Linux 2.0.X, GNU/Linux 2.2.X, FreeBSD 2.2.X, FreeBSD 3.X, FreeBSD 4.X, NetBSD 1.3, OpenBSD 2.4 And also IPv6 stack such as GNU/Linux 2.2, INRIA IPv6, NRI IPv6, KAME are supported. Now Zebra speaks below routing protocols: o RIP version 2 support. o RIPng support. o BGP-4 support. o BGP-4+ support. o OSPF and OSPF for IPv6 is not yet finished but partly working. Please note Zebra is still under development and there is no release in the past. You can get beta version from ftp://ftp.zebra.org/pub/zebra/ Any comments and suggestions are welcome. Please send them to the Zebra discussion list . Please send bug report to Zebra bug report list . If you think Zebra is useful I'm very happy with it. -- Kunihiro Ishiguro Zebra home page From peter@jazz-1.trumpet.com.au Fri May 7 03:15:13 1999 From: peter@jazz-1.trumpet.com.au (Peter Tattam) Date: Fri, 7 May 1999 12:15:13 +1000 (EST) Subject: Application for pTLA (fwd) Message-ID: ---------- Forwarded message ---------- Date: Fri, 7 May 1999 11:32:57 +1000 (EST) From: Peter Tattam To: Bob Fink Subject: Application for pTLA Trumpet Software International would like to apply for a pTLA on the 6bone. I believe we meet the guidelines 7 Guidelines for 6Bone pTLA sites 6Bone pTLA sites are altogether forming the backbone of the 6Bone. In order to ensure the highest level possible of availability and stability for the 6Bone environment, a few constraints are placed onto sites wishing to become or stay a 6Bone pTLA: 1. The site MUST have experience with IPv6 on the 6Bone, at least as a leaf site and preferably as a transit pNLA under an existing pTLA. We have been operating as a leaf and then as an NLA for some time. We have suballocations of the NLA to a select group of Australian users. I am also dual homed to Sprint and VBNS. I have been pleased to supply interim access to the 6bone for AARNet. 2. The site MUST have the ability and intent to provide "production- like" 6Bone backbone service to provide a robust and operationally reliable 6Bone backbone. We currently run an ISP in the state of Tasmania, Australia. We are commited to progress to provide IPv6 service whenever as soon as is practical. 3. The site MUST have a potential "user community" that would be served by becoming a pTLA, e.g., the requester is a major player in a region, country or focus of interest. We have a small ISP in our state called TrumpNet with around 4000 or so customers. We have 3 direct pops which cover the state plus a wholesale internet service from two other larger providers which allows local call access from anywhere in Australia (at a cost). Our backbone is limited in that it only goes to four physical locations. While our ISP is fairly well connected with two larger ISPs, by virtue of our location, we are not at the hub of Internet in Australia, and probably never will be. Potentially, all our customers could be using the 6bone right away with the latest tunneling software that I have been working up in cooperation with the Kame people. I would hope that we could qualify as we are a company with some prominence in developing IPv6 software. 4. Must commit to abide by the 6Bone backbone operational rules and policies as defined in the present document. We will of course abide by these rules and policies. -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From fink@es.net Fri May 7 04:03:17 1999 From: fink@es.net (Bob Fink) Date: Thu, 06 May 1999 20:03:17 -0700 Subject: Application for pTLA from Trumpet - review will close 21 May Message-ID: <4.1.19990506200040.00a5f600@imap2.es.net> Per the request from Peter Tattam, I'm opening a two week window for the review of their pTLA request. I will close this on 21 May 99. (Note this would be the first /28 pTLA assigned.) Thanks, Bob ==== >Date: Fri, 7 May 1999 12:15:13 +1000 (EST) >From: Peter Tattam >To: 6bone@ISI.EDU >Subject: Application for pTLA (fwd) >Sender: owner-6bone@ISI.EDU > >---------- Forwarded message ---------- >Date: Fri, 7 May 1999 11:32:57 +1000 (EST) >From: Peter Tattam >To: Bob Fink >Subject: Application for pTLA > >Trumpet Software International would like to apply for a pTLA on the >6bone. I believe we meet the guidelines > > >7 Guidelines for 6Bone pTLA sites > > 6Bone pTLA sites are altogether forming the backbone of the 6Bone. In order > to ensure the highest level possible of availability and stability for the > 6Bone environment, a few constraints are placed onto sites wishing to > become or stay a 6Bone pTLA: > > 1. The site MUST have experience with IPv6 on the 6Bone, at least as > a leaf site and preferably as a transit pNLA under an existing pTLA. > >We have been operating as a leaf and then as an NLA for some time. We >have suballocations of the NLA to a select group of Australian users. I >am also dual homed to Sprint and VBNS. I have been pleased to supply >interim access to the 6bone for AARNet. > > 2. The site MUST have the ability and intent to provide "production- > like" 6Bone backbone service to provide a robust and operationally > reliable 6Bone backbone. > >We currently run an ISP in the state of Tasmania, Australia. We are >commited to progress to provide IPv6 service whenever as soon as is >practical. > > > 3. The site MUST have a potential "user community" that would be > served by becoming a pTLA, e.g., the requester is a major player in a > region, country or focus of interest. > >We have a small ISP in our state called TrumpNet with around 4000 or so >customers. We have 3 direct pops which cover the state plus a wholesale >internet service from two other larger providers which allows local call >access from anywhere in Australia (at a cost). Our backbone is limited in >that it only goes to four physical locations. While our ISP is fairly well >connected with two larger ISPs, by virtue of our location, we are not at >the hub of Internet in Australia, and probably never will be. >Potentially, all our customers could be using the 6bone right away with >the latest tunneling software that I have been working up in cooperation >with the Kame people. I would hope that we could qualify as we are a >company with some prominence in developing IPv6 software. > > > > 4. Must commit to abide by the 6Bone backbone operational rules and > policies as defined in the present document. > >We will of course abide by these rules and policies. > > >-- >Peter R. Tattam peter@trumpet.com >Managing Director, Trumpet Software International Pty Ltd >Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > From fink@es.net Fri May 7 04:08:39 1999 From: fink@es.net (Bob Fink) Date: Thu, 06 May 1999 20:08:39 -0700 Subject: Application for pTLA from ICM-PL - review will close 21 May Message-ID: <4.1.19990506200405.00aa9720@imap2.es.net> Per the request from Wojtek Sylwestrzak and Rafal Maszkowski, I'm opening a two week window for the review of their pTLA request. I will close this on 21 May 99. (Note this would be the second /28 pTLA assigned.) Thanks, Bob ==== >Date: Thu, 06 May 1999 16:51:00 +0200 >From: Wojtek Sylwestrzak >To: Bob Fink >CC: Rafal Maszkowski >Subject: pTLA request > >Bob, >finally we have grown old enough to request a 6bone pTLA. >Below is a request from a friend of mine, Rafal Maszkowski, >slightly edited by me. > >--w > >I am operating 6BONE router at Interdisciplinary Centre for >Modelling, Warsaw University, Poland. Our registry name is ICM-PL. >We would like to become 6BONE backbone site. > >1. must have experience with ipv6 in the 6bone, at least as a leaf >site, and preferably as an NLA transit under a pTLA. > >My first 6BONE router was connected since April 1997, since Nov 1997 I am >maintaining a router at ICM now. Now we have three tunnels abroad to pTLAs: >CICNET, SICS and UNI-C and several to places inside Poland. >All tunnels abroad and most inside Poland are set up with BGP4+ routing. >Map of Polish part of 6BONE is available at http://www.6bone.pl/ . > >2. must have the ability and intent to provide "production-like" 6bone >backbone service to provide a robust and operationally reliable 6bone >backbone. > >We are using a separate Linux router for routing 6BONE and are going to >run native IPv6/ATM when Cisco implementation is oficially available and >more or less stable. (we cannot use the current cisco beta for we need >some functionality of ios12.0). >We have also a couple of years' experience operating >a WAN/MAN v4 and ATM networks. We are also one of the best conencted >sites in Poland, with separate ATM links to all major ISP and NRNs >(there are 2 of them) and separate PVC to Stockholm. >We have also ATM connection to Dante/TEN155. >We are peering with a number of v4 ASes. >We have adequate staff to maintain 6bone on 'production-like' level. >our networking centre is manned 24h. > >3. must have a potential "user community" that would be served by >becoming a pTLA, e.g., the requester is a major player in a region, >country or focus of interest. > >We have good connectivity with abroad and inside Poland. >Also most of ISPs would care themselves for good connectivity >with us because of our public Internet services. >In short: we are the Internet hub site of Poland. > >Our current 6BONE community is taking part in dicussions on >6bone-pl@sunsite.icm.edu.pl list. >The current pTLA application is the outcome of discussions >with the Polish 6bone community. > >4. must commit to abide by whatever the 6bone backbone operational >rules and policies are (currently there are no formal ones, but the >alain duran draft is a start in trying to define some). > >We accept and respect 6BONE rules and policies even though we do not >like all of them. > >let me know if anything requires more explanation ... > From latif.ladid@tbit.dk" After just four weeks of campaign for the IPv6 FORUM, the feedback is tremendous!!! People around the world support unconditionally IPv6 and see clearly the benefits of a dedicated forum for wider outreach and acceptance. I am personally very pleased to share with you the preliminary results: A - So far officially confirmed IPv6 FORUM '' Founding Members'' ( truly International Team ): 1 - Case Technology, UK-UAE 2 - Thomson-CSF Detexis, France 3 - Telebit, Denmark 4 - Eurocontrol, France 5 - Gigabell, Germany 6 - Hitachi, Japan 7 - Hewlett-Packard, USA 8 - DFN, Germany 9 - Canarie-Viagenie, Canada 10- NTT, Japan 11- WIDE, Japan 12- British Telecom, UK 13- Telecom Italia - CSELT, Italy B - Very interested, but understandably need time to go through internal approval procedure: 1. COMPAQ 2. NOKIA 3. IBM 4. France Telecom 5. Deutsche Telekom 6. AT&T NL 7. Netmedia, Finland 8. Acer, Taiwan 9. RADLAN, Israel 10. Mentat, US 11. UMST Forum ICT Group I might be missing some names ! C - Immediate Plan of Action - First meeting in Oslo along the IETF meeting - First Conference: GLOBAL IPv6 SUMMIT in Paris Oct 6-8. - First Press Release will go out in June 99, timed with the Datacom article on IPv6. - More exciting programs will be published in due time. Hope to win more IPv6 Friends as Founding Members! R, Latif From latif.ladid@tbit.dk" Important correction: Mentat is an Official Founding Member! /Latif From peter@jazz-1.trumpet.com.au Sat May 8 03:04:42 1999 From: peter@jazz-1.trumpet.com.au (Peter Tattam) Date: Sat, 8 May 1999 12:04:42 +1000 (EST) Subject: Application for pTLA (fwd) In-Reply-To: <19990507103539.12559.rocketmail@web601.yahoomail.com> Message-ID: On Fri, 7 May 1999, John El-Rassi wrote: > Just to be sure i have no authority in the 6bone (only as an > active implemntor and user) > > However the point made in the following argument is somewhat > weak as from what i know a "6bone backbone" to be, is a provider > of tunnels (of IPv6 over IPv4) and/or native IPv6 provider. > then not to forget that the 6bone is the test bed for ipv6 and > future p/n/TLA's. > > testing should be in progress (or soon to be within a reasonable > time frame) and not when it is practical. (as that will be a > while) Please note, I can roll out the automatic tunnel system within days if necessary so all my customers could potentially use IPv6. My stuff is tested and it works. By practical, I mean when our router manufacturer supports the full IPv6 over PPP set of protocols. IPv6-header compression is still in I-D stage last time I looked which is a serious gap in the whole IPv6 rollout to the masses. Why we just didn't opt for going with a simple extension of VJ compression for PPP over IPv6 beats me. Also, because some router software is at a beta stage, it is high risk for us to upgrade all our POPs when a significant revenue stream is at stake. In the mean time, I will be setting up a dynamic tunnel server that is tied directly into our RADIUS authentication system. I don't expect the take up to be quick as practically all of my customers don't even know what IPv6 is, let alone even want it. So practical means ASAP in my books. Tunnels will get me so far, but the added tunnel overhead may be a disincentive to customers, especially when they are volume charged. I might even implement the IPv6 compression I-D in the tunnel too if I could work out how to demultiplex the different compressed packet types. I do however have contacts in the industry that may help to speed up the IPv6 rollout within Australia. Having a working system in place for demonstration purposes will be a good step forward. > > i admire your efforts for ipv6 production. Thumbs UP :-) > > i hope i made sense. :-) > > > > >2. The site MUST have the ability and intent to > >rovide"production- > > like" 6Bone backbone service to provide a robust > >andoperationally > > reliable 6Bone backbone. > >We currently run an ISP in the state of Tasmania, Australia. > >Weare > >commited to progress to provide IPv6 service whenever as soon >asispractical. I think the "commitment to progress" is the important point. -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From latif.ladid@tbit.dk" Dear Videhi, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome SUN as one the 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif ---------- From: Videhi Mallela[SMTP:Videhi.Mallela@Eng.Sun.COM] Reply To: Videhi Mallela Sent: Saturday, May 08, 1999 01:45 To: latif.ladid@tbit.dk Subject: Re: IPv6 FORUM '' Founding Members'' Hello Latif, Sun Microsystems would like to join this Forum. However, I need to go through the internal approval process before I can send the forms. If you have any questions please let me know. Thanks, -videhi From danny@public.bjnet.edu.cn Sat May 8 12:52:19 1999 From: danny@public.bjnet.edu.cn (Chen Maoke) Date: Sat, 8 May 1999 20:52:19 +0900 (CDT) Subject: REMONSTRATE RAVEGENCE OF US AND NATO Message-ID: <199905081152.UAA07566@public.bjnet.edu.cn> Folks, The Chinese Embassy in Yugoslavia had been bombed by NATO with 3 missles from different directions! We, chinese students and fellows, are deeply shocked and hurted by this most ravegent instrusion! WE ARE SHOWING OUR STRONGEST REMONSTRATION TO US AND NATO! We believe, that all people who love the Peace WILL be against this kind of unhuman behaviors! Sorry for that this is NOT an academic message, but I cannot help showing my vehemancy! Please forward this message and/or your feelings, if you do hate this kind of behavior which VIOLATES the Peace of the World and the Dominion of an independent Nation and the Human Rights! Thanks, Students in China IPv6 Activities From sixbone@enterzone.net Sat May 8 18:21:48 1999 From: sixbone@enterzone.net (John Fraizer) Date: Sat, 08 May 1999 13:21:48 -0400 Subject: REMONSTRATE RAVEGENCE OF US AND NATO In-Reply-To: <199905081152.UAA07566@public.bjnet.edu.cn> Message-ID: <4.1.19990508124621.016cc230@pop3.enterzone.net> At 08:52 PM 5/8/99 +0900, Chen Maoke wrote: >The Chinese Embassy in Yugoslavia had been bombed by NATO with 3 missles >from different directions! Wow. You are able to determine the trajectory and origin weapons class of the attack prior to even NATO completing the BDA? You guys ARE good. >We, chinese students and fellows, are deeply shocked and hurted by this most >ravegent instrusion! Imagine how we felt about recent visits to Los Alamos. >WE ARE SHOWING OUR STRONGEST REMONSTRATION TO US AND NATO! Please do so in your favorite political forum, NOT on the ipv6 lists. It has no place here. >We believe, that all people who love the Peace WILL be against this kind of >unhuman behaviors! I believe you intended to say "inhumane" and I find it quite hard to swallow coming from a .cn address. Especially considering the track record that China has in the Human Rights and Humane Treatment categories, let alone your foreign relations. HONG KONG, Feb 26 (AFP) - China has made a "veiled threat" to share missile technology with third countries if the United States builds a missile defence shield for its Asian allies, including Taiwan, the Financial Times reported Friday. Full story available at: http://www.freerepublic.com/forum/a36d71a6306bd.htm This one is interesting as well: http://www.falklands.org/china/inter.html Hell, go talk to the Dalai Lama about inhumane treatment. >Sorry for that this is NOT an academic message, but I cannot help showing my >vehemancy! Please forward this message and/or your feelings, if you do hate >this kind of behavior which VIOLATES the Peace of the World and >the Dominion of an independent Nation and the Human Rights! Survey says, "BUZZZZZ" Thank you. We have some nice parting gifts for you. >Students in China IPv6 Activities Students full of Political horse hockey is more like it. You people go and wipe out entire classes, imprison anyone who dares to have different political or religious views and yet you have the audacity to cry foul when your embassy is ACCIDENTLY bombed? We gave you most favored nation status. You can build a new embassy with the profits from a single day of exporting to the US. Oh, that's right. You're exporting at a loss, aren't you. Well, I guess you'll have to replace it with the profits you'll make from selling nuclear and missile technology to the highest bidder. What's the big deal? We aimed for a property owned by one totalitarian government, missed, and hit a property owned by another totalitarian government. ------------ John Fraizer ------------ mailto:john.fraizer@EnterZone.Net http://www.EnterZone.Net http://www.EZ-Hosting.Net http://www.EZ-IP.Net ------------------------------------------ | __ _ | | | / / (_)__ __ ____ __ | The choice | | / /__/ / _ \/ // /\ \/ / | of a GNU | | /____/_/_//_/\_,_/ /_/\_\ | Generation | | | | ------------------------------------------ From bmanning@ISI.EDU Sat May 8 21:40:24 1999 From: bmanning@ISI.EDU (Bill Manning) Date: Sat, 8 May 1999 13:40:24 -0700 (PDT) Subject: moderation Message-ID: <199905082040.NAA26288@boreas.isi.edu> With the recent spate of non-6bone postings and replies I think it would be important to just let it pass. If it persists, I'll moderate postings. -- bill "When in doubt, Twirl..." -anon From tim.larder@virgin.net Sat May 8 21:46:08 1999 From: tim.larder@virgin.net (Tim Larder) Date: Sat, 8 May 1999 21:46:08 +0100 Subject: REMONSTRATE RAVEGENCE OF US AND NATO Message-ID: <000201be9994$18924040$4144a8c2@tsys2> John, This type of talk is absolute rubbish it doesn't solve anything and as you said has no relevance on this list so keep your thoughts to yourself please. Regards Tim -----Original Message----- From: John Fraizer To: Chen Maoke ; 6bone@ISI.EDU <6bone@ISI.EDU> Date: 08 May 1999 20:37 Subject: Re: REMONSTRATE RAVEGENCE OF US AND NATO >At 08:52 PM 5/8/99 +0900, Chen Maoke wrote: >>The Chinese Embassy in Yugoslavia had been bombed by NATO with 3 missles >>from different directions! > >Wow. You are able to determine the trajectory and origin weapons class of >the attack prior to even NATO completing the BDA? You guys ARE good. > >>We, chinese students and fellows, are deeply shocked and hurted by this most >>ravegent instrusion! > >Imagine how we felt about recent visits to Los Alamos. > >>WE ARE SHOWING OUR STRONGEST REMONSTRATION TO US AND NATO! > >Please do so in your favorite political forum, NOT on the ipv6 lists. It >has no place here. > >>We believe, that all people who love the Peace WILL be against this kind of >>unhuman behaviors! > >I believe you intended to say "inhumane" and I find it quite hard to >swallow coming from a .cn address. Especially considering the track record >that China has in the Human Rights and Humane Treatment categories, let >alone your foreign relations. > >HONG KONG, Feb 26 (AFP) - China has made a "veiled threat" to share missile >technology with third countries if the United States builds a missile >defence shield for its Asian allies, including Taiwan, the Financial Times >reported Friday. > >Full story available at: http://www.freerepublic.com/forum/a36d71a6306bd.htm > >This one is interesting as well: http://www.falklands.org/china/inter.html > >Hell, go talk to the Dalai Lama about inhumane treatment. > > > >>Sorry for that this is NOT an academic message, but I cannot help showing my >>vehemancy! Please forward this message and/or your feelings, if you do hate >>this kind of behavior which VIOLATES the Peace of the World and >>the Dominion of an independent Nation and the Human Rights! > >Survey says, "BUZZZZZ" Thank you. We have some nice parting gifts for you. > > >>Students in China IPv6 Activities > > >Students full of Political horse hockey is more like it. You people go and >wipe out entire classes, imprison anyone who dares to have different >political or religious views and yet you have the audacity to cry foul when >your embassy is ACCIDENTLY bombed? We gave you most favored nation status. > You can build a new embassy with the profits from a single day of >exporting to the US. Oh, that's right. You're exporting at a loss, aren't >you. Well, I guess you'll have to replace it with the profits you'll make >from selling nuclear and missile technology to the highest bidder. > >What's the big deal? We aimed for a property owned by one totalitarian >government, missed, and hit a property owned by another totalitarian >government. > > > >------------ >John Fraizer >------------ >mailto:john.fraizer@EnterZone.Net >http://www.EnterZone.Net >http://www.EZ-Hosting.Net >http://www.EZ-IP.Net >------------------------------------------ >| __ _ | | >| / / (_)__ __ ____ __ | The choice | >| / /__/ / _ \/ // /\ \/ / | of a GNU | >| /____/_/_//_/\_,_/ /_/\_\ | Generation | >| | | >------------------------------------------ > > From fink@es.net Sun May 9 03:57:38 1999 From: fink@es.net (Bob Fink) Date: Sat, 08 May 1999 19:57:38 -0700 Subject: 6bone list usage Message-ID: <4.1.19990508195339.00a45e70@imap2.es.net> 6bone Folk, With due respect for everyone's opinion, and the appropriate use of the 6bone list, please do not post non-6bone topics to the list. If you still see someone posting off-topic email to the list, please do not respond to it. The 6bone list maintainer and ngtrans co-chair will deal with it. Thanks, Bob From latif.ladid@tbit.dk" Dear Martin, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome Netmedia Finland Oy/Ab as one the Official 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif Latif, Attached is our IPv6 Forum Membership Application Form. If you want a signed version by FAX, please let me know. Best regards, martin ------------------------------------ Martin Sten Netmedia Finland Oy/Ab PO 98, 65101 Vasa, FINLAND Phone +358 6 3181300 FAX +358 6 3181317 Mobile +358 400 863488 e-mail martin.sten@netmedia.fi ------------------------------------ From latif.ladid@tbit.dk" Dear Christain, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome BellSouth Corporation as one the Official 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif Add us (BellSouth Corporation, USA) to the list under B. From latif.ladid@tbit.dk" Dear Peter, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome Trumpet Software International Pty Ltd, Australia, as one the Official 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif With that in mind, We will go ahead and join the forum. To send the US funds, I will need some bank details to set up a TT. Peter -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From milek@rudy.mif.pg.gda.pl Mon May 10 12:32:07 1999 From: milek@rudy.mif.pg.gda.pl (Robert Milkowski) Date: Mon, 10 May 1999 13:32:07 +0200 (CEST) Subject: mirror on ipv6 Message-ID: Witam. Po adresem ftp://3ffe:902:1a::1:2/mirrors/ jest ekperymentalny ftp site. Ewentualne uwagi prosze zglaszac na milek@task.gda.pl ---- ENG On ftp://3ffe:902:1a::1:2 there's experimental mirror site. Please test it and send any coments to milek@task.gda.pl. ------------------------------------------------------------------------------- A1240D 18MB EDO RAM + HD 2.5GB + CD +... Student of mail to: milek@rudy.mif.pg.gda.pl Technical University of Gdansk Happy owner of Amiga Milek Faculty of Applied Physics ------------------------------------------------------------------------------- From jwkckid1@ix.netcom.com Mon May 10 10:32:27 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Mon, 10 May 1999 10:32:27 +0100 Subject: mirror on ipv6 References: Message-ID: <3736A7AA.40A0126D@ix.netcom.com> Robert, It doesn't seem to be resolving.... Just to let you know. Robert Milkowski wrote: > Witam. > Po adresem ftp://3ffe:902:1a::1:2/mirrors/ > jest ekperymentalny ftp site. > Ewentualne uwagi prosze zglaszac na milek@task.gda.pl > > ---- > ENG > > On ftp://3ffe:902:1a::1:2 > > there's experimental mirror site. Please test it and send any coments to > milek@task.gda.pl. > > ------------------------------------------------------------------------------- > A1240D 18MB EDO RAM + HD 2.5GB + CD +... Student of > mail to: milek@rudy.mif.pg.gda.pl Technical University of Gdansk > Happy owner of Amiga Milek Faculty of Applied Physics > ------------------------------------------------------------------------------- Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From platini@fibertel.com.ar Mon May 10 23:48:00 1999 From: platini@fibertel.com.ar (Patricio Latini) Date: Mon, 10 May 1999 19:48:00 -0300 Subject: Fibertel pTLA WWW site Message-ID: <008e01be9b37$27da3130$1000e818@fibertel.com.ar> This is a multi-part message in MIME format. ------=_NextPart_000_008B_01BE9B1E.027C3050 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 6bone people: We recently become a pTLA, and i want to tell you = that i installes a new WWW server if you want to reach it it's address = is www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 Thanks Patricio Latini Fibertel TCI2 Argentina ------=_NextPart_000_008B_01BE9B1E.027C3050 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
6bone people:
        =    =20            We recently = become a=20 pTLA, and i want to tell you that i installes a new WWW server if you = want to=20 reach it it's address is www.ipv6.fibertel.com.ar or = 3ffe:3800:1::2
 
Thanks
 
Patricio Latini
Fibertel TCI2
Argentina
------=_NextPart_000_008B_01BE9B1E.027C3050-- From peter@jazz-1.trumpet.com.au Tue May 11 03:27:49 1999 From: peter@jazz-1.trumpet.com.au (Peter Tattam) Date: Tue, 11 May 1999 12:27:49 +1000 (EST) Subject: Fibertel pTLA WWW site In-Reply-To: <008e01be9b37$27da3130$1000e818@fibertel.com.ar> Message-ID: On Mon, 10 May 1999, Patricio Latini wrote: > 6bone people: > We recently become a pTLA, and i want to tell you > that i installes a new WWW server if you want to reach it it's address is > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > > Thanks > > Patricio Latini > Fibertel TCI2 > Argentina > I was able to sucessfully surf this web site. Well done. Peter -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From jwkckid1@ix.netcom.com Mon May 10 20:50:37 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Mon, 10 May 1999 20:50:37 +0100 Subject: Fibertel pTLA WWW site References: <008e01be9b37$27da3130$1000e818@fibertel.com.ar> Message-ID: <3737388B.BB6CD88F@ix.netcom.com> --------------3F57C82439146E38514AFF7E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio and all, I am getting a "No DNS entry found" for your URL below. Patricio Latini wrote: > 6bone people: We recently become a pTLA, and i > want to tell you that i installes a new WWW server if you want to > reach it it's address is www.ipv6.fibertel.com.ar or > 3ffe:3800:1::2 Thanks Patricio LatiniFibertel TCI2Argentina Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------------3F57C82439146E38514AFF7E Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio and all,

  I am getting a "No DNS entry found" for your URL below.

Patricio Latini wrote:

6bone people:                       We recently become a pTLA, and i want to tell you that i installes a new WWW server if you want to reach it it's address is www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 Thanks Patricio LatiniFibertel TCI2Argentina


Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
  --------------3F57C82439146E38514AFF7E-- From latif.ladid@tbit.dk" Dear Tasos, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome INTRACOM in Greece as one the Official 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif Dear Latif, Would you please send me the details on how to proceed with the registration fee of the IPv6 Forum. Best Regards Tasos ==================================================== Tasos Dagiuklas Ph.D. Development Programmes Department Advanced Communications Technologies INTRACOM S.A 19 Km Markopoulou Ave Tel: ++30 1 6690368 (direct) Paiania ++30 1 6860000 (ext 4368) 190 02 Fax: ++30 1 6860312 Athens Email:ntan@intracom.gr GREECE ==================================================== From tatsu@tatsu.dynip.com Tue May 11 14:24:05 1999 From: tatsu@tatsu.dynip.com (Greg Lee) Date: Tue, 11 May 1999 06:24:05 -0700 (PDT) Subject: static vs dynamic ipv4 address Message-ID: I am looking into connecting to the 6bone but everything I have read seems to indicate that the box I am going to establish the tunnel with needs to have a static ipv4 address. I was wondering if it can be done with a dynamic address or is is just much easier to use static addresses? //////////////////////////////////////////////// E-mail : tatsu@tatsu.dynip.com Web Page: http://tatsu.dynip.com/ PGP Key : http://tatsu.dynip.com/tatsu.asc Uptime : 2 days 12:02 Load : 2.00 2.00 2.00 //////////////////////////////////////////////// From jwkckid1@ix.netcom.com Wed May 12 09:36:48 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 09:36:48 +0100 Subject: Fibertel pTLA WWW site References: Message-ID: <37393D9E.9B93D69C@ix.netcom.com> Peter and all, I am sorry, but I was NOT able to resolve this Domain name or site. "DNS No entry found" Whiis also shows NO DNS entry for .fibertel.com.ar either. What gives? Peter Tattam wrote: > On Mon, 10 May 1999, Patricio Latini wrote: > > > 6bone people: > > We recently become a pTLA, and i want to tell you > > that i installes a new WWW server if you want to reach it it's address is > > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > > > > Thanks > > > > Patricio Latini > > Fibertel TCI2 > > Argentina > > > > I was able to sucessfully surf this web site. > > Well done. > > Peter > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From rob@consoftware.com Wed May 12 17:19:50 1999 From: rob@consoftware.com (rob) Date: Wed, 12 May 1999 12:19:50 -0400 Subject: REMONSTRATE RAVEGENCE OF US AND NATO In-Reply-To: <199905081152.UAA07566@public.bjnet.edu.cn> Message-ID: <000801be9c94$44494d20$450101c0@rob> Let's keep comments in this newsgroup to IPv6. However, I would like to comment on your comment "this kind of behavior which VIOLATES the Peace of the World". How can you possibly make a comment like that regarding the US and NATO taking action on what was a slaughtering of innocent women and children. Maybe you haven't seen the footage of how the innocent people of Kosovo were being brutally murdered by Serbian soldiers. I know it is nothing new and may seem normal to the people of China and other Communist empires to kill. Here in the United States we are disgusted by this kind of behavior and you can bet your Yen that when we see INNOCENT women and children brutally killed strictly for Communist gain we will show the opposition exactly what it feels like to be the little guy. Did you think we just decided to bomb Yugoslavia? Your country never bombed anyone did they? They never killed women and children did they? I wonder what you would do if you lived in Kosov and your family was killed by Serbian troops. Would you want the whole world just to stand around and watch? Of course not! Like I said, let's keep this kind of trash out of this newsgroup. I also apologize for this posting but these students make me sick by their uneducated view on this crisis. -----Original Message----- From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU]On Behalf Of Chen Maoke Sent: Monday, May 10, 1999 9:03 AM To: 6bone@ISI.EDU Subject: REMONSTRATE RAVEGENCE OF US AND NATO Folks, The Chinese Embassy in Yugoslavia had been bombed by NATO with 3 missles from different directions! We, chinese students and fellows, are deeply shocked and hurted by this most ravegent instrusion! WE ARE SHOWING OUR STRONGEST REMONSTRATION TO US AND NATO! We believe, that all people who love the Peace WILL be against this kind of unhuman behaviors! Sorry for that this is NOT an academic message, but I cannot help showing my vehemancy! Please forward this message and/or your feelings, if you do hate this kind of behavior which VIOLATES the Peace of the World and the Dominion of an independent Nation and the Human Rights! Thanks, Students in China IPv6 Activities From bmanning@ISI.EDU Wed May 12 20:55:56 1999 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Wed, 12 May 1999 12:55:56 -0700 (PDT) Subject: Fibertel pTLA WWW site In-Reply-To: <37393D9E.9B93D69C@ix.netcom.com> from "Jeff Williams" at May 12, 1999 09:36:48 AM Message-ID: <199905121955.AA14979@zed.isi.edu> Jeff, whiis (?) is unknown to me as a DNS manipulator. whois (perhaps what you were really after) has two strikes against it; it is not a DNS manipulator -and- is not hierarchical and so unless you were pointing to the correct server, it would not provide you with any data. DIG indicates that while fibertel.com.ar is delegated, the subzone ipv6 is not. This site has not yet registered in the ipv6 inverse tree. ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUERY SECTION: ;; ipv6.fibertel.com.ar, type = A, class = IN ;; AUTHORITY SECTION: fibertel.com.ar. 165w2d9h46m39s IN SOA dns1.cvtci.com.ar. noc.fibertel.com.ar. ( ... ) The prefix does show up in the routing system though, so it is in similar company with large parts of the IPv4 world. > > Peter and all, > > I am sorry, but I was NOT able to resolve this Domain name or > site. "DNS No entry found" Whiis also shows NO DNS entry > for .fibertel.com.ar either. What gives? > > Peter Tattam wrote: > > > On Mon, 10 May 1999, Patricio Latini wrote: > > > > > 6bone people: > > > We recently become a pTLA, and i want to tell you > > > that i installes a new WWW server if you want to reach it it's address is > > > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > > > > > > Thanks > > > > > > Patricio Latini > > > Fibertel TCI2 > > > Argentina > > > > > > > I was able to sucessfully surf this web site. > > > > Well done. > > > > Peter > > > > -- > > Peter R. Tattam peter@trumpet.com > > Managing Director, Trumpet Software International Pty Ltd > > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > Regards, > > -- > Jeffrey A. Williams > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > Information Network Eng. Group. INEG. INC. > E-Mail jwkckid1@ix.netcom.com > Contact Number: 972-447-1894 > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > -- --bill From pcurran@ticl.co.uk Wed May 12 21:53:17 1999 From: pcurran@ticl.co.uk (Peter Curran) Date: Wed, 12 May 1999 21:53:17 +0100 Subject: Fibertel pTLA WWW site In-Reply-To: <37393D9E.9B93D69C@ix.netcom.com> References: Message-ID: <199905122049.VAA23936@gate.ticl.co.uk> Just to add to the confusion.... I have no problem resolving the name or accessing the site (quite good performance actually). Must be a problem at your end - possibly DNS? Peter TICL At 09:36 12/05/99 +0100, Jeff Williams wrote: >Peter and all, > > I am sorry, but I was NOT able to resolve this Domain name or >site. "DNS No entry found" Whiis also shows NO DNS entry >for .fibertel.com.ar either. What gives? > >Peter Tattam wrote: > >> On Mon, 10 May 1999, Patricio Latini wrote: >> >> > 6bone people: >> > We recently become a pTLA, and i want to tell you >> > that i installes a new WWW server if you want to reach it it's address is >> > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 >> > >> > Thanks >> > >> > Patricio Latini >> > Fibertel TCI2 >> > Argentina >> > >> >> I was able to sucessfully surf this web site. >> >> Well done. >> >> Peter >> >> -- >> Peter R. Tattam peter@trumpet.com >> Managing Director, Trumpet Software International Pty Ltd >> Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > >Regards, > >-- >Jeffrey A. Williams >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. >Information Network Eng. Group. INEG. INC. >E-Mail jwkckid1@ix.netcom.com >Contact Number: 972-447-1894 >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > ============================================================== Peter Curran pcurran@ticl.co.uk http://www.ticl.co.uk Consultant and Author PGP key available from http://wwwkeys.uk.pgp.net:11371 or ldap://certserver.pgp.com PubKey Fingerprint = 5F94 D9A9 45EC 40A7 FB24 18BE 9C2E 74D6 E051 7F1F =============================================================== From fink@es.net Thu May 13 02:02:22 1999 From: fink@es.net (Bob Fink) Date: Wed, 12 May 1999 18:02:22 -0700 Subject: 6bone list usage In-Reply-To: <000801be9c94$44494d20$450101c0@rob> References: <199905081152.UAA07566@public.bjnet.edu.cn> Message-ID: <4.1.19990512174839.00b5c630@imap2.es.net> Rob, I have asked that off-topic email not be sent to the 6bone list. Please (everyone) don't send any more off-topic mailings. Thanks, Bob Fink Co-chair of ngtrans and 6bone project lead === >Date: Sat, 08 May 1999 19:57:38 -0700 >To: 6BONE List <6bone@ISI.EDU> >From: Bob Fink >Subject: 6bone list usage > >6bone Folk, > >With due respect for everyone's opinion, and the appropriate use of the >6bone list, please do not post non-6bone topics to the list. > >If you still see someone posting off-topic email to the list, please do not >respond to it. The 6bone list maintainer and ngtrans co-chair will deal with >it. > > >Thanks, > >Bob From platini@fibertel.com.ar Thu May 13 02:49:37 1999 From: platini@fibertel.com.ar (Patricio Latini) Date: Wed, 12 May 1999 22:49:37 -0300 Subject: New DNS server for IPv6 in Fibertel Message-ID: <006b01be9ce2$dc1cced0$1000e818@fibertel.com.ar> This is a multi-part message in MIME format. ------=_NextPart_000_0068_01BE9CC9.B65CFEE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello 6bone People: Due to the grow of this project in my = company i installed a new DNS server for the domain = ipv6.fibertel.com.ar. This server supports AAAA records and you can reach using it the = www.ipv6.fibertel.com.ar WWW server 3ffe:3800:1::2 and my ipv6 router = cisco.ipv6.fibertel.com.ar (3ffe.3800:1::1). you can also reach my ipv4 running version of the www server at = www-ipv4.ipv6.fibertel.com.ar. i would like to hear toy comments about if it is working from all the = 6bone. Thanks Patricio Latini IPv6 Project Manager Fibertel TCI2 Argentina ------=_NextPart_000_0068_01BE9CC9.B65CFEE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello 6bone People:
        =    =20            =20       Due to the grow of this project in my = company i=20 installed a new DNS server for the domain = ipv6.fibertel.com.ar.
This server supports AAAA records and you can reach = using it=20 the www.ipv6.fibertel.com.ar = WWW=20 server 3ffe:3800:1::2 and my ipv6 router cisco.ipv6.fibertel.com.ar=20 (3ffe.3800:1::1).
you can also reach my ipv4 running version of the = www server=20 at www-ipv4.ipv6.fibertel.com.ar.
 
i would like to hear toy comments about if it is = working from=20 all the 6bone.
 
Thanks
 
Patricio Latini
IPv6 Project Manager
Fibertel TCI2
Argentina
------=_NextPart_000_0068_01BE9CC9.B65CFEE0-- From jwkckid1@ix.netcom.com Wed May 12 19:04:54 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 19:04:54 +0100 Subject: Fibertel pTLA WWW site References: <199905122049.VAA23936@gate.ticl.co.uk> Message-ID: <3739C2C4.69B18FED@ix.netcom.com> Peter, Well I thought that at first too. But after checking, I can find no problem with DNS on my end here. Everything else resolves fine. I did a whois off of RIPE and they cannot resolve this Domain either. Peter Curran wrote: > Just to add to the confusion.... > > I have no problem resolving the name or accessing the site (quite good > performance actually). > > Must be a problem at your end - possibly DNS? > > Peter > TICL > > At 09:36 12/05/99 +0100, Jeff Williams wrote: > >Peter and all, > > > > I am sorry, but I was NOT able to resolve this Domain name or > >site. "DNS No entry found" Whiis also shows NO DNS entry > >for .fibertel.com.ar either. What gives? > > > >Peter Tattam wrote: > > > >> On Mon, 10 May 1999, Patricio Latini wrote: > >> > >> > 6bone people: > >> > We recently become a pTLA, and i want to tell you > >> > that i installes a new WWW server if you want to reach it it's address is > >> > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > >> > > >> > Thanks > >> > > >> > Patricio Latini > >> > Fibertel TCI2 > >> > Argentina > >> > > >> > >> I was able to sucessfully surf this web site. > >> > >> Well done. > >> > >> Peter > >> > >> -- > >> Peter R. Tattam peter@trumpet.com > >> Managing Director, Trumpet Software International Pty Ltd > >> Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > > >Regards, > > > >-- > >Jeffrey A. Williams > >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > >Information Network Eng. Group. INEG. INC. > >E-Mail jwkckid1@ix.netcom.com > >Contact Number: 972-447-1894 > >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > ============================================================== > Peter Curran pcurran@ticl.co.uk http://www.ticl.co.uk > Consultant and Author > PGP key available from http://wwwkeys.uk.pgp.net:11371 or > ldap://certserver.pgp.com > PubKey Fingerprint = 5F94 D9A9 45EC 40A7 FB24 18BE 9C2E 74D6 E051 7F1F > =============================================================== Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From platini@fibertel.com.ar Thu May 13 03:06:24 1999 From: platini@fibertel.com.ar (Patricio Latini) Date: Wed, 12 May 1999 23:06:24 -0300 Subject: Fibertel pTLA WWW site Message-ID: <008301be9ce5$33e804c0$1000e818@fibertel.com.ar> Jeff I made a nslookup based on your server and i saw that your registries are not update since many time ago i dont know why but the version of names of my organization that is cached on your organization nameserver (as1.netcom.com) is very old. Regards Patricio Latini Ipv6 Project Manager Fibertel TCI2 ----- Original Message ----- From: Jeff Williams To: Peter Curran Cc: Peter Tattam ; Patricio Latini ; <6bone@ISI.EDU> Sent: Miércoles 12 de Mayo de 1999 15:04 Subject: Re: Fibertel pTLA WWW site >Peter, > > Well I thought that at first too. But after checking, I can find no problem >with DNS on my end here. Everything else resolves fine. I did a whois >off of RIPE and they cannot resolve this Domain either. > >Peter Curran wrote: > >> Just to add to the confusion.... >> >> I have no problem resolving the name or accessing the site (quite good >> performance actually). >> >> Must be a problem at your end - possibly DNS? >> >> Peter >> TICL >> >> At 09:36 12/05/99 +0100, Jeff Williams wrote: >> >Peter and all, >> > >> > I am sorry, but I was NOT able to resolve this Domain name or >> >site. "DNS No entry found" Whiis also shows NO DNS entry >> >for .fibertel.com.ar either. What gives? >> > >> >Peter Tattam wrote: >> > >> >> On Mon, 10 May 1999, Patricio Latini wrote: >> >> >> >> > 6bone people: >> >> > We recently become a pTLA, and i want to tell you >> >> > that i installes a new WWW server if you want to reach it it's address is >> >> > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 >> >> > >> >> > Thanks >> >> > >> >> > Patricio Latini >> >> > Fibertel TCI2 >> >> > Argentina >> >> > >> >> >> >> I was able to sucessfully surf this web site. >> >> >> >> Well done. >> >> >> >> Peter >> >> >> >> -- >> >> Peter R. Tattam peter@trumpet.com >> >> Managing Director, Trumpet Software International Pty Ltd >> >> Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 >> > >> >Regards, >> > >> >-- >> >Jeffrey A. Williams >> >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. >> >Information Network Eng. Group. INEG. INC. >> >E-Mail jwkckid1@ix.netcom.com >> >Contact Number: 972-447-1894 >> >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 >> > >> ============================================================== >> Peter Curran pcurran@ticl.co.uk http://www.ticl.co.uk >> Consultant and Author >> PGP key available from http://wwwkeys.uk.pgp.net:11371 or >> ldap://certserver.pgp.com >> PubKey Fingerprint = 5F94 D9A9 45EC 40A7 FB24 18BE 9C2E 74D6 E051 7F1F >> =============================================================== > >Regards, > >-- >Jeffrey A. Williams >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. >Information Network Eng. Group. INEG. INC. >E-Mail jwkckid1@ix.netcom.com >Contact Number: 972-447-1894 >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > From Peter Tattam Thu May 13 05:27:48 1999 From: Peter Tattam (Peter Tattam) Date: Thu, 13 May 1999 14:27:48 +1000 (EST) Subject: Yet another Dynamic Tunnel Configuration Protocol Message-ID: I am publishing a draft specification of a tunnel configuration protocol that I have designed and implemented. Another implementation was quickly developed by the KAME group, to which we obtained good interoperability. HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm Comments either to me or to the lists. I will be using this protocol or further derivations of it to roll out IPv6 to our regular IPv4 internet customers. Apologies if this is sent to the wrong lists, or if I have duplicated the work of others. I did review the tunnel broker model and I believe that this protocol can only serve to complement it. Peter -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From jwkckid1@ix.netcom.com Wed May 12 22:26:52 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 22:26:52 +0100 Subject: Fibertel pTLA WWW site References: <199905121955.AA14979@zed.isi.edu> Message-ID: <3739F219.81041648@ix.netcom.com> Bill and all, bmanning@ISI.EDU wrote: > Jeff, > whiis (?) is unknown to me as a DNS manipulator. whois (perhaps > what you were really after) has two strikes against it; it is not a DNS > manipulator -and- is not hierarchical and so unless you were > pointing to the correct server, it would not provide you with any data. Sorry for the mistype on my part as it relates to "Whiis". I did mean to type "Whois". I was pointing towards fibertel.com.ar in my query. > > > DIG indicates that while fibertel.com.ar is delegated, the subzone > ipv6 is not. Well you know as well as I do that DIG will give any of the results you choose for DIG to provide. Hence it is not a very accurate tool to use for this query. I am checking into in further however to assess where the problem well be. > > > This site has not yet registered in the ipv6 inverse tree. Well than it is likely that this is the case it is understandable why it is not reachable, and therefor likely a lame delegation. > > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > ;; QUERY SECTION: > ;; ipv6.fibertel.com.ar, type = A, class = IN > > ;; AUTHORITY SECTION: > fibertel.com.ar. 165w2d9h46m39s IN SOA dns1.cvtci.com.ar. noc.fibertel.com.ar. ( Fibertel.com.ar does not resolve. Nor is it available via Whois. Hence the problem I believe here. But I am still checking. I shall update everyone on my findings as I come across them. > > ... > ) > > The prefix does show up in the routing system though, so it is in > similar company with large parts of the IPv4 world. Yes, understood Bill. But if proper tunneling is done, there should be no resolving problem. And it appears that there is. AOL cannot resolve this address either. > > > > > > Peter and all, > > > > I am sorry, but I was NOT able to resolve this Domain name or > > site. "DNS No entry found" Whiis also shows NO DNS entry > > for .fibertel.com.ar either. What gives? > > > > Peter Tattam wrote: > > > > > On Mon, 10 May 1999, Patricio Latini wrote: > > > > > > > 6bone people: > > > > We recently become a pTLA, and i want to tell you > > > > that i installes a new WWW server if you want to reach it it's address is > > > > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > > > > > > > > Thanks > > > > > > > > Patricio Latini > > > > Fibertel TCI2 > > > > Argentina > > > > > > > > > > I was able to sucessfully surf this web site. > > > > > > Well done. > > > > > > Peter > > > > > > -- > > > Peter R. Tattam peter@trumpet.com > > > Managing Director, Trumpet Software International Pty Ltd > > > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > > > Regards, > > > > -- > > Jeffrey A. Williams > > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > > Information Network Eng. Group. INEG. INC. > > E-Mail jwkckid1@ix.netcom.com > > Contact Number: 972-447-1894 > > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > > > > > > -- > --bill Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Wed May 12 22:44:42 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 22:44:42 +0100 Subject: Fibertel pTLA WWW site References: Message-ID: <3739F648.2072AEE0@ix.netcom.com> Roman and all, Roman V. Palagin wrote: > On Wed, 12 May 1999, Peter Curran wrote: > > > Just to add to the confusion.... > > > > I have no problem resolving the name or accessing the site (quite good > > performance actually). > I confirm this - may be problem at your end? > > Default Server: ns.wuppy.net.ru > Address: 195.9.65.100 This IP address from http://www.nic.ar/consultas/hosts.htm shows as not valid status. > > > > set q=aaaa > > www.ipv6.fibertel.com.ar. > Server: ns.wuppy.net.ru > Address: 195.9.65.100 Again http://www.nic.ar/consultas/hosts.htm shows this IP address as well as the com.ar as not valid. > > > Non-authoritative answer: > Name: www.ipv6.fibertel.com.ar > Address: 3ffe:3800:1::2 And again http://www.nic.ar/consultas/hosts.htm shows this IPv6 IP address as not valid either. Hence I can only thus far conclude it as not routable. > > > ------------------------------------------------------------------------- > Roman V. Palagin |RVP1-6BONE/RP40-RIPE/RVP3-RIPN| Network Administrator > ------------------------------------------------------------------------- Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Wed May 12 22:53:14 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 22:53:14 +0100 Subject: New DNS server for IPv6 in Fibertel References: <006b01be9ce2$dc1cced0$1000e818@fibertel.com.ar> Message-ID: <3739F849.73795093@ix.netcom.com> --------------0CD522955DE669316B79B115 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio and all, Patricio Latini wrote: > Hello 6bone People: Due to the grow of > this project in my company i installed a new DNS server for the domain > ipv6.fibertel.com.ar.This server supports AAAA records and you can > reach using it the www.ipv6.fibertel.com.ar WWW server 3ffe:3800:1::2 > and my ipv6 router cisco.ipv6.fibertel.com.ar (3ffe.3800:1::1).you can > also reach my ipv4 running version of the www server at > www-ipv4.ipv6.fibertel.com.ar. > > This is not possible. The com.ar is not routable thru IPv4 and is > not valid > according to NSI's whois or http://www.nic.ar/consultas/hosts.htm. > Neither > is 3ffe.3800:1::1 routable and is listed as not valid from > http://www.nic.ar/consultas/hosts.htm as well. I also get a "No DNS > entry found" > for you URL address www-ipv4.ipv6.fibertel.com.ar as well. No small > wonder however > given the previous results I just mentioned. I think you have a > tunneling problem > here. > > > > > > > i would like to hear toy comments about if it is working from all > the 6bone. Thanks Patricio LatiniIPv6 Project ManagerFibertel > TCI2Argentina Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------------0CD522955DE669316B79B115 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio and all,

Patricio Latini wrote:

Hello 6bone People:                              Due to the grow of this project in my company i installed a new DNS server for the domain ipv6.fibertel.com.ar.This server supports AAAA records and you can reach using it the www.ipv6.fibertel.com.ar WWW server 3ffe:3800:1::2 and my ipv6 router cisco.ipv6.fibertel.com.ar (3ffe.3800:1::1).you can also reach my ipv4 running version of the www server at www-ipv4.ipv6.fibertel.com.ar.

  This is not possible.  The com.ar is not routable thru IPv4 and is not valid
according to NSI's whois or http://www.nic.ar/consultas/hosts.htm.  Neither
is 3ffe.3800:1::1 routable and is listed as not valid from
http://www.nic.ar/consultas/hosts.htm as well.  I also get a "No DNS entry found"
for you URL address www-ipv4.ipv6.fibertel.com.ar as well.  No small wonder however
given the previous results I just mentioned.  I think you have a tunneling problem
here.
 
 
 
 
 
 
  i would like to hear toy comments about if it is working from all the 6bone. Thanks Patricio LatiniIPv6 Project ManagerFibertel TCI2Argentina


Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
  --------------0CD522955DE669316B79B115-- From jwkckid1@ix.netcom.com Wed May 12 22:57:52 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Wed, 12 May 1999 22:57:52 +0100 Subject: Additional Routing problem to:[Fwd: Undeliverable: Re: Fibertel pTLA WWW site] Message-ID: <3739F95E.6921C24C@ix.netcom.com> This is a multi-part message in MIME format. --------------825419BDD9A6D44D2EC77602 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bill and all, In addition I get these silly Undeliverable messages (Bounce) back from my cc list on Peter Curran, Peter Tattam, and Patricio Latini due to some routing error as well. Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------------825419BDD9A6D44D2EC77602 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: from kii.kochind.com (kii.kochind.com [198.247.195.126]) by ixmail10.ix.netcom.com (8.8.7-s-4/8.8.7/(NETCOM v1.01)) with SMTP id VAA05985; for ; Wed, 12 May 1999 21:10:37 -0700 (PDT) Received: from ictmail01.kochind.com by kii.kochind.com via smtpd (for ixmail10.ix.netcom.com [199.182.120.70]) with SMTP; 13 May 1999 04:07:31 UT Received: from 146.209.16.81 by kochind.com with ESMTP (WorldSecure Server SMTP Relay(WSS) v3.0.2); Wed, 12 May 99 23:05:07 -0500 X-Server-Uuid: 06b7a391-5f90-11d1-8cb8-00805fbb0a47 Received: by imail.kochind.com with Internet Mail Service (5.5.2448.0) id ; Wed, 12 May 1999 23:05:09 -0500 Message-ID: <87E56F4EE47ED011AAE10000F8426A1D02EF43F1@imail.kochind.com> From: "System Administrator" To: Subject: Undeliverable: Re: Fibertel pTLA WWW site Date: Wed, 12 May 1999 23:05:08 -0500 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) X-WSS-ID: 1B2490F9385089-01-01 Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BE9CF5.CA2DD738" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BE9CF5.CA2DD738 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Your message To: Peter Curran Cc: Peter Tattam; Patricio Latini; 6bone@ISI.EDU Subject: Re: Fibertel pTLA WWW site Sent: Wed, 12 May 1999 13:04:54 -0500 did not reach the following recipient(s): 04/12/99 Morehead, Tom on Wed, 12 May 1999 23:05:01 -0500 A restriction in the system prevented delivery of the message. The MTS-ID of the original message is: c=US;a= ;p=kochind;l=ICTMAIL029905130405KRGTZYQT MSEXCH:MSExchangeMTA:wichita:ICTMAIL02 ------_=_NextPart_000_01BE9CF5.CA2DD738 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Message-ID: <3739C2C4.69B18FED@ix.netcom.com> From: "Jeff Williams" To: "Peter Curran" cc: "Peter Tattam" , "Patricio Latini" , <6bone@ISI.EDU> Subject: Re: Fibertel pTLA WWW site Date: Wed, 12 May 1999 13:04:54 -0500 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) X-MS-Embedded-Report: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Peter, Well I thought that at first too. But after checking, I can find no problem with DNS on my end here. Everything else resolves fine. I did a whois off of RIPE and they cannot resolve this Domain either. Peter Curran wrote: > Just to add to the confusion.... > > I have no problem resolving the name or accessing the site (quite good > performance actually). > > Must be a problem at your end - possibly DNS? > > Peter > TICL > > At 09:36 12/05/99 +0100, Jeff Williams wrote: > >Peter and all, > > > > I am sorry, but I was NOT able to resolve this Domain name or > >site. "DNS No entry found" Whiis also shows NO DNS entry > >for .fibertel.com.ar either. What gives? > > > >Peter Tattam wrote: > > > >> On Mon, 10 May 1999, Patricio Latini wrote: > >> > >> > 6bone people: > >> > We recently become a pTLA, and i want to tell you > >> > that i installes a new WWW server if you want to reach it it's address is > >> > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > >> > > >> > Thanks > >> > > >> > Patricio Latini > >> > Fibertel TCI2 > >> > Argentina > >> > > >> > >> I was able to sucessfully surf this web site. > >> > >> Well done. > >> > >> Peter > >> > >> -- > >> Peter R. Tattam peter@trumpet.com > >> Managing Director, Trumpet Software International Pty Ltd > >> Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > > >Regards, > > > >-- > >Jeffrey A. Williams > >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > >Information Network Eng. Group. INEG. INC. > >E-Mail jwkckid1@ix.netcom.com > >Contact Number: 972-447-1894 > >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > ============================================================== > Peter Curran pcurran@ticl.co.uk http://www.ticl.co.uk > Consultant and Author > PGP key available from http://wwwkeys.uk.pgp.net:11371 or > ldap://certserver.pgp.com > PubKey Fingerprint = 5F94 D9A9 45EC 40A7 FB24 18BE 9C2E 74D6 E051 7F1F > =============================================================== Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 ------_=_NextPart_000_01BE9CF5.CA2DD738-- --------------825419BDD9A6D44D2EC77602-- From jabley@clear.co.nz Thu May 13 09:04:44 1999 From: jabley@clear.co.nz (Joe Abley) Date: Thu, 13 May 1999 20:04:44 +1200 Subject: Fibertel pTLA WWW site In-Reply-To: <3739F219.81041648@ix.netcom.com>; from Jeff Williams on Wed, May 12, 1999 at 10:26:52PM +0100 References: <199905121955.AA14979@zed.isi.edu> <3739F219.81041648@ix.netcom.com> Message-ID: <19990513200444.A90764@clear.co.nz> On Wed, May 12, 1999 at 10:26:52PM +0100, Jeff Williams wrote: > > DIG indicates that while fibertel.com.ar is delegated, the subzone > > ipv6 is not. > > Well you know as well as I do that DIG will give any of the results > you choose for DIG to provide. Hence it is not a very accurate > tool to use for this query. Yeah, Bill. The sooner you learn to use the DNS, the better. :) -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Communications Ltd http://www.clear.net.nz/ From jwkckid1@ix.netcom.com Thu May 13 02:16:23 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 02:16:23 +0100 Subject: Fibertel pTLA WWW site References: <008301be9ce5$33e804c0$1000e818@fibertel.com.ar> Message-ID: <373A27E4.68B6404@ix.netcom.com> Patricio and all, You are right. But I am not pointing to as1.netcom.com name server from my client. Not to mention that the IP address at RIPE, ARIN as well as APNIC, shows as not valid. Neither Flashnet nor AOL: can resolve this IP or your URL address either. Hence it is lame. Patricio Latini wrote: > Jeff I made a nslookup based on your server and i saw that your registries > are not update since many time ago i dont know why but the version of names > of my organization that is cached on your organization nameserver > (as1.netcom.com) is very old. > > Regards > > Patricio Latini > Ipv6 Project Manager > Fibertel TCI2 > > ----- Original Message ----- > From: Jeff Williams > To: Peter Curran > Cc: Peter Tattam ; Patricio Latini > ; <6bone@ISI.EDU> > Sent: Miércoles 12 de Mayo de 1999 15:04 > Subject: Re: Fibertel pTLA WWW site > > >Peter, > > > > Well I thought that at first too. But after checking, I can find no > problem > >with DNS on my end here. Everything else resolves fine. I did a whois > >off of RIPE and they cannot resolve this Domain either. > > > >Peter Curran wrote: > > > >> Just to add to the confusion.... > >> > >> I have no problem resolving the name or accessing the site (quite good > >> performance actually). > >> > >> Must be a problem at your end - possibly DNS? > >> > >> Peter > >> TICL > >> > >> At 09:36 12/05/99 +0100, Jeff Williams wrote: > >> >Peter and all, > >> > > >> > I am sorry, but I was NOT able to resolve this Domain name or > >> >site. "DNS No entry found" Whiis also shows NO DNS entry > >> >for .fibertel.com.ar either. What gives? > >> > > >> >Peter Tattam wrote: > >> > > >> >> On Mon, 10 May 1999, Patricio Latini wrote: > >> >> > >> >> > 6bone people: > >> >> > We recently become a pTLA, and i want to tell > you > >> >> > that i installes a new WWW server if you want to reach it it's > address is > >> >> > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 > >> >> > > >> >> > Thanks > >> >> > > >> >> > Patricio Latini > >> >> > Fibertel TCI2 > >> >> > Argentina > >> >> > > >> >> > >> >> I was able to sucessfully surf this web site. > >> >> > >> >> Well done. > >> >> > >> >> Peter > >> >> > >> >> -- > >> >> Peter R. Tattam peter@trumpet.com > >> >> Managing Director, Trumpet Software International Pty Ltd > >> >> Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > >> > > >> >Regards, > >> > > >> >-- > >> >Jeffrey A. Williams > >> >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > >> >Information Network Eng. Group. INEG. INC. > >> >E-Mail jwkckid1@ix.netcom.com > >> >Contact Number: 972-447-1894 > >> >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > >> > > >> ============================================================== > >> Peter Curran pcurran@ticl.co.uk > http://www.ticl.co.uk > >> Consultant and Author > >> PGP key available from http://wwwkeys.uk.pgp.net:11371 or > >> ldap://certserver.pgp.com > >> PubKey Fingerprint = 5F94 D9A9 45EC 40A7 FB24 18BE 9C2E 74D6 E051 7F1F > >> =============================================================== > > > >Regards, > > > >-- > >Jeffrey A. Williams > >CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > >Information Network Eng. Group. INEG. INC. > >E-Mail jwkckid1@ix.netcom.com > >Contact Number: 972-447-1894 > >Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > > Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Thu May 13 02:23:42 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 02:23:42 +0100 Subject: Yet another Dynamic Tunnel Configuration Protocol References: Message-ID: <373A299D.4878B084@ix.netcom.com> Peter and all, The URL you are listing does not resolve either. "No DNS Entry". Do you possibly have a URL with this information on your Trumpet.com domain? Peter Tattam wrote: > I am publishing a draft specification of a tunnel configuration protocol that I > have designed and implemented. Another implementation was quickly > developed by the KAME group, to which we obtained good interoperability. > > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm > > Comments either to me or to the lists. > > I will be using this protocol or further derivations of it to roll out IPv6 to > our regular IPv4 internet customers. > > Apologies if this is sent to the wrong lists, or if I have duplicated the work > of others. I did review the tunnel broker model and I believe that this > protocol can only serve to complement it. > > Peter > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Thu May 13 02:29:19 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 02:29:19 +0100 Subject: Fibertel pTLA WWW site References: <199905121955.AA14979@zed.isi.edu> <3739F219.81041648@ix.netcom.com> <19990513200444.A90764@clear.co.nz> Message-ID: <373A2AED.20955885@ix.netcom.com> Joe and all, What was the purpose of this smart remark? Hummmm? I was pointing out to Bill in a serious manner, that DIG is fine for some things but is not necessarily authoritative, which I know that he knows very well. So I am having a problem with you making such a smart ass remark.... :( Are you Joe, possibly suffering form an attitude problem perhaps? Joe Abley wrote: > On Wed, May 12, 1999 at 10:26:52PM +0100, Jeff Williams wrote: > > > DIG indicates that while fibertel.com.ar is delegated, the subzone > > > ipv6 is not. > > > > Well you know as well as I do that DIG will give any of the results > > you choose for DIG to provide. Hence it is not a very accurate > > tool to use for this query. > > Yeah, Bill. The sooner you learn to use the DNS, the better. :) > > -- > Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 > Network Architect, CLEAR Communications Ltd http://www.clear.net.nz/ Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From antonio.herrera-alcantara@bt.com Thu May 13 11:54:17 1999 From: antonio.herrera-alcantara@bt.com (antonio.herrera-alcantara@bt.com) Date: Thu, 13 May 1999 11:54:17 +0100 Subject: NAT-PT announcement. Message-ID: <97E01B170FC1D211B8EB0000F8FE9E07711551@mbtlipnt03.btlabs.bt.co.uk> Dear 6BONE community, I'm forwarding this announcement on behalf of the NAT-PT development team because I think the previous announcement did not get through this important list, sorry if you are receiving this twice. NAT-PT is a v4/v6 translator developed in BT Labs which allows transparent bidirectional communication between IPv4 and IPv6 networks, the translator includes a DNS ALG which ensures true transparency and makes the major difference between this and other translators. Please see below for more detailed information on NAT-PT. We have tested the NAT-PT and we are very proud of how it works, we firmly believe and hope that the NAT-PT development will help boost IPv6 deployment and proves useful for the transition to IPv6. For this purpose we make available the software including the source code. We encourage you to download NAT-PT (see below) and try it, we welcome any feedback, comments, bug report, etc, and you can obtain support mailing the NAT-PT development team at: natpt@labyrinth.bt.co.uk Thanks, Antonio Herrera BT Laboratories Martlesham Heath, UK. ************** NAT-PT *************** BT have developed an implementation of NAT-PT (Network Address Translation - Protocol Translation) which is based on the IETF draft specification http://search.ietf.org/internet-drafts/draft-ietf-ngtrans-natpt-05.txt. NAT-PT provides a seamless bi-directional translation capability between IPv4 and IPv6 networks. NAT-PT is located on the boundary router between IPv4 and IPv6 and translates all packets crossing the boundary and where necessary assigns a global IPv4 address to represent an IPv6 host. DNS is a vital component of NAT-PT as it allows hosts to communicate across the boundary by knowledge of DNS addresses and negates the need for end hosts to be concerned about the destination host network type of IP address. The implementation developed in BT resides on a FreeBSD host using the Kame IPv6 stack for connection to the IPv6 network. We are making the implementation available to promote the draft specification, which was jointly written by BT and Lucent, and also the concept of NAT-PT as an IPv4/IPv6 translation mechanism. We have two sites from which the NAT-PT implementation may be downloaded from. http://nat-pt.ipv6.bt.net is a 6bone web site. Alternatively http://www.labs.bt.com/technical/nat_pt/ provides the same access via the Internet. We do ask that you identify yourself prior to downloading the code so that we can gauge the level of interest and for the notification of code updates. If you would like to send us comments or report bugs please reply to this email address natpt@labyrinth.bt.co.uk From bmanning@ISI.EDU Thu May 13 12:25:32 1999 From: bmanning@ISI.EDU (Bill Manning) Date: Thu, 13 May 1999 04:25:32 -0700 (PDT) Subject: Yet another Dynamic Tunnel Configuration Protocol In-Reply-To: <373A299D.4878B084@ix.netcom.com> from "Jeff Williams" at May 13, 1999 02:23:42 AM Message-ID: <199905131125.EAA05277@boreas.isi.edu> Odd, it resolves just fine. ; <<>> DiG 8.1 <<>> jazz-1.trumpet.com.au ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 8, ADDITIONAL: 7 ;; QUERY SECTION: ;; jazz-1.trumpet.com.au, type = A, class = IN ;; ANSWER SECTION: jazz-1.trumpet.com.au. 1D IN A 203.5.119.62 > > Peter and all, > > The URL you are listing does not resolve either. "No DNS Entry". > Do you possibly have a URL with this information on your > Trumpet.com domain? > > Peter Tattam wrote: > > > I am publishing a draft specification of a tunnel configuration protocol that I > > have designed and implemented. Another implementation was quickly > > developed by the KAME group, to which we obtained good interoperability. > > > > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm > > > > Comments either to me or to the lists. > > > > I will be using this protocol or further derivations of it to roll out IPv6 to > > our regular IPv4 internet customers. > > > > Apologies if this is sent to the wrong lists, or if I have duplicated the work > > of others. I did review the tunnel broker model and I believe that this > > protocol can only serve to complement it. > > > > Peter > > > > -- > > Peter R. Tattam peter@trumpet.com > > Managing Director, Trumpet Software International Pty Ltd > > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > Regards, > > -- > Jeffrey A. Williams > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > Information Network Eng. Group. INEG. INC. > E-Mail jwkckid1@ix.netcom.com > Contact Number: 972-447-1894 > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > > -- --bill From map@stacken.kth.se Thu May 13 13:52:08 1999 From: map@stacken.kth.se (Magnus Ahltorp) Date: 13 May 1999 14:52:08 +0200 Subject: (IPng 7522) Yet another Dynamic Tunnel Configuration Protocol In-Reply-To: Peter Tattam's message of "Thu, 13 May 1999 14:27:48 +1000 (EST)" References: Message-ID: > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm > > Comments either to me or to the lists. "Once a tunnel is established, the client may use normal tunnel protocols for IPv6 tunnelling using the endpoints supplied by the server, typically over IP port 41." I would suggest using the term "IP protocol 41" instead of "IP port 41". "It is important to note that in this protocol, the is a valid command and should result in a -ERR response." If it is a valid command, why should the command result in a -ERR response? Why is the a valid command? "Unrecognized commands should invoke a -ERR response." "Any other commands are totally ignored by the tunnel server, and no response must be sent." It is just me, or is this inconsistent? The latter tells me that unrecognized commands must result in no response, but the former tells me that it should result in a -ERR response. The quit command response is actually specified to be "+OK tunnel server quitting" which I think should be "+OK " which is consistent with the example in the appendix. /Magnus From platini@fibertel.com.ar Thu May 13 17:56:22 1999 From: platini@fibertel.com.ar (Patricio Latini) Date: Thu, 13 May 1999 13:56:22 -0300 Subject: No subject Message-ID: <007c01be9d61$87eedf40$1000e818@fibertel.com.ar> This is a multi-part message in MIME format. ------=_NextPart_000_0079_01BE9D48.6265FDD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was seeing the evolution of the message that i posted some days ago. = It wasn't my idea to generate something like that but i will give all = the data to finish this mydomain is fibertel.com.ar due to the hierarchial structure od DNS my domain is registered in NIC = Argentina (www.nic.ar) here i cut and parte the registry fibertel.com.ar -------------------------------------------------------------------------= ------- Entidad Registrante: Cablevision S.A. Direcci=F3n: BONPLAND 1773 Ciudad: Capital Federal C=F3digo Postal: 1414 Pa=EDs: Argentina Tel=E9fono: 778-6060 Fax: NO INGRESADO Actividad Principal: Television Persona Responsable: Soporte Tecnico Fibertel Direcci=F3n: Bonpland 1773 Ciudad: Buenos Aires C=F3digo Postal: 1414 Pa=EDs: Argentina Tel=E9fono: 778-6060 Horarios Contacto: 09:00 - 18:00 Direcci=F3n de correo electr=F3nico: noc@fibertel.com.ar Fecha de registraci=F3n: 21/07/1997 Entidad Administradora: Cablevision S.A. Direcci=F3n: BONPLAND 1773 Ciudad: Capital Federal C=F3digo Postal: 1414 Pa=EDs: Argentina Tel=E9fono: 778-6060 Fax: NO INGRESADO Actividad Principal: Television Contacto T=E9cnico: R. E. ESCOBAR Direcci=F3n: BONPLAND 1773 Ciudad: CAPITAL FEDERAL C=F3digo Postal: 1414 Pa=EDs: Argentina Tel=E9fono: 778-6060 Horario Contacto: NO INGRESADO Fax: NO INGRESADO Direcci=F3n de Correo Electr=F3nico: jouvina@lightech.com.ar=20 Servidores de Nombre de Dominio Servidor de Nombres Primario:=20 Nombre: dns1.cvtci.com.ar Direcci=F3n ip: 24.232.0.17 Servidor de Nombres Secundario:=20 Nombre: dns2.cvtci.com.ar Direcci=F3n ip: 24.232.0.18 again Due to hierarchial structure of DNS i havent to registry a = subdomain delegation to anyone.=20 so i created the ipv6.fibertel.com.ar and i delegated in my primary dns = to other DNS Server (24.232.1.4) dns.ipv6.fibertel.com.ar i have also done nslookups from many servers in the internet like aol, = spint and more and all can resolve my domain. but i see that netcom regestries are not updated since one month. = (serial number) Another point is that i'm peering throught 4 tunnels to the other = backbone sites and running bgp 4+ and i think that ipv6 my pool is = reacheable from all the 6bone I ask to all the 6bone members if they cant test the connection to me. = and tell me if i am reacheable from their location Thanks for ALL Patricio Latini IPv6 Project Manager Fibertel TCI2 Argentina ------=_NextPart_000_0079_01BE9D48.6265FDD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I was seeing the evolution of the message that i = posted some=20 days ago. It wasn't my idea to generate something like that but i will = give all=20 the data to finish this
 
mydomain is fibertel.com.ar
due to the hierarchial structure od DNS my domain is = registered in NIC Argentina (www.nic.ar) here i=20 cut and parte the registry
 
fibertel.com.ar
 
----------------------------------------------------------------= ----------------
 
Entidad Registrante: Cablevision = S.A.
Direcci=F3n: BONPLAND=20 1773
Ciudad: Capital Federal
C=F3digo Postal: 1414
Pa=EDs:=20 Argentina
Tel=E9fono: 778-6060
Fax: NO INGRESADO
Actividad = Principal:=20 Television
 
Persona Responsable: Soporte Tecnico = Fibertel
Direcci=F3n:=20 Bonpland 1773
Ciudad: Buenos Aires
C=F3digo Postal: = 1414
Pa=EDs:=20 Argentina
Tel=E9fono: 778-6060
Horarios Contacto: 09:00 - = 18:00
Direcci=F3n=20 de correo electr=F3nico: noc@fibertel.com.ar
 
Fecha de registraci=F3n: 21/07/1997
Entidad = Administradora:=20 Cablevision S.A.
Direcci=F3n: BONPLAND 1773
Ciudad: Capital=20 Federal
C=F3digo Postal: 1414
Pa=EDs: Argentina
Tel=E9fono: = 778-6060
Fax:=20 NO INGRESADO
Actividad Principal: Television
 

Contacto T=E9cnico: R. E. = ESCOBAR
Direcci=F3n: BONPLAND=20 1773
Ciudad: CAPITAL FEDERAL
C=F3digo Postal: 1414
Pa=EDs:=20 Argentina
Tel=E9fono: 778-6060
Horario Contacto: NO = INGRESADO
Fax: NO=20 INGRESADO
Direcci=F3n de Correo Electr=F3nico: jouvina@lightech.com.ar =
Servidores=20 de Nombre de Dominio
Servidor de Nombres Primario:
Nombre:=20 dns1.cvtci.com.ar
Direcci=F3n ip: 24.232.0.17
 
Servidor de Nombres Secundario:
Nombre:=20 dns2.cvtci.com.ar
Direcci=F3n ip: 24.232.0.18
 
again Due to hierarchial structure of DNS i havent = to registry=20 a subdomain delegation to anyone.
so i created the ipv6.fibertel.com.ar and=20 i delegated in my primary dns to other DNS Server (24.232.1.4)=20 dns.ipv6.fibertel.com.ar
 
i have also done nslookups from many servers in the = internet=20 like aol, spint and more and all can resolve my domain.
 
but i see that netcom regestries are not updated = since one=20 month. (serial number)
 
Another point is that i'm peering throught 4 tunnels = to the=20 other backbone sites and running bgp 4+ and i think that ipv6 my pool is = reacheable from all the 6bone
 
I ask to all the 6bone members if they cant test the = connection to me. and tell me if i am reacheable from their=20 location
 
Thanks for ALL
 
Patricio Latini
IPv6 Project Manager
Fibertel TCI2
Argentina
------=_NextPart_000_0079_01BE9D48.6265FDD0-- From jwkckid1@ix.netcom.com Thu May 13 14:36:36 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 14:36:36 +0100 Subject: Fibertel pTLA WWW site References: <002901be9bd0$3aced950$1000e818@fibertel.com.ar> Message-ID: <373AD561.7E8B3AC3@ix.netcom.com> --------------350C83855F3E577615A1943B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio, I will try in a bit, ok? >;) I have a lot of mail to sift through at the moment. Sorry about that. BTW, I hope this reaches you, as you E-mail address is also bouncing, so I am sending this to the list as well, just in case. Patricio Latini wrote: > hello jeff: can you make a nslookup for me?or can you > try now? Thanks Patricio LatiniFibertel TCI2 > > ----- Original Message ----- > From: Jeff Williams > To: Patricio LatiniCc: 6bone@ISI.EDUSent: Lunes 10 de Mayo > de 1999 16:50Subject: Re: Fibertel pTLA WWW site > Patricio and all, > > I am getting a "No DNS entry found" for your URL below. > > Patricio Latini wrote: > > > 6bone people: We recently become a > > pTLA, and i want to tell you that i installes a new WWW > > server if you want to reach it it's address is > > www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 Thanks Patricio > > LatiniFibertel TCI2Argentina > > > Regards, > -- > Jeffrey A. Williams > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development > Eng. > Information Network Eng. Group. INEG. INC. > E-Mail jwkckid1@ix.netcom.com > Contact Number: 972-447-1894 > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 > > Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------------350C83855F3E577615A1943B Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Patricio,

  I will try in a bit, ok?  >;)  I have a lot of mail to sift through at the moment.
Sorry about that.  BTW, I hope this reaches you, as you E-mail address
is also bouncing, so I am sending this to the list as well, just in case.

Patricio Latini wrote:

 hello jeff:              can you make a nslookup for me?or can you try now? Thanks Patricio LatiniFibertel TCI2
----- Original Message ----- To: Patricio LatiniCc: 6bone@ISI.EDUSent: Lunes 10 de Mayo de 1999 16:50Subject: Re: Fibertel pTLA WWW site
 Patricio and all,

  I am getting a "No DNS entry found" for your URL below.

Patricio Latini wrote:

6bone people:                       We recently become a pTLA, and i want to tell you that i installes a new WWW server if you want to reach it it's address is www.ipv6.fibertel.com.ar or 3ffe:3800:1::2 Thanks Patricio LatiniFibertel TCI2Argentina


Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
 


Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
  --------------350C83855F3E577615A1943B-- From jwkckid1@ix.netcom.com Thu May 13 14:39:55 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 14:39:55 +0100 Subject: Additional Routing problem to:[Fwd: Undeliverable: Re: Fibertel pTLA WWW site] References: Message-ID: <373AD628.94F17013@ix.netcom.com> Peter, Are you saying that ISI's DNS server is lame? Hope not! That is where I am pointing. BTW I am cc'ing this to the IPv6 list as your E-Mail bounces fairly often... Peter Tattam wrote: > I believe you must have a bad DNS server causing you much hassle. > > Peter > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Thu May 13 14:49:43 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 14:49:43 +0100 Subject: Additional Routing problem to:[Fwd: Undeliverable: Re: Fibertel pTLA WWW site] References: Message-ID: <373AD874.66375780@ix.netcom.com> Peter, As I have pointed out on two separate occasions on different threads on this subject, I am not pointing to those DNS servers presently. I am pointing to ISI/IANA's DNS servers. However Netcom's Name servers point there as well, as you correctly indicate here. >;) I also already posted where I got my results from my DNS queries on the another thread as well. The are as follows: Your DN and IP address provided by do not resolve or is invalid from the Following: ARIN APPNIC RIPE Two other things also BTW. I am cc'ing this to the list as your E-mail address often bounces, as this thread indicates, and I do NOT partake in smoking or drinking of alcoholic beverages of any kind, just to answer your last question definitively! >;) Peter Tattam wrote: > I did a dig of jazz-1.trumpet.com.au from your name servers at netcom.com > > as1.netcom.com > as2.netcom.com > as3.netcom.com > as4.netcom.com > > and they are all returning the correct results. I don't know what you are > using that is returning host not found. Please explain? Ar you using DNS > servers that are restricted to IPv6 domain or what? (Or are you smoking > something odd :) > > Peter > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From peter@jazz-1.trumpet.com.au Fri May 14 00:12:19 1999 From: peter@jazz-1.trumpet.com.au (Peter Tattam) Date: Fri, 14 May 1999 09:12:19 +1000 (EST) Subject: Yet another Dynamic Tunnel Configuration Protocol In-Reply-To: Message-ID: A fresh draft with corrections is now available. HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-14-may-1999.htm On Thu, 13 May 1999, Peter Tattam wrote: > I am publishing a draft specification of a tunnel configuration protocol that I > have designed and implemented. Another implementation was quickly > developed by the KAME group, to which we obtained good interoperability. > > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm > > Comments either to me or to the lists. > > I will be using this protocol or further derivations of it to roll out IPv6 to > our regular IPv4 internet customers. > > Apologies if this is sent to the wrong lists, or if I have duplicated the work > of others. I did review the tunnel broker model and I believe that this > protocol can only serve to complement it. > > Peter > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > -- Peter R. Tattam peter@trumpet.com Managing Director, Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 From jtn@eboai.org Fri May 14 01:17:25 1999 From: jtn@eboai.org (Jason T. Nelson) Date: Thu, 13 May 1999 20:17:25 -0400 Subject: sigh, re Jeff Williams Message-ID: <19990513201725.A26164@hindenburg.eboai.org> Jeff Williams is a known loonie and possible troll on the inet-access list (thank goodness he seems to have either stopped tormenting us or the list manager finally booted him off). I'm sorry to have to introduce this badly off-topic posting, but he's starting to drag the list down with non-operational issues and I felt everyone here should know. -- Jason T. Nelson BOFH Extraordiaire http://www.eboai.org/~jtn/ disclaimer: My opinions are my own. Don't bother my employer about them. From jwkckid1@ix.netcom.com Thu May 13 22:11:11 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 22:11:11 +0100 Subject: Yet another Dynamic Tunnel Configuration Protocol References: Message-ID: <373B3FED.5527630C@ix.netcom.com> Peter and all, maybe this is why your listed URL is showing partly lame here Peter. http://www.aunic.net/cgi-bin/whois?trumpet.com.au shows No match for "TRUMPET.COM.AU" Also: however, http://www.aunic.net/cgi-bin/whois.aunic?trumpet.com.au shows the following for trumpet.com.au : domain: trumpet.com.au descr: Trumpet Software International descr: GPO Box 1649 descr: Hobart descr: TAS 7001 admin-c: PT1-AU tech-c: SDB200-AU zone-c: PT1-AU remarks: Created 19950731 changed: register@aunic.net 19970120 source: AUNIC person: Peter Tattam address: GPO Box 1649 address: Hobart address: TASMANIA 7001 phone: +61 02 450220 fax-no: +61 02 450210 e-mail: peter@trumpet.com.au nic-hdl: PT1-AU remarks: (Organisation) Trumpet Software International remarks: Created 19960409 changed: register@aunic.net 19981105 source: AUNIC person: Simon David de Bomford address: 24 Cambridge Road address: Bellerive address: TAS 7018 phone: +61 3 6245 0220 fax-no: +61 3 6245 0210 e-mail: simon@trumpet.com.au nic-hdl: SDB200-AU remarks: (Organisation) Trumpet Software International remarks: (position) Network Manager remarks: Created 19961029 changed: register@aunic.net 19961029 source: AUNIC Peter Tattam wrote: > A fresh draft with corrections is now available. > > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-14-may-1999.htm > > On Thu, 13 May 1999, Peter Tattam wrote: > > > I am publishing a draft specification of a tunnel configuration protocol that I > > have designed and implemented. Another implementation was quickly > > developed by the KAME group, to which we obtained good interoperability. > > > > HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm > > > > Comments either to me or to the lists. > > > > I will be using this protocol or further derivations of it to roll out IPv6 to > > our regular IPv4 internet customers. > > > > Apologies if this is sent to the wrong lists, or if I have duplicated the work > > of others. I did review the tunnel broker model and I believe that this > > protocol can only serve to complement it. > > > > Peter > > > > -- > > Peter R. Tattam peter@trumpet.com > > Managing Director, Trumpet Software International Pty Ltd > > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 > > > > > > -- > Peter R. Tattam peter@trumpet.com > Managing Director, Trumpet Software International Pty Ltd > Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Thu May 13 22:19:23 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Thu, 13 May 1999 22:19:23 +0100 Subject: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> Message-ID: <373B41D9.C0174B50@ix.netcom.com> Jason and all, Jason, you have no idea what you are talking about . List manager, is this sort of personal unprovoked attack allowed on this list? Jason T. Nelson wrote: > Jeff Williams is a known loonie and possible troll on the inet-access list > (thank goodness he seems to have either stopped tormenting us or the list > manager finally booted him off). > > I'm sorry to have to introduce this badly off-topic posting, but he's > starting to drag the list down with non-operational issues and I felt > everyone here should know. > > -- > Jason T. Nelson > BOFH Extraordiaire > http://www.eboai.org/~jtn/ > disclaimer: My opinions are my own. Don't bother my employer about them. Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From peterdd@gto.net.om Fri May 14 07:41:05 1999 From: peterdd@gto.net.om (Peter Dawson) Date: Fri, 14 May 1999 10:41:05 +0400 Subject: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> <373B41D9.C0174B50@ix.netcom.com> Message-ID: <373BC580.85AB6A3C@gto.net.om> Jeff, I think that your ISP provider (netcom.com) is having some problems... just followup on with your upstream provider to see , why you can't resolve the issues and the resons on your email bouncing before posting to the list, please. Thank you /pete ------------------------- Netcom E-mail Outage As many of you know, Netcom experienced an e-mail file server failure. Below is an explanation and response from MindSpring CEO, Charles Brewer. Update - Thursday, May 13. We are still working on fixing the problem. Thank you for your continued patience. ------------------ Jeff Williams wrote: > Jason and all, > > Jason, you have no idea what you are talking about . List > manager, > is this sort of personal unprovoked attack allowed on this > list? > > Jason T. Nelson wrote: > > > Jeff Williams is a known loonie and possible troll on the > inet-access list > > (thank goodness he seems to have either stopped tormenting us > or the list > > manager finally booted him off). > > > > I'm sorry to have to introduce this badly off-topic posting, > but he's > > starting to drag the list down with non-operational issues > and I felt > > everyone here should know. > > > > -- > > Jason T. Nelson > > BOFH Extraordiaire > > http://www.eboai.org/~jtn/ > > disclaimer: My opinions are my own. Don't bother my employer > about them. > > Regards, > > -- > Jeffrey A. Williams > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > Information Network Eng. Group. INEG. INC. > E-Mail jwkckid1@ix.netcom.com > Contact Number: 972-447-1894 > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From jwkckid1@ix.netcom.com Fri May 14 00:46:11 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Fri, 14 May 1999 00:46:11 +0100 Subject: Sigh, Pete Dawson was:Re: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> <373B41D9.C0174B50@ix.netcom.com> <373BC580.85AB6A3C@gto.net.om> Message-ID: <373B6441.BC63F5B5@ix.netcom.com> Pete and all, This will make the 4th time I have spelled this out. I am NOT pointing to NETCOM's DNS server with this ID. Second, the URL's that I have pointed out do also not resolve from AOL, and Flashnet either. Third, http://www.aunic.net/cgi-bin/whois?trumpet.com.au shows that No match for "TRUMPET.COM.AU" which I am suggesting that Peters URL: HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-14-may-1999.htm is likely lame, or has a routing (Tunneling?) problem. Forth, Neither my AOL nor my Flashnet can resolve http://www-ipv4.ipv6.fibertel.com.ar , or ipv6.fibertel.com.ar or dns.ipv6.fibertel.com.ar of Patricio Latini and yesterday, (www.nic.ar) whois did not show an entry for fibertel.com.ar, however it did today. In the future Peter, it might be to your advantage before posting to clearly read the previous threads completely and understand them or ask me for clarification on them before creating such a denigrating thread that is both inaccurate and insulting unnecessarily. BTW, I called Netcom/Mindspring operations center and they are not aware of any E-Mail outage and reported none either. I will get in touch with Mr. Brewer in the mourning by phone as I am a large stock holder and find out about your PARTIAL message you quote below. Interesting you did not include his E-mail address in your qoute of him.... Thank you for your cooperation in advance. >;) Peter Dawson wrote: > Jeff, > > I think that your ISP provider (netcom.com) is having some > problems... just followup on with your upstream > provider to see , why you can't resolve the issues > and the resons on your email bouncing before posting > to the list, please. > > Thank you > > /pete > ------------------------- > Netcom E-mail Outage > > As many of you know, Netcom experienced an e-mail file > server failure. > Below is an explanation and response from MindSpring CEO, > Charles > Brewer. > > Update - Thursday, May 13. We are still working on fixing > the problem. > Thank you for your continued patience. > > ------------------ > Jeff Williams wrote: > > > Jason and all, > > > > Jason, you have no idea what you are talking about . List > > manager, > > is this sort of personal unprovoked attack allowed on this > > list? > > > > Jason T. Nelson wrote: > > > > > Jeff Williams is a known loonie and possible troll on the > > inet-access list > > > (thank goodness he seems to have either stopped tormenting us > > or the list > > > manager finally booted him off). > > > > > > I'm sorry to have to introduce this badly off-topic posting, > > but he's > > > starting to drag the list down with non-operational issues > > and I felt > > > everyone here should know. > > > > > > -- > > > Jason T. Nelson > > > BOFH Extraordiaire > > > http://www.eboai.org/~jtn/ > > > disclaimer: My opinions are my own. Don't bother my employer > > about them. > > > > Regards, > > > > -- > > Jeffrey A. Williams > > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > > Information Network Eng. Group. INEG. INC. > > E-Mail jwkckid1@ix.netcom.com > > Contact Number: 972-447-1894 > > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From Jeff Williams Fri May 14 10:32:16 1999 From: Jeff Williams (Peter Dawson) Date: Fri, 14 May 1999 13:32:16 +0400 Subject: Sigh, Pete Dawson was:Re: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> <373B41D9.C0174B50@ix.netcom.com> <373BC580.85AB6A3C@gto.net.om> <373B6441.BC63F5B5@ix.netcom.com> Message-ID: <373BEDA0.35AA7011@gto.net.om> FYI please see http:/www.netcom.com as this is off topic of 6bone activites, I'll refrain from further postings. Thank you /pete Jeff Williams wrote: BTW, I called > Netcom/Mindspring operations center and they are not aware of > any > E-Mail outage and reported none either. I will get in touch > with > Mr. Brewer in the mourning by phone as I am a large stock > holder > and find out about your PARTIAL message you quote below. > Interesting > you did not include his E-mail address in your qoute of him.... From jwkckid1@ix.netcom.com Fri May 14 02:59:43 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Fri, 14 May 1999 02:59:43 +0100 Subject: Sigh, Pete Dawson was:Re: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> <373B41D9.C0174B50@ix.netcom.com> <373BC580.85AB6A3C@gto.net.om> <373B6441.BC63F5B5@ix.netcom.com> <373BEDA0.35AA7011@gto.net.om> Message-ID: <373B838D.B8FAA9D5@ix.netcom.com> --------------44B8E4D6D10D7B96C629F7CC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter and all FIrst of all it would be better if you got you Http address correct. It is http://www2.netcom.com not http:/www.netcom.com. You left out a "/" and you also did not get the "www" correct as it should have been "www2". Second, if you read the E-Mail outage message correctly it clearly goes on to state: "Netcom E-mail Outage As many of you know, Netcom experienced an e-mail file server failure. Below is an explanation and response from MindSpring CEO, Charles Brewer. Update - Thursday, May 13. We are still working on fixing the problem. Thank you for your continued patience. Dear MindSpring/NETCOM Customer, I'm sending this message to all of our customers who have a NETCOM e-mail address beginning with the letter "d". We at MindSpring owe all of you a big apology! On Monday evening, an e-mail server in the NETCOM network failed. As a result, MindSpring/NETCOM customers with mailbox names beginning with the letter "d" were not able to retrieve their e-mail until 6:30 AM EDT/3:30 AM PDT this morning (Wednesday, May 12). Here is the current state of things: Your mailbox should be active by 2AM Eastern Time Thursday morning (Wednesday evening) Because of the heavy traffic while everyone collects their messages, for a short period of time the system may run slowly or even indicate an occasional failed connection to the mail server. This does not indicate the servers have failed again. " Peter Dawson wrote: > FYI please see http:/www.netcom.com > as this is off topic of 6bone activites, > I'll refrain from further postings. > Thank you > > /pete > > Jeff Williams wrote: > > BTW, I called > > > Netcom/Mindspring operations center and they are not aware of > > any > > E-Mail outage and reported none either. I will get in touch > > with > > Mr. Brewer in the mourning by phone as I am a large stock > > holder > > and find out about your PARTIAL message you quote below. > > Interesting > > you did not include his E-mail address in your qoute of him.... Kindest regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 --------------44B8E4D6D10D7B96C629F7CC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Peter and all

  FIrst of all it would be better if you got you Http address correct.  It
is http://www2.netcom.com not http:/www.netcom.com.  You left
out a "/" and you also did not get the "www" correct as it should have been
"www2".  Second, if you read the E-Mail outage message correctly it
clearly goes on to state:
"Netcom E-mail Outage

      As many of you know, Netcom experienced an e-mail file server failure.
      Below is an explanation and response from MindSpring CEO, Charles
      Brewer.

      Update - Thursday, May 13. We are still working on fixing the problem.
      Thank you for your continued patience.
 
 

      Dear MindSpring/NETCOM Customer,

      I'm sending this message to all of our customers who have a NETCOM
      e-mail address beginning with the letter "d". We at MindSpring owe all of
      you a big apology!

      On Monday evening, an e-mail server in the NETCOM network failed. As
      a result, MindSpring/NETCOM customers with mailbox names beginning
      with the letter "d" were not able to retrieve their e-mail until 6:30 AM
      EDT/3:30 AM PDT this morning (Wednesday, May 12).

      Here is the current state of things:

           Your mailbox should be active by 2AM Eastern Time Thursday
           morning (Wednesday evening) Because of the heavy traffic while
           everyone collects their messages, for a short period of time the
           system may run slowly or even indicate an occasional failed
           connection to the mail server. This does not indicate the servers
           have failed again. "
 

Peter Dawson wrote:

FYI   please see http:/www.netcom.com
as this is off topic of 6bone activites,
I'll refrain from further postings.
Thank you

/pete

Jeff Williams wrote:

 BTW, I called

> Netcom/Mindspring operations center and they are not aware of
> any
> E-Mail outage and reported none either.  I will get in touch
> with
> Mr. Brewer in the mourning by phone as I am a large stock
> holder
> and find out about your PARTIAL message you quote below.
> Interesting
> you did not include his E-mail address in your qoute of him....

Kindest regards,

--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
  --------------44B8E4D6D10D7B96C629F7CC-- From latif.ladid@tbit.dk" Dear Patrick, Thanks for the good news in joining the IPv6 FORUM! We are very pleased to welcome CISCO as one the Official 'Founding Members' of the IPv6 FORUM. Thanks for your initiative! R, /Latif Dear Latif, Please find attached Cisco's registration form to the IPv6 Forum. Regards Patrick __________________________________________________________ Patrick Grossetete Senior Consulting Engineer Cisco Systems EMEA * | | * Phone/Vmail: 33.1.6918 6152 * ||| ||| * Fax: 33.1.6928 8326 * ||||| ||||| * mobile: 33.6.0773 7360 * .:||||||||:...:|||||||:. * Email:pgrosset@cisco.com * Cisco Systems EMEA * ____________________________________________________________ From bmanning@ISI.EDU Fri May 14 12:59:39 1999 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 14 May 1999 04:59:39 -0700 (PDT) Subject: New DNS server for IPv6 in Fibertel In-Reply-To: <006b01be9ce2$dc1cced0$1000e818@fibertel.com.ar> from "Patricio Latini" at May 12, 1999 10:49:37 PM Message-ID: <199905141159.AA15459@zed.isi.edu> I'll need the IPv4 address of ipv6.fibertel.com.ar. and you'll need a second server. I can offer our server here for this purpose. If you agree, then I'll code the following entry: ; Patricio S. Latini platini@fibertel.com.ar 14 may 1999 8.3.e.f.f.3.ip6.int. in ns ipv6.fibertel.com.ar. in ns ns.isi.edu. ; > > This is a multi-part message in MIME format. > > ------=_NextPart_000_0068_01BE9CC9.B65CFEE0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hello 6bone People: > Due to the grow of this project in my = > company i installed a new DNS server for the domain = > ipv6.fibertel.com.ar. > This server supports AAAA records and you can reach using it the = > www.ipv6.fibertel.com.ar WWW server 3ffe:3800:1::2 and my ipv6 router = > cisco.ipv6.fibertel.com.ar (3ffe.3800:1::1). > you can also reach my ipv4 running version of the www server at = > www-ipv4.ipv6.fibertel.com.ar. > > i would like to hear toy comments about if it is working from all the = > 6bone. > > Thanks > > Patricio Latini > IPv6 Project Manager > Fibertel TCI2 > Argentina > > ------=_NextPart_000_0068_01BE9CC9.B65CFEE0 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > > http-equiv=3DContent-Type> > > > > >

Hello 6bone People:
>
        = >    =20 >            =20 >       Due to the grow of this project in my = > company i=20 > installed a new DNS server for the domain = > ipv6.fibertel.com.ar.
>
This server supports AAAA records and you can reach = > using it=20 > the href=3D"http://www.ipv6.fibertel.com.ar">www.ipv6.fibertel.com.ar = > WWW=20 > server 3ffe:3800:1::2 and my ipv6 router cisco.ipv6.fibertel.com.ar=20 > (3ffe.3800:1::1).
>
you can also reach my ipv4 running version of the = > www server=20 > at www-ipv4.ipv6.fibertel.com.ar.
>
 
>
i would like to hear toy comments about if it is = > working from=20 > all the 6bone.
>
 
>
Thanks
>
 
>
Patricio Latini
>
IPv6 Project Manager
>
Fibertel TCI2
>
Argentina
> > ------=_NextPart_000_0068_01BE9CC9.B65CFEE0-- > > -- --bill From seamus@insomnia.org Fri May 14 15:52:37 1999 From: seamus@insomnia.org (Patrick Cantwell) Date: Fri, 14 May 1999 09:52:37 -0500 (CDT) Subject: Sigh, Pete Dawson was:Re: sigh, re Jeff Williams In-Reply-To: <373B838D.B8FAA9D5@ix.netcom.com> Message-ID: I've been "lurking" on the 6bone list for a while now, trying to soak up as much about 6bone as I can, so I can begin experimenting with IPv6... I think the best possible solution to the problem of people posting off-topic to the list would be to have someone moderate... All lists, no matter what topic, degrade to this after time if they are not moderated... It's a shame that intelligent, technology-oriented people have to personally attack each other on a TECHNOLOGY list.. but that's how people are. Pat -- Patrick Cantwell President/Systems Administrator, Insomnia Communications pat@insomnia.org TheFloyd @ irc 4668163 @ icq From hansolofalcon@worldnet.att.net Fri May 14 16:02:56 1999 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Fri, 14 May 1999 11:02:56 -0400 Subject: Fuel for further off topic postings Message-ID: <01BE9DF9.5659DD20.hansolofalcon@worldnet.att.net> ------ =_NextPart_000_01BE9DF9.57095700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello from Gregg Levine usually at Jedi Knight Computers While I usually do not post immflamatory postings, and since everyone just got their noses rapped on, I will stretch my credibilty by mentioning this factoid: Around four years ago, AOL had a massive failure in their electronic mail servers, and it took them 14 days to find the problem. It also took them 14 days to repair the problem. As these were the Internet servers for that kind of mail, I feel that the responsibilty of Mindspring/Netcom to solve this problem, in the time frame quoted is very proper. And that all of this complaining is just plain wrong. This is the absolute last blerb on the subject. Let us return to the medium that this mailing list was created for. Gregg C Levine mailto:hansolofalcon@worldnet.att.net This signature supports the Alliance to restore the Republic "They were in the wrong place at the wrong time. Naturally they became heroes" Princess Leia Organa of Alderaan, Senator "Remember, the Force will be with you. Always." General Obi-Wan Kenobi Jedi Knight, Retired ------ =_NextPart_000_01BE9DF9.57095700 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IgQPAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEkAYAjAEAAAEAAAAQAAAAAwAAMAIAAAAL AA8OAAAAAAIB/w8BAAAAZQAAAAAAAAC1O8LALHcQGqG8CAArKlbCFQAAAO++p2H5YdIRhkBERVNU AAEkgQAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAEANmJvbmVAaXNpLmVkdQBTTVRQADZib25lQGlz aS5lZHUAAAAAHgACMAEAAAAFAAAAU01UUAAAAAAeAAMwAQAAAA4AAAA2Ym9uZUBpc2kuZWR1AAAA AwAVDAEAAAADAP4PBgAAAB4AATABAAAAEAAAACc2Ym9uZUBpc2kuZWR1JwACAQswAQAAABMAAABT TVRQOjZCT05FQElTSS5FRFUAAAMAADkAAAAACwBAOgEAAAAeAPZfAQAAAA4AAAA2Ym9uZUBpc2ku ZWR1AAAAAgH3XwEAAAAsAAAAvwAAALU7wsAsdxAaobwIACsqVsIVAAAA776nYflh0hGGQERFU1QA ASSBAAADAP1fAQAAAAMA/18AAAAAAgH2DwEAAAAEAAAAAAAAAmdNAQSAAQAkAAAARnVlbCBmb3Ig ZnVydGhlciBvZmYgdG9waWMgcG9zdGluZ3MARA0BBYADAA4AAADPBwUADgALAAIAOAAFADMBASCA AwAOAAAAzwcFAA4ACgAwADUABQBdAQEJgAEAIQAAADM2QjFFMjNDMEI3RjAyNDk4Nzc1OTQzMjM3 QzY0RjdCAAoHAQOQBgDkBwAAIQAAAAsAAgABAAAACwAjAAEAAAADACYAAAAAAAsAKQABAAAAAgEx AAEAAADcAAAAUENERkVCMDkAAQACAFMAAAAAAAAAOKG7EAXlEBqhuwgAKypWwgAAbXNwc3QuZGxs AAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XE1TT0ZGSUNFXHdncG8wMDAwXG1haWwucHN0ABgAAAAA AAAA5r6nYflh0hGGQERFU1QAAaKAAAAAAAAAGAAAAAAAAADmvqdh+WHSEYZAREVTVAABwoAAABAA AAA2seI8C38CSYd1lDI3xk97JAAAAEZ1ZWwgZm9yIGZ1cnRoZXIgb2ZmIHRvcGljIHBvc3Rpbmdz AAMANgAAAAAAQAA5AKCUS9kanr4BHgBwAAEAAAAkAAAARnVlbCBmb3IgZnVydGhlciBvZmYgdG9w aWMgcG9zdGluZ3MAAgFxAAEAAAAWAAAAAb6eGtirI+U9mm6SRyWaJGKkrMT/5QAAHgAeDAEAAAAF AAAAU01UUAAAAAAeAB8MAQAAAB8AAABoYW5zb2xvZmFsY29uQHdvcmxkbmV0LmF0dC5uZXQAAAMA BhCiOs/tAwAHEGsDAAAeAAgQAQAAAGUAAABIRUxMT0ZST01HUkVHR0xFVklORVVTVUFMTFlBVEpF RElLTklHSFRDT01QVVRFUlNXSElMRUlVU1VBTExZRE9OT1RQT1NUSU1NRkxBTUFUT1JZUE9TVElO R1MsQU5EU0lOQ0VFAAAAAAIBCRABAAAA0wMAAM8DAAAOBQAATFpGdeII9xkDAAoAcmNwZzEyNRYy APgLYG4OEDAzM50B9yACpANjAgBjaArAYHNldDAgB20CgH2zCoAIyCA7CW8OMDUCgDkKgXVjAFAL Awu1IEiUZWwJACADUiBHCXBAZ2cgTGV2C4BlECB1c3UHQGx5IIphBUBKCYBpIEsDAAxnaAVACFBt cHV0zQSQcwqiCoBXaAMQF4BKSReXZBZgbm8FQHBsb3MFQAdwbQ7xAMB0jwWwGAAbcguAZ3MsGBDI bmQgAJBuYxeAF0BtBJB5AiAXgGoXoAVAZ+EbQXRoZWkFwBswETChBCByYXBwCYAgAiBfHRAaYAPw FkAdYHQJcHS5EPAgbRgABQAYYWIDELp0GABiGAAHgAIwaQIgPxzRHuEEABZwANAcQGlk/joK4wqA BxAIYB1BAhAIcHggeWURERgQHrAdEEFYT0wgEQAdUGEhQGH9BBBpHeAjUQMQCHAXgAuA3x7lFjAF kCDgIrFjJlEDES0RMHId4R0FaR7Rb28max7iFrAxNBrwYXn/BCAcQBZwC4AdUB7xG2ADYLsCYCpg LhpQBUAHQHMWYL8p/ysCCXAKsB8hK5tBKvG/HwARMCBwBJAXgCuSSQIwvwSREUAo5iSxLoIYIWsr UuxvZiiTIEJmCeADIDHjeyuSCXBzG3AAgSHUMoFN7ytRNDAFEA8gLwfAIRAWofsrESywbCaxIxMr 1R0QJ2SfHuAHcRZxHBAXgHF1G0DfH/EjMR3iK8If4HIvUStj/xghF9EyciMTNgELUyLSIzGvHmML UyBwKEFnLEBUIyLfIzErkgGgNnEZUSALYBuROSwBcmIgESuDF7Biar8oESxAFzAFQBegLiF0CHDf J3EswSuhB4AYcHU2ITOU3yMxKKIi0kMwG5F3JnAhcncYIB/xMaEuGaQK8xbFQ3cXJgjQAEF1AyAo ohxAOi8RAACACPEjYGwFoG5A0ncFsGxkMOEuGCBAcP8w4UaBAUBG0AFAGbM9owCQ/GduGCAnIhew H9AJET4E/kEWQAcwHZIuAxuQBbAwNL5SLkBAIEMwAOAZsyI9oP5lGAAwAze1PTM8wh2hM6X3T3Q4 IixATkrCF9Me8SIRXwWQOJIfAANgB5AiGaRQHzWBHaAEERcwBzAgT3K+ZwBwJkAygUvwBIFhAHD/ HRAGYEqxBbBN9U1wB4AG0PcEkB0QK5JGBbAdoSCDUlDfIHEe8CUACGAvUWxD0Crgui5TJUcJ8FVB AyBPIdD0LVcDkUsJ8CvwGIAYWX8dEE1wHMAJcUTZGaQSkQABXdAAAwAQEAAAAAADABEQAAAAAAMA gBD/////QAAHMEA0w+IYnr4BQAAIMEA0w+IYnr4BCwAAgAggBgAAAAAAwAAAAAAAAEYAAAAAA4UA AAAAAAADAAKACCAGAAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAMABYAIIAYAAAAAAMAAAAAAAABG AAAAAFKFAADzFQAAHgAlgAggBgAAAAAAwAAAAAAAAEYAAAAAVIUAAAEAAAAFAAAAOC4wNAAAAAAD ACaACCAGAAAAAADAAAAAAAAARgAAAAABhQAAAAAAAAsAL4AIIAYAAAAAAMAAAAAAAABGAAAAAA6F AAAAAAAAAwAwgAggBgAAAAAAwAAAAAAAAEYAAAAAEYUAAAAAAAADADKACCAGAAAAAADAAAAAAAAA RgAAAAAYhQAAAAAAAB4AQYAIIAYAAAAAAMAAAAAAAABGAAAAADaFAAABAAAAAQAAAAAAAAAeAEKA CCAGAAAAAADAAAAAAAAARgAAAAA3hQAAAQAAAAEAAAAAAAAAHgBDgAggBgAAAAAAwAAAAAAAAEYA AAAAOIUAAAEAAAABAAAAAAAAAB4APQABAAAAAQAAAAAAAAADAA00/TcAADro ------ =_NextPart_000_01BE9DF9.57095700-- From jwkckid1@ix.netcom.com Fri May 14 10:38:34 1999 From: jwkckid1@ix.netcom.com (Jeff Williams) Date: Fri, 14 May 1999 10:38:34 +0100 Subject: sigh, re Jeff Williams References: <19990513201725.A26164@hindenburg.eboai.org> <373B41D9.C0174B50@ix.netcom.com> <373BC580.85AB6A3C@gto.net.om> Message-ID: <373BEF17.1DD14E66@ix.netcom.com> Peter and all, Thank you for your suggestion. However I already KNOW why some addresses on cc's were bouncing. Netcom had nothing to do with the problem. I believe I stated them clearly on Wednesday and again on thursday as well. They are as follows: 1.) www.nic.ar showed in the whois results the domain, fibertel.com.ar on Wednesday was NOT available. This was in my cc list for relevant posts as well as other DN's that Patricio Latini posted on those relevant threads. 2.) I also pointed out to Peter Tattem that his URL, HTTP://jazz-1.trumpet.com.au/ipv6-draft/dtcp-draft-prt-13-may-1999.htm was not resolving because trumpet.com.au at ARIN's whois was showing did not exist. This URL still does not resolve at this moment. Peter Tattem incorrectly stated that I was pointing to Netcom's DNS. I corrected him informing him that I was not pointing to Netcom's DNS servers. Hence his DN is partly of completely lame, or he has a routing problem. Hence my E-Mail bounced on his DN. I hope that this helps to clarify things a bit for you. I realize that following the relevant threads is sometime confusing. But it is really advisible that you do your homework before making statements on a public list such as this. However anyone can make a mistake, so don't feel bad... Peter Dawson wrote: > Jeff, > > I think that your ISP provider (netcom.com) is having some > problems... just followup on with your upstream > provider to see , why you can't resolve the issues > and the resons on your email bouncing before posting > to the list, please. > > Thank you > > /pete > ------------------------- > Netcom E-mail Outage > > As many of you know, Netcom experienced an e-mail file > server failure. > Below is an explanation and response from MindSpring CEO, > Charles > Brewer. > > Update - Thursday, May 13. We are still working on fixing > the problem. > Thank you for your continued patience. > > ------------------ > Jeff Williams wrote: > > > Jason and all, > > > > Jason, you have no idea what you are talking about . List > > manager, > > is this sort of personal unprovoked attack allowed on this > > list? > > > > Jason T. Nelson wrote: > > > > > Jeff Williams is a known loonie and possible troll on the > > inet-access list > > > (thank goodness he seems to have either stopped tormenting us > > or the list > > > manager finally booted him off). > > > > > > I'm sorry to have to introduce this badly off-topic posting, > > but he's > > > starting to drag the list down with non-operational issues > > and I felt > > > everyone here should know. > > > > > > -- > > > Jason T. Nelson > > > BOFH Extraordiaire > > > http://www.eboai.org/~jtn/ > > > disclaimer: My opinions are my own. Don't bother my employer > > about them. > > > > Regards, > > > > -- > > Jeffrey A. Williams > > CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. > > Information Network Eng. Group. INEG. INC. > > E-Mail jwkckid1@ix.netcom.com > > Contact Number: 972-447-1894 > > Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 Regards, -- Jeffrey A. Williams CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng. Information Network Eng. Group. INEG. INC. E-Mail jwkckid1@ix.netcom.com Contact Number: 972-447-1894 Address: 5 East Kirkwood Blvd. Grapevine Texas 75208 From bmanning@ISI.EDU Fri May 14 18:40:23 1999 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 14 May 1999 10:40:23 -0700 (PDT) Subject: moderation is the order of the day Message-ID: <199905141740.KAA23181@boreas.isi.edu> Hi, Since we have not had the foresight to constrain postings on this list to 6bone & IPv6 issues and have degenerated into assertions of who's ISP does what to whom and why the 6bone does not meet some peoples views on what is operationally correct (this is a testbed fur crying out loud!) I am envoking list admin privledge and will begin list moderation. -- bill From kazu@iijlab.net Thu May 20 06:48:11 1999 From: kazu@iijlab.net (Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)) Date: Thu, 20 May 1999 14:48:11 +0900 Subject: pTLA request from IIJ Message-ID: <19990520144811J.kazu@iijlab.net> IIJ(http://www.iij.ad.jp) would like to request one pTLA block. Conformance to RFC 2546 is as follows; 1. The site MUST have experience with IPv6 on the 6Bone, at least as a leaf site and preferably as a transit pNLA under an existing pTLA. IIJ is a transit pNLA of the WIDE pTLA. 2. The site MUST have the ability and intent to provide "production- like" 6Bone backbone service to provide a robust and operationally reliable 6Bone backbone. IIJ is now providing robust connectivity services to seven IPv6 sites. 3. The site MUST have a potential "user community" that would be served by becoming a pTLA, e.g., the requester is a major player in a region, country or focus of interest. IIJ is one of the biggest IPv4 ISPs in Japan. And already connects seven IPv6 sites. 4. Must commit to abide by the 6Bone backbone operational rules and policies as defined in the present document. IIJ certainly commits. Note that some of IIJ guys are actually the operators of WIDE IPv6 backbone. --Itojun & Kazu, IIJ From fink@es.net Thu May 20 07:38:34 1999 From: fink@es.net (Bob Fink) Date: Wed, 19 May 1999 23:38:34 -0700 Subject: Application for pTLA from ICM-PL - review will close 4 June Message-ID: <4.1.19990519233421.00b1f950@imap2.es.net> Per the request from Kazu Yamamoto (below), I'm opening a two week window for the review of a pTLA for IIJ. I will close this on 4 June 99. Note that this will be a /28 pTLA assignment. Thanks, Bob ==== >To: 6bone@ISI.EDU >Subject: pTLA request from IIJ >From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) > | >Date: Thu, 20 May 1999 14:48:11 +0900 > >IIJ(http://www.iij.ad.jp) would like to request one pTLA block. > >Conformance to RFC 2546 is as follows; > > 1. The site MUST have experience with IPv6 on the 6Bone, at least as > a leaf site and preferably as a transit pNLA under an existing > pTLA. > >IIJ is a transit pNLA of the WIDE pTLA. > > 2. The site MUST have the ability and intent to provide "production- > like" 6Bone backbone service to provide a robust and operationally > reliable 6Bone backbone. > >IIJ is now providing robust connectivity services to seven IPv6 sites. > > 3. The site MUST have a potential "user community" that would be > served by becoming a pTLA, e.g., the requester is a major player > in a region, country or focus of interest. > >IIJ is one of the biggest IPv4 ISPs in Japan. And already connects >seven IPv6 sites. > > 4. Must commit to abide by the 6Bone backbone operational rules and > policies as defined in the present document. > >IIJ certainly commits. Note that some of IIJ guys are actually >the operators of WIDE IPv6 backbone. > >--Itojun & Kazu, IIJ From bmanning@ISI.EDU Thu May 20 14:57:52 1999 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Thu, 20 May 1999 06:57:52 -0700 (PDT) Subject: Application for pTLA from ICM-PL - review will close 4 June In-Reply-To: <4.1.19990519233421.00b1f950@imap2.es.net> from "Bob Fink" at May 19, 1999 11:38:34 PM Message-ID: <199905201357.AA07092@zed.isi.edu> I think this is a reasonable request and should be approved. > > Per the request from Kazu Yamamoto (below), I'm opening a two week window for the review of a pTLA for IIJ. I will close this on 4 June 99. Note that this will be a /28 pTLA assignment. > > Thanks, > Bob > ==== > >To: 6bone@ISI.EDU > >Subject: pTLA request from IIJ > >From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) > > | > >Date: Thu, 20 May 1999 14:48:11 +0900 > > > >IIJ(http://www.iij.ad.jp) would like to request one pTLA block. > > > >Conformance to RFC 2546 is as follows; > > > > 1. The site MUST have experience with IPv6 on the 6Bone, at least as > > a leaf site and preferably as a transit pNLA under an existing > > pTLA. > > > >IIJ is a transit pNLA of the WIDE pTLA. > > > > 2. The site MUST have the ability and intent to provide "production- > > like" 6Bone backbone service to provide a robust and operationally > > reliable 6Bone backbone. > > > >IIJ is now providing robust connectivity services to seven IPv6 sites. > > > > 3. The site MUST have a potential "user community" that would be > > served by becoming a pTLA, e.g., the requester is a major player > > in a region, country or focus of interest. > > > >IIJ is one of the biggest IPv4 ISPs in Japan. And already connects > >seven IPv6 sites. > > > > 4. Must commit to abide by the 6Bone backbone operational rules and > > policies as defined in the present document. > > > >IIJ certainly commits. Note that some of IIJ guys are actually > >the operators of WIDE IPv6 backbone. > > > >--Itojun & Kazu, IIJ > > > -- --bill From bmanning@ISI.EDU Fri May 21 12:10:54 1999 From: bmanning@ISI.EDU (Bill Manning) Date: Fri, 21 May 1999 04:10:54 -0700 (PDT) Subject: BOUNCE 6bone@zephyr.isi.edu: Message too long (>40000) (fwd) Message-ID: <199905211110.EAA29403@boreas.isi.edu> > > This is a multi-part message in MIME format. > --------------932A34D6E25E10D9739ADD55 > Content-Type: text/plain; charset=EUC-KR > Content-Transfer-Encoding: 7bit > > Dear Members: > > My job is to design a 6Bone based on KOREN(KOrea > Research and Education Network). > I saw a presentation(attached in this E-mail) from telebit > company. At page 8, there is a expression like that: > > AGGRESSIVE : IETF Will Not Support IPv4 beyond 2002 > > Is it really true that IETF will support only IPv6 from > 2003? > This is a important matter to decide the future plan of data > networks for my company. Please send me a E-mail if > you have the answer. > > Sincerely, > Sahng-Beom Kim > > -- > Kim, Sahng-Beom / Korea Telecom > TEL : +82-42-870-8322 > FAX : +82-42-870-8329 > E-mail : ksbn@kt.co.kr > -- > > > --------------932A34D6E25E10D9739ADD55 > Content-Type: application/ppt; > name="6REN-IPv6.ppt" > Content-Transfer-Encoding: base64 > Content-Disposition: inline; > filename="6REN-IPv6.ppt" > ( attached ppt file excised ) -- "When in doubt, Twirl..." -anon From latif.ladid@tbit.dk" 40000) (fwd) Message-ID: <01BEA3AB.4EA62900.Latif.LADID@village.uunet.lu> I have already responded to this email. /Latif ---------- From: Bill Manning[SMTP:bmanning@ISI.EDU] Sent: Friday, May 21, 1999 01:10 To: 6bone@ISI.EDU Subject: BOUNCE 6bone@zephyr.isi.edu: Message too long (>40000) (fwd) > > This is a multi-part message in MIME format. > --------------932A34D6E25E10D9739ADD55 > Content-Type: text/plain; charset=EUC-KR > Content-Transfer-Encoding: 7bit > > Dear Members: > > My job is to design a 6Bone based on KOREN(KOrea > Research and Education Network). > I saw a presentation(attached in this E-mail) from telebit > company. At page 8, there is a expression like that: > > AGGRESSIVE : IETF Will Not Support IPv4 beyond 2002 > > Is it really true that IETF will support only IPv6 from > 2003? > This is a important matter to decide the future plan of data > networks for my company. Please send me a E-mail if > you have the answer. > > Sincerely, > Sahng-Beom Kim > > -- > Kim, Sahng-Beom / Korea Telecom > TEL : +82-42-870-8322 > FAX : +82-42-870-8329 > E-mail : ksbn@kt.co.kr > -- > > > --------------932A34D6E25E10D9739ADD55 > Content-Type: application/ppt; > name="6REN-IPv6.ppt" > Content-Transfer-Encoding: base64 > Content-Disposition: inline; > filename="6REN-IPv6.ppt" > ( attached ppt file excised ) -- "When in doubt, Twirl..." -anon From fink@es.net Mon May 24 23:26:11 1999 From: fink@es.net (Bob Fink) Date: Mon, 24 May 1999 15:26:11 -0700 Subject: new pTLAs for TRUMPET/AU and ICM-PL/PL Message-ID: <4.1.19990524150124.00b8d950@imap2.es.net> I would like to announce the assignment of two pTLAs based on review comments. Please note that these are the first two 28-bit pTLAs. --- TRUMPET/AU - Trumpet Software International Pty Ltd is an Internet shareware developer (e.g., WinSock and FireSock), as well as a Tasmanian ISP located in Hobart the capital city of Tasmania, Australia: inet6num: 3FFE:8000::/28 netname: TRUMPET --- ICM-PL - Interdisciplinary Centre for Mathematical and Computational Modelling at Warsaw University, Poland, an Internet hub site for Poland with very good international connectivity: inet6num: 3FFE:8010::/28 netname: ICM-PL --- Welcome both networks to the 6bone backbone! Bob From map@stacken.kth.se Thu May 27 02:34:12 1999 From: map@stacken.kth.se (Magnus Ahltorp) Date: 27 May 1999 03:34:12 +0200 Subject: Peering Message-ID: Our site (STACKEN) peers with SICS and ATT-LABS-EUROPE. We speak BGP4+ to SICS and we wish to peer with someone else that can speak BGP4+. I have tried to contact ATT-LABS-EUROPE to ask them to turn BGP4+ on, but I have failed to reach them. Would someone else be interested in peering with us? We wish to do some testing in the multihoming area, and therefore we need access to two different "providers". We must be able to speak BGP4+ to you, in order to make routing decisions. You must be able to hand out a /48 to us. Magnus Ahltorp Stacken Computer Club Royal Institute of Technology Stockholm, Sweden From fink@es.net Thu May 27 02:54:30 1999 From: fink@es.net (Bob Fink) Date: Wed, 26 May 1999 18:54:30 -0700 Subject: Application for pTLA from Dante/Terena/Quantum - review will close 8 June Message-ID: <4.1.19990526184936.0097eb70@imap2.es.net> 6bone Folk, Per the request from Simon Nybroe (below), I'm opening a two week window for the review of a pTLA for QTP. I will close this on 8 June 99 (a little shy of 2 weeks given my scheduled departure for Vacation). I believe this is a very important step for v6 as it represents pan-European network connectivity via IPv6 with connections to 6REN participants via the 6TAP. Note that this will be a /28 pTLA assignment. Thanks, Bob ==== >Date: Wed, 26 May 1999 20:08:59 +0200 >From: Simon Nybroe >To: Bob Fink >Subject: pTLA Request > >Hi, > >We (The ipv6 testing group under the QTP) are working on plans of >connecting the European National Research Networks in a native IPv6 backbone. >We plan to use a >setup very much similar to the one used for the 6TAP. The entire project >are to be run as an long running test under the Quantum Test Project (QTP): > > > >As the plans are right now, limited bandwidth PVCs (in the range >0.5-2mbps) will be allocate in the TEN-155 backbone and Telebit will >provide a IPv6 capable router as an open-ended loan. > >Currently we have 12 participants, many already with 6bone experience >and the plan is to get the infrastructure established as soon as >possible. > >Future experiments will include both IPv6 end-to-end as well as more >experiments with v6 peering. For details on what we plan to do, please >see . The pages in no way done, but >they do reflect what we plan to do. > >The v6 peering experiments plans will require the use of a new pTLA and >we will therefore like to request one. > >I understand that the current guidelines for obtaining a pTLA are the >ones listed in RFC2546 Chapter 7. Many of the participants already holds >pTLAs and operate under the exact same guidelines, and I can assure you >that we have no plans to do otherwise in the context of the QTPv6 Group. > >-- >Simon Nybroe System Developer, M. Sc. >Telebit Communications A/S tel: +45 87 38 22 58 >Fabrikvej 11 fax: +45 86 28 81 86 >DK-8260 Viby J e-mail: sin@tbit.dk -end From bmanning@ISI.EDU Fri May 28 17:19:53 1999 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 28 May 1999 09:19:53 -0700 (PDT) Subject: v6 message to IANA (fwd) Message-ID: <199905281619.AA06435@zed.isi.edu> This was sent to the ARIN members list. I've sent some comments back to Kim which I'll forward to the list in a moment. > > The following message was sent to the IANA on behalf of the Regional > Internet Registries. Once we receive approval from IANA on the v6 > policy guidelines, below, we'll be ready to begin making allocations. > > Kim > > > > Joint Regional Internet Registry email to IANA > > To: the Internet Assigned Numbers Authority > > Subject: Initial IPv6 allocations > > As you will be aware, APNIC, ARIN, and the RIPE NCC have for many months > been working closely with their respective memberships and the IPv6 > community to produce a document setting out the policies and guidelines > required for supporting responsible management of IPv6 address space. We > now believe that the attached "Provisional IPv6 Assignment and Allocation > Policy Document" is sufficiently advanced to allow the initial "bootstrap" > phase of allocations to begin. > > There is growing anticipation within the IPv6 community and the Internet > community in general that IPv6 operations be established as soon as > possible. We therefore propose to commence allocating sub-TLAs following > the general scheme described in the Internet Draft "Initial IPv6 Sub-TLA > Assignments" and the more specific > policies and guidelines set out in the attached policy document. Although > the document will be further developed and refined in the coming months - > according to the input and experience gained during the initial period - > the general community support for this document is strong enough to > justify its implementation in its current form. > > Accordingly, the Regional Internet Registries seek IANA's formal > delegation of the address ranges specified in the Internet Draft and the > approval to commence IPv6 allocations on the basis set out in this email. > > On behalf and with the authority of: > > Paul Wilson, Director-General APNIC > Kim Hubbard, President ARIN > Daniel Karrenberg, General Manager RIPE NCC > > > > PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT > > (28 May 1999) > > Scheduled revision: Formal revision of this document is scheduled to be > commenced by 1 October 1999. > > TABLE OF CONTENTS > > Abstract > > 1. Scope > > 2. IPv6 Address Space and the Internet Registry System > > 2.1 The Internet Registry System Hierarchy > > 2.2 Goals of the Internet Registry System > > 3. IPv6 Technical Framework > > 3.1 IPv6 Addressing Hierarchy > > 3.2 Initial IPv6 Addressing Hierarchy > > 4. Addressing Policies > > 4.1 IPv6 Addresses Not to be Considered Property > > 4.2 Allocations > > 4.3 Assignments > > 4.4 Reclamation Methods/Conditions > > 5. Organizations Operating in More than One Region > > 6. DNS and Reverse Address Mapping > > 7. Glossary > > 8. List of References > > ABSTRACT > > This document describes the registry system for distributing globally > unique unicast IPv6 address space. IPv6 address space is distributed in a > hierarchical manner (as is IPv4 address space), managed by the IANA and > further delegated by the Regional Internet Registries (Regional IRs) as > described in RFC 1881. In the case of IPv6, the Regional IRs allocate > Top-Level Aggregation Identifiers (TLAs) to organizations, which, as TLA > Registries, in turn allocate or assign address space to other Internet > Service Providers (ISPs) and end users. ISPs then serve as Next Level > Aggregation (NLA) Registries for their customers. > > This document describes the responsibilities, policies, and procedures > associated with IPv6 address space management, to be followed by all > organizations within the allocation hierarchy. The intention of this > document is to provide a framework for clear understanding and consistent > application of those responsibilities, policies, and procedures throughout > all layers of the hierarchy. > > 1. SCOPE > > This document first describes the global Internet Registry system for the > distribution of IPv6 address space (as defined in RFC 2374) and the > management of that address space. It then describes the policies and > guidelines governing the distribution of IPv6 address space. The policies > set forth in this document should be considered binding on all > organizations that receive allocations or assignments of IPv6 address space > either directly or indirectly from a Regional IR. > > This document describes the primary operational policies and guidelines in > use by all Regional IRs. Regional IRs may implement supplementary policies > and guidelines to meet the specific needs of the Internet communities > within their regions. > > These policies and guidelines are subject to change based upon the > development of operational experience and technological innovations, which > together emerge as Internet best practice. > > The structure of this document is as follows: > > Section 2, "IPv6 Address Space and the Internet Registry System", describes > the hierarchical structure of responsible organizations within the Internet > Registry system and the explicit goals that determine the framework of > policies for allocation and assignment of IPv6 address space. > > Section 3, "IPv6 Technical Framework", explains the IPv6 addressing format > and describes the differences between TLA, NLA, and SLA blocks. > > Section 4, "Addressing Policies", describes the requirements for applying > for a TLA allocation and the policies that apply to such allocations. It > discusses how TLA registries can allocate space to other ISPs (NLA blocks) > and assign address space to end-users (SLAs). > > Section 5, "Organizations Operating in More than One Region", describes the > requirements for organizations operating in more than one IR region > requesting address space. > > Section 6, "DNS and Reverse Address Mapping", describes the role of the > Regional IRs in providing reverse delegation and explains how the Regional > IRs can manage subsidiary reverse delegation of allocated/assigned address > space. > > Section 7, "Glossary", provides a listing of terms used in this document > along with their definitions. > > Section 8, "List of References", provides a list of documents referenced in > this document. > > 2 IPv6 ADDRESS SPACE AND THE INTERNET REGISTRY SYSTEM > > IPv6 unicast addresses are aggregatable with contiguous bit-wise masks used > to define routable prefixes, using a method similar to that used for IPv4 > addresses under CIDR. With IPv6, scarcity of address space is assumed to no > longer exist for the end-user. However, inefficient assignments of address > space and rapid expansion of routing tables remain as serious potential > impediments to the scalability of the Internet. The Internet Registry > system exists to ensure that IPv6 address space is managed in a globally > consistent, fair, and responsible manner that minimizes wastage, and > maximizes aggregation within the routing structure. > > 2.1 The Internet Registry System Hierarchy > > The hierarchical Internet Registry system exists to enable the goals > described in this document to be met. In the case of IPv6, this hierarchy > consists of the following levels, as seen from the top down: IANA, Regional > Internet Registries, TLA, NLA Registries, and end-sites. > > 2.1.1 IANA > > The Internet Assigned Numbers Authority (IANA) has authority over all IP > number spaces used in the Internet, including IPv6 address space. IANA > allocates parts of the IPv6 address space to Regional Internet Registries > (Regional IRs) according to their established needs. > > 2.1.2 Regional Internet Registries > > Regional IRs operate in large geographical regions such as continents. > Currently, three Regional IRs exist: ARIN serving North and South America, > the Caribbean, and sub-Saharan Africa; RIPE NCC serving Europe, the Middle > East, and parts of Africa; and APNIC serving the Asia Pacific region. These > Regional IRs also serve areas beyond their core service areas to ensure > that all parts of the globe are covered. Additional Regional IRs may be > established in the future, although their number will remain relatively > low. Service areas will be of continental dimensions. > > Regional IRs are established under the authority of the IANA. This requires > consensus within the Internet community and among the ISPs of the > respective region. > > 2.1.3 TLA Registries > > TLA Registries are established under the authority of the appropriate > Regional IR to enable "custodianship" of a TLA or sub-TLA block of IPv6 > addresses. TLA Registries perform roles and bear responsibilities which are > analogous and consistent with those of the Regional IR within their > designated network services and infrastructures. > > 2.1.4 NLA Registries > > [to be written] > > 2.1.5 End-sites [to be written] > > 2.2 Goals of the Internet Registry System > > The goals described in this section have been formulated by the Internet > community with specific reference to IPv6 address space. They reflect the > mutual interest of all members of that community in ensuring that the > Internet is able to function and grow to the maximum extent possible. It is > the responsibility of every IR to ensure that all assignments and > allocations of IPv6 address space are consistent with these goals. > > These goals will occasionally be in conflict with the interests of > individual ISPs or end-users. Therefore, IRs evaluating requests for > allocations and assignments must carefully analyze all relevant > considerations and must seek to balance the needs of individual applicants > with the needs of the Internet community as a whole. The policies and > guidelines described in this document are intended to help IRs balance > these needs in consistent and equitable ways. Full documentation of, and > transparency within, the decision making process must also be maintained in > order to achieve this result. > > 2.2.1 Uniqueness > > Each IPv6 unicast address must be globally unique. This is an absolute > requirement for guaranteeing that every host on the Internet can be > uniquely identified. > > 2.2.2 Aggregation > > IPv6 addresses must be distributed in a hierarchical manner, permitting the > aggregation of routing information and limiting the number of routing > entries advertised into the Internet. This is necessary to ensure proper > operation of Internet routing and to maximize the routing system's ability > to meet the demands of both likely and unforeseeable future increases in > both size and topological complexity. In IPv6, aggregation of external > routes is the primary goal. > > This goal is motivated by the problems which arose in IPv4 network > addressing. IPv4 address allocations have not been sufficiently > hierarchical to ensure efficient routing across the Internet. Inefficient > use of classful allocations led to an excess of routing entries appearing > in the default-free routing table. Furthermore, increased complexity of > network topologies led to IPv4 prefixes being announced many times via > different routes. > > Responsible policies and guidelines must limit the number of top level > prefixes that are announced on the Internet so as to ensure that the > problems of IPv4 are not repeated in IPv6. Such policies and guidelines > will always reflect the constraints of current router technology and will > be subject to reevaluation as that technology advances. Furthermore, such > policies and guidelines will be reviewed according to a model consistent > with that provided in RFC 2374 and RFC 2450. Under this model, a threshold > is set significantly below the number of default-free routing table entries > considered to be currently supportable. If the number of entries reaches > that threshold, then allocation criteria are to be reviewed (see section > 4.4). > > 2.2.3 Efficient Address Usage > > Although IPv6 address resources are abundant, the global Internet community > must be careful to avoid repeating the problems that arose in relation to > IPv4 addresses. Specifically, even though "conservation" of IPv6 addresses > is not a significant concern, registries must implement policies and > guidelines that prevent organizations from stockpiling addresses. IPv6 > addressing architecture allows considerable flexibility for end-users; > however, all registries must avoid wasteful use of TLA and NLA address > space by ensuring that allocations and assignments are made efficiently and > based on demonstrated need. > > 2.2.4 Registration > > Every assignment and allocation of IPv6 Internet address space must be > registered in a publicly accessible database. This is necessary to ensure > uniqueness and to provide information for Internet trouble shooting at all > levels. It also reflects the expectation of the Internet community that all > custodians of public resources, such as public address space, should be > identifiable. As is the case with IPv4 addresses, each of the Regional IRs > will maintain a public database where all IPv6 allocations and assignments > are entered. > > 3. IPv6 TECHNICAL FRAMEWORK > > 3.1 IPv6 Addressing Hierarchy > > RFC 2374 specifies that aggregatable addresses are organized into a > topological hierarchy, consisting of a public topology, a site topology, > and interface identifiers. These in turn map to the following: > > | 3| 13 | 8 | 24 | 16 | 64 bits | > +--+-----+---+--------+--------+----------------------------+ > |FP| TLA |RES| NLA | SLA | Interface ID | > | | ID | | ID | ID | | > +--+-----+---+--------+--------+----------------------------+ > |-- public topology---| site | Interface | > | |topology| | > +---------------------+--------+----------------------------+ > | | | > |-------- network portion----->+<-----host portion----------| > | /64 | > |-----------------------------------------------------------| > > The public routing topology is represented by a /48, giving each site 16 > bits to create their local topology. The host portion is represented by the > last 64 bits of the address. > > Because all interface IDs are required to be in the EUI-64 format (as > specified in RFC 2373 and RFC 2374) the boundary between the network and > host portions is "hard" and ID address space cannot be further sub-divided. > > Also, in order to facilitate multihoming and renumbering, the boundary > between the public topology and the site topology division at the /48 is > also hard. (RFC 2374 explains this more completely.) > > 3.2 Initial IPv6 Addressing Hierarchy > > A modified version of the addressing hierarchy described in section 3.1 > will be used for the initial IPv6 allocations. The first TLA prefix (TLA > 0x0001) has been divided into further blocks, called "sub-TLAs", with a > 13-bit sub-TLA identifier. Part of the reserved space and the NLA space > have been used for this purpose. > > This modified addressing hierarchy has the following format and prefix > boundaries: > > Format boundaries > > | 3| 13 | 13 | 6 | 13 | 16 | 64 bits | > +--+----------+---------+---+--------+--------+--------------------+ > |FP| TLA | sub-TLA |Res| NLA | SLA | Interface ID | > | | ID | | | ID | ID | | > +--+----------+---------+---+--------+--------+--------------------+ > > Prefix boundaries (starting at bit 0) > > number of the number of the ID > left-most right-most longest length > bit bit prefix (in bits) > ************ ************ ******* ******** > TLA ID 3 15 /16 13 > sub-TLA ID 16 28 /29 13 > Reserved 29 34 > NLA ID 35 47 /48 13 > SLA ID 48 63 /64 16 > > For purposes of a "slow start" of a sub-TLA, the first allocation to a TLA > Registry will be a /35 block (representing 13 bits of NLA space). The > Regional IR making the allocation will reserve an additional six bits for > the allocated sub-TLA. When the TLA Registry has fully used the first /35 > block, the Regional IR will use the reserved space to make subsequent > allocations (see section 4.2.5). > > All router interfaces are required to have at least one link-local unicast > address or site-local address. It is recommended that site-local addresses > be used for all point-to-point links, loopback addresses, and so forth. As > these are not required to be visible outside the site's network, they do > not require public address space. Any global unicast address space assigned > must not be used for link-local or site-local purposes as there is address > space reserved for these purposes. (Note that "all 1s" and "all 0s" are > valid unless specifically excluded through reservation. See list of > reserved addresses in RFC 2373.) > > 4. ADDRESSING POLICIES > > As described above, Regional IRs make IPv6 allocations to requesting > organizations that qualify for a sub-TLA (TLA Registries). TLA Registries > then allocate NLA space to ISPs that are their customers (NLA Registries). > NLA Registries in turn assign SLA space to end-users. TLA Registries may > also assign SLA space directly to end-users. TLA Registries and NLA > Registries also use SLA space to address their own networks. This > hierarchical structure of allocations and assignments is designed to > maximize the aggregation of routing information. > > 4.1 IPv6 Addresses not to be considered property > > All allocations and assignments of IPv6 address space are made on the basis > that the holder of the address space is not to be considered the "owner" of > the address space, and that all such allocations and assignments always > remain subject to the current policies and guidelines described in this > document. Holders of address space may potentially be required, at some > time in the future, to return their address space and renumber their > networks in accordance with the consensus of the Internet community in > ensuring that the goals of aggregation and efficiency continue to be met. > > 4.1.1 Terms of allocations and assignments to be specified > > At the time of making any allocation or assignment of IPv6 address space, > Registries should specify the terms upon which the address space is to be > held and the procedures for reviewing those terms in the future. Such terms > and procedures should be consistent with the policies and guidelines > described in this document. > > 4.2 Allocations > > In order to meet the goal of aggregation (section 2.2.2) Regional IRs will > only allocate sub-TLA address space to organizations that meet the criteria > specified in one or more of the following sections: 4.2.1 "General Criteria > for Initial Sub-TLA Allocation" and 4.2.2 "Criteria for sub-TLA Allocations > in Transitional 'Bootstrap' Phase". > > The criteria for an initial allocation to an organization are different > from the criteria that apply for subsequent allocations. Whereas the > requirements for an initial allocation are based on technical > considerations, requests for additional address space are evaluated solely > on the basis of the usage rate of the initial allocation. > > The following criteria for sub-TLA allocations reflect the intentions of > the authors of the IPv6 addressing architecture (see RFC 2374, RFC 2373, > and RFC 2950), namely that addressing policies must promote the goal of > aggregation. The basis of these criteria is that it is primarily the > organizations acting as transit providers or exchange points that will be > involved in the top-level routing hierarchy and that other Service > Providers should receive NLA address space from these organizations. > > 4.2.1 General Criteria for Initial Sub-TLA Allocation > > Subject to sections 4.2.2, and 4.2.3, Regional IRs will only make an > initial allocation of sub-TLA address space to organizations that meet > criterion (a) AND at least one part of criterion (b), as follows: > > a. The requesting organization's IPv6 network must have exterior routing > protocol peering relationships with the IPv6 networks of at least three > other organizations that have a sub-TLA allocated to them. > > AND either > > b(i). The requesting organization must have reassigned IPv6 addresses > received from its upstream provider or providers to 40 SLA customer sites > with routed networks connected by permanent or semi-permanent links. > > OR > > b(ii). The requesting organization must demonstrate a clear intent to > provide IPv6 service within 12 months after receiving allocated address > space. This must be substantiated by such documents as an engineering plan > or deployment plan. > > 4.2.2 Criteria for sub-TLA Allocations in Transitional "Bootstrap" Phase > > By requiring exterior routing protocol peering relationships with at least > three other IPv6 networks, section 4.2.1 creates a problem during the > initial period of transition to IPv6 network addressing, namely that too > few organizations will meet the general criteria during this phase > (referred to as the "bootstrap phase"). The criteria in this section > provide an interim mechanism for eligibility that will only apply during > the bootstrap phase, that is until the number of organizations operating > IPv6 networks is considered sufficient for the general criteria to operate. > (See section 4.2.2.1 "Duration of Bootstrap Phase".) > > Notwithstanding section 4.2.1, during the bootstrap phase, Regional IRs > will make an initial allocation of sub-TLA address space to organizations > that meet criterion (a) AND criterion (b) AND either criterion (c) OR > criterion (d). > > a. The requesting organization's network must have exterior routing > protocol peering relationships with at least three other public Autonomous > Systems in the default-free zone. > > AND > > b. The requesting organization must show that it plans to provide > production IPv6 service within 12 months after receiving allocated address > space. This must be substantiated by such documents as an engineering plan > or a deployment plan. > > AND either > > c. The requesting organization must be an IPv4 transit provider and must > show that it already has issued IPv4 address space to 40 customer sites > that can meet the criteria for a /48 IPv6 assignment. In this case, the > organization must have an up-to-date routing policy registered in one of > the databases of the Internet Routing Registry, which the Regional IR may > verify by checking the routing table information on one of the public > looking glass sites). > > OR d. The requesting organization must demonstrate that it has experience > with IPv6 through active participation in the 6bone project for at least > six months, during which time it operated a pseudo-TLA (pTLA) for at least > three months. The Regional IRs may require documentation of acceptable > 6Bone routing policies and practice from the requesting organization. > > 4.2.2.1 Duration of Bootstrap Phase > > The eligibility criteria in this section will only apply until 100 > requesting organizations have received allocations of sub-TLA address > space, provided that no more than 60 of these organizations are located in > one Regional IR's region. After this threshold has been reached, the > bootstrap phase will be considered to be over and Regional IRs will only > make allocations to organizations that meet the general criteria in section > 4.2.1. > > If 60 organizations have been allocated sub-TLAs within one region (but > less than 100 have been allocated worldwide) then the bootstrap phase > within that region will be considered to be over. Additional applications > from that region must satisfy the general criteria in section 4.2.1, while > applications from other regions need only satisfy the bootstrap criteria. > > When 100 sub-TLA registries are formed worldwide, there will be enough > choices for new prospective sub-TLAs to find others to connect to and the > bootstrap phase can end. The regional limitation on bootstrapping is > intended to prevent one region consuming all available bootstrap > opportunities before IPv6 deployment has started in other regions. > > 4.2.3 Special considerations > > 4.2.3.1 Exchange Points > > It is expected that some exchange points will play a new role in IPv6, by > acting as a sub-TLA registry for ISPs that connect to the exchange point. > Because there is little information available about such exchange points > and how they will operate, they have not been considered during development > of sub-TLA eligibility criteria. As these exchange points are established, > the Regional IRs will evaluate whether special criteria are required. It is > expected that the Regional IRs will request from the exchange point > information about the nature of the contracts they enter with the ISPs > seeking IPv6 service. > > 4.2.3.2 Multihomed Sites > > [to be written] > > 4.2.4 Size for Initial Allocation: "Slow-Start" Mechanism > > Regional IRs will adopt a "slow start" mechanism when making initial > allocations of sub-TLA space to eligible organizations. By this mechanism, > the initial allocation will allow 13 bits worth of NLA IDs to be used by > the organization unless the requesting organization submits documentation > to the Regional IR to justify an exception based on topological grounds. > This initial allocation allows the organization to create a hierarchy > within the allocation depending on their customer type (ISP or end-site) > and the topology of their own network. For example, an organization may > receive 8,192 SLAs (a /48 each). (See section 4.3 for policies relating to > assignments.) > > The slow-start mechanism for sub-TLA allocations is important to the > development of IPv6 addressing hierarchies for several reasons. One > significant reason is that it allows the Regional IRs to set relatively low > entrance criteria for organizations seeking a sub-TLA allocation. This > makes the process fair to all organizations requesting sub-TLA space by > giving everybody the same (relatively small) amount and basing future > allocations on track record. Furthermore, the effect of this process will > be to create a range of different prefix lengths which, in the event that > routing table growth requires it, will allow the ISP industry to make > rational decisions about which routes to filter. > > Another important reason for adopting the slow-start mechanism is to allow > Regional IRs to maintain contact with TLA Registries as they develop, > thereby providing a level of support and training that will help ensure > that policies and practices are implemented consistently. Without a slow > start mechanism, TLA Registries receiving large initial allocations may not > have formal contact with the Regional IR for several years. The slow-start > mechanism helps Regional IRs to meet the goals of registration and > efficiency, by providing a process that enables them to monitor whether the > TLA Registries are properly registering assignments in the database and > correctly applying the policies for NLA and SLA assignments contained in > this document. > > 4.2.5 Criteria for Subsequent Sub-TLA Allocations > > Regional IRs will not make subsequent allocations of sub-TLA address space > to a TLA Registry unless the TLA Registry has used at least 80 percent of > its previously allocated address space. In this context, address space is > considered to be "used" if the TLA Registry has made all of its allocations > and assignments of that address space to its own infrastructure or customer > needs in accordance with the policies and guidelines specified in this > document. > > The size of subsequent allocations depend on the demonstrated usage rate of > the previous allocations. > > 4.2.5.1 Contiguous allocations > > The subsequent allocation will be contiguous with the previously allocated > range to allow for aggregation of routing information. When a Regional IR > makes an initial allocation to TLA Registry, it will reserve the full > sub-TLA from which this allocation was made. Subsequent allocations to that > TLA Registry will be made from the reserved sub-TLA. If no further growth > is possible within that sub-TLA range, the Regional IR may allocate a full > TLA. (Note, this practice may eventually lead to a situation in which no > empty sub-TLAs are available, but the existing sub-TLAs are not fully > utilised. If this occurs, then the provisions of section 4.4 will apply.) > > 4.2.6 Registering and Verifying Usage > > Each TLA Registry is responsible for the usage of the sub-TLA address space > it receives and must register all end-site assignments and ISP allocations > in the database of the Regional IR in its region. The Regional IR may > verify whether all assignments are registered in the database. In addition > to the database entries, the Regional IR may ask for periodic reports > specifying how the addresses are being used. > > Registered end-sites must be connected and reachable. To verify this, the > relevant Regional IR is entitled to ping /48s within end-sites. Filtering > holes should be negotiated by the Regional IR and the organization holding > the addresses in question. Therefore, it is suggested that end-sites use > anycast cluster addresses on their border routers to enable this. It is > expected that one /48 SLA block is enough address space per end-site. If an > end-site requests an additional SLA, the TLA Registry must send the request > to the Regional IR for a second opinion. > > 4.2.7 Renumbering > > It is possible that circumstances could arise whereby sub-TLA address space > becomes scarce. This could occur, for example, due to inefficient use of > assigned address space, or to an increase in the number of organizations > holding both TLA and sub-TLA space. > > If such circumstances arise, it may be necessary for Regional IRs to > require that previously allocated address space be renumbered into > different ranges. > > If a Regional IR requires a TLA Registry to renumber its own network, this > will also have an impact on all of its customers' networks. Therefore, it > is recommended that TLA Registries and NLA Registries enter contractual > arrangements with their customers at the time of the first allocation or > assignment. Such arrangements should clarify that the address space might > have to be returned, requiring all end-sites to be renumbered. If > renumbering is required, then TLA Registries should inform their customers > as soon as possible. > > Regional IRs requiring a TLA Registry to renumber will allow that Registry > at least 12 months to return the sub-TLA space. [Note that the granted > renumbering time may depend on the prefix length returned. The draft > document > > describes the issues involved in and methods used for renumbering IPv6 > networks.] > > [Note that site-local addresses are not affected by renumbering the global > unicast IPv6 addresses.] > > 4.2.8 Allocations to NLA Registries > > TLA Registries with ISP customers may use their 13 bits of NLA address > space to create an addressing hierarchy for those ISPs. Each of the TLA > Registry's own end-user organizations would receive a /48 (see section > 4.3); however, the ISP customers (NLA Registries) could be "allocated" > additional bits in order to aggregate the ISP's customers internally. A > slow-start mechanism will be used for these NLA allocations. > > The NLA block is an allocation to the NLA Registry and not an assignment. > If the NLA Registry does not sufficiently use it within a reasonable time, > the TLA Registry may require it to be returned. Definitions of 'sufficient > use' and 'reasonable time' will be provided in a future version of this > policy document. These definitions will be influenced by IPv6 operational > experience and determined by the Regional IR's with the consensus of the > Internet registry and engineering communities. > > Once an NLA Registry has assigned at least 80 percent of its allocation, it > may request an additional block from the TLA Registry. This block can be > any size, depending on the NLA Registry's usage rate for its first block. A > TLA Registry receiving a request for subsequent NLA allocations must submit > the request to the relevant Regional IR for a second opinion. > > Each NLA allocation must be registered in the Regional IR's database. All > end-user assignments must also be registered in the Regional IR's database. > The same procedures for these end-user assignments apply for the end-user > assignments made by the TLA Registry to their customers directly. > Ultimately, the TLA Registry is responsible for management of all address > space it allocates and should, therefore, appropriately monitor all > assignments made by the NLA Registries to which it allocates. The Regional > IR can at any time ask for additional information about the allocations and > assignments being made. > > 4.3 Assignments > > 4.3.1 Assignments to End-users > > The minimum assignment to end-user organizations that have a need to create > subnets in their network is a /48 (80 bits of address space). Within this > /48, 16 bits are an SLA block used for subnetting and further 64 bits are > used per interface. > > TLA Registries must submit all requests they receive for additional > assignments to the relevant Regional IR for evaluation (a "second > opinion"). All such requests must document the full use of the initial SLA > and must be accompanied by an engineering plan justifying the need for > additional address space. > > Dial-up lines are considered part of an ISP's infrastructure and, > therefore, addresses for such purposes should be assigned from the SLA > block of that ISP. It is expected that longer prefixes be used for > non-permanent, single-user connections. > > 4.4 Reclamation Methods/Conditions > > Allocations are valid only as long as the organizations holding the address > space continue to meet the criteria for allocations set out in sections > 4.2.1, 4.2.2, and other criteria which may be specified subject to the > provisions of this section. Consistent with the goal of aggregation > described in section 2.2.2, the criteria for allocations may be reviewed > with regard to current routing technology. The current threshold point for > reviewing the allocation criteria is 4096 default-free entries in the > global routing table. > > If this threshold is reached and current routing technology then allows > additional route entries, the number of possible TLAs and sub-TLAs may be > increased accordingly. > > However, if the limit is reached and routing technology at that time is not > able to support additional routing entries, Regional IRs will review all > allocations made up to that point. In the course of this review, the > Regional IRs may seek consensus of the Internet registry and engineering > communities to set minimum acceptable usage rates or new criteria > determining eligibility to hold sub-TLA space. Dependent upon such a > consensus, the Regional IRs may revoke the sub-TLA allocations of any > Registry not complying with those rates or criteria. Such Registries will > be required by the relevant Regional IR to renumber their networks and > return their previous allocation within a reasonable time. > > During the period that routing technology is being investigated, the > Regional IRs will continue allocating address space even if the number of > "possible" routes are reached. > > 5. ORGANIZATIONS OPERATING IN MORE THAN ONE REGION > > Organizations requesting sub-TLA space that operate in more than one > region, and that need separate sub-TLA blocks for routing purposes, may > request the address space from more than one of the Regional IRs, provided > that the organization's networks meet the criteria for allocation of > sub-TLA address space in each of the relevant regions. > > 6. DNS AND REVERSE ADDRESS MAPPING > > [To be written..] > > 7. GLOSSARY > > Allocation - The provision of IP address space to ISPs that reassign their > address space to customers. > > Assignment - The provision of IP address space to end-user organizations. > > Default-free zone - The default-free zone is made up of Internet routers > which have explicit routing information about the rest of the Internet and, > therefore, do not need to use a default route. > > End-user - An organization receiving reassignments of IPv6 addresses > exclusively for use in operational networks. > > Exterior routing protocol peering relationships - Routing relationships in > which the organisations receive the full Internet routing table separately > from neighbouring Autonomous Systems and are, therefore, able to use that > routing table to make informed decisions about where to send IP packets. > > Interface Identifiers - A 64-bit IPv6 unicast address identifier that > identifies an interface on a link. > > NLA ID - Next-Level Aggregation Identifier. > > NLA Registry - Internet Service Providers receiving IPv6 address > allocations from a TLA Registry. > > Public Topology - The collection of providers and exchanges who provide > public Internet transit service. > > Regional Internet Registries - Organizations operating in large > geographical regions such as continents which are responsible for fair > distribution of globally unique Internet address space and for documenting > address space allocation and assignment. > > Site - A location, physical or virtual, with a network backbone connecting > various network equipment and systems together. There is no limit to the > physical size or scope of a site. > > Site Topology - A local, specific site or organization which does not > provide public transit service to nodes outside the site. > > SLA ID - Site-Level Aggregation Identifier. > > Slow Start - The efficient means by which addresses are allocated to TLA > Registries and to NLA ISPs. This method involves issuing small address > blocks until the provider can show an immediate requirement for larger > blocks. > > TLA ID - Top-Level Aggregation Identifier. > > TLA Registry - Organizations receiving TLA/sub-TLA ID from Regional IRs to > reassign to customers. > > Unicast - An identifier for a single interface. A packet sent to a unicast > address is delivered to the interface identified by that address. Note that > the definition of an IPv4 host is different from an IPv6 identifier. One > physical host may have many interfaces, and therefore many IPv6 > identifiers. > > 8. LIST OF REFERENCES > > ------ =_NextPart_000_01BEA929.E5CD8FC0-- > > > > -- "When in doubt, Twirl..." -anon From bmanning@ISI.EDU Fri May 28 18:14:29 1999 From: bmanning@ISI.EDU (bmanning@ISI.EDU) Date: Fri, 28 May 1999 10:14:29 -0700 (PDT) Subject: BOUNCE 6bone@zephyipv6 delegation plan commetns Message-ID: <199905281714.AB07153@zed.isi.edu> > Subject: Re: v6 message to IANA - followup > To: 6bone@ISI.EDU > Date: Fri, 28 May 1999 09:31:11 -0700 (PDT) > > > PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT > > (28 May 1999) > > Scheduled revision: Formal revision of this document is scheduled to be > > commenced by 1 October 1999. > > > .... > > Prefix boundaries (starting at bit 0) > > > > number of the number of the ID > > left-most right-most longest length > > bit bit prefix (in bits) > > ************ ************ ******* ******** > > TLA ID 3 15 /16 13 > > sub-TLA ID 16 28 /29 13 > > Reserved 29 34 > > NLA ID 35 47 /48 13 > > SLA ID 48 63 /64 16 > > > > For purposes of a "slow start" of a sub-TLA, the first allocation to a TLA > > Registry will be a /35 block (representing 13 bits of NLA space). The > > Regional IR making the allocation will reserve an additional six bits for > > the allocated sub-TLA. When the TLA Registry has fully used the first /35 > > block, the Regional IR will use the reserved space to make subsequent > > allocations (see section 4.2.5). > > This will pose a problem with most all existing DNS code. DNS code > tends to follow octect or nibble alignment. Bit alignment is proposed > but not developed. Widescale deployment is not expected within the > next 18 months. Use of this delegation framework will inhibit the use > of DNS with IPv6. (see the recent 6bone discussion on subTLA assingment > policy. 05may1999 posting from Bob Fink)). > > > > 4.2.6 Registering and Verifying Usage > > > > Each TLA Registry is responsible for the usage of the sub-TLA address space > > it receives and must register all end-site assignments and ISP allocations > > in the database of the Regional IR in its region. > > So a distributed service aka, rwhois or DNS is not acceptable > as a registration service? To me, this insistence on centralized > databases will be a significant hurdle in growing the Internet > two more orders of magnitude. > > > Registered end-sites must be connected and reachable. To verify this, the > > relevant Regional IR is entitled to ping /48s within end-sites. > > Again, this indicates a lack of vision for future Internet > developments. There is significant developmental work being > done for loosely coupled networks, e.g. networks that are > only "attached" to the rest of the Internet sporadically. > > > 6. DNS AND REVERSE ADDRESS MAPPING > > > > [To be written..] > > > See my comments above on why 13 bits are wrong. > > > While I don't expect my comments to be persuasive to the RIR juggernaut, > I feel they should be heard. If others feel they are relevent, then > perhaps they can try and persuade these folks that they are promoting > seriously flawed policies. > > --bill > -- "When in doubt, Twirl..." -anon From richdr@microsoft.com Sun May 30 23:28:10 1999 From: richdr@microsoft.com (Richard Draves) Date: Sun, 30 May 1999 15:28:10 -0700 Subject: 6bone problems Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145151B0@RED-MSG-50> In the last several days the BGP traffic has skyrocketed... does anybody know what's up? -----Original Message----- From: owner-6bone-routing-report@merit.edu [mailto:owner-6bone-routing-report@merit.edu] Sent: Saturday, May 29, 1999 11:18 PM To: 6bone-routing-report@merit.edu Subject: 05/29/99 6Bone Routing Report See http://www.merit.edu/ipma for a more detailed report on routing problems and recommendations on ways service providers can limit the spread of invalid routing information. Send comments and questions to ipma-support@merit.edu To unsubscribe from this list, send mail to 6bone-routing-report-request@merit.edu. A hypermail archive is available at http://www.merit.net/mail.archives/html/6bone-routing-report/ Also see http://www.caida.org for more information about Internet statistics collection research efforts. --------------------------------------------- This report is for 05/29/99, peering with VIAGENIE (AS10566) CISCO (AS109) IDIR (AS11264) CICNET (AS1225) MERIT (AS237) WIDE (AS2500) ETRI (AS3559) EWD-3COM (AS561) UUNET-US (AS704) CAIRN (AS7081) NUS-IRDU (AS7610) --------------------------------------------- Size of 6Bone Routing Table: Max = 179, Min = 177, Average = 177 59 Unique Autonomous System (AS) numbers BGP4+ Traffic Summary: Announcements = 569211 Withdraws = 200295 Unique Routes = 70 Non-6Bone Prefixes (outside of 3ffe::/16): -------------------------------- 0000::/0 path 1225 48 1752 5408 559 137 1275 (JOIN) 1800::/4 path 1225 48 1752 5408 559 137 1275 (JOIN) 5f01:7800::/32 path 1225 (CICNET) 5f0b:4f00::/32 path 109 2895 (INR) 5f0d:e900:ce9c:9400::/64 path 1225 (CICNET) Poorly Aggregated Prefixes (>24): -------------------------------- VIAGENIE (3ffe:b00::/24) had 5 route(s) 3ffe:b00:c18:2::2/127 path 7081 6509 10566 (VIAGENIE) 3ffe:b00:c18::b/127 path 7081 6509 10566 (VIAGENIE) 3ffe:b00:800:1::/64 path 7081 6509 10566 (VIAGENIE) 3ffe:b00:c18:2::/64 path 7081 6509 10566 (VIAGENIE) 3ffe:b00:c18::/48 path 7081 6509 10566 (VIAGENIE) UUNET-UK (3ffe:1100::/24) had 2 route(s) 3ffe:1108:40a::/48 path 1225 1275 8319 5539 (SPACENET-DE) 3ffe:1108:1400::/40 path 704 (UUNET-US) CICNET (3ffe:900::/24) had 2 route(s) 3ffe:900:1::/48 path 1225 1312 (LORE/VT) 3ffe:900:2::/48 path 1225 3899 (CHICO) SMS (3ffe:2600::/24) had 2 route(s) 3ffe:2610:2::/48 path 1225 1103 3274 8432 (TF-INET-DEV) 3ffe:2620::/32 path 1225 1103 3274 1741 (FUNET/OTOL) VBNS (3ffe:2800::/24) had 1 route(s) 3ffe:2802::/32 path 1225 1312 (LORE/VT) SPRINT (3ffe:2900::/24) had 1 route(s) 3ffe:2900:5::/48 path 1225 1312 (LORE/VT) SWITCH (3ffe:2000::/24) had 1 route(s) 3ffe:202a:1::/64 path 1225 1275 559 1836 (SIMULTAN) JANET (3ffe:2100::/24) had 1 route(s) 3ffe:2101::/48 path 1225 48 1752 3185 (ULANC) MERIT (3ffe:1c00::/24) had 1 route(s) 3ffe:1cee::/48 path 11264 (IDIR) INFN-CNAF (3ffe:2300::/24) had 1 route(s) 3ffe:23f0::/28 path 1225 1275 559 137 8253 (DUTHNET) UNI-C (3ffe:1400::/24) had 1 route(s) 3ffe:1402:1:1::/64 path 7610 1849 5539 1273 (ECRC) GRNET (3ffe:2d00::/24) had 1 route(s) 3ffe:2d00:3::/48 path 1225 1849 1752 5408 8643 (UOA) INR (3ffe:2400::/24) had 1 route(s) 3ffe:2401::/32 path 109 2895 2118 (STC-IPNG) JOIN (3ffe:400::/24) had 1 route(s) 3ffe:400:1c0::/48 path 1225 48 8319 (REGIO-DE) The Top Five Most Active Prefixes: ---------------------------------- 1. (1800::/4) had 215895 BGP+ updates (10 unique aspaths) 237 1225 2547 559 137 1275 (33095) 237 1225 48 1752 5408 559 137 1275 (21866) 1225 2547 559 137 1275 (14764) 237 1225 48 3251 1930 559 137 1275 (14578) 1225 48 1752 5408 559 137 1275 (9734) 1225 48 3251 1930 559 137 1275 (6491) 237 1225 33 5609 48 (2131) 237 1225 48 1752 3185 786 2547 2547 559 137 1275 (1067) 1225 33 5609 48 (948) 1225 48 1752 3185 786 2547 2547 559 137 1275 (476) 2. (0000::/0) had 177374 BGP+ updates (10 unique aspaths) 237 1225 2547 559 137 1275 (26850) 237 1225 48 1752 5408 559 137 1275 (21442) 1225 2547 559 137 1275 (11978) 237 1225 48 3251 1930 559 137 1275 (10743) 1225 48 1752 5408 559 137 1275 (9554) 1225 48 3251 1930 559 137 1275 (4790) 237 1225 33 5609 48 (2131) 1225 33 5609 48 (948) 237 1225 48 1752 3185 786 2547 2547 559 137 1275 (476) 1225 48 1752 3185 786 2547 2547 559 137 1275 (212) 3. SIMULTAN (3ffe:202a:1::/64) had 95756 BGP+ updates (9 unique aspaths) 237 1225 1275 559 1836 (26636) 237 1225 2547 559 1836 (26636) 10566 10566 10566 10566 1930 559 1836 (18440) 1225 2547 559 1836 (12051) 1225 1275 559 1836 (11855) 10566 10566 10566 10566 3462 3263 1275 559 1836 (78) 237 109 1225 1275 559 1836 (8) 109 1225 1275 559 1836 (3) 561 5609 1225 1275 559 1836 (1) 4. SWISSCOM (3ffe:1e00::/24) had 93998 BGP+ updates (11 unique aspaths) 237 1225 2547 559 3303 (27248) 237 1225 1275 559 3303 (27221) 10566 10566 10566 10566 1930 559 3303 (14918) 1225 2547 559 3303 (12302) 1225 1275 559 3303 (12113) 10566 10566 10566 10566 6175 137 559 3303 (153) 2500 33 1849 5623 559 3303 (13) 237 109 5409 559 3303 (9) 109 5409 559 3303 (3) 561 5609 1225 1275 559 3303 (1) 561 6175 137 559 3303 (1) 5. SWITCH (3ffe:2000::/24) had 92010 BGP+ updates (11 unique aspaths) 237 1225 2547 559 (26636) 237 1225 1275 559 (26609) 10566 10566 10566 10566 1930 559 (14676) 1225 2547 559 (12051) 1225 1275 559 (11841) 10566 10566 10566 10566 6175 137 559 (153) 2500 33 1849 5409 559 (13) 237 109 5409 559 (9) 109 5409 559 (3) 561 5609 1225 1275 559 (1) 561 6175 137 559 (1) From fink@es.net Mon May 31 02:19:03 1999 From: fink@es.net (Bob Fink) Date: Sun, 30 May 1999 18:19:03 -0700 Subject: 6bone problems In-Reply-To: <4D0A23B3F74DD111ACCD00805F31D810145151B0@RED-MSG-50> Message-ID: <4.1.19990530181637.00aa2e30@imap2.es.net> Rich, At 03:28 PM 5/30/99 -0700, Richard Draves wrote: >In the last several days the BGP traffic has skyrocketed... does anybody >know what's up? Rob Rockell had speculated to me that it looked as if someone was not filtering their downstreams, and one of their leaf-nodes descided to advertise default. He was looking into it, but also noted that he didn't see it in his (Sprint's) routing table due to his agressive filtering (one of those things we hope to harden on the 6bone!). Maybe Rob can comment (I've cc'd him here). Bob From hansolofalcon@worldnet.att.net Mon May 31 04:42:08 1999 From: hansolofalcon@worldnet.att.net (Gregg C Levine) Date: Sun, 30 May 1999 23:42:08 -0400 Subject: 6bone problems Message-ID: <01BEAAF6.B7900BA0.hansolofalcon@worldnet.att.net> ------ =_NextPart_000_01BEAAF6.B7A875A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello from Gregg Levine usually at Jedi Knight Computers I have not been paying, my usual amounts of attention to the traffic, but I would hazard a guess that more people are testing their installed setups. Its just a guess though. Gregg C Levine mailto:hansolofalcon@worldnet.att.net This signature supports the Alliance to restore the Republic "They were in the wrong place at the wrong time. Naturally they became heroes" Princess Leia Organa of Alderaan, Senator "The Force will be with you." General Obi-Wan Kenobi Jedi Knight, Retired On Sunday, May 30, 1999 6:28 PM, Richard Draves [SMTP:richdr@microsoft.com] wrote: | In the last several days the BGP traffic has skyrocketed... does anybody | know what's up? | | -----Original Message----- | From: owner-6bone-routing-report@merit.edu | [mailto:owner-6bone-routing-report@merit.edu] | Sent: Saturday, May 29, 1999 11:18 PM | To: 6bone-routing-report@merit.edu | Subject: 05/29/99 6Bone Routing Report | | | See http://www.merit.edu/ipma for a more detailed report on routing | problems and recommendations on ways service providers can limit the | spread of invalid routing information. | Send comments and questions to ipma-support@merit.edu | | To unsubscribe from this list, send mail to | 6bone-routing-report-request@merit.edu. | A hypermail archive is available at | http://www.merit.net/mail.archives/html/6bone-routing-report/ | | Also see http://www.caida.org for more information about Internet | statistics collection research efforts. | | --------------------------------------------- | This report is for 05/29/99, peering with | VIAGENIE (AS10566) CISCO (AS109) IDIR (AS11264) CICNET (AS1225) MERIT | (AS237) WIDE (AS2500) ETRI (AS3559) EWD-3COM (AS561) UUNET-US (AS704) | CAIRN (AS7081) NUS-IRDU (AS7610) | --------------------------------------------- | | Size of 6Bone Routing Table: | Max = 179, Min = 177, Average = 177 | 59 Unique Autonomous System (AS) numbers | | BGP4+ Traffic Summary: | Announcements = 569211 Withdraws = 200295 Unique Routes = 70 | | Non-6Bone Prefixes (outside of 3ffe::/16): | -------------------------------- | 0000::/0 path 1225 48 1752 5408 559 137 1275 (JOIN) | 1800::/4 path 1225 48 1752 5408 559 137 1275 (JOIN) | 5f01:7800::/32 path 1225 (CICNET) | 5f0b:4f00::/32 path 109 2895 (INR) | 5f0d:e900:ce9c:9400::/64 path 1225 (CICNET) | | Poorly Aggregated Prefixes (>24): | -------------------------------- | VIAGENIE (3ffe:b00::/24) had 5 route(s) | 3ffe:b00:c18:2::2/127 path 7081 6509 10566 (VIAGENIE) | 3ffe:b00:c18::b/127 path 7081 6509 10566 (VIAGENIE) | 3ffe:b00:800:1::/64 path 7081 6509 10566 (VIAGENIE) | 3ffe:b00:c18:2::/64 path 7081 6509 10566 (VIAGENIE) | 3ffe:b00:c18::/48 path 7081 6509 10566 (VIAGENIE) | | UUNET-UK (3ffe:1100::/24) had 2 route(s) | 3ffe:1108:40a::/48 path 1225 1275 8319 5539 (SPACENET-DE) | 3ffe:1108:1400::/40 path 704 (UUNET-US) | | CICNET (3ffe:900::/24) had 2 route(s) | 3ffe:900:1::/48 path 1225 1312 (LORE/VT) | 3ffe:900:2::/48 path 1225 3899 (CHICO) | | SMS (3ffe:2600::/24) had 2 route(s) | 3ffe:2610:2::/48 path 1225 1103 3274 8432 (TF-INET-DEV) | 3ffe:2620::/32 path 1225 1103 3274 1741 (FUNET/OTOL) | | VBNS (3ffe:2800::/24) had 1 route(s) | 3ffe:2802::/32 path 1225 1312 (LORE/VT) | | SPRINT (3ffe:2900::/24) had 1 route(s) | 3ffe:2900:5::/48 path 1225 1312 (LORE/VT) | | SWITCH (3ffe:2000::/24) had 1 route(s) | 3ffe:202a:1::/64 path 1225 1275 559 1836 (SIMULTAN) | | JANET (3ffe:2100::/24) had 1 route(s) | 3ffe:2101::/48 path 1225 48 1752 3185 (ULANC) | | MERIT (3ffe:1c00::/24) had 1 route(s) | 3ffe:1cee::/48 path 11264 (IDIR) | | INFN-CNAF (3ffe:2300::/24) had 1 route(s) | 3ffe:23f0::/28 path 1225 1275 559 137 8253 (DUTHNET) | | UNI-C (3ffe:1400::/24) had 1 route(s) | 3ffe:1402:1:1::/64 path 7610 1849 5539 1273 (ECRC) | | GRNET (3ffe:2d00::/24) had 1 route(s) | 3ffe:2d00:3::/48 path 1225 1849 1752 5408 8643 (UOA) | | INR (3ffe:2400::/24) had 1 route(s) | 3ffe:2401::/32 path 109 2895 2118 (STC-IPNG) | | JOIN (3ffe:400::/24) had 1 route(s) | 3ffe:400:1c0::/48 path 1225 48 8319 (REGIO-DE) | | The Top Five Most Active Prefixes: | ---------------------------------- | 1. (1800::/4) had 215895 BGP+ updates (10 unique aspaths) | 237 1225 2547 559 137 1275 (33095) | 237 1225 48 1752 5408 559 137 1275 (21866) | 1225 2547 559 137 1275 (14764) | 237 1225 48 3251 1930 559 137 1275 (14578) | 1225 48 1752 5408 559 137 1275 (9734) | 1225 48 3251 1930 559 137 1275 (6491) | 237 1225 33 5609 48 (2131) | 237 1225 48 1752 3185 786 2547 2547 559 137 1275 (1067) | 1225 33 5609 48 (948) | 1225 48 1752 3185 786 2547 2547 559 137 1275 (476) | | 2. (0000::/0) had 177374 BGP+ updates (10 unique aspaths) | 237 1225 2547 559 137 1275 (26850) | 237 1225 48 1752 5408 559 137 1275 (21442) | 1225 2547 559 137 1275 (11978) | 237 1225 48 3251 1930 559 137 1275 (10743) | 1225 48 1752 5408 559 137 1275 (9554) | 1225 48 3251 1930 559 137 1275 (4790) | 237 1225 33 5609 48 (2131) | 1225 33 5609 48 (948) | 237 1225 48 1752 3185 786 2547 2547 559 137 1275 (476) | 1225 48 1752 3185 786 2547 2547 559 137 1275 (212) | | 3. SIMULTAN (3ffe:202a:1::/64) had 95756 BGP+ updates (9 unique aspaths) | 237 1225 1275 559 1836 (26636) | 237 1225 2547 559 1836 (26636) | 10566 10566 10566 10566 1930 559 1836 (18440) | 1225 2547 559 1836 (12051) | 1225 1275 559 1836 (11855) | 10566 10566 10566 10566 3462 3263 1275 559 1836 (78) | 237 109 1225 1275 559 1836 (8) | 109 1225 1275 559 1836 (3) | 561 5609 1225 1275 559 1836 (1) | | 4. SWISSCOM (3ffe:1e00::/24) had 93998 BGP+ updates (11 unique aspaths) | 237 1225 2547 559 3303 (27248) | 237 1225 1275 559 3303 (27221) | 10566 10566 10566 10566 1930 559 3303 (14918) | 1225 2547 559 3303 (12302) | 1225 1275 559 3303 (12113) | 10566 10566 10566 10566 6175 137 559 3303 (153) | 2500 33 1849 5623 559 3303 (13) | 237 109 5409 559 3303 (9) | 109 5409 559 3303 (3) | 561 5609 1225 1275 559 3303 (1) | 561 6175 137 559 3303 (1) | | 5. SWITCH (3ffe:2000::/24) had 92010 BGP+ updates (11 unique aspaths) | 237 1225 2547 559 (26636) | 237 1225 1275 559 (26609) | 10566 10566 10566 10566 1930 559 (14676) | 1225 2547 559 (12051) | 1225 1275 559 (11841) | 10566 10566 10566 10566 6175 137 559 (153) | 2500 33 1849 5409 559 (13) | 237 109 5409 559 (9) | 109 5409 559 (3) | 561 5609 1225 1275 559 (1) | 561 6175 137 559 (1) | ------ =_NextPart_000_01BEAAF6.B7A875A0 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IgQDAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEkAYAJAMAAAIAAAARAAAAAwAAMAMAAAAL AA8OAQAAAAIB/w8BAAAAQQAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAABAFJpY2hhcmQgRHJhdmVz AFNNVFAAcmljaGRyQG1pY3Jvc29mdC5jb20AAAAAHgACMAEAAAAFAAAAU01UUAAAAAAeAAMwAQAA ABUAAAByaWNoZHJAbWljcm9zb2Z0LmNvbQAAAAADABUMAQAAAAMA/g8GAAAAHgABMAEAAAARAAAA J1JpY2hhcmQgRHJhdmVzJwAAAAACAQswAQAAABoAAABTTVRQOlJJQ0hEUkBNSUNST1NPRlQuQ09N AAAAAwAAOQAAAAALAEA6AAAAAAMAcToAAAAAHgD2XwEAAAAPAAAAUmljaGFyZCBEcmF2ZXMAAAIB 918BAAAAQQAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAABAFJpY2hhcmQgRHJhdmVzAFNNVFAAcmlj aGRyQG1pY3Jvc29mdC5jb20AAAAAAwD9XwEAAAADAP9fAAAAAAIB9g8BAAAABAAAAAAAAAMQAAAA AwAAMAQAAAALAA8OAAAAAAIB/w8BAAAAZQAAAAAAAAC1O8LALHcQGqG8CAArKlbCFQAAAO++p2H5 YdIRhkBERVNUAAEkgQAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAEANmJvbmVAaXNpLmVkdQBTTVRQ ADZib25lQGlzaS5lZHUAAAAAHgACMAEAAAAFAAAAU01UUAAAAAAeAAMwAQAAAA4AAAA2Ym9uZUBp c2kuZWR1AAAAAwAVDAEAAAADAP4PBgAAAB4AATABAAAAEAAAACc2Ym9uZUBpc2kuZWR1JwACAQsw AQAAABMAAABTTVRQOjZCT05FQElTSS5FRFUAAAMAADkAAAAACwBAOgEAAAAeAPZfAQAAAA4AAAA2 Ym9uZUBpc2kuZWR1AAAAAgH3XwEAAAAsAAAAvwAAALU7wsAsdxAaobwIACsqVsIVAAAA776nYflh 0hGGQERFU1QAASSBAAADAP1fAQAAAAMA/18AAAAAAgH2DwEAAAAEAAAAAAAABCudAQSAAQATAAAA UkU6IDZib25lIHByb2JsZW1zAE8GAQWAAwAOAAAAzwcFAB4AFwAqAAgAAABCAQEggAMADgAAAM8H BQAeABcAJgAcAAAAUgEBCYABACEAAAAwNDc0RjU4NDQ0RDg2ODQ5OUM2QzY4MjlDRDkxM0JDNwAj BwEDkAYAkA8AACIAAAALAAIAAQAAAAsAIwAAAAAAAwAmAAAAAAALACkAAAAAAAMALgAAAAAAAwA2 AAAAAABAADkA4KMejxervgEeAHAAAQAAABMAAABSRTogNmJvbmUgcHJvYmxlbXMAAAIBcQABAAAA FgAAAAG+qxeMd2yPhn+4hknevTBl4IzdTFoAAB4AHgwBAAAABQAAAFNNVFAAAAAAHgAfDAEAAAAf AAAAaGFuc29sb2ZhbGNvbkB3b3JsZG5ldC5hdHQubmV0AAADAAYQsQR1WAMABxCuEwAAHgAIEAEA AABlAAAASEVMTE9GUk9NR1JFR0dMRVZJTkVVU1VBTExZQVRKRURJS05JR0hUQ09NUFVURVJTSUhB VkVOT1RCRUVOUEFZSU5HLE1ZVVNVQUxBTU9VTlRTT0ZBVFRFTlRJT05UT1RIRVRSQQAAAAACAQkQ AQAAACcMAAAjDAAAhR0AAExaRnVJBS0sPwAKAQMB9wKkA2MCAGNowQrAc2V0MCAHbQKASn0KgXYI kHdrC4BkOjQMYGMAUAsDC2BuZxAxMDMzC6YgSGVKbAkAIANSIEcJcGcQZyBMZRFAbmUgCHVzdQdA bHkgYUUFQEoJgGkgSwMAZ4ZoBUAIUG1wdXQEkKZzCqIKgEkgD3B2FOBUbm8FQGIJ4SAKsHnhC4Bn LCBtFWAVAxVwzQRgdQIwBCBvZhVxFsAlAjBpAiAgdBPAdGiRFOB0cmEBIGljGMAqYhawIBdgdwhg bGTNF3F6CxEVcCBnClAEEZ8a8BWBBGAJcBhQZW8LUH8U4ArAGxEHkBpwEpAa4mlfBcALgB7gFTEJ gCAPoXXYcHMuG/AZwWoVAAVAvxz4CGAWMCCgFwQUNEMUhncAwAMQGsA6D3AAgAjxZtMHQAWgbkAc IHIcUBTQNHQuGiEuJUEXBFRo9wQAIDAWIG4VgAhwFOAVENxwcAkRHVIU4EEToAcw/G5jGxETwAlw HuAd0hryvFJlFqACYBuAFwQiJlB6ZRVgdwSQFOALgBrjd/8DYB8RC1EocRWBK1gacAeAfSCgTibi FTMa8RVgGBBjXxlwFOAbAANgB5AiFwRQHwUQKGEEERSQBzAgT3K+ZwBwHPAZ8SgQBIFhAHCfGMAG YCbRBbAqGCBGBbA/KHED8BOgGAEzQRrwIHl1CGAuL0VHCfAxYQMgT1BiaS1XA5FLCfBv/zVgFaoY wCmQGnAJcRcEFwRqTwOgUxmgZBhwGMBNkRhwIDMwGMAxOTmAACA2OjI4IFBN7zbxG4APcRxgRBtA F6AEIMBbU01UUDoFEA9g8GRyQG0bgANgJEABgLIuBaBtXSuCFsA6FwT+fBvwKzQLYCEhD6AXoDUS 4zihJ7RCR1AbJhdxJoFka3kDYGNrD7AJgC5PQWA/EC8RFXBueQbgZFp5PWZrF9AH4HcdgSfbBCAg cD89Zj1mLUTSMJAXFiALgBlBTR0xYWdlq0TTPWZGA2E6GeB3NPHsLTYG4BTQLQNgFrAYkf9IACmg CRE8AAZxJWAJgAxw/T11WyOlR19Ib0lwPOA9Zj0x0XRHMAYQJvE4pzI5YTlVMTE6MTnyPWZUvyPw ObBLD0jfTUIpwGoFkFFNoTA1L06wLzmSQv9QoQfxUQMpggkRQ95M+C7BQQJAcDovL3dXcC79Udcv BSAAwBPQBbEc8B3D/wEAAZADECARUWQZ4AOgUOXNREdwA2ACYGVtQdJZwr88sQeAOJEachnRA6B3 PzL9D6ByEUAocVuBEUAEgQQgvy6QA6AoMDwQLGQ9ZnNbgNxlYRxgGfELgHYHQF6Q31p3C4BYoQDA GnIuTPkcYPdcdBnBXBJxHSFc9BrBWFL+LSdFUc9ER1BAFPAAgCnA/wTyM6ET4xrwJnEoMB7gGMD/ D6BcISOiGrI9ZmqyUI8JEa9RUWRTZehip0EXcHkeEO9iMQMRCsAPYGkXoSZxF5B/I7EBoB5SVTdq slcPJUEvJyOiJXBuxHMvFkBtbPYvaw8JES9D3igQJEAgMedW6y6QXpBhLgWwFHBYov8dw2H5FXAG 4BvSAjAEkQ+w71/IAZAacB7hY17RBvAeUN9TMBqCKNFggG7BIAERJ4L/YqdEW34Pfx9/hE/HJmJZ 5f8mcViiU3YYwB4QBnEfETPSAWpIVklBR0VOSSBFIChBUxKwNTYENilqsENJU0NPhYTEOYVRSURJ UoTDEDEyNjSFU0NORSJUhMMyMjWFUU1FGFJJVD1mhNEyMzedhVFXhnCEs4gwMDCFUUeHsIighMIz NTWGMkXQV0QtM4WwTYTChSCSMYVRVVWHoS1VBfCZhNE3MIcwPWZDQYaQqk6NZDiMok6NQC2GkPxE VY1jjJCKkH1PkX+Sj3NGWEz3aXoU4BnxVAxUj2+yPVcMgjjheCA9OWBaN07BTSshl5I3GMBB/z7C RgCYNJaLi3CM0AMAZFH/KAAWsAIgA3AIYAZBP0AWwOcUEITRhVBudQbQFtdEOPk/sTQrD+BABThw XJAKwM55RzBVuJcSQW4X0BmgzyhwY7SXkIUgOTJPQGqyZlcz4TvgYXeg4gHQMP1OsDVqsZqFVGIH kZeQjaB9fM5OAiBK4FQTL7ABEGl6eAeRKFDxAJABABniM/cBID1AV0AxhUA9V5K/kt//amaKgIqA p2EP0AqwM/GIEkwgNDnwl7A1MppANPePAJpAmlExiZCrwaxghMDwSk9JTo3XarBPcKsT3jSrf6yP rZ9qsDUBME9Q2jeu1DOwUK9YKId0sex4Yjo0ATCzG4YgTqA4FaLBKK3wUrHsZDplhjmrEShwOWM6 ObCAn6sihyCzf7SIPWZQbyUBfRVgQRRgFEEVgCARpdg+fjKHMKfPvr+p74RIpyNiP6sTvYEXcRxg otBQ4mUo3nOuGWqwwYcR8Dg50Kdg/jKngLFQr0SO8jmwinBPIf+FEoTAhEbDT8RXwcDFL8Y//8dP wbSu0k9QuUjJv8rPx+//xOHNH84vzz/IaK8gOfDRT/fSX3z7jMdLwWVPQMHrsFDfwt/P1tkRxMCw gGHUua+jWbFDODM5cLCxMzmgKPBTUEFDhICNEYoA2p+926QxuQSwgNUGrzAojOb/1v+HWKcjuGLZ b9p/4+XM4gfcbN2QsFAoTE9SRbwvVrSK5jnQ0txrM7bQ6d4BQ0iHgE/iH2qwO1D/jVGnI4cQ5C/l P6cUhxASsD/qH08xEsA5ILFQrzA4NLGzUShURo+Q3oRW7z9f7aEB0LMu8biXsDShcCiCRozyL09U T0zr7/mEIUJO7Teu1MI2oXDuz7/v167Q0NL0/OgP7D1QiKB+TuOWTrD5b/p/7/W4YjXv8L/9P+w9 ieBU65DtRqsE9wBvAX8GsTLcIMzq3OiwwwPdgNZBU0lNVUxU9kGuCGpISgwQ44ehUAbvvwf/7/US sObvr/bdkDixcbsL4AwQQww/iGXYpmMOT/8PX9tVKHCnUtxnhwK3AYaBQxM/hlFORk4th5BB/kbt RjkwFV8WbxtFtVDCAlvcf7DGOIgw8eAoj8BU/ki6f9fUhJAa0NimuQQcD38dH+BCxOBPUdDqkDGu sTTH3bWxQSBxRUNSEy9qsfZHjpANmGQjLyQ/7/UqYm4zAv8nMrAoOIcgIHFV/E9BKG8acoah7WQj Hyt//+/msIDM4rYPoVE58N4gBiDxj5BQTkcv3w1BreHBZf8xvzLPz+W5AhUhEQ8vId2S4ijocEdJ T966gJim0M1ngHBG4G7yTW9kgHWgP3tRbwGl1r2/Qb+/vzEuzWqwKK7G7kUxNbbSndF/nhBlgFzR vTIm8WewmqNhv2BQEXE56omBr5SIMDSxIP2wzDMboKLAR3+vz7DboVD/L0CFQK4pSH+xROBQkCCN yHtKzLNQNaFw3aAboE6/Ne+y4E1+S3+xCDkn4E/qUO/7sL2HIDmMoFAP6xHx4IUg/7aRVDFNEd2Q WR8R3rLg1kD3TnNOf0ZCNomgTY1aWrjwv1MvXJ9dr7E1T7E9nzJD8v+q9jkFmHCJkK8wRY9Gn1uP +2O/TQE2EqCQWFvvVJ9M5Pg0NDJNf2sPRCDdoFMb71CvV69ogvYwM2Ffbc9VWP+LYFYfc39kSrhg cj9aL1s7/3xPYSxtL2LfY+9k+WHvgW/3TE5vqDoGM0PwC7YGVwmH/zkEosB2sNZAZ8yaYGjff7/7 Cs1sIDYLcIzPcIuOr66D/9YTkn952QtjJyF3AG+/kJz/BBDWEH2PCs010bDAkc+ab/0ScDT0kPHx jxAKvnIftoL/mC/WQWFLnp8LVHVqfMD2kG98w6EPlLKHTzSIYQYAU+pT68BN2KZlwet58OtQ/xhA Z832kIvvj3+F50nhIHH/sVC9gJ2Po6usJzXAmb+wD/952Kwk4FBY8GFPq50EEBug/2+vrh0EEDXQ dWuwf9YEJuD/H5EgArHZ3eCdmmxQ4NB8kf8nJPSQfKGx6LrLnlV28d2y/awGOaAdvp2iT6NfsgbB jfe5f6S/30E1pgMGL6eHBsD/JvGob6l/rQ+F55FvrY/NU/9KALdP0K952E+RX0CDf8zY/5cvzsw1 0faAz//Xr8T8up//u6q+pr0/wDy/f9u4wX/Cj1fD79kexk19JNAA5UAAAwAQEAAAAAADABEQAQAA AB4AQhABAAAANgAAADw0RDBBMjNCM0Y3NEREMTExQUNDRDAwODA1RjMxRDgxMDE0NTE1MUIwQFJF RC1NU0ctNTA+AAAAAwCAEP////9AAAcwgCydCxervgFAAAgwgCydCxervgELAACACCAGAAAAAADA AAAAAAAARgAAAAADhQAAAAAAAAMAAoAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAFgAgg BgAAAAAAwAAAAAAAAEYAAAAAUoUAAPMVAAAeACWACCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAA AAUAAAA4LjA0AAAAAAMAJoAIIAYAAAAAAMAAAAAAAABGAAAAAAGFAAAAAAAACwAvgAggBgAAAAAA wAAAAAAAAEYAAAAADoUAAAAAAAADADCACCAGAAAAAADAAAAAAAAARgAAAAARhQAAAAAAAAMAMoAI IAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAAHgBBgAggBgAAAAAAwAAAAAAAAEYAAAAANoUAAAEA AAABAAAAAAAAAB4AQoAIIAYAAAAAAMAAAAAAAABGAAAAADeFAAABAAAAAQAAAAAAAAAeAEOACCAG AAAAAADAAAAAAAAARgAAAAA4hQAAAQAAAAEAAAAAAAAAHgA9AAEAAAAFAAAAUkU6IAAAAAADAA00 /TcAAF2Z ------ =_NextPart_000_01BEAAF6.B7A875A0-- From rrockell@sprint.net Mon May 31 08:07:14 1999 From: rrockell@sprint.net (Robert Rockell) Date: Mon, 31 May 1999 03:07:14 -0400 (EDT) Subject: 6bone problems In-Reply-To: <4.1.19990530181637.00aa2e30@imap2.es.net> Message-ID: What are you seeing? More specifics, or just more routes? maybe the new /28 delegations are playing tricks on some people's filters... Lemme know. I don't see anything. I am looking for a connection into one of the public native v6 peering circles for an unfiltered connection, but I don't see anything here, due to my filters. Let me know what you are seeing secifically. Thanks Rob Rockell Sprintlink Internet Service Center Operations Engineering 703-689-6322 1-800-724-3329, PIN 385-8833 Ines|e gnyne qh vagr bz s|e Ino ngg una {e hgr bpu plxyne? On Sun, 30 May 1999, Bob Fink wrote: ->Rich, -> ->At 03:28 PM 5/30/99 -0700, Richard Draves wrote: ->>In the last several days the BGP traffic has skyrocketed... does anybody ->>know what's up? -> ->Rob Rockell had speculated to me that it looked as if someone was not filtering their downstreams, and one of their ->leaf-nodes descided to advertise default. He was looking into it, but also noted that he didn't see it in his (Sprint's) routing table due to his agressive filtering (one of those things we hope to harden on the 6bone!). -> ->Maybe Rob can comment (I've cc'd him here). -> -> ->Bob -> -> -> ->