- ipv6-wg - mailman.ripe.net

v6 Countries...
by Carlos Friacas 12 Sep '02

12 Sep '02

David, .DO is the Dominican Republic (on the caribeean). I've been disappointed with the 58 figure... and im not sure if some of these 58 have real users... some less-developed countries resources are being run on europe or states. Can you detail a bit more how is this count being done? UN has 190 members, there is yet a long, long, long (...) path to go... Thanks in advance, ./Carlos "Networking is fun!" -------------- [http://www6.ip6.fccn.pt, IPv6 only] http://www.fccn.pt <cfriacas(a)fccn.pt>, CMF8-RIPE, CF596-ARIN, Wide Area Network Workgroup F.C.C.N. - Fundacao para a Computacao Cientifica Nacional fax: +351 218472167

5 7

Renater & G6 - Conférence IPv6 2002 - Paris
by Bernard Tuy 12 Sep '02

12 Sep '02

Dears, For an unknown reason I was noticed this information didn't spread out though I sent it at the end of the IPv6 wg meeting yesterday. Anyway, here it is again. See you soon in Paris then ... Cheers. +Bernard Tuy. info on the conference at *http://www.renater.fr/IPv6-2002/

1 0

M6Bone : IPv6 Multicast Service
by Bernard Tuy 11 Sep '02

11 Sep '02

As asked by the IPv6 wg chair, please find the URL of the M6bone project deploying IPv6 multicast network and currently exchanging data over videoconferncing tools You can also join the mailing list as described in these pages. Enjoy, +Bernard T. --- http://sem2.renater.fr/m6bone/

1 0

Re: draft agenda (v2) RIPE43
by Wilfried Woeber, UniVie/ACOnet 10 Sep '02

10 Sep '02

>> Isnt this proposed topic of the kind: >> "See? no traffic, we should shut down IPv6!!! Nobody is using it!!!" >> or >> "Bahhhh, i was right... IPv6 is worthless..." Those who support that point of view would do so anyway, either backed by real data or by data made up on the fly :-) >no. it is wanting baseline measurement. e.g. apnic is tracking >hits on ip6.int service. > >five years from now, we will wish we have such data. > >randy Randy, I agree. Nevertheless a brief summary on projects (looking at quality instead of sheer "volume") would still be interesting, I guess. Wilfried. PS: David, I can bring a few minutes' worth of snap-shot info for our sandbox.

6 6

Agenda RIPE43
by David Kessens 06 Sep '02

06 Sep '02

Hi, Below follows the agenda for the ipv6 wg. Please note that after discussion between me and the working group chairs of the lir working group, we decided to move the topic of '6Bone Address Allocation and Registration Transition' to the lir working group. Also, you are all invited to the ipv6 tutorial which has been scheduled on monday. See my earlier mail for more details. Thanks & I hope to see you all in Rhodes! David K. --- Agenda for the IPv6 Working Group Meeting RIPE43 September 11, 2002, 14:00 - 17:30, Rhodes, Greece 1st slot A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. IPv6 version of TTM (Henk Uijterwaal) D. Action point 42.1: Investigate the CNAME and other solutions for v6-reverse delegation (RIPE NCC) E. IPv6 capable RR DNS servers - what is needed, what are the issues ?!? (RIPE NCC) F. Action point 42.2: Give an overview of 6-to-4 reverse delegation issues at RIPE 43 (RIPE NCC) G. Global IPv6 routing table status (Gert Doering) Coffee break 15:30 - 16:00 H. Report(s) about *actual* v6 traffic volume as compared to v4? what's *real* out there, not what's on powerpoint? - baseline measurement for ipv6.int queries (Terry Manderson, APNIC) - some snap-shot info (Wilfried Woeber) - more reports are welcome! we will also have a discussion whether we can do something as a working group in this area I. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Z. AOB ---

1 0

draft agenda (v2) RIPE43
by David Kessens 30 Aug '02

30 Aug '02

Hi, Below follows the second version of the draft agenda (v2) for the ipv6 wg. The proposed agenda for the ipv6 working group still has quite some room for other topics/presentations. I would very much welcome your input on other interesting topics that you might want to volunteer yourself or somebody else for. There are a couple of items that ask for 'input of the audience' or 'need a volunteer'. Please don't hesitate to contact me if you are willing to help out, even if you can only talk for just a few minutes. Also, you are all invited to the ipv6 tutorial which has been scheduled on monday. See my previous mail for more details. Thanks, David K. --- Draft agenda (v2) for the IPv6 Working Group Meeting RIPE43 September 11, 2002, 14:00 - 17:30, Rhodes, Greece 1st slot A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. 6Bone Address Allocation and Registration Transition (Ray Plzak) D. IPv6 version of TTM (5-10m) (Henk Uijterwaal) E. Action point 42.1: Investigate the CNAME and other solutions for v6-reverse delegation (RIPE NCC) F. IPv6 capable RR DNS servers - what is needed, what are the issues ?!? (We are looking for a speaker from the RIPE NCC) G. Action point 42.2: Give an overview of 6-to-4 reverse delegation issues at RIPE 43 (RIPE NCC) Coffee break 15:30 - 16:00 H. Global IPv6 routing table status (Gert Doering) I. Report about *actual* v6 traffic volume as compared to v4? what's *real* out there, not what's on powerpoint? (Proposed by Randy Bush, we are looking for a volunteer(s)) J. DNS and IPv6 - issues and current BCP: draft-ietf-dnsext-ipv6-addresses-01.txt (I am looking for a volunteer who is willing to cover this topic) K. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Z. AOB ---

