- ipv6-wg - mailman.ripe.net

(IPng 6602) Request to Advance "Router Renumbering for IPv6" (fwd)
by Thomas Trede 09 Oct '98

09 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Fri, 09 Oct 1998 09:14:37 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com, Jeffrey Burgan <burgan(a)corp.home.net> Cc: scoya(a)cnri.reston.va.us, deering(a)cisco.com, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6602) Request to Advance "Router Renumbering for IPv6" Jeff, Thomas, The chairs of the IP Next Generation working group, on behalf of the working group, request that the following document be published as a Proposed Standard: Title : Router Renumbering for IPv6 Author(s) : M. Crawford Filename : draft-ietf-ipngwg-router-renum-05.txt Pages : 22 Date : 17-Sep-98 A working group last call for this document was completed on October 5, 1998. No comments were received. Bob Hinden / Steve Deering IPng Working Group Co-Chairs -------------------------------------------------------------------- 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

Re: minutes RIPE31
by Bernard.Tuy＠urec.cnrs.fr 02 Oct '98

02 Oct '98

| Date: Tue, 29 Sep 1998 18:35:00 +0000 | From: David Kessens <davidk(a)ISI.EDU> | | Minutes of IPv6 Working Group, 24th of Sept. 1998 | (...) | | 3. Current status of RIPE regarding address assignments in IPv6 by | Paula Caslav | | - RIPE NCC is in process of discussing the documentation, finding | guidelines and procedures, by taking the IETF draft, looking at the | criteria, what documentation will we need, working on details with | other regional registries and will have a meeting with them, send than ====BT: ^^^^_ then ? | a draft to the relevant working groups and the RIPE community, final | version will be published - Hopefully ready in January 1999 | | | 2.3. News about manufacturers implementation | - input from the audience | | Bernhard Tuy showed an overview of all vendors and what they ====BT: ^^^^_ Bernard ! ...............^^^_ some | currently support. For details see: | http://www.phoebe.urec.fr/G6 ====BT: ^^^^_ http://phoebe.urec.fr/G6/ | http://www.ipv6.urec.fr/G6 ====BT: this URL (to access the server in IPv6) is correct | | | 4. General Input from other Working Groups | | Action points: | | 31.1 RIPE NCC will start allocating IPv6 addresses by the next RIPE | meeting in January. ====BT: 31.2 ? send out to 1) experienced people draft documents about address registration and allocation 2) concerned WGs more finalized papers to stress the discussion and have working papers ready by the end of '98. Thanx to all participants for their valuable contribution, Cheers. +Bernard Tuy. P.S.: Joachim's presentation rose a question : how to proceed with the IRRv6 ? how to have people from different WGs involved in and able to provide an effective work to achieve this ? .[BT].

1 0

minutes RIPE31
by David Kessens 30 Sep '98

30 Sep '98

