- ipv6-wg - mailman.ripe.net

RE: [ipv6-wg@ripe.net] IPv6, future internet, hierarchy
by Michel Py 12 Feb '03

12 Feb '03

> Do the ops types include people like me who worry that every > time a NIC has to be replaced it's going to require changes > to DNS, ACLs and anything else that's keyed on IP address? Mmm, I don't know. I'm the kind of ops type that also reads RFCs and understand the importance of respecting standards. From an operational standpoint, it pays off in the long run. I would never configure a server or router with an IPv6 address that includes some part of the BIA, but I try to respect standards too, and even the current standard could be respected although its clumsiness definitely makes modified EUI-64 desirable. Michel.

1 0

RE: [ipv6-wg@ripe.net] IPv6, future internet, hierarchy
by Michel Py 12 Feb '03

12 Feb '03

Robert, > There are a number of advantages of non-/64 for p2p. For example, > you can have an easy address allocation scheme like ...: > <routernumber>:<index>:<host id>" which does not require any > bookkeeping. That's not possible with /64 addresses. You are completely mistaken. Using your own example: Hostid = 0xcafe Index = 0x77 Routernumber = 0xbeef I'll even go over an EUI-64/RFC2373 example although it's going to be obsolete real soon. +-----+---------+---------+-------+--------------+ | 8 | 16 | 16 | 8 | 16 | | | hostid | | index | routernumber | +-----+---------+---------+-------+--------------+ 02 ca : fe FF : FE 77 : beef The long way: ------------- cisco3640#conf t cisco3640(config)#inte e0/0 cisco3640(config-if)#mac-address ca.fe77.beef cisco3640(config-if)#ipv6 address 2001:db8::/64 eui-64 cisco3640(config-if)#end cisco3640#sh ipv6 inte e0/0 Global unicast address(es): 2001:DB8::2CA:FEFF:FE77:BEEF, subnet is 2001:DB8::/64 ^^ ^^ ^^ ^^^^ \\|| || |||| CAFE 77 BEEF The short way: cisco3640#conf t cisco3640(config)#inte e0/0 cisco3640(config-if)#ipv6 address 2001:db8::02CA:FEff:fe77:BEEF/64 This is compliant with EUI-64 and RFC 2373. As I said before, we're talking about straight EUI-64 here and this is soon to be obsoleted. The replacement for RFC2373 (draft-ietf-ipngwg-addr-arch-v3-11.txt) uses _modified_ EUI-64, and you can do almost whatever you want, such as: ipv6 address 2001:db8::02CA:FE00:0077:BEEF/64 ipv6 address 2001:db8::02:CAFE:77:BEEF/64 ipv6 address 2001:db8::1/64 All of which are compliant modified EUI-64 addresses. > The standard also requires EUI-64 addresses which is clearly > not desirable for a number of application. For example, it would > be very silly to require a change all your peering sessions just > because you change your NIC. There is no relation. You can construct an EUI-64 or a modified EUI-64 address without using the BIA, what's your problem here? Michel.

2 1

RE: [ipv6-wg@ripe.net] IPv6, future internet, hierarchy
by Michel Py 12 Feb '03

12 Feb '03

> Jeroen Massar > Thus 2001:db8::1 is a 'modified' EUI-64 and thus can be > assigned. You are just lying a bit that the local scope > id is not available and thus you are making it up, but > you do correctly set it as per RFC. Easy to fix, make it 2001:db8:2::1 Michel.

1 0

[ipv6-wg@ripe.net] urls with ipv6 ip.
by Priyaupnp＠netscape.net 06 Feb '03

06 Feb '03

hi all, I couldn't load a loacal page from my linux system with IPv6 link local IP,(The browser used was netscape7). When the site local ip is added to the system, could load the page using that ip. Is it possible to load a page with link local ip using netscape or any other browser. Thanks in advance. Regards Pria __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

3 2

[ipv6-wg@ripe.net] ANNOUNCEMENT: IPv6 support for RIPE NCC TTM Service
by Henk Uijterwaal (RIPE-NCC) 03 Feb '03

03 Feb '03