6 6

FW: Proposal for Transfer of 6bone Address Management Responsibilities to RIRs
by leo vegoda 26 Aug '02

26 Aug '02

Dear Colleagues, It has been proposed that the management of the 6bone 3FFE::/16 address space be transferred to the Regional Internet Registries (RIRs). More information about the 6bone can be obtained at: <http://www.6bone.net/> At a recent 6bone meeting, Bob Fink made a proposal for this management transfer. A copy of the presentation slides are available at: <http://www.6bone.net/ngtrans/minutes/default.htm> or at: <http://www.apnic.net/meetings/14/sigs/policy/index.html> These presentation slides were based on the text, "Policies for transfer of 6bone address management responsibilities to RIRs," provided below. Please send your comments about this proposal to the LIR WG mailing list <lir-wg(a)ripe.net>. The 6bone and other RIRs will be conducting similar reviews within their communities and the RIPE NCC will summarise the collective responses, issues, and concerns, made in regard to this proposal. This review process will end on December 31, 2002. Regards, -- leo vegoda RIPE NCC Registration Services ----- Forwarded message ----- ******************* Policies for transfer of 6bone address management responsibilities to RIR Version: 20 August 2002 1. Introduction 6bone was established in 1996 as a continuing IPv6 test bed with the original purpose of testing of standards and implementations, and the more current focus on testing of transition and operational procedures, as well as application conversion. It provides an opportunity for those wanting early experience and/or needing to experiment with IPv6, with a minimum of startup complexity, particularly in terms of address management policies, and at minimal cost. It also provides an open peer process for information, hookup help, and support, with strong ties to the IETF process as well as to the operational community. To date, 6bone address space has been allocated and registered in an informal process quite separate from the existing Regional Internet Registry system. The purpose of this proposal is to establish a long term model that provides for a more "official" home for 6bone address space management within the established Internet administrative structures. At the same time, the proposal recognizes that 6bone's most important functions as an accessible and informal test bed network must be maintained. This document proposes the transfer of responsibility for administration of 6bone address space (3ffe::/16) to the Regional Internet Address Registries (RIRs). It describes a set of policies and procedures for this transfer, and for the ongoing administration of 6bone address space within the RIR framework. It should be noted that the ongoing operation of the 6bone, and policies related to it, are still the purview of the 6bone community itself. For example, 6bone network compliance with the 6bone routing guidelines is a matter for the community itself to resolve, typically by mail lists. It is also important to continue the strongly volunteer efforts of the 6bone, both to make it as easy and friendly as possible for individuals, sites and networks to experiment and learn about IPv6, but also to keep the process streamlined and cost-effective. 2. Definitions a) "6bone" and "6bone community", as it appears in section 3 below, means 6bone organizations and individuals including the RIRs, "6bone members" (see below), and those participating in the 6bone mail list. b) 6bone members are defined as entities which are approved for address space allocation by the 6bone community in accordance with 6bone policies, and who agree to be bound by those policies and the policies stated below. c) 6bone allocations are allocations of 6bone address space which are held by 6bone members, or made to 6bone members in accordance with these policies. d) 6bone address space is defined as IPv6 address space within the 3ffe::/16 address block. 3. Policies 3.1 General a) In consultation with 6bone, RIRs will implement a common set of policies applying specifically to 6bone allocations. This will follow the current RFC2772, "6Bone Backbone Routing Guidelines" and/or successor documents resulting as an evolution of conversations in the 6bone community and the RIRs.; b) 6bone members will be served by respective RIR in their region, for "6bone Address Services" including 6bone address allocation, database registration and maintenance, and ip6.arpa registration (as described below); c) In order to receive 6bone address services from an RIR as described here, each 6bone member must "join" that RIR, that is, enter into the appropriate membership or services agreement with the RIR. d) RIR fees will be waived for 6bone address services provided by RIRs to 6bone members (but not for other services 6bone members may require), until 1 year after this agreement starts. After this time each RIR may charge an administration fee to cover each allocation made. This fee simply covers registration and maintenance, rather than the full allocation process for standard RIR members. This administration fee should be as low as possible as these requests do not have to undergo the same evaluation process as those requested in the normal policy environment. e) Organizations may receive 6bone address services from the RIR only on approval by 6bone, and in accordance with these policies; f) 6bone members will have the option to receive other services from an RIR (including allocation of production IPv6 address space), by following the policy, process and procedures in place at the time of application for those services. g) Continuing compliance with 6bone policies, and with the policies defined here, will be verified by 6bone at least every 2 years; 3.2 6bone Address Services a) 6bone Address Services include allocation of 6bone address space, registration and maintenance of database records relating to that address space, and registration of ip6.arpa records; b) 6bone address space allocations will be made from 3ffe::/16 and only /32 prefixes will be allocated. There will be exceptions for unusual and new proposals per joint RIR and 6bone review and approval. A relevant example of this is one or more new strategies such as geographic or metro addressing; c) No additional 6-bone address space will be allocated to any 6bone member (therefore no provision will be made for aggregation of multiple allocations, reservations etc); d) 6bone address services will be provided strictly for experimental, non-commercial use; e) Allocations will be made on the clear and stated understanding that the prefix 3ffe::/16 has a limited lifetime. The dates for the termination of allocation from the prefix and the expiration of the prefix will be determined at a future date. The RIRs will not participate in these determinations. f) 6bone address space will be returned to the RIR when no longer in use, when reclaimed due to non-compliance with 6bone or RIR policies, or when 3ffe: space is finally withdrawn; g) Registration of 6bone address space within the ip6.int zone is not covered by this policy, and is at option of 6bone member; h) Registration of 6bone sites, maintainers, persons and address space within the existing consolidated 6bone registry is not covered by this policy, and is at option of 6bone and its current policies. 3.3 Transfer of existing 6bone members a) Responsibility for existing 6bone members in respect of services described here will be transferred from 6bone to the respective RIR, at the option of those members individually, on entering into the appropriate agreement with the RIR; b) On joining the RIR, 6bone address registration records for the member concerned will be transferred from 6bone registry to the respective RIR database; c) On joining the RIR, 6bone members may establish ip6.arpa delegation records in accordance with applicable RIR procedures; d) Legacy holders will use RIR administrative procedures for management of their records; e) There will be a sunset (2 years?) on existing 6bone members not transferring to RIR administrative procedures, after which their address allocation will be revoked. ----- End forwarded message -----

