May 2000 - ipv6-wg - mailman.ripe.net

Fw: Protocol Action: DNS Extensions to Support IP Version 6 to Proposed Standard
by Thomas Trede 31 May '00

31 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Matt Crawford" <crawdad(a)fnal.gov> To: "The IESG" <iesg-secretary(a)ietf.org> Cc: "RFC Editor" <rfc-editor(a)isi.edu>; "Internet Architecture Board" <iab(a)isi.edu>; <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, May 31, 2000 4:46 PM Subject: Re: Protocol Action: DNS Extensions to Support IP Version 6 to Proposed Standard > > The IESG has approved the Internet-Draft 'DNS Extensions to Support IP > > Version 6' <draft-ietf-ipngwg-dns-lookups-08.txt> as a Proposed > > Right draft, wrong title. > > > DNS Extensions to Support IPv6 Address Aggregation and Renumbering > <draft-ietf-ipngwg-dns-lookups-08.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

Fw: Protocol Action: DNS Extensions to Support IP Version 6 to Proposed Standard
by Thomas Trede 31 May '00

31 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "The IESG" <iesg-secretary(a)ietf.org> To: <IETF-Announce: ;> Cc: "RFC Editor" <rfc-editor(a)isi.edu>; "Internet Architecture Board" <iab(a)isi.edu>; <ipng(a)sunroof.eng.sun.com> Sent: Wednesday, May 31, 2000 4:14 PM Subject: Protocol Action: DNS Extensions to Support IP Version 6 to Proposed Standard > > > The IESG has approved the Internet-Draft 'DNS Extensions to Support IP > Version 6' <draft-ietf-ipngwg-dns-lookups-08.txt> as a Proposed > Standard. This document is the product of the IPNG Working Group. The > IESG contact persons are Erik Nordmark and Thomas Narten. > > > Technical Summary > > This document defines changes to the Domain Name System to support > renumberable and aggregatable IPv6 addressing. The changes include a > new resource record type (called A6) to store an IPv6 address in a > manner that expedites network renumbering and updated definitions of > existing query types that return Internet addresses as part of > additional section processing. A6 records can hold all or part of an > address, with pointers to other DNS names holding the remaining part > of the address. > > For lookups keyed on IPv6 addresses (often called reverse lookups), > this document defines a new zone structure that allows a zone to be > used without modification for parallel copies of an address space (as > for a multihomed provider or site) and across network renumbering > events. > > Working Group Summary > > This document was discussed extensively in both the IPNG and DNSIND > working groups. Although concern has been raised that use of the A6 > records will increase the demands placed on the DNS when resolving > names to addresses, the goal of easing site renumbering was deemed > important and the mechanism described in this document was viewed as > the best approach. > > Protocol Quality > > This document has been reviewed for the IESG by Thomas Narten and Erik > Nordmark. > > -------------------------------------------------------------------- > 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

Fw: Last Call: Router Renumbering for IPv6 to Proposed Standard
by Thomas Trede 26 May '00