Dear All, (Apologies for any duplicate mails). The RIPE NCC is pleased to announce full IPv6 support for its test-boxes and Test Traffic Measurement Service (TTM). This new version can do all the measurements that the previous version could do on IPv4 networks, but now on IPv6. Measurements can be done on IPv4 and IPv6 networks in parallel. Most of the porting work has been done by Florian Frotzler, an CS student doing an Internship at the RIPE NCC. It is described in more detail in an internal report available at: http://www.ripe.net/ttm/Documents/Various/florian_xmas.pdf as well as in the slides of his presentation at RIPE44 last week: http://www.ripe.net/ripe/meetings/archive/ripe-44/presentations/ripe44-tt-i… IPv6 support will be included on all test-boxes ordered after 1/2/2003. To order a test-box, please go to: http://www.ripe.net/ttm/Host_testbox/host_testbox.html If you are already hosting a test-box and want to upgrade to the IPv6 enabled version, then please find instructions for upgrading at the bottom of this mail. If anything is unclear, please contact us at ttm(a)ripe.net. More about the TTM service can be found at: http://www.ripe.net/ttm Kind regards, Henk Uijterwaal Instructions for upgrading test-boxes ===================================== If you already own a test-box and want to upgrade to the IPv6-capable version of the software, then this is the procedure: 1. Determine the version of your test-box. This can be series A, B, C or D. Series D boxes are 1u high and manufactured by Dell. Series C boxes are all boxes delivered after 1/1/2001. A or B are boxes delivered before 1/1/2001. 2. Your box is series A or B: 1. In this case, a hardware upgrade to a series D box will be necessary. The (usually 3-5 years) old hardware does not support v6. 2. Series D boxes cost 2,500 euro, however, if you return your old box, you will get a 500 euro discount. 3. Send an email with a v6 address to tt-ops(a)ripe.net 4. A new box will be configured and shipped. 5. Schedule a time to unplug the old box and plug in the new box with our operators. 3. Your box is series C or D: 1. Send an IPv6 address to tt-ops(a)ripe.net 2. Our operators will schedule a time for the upgrade 3. You will have to download a boot floppy from our ftp site. 4. At the time of the upgrade, boot with the floppy. Note that we will only do this upgrade if all outstanding invoices have been paid and the service contract for the existing box has been signed. ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ That problem that we weren't having yesterday, is it better? (Big ISP NOC)

1 0

[ipv6-wg@ripe.net] Connection IPv6
by Jordi Bort 31 Jan '03

31 Jan '03

Hi, We have one /32 IPv6 prefix (2001:a50::). At the moment we have some VLANs with IPv4 traffic on two Catalyst 6500. The tunneling between IPv4-IPv6 works fine, as does the DNS-v6. Now we would like to connect ourselves with the International IPv6 Network. Does anyone know how to do it? Shall we announce our prefix? Is it possible for RIPE to connect our IPv6 network? Thanks,

3 2

[ipv6-wg@ripe.net] IPV6 Whois
by DB-News 24 Jan '03

24 Jan '03

[apologies for duplicate messages] Dear Colleagues, We are happy to announce the availability of RIPE Whois servers on IPv6 network. It is now possible to query whois.ripe.net and test-whois.ripe.net from an IPv6 host, using an IPv6 enabled whois client. If your system doesn't already have one, you can find the latest RIPE Whois client at: ftp://ftp.ripe.net/ripe/tools/ripe-whois-latest.tar.gz You can read the full anouncement at: http://www.ripe.net/ripencc/pub-services/db/whois-ipv6.html Best regards, -- Can Bican Database Group RIPE NCC

4 4

[ipv6-wg@ripe.net] IPv6 Whois update
by Shane Kerr 23 Jan '03

23 Jan '03

Colleagues, As you may have seen on the list, there were a few reachability problems with the new IPv6 Whois service. We believe these are configuration related, and have a workaround allowing queries to WHOIS.RIPE.NET to work while we research it further. If you have network issues with this service please e-mail <ripe-dbm(a)ripe.net>. We also have heard some problems people are having with their Whois clients giving them errors querying the RIPE Whois server. These can occur in the case that: - The Whois client has IPv6 support. - The host computer does not have working IPv6 support. The client will: 1. Get the AAAA record for WHOIS.RIPE.NET. 2. Try to connect to the IPv6 address. 3. Fail because there is no IPv6 stack/address/router/etc. If you are experiencing this problem, you may be able to fix it by enabling IPv6 on your host (so that the IPv6 queries work), disabling IPv6 *completely* on your host (so that no AAAA records are returned), or by using another Whois client. The RIPE Whois client will work in this case, and is available from our FTP site: ftp://ftp.ripe.net/tools/ripe-whois-latest.tar.gz -- Shane Kerr RIPE NCC

