- ipv6-wg - mailman.ripe.net

Fw: (ngtrans) Document Action: 6Bone Routing Practice to Informational
by Thomas Trede 03 Feb '99

03 Feb '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: The IESG <iesg-secretary(a)ietf.org> An: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: RFC Editor <rfc-editor(a)isi.edu>; Internet Architecture Board <iab(a)isi.edu>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Datum: Dienstag, 2. Februar 1999 21:45 Betreff: (ngtrans) Document Action: 6Bone Routing Practice to Informational > > >The IESG has approved the Internet-Draft '6Bone Routing Practice' ><draft-ietf-ngtrans-6bone-routing-01.txt> as a Informational. This >document is the product of the Next Generation Transition Working >Group. The IESG contact persons are Bert Wijnen and Harald >Alvestrand. >

1 0

Fw: (IPng 7149) Document Action: Basic Socket Interface Extensions for IPv6 to Informational
by Thomas Trede 03 Feb '99

03 Feb '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: The IESG <iesg-secretary(a)ietf.org> An: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: RFC Editor <rfc-editor(a)isi.edu>; Internet Architecture Board <iab(a)isi.edu>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Datum: Dienstag, 2. Februar 1999 21:41 Betreff: (IPng 7149) Document Action: Basic Socket Interface Extensions for IPv6 to Informational > > >The IESG has approved the Internet-Draft 'Basic Socket Interface >Extensions for IPv6' <draft-ietf-ipngwg-bsd-api-new-06.txt> as a >Informational. This document is the product of the IPNG Working >Group. The IESG contact persons are Jeffrey Burgan and Thomas Narten. > >-------------------------------------------------------------------- >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 7148) Protocol Action: Reserved IPv6 Subnet Anycast Addresses to Proposed Standard
by Thomas Trede 02 Feb '99

02 Feb '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: The IESG <iesg-secretary(a)ietf.org> An: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: RFC Editor <rfc-editor(a)isi.edu>; Internet Architecture Board <iab(a)isi.edu>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Datum: Dienstag, 2. Februar 1999 20:04 Betreff: (IPng 7148) Protocol Action: Reserved IPv6 Subnet Anycast Addresses to Proposed Standard > > >The IESG has approved the Internet-Draft 'Reserved IPv6 Subnet Anycast >Addresses' <draft-ietf-ipngwg-resv-anycast-02.txt> as a Proposed >Standard. This document is the product of the IPNG Working Group. The >IESG contact persons are Jeffrey Burgan and Thomas Narten. > > >Technical Summary > >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. > >Working Group Summary > >There was strong WG support for this document. Other documents in the >pipeline (e.g., Mobile IP for IPv6) make use of anycast addresses. > >Protocol Quality > >This document has been reviewed for the IESG by Thomas Narten. > >-------------------------------------------------------------------- >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 7147) Protocol Action: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels to Proposed Standard
by Thomas Trede 02 Feb '99

02 Feb '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: The IESG <iesg-secretary(a)ietf.org> An: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: RFC Editor <rfc-editor(a)isi.edu>; Internet Architecture Board <iab(a)isi.edu>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Datum: Dienstag, 2. Februar 1999 19:36 Betreff: (IPng 7147) Protocol Action: Transmission of IPv6 over IPv4 Domains without Explicit Tunnels to Proposed Standard > > >The IESG has approvedTransmission of IPv6 over IPv4 Domains without >Explicit Tunnels <draft-ietf-ipngwg-6over4-02.txt> as a Proposed >Standard. This document is the product of the IPNG Working Group. The >IESG contact persons are Jeffrey Burgan and Thomas Narten. > > >Technical Summary > >This document specifies how to run IPv6 over an IPv4 multicast >domain. The entire IPv4 cloud is treated as a virtual local link. >The motivation for this method is to allow isolated IPv6 hosts, >located on a physical link which has no directly connected IPv6 >router, to become fully functional IPv6 hosts by using an IPv4 >domain that supports IPv4 multicast as their virtual local >link. It uses IPv4 multicast as a "virtual Ethernet." > >This document specifies the frame format for transmission of IPv6 >packets and the method of forming IPv6 link-local addresses over IPv4 >domains. It also specifies the content of the Source/Target Link- >layer Address option used in the Router Solicitation, Router >Advertisement, Neighbor Solicitation, and Neighbor Advertisement and >Redirect messages, when those messages are transmitted on an IPv4 >multicast network. > >Working Group Summary > >There was consensus in the WG for this approach. > >Protocol Quality > >This document has been reviewed for the IESG by Thomas Narten. > >Note to RFC Editor: > >RFC 1972 is mentioned in the text, but is not listed in the >references. Please add a reference. >-------------------------------------------------------------------- >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: (ngtrans) I-D ACTION:draft-ietf-ngtrans-siit-05.txt
by Thomas Trede 01 Feb '99

