- ipv6-wg - mailman.ripe.net

Fw: Protocol Action: Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification to Proposed Standard
by Thomas Trede 09 Apr '01

09 Apr '01

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>; "IANA" <iana(a)iana.org>; "Internet Architecture Board" <iab(a)isi.edu>; <ipng(a)sunroof.eng.sun.com> Sent: Friday, April 06, 2001 9:31 PM Subject: Protocol Action: Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification to Proposed Standard > > > The IESG has approved the Internet-Draft 'Extensions to IPv6 Neighbor > Discovery for Inverse Discovery Specification' > <draft-ietf-ion-ipv6-ind-05.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 protocol describes extensions to the IPv6 Neighbor Discovery that > allow a node to determine and advertise an IPv6 address corresponding > to a given link-layer address. The extensions are called Inverse > Neighbor Discovery. They were originally developed for Frame Relay > networks but may also apply to other networks with similar behavior. > > Working Group Summary > > This document was originally developed within the ION WG but was moved > to the IPng WG because it extended IPv6's Neighbor Discovery. There > was concensus in the WG for the extensions defined in this document. > > Protocol Quality > > This document has been reviewed for the IESG by Thomas Narten. > > Note to RFC Editor: > > In the "References" section, there is a work in progress that > needs to be updated: > > [IPv6-FR] citation needs to have the title change: > "Transmission of IPv6 Packets over Frame Relay", > and update with its RFC number - RFC 2590, May 1999. > > > -------------------------------------------------------------------- > 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: interim meeting
by Thomas Trede 03 Apr '01

03 Apr '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Steve Deering" <deering(a)cisco.com> To: <ipng(a)sunroof.eng.sun.com> Cc: "Bob Hinden" <hinden(a)iprg.nokia.com> Sent: Saturday, March 31, 2001 1:56 AM Subject: interim meeting > For those who didn't hear this in Minneapolis and haven't read the > minutes, note that we are planning to hold an interim meeting of the > IPng Working Group on May 30, 31, and June 1, 2001, hosted by > Microsoft at their "site" in Redmond, Washington, USA, near Seattle. > > Part of the time will be spent as a joint meeting with folks from the > 3GPP standards bodies that have IPv6 requirements, and there may also > be some NGtrans sessions, though the exact times and details for those > are still to be worked out. Please send proposed agenda topics to > Bob and me. > > Information about accommodation, driving directions, etc. will be > posted here as it becomes available. > > Bob & Steve > -------------------------------------------------------------------- > 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-default-addr-select-03.txt
by Thomas Trede 30 Mar '01

30 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 30, 2001 2:29 PM Subject: I-D ACTION:draft-ietf-ipngwg-default-addr-select-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 : Default Address Selection for IPv6 > Author(s) : R. Draves > Filename : draft-ietf-ipngwg-default-addr-select-03.txt > Pages : 20 > Date : 29-Mar-01 > > This document describes two algorithms, for source address selection > and for destination address selection. The algorithms specify > default behavior for all IPv6 implementations. They do not override > choices made by applications or upper-layer protocols, nor do they > preclude the development of more advanced mechanisms for address > selection. The two algorithms share a common framework, including an > optional mechanism for allowing administrators to provide policy > that can override the default behavior. In dual stack > implementations, the framework allows the destination address > selection algorithm to consider both IPv4 and IPv6 addresses - > depending on the available source addresses, the algorithm might > prefer IPv6 addresses over IPv4 addresses, or vice-versa. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-default-addr-select-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-default-addr-select-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-default-addr-select-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

RIPE-196 (IPv6 policy document) analysis and proposed changes
by Niall Richard Murphy 29 Mar '01

29 Mar '01

Folks, At RIPE 38 there was a significant amount of discussion and several presentations in the IPv6 WG about the current IPv6 allocation policy document, RIPE 196. On foot of that a small task force got together to try and put their thoughts into a better form. Now we are announcing the results, viewable at: http://www.enigma.ie/articles/global-ipv6-alteration.html We hope that this document will help to provoke discussion about current IPv6 policies, and perhaps even act as a catalyst for their modification :-) I'd like to thank all who participated for their hard work. Niall -- Enigma Consulting Limited: Security, UNIX and telecommunications consultants. Address: Floor 2, 45 Dawson Street, Dublin 2, Ireland. http://www.enigma.ie/

1 0

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

27 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 3: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: IPng Minutes from Minneapolis IETF
by Thomas Trede 27 Mar '01

27 Mar '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, March 27, 2001 4:20 AM Subject: IPng Minutes from Minneapolis IETF > The IPng w.g. minutes from Minneapolis IETF can be found at: > > http://playground.sun.com/pub/ipng/html/minutes/ipng-minutes-mar2001.txt > > Presentations for most of the talks can be found at: > > http://playground.sun.com/pub/ipng/html/meetings.html > > Please send me corrections and updates. > > Thanks, > 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

Fw: draft-draves-ipngwg-router-selection-01
by Thomas Trede 27 Mar '01

27 Mar '01

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Richard Draves" <richdr(a)microsoft.com> To: <multi6(a)ops.ietf.org> Cc: "IPng List (E-mail)" <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, March 27, 2001 7:44 AM Subject: draft-draves-ipngwg-router-selection-01 > draft-draves-ipngwg-router-selection-01 specifies a protocol (optional > extensions to Neighbor Discovery's Router Advertisement) for > distributing routes from routers to hosts. The idea is to help > multi-homed hosts (hosts with multiple physical or virtual network > interfaces), because Redirects don't work for them. > > The protocol is defined narrowly, to avoid the traditional problems with > having hosts learn routes from routers. The hosts are not exposed to > routing protocol metrics, routers do not dump their entire routing > tables to hosts, etc. > > The ipng working group decided to accept the draft as a work item, but > one of the major comments was that it would be a good idea to solicit > feedback from the operational community. Hence this message. I know the > draft does not relate directly to the multi6 charter, but I'm hoping to > find on the multi6 list operational people with some knowledge of IPv6 > who might be interested in this draft. Please confine followup > discussions to the ipng list. > > Section 4 is of particular operational interest, because it discusses > router configuration issues. > > ftp://ftp.research.microsoft.com/users/richdr/draft-draves-ipngwg-router > -selection-01.txt > > Thanks, > Rich > -------------------------------------------------------------------- > 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-ipv6-2260-00.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-ipv6-2260-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 : IPv6 multihoming support at site exit routers > Author(s) : J. Hagino > Filename : draft-ietf-ipngwg-ipv6-2260-00.txt > Pages : 9 > Date : 22-Mar-01 > > The document describes a mechanism for basic IPv6 multihoming support, > and its operational requirements. The mechanism can be combined with > more sophisticated (or complex) multihoming support mechanisms, and can > be used as a foundation for other mechanisms. The document is largely > based on RFC2260 [Bates, 1998] by Tony Bates. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-2260-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-ipv6-2260-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-ipv6-2260-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: 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