From platini@fibertel.com.ar Wed Jun 2 01:32:54 1999
From: platini@fibertel.com.ar (Patricio Latini)
Date: Tue, 1 Jun 1999 21:32:54 -0300
Subject: Reacheability of Fibertel WWW Site
Message-ID: <004001beac8f$74a82530$3f64a8c0@fibertel.com.ar>
This is a multi-part message in MIME format.
------=_NextPart_000_003D_01BEAC76.4F459070
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I wank to ask to all 6bone members if you can reach without any problem =
my www site or my router
the www site is www.ipv6.fibertel.com.ar - 3ffe:3800:1::2 by ping or =
http
and my router at cisco.ipv6.fibertel.com.ar - 3ffe:3800:1::1 by ping
Thanks
------------------------------------------------------
Patricio Sebasti=E1n Latini
Network Administrator
Network Operations Center
Fibertel TCI2
Buenos Aires - Argentina
------------------------------------------------------
------=_NextPart_000_003D_01BEAC76.4F459070
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I wank to ask to all 6bone members if =
you can reach=20
without any problem my www site or my router
the www site is www.ipv6.fibertel.com.ar -=20
3ffe:3800:1::2 by ping or http
and my router at =
cisco.ipv6.fibertel.com.ar -=20
3ffe:3800:1::1 by ping
Thanks
------------------------------------------------------
Patric=
io=20
Sebasti=E1n Latini
Network Administrator
Network Operations=20
Center
Fibertel TCI2
Buenos Aires -=20
Argentina
------------------------------------------------------
------=_NextPart_000_003D_01BEAC76.4F459070--
From Marc.Blanchet@viagenie.qc.ca Wed Jun 2 16:25:38 1999
From: Marc.Blanchet@viagenie.qc.ca (Marc Blanchet)
Date: Wed, 02 Jun 1999 11:25:38 -0400
Subject: 400th tunnel!
Message-ID: <4.1.19990602112121.0362b7f0@mail.viagenie.qc.ca>
Hi,
by midnight yesterday, we just reached the 400th tunnel on our tunnel
server (http://www.freenet6.net)!
Regards, Marc.
PS. the purpose of this message is not a commercial announcement (our
service is a voluntary,free service), but just to tell people that IPv6 is
more than alive!
-----------------------------------------------------------
Marc Blanchet | Marc.Blanchet@viagenie.qc.ca
Viagénie inc. | http://www.viagenie.qc.ca
3107 des hôtels | tél.: 418-656-9254
Ste-Foy, Québec | fax.: 418-656-0183
Canada, G1W 4W5 | radio: VA2-JAZ
------------------------------------------------------------
Internet Engineering Standards/Normes d'ingénierie Internet
http://www.normos.org
------------------------------------------------------------
From mitra@ukr.net Sat Jun 5 00:15:29 1999
From: mitra@ukr.net (Alexei Akimov)
Date: Sat, 5 Jun 1999 02:15:29 +0300 (EEST)
Subject: No subject
Message-ID: <199906042315.CAA10955@wind.ukr.net>
Hi!
I am situated in Kiev, Ukraine and I'm looking for IPv6 peer to
connect to.
--
Wishing all the best,
Alexei Akimov AA914-RIPE Best Known As M1tRA
E-Mail: mitra@ukr.net ICQ: 2655858 +380 (44) 235-85-55 UkrNet Ltd., Kiev
From fink@es.net Sat Jun 5 03:26:03 1999
From: fink@es.net (Bob Fink)
Date: Fri, 04 Jun 1999 19:26:03 -0700
Subject: Ukraine connection to 6bone
In-Reply-To: <199906042315.CAA10955@wind.ukr.net>
Message-ID: <4.1.19990604191311.00b64580@imap2.es.net>
Alexei,
At 02:15 AM 6/5/99 +0300, Alexei Akimov wrote:
> Hi!
>I am situated in Kiev, Ukraine and I'm looking for IPv6 peer to
>connect to.
The one other Ukraine site, IPV6UA, Donetsk State Technical University:
gets their tunnel from INR, the Institute for Nuclear Resarch in Moscow:
so you might try them.
Bob
From fink@es.net Sat Jun 5 04:22:11 1999
From: fink@es.net (Bob Fink)
Date: Fri, 04 Jun 1999 20:22:11 -0700
Subject: Application for pTLA from Dante/Terena/Quantum - review
will close 8 June
In-Reply-To: <4.1.19990526184936.0097eb70@imap2.es.net>
Message-ID: <4.1.19990604200834.00c0e320@imap2.es.net>
--=====================_25062087==_.ALT
Content-Type: text/plain; charset="us-ascii"
I would like to announce the assignment of a pTLA to QTPVSIX based on the
comments received during the open review period.
Please note that this as a 28-bit pTLA.
---
QTPVSIX - The Quantum Test Programme IPv6 Project - This project will connect
european research networks using the native ATM service provided by the TEN-155
network operated by Dante.
inet6num: 3FFE:8030::/28
netname: QTPVSIX
---
Welcome QTPVSIX to the 6bone backbone!
Bob
--=====================_25062087==_.ALT
Content-Type: text/html; charset="us-ascii"
I would like to announce the assignment of a pTLA to QTPVSIX based on the
comments received during the open review period.
Please note that this as a 28-bit pTLA.
---
QTPVSIX - The Quantum Test Programme IPv6 Project - This project will
connect european research networks using the native ATM service provided
by the TEN-155 network operated by Dante.
inet6num: 3FFE:8030::/28
netname: QTPVSIX
<http://www.ip.qwest.net/~david/cgi-bin/whois?trumpet>
---
Welcome QTPVSIX to the 6bone backbone!
Bob
--=====================_25062087==_.ALT--
From yjchui@ms.chttl.com.tw Sat Jun 5 04:21:13 1999
From: yjchui@ms.chttl.com.tw (Yann-Ju Chu)
Date: Sat, 05 Jun 1999 11:21:13 +0800
Subject: about Reverse Name Lookup
Message-ID: <375897A9.5D1FEC88@ms.chttl.com.tw>
Hi:
When we are a transit site or leaf site, we will ask our provider to
have a pionter to us for the reverse name lookup in their DNS. However, when
we become a backbone site, how can we set in DNS for our reverse name lookup?
Thanks
From fink@es.net Sat Jun 5 15:48:30 1999
From: fink@es.net (Bob Fink)
Date: Sat, 05 Jun 1999 07:48:30 -0700
Subject: about Reverse Name Lookup
In-Reply-To: <375897A9.5D1FEC88@ms.chttl.com.tw>
Message-ID: <4.1.19990605074504.00c5e3d0@imap2.es.net>
At 11:21 AM 6/5/99 +0800, Yann-Ju Chu wrote:
>
>Hi:
> When we are a transit site or leaf site, we will ask our provider to
>have a pionter to us for the reverse name lookup in their DNS. However, when
>we become a backbone site, how can we set in DNS for our reverse name lookup?
Unfortunately I just noticed that the "How to Join the 6bone" page at has busted DNS setup pointers. If anyone can send me new info on DNS setup I will add it to this page.
Bill Manning is the best person, I think, to tell you how to setup the reverse path stuff. Of ocurse he sets it from the root.
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
From ksbn@kt.co.kr Mon Jun 7 10:30:11 1999
From: ksbn@kt.co.kr (ksb)
Date: Mon, 07 Jun 1999 18:30:11 +0900
Subject: v6 application
Message-ID: <375B9123.C8A43E66@kt.co.kr>
Dear members:
I'm looking for some applications, services, web server
addresses and so on for IPv6.
I have a FreeBSD router(with KAME code) and a Solaris 7
host(with SUN's IPv6 prototype).
WIll you send me some information?
Thank you.
--
Kim, Sahng-Beom / Korea Telecom
TEL : +82-42-870-8322
FAX : +82-42-870-8329
E-mail : ksbn@kt.co.kr
--
From peter@jazz-1.trumpet.com.au Mon Jun 7 14:23:27 1999
From: peter@jazz-1.trumpet.com.au (Peter Tattam)
Date: Mon, 7 Jun 1999 23:23:27 +1000 (EST)
Subject: Trumpet pTLA (3ffe:8000::/28) now online.
Message-ID:
I know it might seem trivial to some, but we've just made history by being the
first /28 to come online to the 6bone. Also this is a first for Australia,
Trumpet being the first pTLA in the Australian region.
There are however a couple of teething troubles that may need to be ironed out.
Firstly, some sites are filtering out /28 advertisements resulting in me not
being accesible to parts of the 6bone. Could everyone check their BGP setups
to see if they are allowing the /28 advertisements.
The second is a minor related one, and that is that the BGP reporting and other
software will need fixing to register /28's as pTLAs from now on.
I will also need another couple of peering points, preferably within good
proximity to us in the IPv4 world.
Thanks to all those who have helped in getting this to happen. You know who
you are :-)
Hip Hip Hooray!!!...
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 rsofia@rccn.net Mon Jun 7 14:24:39 1999
From: rsofia@rccn.net (Rute Sofia)
Date: Mon, 7 Jun 1999 14:24:39 +0100 (WET DST)
Subject: about Reverse Name Lookup
In-Reply-To: <4.1.19990605074504.00c5e3d0@imap2.es.net>
Message-ID:
Hi.
We have at http://www.fccn.pt/rcn/projectos/ipv6/ some DNS tutorials.
They now are only in portuguese :-), but the english version will be
available soon, hopefully by the end of this week.
So, I think it would be a good idea to add a link.
Thanks,
Rute Sofia
---------------------------------------------------
Helena Rute Esteves Carvalho Sofia
FCCN
Av. do Brasil, 101
1799 LISBOA CODEX
tel.: 8440115
fax: 8472167
e-mail: rsofia@rccn.net
"After silence, that which comes nearest to expressing
the inexpressible is Music." - Aldous Huxley
---------------------------------------------------
On Sat, 5 Jun 1999, Bob Fink wrote:
> At 11:21 AM 6/5/99 +0800, Yann-Ju Chu wrote:
> >
> >Hi:
> > When we are a transit site or leaf site, we will ask our provider to
> >have a pionter to us for the reverse name lookup in their DNS. However, when
> >we become a backbone site, how can we set in DNS for our reverse name lookup?
>
> Unfortunately I just noticed that the "How to Join the 6bone" page at has busted DNS setup pointers. If anyone can send me new info on DNS setup I will add it to this page.
>
> Bill Manning is the best person, I think, to tell you how to setup the reverse path stuff. Of ocurse he sets it from the root.
>
>
> Bob
>
>
> ---
> Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
>
From fink@es.net Mon Jun 7 15:54:03 1999
From: fink@es.net (Bob Fink)
Date: Mon, 07 Jun 1999 07:54:03 -0700
Subject: new pTLA for IIJ/JP: 3FFE:8020::/28
In-Reply-To: <19990607121906I.kazu@iijlab.net>
References: <4.1.19990604194335.00c16680@imap2.es.net>
<4.1.19990519233421.00b1f950@imap2.es.net>
<4.1.19990604194335.00c16680@imap2.es.net>
Message-ID: <4.1.19990607073914.00ae15c0@imap2.es.net>
--=====================_5122966==_.ALT
Content-Type: text/plain; charset="us-ascii"
I would like to announce the assignment of a pTLA to IIJ based on the comments
received during the open review period.
Please note that this as a 28-bit pTLA.
---
IIJ - The Internet Initiative Japan Inc. - IIJ is one of the largest IPv4
Internet service providers in Japan, providing Internet access and related
services, as well as providing IPv6 transit services to the WIDE project.
inet6num: 3FFE:8020::/28
netname: IIJ
---
Welcome IIJ to the 6bone backbone!
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and
will not be responsive to email until July 21. Please direct 6bone & ngtrans
questions to Alain Durand .
--=====================_5122966==_.ALT
Content-Type: text/html; charset="us-ascii"
I would like to announce the assignment of a pTLA to IIJ based on the
comments received during the open review period.
Please note that this as a 28-bit pTLA.
---
IIJ - The Internet Initiative Japan Inc. - IIJ is one of the largest IPv4
Internet service providers in Japan, providing Internet access and
related services, as well as providing IPv6 transit services to the WIDE
project.
inet6num: 3FFE:8020::/28
netname: IIJ
<http://www.ip.qwest.net/~david/cgi-bin/whois?iij>
---
Welcome IIJ to the 6bone backbone!
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July
11-16), and will not be responsive to email until July 21. Please direct
6bone & ngtrans questions to Alain Durand
<Alain.Durand@imag.fr>.
--=====================_5122966==_.ALT--
From bmanning@ISI.EDU Mon Jun 7 18:25:22 1999
From: bmanning@ISI.EDU (bmanning@ISI.EDU)
Date: Mon, 7 Jun 1999 10:25:22 -0700 (PDT)
Subject: about Reverse Name Lookup
In-Reply-To: <375897A9.5D1FEC88@ms.chttl.com.tw> from "Yann-Ju Chu" at Jun 05, 1999 11:21:13 AM
Message-ID: <199906071725.AA19747@zed.isi.edu>
>
> Hi:
> When we are a transit site or leaf site, we will ask our provider to
> have a pionter to us for the reverse name lookup in their DNS. However, when
> we become a backbone site, how can we set in DNS for our reverse name lookup?
> Thanks
>
This is a current weakness in the delegation process. While the registry is
a fine idea, it leaves out the DNS component. I've opined that the inverse
tree of the DNS works very well as a publication method for registry
data and avoids the problems inherent in a centralized registry... however:
When Bob authorizes a delegation, he sends an announcement to the list.
The delegates need to have at least two servers available to host the
delegation. For IP6.INT zones, it is -NOT- mandatory that you have a viable
ipv6 stack or server. Normal nameservers work just fine.
Since these delegations presume that you will have to make sub-delegations,
the following steps should help:
- Send me a list of your selected servers that will host
your delegation. I'll be happy to provide one.
the zone cuts will look like this:
f.5.ip6.int. in soa ns.isi.edu. bmanning.isi.edu. (
1925845 10800 900 604800 129600 )
in ns NS.ISI.EDU.
in ns dot.ep.net.
;
; bill manning bmanning@vacation.karoshi.com 02dec96 ASN-4555
0.0.1.1.c.b.f.5.ip6.int. in ns ns.isi.edu.
in ns dot.ep.net.
;
; bill manning bmanning@isi.edu 02dec96 ASN-226
0.0.0.0.e.2.f.5.ip6.int. in ns ns.isi.edu.
in ns orb.isi.edu.
;
; eof
-------------
For your specific zone, you'll need your downstreams to do
the same; e.g.
0.0.0.0.e.2.f.5.ip6.int. in soa ns.isi.edu. bmanning.isi.edu. (
1925845 10800 900 604800 129600 )
in ns NS.ISI.EDU.
in ns dot.ep.net.
;
b.0.2.0.0.0.0.C.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 in ptr IOSv6-7k.ep.net.
;
; sub-tla delegation for testing.
1.0.0.0 in ns dot.ep.net.
in ns flag.ep.net.
;
;
You may want to add something like this to your zone header, to help keep
this straight:
;
; | 16 | 32 | 16 | 64 bits |
; +--+------+---------------+--------+--------------------------------+
; |FP| TLA | NLA | SLA | Interface ID |
;
; | 16 | 8 | 8 | 16 | 8 | 8 | |
; +---------+----+---+------+----+---+--------------------------------+
; | 0x3ffe |0x8 | | RES |RES | | |
; +---------+----+---+------+----+---+--------------------------------+
; ^ ^ ^ ^
; | | | |
; | | | +--------+
; | | | |
; | | |
; | | | 0x26 128.9.160.26 = 3ffe:801:0000:0026::/64
; | | | 0x11 198.32.146.11= 3ffe:800:0000:0011::/64
; | | |
; | | +--- NLA2 0x00 LAP = 3ffe:800:0000::/48
; | | 0x01 ISI = 3ffe:801:0000::/48
; | | 0x02 CalTech = 3ffe:802:0000::/48
; | | 0x03 USC = 3ffe:803:0000::/48
; | | 0x04 NMSU = 3ffe:804:0000::/48 Jonathan Cook
; | | 0x05 iHighway= 3ffe:805:0000::/48 John M. Brown
; | | 0x06 AboveNet= 3ffe:806:0000::/48 Steve Rubin
; | | 0x07 Zocalo = 3ffe:807:0000::/48 Bill Woodcock
; | |
; | +-------- NLA1 for LAP = 3ffe:800::/24
; |
; +---------------- FP+TLA for 6bone = 3ffe::/16
;
;
...
Does this help at all?
--
--bill
From fink@es.net Mon Jun 7 19:11:03 1999
From: fink@es.net (Bob Fink)
Date: Mon, 07 Jun 1999 11:11:03 -0700
Subject: about Reverse Name Lookup
In-Reply-To: <199906071725.AA19747@zed.isi.edu>
References: <375897A9.5D1FEC88@ms.chttl.com.tw>
Message-ID: <4.1.19990607110857.00b6fed0@imap2.es.net>
Bill,
Thanks for your note on this. I've put it on a web page that has a pointer on the "How to Join the 6bone" page (near the bottom).
Thanks,
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
From bmanning@ISI.EDU Mon Jun 7 23:00:59 1999
From: bmanning@ISI.EDU (bmanning@ISI.EDU)
Date: Mon, 7 Jun 1999 15:00:59 -0700 (PDT)
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?) version
In-Reply-To: <4.1.19990505151055.00b08270@imap2.es.net> from "Bob Fink" at May 05, 1999 04:27:44 PM
Message-ID: <199906072201.AA23564@zed.isi.edu>
Note that this change affects the existant documents that are being
used by the various RIR's on their delegation policies, i.e.
RFC 2450,
RFC 2471,
draft-ietf-ipngwg-iana-tla-01.txt
which appears to conflict with RFC 1897.
I think that this change, as implemented in the 6bone should
be incorporated by the various RIRs in their operational documents
and be used as a reference by the IANA in their discussions
about longer term delegation policies.
Yes, there is a movement afoot to get real bit level delegation
deployed in the DNS but I don't think we can wait for that.
>
> 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
>
>
>
--
--bill
From fink@es.net Mon Jun 7 23:25:37 1999
From: fink@es.net (Bob Fink)
Date: Mon, 07 Jun 1999 15:25:37 -0700
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
version
In-Reply-To: <199906072201.AA23564@zed.isi.edu>
References: <4.1.19990505151055.00b08270@imap2.es.net>
Message-ID: <4.1.19990607152119.00c32aa0@imap2.es.net>
Bill,
I don't understand your comment on this. There appears no conflict in the proposed 6bone TLA usage with any of the docs you mention (by the way, RFC1897 is obsoleted). I'm probably missing something obvious, so please say more.
Thanks,
Bob
===
At 03:00 PM 6/7/99 -0700, bmanning@ISI.EDU wrote:
>
>Note that this change affects the existant documents that are being
>used by the various RIR's on their delegation policies, i.e.
>RFC 2450,
>RFC 2471,
>draft-ietf-ipngwg-iana-tla-01.txt
>which appears to conflict with RFC 1897.
>
> I think that this change, as implemented in the 6bone should
> be incorporated by the various RIRs in their operational documents
> and be used as a reference by the IANA in their discussions
> about longer term delegation policies.
> Yes, there is a movement afoot to get real bit level delegation
> deployed in the DNS but I don't think we can wait for that.
>
>
>>
>> 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
>>
>>
>>
>
>
>--
>--bill
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
From bmanning@ISI.EDU Mon Jun 7 23:40:57 1999
From: bmanning@ISI.EDU (bmanning@ISI.EDU)
Date: Mon, 7 Jun 1999 15:40:57 -0700 (PDT)
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: <4.1.19990607152119.00c32aa0@imap2.es.net> from "Bob Fink" at Jun 07, 1999 03:25:37 PM
Message-ID: <199906072240.AA24132@zed.isi.edu>
>
> Bill,
>
> I don't understand your comment on this. There appears no conflict in the proposed 6bone TLA usage with any of the docs you mention (by the way, RFC1897 is obsoleted). I'm probably missing something obvious, so please say more.
Well, in the document:
..........
PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT
(28 May 1999)
..........
That the RIRs sent to the IANA, they adopt the 13bit cutpoint
that was proposed in RFC 2450 and also proposed for the 6bone
and rejected for pragmatic operational reasons as described in
you note to the 6bone (below). RFC 2471 also calls for bit-level
delegations. My feeling is that the RIRs
should also adopt this feature and not attempt to enforce
delegations on bit bounds.
And while we can declare RFC1897 obsolete, the fact remains that it still
exists. (sort of like the all-ones, all-zeros broadcast values) Unless I
am mis-reading the draft-ietf-ipngwg-iana-tla-01.txt document, this old
delegation falls right in the APNIC proposed delegation... (I must be
misreading this)
> Thanks,
>
> Bob
>
> ===
> At 03:00 PM 6/7/99 -0700, bmanning@ISI.EDU wrote:
> >
> >Note that this change affects the existant documents that are being
> >used by the various RIR's on their delegation policies, i.e.
> >RFC 2450,
> >RFC 2471,
> >draft-ietf-ipngwg-iana-tla-01.txt
> >which appears to conflict with RFC 1897.
> >
> > I think that this change, as implemented in the 6bone should
> > be incorporated by the various RIRs in their operational documents
> > and be used as a reference by the IANA in their discussions
> > about longer term delegation policies.
> > Yes, there is a movement afoot to get real bit level delegation
> > deployed in the DNS but I don't think we can wait for that.
> >
> >
> >>
> >> 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
> >>
> >>
> >>
> >
> >
> >--
> >--bill
>
>
>
> ---
> Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
>
--
--bill
From fink@es.net Tue Jun 8 16:44:17 1999
From: fink@es.net (Bob Fink)
Date: Tue, 08 Jun 1999 08:44:17 -0700
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: <199906072240.AA24132@zed.isi.edu>
References: <4.1.19990607152119.00c32aa0@imap2.es.net>
Message-ID: <4.1.19990608083355.00b706a0@imap2.es.net>
Bill,
At 03:40 PM 6/7/99 -0700, bmanning@ISI.EDU wrote:
>>
>> Bill,
>>
>> I don't understand your comment on this. There appears no conflict in the
>proposed 6bone TLA usage with any of the docs you mention (by the way,
>RFC1897 is obsoleted). I'm probably missing something obvious, so please say
>more.
>
> Well, in the document:
>..........
> PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT
> (28 May 1999)
>..........
> That the RIRs sent to the IANA, they adopt the 13bit cutpoint
> that was proposed in RFC 2450 and also proposed for the 6bone
> and rejected for pragmatic operational reasons as described in
> you note to the 6bone (below). RFC 2471 also calls for bit-level
> delegations. My feeling is that the RIRs
> should also adopt this feature and not attempt to enforce
> delegations on bit bounds.
>
>And while we can declare RFC1897 obsolete, the fact remains that it still
>exists. (sort of like the all-ones, all-zeros broadcast values) Unless I
>am mis-reading the draft-ietf-ipngwg-iana-tla-01.txt document, this old
>delegation falls right in the APNIC proposed delegation... (I must be
>misreading this)
RFC1897 is truly obsolete, and tho a few people persist in not renumbering their devices, most of us just filter them out. For all real purposes they are non-existant.
Also, RFC1897 used the old format prefix 010 that is unassigned in the current address architecture doc, RFC2373, so there is no overlap even if you believe the old 6bone test prefixes are still in use (which they really arent').
As for RFC2471, in real practice it only exists to allocate the special 1FFE TLA to the 6bone, nothing else. It certainly isn't in conflict with what the RIRs are doing. The RIR plans to allocate /29 prefixes while not allowing the sTLA holder to use more than /35 without approval is consitent with history, and at this point a fact of life. I also don't thnk it will matter much at this stage of the IPv6 process.
Thanks,
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
From bmanning@ISI.EDU Tue Jun 8 17:27:49 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Tue, 8 Jun 1999 09:27:49 -0700 (PDT)
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: <4.1.19990608083355.00b706a0@imap2.es.net> from "Bob Fink" at Jun 08, 1999 08:44:17 AM
Message-ID: <199906081627.JAA14302@boreas.isi.edu>
> > PROVISIONAL IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT
> > (28 May 1999)
> >..........
> > That the RIRs sent to the IANA, they adopt the 13bit cutpoint
> > that was proposed in RFC 2450 and also proposed for the 6bone
> > and rejected for pragmatic operational reasons as described in
> > you note to the 6bone (below). RFC 2471 also calls for bit-level
> > delegations. My feeling is that the RIRs
> > should also adopt this feature and not attempt to enforce
> > delegations on bit bounds.
> >
> As for RFC2471, in real practice it only exists to allocate the special 1FFE TLA to the 6bone, nothing else. It certainly isn't in conflict with what the RIRs are doing. The RIR plans to allocate /29 prefixes while not allowing the sTLA holder to use more than /35 without approval is consitent with history, and at this point a fact of life. I also don't thnk it will matter much at this stage of the IPv6 process.
>
Bob,
There is a real problem with cut points on bit boundaries.
The DNS implementations we have available for use won't
work unless apply the cname hack on the equivalent of IPv4
/2 boundaries. This is an operational hit that the existing
6bone users refused to take.
Thats why there was the encouragement for you to change the
6bone delegations to /28 and not /29
RFC 2450 and RFC 2471 both recommend sub-TLA delegations
at the /29 level. So does this proposed RIR document.
If you really don't think this is a problem then why did
you make the change to /28 delegations for the 6bone?
Also remember that there is nothing that an RIR can do
to "not allow" a delegate to use their full delegation.
If you really beleive that it does not matter at this stage
then I disagree with you. Inverse delegations will not work,
delaying acceptence of this protocol.
> Thanks,
>
> Bob
>
>
> ---
> Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
>
--
--bill
From fink@es.net Tue Jun 8 18:18:37 1999
From: fink@es.net (Bob Fink)
Date: Tue, 08 Jun 1999 10:18:37 -0700
Subject: just a reminder, Bob is on vacation
Message-ID: <4.1.19990608101613.009af8a0@imap2.es.net>
6bone Folk,
Just a reminder that I am now on vacation until Oslo (IETF).
Please address all questions you would normally have for me to:
Alain Durand
and to me, Bob Fink
Thanks,
Bob
---
Bob will be on travel from June 9 until the Oslo IETF meeting (July 11-16), and will not be responsive to email until July 21. Please direct 6bone & ngtrans questions to Alain Durand .
From crawdad@fnal.gov Tue Jun 8 18:38:14 1999
From: crawdad@fnal.gov (Matt Crawford)
Date: Tue, 08 Jun 1999 12:38:14 -0500
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: Your message of Tue, 08 Jun 1999 09:27:49 PDT.
<199906081627.JAA14302@boreas.isi.edu>
Message-ID: <199906081738.MAA00770@gungnir.fnal.gov>
All right, enough already. Bill, I think you're overemphasizing the
ugliness of the classless in-addr hack, and omitting the fact that
it's just temporary until the bit-string labels and new reverse-zone
structure come on-line.
Matt
From bmanning@ISI.EDU Tue Jun 8 18:45:55 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Tue, 8 Jun 1999 10:45:55 -0700 (PDT)
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: <199906081738.MAA00770@gungnir.fnal.gov> from "Matt Crawford" at Jun 08, 1999 12:38:14 PM
Message-ID: <199906081745.KAA22981@boreas.isi.edu>
>
> All right, enough already. Bill, I think you're overemphasizing the
> ugliness of the classless in-addr hack, and omitting the fact that
> it's just temporary until the bit-string labels and new reverse-zone
> structure come on-line.
> Matt
Well perhaps. The hack is really intrackable above a /16 delegation
in the IPv4 world. And I place the "temporary" window at 24 months before
reasonable deployment occurs. Which is the same timeframe as this transition
service is expected to last.
--bill
From drj@lamar.colostate.edu Thu Jun 10 19:48:40 1999
From: drj@lamar.colostate.edu (Joseph Williams)
Date: Thu, 10 Jun 1999 12:48:40 -0600
Subject: HP-UX implementation of IPv6
Message-ID: <000201beb371$db5dda70$fe855281@joseph.colostate.edu>
Hi Folks:
I'm doing an install of IPv6 on HP-UX 11.0 and have been unable to work
with the binary that is posted on HP's site. The HP folks who manage
that site have been nice about things and they are looking into the
problems I've reported. However, in the meantime I'm wondering if
anyone else out there has successfully deployed HP's IPv6 stack. If you
have, I would like to hear from you to find out how the install went and
whether your implementation is still up and running.
Thank you,
Joseph Williams, Ph.D.
CIS Department, College of Business
Colorado State University
http://lamar.colostate.edu/~drj
From peter@jazz-1.trumpet.com.au Fri Jun 11 02:10:19 1999
From: peter@jazz-1.trumpet.com.au (Peter Tattam)
Date: Fri, 11 Jun 1999 11:10:19 +1000 (EST)
Subject: BGP page for TRUMPET pTLA
Message-ID:
To show the health of our view of the 6bone...
http://blues.trumpet.com.au/bgpstat/bgp.html
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 greg_dreelin@hotmail.com Fri Jun 11 18:01:27 1999
From: greg_dreelin@hotmail.com (Gregory Dreelin)
Date: Fri, 11 Jun 1999 17:01:27 JST
Subject: List Removal
Message-ID: <19990611080128.24274.qmail@hotmail.com>
How do I get off this list???
Thanks
Greg Dreelin
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
From latif.ladid@tbit.dk"
Please, find an update on the membership as of June 14th :
Please, welcome the newest Founding Members:
--------------------------------
- Microsoft: Thanks to Tony Hain and John Montgomery
- 3Com : Thanks to Cyndi Jung and Brad Turner
-------------------------------
A - So far officially confirmed IPv6 FORUM '' Founding Members'' :
A 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
14- Mentat, USA
15- SUN, USA
16- Netmedia, Finland
17- Trumpet Software, Australia
18- Intracom, Greece
19- Cisco, USA
20- COMPAQ, USA
21- SPRINT, USA
22- NOKIA, USA
23- AT&T, USA/EMEA
24- Teldat, Spain
25- Deutsche Telekom, Germany
26- Qwest, USA
27- IABG, Germany
28- ESNet, USA
29- MCIWorldcom, USA
30- Ericsson, Sweden
31- Microsoft, US
32- 3Com, US
B - Very interested, but understandably need time to go through internal
approval procedure:
1. IBM, USA
2. Acer, Taiwan
3. RADLAN, Israel
4. UMST Forum ICT Group
5. ATNET, USA
6. SBC Technology Resources, USA
7. Bell South Corporation, USA
8. N2G, US
9. Loran Technologies, Canada
10. Center for Wireless Comms, Singapore
11. UCAID, USA
12. SGI, USA
13. France Telecom, France
14. Nortel Networks, USA
15. Apple, USA
I might be missing some names !
C - Immediate Plan of Action
- First Update Session in Oslo along the IETF meeting
- First IPv6 FORUM Conference: GLOBAL IPv6 SUMMIT in Paris Oct 6-8.
- First Press Release will go out soon.
- More exciting programs will be published in due time.
Hope to win more IPv6 Friends as Founding Members!
R,
Latif
From yjchui@ms.chttl.com.tw Tue Jun 15 07:07:03 1999
From: yjchui@ms.chttl.com.tw (Yann-Ju Chu)
Date: Tue, 15 Jun 1999 14:07:03 +0800
Subject: sub-TLA assignment document
Message-ID: <3765ED87.FB21F041@ms.chttl.com.tw>
I am looking for the document about the sub-TLA assignment rule. Can anybody
tell me the full name of the Internet draft to refer to?
Thanks
Yann-Ju Chu
From rsofia@rccn.net Tue Jun 15 16:04:03 1999
From: rsofia@rccn.net (Rute Sofia)
Date: Tue, 15 Jun 1999 16:04:03 +0100 (WET DST)
Subject: FCCN's IPv6 Site
Message-ID:
Hi.
FCCN's IPv6 site is now also in english, at
http://www.fccn.pt/rccn/projectos/ipv6/ingles/ or on our IPv6/IPv4 Web
server, at http://www.ip6.rccn.net/ingles/
Among other information, we have some IPv6 basic tutorials, including one
about DNS.
Comments and suggestions are welcome :-)
Thanks,
Rute Sofia
---------------------------------------------------
Helena Rute Esteves Carvalho Sofia
FCCN
Av. do Brasil, 101
1799 LISBOA CODEX
tel.: 8440115
fax: 8472167
e-mail: rsofia@rccn.net
"After silence, that which comes nearest to expressing
the inexpressible is Music." - Aldous Huxley
---------------------------------------------------
From bmanning@ISI.EDU Tue Jun 15 20:33:18 1999
From: bmanning@ISI.EDU (bmanning@ISI.EDU)
Date: Tue, 15 Jun 1999 12:33:18 -0700 (PDT)
Subject: BOUNCE 6bone@zephyr.isi.edu: Non-member submission from [Bob Hinden ]
In-Reply-To: <199906151804.LAA08329@zephyr.isi.edu> from "owner-6bone@ISI.EDU" at Jun 15, 1999 11:04:28 AM
Message-ID: <199906151933.AA13198@zed.isi.edu>
> To: Yann-Ju Chu
> From: Bob Hinden
> Subject: Re: sub-TLA assignment document
> Cc: 6Bone <6bone@ISI.EDU>
> In-Reply-To: <3765ED87.FB21F041@ms.chttl.com.tw>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
>
> See:
>
> RFC2450 "Proposed TLA and NLA Assignment Rules"
>
> Bob
>
> At 02:07 PM 6/15/99 +0800, Yann-Ju Chu wrote:
> > I am looking for the document about the sub-TLA assignment rule. Can anybody
> >tell me the full name of the Internet draft to refer to?
> > Thanks
> > Yann-Ju Chu
Note that there is also:
draft-ietf-ipngwg-iana-tla-01.txt
Both have a potential showstopper in that they use bit-level delegation.
This can not currently be represented in the DNS in a managable fashion.
While I can remember 4 octects, 16 is right out.
I've made some comments about this failing on this and other lists.
The comment to the author(s) is to correct/modify the draft and re-issue
the RFC with the bit shift that Bob Fink agreed to for the 6bone on
05 may 1999. Then people who would like to deploy IPv6 can do so
without the pain of not having working DNS for address-name lookup.
--bill
From carl@bl.echidna.id.au Thu Jun 17 11:02:37 1999
From: carl@bl.echidna.id.au (Carl Brewer)
Date: Thu, 17 Jun 1999 20:02:37 +1000 (EST)
Subject: new Solaris patch for IPv6, anyone using it? help a newbie?
Message-ID: <199906171002.UAA00613@oversteer.bl.echidna.id.au>
G'day,
I've been trying to get IPv6 support onto my machines for a while,
but it's only just been made practical for me with Sun's release of
a patch to add in IPv6 support, so I'm a newbie here!
Is anyone else using it yet, and if so, could I get some tips
as to how to go about setting up my interfaces and connecting
a tunnel in Australia?
I've had a read through various documents, and have an idea
as to how the address structure works etc, but I've got few clues
when it comes to actually building something that works, any
pointers will be greatly appreciated.
Thanks,
Carl
From bmanning@ISI.EDU Mon Jun 21 16:50:16 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Mon, 21 Jun 1999 08:50:16 -0700 (PDT)
Subject: Proposed change in 6bone pTLA 3FFE usage - 2nd (final?)
In-Reply-To: from "Simon Leinen" at Jun 21, 1999 02:41:55 PM
Message-ID: <199906211550.IAA15594@zephyr.isi.edu>
nibble waste can be the source of hugh waste.
however, its what folks want, its do-able, and
I've been persuaded that my real source of concern
may not get triggered. I drop this isssue for now
and lets move on.
>
> Bill,
>
> > Well perhaps. The hack is really intrackable above a /16
> > delegation in the IPv4 world.
>
> in IPv4 the problem is much worse than in IPv6. To inverse-delegate a
> /9, /17 or /25 in IPv4, you need 128 CNAME pointers. In IPv6, the
> worst case requires only eight of them.
>
> Having personally delegated quite a few eight-host subnets according
> to the classless in-addr "hack", I think this is quite tractable.
>
> At least I don't think it's a good enough excuse to potentially waste
> gazillions of addresses by choosing bit boundaries a "user friendly"
> way. Although this is just the 6bone, I think that it would set a
> really bad example.
> --
> Simon.
>
--
--bill
From Marc.Blanchet@viagenie.qc.ca Thu Jun 24 20:37:38 1999
From: Marc.Blanchet@viagenie.qc.ca (Marc Blanchet)
Date: Thu, 24 Jun 1999 15:37:38 -0400
Subject: IPv6 deployment BOF at INET99
Message-ID: <4.1.19990624152922.0355b9d0@mail.viagenie.qc.ca>
Hi,
for those that are at INET99 in San José, or those that are in the Bay
area, there will be an IPv6 deployment BOF at 18h00 today. Meet near room
B3/B4 at 18h00 in the SanJosé Convention center.
agenda is in the works, but basically related to: status of deployment
efforts and how to join.
Regards, Marc.
-----------------------------------------------------------
Marc Blanchet | Marc.Blanchet@viagenie.qc.ca
Viagénie inc. | http://www.viagenie.qc.ca
3107 des hôtels | tél.: 418-656-9254
Ste-Foy, Québec | fax.: 418-656-0183
Canada, G1W 4W5 | radio: VA2-JAZ
------------------------------------------------------------
Internet Engineering Standards/Normes d'ingénierie Internet
http://www.normos.org
------------------------------------------------------------
From richdr@microsoft.com Thu Jun 24 21:53:07 1999
From: richdr@microsoft.com (Richard Draves)
Date: Thu, 24 Jun 1999 13:53:07 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153D2@RED-MSG-50>
I've started experimenting with connecting a 6to4 relay router to the 6bone.
(See http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
This means that the 2010::/16 prefix is now being advertised in the 6bone.
However it appears that many sites are filtering this prefix. If you are
filtering, could you permit the 2010::/16 prefix?
As a check, please try pinging 2010:836b:4179::836b:4179.
Thanks,
Rich
From cmj@3com.com Thu Jun 24 23:17:03 1999
From: cmj@3com.com (Cyndi Jung)
Date: Thu, 24 Jun 1999 15:17:03 -0700
Subject: 2010::/16 filtering
Message-ID: <3.0.32.19990624151659.00b2a730@pop.nsd.3com.com>
At 01:53 PM 6/24/99 -0700, Richard Draves wrote:
>I've started experimenting with connecting a 6to4 relay router to the 6bone.
>(See http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
>
>This means that the 2010::/16 prefix is now being advertised in the 6bone.
>
>However it appears that many sites are filtering this prefix. If you are
>filtering, could you permit the 2010::/16 prefix?
>
I don't know about filtering, but I run into a loop attempting to get
to it:
Welcome to the 3Com NETBuilder
[1]TDC-ipv6 # trr6 2010:836b:4179::836B:4179
TraceRoute to 2010:836B:4179::836B:4179/128
TTL Next Hop Address RTTs
1 3FFE:1900:5:1:200:81FF:FED5:805A/128 16 ms 16 ms 14 ms
2 3FFE:1C00::3/128 86 ms 83 ms 85 ms
3 3FFE:1001:1:F004::2/128 313 ms 327 ms 307 ms
4 3FFE:900:0:3::2/128 115 ms 119 ms 113 ms
5 3FFE:1001:1:F004::2/128 356 ms 359 ms 335 ms
6 3FFE:900:0:3::2/128 150 ms 145 ms 148 ms
7 3FFE:1001:1:F004::2/128 377 ms 374 ms 371 ms
8 3FFE:900:0:3::2/128 183 ms 184 ms 192 ms
9 *
9 3FFE:1001:1:F004::2/128 403 ms *
10 3FFE:900:0:3::2/128 271 ms 228 ms 249 ms
11 3FFE:1001:1:F004::2/128 451 ms
12 3FFE:900:0:3::2/128 254 ms 250 ms
13 3FFE:1001:1:F004::2/128 850 ms *
14 3FFE:900:0:3::2/128 284 ms * *
15 * * *
16 3FFE:900:0:3::2/128
Cyndi
From bmanning@ISI.EDU Fri Jun 25 00:13:22 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Thu, 24 Jun 1999 16:13:22 -0700 (PDT)
Subject: 2010::/16 filtering
In-Reply-To: <4D0A23B3F74DD111ACCD00805F31D810145153D2@RED-MSG-50> from "Richard Draves" at Jun 24, 1999 01:53:07 PM
Message-ID: <199906242313.QAA14612@zephyr.isi.edu>
>
> I've started experimenting with connecting a 6to4 relay router to the 6bone.
> (See http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
>
> This means that the 2010::/16 prefix is now being advertised in the 6bone.
>
> However it appears that many sites are filtering this prefix. If you are
> filtering, could you permit the 2010::/16 prefix?
>
> As a check, please try pinging 2010:836b:4179::836b:4179.
>
> Thanks,
> Rich
Thats a bit much, don't you think? It comprehends the entire range ear-marked
for the IANA, the three RIRs and the reserved sub-TLA space.
--bill
From bmanning@ISI.EDU Fri Jun 25 00:36:18 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Thu, 24 Jun 1999 16:36:18 -0700 (PDT)
Subject: 2010::/16 filtering
In-Reply-To: <4D0A23B3F74DD111ACCD00805F31D810145153DD@RED-MSG-50> from "Richard Draves" at Jun 24, 1999 04:27:57 PM
Message-ID: <199906242336.QAA16283@zephyr.isi.edu>
>
> > Thats a bit much, don't you think? It comprehends the entire
> > range ear-marked
> > for the IANA, the three RIRs and the reserved sub-TLA space.
>
> I don't follow you?
> 2010::/16 is just taking one TLA.
>
> Rich
Isn't this the one earmarked for subtla assignment?
--bill
From richdr@microsoft.com Fri Jun 25 00:27:57 1999
From: richdr@microsoft.com (Richard Draves)
Date: Thu, 24 Jun 1999 16:27:57 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153DD@RED-MSG-50>
> Thats a bit much, don't you think? It comprehends the entire
> range ear-marked
> for the IANA, the three RIRs and the reserved sub-TLA space.
I don't follow you?
2010::/16 is just taking one TLA.
Rich
From richdr@microsoft.com Fri Jun 25 00:47:25 1999
From: richdr@microsoft.com (Richard Draves)
Date: Thu, 24 Jun 1999 16:47:25 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153DF@RED-MSG-50>
> > > Thats a bit much, don't you think? It comprehends the entire
> > > range ear-marked
> > > for the IANA, the three RIRs and the reserved sub-TLA space.
> >
> > I don't follow you?
> > 2010::/16 is just taking one TLA.
> >
> > Rich
>
> Isn't this the one earmarked for subtla assignment?
I have no idea. The 6to4 draft says to use TLA 0x0010 so that's what I'm
using.
Rich
From cmetz@inner.net Fri Jun 25 01:34:57 1999
From: cmetz@inner.net (Craig Metz)
Date: Thu, 24 Jun 1999 20:34:57 -0400
Subject: 2010::/16 filtering
In-Reply-To: Your message of "Thu, 24 Jun 1999 13:53:07 PDT."
<4D0A23B3F74DD111ACCD00805F31D810145153D2@RED-MSG-50>
Message-ID: <199906250028.AAA15164@inner.net>
In message <4D0A23B3F74DD111ACCD00805F31D810145153D2@RED-MSG-50>, you write:
>I've started experimenting with connecting a 6to4 relay router to the 6bone.
>(See http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
>
>This means that the 2010::/16 prefix is now being advertised in the 6bone.
>
>However it appears that many sites are filtering this prefix. If you are
>filtering, could you permit the 2010::/16 prefix?
>
>As a check, please try pinging 2010:836b:4179::836b:4179.
Is it possible to make the 6to4 translator appear under your legitimate
prefix?
I don't think it's a good idea to let every "hey, I'm testing a new service,
so please let me advertise a huge prefix" request happen; that will just lead
us to a bad place.
-Craig
From rrockell@sprint.net Fri Jun 25 02:47:32 1999
From: rrockell@sprint.net (Robert Rockell)
Date: Thu, 24 Jun 1999 21:47:32 -0400 (EDT)
Subject: 2010::/16 filtering
In-Reply-To: <199906250028.AAA15164@inner.net>
Message-ID:
I have permitted the prefix into and out of Sprint filters, FYI. I am seeing
the announcement currently through the following AS-paths.
sl-bb1-6bone#sho ipv bgp 2010::/16
BGP routing table entry for 2010::0/16, version 345
Paths: (5 availiable, best #1)
nexthop: 3FFE:2900:A:3::2 from: 3FFE:2900:A:3::2
linklocal: FE80::26F5:4C36 Tunnel10
weight 0
AS path: 7081
nexthop: 3FFE:2900:B:F::2 from: 3FFE:2900:B:F::2
linklocal: FE80::C5C:69A8:B Tunnel45
weight 0
AS path: 5761
nexthop: 3FFE:900:0:1C::1 from: 3FFE:900:0:1C::1
linklocal: FE80::C8E:50C2:22 Tunnel21
weight 0
AS path: 1225 237 7081
nexthop: 3FFE:C00:E:1::1 from: 3FFE:C00:E:1::1
linklocal: FE80::60:3E11:6770:27 Tunnel50
weight 0
AS path: 109 237 7081
nexthop: 3FFE:2900:1::1E from: 3FFE:2900:1::1E
linklocal: FE80::200:81FF:FED5:805A Tunnel1
weight 0
AS path: 561 237 7081
Should it be deemed that the 2010::/16 block will be split up into
sub-delegations, I will allow up to /24 announcements. Currently, I only
allow the /16 through.
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 Thu, 24 Jun 1999, Craig Metz wrote:
->In message <4D0A23B3F74DD111ACCD00805F31D810145153D2@RED-MSG-50>, you write:
->>I've started experimenting with connecting a 6to4 relay router to the 6bone.
->>(See http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
->>
->>This means that the 2010::/16 prefix is now being advertised in the 6bone.
->>
->>However it appears that many sites are filtering this prefix. If you are
->>filtering, could you permit the 2010::/16 prefix?
->>
->>As a check, please try pinging 2010:836b:4179::836b:4179.
->
-> Is it possible to make the 6to4 translator appear under your legitimate
->prefix?
->
-> I don't think it's a good idea to let every "hey, I'm testing a new service,
->so please let me advertise a huge prefix" request happen; that will just lead
->us to a bad place.
->
-> -Craig
->
From carl@bl.echidna.id.au Fri Jun 25 03:53:14 1999
From: carl@bl.echidna.id.au (Carl Brewer)
Date: Fri, 25 Jun 1999 12:53:14 +1000 (EST)
Subject: anyone using the new Sun IPv6 patch and want to help a newbie? :)
Message-ID: <199906250253.MAA03501@oversteer.bl.echidna.id.au>
G'day,
I'm currently wrestling with Sun's latest IPv6 patch for SunOS 5.7
(patch 107788-01), and the doco is somewhat scant. If anyone
else is using this stuff and wants to point me in the right
direction (I have a tunnel through trumpet.com.au allocate, but
can't get it to work at the moment) I'd much appreciate some hints.
Once I get it up and running I want to put up an easy "how to"
webpage for setting up my config as a router and tunnel endpoint,
in particular how to drive in.ndpd! (what doco?!!!)
Rather than me clogging your mailboxes with my config stuff,
can anyone that wants to help drop me an email and we'll work from
there?
thankyou,
Carl
From richdr@microsoft.com Fri Jun 25 04:21:23 1999
From: richdr@microsoft.com (Richard Draves)
Date: Thu, 24 Jun 1999 20:21:23 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>
> Is it possible to make the 6to4 translator appear under
> your legitimate
> prefix?
>
> I don't think it's a good idea to let every "hey, I'm
> testing a new service,
> so please let me advertise a huge prefix" request happen;
> that will just lead
> us to a bad place.
6to4 has been accepted by the ngtrans WG as a valuable tool. There are
already two interoperating implementations that I know of. The logical next
step is to setup and start testing a 6to4 relay router. I think it makes
sense to do this using the real 6to4 prefix - otherwise we'll need a
transition from the temporary 6to4 prefix to the real 6to4 prefix. That
would be a bad place.
Rich
From peter@jazz-1.trumpet.com.au Fri Jun 25 04:33:02 1999
From: peter@jazz-1.trumpet.com.au (Peter Tattam)
Date: Fri, 25 Jun 1999 13:33:02 +1000 (EST)
Subject: Trumpet Software International begins rollout of IPv6 services.
Message-ID:
This message is not meant as marketing and will probably have little direct
impact on existng 6bone memebers, but instead serves to reiterate the
commitment that we here at Trumpet Software International have to the IPv6
project and the 6bone in general. We feel that a strong and decisive step in
this direction will assist the acceleration of IPv6 services worldwide.
This press release has been distributed to the local media in Tasmania, one key
national paper (The Australian) and interested federal and state govt members
in Tasmania.
Peter
PRESS RELEASE
25th June 1999
Trumpet Software International Introduces IPv6 to Internet Users in Australia.
Trumpet Software International Pty. Ltd. based in Hobart is heralding a new era
for Internet users by introducing Australia's first Internet Service Provider
(ISP) using the new emergent standard in Internet Protocols known as the IPv6
protocol.
The Federal Government, through their strategy of Building on IT Strengths,
aims to assist in funding next generation networks, support of digital
transmission trial test-beds and the development of international broadband R&D
links. What Trumpet has achieved is very much in line with this strategy and
attains a strong position to take full advantage of the new developments in
communications infrastructure.
INTERNET ADDRESSING
All addresses used in the Internet must be unique. With the present method of
address allocation, there is a finite limit that will be reached sooner rather
than later. The problem is a bit like the millennium bug. Potentially a time
bomb waiting to go off.
WHAT IS IPv6?
IPv6 is a replacement Internet Protocol that will enhance the ability to
sustain the continuous growth of the Internet, solving the IP address space
depletion dilemma and enhancing other properties that will eventually impact on
the viability of the Internet. By the use of the IPv6 Addressing capability,
rather than the existing IPv4 protocol, the limit on addresses has been
extended from a theoretical 4 billion to 340 trillion, trillion, trillion
(3.4x10 (38)
WHY HAVE IPv6?
IPv6 is more than an improved longer term addressing facility. It is also a
protocol that offers more scalable network architecture, improved security and
data integrity, improved quality of service and security enhancements.
The 128 bit address space that IPv6 uses will allow businesses to deploy a
great array of new desktop, mobile and embedded network devices in a cost
effective, managed manner. The advanced auto configuration features will allow
automatic attachment of these devices to the network without the costs of
manual configuring.
These features and the new IPv6 security features of encryption and
authentication services make the protocol very much an end user and business
concern.
Other factors that are important in the Internet changes are the need for
effective scalable routing. This is the technique that enables the addresses of
all nodes or devices on the Internet to be located by a tree structure search
without the need to hold all addresses on key routers only.
As a consequence of the existing 32 bit addressing architecture, the Ipv4
network regularly experiences small "tremors" when these key Internet routers
have difficulty in keeping up with the current network.
The way that IPv6 assigns addresses will make this a lot more effective with a
minimum of human intervention.
Consequently new devices can be configured in a simpler manner and existing
ones renumbered without any visible impact on the bulk of users.
As with many new technical advances, networked business enterprises that invest
in IPv6 planning now will enhance their competitive advantage as the growth of
Internetworking proceeds.
IPv6 as the standard for Internet Protocol or IP as set out by the Internet
Engineering Steering Group has been approved as far back as 1994. Most major
vendors such as Digital, Apple, HP, Novell and Sun have started to deliver IPv6
on desktop machines and servers. A wide range of support already exists for the
protocol.
IPv6 is not just an address improvement, it introduces a completely fresh start
and structured hierarchy of routing that will replace the present chaotic
anomalies and liabilities.
WHAT HAS TRUMPET DONE FOR IPv6 AND THE INTERNET?
Trumpet Software International Pty. Ltd. has established the first IPv6
Internet Service Provider (ISP) in Australia. This has been made possible by
the impending release of the Trumpet Winsock Version 5.0 product that is IPv6
compatible. Trumpet is also the first pseudo Top Level Aggregate (pTLA) for
the 6bone in Australia. The 6bone is a virtual network for the testing of IPv6
technology that runs off the regular Internet. This facility is rapidly
reaching production level status. The advances at Trumpet enable the Company to
provide 6bone connections to other organisations around the nation.
--
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 cmetz@inner.net Fri Jun 25 06:57:48 1999
From: cmetz@inner.net (Craig Metz)
Date: Fri, 25 Jun 1999 01:57:48 -0400
Subject: 2010::/16 filtering
In-Reply-To: Your message of "Thu, 24 Jun 1999 20:21:23 PDT."
<4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>
Message-ID: <199906250551.FAA15538@inner.net>
In message <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>, you write:
>> Is it possible to make the 6to4 translator appear under
>> your legitimate
>> prefix?
>>
>> I don't think it's a good idea to let every "hey, I'm
>> testing a new service,
>> so please let me advertise a huge prefix" request happen;
>> that will just lead
>> us to a bad place.
>
>6to4 has been accepted by the ngtrans WG as a valuable tool. There are
>already two interoperating implementations that I know of. The logical next
>step is to setup and start testing a 6to4 relay router. I think it makes
>sense to do this using the real 6to4 prefix - otherwise we'll need a
>transition from the temporary 6to4 prefix to the real 6to4 prefix. That
>would be a bad place.
Without some care to get the routing configuration done right, when that
second implementation's author wants to also advertise the prefix on the 6Bone,
bad things could happen. I'm no BGP wizard, but I think that it might be clever
to grab a private-use ASN and to advertise all instances of this special prefix
out of that ASN. Can someone who is more of a routing geek than I confirm or
refute this?
-Craig
From rrockell@sprint.net Fri Jun 25 08:04:33 1999
From: rrockell@sprint.net (Robert Rockell)
Date: Fri, 25 Jun 1999 03:04:33 -0400 (EDT)
Subject: 2010::/16 filtering
In-Reply-To: <199906250551.FAA15538@inner.net>
Message-ID:
I think that it becomes irrelevant which 6to4 router you use, so
potentially, multiple people could announce the same prefix. If we adopt
some kind of rule whereby all pTLA's have a 6to4 router, we won't even have
to announce it at all.
Brian, could you comment? I don't want to misinterpret the draft.
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 Fri, 25 Jun 1999, Craig Metz wrote:
->In message <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>, you write:
->>> Is it possible to make the 6to4 translator appear under
->>> your legitimate
->>> prefix?
->>>
->>> I don't think it's a good idea to let every "hey, I'm
->>> testing a new service,
->>> so please let me advertise a huge prefix" request happen;
->>> that will just lead
->>> us to a bad place.
->>
->>6to4 has been accepted by the ngtrans WG as a valuable tool. There are
->>already two interoperating implementations that I know of. The logical next
->>step is to setup and start testing a 6to4 relay router. I think it makes
->>sense to do this using the real 6to4 prefix - otherwise we'll need a
->>transition from the temporary 6to4 prefix to the real 6to4 prefix. That
->>would be a bad place.
->
-> Without some care to get the routing configuration done right, when that
->second implementation's author wants to also advertise the prefix on the 6Bone,
->bad things could happen. I'm no BGP wizard, but I think that it might be clever
->to grab a private-use ASN and to advertise all instances of this special prefix
->out of that ASN. Can someone who is more of a routing geek than I confirm or
->refute this?
->
-> -Craig
->
From bmanning@ISI.EDU Fri Jun 25 14:22:47 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Fri, 25 Jun 1999 06:22:47 -0700 (PDT)
Subject: 2010::/16 filtering
In-Reply-To: <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50> from "Richard Draves" at Jun 24, 1999 08:21:23 PM
Message-ID: <199906251322.GAA01709@boreas.isi.edu>
>
> > Is it possible to make the 6to4 translator appear under
> > your legitimate
> > prefix?
> >
> > I don't think it's a good idea to let every "hey, I'm
> > testing a new service,
> > so please let me advertise a huge prefix" request happen;
> > that will just lead
> > us to a bad place.
>
> 6to4 has been accepted by the ngtrans WG as a valuable tool. There are
> already two interoperating implementations that I know of. The logical next
> step is to setup and start testing a 6to4 relay router. I think it makes
> sense to do this using the real 6to4 prefix - otherwise we'll need a
> transition from the temporary 6to4 prefix to the real 6to4 prefix. That
> would be a bad place.
>
> Rich
>
I think that there is a problem here w/ 6to4 and the subTLA drafts
taking the same TLA. If this is correct, which would you prefer to keep?
--
--bill
From perry@piermont.com Fri Jun 25 15:38:44 1999
From: perry@piermont.com (Perry E. Metzger)
Date: 25 Jun 1999 10:38:44 -0400
Subject: anyone using the new Sun IPv6 patch and want to help a newbie? :)
In-Reply-To: Carl Brewer's message of "Fri, 25 Jun 1999 12:53:14 +1000 (EST)"
References: <199906250253.MAA03501@oversteer.bl.echidna.id.au>
Message-ID: <871zf0s5u3.fsf@jekyll.piermont.com>
Carl Brewer writes:
> I'm currently wrestling with Sun's latest IPv6 patch for SunOS 5.7
> (patch 107788-01), and the doco is somewhat scant. If anyone
> else is using this stuff and wants to point me in the right
> direction (I have a tunnel through trumpet.com.au allocate, but
> can't get it to work at the moment) I'd much appreciate some hints.
BTW, a lot of IPv6 users are subscribed to users@ipv6.org
The vision in creating it was so that 6bone could handle the "how to
deal with the 6bone" types of issues, and "users" could handle the "I
can't get my AIX box to do neighbor discovery" type questions...
Perry
From platini@fibertel.com.ar Fri Jun 25 16:14:05 1999
From: platini@fibertel.com.ar (Patricio Latini)
Date: Fri, 25 Jun 1999 12:14:05 -0300
Subject: 2010::/16 filtering
References:
Message-ID: <00e601bebf1d$5d5a7a40$d064a8c0@fibertel.com.ar>
I thinks that in the inital stage of the 6to4 transalations each pTLA or sub
TLA should use a subnet his own prefix to do the tests..
and in a future all of us could adopt the common prefix to do the
translation. i think that kind of decitions should be talked by all the
6bone members.
----------------------------------------------------
Patricio Sebastián Latini
Network Administrator
Network Operations Center
Fibertel TCI2
Buenos Aires - Argentina
------------------------------------------------------
----- Original Message -----
From: Robert Rockell
To: Craig Metz
Cc: Richard Draves ; <6bone@ISI.EDU>
Sent: Friday, June 25, 1999 4:04 AM
Subject: Re: 2010::/16 filtering
> I think that it becomes irrelevant which 6to4 router you use, so
> potentially, multiple people could announce the same prefix. If we adopt
> some kind of rule whereby all pTLA's have a 6to4 router, we won't even
have
> to announce it at all.
> Brian, could you comment? I don't want to misinterpret the draft.
>
> 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 Fri, 25 Jun 1999, Craig Metz wrote:
>
> ->In message <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>, you
write:
> ->>> Is it possible to make the 6to4 translator appear under
> ->>> your legitimate
> ->>> prefix?
> ->>>
> ->>> I don't think it's a good idea to let every "hey, I'm
> ->>> testing a new service,
> ->>> so please let me advertise a huge prefix" request happen;
> ->>> that will just lead
> ->>> us to a bad place.
> ->>
> ->>6to4 has been accepted by the ngtrans WG as a valuable tool. There are
> ->>already two interoperating implementations that I know of. The logical
next
> ->>step is to setup and start testing a 6to4 relay router. I think it
makes
> ->>sense to do this using the real 6to4 prefix - otherwise we'll need a
> ->>transition from the temporary 6to4 prefix to the real 6to4 prefix. That
> ->>would be a bad place.
> ->
> -> Without some care to get the routing configuration done right, when
that
> ->second implementation's author wants to also advertise the prefix on the
6Bone,
> ->bad things could happen. I'm no BGP wizard, but I think that it might be
clever
> ->to grab a private-use ASN and to advertise all instances of this special
prefix
> ->out of that ASN. Can someone who is more of a routing geek than I
confirm or
> ->refute this?
> ->
> -> -Craig
> ->
>
From richdr@microsoft.com Fri Jun 25 19:39:35 1999
From: richdr@microsoft.com (Richard Draves)
Date: Fri, 25 Jun 1999 11:39:35 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153EC@RED-MSG-50>
> Without some care to get the routing configuration done
> right, when that
> second implementation's author wants to also advertise the
> prefix on the 6Bone,
> bad things could happen. I'm no BGP wizard, but I think that
> it might be clever
> to grab a private-use ASN and to advertise all instances of
> this special prefix
> out of that ASN. Can someone who is more of a routing geek
> than I confirm or
> refute this?
This is exactly the kind of thing I want to test.
Rich
From richdr@microsoft.com Fri Jun 25 19:44:32 1999
From: richdr@microsoft.com (Richard Draves)
Date: Fri, 25 Jun 1999 11:44:32 -0700
Subject: 2010::/16 filtering
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810145153EE@RED-MSG-50>
This routing loop should be fixed now.
If anyone else can't reach 2010:836b:4179::836b:4179, please let me know.
Thanks,
Rich
> -----Original Message-----
> From: Cyndi Jung [mailto:cmj@3com.com]
> Sent: Thursday, June 24, 1999 3:17 PM
> To: Richard Draves; '6bone'
> Subject: Re: 2010::/16 filtering
>
>
> At 01:53 PM 6/24/99 -0700, Richard Draves wrote:
> >I've started experimenting with connecting a 6to4 relay
> router to the 6bone.
> >(See
> http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-02.txt.)
> >
> >This means that the 2010::/16 prefix is now being advertised
> in the 6bone.
> >
> >However it appears that many sites are filtering this
> prefix. If you are
> >filtering, could you permit the 2010::/16 prefix?
> >
>
> I don't know about filtering, but I run into a loop attempting to get
> to it:
>
>
> Welcome to the 3Com NETBuilder
> [1]TDC-ipv6 # trr6 2010:836b:4179::836B:4179
> TraceRoute to 2010:836B:4179::836B:4179/128
> TTL Next Hop Address RTTs
> 1 3FFE:1900:5:1:200:81FF:FED5:805A/128 16 ms 16 ms 14 ms
> 2 3FFE:1C00::3/128 86 ms 83 ms 85 ms
> 3 3FFE:1001:1:F004::2/128 313 ms 327
> ms 307 ms
> 4 3FFE:900:0:3::2/128 115 ms 119
> ms 113 ms
> 5 3FFE:1001:1:F004::2/128 356 ms 359
> ms 335 ms
> 6 3FFE:900:0:3::2/128 150 ms 145
> ms 148 ms
> 7 3FFE:1001:1:F004::2/128 377 ms 374
> ms 371 ms
> 8 3FFE:900:0:3::2/128 183 ms 184
> ms 192 ms
> 9 *
> 9 3FFE:1001:1:F004::2/128 403 ms *
> 10 3FFE:900:0:3::2/128 271 ms 228
> ms 249 ms
> 11 3FFE:1001:1:F004::2/128 451 ms
>
> 12 3FFE:900:0:3::2/128 254 ms 250 ms
> 13 3FFE:1001:1:F004::2/128 850 ms *
> 14 3FFE:900:0:3::2/128 284 ms * *
> 15 * * *
> 16 3FFE:900:0:3::2/128
>
> Cyndi
>
From brian@hursley.ibm.com Fri Jun 25 18:56:18 1999
From: brian@hursley.ibm.com (Brian E Carpenter)
Date: Fri, 25 Jun 1999 12:56:18 -0500
Subject: 2010::/16 filtering
References:
Message-ID: <3773C2C2.85D36DD@hursley.ibm.com>
What the draft says is that many relay routers may advertise
2010::/16 but that these advertisements should be limited
in scope by BGP policy. So yes, using an AS # is indicated
so that policies can be put in place. BGP mavens please apply
sanity checks to the new draft draft-ietf-ngtrans-6to4-02.txt
Brian
Robert Rockell wrote:
>
> I think that it becomes irrelevant which 6to4 router you use, so
> potentially, multiple people could announce the same prefix. If we adopt
> some kind of rule whereby all pTLA's have a 6to4 router, we won't even have
> to announce it at all.
> Brian, could you comment? I don't want to misinterpret the draft.
>
> 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 Fri, 25 Jun 1999, Craig Metz wrote:
>
> ->In message <4D0A23B3F74DD111ACCD00805F31D810145153E3@RED-MSG-50>, you write:
> ->>> Is it possible to make the 6to4 translator appear under
> ->>> your legitimate
> ->>> prefix?
> ->>>
> ->>> I don't think it's a good idea to let every "hey, I'm
> ->>> testing a new service,
> ->>> so please let me advertise a huge prefix" request happen;
> ->>> that will just lead
> ->>> us to a bad place.
> ->>
> ->>6to4 has been accepted by the ngtrans WG as a valuable tool. There are
> ->>already two interoperating implementations that I know of. The logical next
> ->>step is to setup and start testing a 6to4 relay router. I think it makes
> ->>sense to do this using the real 6to4 prefix - otherwise we'll need a
> ->>transition from the temporary 6to4 prefix to the real 6to4 prefix. That
> ->>would be a bad place.
> ->
> -> Without some care to get the routing configuration done right, when that
> ->second implementation's author wants to also advertise the prefix on the 6Bone,
> ->bad things could happen. I'm no BGP wizard, but I think that it might be clever
> ->to grab a private-use ASN and to advertise all instances of this special prefix
> ->out of that ASN. Can someone who is more of a routing geek than I confirm or
> ->refute this?
> ->
> -> -Craig
> ->
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter (IAB Chair)
Program Director, Internet Standards & Technology, IBM Internet Div
As of May 24, 1999: on assignment for IBM at http://www.iCAIR.org
Non-IBM email: brian@icair.org
From brian@hursley.ibm.com Fri Jun 25 19:06:02 1999
From: brian@hursley.ibm.com (Brian E Carpenter)
Date: Fri, 25 Jun 1999 13:06:02 -0500
Subject: 2010::/16 filtering
References: <4D0A23B3F74DD111ACCD00805F31D810145153DF@RED-MSG-50>
Message-ID: <3773C50A.C5E5B2D2@hursley.ibm.com>
Richard Draves wrote:
>
> > > > Thats a bit much, don't you think? It comprehends the entire
> > > > range ear-marked
> > > > for the IANA, the three RIRs and the reserved sub-TLA space.
> > >
> > > I don't follow you?
> > > 2010::/16 is just taking one TLA.
> > >
> > > Rich
> >
> > Isn't this the one earmarked for subtla assignment?
>
> I have no idea. The 6to4 draft says to use TLA 0x0010 so that's what I'm
> using.
I though the sub-TLA prefix was 2001::/16. Bill please double check
this; it is rather confusing in the drafts due to the format
prefix being 3 bits long.
To be clear the sub-TLA prefix is specified as
> > FP = 001
> > TLA ID = 0x0001
which I thought turns into 2001::/16. Tell me if I am confused.
Brian
From brian@hursley.ibm.com Sat Jun 26 04:30:40 1999
From: brian@hursley.ibm.com (Brian E Carpenter)
Date: Fri, 25 Jun 1999 22:30:40 -0500
Subject: 2010::/16 filtering
References: <199906251322.GAA01709@boreas.isi.edu>
Message-ID: <37744960.2027182B@hursley.ibm.com>
Bill,
> I think that there is a problem here w/ 6to4 and the subTLA drafts
> taking the same TLA. If this is correct, which would you prefer to keep?
Since I'm on travel, I haven't seen your reply to my assertion that
the subTLA draft allocates 2001::/16, but if I've got that wrong then
6to4 will concede. The actual value doesn't matter in the least.
I was a bit taken aback (and pleased) by the rapid deployment; my
intention is to ask IANA formally for this technical allocation
to be made right after Oslo.
Brian
From bmanning@ISI.EDU Sat Jun 26 04:56:06 1999
From: bmanning@ISI.EDU (Bill Manning)
Date: Fri, 25 Jun 1999 20:56:06 -0700 (PDT)
Subject: 2010::/16 filtering
In-Reply-To: <3773C50A.C5E5B2D2@hursley.ibm.com> from "Brian E Carpenter" at Jun 25, 1999 01:06:02 PM
Message-ID: <199906260356.UAA21462@boreas.isi.edu>
> Richard Draves wrote:
> >
> > > > > Thats a bit much, don't you think? It comprehends the entire
> > > > > range ear-marked
> > > > > for the IANA, the three RIRs and the reserved sub-TLA space.
> > > >
> > > > I don't follow you?
> > > > 2010::/16 is just taking one TLA.
> > > >
> > > > Rich
> > >
> > > Isn't this the one earmarked for subtla assignment?
> >
> > I have no idea. The 6to4 draft says to use TLA 0x0010 so that's what I'm
> > using.
>
> I though the sub-TLA prefix was 2001::/16. Bill please double check
> this; it is rather confusing in the drafts due to the format
> prefix being 3 bits long.
>
> To be clear the sub-TLA prefix is specified as
> > > FP = 001
> > > TLA ID = 0x0001
> which I thought turns into 2001::/16. Tell me if I am confused.
>
> Brian
You are right. 2001 is the subTLA space, 2010 is the 6to4 space.
--bill
From brigm@spawar.navy.mil Mon Jun 28 14:56:45 1999
From: brigm@spawar.navy.mil (Brig, Michael P.)
Date: Mon, 28 Jun 1999 09:56:45 -0400
Subject: What commercial ISPs currently provide IPv6 services or plan to i
n the near future??
Message-ID: <63C0A6A40374D21195510000F8E781DF0167A656@sctern.nosc.mil>
I know Trumpet Software International recently made a press statement that
it is commencing commercial IPv6 service. What other commercial ISPs also
provide IPv6 services today around the world? What ISPs plan to provide IPv6
services within the next 6 months?
thanks...
Michael P. Brig
USN SPAWAR System Center Charleston SC
843-974-4675
brigm@spawar.navy.mil
From platini@fibertel.com.ar Mon Jun 28 19:05:28 1999
From: platini@fibertel.com.ar (Patricio Latini)
Date: Mon, 28 Jun 1999 15:05:28 -0300
Subject: What commercial ISPs currently provide IPv6 services or plan to in the near future??
References: <63C0A6A40374D21195510000F8E781DF0167A656@sctern.nosc.mil>
Message-ID: <003601bec190$cf3cc3f0$d064a8c0@fibertel.com.ar>
now we are giving Point to point conecction with ipv6 and within 3 month we
will give PPP dial limks over ipv6.
------------------------------------------------------
Patricio Sebastián Latini
Network Administrator
Network Operations Center
Fibertel TCI2
Buenos Aires - Argentina
------------------------------------------------------
----- Original Message -----
From: Brig, Michael P.
To: <6bone@ISI.EDU>
Cc: Charlow, Kevin ; Byrnes, Robert
Sent: Monday, June 28, 1999 10:56 AM
Subject: What commercial ISPs currently provide IPv6 services or plan to in
the near future??
> I know Trumpet Software International recently made a press statement that
> it is commencing commercial IPv6 service. What other commercial ISPs also
> provide IPv6 services today around the world? What ISPs plan to provide
IPv6
> services within the next 6 months?
>
> thanks...
>
> Michael P. Brig
> USN SPAWAR System Center Charleston SC
> 843-974-4675
> brigm@spawar.navy.mil
From dancer@zeor.simegen.com Tue Jun 29 00:54:20 1999
From: dancer@zeor.simegen.com (Dancer)
Date: Tue, 29 Jun 1999 09:54:20 +1000
Subject: What commercial ISPs currently provide IPv6 services or plan to in
the near future??
References: <63C0A6A40374D21195510000F8E781DF0167A656@sctern.nosc.mil>
Message-ID: <37780B2C.7E6DC13C@zeor.simegen.com>
"Brig, Michael P." wrote:
> I know Trumpet Software International recently made a press statement that
> it is commencing commercial IPv6 service. What other commercial ISPs also
> provide IPv6 services today around the world? What ISPs plan to provide IPv6
> services within the next 6 months?
>
> thanks...
>
> Michael P. Brig
> USN SPAWAR System Center Charleston SC
> 843-974-4675
> brigm@spawar.navy.mil
>From personal experience, I am aware of quite a few australian ISP's that have
at least one experimental IPv6 box kicking around, and usually a small
cluster...but damned if anyone's using them for anything :/
D
From richdr@microsoft.com Tue Jun 29 19:07:42 1999
From: richdr@microsoft.com (Richard Draves)
Date: Tue, 29 Jun 1999 11:07:42 -0700
Subject: MSR IPv6 Release 1.3
Message-ID: <4D0A23B3F74DD111ACCD00805F31D81014515438@RED-MSG-50>
Microsoft Research and ISI East are pleased to announce Release 1.3 of our
MSR IPv6 stack for Windows NT. See http://www.research.microsoft.com/msripv6
for more details and download information.
The main highlights:
- IPsec support for all combinations of AH & ESP headers, both
transport-mode and tunnel-mode. Note that we only support static keying and
we only support authentication algorithms, not encryption algorithms.
- 6to4 support. See http://www.research.microsoft.com/msripv6/docs/6to4.htm.
In the future we'll automate 6to4 configuration, with a little configuration
applet.
- The usual miscellaneous enhancements and fixes, especially for routing.
To support developers, we're also doing daily source drops. Send email to
msripv6-bugs@list.research.microsoft.com to request more information about
the daily source drops. See
http://list.research.microsoft.com/archives/msripv6-users.html to join our
discussion list or search the archives.
Thanks,
Rich
From richdr@microsoft.com Tue Jun 29 21:35:24 1999
From: richdr@microsoft.com (Richard Draves)
Date: Tue, 29 Jun 1999 13:35:24 -0700
Subject: pTLAs missing in action
Message-ID: <4D0A23B3F74DD111ACCD00805F31D8101451543D@RED-MSG-50>
Does anyone know of any active nodes with addresses belonging to the
following prefixes:
3ffe:800::/24 (ISI-LAP)
3ffe:d00::/24 (ANSNET)
3ffe:e00::/24 (IFB)
3ffe:1500::/24 (UO)
3ffe:1600::/24 (NUS-IRDU)
3ffe:1700::/24 (MREN)
3ffe:1f00::/24 (NETCOM-UK)
3ffe:2700::/24 (ERA)
3ffe:2d00::/24 (GRNET)
3ffe:3000::/24 (AMS-IX)
3ffe:3500::/24 (REGIO-DE)
3ffe:3700::/24 (ABILENE)
3ffe:3800::/24 (FIBERTEL)
3ffe:8010::/28 (ICM-PL)
3ffe:8020::/28 (IIJ)
3ffe:8030::/28 (QTPVSIX)
Either I can't find any DNS names associated with them in the 6bone
registry, or the DNS names that I do find do not resolve.
Thanks,
Rich
From cmj@3com.com Tue Jun 29 23:10:17 1999
From: cmj@3com.com (Cyndi Jung)
Date: Tue, 29 Jun 1999 15:10:17 -0700
Subject: What commercial ISPs currently provide IPv6 services or
plan to in the near future??
Message-ID: <3.0.32.19990629151015.00e796c8@pop.nsd.3com.com>
Maybe you could help linking those ISPs with those people that might be
looking for them. Do you have names of these ISPs? Perhaps those ISPs
have URLs to make it possible for people in their region to get more
information about their IPv6 service offering?
I have heard that Japan has some ISPs offering IPv6 - if anybody
has any useable pointers for them it would be helpful too.
Perhaps URLs for these ISPs with IPv6 service could be added to the
information on the IPv6 websites.
Cyndi
At 09:54 AM 6/29/99 +1000, Dancer wrote:
>"Brig, Michael P." wrote:
>
>> I know Trumpet Software International recently made a press statement that
>> it is commencing commercial IPv6 service. What other commercial ISPs also
>> provide IPv6 services today around the world? What ISPs plan to provide
IPv6
>> services within the next 6 months?
>>
>> thanks...
>>
>> Michael P. Brig
>> USN SPAWAR System Center Charleston SC
>> 843-974-4675
>> brigm@spawar.navy.mil
>
>>From personal experience, I am aware of quite a few australian ISP's that
have
>at least one experimental IPv6 box kicking around, and usually a small
>cluster...but damned if anyone's using them for anything :/
>
>D
>
>
>
>
From richdr@microsoft.com Wed Jun 30 00:10:39 1999
From: richdr@microsoft.com (Richard Draves)
Date: Tue, 29 Jun 1999 16:10:39 -0700
Subject: pTLAs missing in action
Message-ID: <4D0A23B3F74DD111ACCD00805F31D8101451544F@RED-MSG-50>
> $ host -t aaaa amsterdam9.ipv6.ams-ix.net DNS1.microsoft.com
> amsterdam9.ipv6.ams-ix.net AAAA
> 3FFE:3000:0:0:200:CFF:FE37:56F9
Thanks, I can ping that address.
And now I can also lookup that name. Hmm. I was groveling through the
database by hand, I don't remember if I accidentally skipped that host or it
was failing previously.
Rich
From platini@fibertel.com.ar Wed Jun 30 00:20:46 1999
From: platini@fibertel.com.ar (Patricio Latini)
Date: Tue, 29 Jun 1999 20:20:46 -0300
Subject: pTLAs missing in action
References: <4D0A23B3F74DD111ACCD00805F31D8101451543D@RED-MSG-50>
Message-ID: <006b01bec286$04ba3170$d064a8c0@fibertel.com.ar>
richar i think that there is a routing problem between digital ca and your
ptla
------------------------------------------------------
Patricio Sebastián Latini
Network Administrator
Network Operations Center
Fibertel TCI2
Buenos Aires - Argentina
------------------------------------------------------
----- Original Message -----
From: Richard Draves
To: '6bone' <6bone@ISI.EDU>
Sent: Tuesday, June 29, 1999 5:35 PM
Subject: pTLAs missing in action
> Does anyone know of any active nodes with addresses belonging to the
> following prefixes:
>
> 3ffe:800::/24 (ISI-LAP)
> 3ffe:d00::/24 (ANSNET)
> 3ffe:e00::/24 (IFB)
> 3ffe:1500::/24 (UO)
> 3ffe:1600::/24 (NUS-IRDU)
> 3ffe:1700::/24 (MREN)
> 3ffe:1f00::/24 (NETCOM-UK)
> 3ffe:2700::/24 (ERA)
> 3ffe:2d00::/24 (GRNET)
> 3ffe:3000::/24 (AMS-IX)
> 3ffe:3500::/24 (REGIO-DE)
> 3ffe:3700::/24 (ABILENE)
> 3ffe:3800::/24 (FIBERTEL)
> 3ffe:8010::/28 (ICM-PL)
> 3ffe:8020::/28 (IIJ)
> 3ffe:8030::/28 (QTPVSIX)
>
> Either I can't find any DNS names associated with them in the 6bone
> registry, or the DNS names that I do find do not resolve.
>
> Thanks,
> Rich
From platini@fibertel.com.ar Wed Jun 30 00:59:33 1999
From: platini@fibertel.com.ar (Patricio Latini)
Date: Tue, 29 Jun 1999 20:59:33 -0300
Subject: pTLAs missing in action
Message-ID: <00a001bec28b$6f6400a0$d064a8c0@fibertel.com.ar>
This is a multi-part message in MIME format.
------=_NextPart_000_009D_01BEC272.4A10AE20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The fibertel www ipv6 is working good since may it have benn tested with
many members of the 6bone all of them answered to me that they could =
reach
the ipv6 www site.. So i ask again to all the members that cant reackh =
my
site email me to solve the problem.
Thanks for your help
------------------------------------------------------
Patricio Sebasti=E1n Latini
Network Administrator
Network Operations Center
Fibertel TCI2
Buenos Aires - Argentina
------------------------------------------------------
------=_NextPart_000_009D_01BEC272.4A10AE20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The fibertel www ipv6 is working good =
since may it=20
have benn tested with
many members of the 6bone all of them answered =
to me=20
that they could reach
the ipv6 www site.. So i ask again to all the =
members=20
that cant reackh my
site email me to solve the problem.
Thanks =
for=20
your =
help
------------------------------------------------------
Patrici=
o=20
Sebasti=E1n Latini
Network Administrator
Network Operations=20
Center
Fibertel TCI2
Buenos Aires -=20
Argentina
------------------------------------------------------
------=_NextPart_000_009D_01BEC272.4A10AE20--
From jabley@clear.co.nz Wed Jun 30 01:33:24 1999
From: jabley@clear.co.nz (Joe Abley)
Date: Wed, 30 Jun 1999 12:33:24 +1200
Subject: What commercial ISPs currently provide IPv6 services or plan to in the near future??
In-Reply-To: <3.0.32.19990629151015.00e796c8@pop.nsd.3com.com>; from Cyndi Jung on Tue, Jun 29, 1999 at 03:10:17PM -0700
References: <3.0.32.19990629151015.00e796c8@pop.nsd.3com.com>
Message-ID: <19990630123324.A18414@clear.co.nz>
On Tue, Jun 29, 1999 at 03:10:17PM -0700, Cyndi Jung wrote:
> Maybe you could help linking those ISPs with those people that might be
> looking for them. Do you have names of these ISPs? Perhaps those ISPs
> have URLs to make it possible for people in their region to get more
> information about their IPv6 service offering?
>
> I have heard that Japan has some ISPs offering IPv6 - if anybody
> has any useable pointers for them it would be helpful too.
>
> Perhaps URLs for these ISPs with IPv6 service could be added to the
> information on the IPv6 websites.
We're pretty well-connected to Australia, and have an IPv6 router
available for people to connect to:
http://www.clear.net.nz/
Look for CLIX-NG in whois.
Joe
From rsofia@rccn.net Wed Jun 30 15:47:02 1999
From: rsofia@rccn.net (Rute Sofia)
Date: Wed, 30 Jun 1999 15:47:02 +0100 (WET DST)
Subject: DiffServ and IPv6
Message-ID:
Hi.
I would like to know if anyone's working in DiffServ but specifically
with IPv6, besides the use of the Traffic Class field as the DS byte.
Does anyone have any ideas on this? If yes, could you please point out
some links or papers on the subject ?
Thanks,
Rute Sofia
---------------------------------------------------
Helena Rute Esteves Carvalho Sofia
FCCN
Av. do Brasil, 101
1799 LISBOA CODEX
tel.: 8440115
fax: 8472167
e-mail: rsofia@rccn.net
"After silence, that which comes nearest to expressing
the inexpressible is Music." - Aldous Huxley
---------------------------------------------------
From phoenix1@pacbell.net Wed Jun 30 16:53:45 1999
From: phoenix1@pacbell.net (Luis Paz Ph. D.)
Date: Wed, 30 Jun 1999 08:53:45 -0700
Subject: What commercial ISPs currently provide IPv6 services or plan to in
the near future??
References: <63C0A6A40374D21195510000F8E781DF0167A656@sctern.nosc.mil>
Message-ID: <377A3D89.9CBC424D@pacbell.net>
Michael; AboveNet can support IPv6
here is contact information if you need it.
"Brig, Michael P." wrote:
> I know Trumpet Software International recently made a press statement that
> it is commencing commercial IPv6 service. What other commercial ISPs also
> provide IPv6 services today around the world? What ISPs plan to provide IPv6
> services within the next 6 months?
>
> thanks...
>
> Michael P. Brig
> USN SPAWAR System Center Charleston SC
> 843-974-4675
> brigm@spawar.navy.mil
--
Respectfully,
Luis Paz Ph.D.
Phoenix1@pacbell.net
206 328-9732
"I have not doubt the devil grins
At these seas of ink I spatter
Yea gods forgive my literary sins
For the other kind don't matter"
-Robert Service
From richdr@microsoft.com Wed Jun 30 19:30:37 1999
From: richdr@microsoft.com (Richard Draves)
Date: Wed, 30 Jun 1999 11:30:37 -0700
Subject: pTLAs missing in action
Message-ID: <4D0A23B3F74DD111ACCD00805F31D8101451545D@RED-MSG-50>
OK, some progress... now the list of pTLAs for which I have no addresses to
ping is
3ffe:800::/24 (ISI-LAP)
3ffe:d00::/24 (ANSNET)
3ffe:1500::/24 (UO)
3ffe:1600::/24 (NUS-IRDU)
3ffe:1700::/24 (MREN)
3ffe:1f00::/24 (NETCOM-UK)
3ffe:2700::/24 (ERA)
3ffe:2d00::/24 (GRNET)
3ffe:3500::/24 (REGIO-DE)
3ffe:3700::/24 (ABILENE)
3ffe:8010::/28 (ICM-PL)
3ffe:8030::/28 (QTPVSIX)
I have found test-gw.ipv6.regio.net but it resolves to a 3ffe:400::/24
address. And 6bone-gw.6bone.pl resolves to a 3ffe:900::/24 address.
Some DNS names in the registry associated with the above pTLAs, that do not
resolve to AAAA addresses:
sandbox.ep.net
6bone.wtn.ans.net
6bone-gw.uoregon.edu
ipv6-gw.6bone.cir.nus.edu.sg
6bone-gw1.ar.singaren.net.sg
r-x-mren.fnal.gov
beavis.ip6.netcom.net.uk
ip6-gw.ip6.netcom.net.uk
tom.testbed.era.ericsson.se
6bone-gw.testbed.era.ericsson.se
ipv6-gw.grnet.gr
ifigenia.ipv6.cs.teiath.gr
ocarine.ariadne-t.gr
6bone.regio.net
6bone-gw.regio.net
zatoka.icm.edu.pl
Thanks,
Rich
From brian@hursley.ibm.com Wed Jun 30 22:09:06 1999
From: brian@hursley.ibm.com (Brian E Carpenter)
Date: Wed, 30 Jun 1999 16:09:06 -0500
Subject: DiffServ and IPv6
References:
Message-ID: <377A8772.11875F88@hursley.ibm.com>
Diffserv only uses the Traffic Class field, and operates identically
for IPv4 and IPv6. It would be interesting to hear if anyone
has implemented diffserv for IPv6 so far, but there should be no
difference from IPv4.
Brian
Rute Sofia wrote:
>
> Hi.
>
> I would like to know if anyone's working in DiffServ but specifically
> with IPv6, besides the use of the Traffic Class field as the DS byte.
>
> Does anyone have any ideas on this? If yes, could you please point out
> some links or papers on the subject ?
>
> Thanks,
>
> Rute Sofia
>
> ---------------------------------------------------
> Helena Rute Esteves Carvalho Sofia
> FCCN
> Av. do Brasil, 101
> 1799 LISBOA CODEX
> tel.: 8440115
> fax: 8472167
> e-mail: rsofia@rccn.net
> "After silence, that which comes nearest to expressing
> the inexpressible is Music." - Aldous Huxley
>
> ---------------------------------------------------
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter (IAB Chair)
Program Director, Internet Standards & Technology, IBM Internet Div
As of May 24, 1999: on assignment for IBM at http://www.iCAIR.org
Non-IBM email: brian@icair.org