- ipv6-wg - mailman.ripe.net

Fw: I-D ACTION:draft-ietf-ipngwg-ipv6-2260-00.txt
by Thomas Trede 27 Jun '00

27 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, June 27, 2000 12:44 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 : 26-Jun-00 > > 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: W.G. Last Call on "IPv6 Multihoming with Route Aggregation"
by Thomas Trede 25 Jun '00

25 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Saturday, June 24, 2000 1:20 AM Subject: W.G. Last Call on "IPv6 Multihoming with Route Aggregation" > This is a IPng working group last call for comments on advancing the > following document as Informational: > > Title : IPv6 Multihoming with Route Aggregation > Author(s) : J. Yu > Filename : draft-ietf-ipngwg-ipv6multihome-with-aggr-00.txt > Pages : 7 > Date : 24-Nov-99 > > 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 July 7, 2000. > > 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: Revised IPng Working Group Charter
by Thomas Trede 25 Jun '00

25 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Cc: <hinden(a)iprg.nokia.com>; <deering(a)cisco.com> Sent: Friday, June 23, 2000 11:34 PM Subject: Revised IPng Working Group Charter > Folks, > > Attached is a draft of a revised charter for the working group. Updating > the charter was agreed to at the Grenoble and Minneapolis working group > meetings, but it took the chairs and AD's a while to draft a new one. > > The charter includes changing the name of the working group to the "IP > Version 6 Working Group", but will keep the acronym of "ipngwg". This will > avoid having to rename all current internet drafts. > > Please send comments on the new charter to the mailing list. There will be > a short session in Pittsburgh to discuss it as well. > > Bob Hinden / Steve Deering > > -------------------------------------------------------------------------- --- > Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft > -------------------------------------------------------------------------- --- > > IP Version 6 Working Group (ipngwg) *** note: change of name but not acronym > > Chair(s): > > Bob Hinden <hinden(a)iprg.nokia.com> > Steve Deering <deering(a)cisco.com> > > Document Editor > > Bob Hinden (hinden(a)iprg.nokia.com) > > Internet Area Director(s): > > Thomas Narten <narten(a)raleigh.ibm.com> > Erik Nordmark <nordmark(a)eng.sun.com> > > Internet Area Advisor: > > Thomas Narten <narten(a)raleigh.ibm.com> > > Mailing Lists: > > General Discussion:ipng@sunroof.eng.sun.com > To Subscribe: majordomo(a)sunroof.eng.sun.com > In Body: in body: subscribe ipng > Archive: ftp://playground.sun.com/pub/ipng/mail-archive > > Description of Working Group: > > IP version 6 or IPv6 (also formerly known as IP Next Generation or IPng) > is intended to support the continued growth of the Internet, both in > size and capabilities, by offering a greatly increased IP address space > and other enhancements over IPv4. The working group was originally > chartered to implement the recommendations of the IPng Area Directors > as outlined at the July 1994 IETF meeting and in "The Recommendation > for the IP Next Generation Protocol," RFC1752, January 1995. Most of > the tasks in that original charter have been completed, and the core > IPv6 protocol specifications are now on the IETF standards track. > The working group's ongoing responsibilities are as follows: > > - Complete work from the original charter and follow-on work, as > outlined below. > > - Keep all IPv6 working group documents moving along publication / > standardization track. > > - Serve as a review board and body of competence and coordination for > IPv6 architectural issues that span multiple IETF working groups. > > - Provide a home for IPv6-related work that doesn't fit in an existing > IETF working group and doesn't merit a working group of its own. > > - Provide technical input to ICANN, Internet Address Registries, and > IANA with regard to IPv6 address allocation policies and procedures. > > - Provide technical input and review to IANA with regard to IPv6 > protocol and parameter assignments. > > The list of the working group's current work items is as follows: > > - Revise ICMPv6 spec (scope-exceeded err, no error to redirect, > editorial) > - Revise Generic Tunneling spec (add bidirectional tunnels) > - Update Basic and Advanced API specs > - Complete Router Renumbering spec > - Complete Scoped Address Architecture spec and any necessary revisions > to other working group drafts required to properly implement support > for IPv6 address scoping > - Complete work on recommended address-selection algorithms > - Work on new solutions to site-multihoming problems, possibly including > both host-based and router-based solutions. > - Complete work on local IPv6 networking as part of IPv6 plug-and-play > - Complete work on privacy extensions to stateless address configuration > - Document IPv6 renumbering model > - Complete the GSE Analysis document > - Complete the Inverse Neighbor Discovery spec > - Complete the IPv6 Node Information Queries spec > - Complete MIB specs as required by any working group protocol specs > > New work items not listed above require the approval of the working > group and Internet Area directors before they will be taken on by the > working group. > > The working group would welcome contributions on the following topics > (this is not an exhaustive list): > > - Flow label standardization > - Solutions to other multihoming issues, beyond those specific to > site-multihoming > - Integration of autoconfiguration, mobility, DNS, service discovery > and other technologies to enhance IPv6 plug-and-play > - IPv6 dial-up issues relating to address assignment, use of Neighbor > Discovery, etc. (not including AAA work) > - Specifications for IPv6 over additional media > - Extending MLD to include functionality of IGMPv3 > - Host use of anycast; TCP use of anycast > - Support for multi-link subnets (single subnet spans multiple links) > - Scope-name discovery > - IPv6 protocol extensions to accommodate mobile wireless networks. > > Goals and Milestones: > > Aug 2000 Complete MLD MIB and submit for Proposed Standard > > Aug 2000 Complete privacy extensions specification and submit for > Proposed Standard > > Aug 2000 Completed revision of GSE Analysis document and resubmit > for Informational > > Aug 2000 Complete the Inverse Neighbor Discovery specification > and submit for Proposed Standard > > Aug 2000 Complete IPv6 Multihoming with Route Aggregation and submit > for Informational. > > Oct 2000 Update ICMP document and resubmit for Draft Standard > > Oct 2000 Update Generic Tunneling specification and resubmit for > Proposed Standard > > Oct 2000 Complete updates to Basic and Advanced API specifications > and submit for Informational > > Dec 2000 Complete Scoped Address Architecture and submit for Proposed > Standard > > Dec 2000 Compete Address Selection specification and submit for Proposed > Standard > > Dec 2000 Complete Local IPv6 Networking Specification and submit for > Proposed Standard > > Dec 2000 Complete the IPv6 Node Information Queries specification > and submit for Proposed Standard > > Mar 2001 Complete IPv6 renumbering model document and submit for > Informational > > -------------------------------------------------------------------------- --- > Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft - Draft > -------------------------------------------------------------------------- --- > > -------------------------------------------------------------------- > 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: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"
by Thomas Trede 23 Jun '00