1 0

IPv6 Tutorial
by David Kessens 23 Aug '02

23 Aug '02

Please see below for more information on the IPv6 tutorial. Thanks, David K. --- ------------------------------------------------------------------------ IPv6 tutorial Monday 9/9/2002, 14:00 - 17:30, Rhodes, Greece The success of the Internet has lead to an increased usage and requirement of IP addresses. IPv6 is the new generation of the Internet Protocol. It was introduced to help overcome the limitations of the current version (IPv4). The tutorial will introduce IPv6 and the transition mechanisms that can be used to ease the migration towards IPv6. Apart from the address space extension (IPv6 address is 128 bit long compared to the 32 bit long addresses in IPv4), IPv6 makes equipment autoconfiguration possible. Moreover, thanks to the very large space of global IPv6 addresses, usage of palliatives such as NATs will decrease and end-to-end communication, which is one of the basic principles of IP, will become again possible. There will be no D day to migrate from IPv4 to IPv6. IPv6 deployment started years ago and several transition mechanisms have been proposed by the IETF ngtrans working group to help networkers choose the appropriate migration strategies. Among others, the tutorial will be presented by: Bernard Tuy, Renater - G6, France Mohsen Souissi, AFNIC - G6, France ------------------------------------------------------------------------

1 0

E-mail address masquerading for archived mail messages
by RIPE NCC WebMaster 16 Aug '02

16 Aug '02

Dear Colleagues, [Apologies for duplicate mails] Beginning today, 16 August, the RIPE NCC will implement "e-mail address masquerading" for messages displayed on the web site in the RIPE and the RIPE NCC mailing list archives. E-mail masquerading makes it more difficult for spammers to harvest e-mail addresses from the mailing list archives. When masquerading is applied, the e-mail address of the sender will be hidden in the mail archived messages. Those reading archived mail will see a return e-mail address that appears as "<somebody@localhost>". When clicking on this e-mail address, the address of the original sender will be loaded in your mail program, enabling you to send a message to the author. The RIPE NCC has chosen to implement this security measure as there have been various complaints from members of the RIPE community that e-mail addresses were being abused by spammers for Unsolicited Bulk E-mail (UBE). By implementing this security measure we anticipate there will be a sharp reduction to address harvesting of archived e-mail addresses. We will be checking for harvesters who manage to overcome this measure and will take further steps if necessary. E-mail masquerading will be applied to all mailing lists found in the following directories: http://www.ripe.net/ripencc/mail-archives/ http://www.ripe.net/ripe/mail-archives/ We appreciate your understanding on this matter. Regards Jeroen Bet RIPE NCC WEBMASTER ==================

1 0

Updating inet6num objects with a legacy status attribute
by leo vegoda 06 Aug '02

06 Aug '02

Dear Colleagues, The RIPE Database server, whois.ripe.net, has been updated to allow the new status attributes specified in the document: "New Values of the 'status:' Attribute for inet6num Objects" <http://www.ripe.net/docs/new-value-status.html> The status values of all inet6num objects maintained by the RIPE NCC have been updated as appropriate. We would be grateful if everyone maintaining inet6num objects would update them to use the new status attribute values. The RIPE NCC will use the "ASSIGNED" status value to determine the HD ratio when it receives a request for an additional IPv6 allocation. A request form for additional IPv6 allocations will be published in the near future. Best regards, -- leo vegoda RIPE NCC Registration Services

1 0