Hi, Below follow the preliminary minutes of the IPv6 wg. I would like to thank Sabrina Waschke of the RIPE NCC for taking the minutes. The minutes will be regarded final and I will forward them to the RIPE NCC if I don't receive comments within one week from now. Thank you all for attending the meeting, David K. --- Minutes of IPv6 Working Group, 24th of Sept. 1998 1. Administrative stuff: Chair: David Kessens (Thomas Trede apologised) Minutes: Sabrina Waschke # Attendees: 81 2. Reports Report - 6Bone by David Kessens - Status report there are now about 300 IPv6 connected sites on the 6bone the trend is to connect natively instead of using tunnels (slides will be available at http://www.ripe.net/meeting/ripe/ripe31/pres/) - Information on the 6bone can be found at: see <http://www.6bone.net> 3. Current status of RIPE regarding address assignments in IPv6 by Paula Caslav - RIPE NCC is in process of discussing the documentation, finding guidelines and procedures, by taking the IETF draft, looking at the criteria, what documentation will we need, working on details with other regional registries and will have a meeting with them, send than a draft to the relevant working groups and the RIPE community, final version will be published - Hopefully ready in January 1999 Question by: David Kessens: Could you give more detail in the time scale ? Paula Caslav: November 1998: first draft of procedures document ready to be discussed among the regional registries and RIPE January 1999: start allocating IPv6 addresses (depends on IANA to be ready to allocate to the regional registries and on the registries to get their databases and procedures compliant) All regional registries will start allocating at the same time. There will be no change in the fee structure for the next year. Question by David Kessens: Do you have any comments what will be different in the assignment guidelines for the TLA's in the IETF draft and yours ? Paula Caslav: We might do a slow start mechanism in meaning of allocating a sub TLA first. Mirjam Kuehne: We also need to define still how to determine if an organisation is a transit provider. Many details are still under discussion. Comment by the audience: It might be useful to have a document in this Working Group as soon as possible. Mirjam Kuehne: We are in the process of collecting input and will discuss it with the other Working Groups. We receive requests for IPv6 addresses, some are detailed, some are just general. We will see how we can implement this in the operations and procedures. Paula Caslav: If you have any ideas send them to us or the mailing list of this Working Group. 2.3. News about manufacturers implementation - input from the audience Bernhard Tuy showed an overview of all vendors and what they currently support. For details see: http://www.phoebe.urec.fr/G6 http://www.ipv6.urec.fr/G6 4. General Input from other Working Groups Routing WG presented by Joachim Schmitz (slides will be available at http://www.ripe.net/meeting/ripe/ripe31/pres/) Do we need an IRR for IPv6 ? Need for an IPv6 IRR: - due to the benefits: YES - plus: manage interface ipv4 _> ipv6 - time to early: NO We need an IPv6 routing registry ! <general acceptence without taking over any concrete initiative by the audience> Joachim Schmitz: Call for participation. He expects a gradual move over, requirements in the beginning are not very high, so one registry might be enough to start with. David Kessens: The regional registries also need to think about assignment policies for AS numbers, they might be different. David K: There are several ways to go to a IPv6 routing registry: 1. just replace IPv4 with IPv6 addresses in RPSL, and add IPv6 specific support later on 2. a special RPSLv6 draft with all bells and whistles that are required to do IPv6 routing registries What is better ? Joachim Schmitz: Both are needed, because RPSL took some time to be developed and we need something running soon. That's not sufficient but better than nothing. David Kessens: Coming out with an RPSL IPv6 version would make sense. 5. AOB: David Kessens: Keep this Working Group and move on because of the large interest (81 attendees). Discuss the allocation and assignment process in more detail. Action points: 31.1 RIPE NCC will start allocating IPv6 addresses by the next RIPE meeting in January.

2 1

(IPng 6546) Last Call: IPv6 over Non-Broadcast Multiple Access (NBMA) networks to Proposed Standard (fwd)
by Thomas Trede 29 Sep '98

29 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Mon, 28 Sep 1998 07:24:17 -0700 From: The IESG <iesg-secretary(a)ietf.org> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6546) Last Call: IPv6 over Non-Broadcast Multiple Access (NBMA) networks to Proposed Standard The IESG has received a request from the Internetworking Over NBMA Working Group to consider the following two Internet-Drafts as Proposed Standards: o IPv6 over Non-Broadcast Multiple Access (NBMA) networks <draft-ietf-ion-ipv6-01.txt> o IPv6 over ATM Networks <draft-ietf-ion-ipv6-atm-02.txt> The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg(a)ietf.org or ietf(a)ietf.org mailing lists by October 12, 1998. Files can be obtained via: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ion-ipv6-01.txt ftp://ftp.ietf.org/internet-drafts/draft-ietf-ion-ipv6-atm-02.txt -------------------------------------------------------------------- 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

(IPng 6519) I-D ACTION:draft-ietf-ipngwg-scoped-routing-00.txt (fwd)
by Thomas Trede 25 Sep '98