23 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Friday, June 23, 2000 1:04 AM Subject: Re: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification" > The author of this draft's email address has changed. His new address is: > > aconta(a)txc.com > > Bob > > At 01:35 PM 6/22/2000 -0700, Bob Hinden wrote: > >I forgot to add that this document is now an IPng w.g. document. We > >inherited it when the ION w.g. concluded. > > > >Bob > > > >At 01:26 PM 6/22/2000 -0700, Bob Hinden wrote: > >>This is a IPng working group last call for comments on advancing the > >>following document as a Proposed Standard: > >> > >> Title : Extensions to IPv6 Neighbor Discovery for Inverse > >> Discovery Specification > >> Author(s) : A. Conta > >> Filename : draft-ietf-ion-ipv6-ind-03.txt > >> Pages : 22 > >> Date : 27-Oct-99 > >> > >>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 July 6, 2000. > > -------------------------------------------------------------------- > 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: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"
by Thomas Trede 23 Jun '00

23 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, June 22, 2000 10:35 PM Subject: Re: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification" > I forgot to add that this document is now an IPng w.g. document. We > inherited it when the ION w.g. concluded. > > Bob > > At 01:26 PM 6/22/2000 -0700, Bob Hinden wrote: > >This is a IPng working group last call for comments on advancing the > >following document as a Proposed Standard: > > > > Title : Extensions to IPv6 Neighbor Discovery for Inverse > > Discovery Specification > > Author(s) : A. Conta > > Filename : draft-ietf-ion-ipv6-ind-03.txt > > Pages : 22 > > Date : 27-Oct-99 > > > >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 July 6, 2000. > > > >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: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"
by Thomas Trede 23 Jun '00

