- ipv6-wg - mailman.ripe.net

(IPng 6652) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-03.txt (fwd)
by Thomas Trede 20 Oct '98

20 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Tue, 20 Oct 1998 10:43:54 -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 6652) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-03.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 : Basic Socket Interface Extensions for IPv6 Author(s) : R. Gilligan, S. Thomson, J. Bound, W. Stevens Filename : draft-ietf-ipngwg-bsd-api-new-03.txt Pages : 33 Date : 19-Oct-98 The de facto standard application program interface (API) for TCP/IP applications is the 'sockets' interface. Although this API was developed for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document [4]. 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-bsd-api-new-03.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-bsd-api-new-03.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-bsd-api-new-03.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 6651) I-D ACTION:draft-ietf-ipngwg-resv-anycast-01.txt (fwd)
by Thomas Trede 20 Oct '98

20 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Tue, 20 Oct 1998 10:33: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, mobile-ip(a)smallworks.com Subject: (IPng 6651) I-D ACTION:draft-ietf-ipngwg-resv-anycast-01.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 : Reserved IPv6 Subnet Anycast Addresses Author(s) : D. Johnson, S. Deering Filename : draft-ietf-ipngwg-resv-anycast-01.txt Pages : 5 Date : 19-Oct-98 The IP Version 6 addressing architecture defines an 'anycast' address as an IPv6 address that is assigned to one or more network interfaces (typically belonging to different nodes), with the property that a packet sent to an anycast address is routed to the 'nearest' interface having that address, according to the routing protocols' measure of distance. This document defines a set of reserved anycast addresses within each subnet prefix, and lists the initial allocation of these reserved subnet anycast 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-resv-anycast-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-resv-anycast-01.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-resv-anycast-01.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 6635) Draft: Request to Advance "DNS Extensions to Support IP Version 6" (fwd)
by Thomas Trede 16 Oct '98

16 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Thu, 15 Oct 1998 08:02:02 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com, Jeffrey Burgan <burgan(a)corp.home.net> Cc: hinden(a)iprg.nokia.com, scoya(a)cnri.reston.va.us, deering(a)cisco.com, ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6635) Draft: Request to Advance "DNS Extensions to Support IP Version 6" 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 : DNS Extensions to Support IP Version 6 Author(s) : M. Crawford, C. Huitema, S. Thomson Filename : draft-ietf-ipngwg-dns-lookups-02.txt Pages : 15 Date : 15-Sep-98 A working group last call for this document was completed on October 2, 1998. Comments received regarding transitioning from the current AAAA scheme to this scheme have been discussed and are thought to be manageable. Comments received during the last call regarding procedural issue were responded to by the w.g. chairs. 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

(IPng 6636) Last Call: Router Renumbering for IPv6 to Proposed Standard (fwd)
by Thomas Trede 16 Oct '98

16 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Thu, 15 Oct 1998 12:57:14 -0400 From: The IESG <iesg-secretary(a)ietf.org> Reply-To: iesg(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6636) Last Call: Router Renumbering for IPv6 to Proposed Standard The IESG has received a request from the IPNG Working Group to consider Router Renumbering for IPv6 <draft-ietf-ipngwg-router-renum-05.txt> as a Proposed Standard. 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 29, 1998. Files can be obtained via ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-05.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 6631) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-02.txt (fwd)
by Thomas Trede 14 Oct '98

14 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Tue, 13 Oct 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 6631) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-02.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 : Basic Socket Interface Extensions for IPv6 Author(s) : R. Gilligan, S. Thomson, J. Bound, W. Stevens Filename : draft-ietf-ipngwg-bsd-api-new-02.txt Pages : 33 Date : 12-Oct-98 The de facto standard application program interface (API) for TCP/IP applications is the 'sockets' interface. Although this API was developed for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document [4]. 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-bsd-api-new-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-bsd-api-new-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-bsd-api-new-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

(IPng 6633) W.G. Last Call on "A Method for the Transmission of IPv6 Packets over ARCnet Networks" (fwd)
by Thomas Trede 13 Oct '98

13 Oct '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Tue, 13 Oct 1998 12:15:12 -0700 From: Bob Hinden <hinden(a)iprg.nokia.com> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 6633) W.G. Last Call on "A Method for the Transmission of IPv6 Packets over ARCnet Networks" This is a IPng working group last call for comments on advancing the following document as a Proposed Standard: Title : A Method for the Transmission of IPv6 Packets over ARCnet Networks. Author(s) : I. Souvatzis Filename : draft-souvatzis-ipv6-arcnet-04.txt Pages : 6 Date : 28-Sep-98 Please send substantive comments to the ipng mailing list, and minor editorial comments to the author. This last call period will end two week from today on October 27, 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

IPv6 at the ams-ix
by horke＠mail.regio.net 12 Oct '98

12 Oct '98

I remeber someone saying at the RIPE-31 there is a plan for installing an ipv6 peering-site the ams-ix in amsterdam. Can someone provide me with a contact of this project ? Ciao Bernhard -- Bernhard Kroenung, Bahnhofstr 8, 36157 Ebersburg/Rhoen, Germany +49 6656 910101 @work : bernhard(a)kroenung.de Work: +49 661 9011777 @home : horke(a)Rhoen.De @school : Bernhard.Kroenung(a)Informatik.FH-Fulda.De

2 1

(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