25 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Thu, 24 Sep 1998 10:26:44 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6519) I-D ACTION:draft-ietf-ipngwg-scoped-routing-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Routing of Scoped Addresses in the Internet Protocol Version 6 (IPv6) Author(s) : B. Haberman Filename : draft-ietf-ipngwg-scoped-routing-00.txt Pages : 7 Date : 22-Sep-98 This document outlines a mechanism for generating routing tables that include scoped IPv6 addresses. It defines a set of rules for routers to implement in order to forward scoped unicast and multicast addresses regardless of the routing protocol. It should be noted that these rules will apply to all scoped addresses. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-scoped-routing-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-scoped-routing-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-scoped-routing-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

(IPng 6530) IPng Web Site Updated (fwd)
by Thomas Trede 25 Sep '98

25 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Fri, 25 Sep 1998 11:12:52 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6530) IPng Web Site Updated I just completed an update to the IPng web site at: http://playground.sun.com/ipng The changes include new minutes, pointers to current specifications, implementations, etc. Corrections/additions to me. Bob -------------------------------------------------------------------- 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

(IPng 6527) I-D ACTION:draft-ietf-ipngwg-icmp-v2-02.txt (fwd)
by Thomas Trede 25 Sep '98

25 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Fri, 25 Sep 1998 10:25:44 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6527) I-D ACTION:draft-ietf-ipngwg-icmp-v2-02.txt Note: This revision reflects comments received during the last call period. A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification Author(s) : A. Conta, S. Deering Filename : draft-ietf-ipngwg-icmp-v2-02.txt Pages : 21 Date : 24-Sep-98 This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-icmp-v2-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-icmp-v2-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-icmp-v2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

meeting time
by David Kessens 23 Sep '98

23 Sep '98

Hi, Thomas sent his apologies and asked me to chair the working group session. Unfortunetely, I had an agenda collision so the meeting has been moved to the second slot of the DNS wg: Thursday 24th, 11am, Room 2 I hope to see you all, David K. ---

1 0

(IPng 6509) W.G. Last Call on "Router Renumbering for IPv6" (fwd)
by Thomas Trede 22 Sep '98

22 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Mon, 21 Sep 1998 19:43:33 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6509) W.G. Last Call on "Router Renumbering for IPv6" This is a IPng working group last call for comments on advancing the following document as a Proposed Standard: Title : Router Renumbering for IPv6 Author(s) : M. Crawford Filename : draft-ietf-ipngwg-router-renum-05.txt Pages : 22 Date : 17-Sep-98 Please send substantive comments to the ipng mailing list, and minor editorial comments to the authors. This last call period will end two week from today on October 5, 1998. Bob Hinden / Steve Deering -------------------------------------------------------------------- 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

(IPng 6508) I-D ACTION:draft-ietf-ipngwg-router-renum-05.txt (fwd)
by Thomas Trede 21 Sep '98

21 Sep '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Mon, 21 Sep 1998 09:46:33 -0400 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6508) I-D ACTION:draft-ietf-ipngwg-router-renum-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Router Renumbering for IPv6 Author(s) : M. Crawford Filename : draft-ietf-ipngwg-router-renum-05.txt Pages : 22 Date : 17-Sep-98 IPv6 Neighbor Discovery and Address Autoconfiguration conveniently make initial assignments of address prefixes to hosts. Aside from the problem of connection survival across a renumbering event, these two mechanisms also simplify the reconfiguration of hosts when the set of valid prefixes changes. This document defines a mechanism called Router Renumbering ('RR') which allows address prefixes on routers to be configured and reconfigured almost as easily as the combination of Neighbor Discovery and Address Autoconfiguration works for hosts. It provides a means for a network manager to make updates to the prefixes used by and advertised by IPv6 routers throughout a site. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-router-renum-05.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-05.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-router-renum-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0