01 Feb '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> An: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Datum: Montag, 1. Februar 1999 18:05 Betreff: (ngtrans) I-D ACTION:draft-ietf-ngtrans-siit-05.txt >A New Internet-Draft is available from the on-line Internet-Drafts directories. >This draft is a work item of the Next Generation Transition Working Group of the IETF. > > Title : Stateless IP/ICMP Translator (SIIT) > Author(s) : E. Nordmark > Filename : draft-ietf-ngtrans-siit-05.txt > Pages : 23 > Date : 29-Jan-99 > > This document specifies a transition mechanism in addition to those > already specified in RFC 1933. The new mechanism can be used as part > of a solution that allows IPv6 hosts that do not have a permanently > assigned IPv4 address to communication with IPv4-only hosts. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-siit-05.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-ngtrans-siit-05.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-ngtrans-siit-05.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. > ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-siit-05.txt

1 0

Fw: (IPng 7140) New IPng Internet Draft Procedure
by Thomas Trede 31 Jan '99

31 Jan '99

-----Urspr|ngliche Nachricht----- Von: Bob Hinden <hinden(a)iprg.nokia.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Cc: hinden(a)iprg.nokia.com <hinden(a)iprg.nokia.com>; deering(a)cisco.com <deering(a)cisco.com> Datum: Freitag, 29. Januar 1999 20:01 Betreff: (IPng 7140) New IPng Internet Draft Procedure >Please note that all new IPng Internet drafts submitted on or after >February 1, 1999 need to follow the procedure described in the attached email. > >This procedure includes the following: > > "All Internet-Drafts must begin with ONE of the following three > statements: > > This document is an Internet-Draft and is in full conformance > with all provisions of Section 10 of RFC2026. > > This document is an Internet-Draft and is in full conformance > with all provisions of Section 10 of RFC2026 except for the > right to produce derivative works. > > This document is an Internet-Draft and is NOT offered in > accordance with Section 10 of RFC2026, and will only exist as > an Internet-Draft. > > Any submission which does not include one (and only one) of the above > three statements will be returned to the submitter. The IETF > Secretariat will NOT add this text." > >The IPng w.g. chairs require anyone considering the submission an IPng >Internet Draft (i.e. draft-ietf-ipngwg-xxxx) that does not include the >first statement obtain permission from the chairs prior to publication. >Without the first statement is not possible to consider the draft for entry >into the standards process. > >Bob Hinden / Steve Deering >IPng w.g. Chairs > > >>To: IETF-Announce:; >>Subject: Revised Internet-Draft boilerplate >>From: The IESG <iesg-secretary(a)ietf.org> >>Date: Fri, 29 Jan 1999 11:23:40 -0500 >>Sender: scoya(a)ns.cnri.reston.va.us >> >> >>Following up on the discussion in the plenary session at the IETF meeting in >>Orlando and the discussion on the poised mailing list, the IESG on Thursday, >>January 28th approved the new boilerplate text that must be included with >>all Internet-Draft submissions. >> >>Beginning Monday, February 1, all Internet-Draft submissions must include >>the new boilerplate. Any submissions that do not use the new text will >>be returned to the author/submitter. >> >>The new template can be accessed with this URL: >> >> http://www.ietf.org/ietf/1id-guidelines.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: (IPng 7125) UPDATED AGENDA - V6 Deploy 3rd Day
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Jim Bound <bound(a)wasted.zk3.dec.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM>; 6bone(a)isi.edu <6bone(a)isi.edu>; v6-deployment-cabal(a)alpha.zk3.dec.com <v6-deployment-cabal(a)alpha.zk3.dec.com> Datum: Donnerstag, 28. Januar 1999 17:54 Betreff: (IPng 7125) UPDATED AGENDA - V6 Deploy 3rd Day >Folks, > >OK I added the last three requests including the one Bob F got on >ngtrans just now. > >Any more changes will have to be done on the fly folks. > >A saying for IPv6'ers: > > Poor or late Planning on your part does not constitute an emergency > on the WG, Authors, IESG, or Chairs part -----).... > >/jim > >=== >Thursday, February 4 -- IPv6 Deployment and Promotion >----------------------------------------------------- >The purpose of this day will be to review current deployment >activities, potential additional efforts, and opportunities for >educating and influencing developers, ISPs, network managers, and >users. This will include answering the following questions: >- Why would anyone run IPv6 now? >- Why would anyone ever run IPv6? >- Who will deploy IPv6 first? >- Will the Internet lead Corporate networks or follow as IPv6 is >deployed? >- How to get ISPs to deploy IPv6? > >We would like to request that each attendee come with answers to the >above questions for discussion on this 3rd day. > >This is the Final Agenda before Grenbole. We will do Agenda Bashing at >Grenoble and select order and times. > >Agenda: >(1) Discussion of the questions above. >(2) Existing deployment efforts: >- 6BONE (who?) >- 6REN (who?) >(3) Potential efforts: >- IPv6 Exchanges (who?) >- Corporate Plans (who?) >- ISP Plans (who?) >- ... >(4) Promotion >- IPv6.org (who?) >- Influencing developers, vendors, etc. (who?) >(5) Presentations: >- Bob Fink - 6REN and 6TAP >- Jim Bound - The Palo Alto Gateway and IPv6 and sub-TLA Request Strategy >- Marc Blanchet - IPv6 Deployment Issues >- Henk Steenman - Amsterdam Internet Exchange (AMS-IX) native IPv6 environment >- Jim Bound for Perry Metzger - Status of the V6 Deployment List Activities >- Jun Murai - IPv6 Deployment in Japan >- Paula Caslav - Proposed Guidelines RIPE NCC Regional Registries for IPv6 >- Jun-ichiro itojun Hagino - IPv6 verification technologies and open > result by FREE see: > http://www.tahil.org/ >- Latif LADID - Influencing IPv6 Developers and Promotion >- Kenji OTA - IETF Terminal Room Experiences with IPv6 >(6) Public Domain Code Needs for IPv6 Discussion >- Appache Web Server >- Sendmail >- BIND >- BSD Network Utilities > >thanks >/jim >-------------------------------------------------------------------- >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 7118) I-D ACTION:draft-ietf-ipngwg-resv-anycast-02.txt
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> To: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 28. Januar 1999 16:47 Subject: (IPng 7118) I-D ACTION:draft-ietf-ipngwg-resv-anycast-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. > >Note: This revision reflects comments received during the last call period. > > Title : Reserved IPv6 Subnet Anycast Addresses > Author(s) : D. Johnson, S. Deering > Filename : draft-ietf-ipngwg-resv-anycast-02.txt > Pages : 6 > Date : 27-Jan-99 > > 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. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-resv-anycast-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-resv-anycast-02.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html > >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-resv-anycast-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. > ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-resv-anycast-02.txt

