- ipv6-wg - mailman.ripe.net

Agenda for IPv6 working group RIPE40
by David Kessens 21 Sep '01

21 Sep '01

Hi, Below follows the official agenda for the ipv6 wg. We will only meet for one meeting slot for the regular working group session due to all the attention for ipv6 in other (joint) sessions. There will be an ipv6 tutorial on monday, and two joint sessions on ipv6 allocation policy. One session will be used to discuss the interim policy on ipv6 assignments for exchange points and the other session will be used to make progress on the revision on the general allocation guidelines of ipv6 adresses. A separate agenda will be published regarding these sessions. Please let me know if you have any other last minute topics that you want to have discussed and I will try to accomodate them. Thanks, David K. --- Agenda for the IPv6 Working Group Meeting RIPE40, Prague Tuesday, October 2nd, 2001, 16:00 - 17:30 A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. Addressing on cable systems (Pascal Julienne) D. Global IPv6 routing table status (Gert Doering & input of the audience requested) E. Discussion on RPSL and IPv6 routing policies (Florent Parent) F. Euro6IX: The Pan-European IPv6 IX Backbone (Jordi Palet Martinez) G. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Z. AOB ---

1 0

DNS root servers
by Miguel Angel Sotos - NOC 19 Sep '01

19 Sep '01

Hi all, We want to configure an IPv6 only DNS, Is there any root servers for IPv6? Or does the server need to have IPv6+IPv4 to access the IPv4 root servers? Thanks in advance, Miguel Angel.

3 2

WG: Document Action: IPv6 multihoming support at site exit routers to Informational
by Thomas Trede 14 Sep '01

14 Sep '01

FYI. Regards, Thomas Trede -----Ursprï¿½ngliche Nachricht----- Von: owner-ipng(a)sunroof.eng.sun.com [mailto:owner-ipng@sunroof.eng.sun.com]Im Auftrag von The IESG Gesendet: Donnerstag, 13. September 2001 19:41 An: IETF-Announce: Cc: RFC Editor; Internet Architecture Board; ipng(a)sunroof.eng.sun.com Betreff: Document Action: IPv6 multihoming support at site exit routers to Informational The IESG has approved the Internet-Draft 'IPv6 multihoming support at site exit routers' <draft-ietf-ipngwg-ipv6-2260-02.txt> as an Informational RFC. This document is the product of the IPNG Working Group. The IESG contact persons are Erik Nordmark and Thomas Narten. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

The IX assignment Issue
by David Gethings 12 Sep '01

12 Sep '01

Hi All, I know RIPE NCC has already published is policy on assigning IX's with IPv6 address space, so apologies for coming in late on this issue. I've recently came across RFC 2928 (Initial IPv6 Sub-TLA ID Assignments). The last paragraph of Section 3 of this informational RFC says: "The block of Sub-TLA IDs assigned to the IANA (i.e., 2001:0000::/29 - 2001:01F8::/29) is for assignment for testing and experimental usage to support activities such as the 6bone, and for new approaches like exchanges." Does the RIPE NCC policy follow this RFC? It was written in Sept 2000, and could be out of date. I'm just looking for clarification. Regards -- David Gethings Worldcom, Network Activation Engineer Internet House, 332 Science Park, Email: davidg(a)uk.uu.net Cambridge, CB4 0BZ, United Kingdom. Phone: +44 (0)1223 581515 http://www.uk.uu.net/

1 0

draft agendas (v1) for IPv6/lir/eix joint sessions RIPE40
by David Kessens 11 Sep '01

11 Sep '01

Hi, Below follow the first drafts of the agendas for the joint sessions regarding ipv6 allocation policies. We have asked to schedule two seperate sessions, one for discussions regarding the new interim policy for exchange points, and one for discussions regarding the revision of the general allocation guidelines. We would like to limit discussion to the lir-wg maillist to minimize the amount of duplicate mails. Please let me know if you have any other topics that you want to have discussed and we will try to accomodate them in the agenda. Thanks, David K. --- Agenda for the IPv6/lir joint session RIPE40, Prague Topic: Revision of the general ipv6 allocation guidelines Materials to read: - ripe-196: http://www.ripe.net/ripe/docs/ipv6policy.html - http://www.ripe.net/ripe/meetings/archive/ripe-39/presentations/ipv6develop… - http://www.djp.net/ipv6/proposal.html - http://www.ripe.net/ripe/meetings/archive/ripe-39/presentations/RIPE39-IPv6… A. Administrative stuff - appointment of scribe - agenda bashing B. How to proceed for the next iteration of the policy. C. Status of the draft currently being discussed between the RIRs (Presentations from RIRs) D. Proposal for the next version of the policy http://www.djp.net/ipv6/proposal.html (Dave Pratt) E. Discussion Z. AOB ------------------------- Agenda for the IPv6/lir/eix joint session RIPE40, Prague Topic: Interim policy for allocation of ipv6 addresses for Internet Exchange Points A. Administrative stuff - appointment of scribe - agenda bashing B. How to proceed for the next iteration of the policy. C. Selection of most important issues that we want to discuss during this session: - how to proceed from the interim policy ?!? - default /64 or /48 allocation size - do we want to have this space allocated from a special block, may be even block that is used by all RIRs for this purpose - what documentation is needed to get an allocation - is there any need to document allocations in the RIPE database, and if so, how ?!? - general wording of the policy D. Discussion of the issues Z. AOB ---

