- ipv6-wg - mailman.ripe.net

Fw: I-D ACTION:draft-ietf-ipngwg-dns-discovery-01.txt
by Thomas Trede 23 Mar '01

23 Mar '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Friday, March 23, 2001 2:02 PM Subject: I-D ACTION:draft-ietf-ipngwg-dns-discovery-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 : Analysis of DNS Server Discovery Mechanisms for IPv6 > Author(s) : D. Thaler > Filename : draft-ietf-ipngwg-dns-discovery-01.txt > Pages : 43 > Date : 22-Mar-01 > > There are any number of ways that IPv6 hosts can discover > information required to enable name resolution, in the absence of > a DHCP server. This document discusses the issues and provides a > taxonomy of possible solutions, and evaluates them against various > design criteria. Finally, it provides recommendations as input to > the standards process. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-dns-discovery-01.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-discovery-01.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-discovery-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

Fw: UNH IPv6 Testing at Connectathon2001
by Thomas Trede 20 Mar '01

20 Mar '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "William Lenharth" <whl(a)sr.unh.edu> To: <ipng(a)sunroof.eng.sun.com> Sent: Monday, March 19, 2001 10:34 PM Subject: UNH IPv6 Testing at Connectathon2001 > > This message is transmitted to the IPng list at the request of the Area > Director for IPv6 Working > group. > > *********************************************************************** > A report on the IPv6 Testing at Connectaton2001 > *********************************************************************** > > Three full days of testing in the areas, General Spec. testing , RIPng, > and Mobility for IPv6. > > Companies that participated: SUN Microsystems, HP, SGI, Matsushita, > Ericsson, Nokia, > Microsoft, Ericsson-Telebit, Helsinki University of Technology, Compaq, > and Tahi / Kame. > > Most base spec. testing was executed without a serious problem being > noted. The RIPng > testing was also executed without serious problem. > > The mobility testing consisted of conformance testing against the IETF > specification. All > vendors had some minor issues, the following issue / problems were also > noted. It was > unclear in some cases that an ICMP message should be sent when a bad > packet was encountered. Also, if you try to remove a binding update that > was previously removed > in some cases implementations would acknowledge it with a reject > status. It was felt that > it should be accepted so that the status was clear. > > For more info contact: jfl(a)iol.unh.edu, schultz(a)iol.unh.edu > > *********************************************************************** > > > -------------------------------------------------------------------- > 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-ipaddressassign-02.txt
by Thomas Trede 08 Mar '01

08 Mar '01

FYI! Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, March 08, 2001 12:55 PM Subject: I-D ACTION:draft-ietf-ipngwg-ipaddressassign-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 : A flexible method for managing the assignment of > bites of an IPv6 address block > Author(s) : M. Blanchet > Filename : draft-ietf-ipngwg-ipaddressassign-02.txt > Pages : 13 > Date : 07-Mar-01 > > This document presents a method to manage the assignment of bits of > an IPv6 address block or range. When an organisation needs to make > an address plan for its subnets or when an ISP needs to make an > address plan for allocating address ranges to its customers, this > method enables the organisation to postpone the final decision on > the number of bits to partition in the address space they have. It > does it by keeping the bits around the borders of the partition to > be free as long as possible. This scheme is applicable to any bits > addressing scheme using bits with partitions in the space, but its > first intended use is for IPv6. It is a generalization of RFC1219 > and can be used for IPv6 assignments based on RFC2373 and RFC2374. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-ipaddressassign-02.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-ipaddressassign-02.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-ipaddressassign-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

Fw: W.G. Last Call on "Unicast-Prefix-based IPv6 Multicast Addresses"
by Thomas Trede 28 Feb '01

28 Feb '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, February 27, 2001 4:35 PM Subject: W.G. Last Call on "Unicast-Prefix-based IPv6 Multicast Addresses" > This is a IPng working group last call for comments on advancing the > following document as a Proposed Standard: > > Title : Unicast-Prefix-based IPv6 Multicast Addresses > Author(s) : B. Haberman, D. Thaler > Filename : draft-ietf-ipngwg-uni-based-mcast-01.txt > Pages : 5 > Date : 26-Jan-01 > > 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 March 13, 2001. > > 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

Fw: I-D ACTION:draft-vida-mld-v2-00.txt
by Thomas Trede 27 Feb '01