1 0

Fw: (IPng 7117) I-D ACTION:draft-ietf-ipngwg-router-renum-07.txt
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> To: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 28. Januar 1999 16:47 Subject: (IPng 7117) I-D ACTION:draft-ietf-ipngwg-router-renum-07.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. > >Note: This revision reflects comments received during the last call period. > > Title : Router Renumbering for IPv6 > Author(s) : M. Crawford > Filename : draft-ietf-ipngwg-router-renum-07.txt > Pages : 26 > Date : 27-Jan-99 > > IPv6 Neighbor Discovery and Address Autoconfiguration conveniently > make initial assignments of address prefixes to hosts. Aside from > the problem of connection survival across a renumbering event, these > two mechanisms also simplify the reconfiguration of hosts when the > set of valid prefixes changes. > > This document defines a mechanism called Router Renumbering ('RR') > which allows address prefixes on routers to be configured and > reconfigured almost as easily as the combination of Neighbor > Discovery and Address Autoconfiguration works for hosts. It > provides a means for a network manager to make updates to the > prefixes used by and advertised by IPv6 routers throughout a site. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-07.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-router-renum-07.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-router-renum-07.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. > ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-router-renum-07.txt

1 0

agenda v2 for IPv6 working group RIPE32
by David Kessens 28 Jan '99

28 Jan '99

Hi, Below follows the most recent version of the IPv6 wg's agenda. David K. --- Proposed Agenda (draft v2) for the IPv6 Working Group Meeting RIPE32, Januari 1999, Amsterdam A. Administrative stuff (David Kessens, chair, 5min) - appointment of scribe - agenda bashing B. Selection of chair C. Review of action points: 31.1 RIPE NCC will start allocating IPv6 addresses by the next RIPE meeting in January. 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. D. Status of 6bone (David Kessens) E. 6REN - first IPv6 production network (David Kessens, presentation originally from Bob Fink) F. IPv6 allocation progress (Paula Caslav) - discussion of 'IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT (3rd draft)' G. Experience from ISPs with IPv6 (input from audience requested) H. Future directions of the wg Z. AOB

1 0