1 0

ipv6 tutorial
by David Kessens 11 Sep '01

11 Sep '01

In case you haven't noticed yet, we will have an ipv6 tutorial on: Monday 1 October : 10 am - 5 pm. The tutorial will be given by Florent Parent. Florent Parent is currently working at Viaginie inc. as a consultant in network architecture and security. He is involved in the architecture and deployment of IPv6 in the CA*net network. IPv6 Tutorial outline: Rationale Features Header Addressing ICMPv6, Neighbor Discovery, Autoconfiguration DNS Routing protocols Transition mechanisms Host and Router configurations Internet deployment I hope this helps, David K. ---

1 0

Exchange point interim policy
by David Kessens 10 Sep '01

10 Sep '01

The final date for comments on the proposed interim policy for ipv6 address allocations for Internet exchange points has passed. Since posting the interim conclusions, the direction of the discussion has not fundamentally changed. Therefore, we believe that we can ask the RIPE NCC to publish the proposed policy now, to clearly mark it as an interim policy and to start making the first allocations (with /64 allocations made out of fully reserved /48's and all allocations made out of one common block of address space). We would like to emphasize that this is the first version of the policy. It's pretty clear from the discussions on the list that though the policy is approved, there are still some issues that need more discussion. It looks like that many people felt that it was more important to get a policy in place rather sooner than later despite that they might not agree with all details in the policy. We have asked the RIPE NCC to reserve a slot at the next RIPE meeting to discuss the remaining issues and make recommendations to the RIPE NCC for improvements to the interim policy. Issues that we currently have on our list include: - how to proceed from the interim policy ?!? - default /64 or /48 allocation size - do we want to have this space allocated from a special block, may be even block that is used by all RIRs for this purpose - what documentation is needed to get an allocation - is there any need to document allocations in the RIPE database, and if so, how ?!? - general wording of the policy Don't hesitate to contact us if you want to have other issues discussed as well. For discussions on the maillist, we suggest that you post your mail only to the lir-wg list. Thanks, Fearghas McKay David Kessens EIX-WG Chair IPv6 wg Chair ---

1 0

draft agenda (v1) for IPv6 working group RIPE40
by David Kessens 09 Sep '01

09 Sep '01

Hi, Below follows the first draft of the agenda for the ipv6 wg. We will only meet for one meeting slot for the regular working group session due to all the attention for ipv6 in other (joint) sessions. There will be an ipv6 tutorial on monday, and two joint sessions on ipv6 allocation policy. One session will be used to discuss the interim policy on ipv6 assignments for exchange points and the other session will be used to make progress on the revision on the general allocation guidelines of ipv6 adresses. Separate agendas will be published regarding these sessions. Please let me know if you have any other topics that you want to have discussed and I will try to accomodate them in the agenda, Thanks, David K. --- Agenda for the IPv6 Working Group Meeting RIPE40, Prague A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. Addressing on cable systems (Pascal Julienne) D. Global IPv6 routing table status (Gert Doering & input of the audience requested) E. Euro6IX: The Pan-European IPv6 IX Backbone (Jordi Palet Martinez) F. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) Z. AOB ---

1 0

RE: Interim Policy proposal for IPv6 Address Assignment Policy fo rInternet Exchange Points
by paul.mylotte＠bt.com 07 Sep '01

07 Sep '01

All, YES - and I am hoping that the WGs will reach consensus at the Prague meeting that the interim policy-based allocations will permit extension to a /48 allocation. Paul P. S. Mylotte IP Addressing & Naming BTexact Technologies Adastral Park 01473 606333 / + 44 1473 606333 paul.mylotte(a)bt.com BTexact Technologies is a trademark of British Telecommunications plc Registered office 81 Newgate Street London EC1A 7AJ Registered in England no. 1800000 This electronic message contains information from British Telecommunications plc which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the number or address above) immediately. > -----Original Message----- > From: David R Huberman [SMTP:huberman@gblx.net] > Sent: 04 September 2001 17:57 > To: lir-wg(a)ripe.net; eix-wg(a)ripe.net; ipv6-wg(a)ripe.net > Subject: Re: Interim Policy proposal for IPv6 Address Assignment > Policy forInternet Exchange Points > > > So I ask: > > > > In lieu of any other policy changes, are you, as a RIPE member and > > participant in the LIR, EIX, and IPv6 WGs, in favor of the interim > policy > > proposal for IPv6 address assignment policy for internet exchange > points? > > To answer my own question, I support the interim policy proposal and hope > it is ratified by the WGs as soon as possible. > > /david

1 0

Re: Interim Policy proposal for IPv6 Address Assignment Policy for Internet Exchange Points
by Wilfried Woeber, UniVie/ACOnet 06 Sep '01

06 Sep '01

=>What I believe is needed is an allocation for IXP service networks as well =>as for the IX mesh, which is globally routable. I'd like to propose this =>alongside the existing proposal we have on the table. => =>Comments? = =I agree with you Mike, I think this is the only way an IXP can show its =independence from any one of its members (connected ISPs, carriers or =whatever) = = - Henk This "independence" argument is completly off-topic for this discussion. "Independence" can mean too many different things to too many different people. Usually you deal with that by making contingency plans or by building redundancy (or by defining procedures for the management plane ;-). Wilfried.

1 0