- ipv6-wg - mailman.ripe.net

Fw: (ngtrans) I-D ACTION:draft-ietf-ngtrans-translator-01.txt
by Thomas Trede 26 Jan '99

26 Jan '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: Dienstag, 26. Januar 1999 18:01 Betreff: (ngtrans) I-D ACTION:draft-ietf-ngtrans-translator-01.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 : Categorizing Translators between IPv4 and IPv6 > Author(s) : K. Yamamoto, M. Sumikawa > Filename : draft-ietf-ngtrans-translator-01.txt > Pages : 7 > Date : 25-Jan-99 > > This memo categorizes translators between IPv4 and IPv6. The two > components, address interpretation and address mapping, are > discussed. This draft is based on a paper appeared in the > proceedings of INET98[INET]. The intention of this memo is > circulation of such knowledge. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-translator-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-ngtrans-translator-01.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-ngtrans-translator-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. > ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-translator-01.txt

1 0

Fw: (ngtrans) I-D ACTION:draft-ietf-ngtrans-6to4-00.txt
by Thomas Trede 26 Jan '99

26 Jan '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: Dienstag, 26. Januar 1999 18:01 Betreff: (ngtrans) I-D ACTION:draft-ietf-ngtrans-6to4-00.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 : Connection of IPv6 Domains via IPv4 Clouds > without Explicit Tunnels > Author(s) : B. Carpenter, K. Moore > Filename : draft-ietf-ngtrans-6to4-00.txt > Pages : 10 > Date : 25-Jan-99 > > This memo specifies an optional mechanism for assigning a unique > IPv6 address prefix to any site that currently has at least one > globally unique IPv4 address, and describes scenarios for using such > a prefix during the co-existence phase of IPv4 to IPv6 transition. > > The motivation for this method is to allow isolated IPv6 domains, > attached to an IPv4 network which has no native IPv6 support, to > communicate with other such IPv6 domains with minimal manual > configuration. Effectively it treats the IPv4 network as a virtual > link layer. It also automatically provides 80 bits of globally unique > IPv6 address space to any site with at least one globally unique IPv4 > address. If combined with a Network Address Translator (NAT), it > allows the NAT to provide a globally-unique and globally-routable > IPv6 address to each of its client hosts. > > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-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-ngtrans-6to4-00.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-ngtrans-6to4-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. > ENCODING mime FILE /internet-drafts/draft-ietf-ngtrans-6to4-00.txt

1 0

(IPng 7085) Protocol Action: A Method for the Transmission of IPv6 Packets over ARCnet Networks. to Proposed Standard (fwd)
by Thomas Trede 23 Jan '99

23 Jan '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Fri, 22 Jan 1999 12:16:28 -0500 From: The IESG <iesg-secretary(a)ietf.org> To: 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 Subject: (IPng 7085) Protocol Action: A Method for the Transmission of IPv6 Packets over ARCnet Networks. to Proposed Standard The IESG has approved A Method for the Transmission of IPv6 Packets over ARCnet Networks <draft-souvatzis-ipv6-arcnet-05.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 defines how to run IPv6 over an ARCnet network. It defines the protocol ID, encapsulation format, method for forming interface identifiers, etc. Working Group Summary There was consensus within the WG for this document. 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: (ngtrans) W.G. Last Call on "Bump-in-the-Stack" for Experimental RFC
by Thomas Trede 22 Jan '99

22 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Bob Fink <fink(a)es.net> An: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Cc: Kazuaki Tsuchiya <tsuchi(a)ebina.hitachi.co.jp>; Tony Hain <tonyhain(a)microsoft.com>; Bob Fink <fink(a)es.net>; Harald Tveit Alvestrand <Harald.Alvestrand(a)maxware.no>; Bert Wijnen <WIJNEN(a)VNET.IBM.COM> Datum: Freitag, 22. Januar 1999 04:41 Betreff: (ngtrans) W.G. Last Call on "Bump-in-the-Stack" for Experimental RFC >NGtrans Folk, > >I have still not seen any comments against moving forward with >"Bump-in-the-Stack" as Experimental RFC per my email in late December. Thus >I'm proceeding with a "last call". > >This is an NGtrans working group last call for comments on advancing the >following document as an Experimental RFC: > > Title : Dual Stack Hosts using the "Bump-in-the-Stack" Technique > Author(s) : K. Tsuchiya, H. Higuchi & Y. Atarashi > Filename : draft-ietf-ngtrans-dual-stack-hosts-00.txt > Pages : 11 > Date : 16-Nov-98 > >Please send substantive comments to the ngtrans mailing list, and minor >editorial comments to the authors. This last call period will end two >weeks from today on February 5, 1999. > >Bob Fink/ Tony Hain > > > >

1 0

Fw: (IPng 7076) Interim Meeting registration fees.
by Thomas Trede 21 Jan '99

21 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Alain Durand <Alain.Durand(a)imag.fr> 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> Datum: Donnerstag, 21. Januar 1999 15:17 Betreff: (IPng 7076) Interim Meeting registration fees. >Hi. > >We came out with a solution to get you some lunch during the meeting. >We will have a catering service with a buffet and we will have to charge >some fees for that. >The registration fees, covering the 3 lunches and 3 afternoom breaks, >will be 100F per day. > >So, the total will be 300F (about $50) for the meeting and >450F (300+150) if you attend the social. > >We will open a registration desk on tuesday, Feb. 2nd, morning at 8:00 AM. > >--------------------------------------------------------------------------- - >--------- >---- Please come with ***exact*** change in cash in french francs ---- >--------------------------------------------------------------------------- - >--------- > >We can take french checks from a french bank, >but we can not take credit cards. > > - Alain. > >-------------------------------------------------------------------- >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) Grenoble Discussion - Proposals to assist "initial" transition of IPv6
by Thomas Trede 20 Jan '99