26 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "The IESG" <iesg-secretary(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, May 25, 2000 9:12 PM Subject: 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-10.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 June 8, 2000. > > Files can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-10.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

Slides from UK IPv6 Event are now available online
by stuart.prevost＠bt.com 21 May '00

21 May '00

F.Y.I. Please visit the IPv6 Forum website if you wish to see the presentations from the UK IPv6 event held on the 10th May. The URL for the website is www.ipv6forum.com and follow the link at the top of the page. Regards, Stuart Prevost

1 0

Fw: I-D ACTION:draft-ietf-ipngwg-dns-lookups-08.txt
by Thomas Trede 18 May '00

18 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Matt Crawford" <crawdad(a)fnal.gov> To: <ipng(a)sunroof.eng.sun.com> Cc: <namedroppers(a)ops.ietf.org> Sent: Thursday, May 18, 2000 3:50 PM Subject: Re: I-D ACTION:draft-ietf-ipngwg-dns-lookups-08.txt > Differences between -07 and -08 are: > > > > IP6.INT -> IP6.ARPA for new style (bit based rather than nibble > based) reverse lookups. > > > > + Implementers are reminded of the necessity to limit the > + amount of work a resolver will perform in response to a > + client request. This principle MUST be extended to also > + limit the generation of DNS requests in response to one > + name-to-address (or address-to-name) lookup request. > > > Fixed a misformatted references. > -------------------------------------------------------------------- > 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

Fw: I-D ACTION:draft-ietf-ipngwg-dns-lookups-08.txt
by Thomas Trede 18 May '00

18 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, May 18, 2000 12:54 PM Subject: I-D ACTION:draft-ietf-ipngwg-dns-lookups-08.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 : DNS Extensions to Support IPv6 Address Aggregation and > Renumbering > Author(s) : M. Crawford, . Huitema, S. Thomson > Filename : draft-ietf-ipngwg-dns-lookups-08.txt > Pages : 20 > Date : 17-May-00 > > This document defines changes to the Domain Name System to support > renumberable and aggregatable IPv6 addressing. The changes include > a new resource record type to store an IPv6 address in a manner > which expedites network renumbering and updated definitions of > existing query types that return Internet addresses as part of > additional section processing. > > For lookups keyed on IPv6 addresses (often called reverse lookups), > this document defines a new zone structure which allows a zone to be > used without modification for parallel copies of an address space > (as for a multihomed provider or site) and across network > renumbering events. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-dns-lookups-08.txt > > Internet-Drafts are also 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-dns-lookups-08.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-dns-lookups-08.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

Fw: I-D ACTION:draft-ietf-ipngwg-rfc2553bis-00.txt
by Thomas Trede 12 May '00

12 May '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Friday, May 12, 2000 4:56 PM Subject: I-D ACTION:draft-ietf-ipngwg-rfc2553bis-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 : Basic Socket Interface Extensions for IPv6 > Author(s) : R. Gilligan, S. Thomson, J. Bound, W. Stevens > Filename : draft-ietf-ipngwg-rfc2553bis-00.txt > Pages : 34 > Date : 11-May-00 > > 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]. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-rfc2553bis-00.txt > > Internet-Drafts are also 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-rfc2553bis-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-rfc2553bis-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

final agenda for IPv6 working group RIPE36
by David Kessens 12 May '00

12 May '00

Hi, Below follows the final version of the IPv6 wg agenda. Please let me know if you have any other topics that you want to have discussed or if you have other comments. Despite being the final version of the agenda, we still have the freedom to add more topics during the agenda bashing. I am still looking for volunteers to cover some of the topics as proposed in the agenda. Please let me know if you are willing to take care of one of these. I have asked for a one hour time slot this time since we are already providing an IPv6 tutorial on tuesday (see RIPE NCC website for details). In addition, Bill Manning will give a presentation on DNS and IPv6 to the dns working group. In order to allow you to attend this presentation, I have asked the meeting organization to make sure that the DNS working group session and IPv6 working group session will not fall into the same time slot. At this point I still haven't heard whether the registries will be ready before the meeting with the draft revision of the IPv6 allocation guidelines. I will try to get more time allocated to us and the local ir working group in case they are able to get the draft out just before the meeting. Thanks and see you at the meeting, David K. --- Agenda for the IPv6 Working Group Meeting RIPE36, May 2000, Budapest A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of 6bone (David Kessens) C. News from the IPv6 forum (Juergen Rauschenbach) D. Summary of the Birmingham IPv6 event (Stuart Prevost) E. European developments/initiatives regarding IPv6 (input from the audience) F. Reports on on-going projects, success & failures stories on IPv6 (I am looking for volunteers who are willing to share their experiences) G. Future plans for the working group (input from the audience) tutorials, topics for next meeting, call for volunteers Z. AOB ---

1 0

draft agenda (v1) for IPv6 working group RIPE36
by David Kessens 01 May '00

01 May '00

Hi, Below follows the first draft of the IPv6 wg agenda. Please let me know if you have any other topics that you want to have discussed or if you have other comments on this first draft of the agenda. I am still looking for volunteers to cover some of the topics as proposed in the agenda. Please let me know if you are willing to take care of one of these. I have asked for a one hour time slot this time since we are already providing an IPv6 tutorial on tuesday (see RIPE NCC website for details). In addition, Bill Manning will give a presentation on DNS and IPv6 to the dns working group. In order to allow you attend this presentation, I have asked the meeting organization to make sure that the DNS working group session and IPv6 working group session will not fall into the same time slot. At this point it is still unclear whether the registries will be ready before the meeting with the draft revision of the IPv6 allocation guidelines. I will try to get more time allocated to us and the local ir working group in case they are able to get the draft out in time. Thanks, David K. --- Proposed Agenda (draft v1) for the IPv6 Working Group Meeting RIPE36, May 2000, Budapest A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of 6bone (David Kessens) C. News from the IPv6 forum and meeting in Telluride (Juergen Rauschenbach/Thomas Trede ?!?) D. European developments/initiatives regarding IPv6 (input from the audience) E. Reports on on-going projects, success & failures stories on IPv6 (I am looking for volunteers who are willing to share their experiences) Z. AOB ---

1 0