23 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, June 22, 2000 10:26 PM Subject: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification" > This is a IPng working group last call for comments on advancing the > following document as a Proposed Standard: > > Title : Extensions to IPv6 Neighbor Discovery for Inverse > Discovery Specification > Author(s) : A. Conta > Filename : draft-ietf-ion-ipv6-ind-03.txt > Pages : 22 > Date : 27-Oct-99 > > 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 July 6, 2000. > > 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: W.G. Last Call on "IP Version 6 Management Information Base for the Multicast Listener Discovery Protocol"
by Thomas Trede 20 Jun '00

20 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Monday, June 19, 2000 6:34 PM Subject: W.G. Last Call on "IP Version 6 Management Information Base for the Multicast Listener Discovery Protocol" > This is a IPng working group last call for comments on advancing the > following document as a Proposed Standard: > > Title : IP Version 6 Management Information Base for the > Multicast Listener Discovery Protocol > Author(s) : B. Haberman, R. Worzella > Filename : draft-ietf-ipngwg-mld-mib-03.txt > Pages : 14 > Date : 05-Jun-00 > > 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 July 3, 2000. > > 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: IPng Web Page Updated
by Thomas Trede 07 Jun '00

07 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, June 06, 2000 3:37 AM Subject: IPng Web Page Updated > I updated the IPv6 implementations page on the IPng web pages at: > > http://playground.sun.com/ipng > > Please let me know if I missed anyone's update. I plan to update the > specifications page in the next day or two. > > 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: IIJ to Launch Japan's First IPv6 Native Service
by Thomas Trede 07 Jun '00

07 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Jun-ichiro itojun Hagino" <itojun(a)iijlab.net> To: <users(a)ipv6.org> Sent: Wednesday, June 07, 2000 7:23 AM Subject: Re: IIJ to Launch Japan's First IPv6 Native Service > > > sorry for advertisement-ish email, I believe it is extremely > > good thing for IPv6. > > IIJ will start IPv6-only leased line ISP service, starting from > > September 1, 2000. > >IIJ to Launch Japan's First IPv6 Native Service > >http://www.iij.ad.jp/pressrelease/2000/ipv6-native-e.html > > forgot to note. (sorry if it is too obvious) > this is NOT based on IPv6-over-IPv4 tunnel. we carry IPv6 datagram > by IPv6 PPP native encapsulation - RFC2472. > > itojun > > --------------------------------------------------------------------- > The IPv6 Users Mailing List > Unsubscribe by sending "unsubscribe users" to majordomo(a)ipv6.org >

1 0

Fw: I-D ACTION:draft-ietf-ipngwg-mld-mib-03.txt
by Thomas Trede 07 Jun '00

07 Jun '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Tuesday, June 06, 2000 3:48 PM Subject: I-D ACTION:draft-ietf-ipngwg-mld-mib-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 : IP Version 6 Management Information Base for the > Multicast Listener Discovery Protocol > Author(s) : B. Haberman, R. Worzella > Filename : draft-ietf-ipngwg-mld-mib-03.txt > Pages : 14 > Date : 05-Jun-00 > > This document defines an experimental portion of the Management > Information Base (MIB) for use with network management protocols in > Internet Protocol Version 6 internets. Specifically, this document > is the MIB module which defines managed objects for implementations > of the Multicast Listener Discovery Protocol [MLD]. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-mld-mib-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-mld-mib-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-mld-mib-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