27 Feb '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, February 27, 2001 12:52 PM Subject: I-D ACTION:draft-vida-mld-v2-00.txt > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Multicast Listener Discovery Version 2 (MLDv2) for > IPv6 > Author(s) : R. Vida et al. > Filename : draft-vida-mld-v2-00.txt > Pages : 48 > Date : 26-Feb-01 > > This document specifies Version 2 of the Multicast Listener Discovery > protocol, MLDv2. MLD is the protocol used by an IPv6 router to > discover the presence of multicast listeners (that is, nodes wishing > to receive multicast packets) on its directly attached links, and to > discover specifically which multicast addresses are of interest to > those neighboring nodes. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-vida-mld-v2-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-vida-mld-v2-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-vida-mld-v2-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

Fw: W.G. Last Call on "Basic Socket Interface Extensions for IPv6"
by Thomas Trede 22 Feb '01

22 Feb '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, February 22, 2001 12:39 AM Subject: W.G. Last Call on "Basic Socket Interface Extensions for IPv6" > This is a IPng working group last call for comments on advancing the > following document as an Informational RFC: > > Title : Basic Socket Interface Extensions for IPv6 > Author(s) : R. Gilligan, S. Thomson, J. Bound, W. Stevens > Filename : draft-ietf-ipngwg-rfc2553bis-03.txt > Pages : 31 > Date : 12-Feb-01 > > 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 March 7, 2001. > > 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

Fw: Last Call: Transmission of IPv6 Packets over IEEE 1394 Networks to Proposed Standard
by Thomas Trede 20 Feb '01

20 Feb '01

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: Monday, February 19, 2001 8:50 PM Subject: Last Call: Transmission of IPv6 Packets over IEEE 1394 Networks to Proposed Standard > > The IESG has received a request from the IPNG Working Group to consider > Transmission of IPv6 Packets over IEEE 1394 Networks > <draft-ietf-ipngwg-1394-01.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 March 5, 2001. > > Files can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-1394-01.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: I-D ACTION:draft-ietf-ipngwg-1394-01.txt
by Thomas Trede 15 Feb '01

15 Feb '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, February 15, 2001 12:46 PM Subject: I-D ACTION:draft-ietf-ipngwg-1394-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 : Transmission of IPv6 Packets over IEEE 1394 Networks > Author(s) : K. Fujisawa, A. Onoe > Filename : draft-ietf-ipngwg-1394-01.txt > Pages : 8 > Date : 14-Feb-01 > > IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. > This document describes the frame format for transmission of IPv6 > [IPV6] packets and the method of forming IPv6 link-local addresses > and statelessly autoconfigured addresses on IEEE1394 networks. > It also describes the content of the Source/Target Link-layer Address > option used in Neighbor Discovery [DISC] when the messages are > transmitted on an IEEE1394 network. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-1394-01.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-1394-01.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-1394-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

Fw: I-D ACTION:draft-ietf-ipngwg-rfc2553bis-03.txt
by Thomas Trede 13 Feb '01

13 Feb '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, February 13, 2001 12:59 PM Subject: I-D ACTION:draft-ietf-ipngwg-rfc2553bis-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-rfc2553bis-03.txt > Pages : 31 > Date : 12-Feb-01 > > 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-03.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-03.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-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

6.0.1.0.0.2.ip6.int. vanished?
by Hauke Johannknecht 12 Feb '01

12 Feb '01

-----BEGIN PGP SIGNED MESSAGE----- Hi. I might haved missed some things in the last weeks but it looks like the delegation of 6.0.1.0.0.2.ip6.int. to RIPE has vanished from DNS? Is it supposed to be this way? Have we moved to "whatever v6-rdns is supposed to be this year"? Gruss, Hauke - -- Hauke Johannknecht Berlin / Germany HJ422-RIPE Use PGP ! -> lynx -dump http://www.ash.de/ash.asc | pgp -kaf -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOobGXHO2fBh4VhzZAQHYgwgAmM/Q+PA2maIqJRDrQEJgscBCHtJjyna5 ocdeG0xBKo5Vwb/EwHic1rR6BzDI35IQrPsMOBXiRLVSEOCGjSIeqplqDy6dqORB EoN9pJQHsgsb4y6t2VZAqQfBvesUzUr49omihm3bn2JYRu+gQE3cXTd7jRypnIo9 +pWIwL4hecJUbH9ZuFRWkUkcGcmVQn/hjFd6K4XlHj2DbgKQXQJRQuTMJAqCUVcy ODRQHYqlv+ApXhiQcFPv9qXW3Csut6NqcrzhfR93JQPjvOfDQHI0OreYR6ZU3wFJ O/Gyv6/GHxLWDuI1L0V8Ypthbo6QbuW9MjKP/GNthjUhABR55EyGGA== =+Nn0 -----END PGP SIGNATURE-----

3 2