3 2

RE: [ipv6-wg@ripe.net] IPV6 Whois
by matthew.ford＠bt.com 23 Jan '03

23 Jan '03

I'm getting Type 1 (Unreachable) Code 1 (Administratively Prohibited) messages back from 2001:7f8:1::a500:3333:1 - luckily the client falls back to IPv4 and that works just fine ;-) Mat. > -----Original Message----- > From: Pim van Pelt [mailto:pim@ipng.nl] > Sent: 23 January 2003 14:17 > To: ripe-dbm(a)ripe.net > Cc: db-wg(a)ripe.net; ipv6-wg(a)ripe.net > Subject: Re: [ipv6-wg(a)ripe.net] IPV6 Whois > > > | We are happy to announce the availability of RIPE Whois > servers on IPv6 > | network. It is now possible to query whois.ripe.net and > test-whois.ripe.net > | from an IPv6 host, using an IPv6 enabled whois client. If > your system doesn't > | already have one, you can find the latest RIPE Whois client at: > Hi Can, > > I cannot reach the server from AS12859, nor from AS8954. > > --- whois.ripe.net ping6 statistics --- > 2 packets transmitted, 0 packets received, 100% packet loss > > A traceroute from me (2001:7b8:3:17:202:b3ff:fe10:d926) to you gives: > 1 dapje-gw.ipv6.network.bit.nl 0.383 ms 0.286 ms 0.269 ms > 2 jun1.telecity.ipv6.network.bit.nl 1.537 ms 1.552 ms 1.505 ms > 3 nikipv6.ripe.net 3.378 ms 3.035 ms 3.111 ms > 4 nikipv6.ripe.net 4.432 ms !P 3.248 ms !P 3.288 ms !P > > And telnetting to port 43 of whois.ripe.net does not do much: > $ telnet 2001:610:240:0:193::135 whois > Trying 2001:610:240:0:193::135... > ^C > > Please advise. > -- > ---------- - - - - -+- - - - - ---------- > Pim van Pelt Email: pim(a)ipng.nl > http://www.ipng.nl/ IPv6 Deployment > ----------------------------------------------- > >

1 0

[ipv6-wg@ripe.net] New Documents available: RIPE-263, RIPE-267
by RIPE NCC Document Announcement Service 22 Jan '03

22 Jan '03

New RIPE Documents Announcement -------------------------------------- Two new documents are available from the RIPE document store. Ref: ripe-263 Title: Autonomous System (AS) Number Assignment Policies and Procedures Author: Mirjam Kuehne, Nurani Nimpuno, Sabrina Wilmot Date: 22 January 2003 Format: PS=16292 TXT=6248 Obsoletes: ripe-185, ripe-245 Obsoleted by: Updates: Updated by: Ref: ripe-267 Title: IPv6 Address Allocation and Assignment Policy Author: ARIN, APNIC, RIPE NCC Date: 22 January 2003 Format: PS=816883 TXT=34295 Obsoletes: ripe-196, ripe-246 Obsoleted by: Updates: Updated by: Short content description ------------------------- The "Autonomous System (AS) Number Assignment Policies and Procedures" provides a description of Autonomous System Numbers, their assignment procedures and guidelines on how to obtain them in RIPE NCC service region. "Assignments for Internet Experiments" has been included in this latest version. The "IPv6 Address Allocation and Assignment Policy" defines registry policies for the assignment and allocation of globally unique IPv6 addresses to Internet Service Providers (ISPs) and other organisations. "Assignments for Internet Experiments" has been included in this latest version. Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website at the following URLs:. http://www.ripe.net/ripe/docs/asn-assignment.html http://www.ripe.net/ripe/docs/ipv6policy.html The RIPE Document Store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-263.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-263.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-267.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-267.txt plain text version

1 0