20 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Jim Bound <bound(a)wasted.zk3.dec.com> An: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Cc: bound(a)zk3.dec.com <bound(a)zk3.dec.com> Datum: Mittwoch, 20. Januar 1999 16:57 Betreff: (ngtrans) Grenoble Discussion - Proposals to assist "initial" transition of IPv6 >Folks, > >At the Grenoble Interim meeting it would be really great if during the >ngtrans session if we could discuss the merits and differences between >the initial set of proposals that would be useful to assist IPv6 >deployment. In addition we should also discuss the implementation >complexities for each of them. Also what common implementation problems >to each of them face which are similar (e.g. DNS, Assignment of >Addresses). The list below are the ones I would think are important for >initial deployment and then I list the ones which may be needed later. >We can debate the order but covering the first set would be a lot of >work if folks want we can cover the second set at Minnieapolis. > >draft-ietf-ngtrans-dti-00.txt (note this proposal contrasts and >compares the others here in the draft and I think incorrectly but I will >be sending my input on this to the list before Grenoble soon). > >draft-ietf-ngtrans-natpt-04.txt > >draft-ietf-ngtrans-siit-04.txt > >draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt > >Could I ask for some volunteers to help lead with me such a discussion >and if possible do some prepartory work with me offline? > >The ones we need to do later are: > >draft-ietf-ngtrans-dual-stack-hosts-00.txt > >draft-ietf-ngtrans-ipv4-ipv6-xlator-00.txt > >draft-ietf-ngtrans-translator-00.txt > >thanks >/jim >

1 0

Fw: (IPng 7071) I-D ACTION:draft-ietf-ipngwg-6over4-02.txt
by Thomas Trede 20 Jan '99

20 Jan '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: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Datum: Mittwoch, 20. Januar 1999 17:56 Betreff: (IPng 7071) I-D ACTION:draft-ietf-ipngwg-6over4-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 : Transmission of IPv6 over IPv4 Domains > without Explicit Tunnels > Author(s) : B. Carpenter, C. Jung > Filename : draft-ietf-ipngwg-6over4-02.txt > Pages : 9 > Date : 19-Jan-99 > > This memo specifies the frame format for transmission of IPv6 [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. > > 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.' > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-6over4-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-6over4-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-6over4-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-6over4-02.txt

1 0

Fw: (IPng 7070) Protocol Action: A Method for the Transmission of IPv6 Packets over ARCnet Networks. to Proposed Standard
by Thomas Trede 20 Jan '99

20 Jan '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: Mittwoch, 20. Januar 1999 16:57 Betreff: (IPng 7070) Protocol Action: A Method for the Transmission of IPv6 Packets over ARCnet Networks. to Proposed Standard > > >The IESG has approved A Method for the Transmission of IPv6 Packets >over ARCnet Networks <draft-souvatzis-ipv6-arcnet-05.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 defines how to run IPv6 over an ARCnet network. It >defines the protocol ID, encapsulation format, method for forming >interface identifiers, etc. > >Working Group Summary > >There was consensus within the WG for this document. > >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 7069) Last Call: IPv6 Addressing Architecture and Aggregatable Global Unicast Address Format to Draft
by Thomas Trede 20 Jan '99

20 Jan '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: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Datum: Mittwoch, 20. Januar 1999 15:23 Betreff: (IPng 7069) Last Call: IPv6 Addressing Architecture and Aggregatable Global Unicast Address Format to Draft > >The IESG has received a request to consider elevating the following two >RFCs (current Proposed Standards) to Draft Standard. > > o RFC2373: IP Version 6 Addressing Architecture > > o RFC2374: An IPv6 Aggregatable Global Unicast Address Format > >These documents are a product of the IPNG Working Group of the IETF. > >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)cnri.reston.va.us or ietf(a)ietf.org mailing lists by February 2,1999. > >Files can be obtained via http://www.ietf.org/rfc/rfc2273.txt > http://www.ietf.org/rfc/rfc2274.txt > > >All Implementation Reports can be found at: >http://www.ietf.org/IESG/implementation.html >-------------------------------------------------------------------- >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

IPv6 addressing delegation
by Rute Sofia 19 Jan '99

19 Jan '99

At the 31th RIPE Meeting was said that by January 1999 RIPE would start delegating IPv6 addresses: "January 1999: start allocating IPv6 addresses (depends on IANA to be ready to allocate to the regional registries and on the registries to get their databases and procedures compliant)". FCCN is a pTLA at the 6bone and, as a service provider is interested in having real IPv6 addressing space as soon as possible. We would like to know, if possible, what is the sate of IPv6 address allocation, and what is the procedure one has to follow in order to obtain IPv6 addresses. Thanks, Rute Sofia --------------------------------------------------- Helena Rute Esteves Carvalho Sofia FCCN Av. do Brasil, 101 1799 LISBOA CODEX tel.: 8440100 fax: 8472167 e-mail: rsofia(a)rccn.net "After silence, that which comes nearest to expressing the inexpressible is Music." - Aldous Huxley ---------------------------------------------------

2 1