- ipv6-wg - mailman.ripe.net

Fw: (ngtrans) I-D ACTION:draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt
by Thomas Trede 15 Jan '99

15 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: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 14. Januar 1999 00:19 Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-assgn-ipv4-addrs-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 : Assignment of IPv4 Global Addresses to > IPv6 Hosts (AIIH) > Author(s) : J. Bound > Filename : draft-ietf-ngtrans-assgn-ipv4-addrs-01.txt > Pages : 18 > Date : 12-Jan-99 > > The initial deployment of IPv6 will require a tightly coupled use of > IPv4 addresses to support the interoperation of IPv6 and IPv4. Nodes > will be able to be deployed with IPv6 addresses, but will still need > to communicate with IPv4 nodes that do not have a dual IP layer > supporting both IPv4 and IPv6. This specification defines a > mechanism called Assignment of IPv4 Global Addresses to IPv6 Hosts > (AIIH), which will assign an IPv6 Host a temporary IPv4 Global > Address, which can be used to communicate with a Host that supports > IPv4 or IPv4/IPv6. An objective of this specification is to avoid > the use of address translation for the deployment of IPv6 in a > network. Another objective is to demonstrate that IPv6 Addresses can > be deployed now instead of non-Global IPv4 Addresses within an > Intranet. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-assgn-ipv4-addrs-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-assgn-ipv4-addrs-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-assgn-ipv4-addrs-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-assgn-ipv4-addrs-01.txt

1 0

Fw: (ngtrans) W.G. Last Call on "Network Address Translation - Protocol Translation (NAT-PT)"
by Thomas Trede 14 Jan '99

14 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Bob Fink <fink(a)es.net> To: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Cc: George Tsirtsis <george(a)gideon.bt.co.uk>; 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> Date: Donnerstag, 14. Januar 1999 00:19 Subject: (ngtrans) W.G. Last Call on "Network Address Translation - Protocol Translation (NAT-PT)" >NGtrans Folk, > >Thanks to George for the cleanup of NAT-PT per the Orlando IETF meeting. > >This is an NGtrans working group last call for comments on advancing the >following document as an Experimental RFC: > > Title : Network Address Translation - Protocol Translation (NAT-PT) > Author(s) : G. Tsirtsis & P. Srishuresh > Filename : draft-ietf-ngtrans-natpt-04.txt > Pages : 15 > Date : 13-Jan-99 > >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 January 27, 1999. > >Bob Fink/ Tony Hain > > >

1 0

draft agenda v1 for IPv6 working group RIPE32
by David Kessens 12 Jan '99

12 Jan '99

Hi, Recently, Thomas Trede let me and Rob Blokzijl know that he was no longer available as chairman of the IPv6 working group. He proposed to me and Rob Blokzijl if I could take up this function for the next RIPE meeting. I have agreed to do so. I would like to thank Thomas for chairing the working group. Attached please find the 1st draft of the proposed agenda for the IPv6 wg meeting during RIPE32 in Amsterdam. A working group session is supposed to have active participation of it's members. In the past, we have seen a fair amount of interest in the topic of IPv6 but at the same time a lack of knowledge from parts of the audience. I would like to know if there are volunteers who are willing to talk about the following topics: - How to get started with IPv6: sample IPv6 setup - using one of the available implementations - IPv6 routing/multi homing - IPv6 address allocation - general introduction to IPv6 - or anything that you think that might be useful. Furthermore, on a topic that is closely related to the lir-wg, I am looking for somebody from the RIPE NCC who can give us an update on the IPv6 allocation status. Other topics and input is of course more then welcome! I am looking forward to see many of you in Amsterdam! David K. --- Proposed Agenda (draft v1) 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. Status of 6bone (David Kessens) D. 6REN - first IPv6 production network (David Kessens, presentation originally from Bob Fink) E. IPv6 allocation progress (RIPE NCC) Z. AOB ---

2 1

Fw: (IPng 7012) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-05.txt
by Thomas Trede 12 Jan '99

12 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: Mittwoch, 6. Januar 1999 16:05 Subject: (IPng 7012) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-05.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-bsd-api-new-05.txt > Pages : 33 > Date : 05-Jan-99 > >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-bsd-api-new-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-ipngwg-bsd-api-new-05.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-bsd-api-new-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-ipngwg-bsd-api-new-05.txt

1 0

Fw: (ngtrans) Grenoble interim IETF social event
by Thomas Trede 11 Jan '99

11 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Alain Durand <Alain.Durand(a)imag.fr> To: 6bone(a)isi.edu <6bone(a)isi.edu>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 7. Januar 1999 19:34 Subject: (ngtrans) Grenoble interim IETF social event >Hi alll. > >The agenda is now online on http://www.ipv6.imag.fr/ietf1999.html. > >Also, I'm pleased to announce that we will have a social event >on tuesday evening. Places are limited to 50 only... sorry about that, >so they'll go to the first 50 who will register. Be quick! > >More on this social event on the web server. >To register to the social, send e-mail to ietf(a)imag.fr > > - Alain. > >

1 0

Fw: (IPng 7031) Request to Advance "Separating Identifiers and Locators in Addresses: An Analysis of the GSE Proposal for IPv6"
by Thomas Trede 11 Jan '99

11 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com <narten(a)raleigh.ibm.com>; Jeffrey Burgan <burgan(a)corp.home.net> Cc: scoya(a)cnri.reston.va.us <scoya(a)cnri.reston.va.us>; deering(a)cisco.com <deering(a)cisco.com>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 7. Januar 1999 23:02 Subject: (IPng 7031) Request to Advance "Separating Identifiers and Locators in Addresses: An Analysis of the GSE Proposal for IPv6" >Jeff, Thomas, > >The chairs of the IP Next Generation working group, on behalf of the >working group, request that the following document be published as an >Informational RFC: > > Title : Separating Identifiers and Locators > in Addresses: An Analysis of the GSE Proposal > for IPv6 > Author(s) : M. Crawford, A. Mankin, T. Narten, > J. Stewart, L. Zhang > Filename : draft-ietf-ipngwg-esd-analysis-03.txt > Pages : 50 > Date : 20-Nov-98 > >A working group last call for this document was completed on January 4, >1999. No comments were received. > >Bob Hinden / Steve Deering >IPng Working Group Co-Chairs > > > >-------------------------------------------------------------------- >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 7033) Request to Advance "Basic Socket Interface Extensions for IPv6"
by Thomas Trede 11 Jan '99

11 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com <narten(a)raleigh.ibm.com>; Jeffrey Burgan <burgan(a)corp.home.net> Cc: scoya(a)cnri.reston.va.us <scoya(a)cnri.reston.va.us>; deering(a)cisco.com <deering(a)cisco.com>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 7. Januar 1999 23:25 Subject: (IPng 7033) Request to Advance "Basic Socket Interface Extensions for IPv6" >Jeff, Thomas, > >The chairs of the IP Next Generation working group, on behalf of the >working group, request that the following document be published 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-bsd-api-new-05.txt > Pages : 33 > Date : 05-Jan-99 > >This document replaces RFC2133. RFC2133 should become Historical. > >A working group last call for this document was completed on November 3, >1998 and this document was discussed at the IPng session at the Orlando >IETF. The current draft (-05) incorporates comments received during the >last call. > >Bob Hinden / Steve Deering >IPng Working Group Co-Chairs > >-------------------------------------------------------------------- >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 7032) Request to Advance RFC2373 and RFC2374 to Draft Standard
by Thomas Trede 11 Jan '99

11 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Bob Hinden <hinden(a)iprg.nokia.com> To: narten(a)raleigh.ibm.com <narten(a)raleigh.ibm.com>; Jeffrey Burgan <burgan(a)corp.home.net> Cc: scoya(a)cnri.reston.va.us <scoya(a)cnri.reston.va.us>; deering(a)cisco.com <deering(a)cisco.com>; ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 7. Januar 1999 23:26 Subject: (IPng 7032) Request to Advance RFC2373 and RFC2374 to Draft Standard >Jeff, Thomas, > >The chairs of the IP Next Generation working group, on behalf of the >working group, request that the following documents be published as >Draft Standards: > > RFC2373 IP Version 6 Addressing Architecture > > RFC2374 An Aggregatable Global Unicast Address Format > >An implementation report for these RFC's is available at: > > ftp://playground.sun.com/pub/ipng/implementation-reports > > as: > > add-arch-aggregat.txt > >A working group last call for this document was completed on January 4, >1999. No comments were received. Advancing these documents to draft >standard was also discussed at the Orlando IETF meeting. > >Bob Hinden / Steve Deering >IPng Working Group Co-Chairs > > > >-------------------------------------------------------------------- >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) interim meeting planning
by Thomas Trede 16 Dec '98

16 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: Steve Deering <deering(a)cisco.com> To: 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> Cc: hinden(a)iprg.nokia.com <hinden(a)iprg.nokia.com>; rlfink(a)lbl.gov <rlfink(a)lbl.gov>; tonyhain(a)microsoft.com <tonyhain(a)microsoft.com>; deering(a)cisco.com <deering(a)cisco.com> Date: Mittwoch, 16. Dezember 1998 09:30 Subject: (ngtrans) interim meeting planning >As mentioned in the ipngwg and ngtrans meetings in Orlando last week, >the chairs of the two working groups propose to hold a two-day joint >interim meeting in the first week of February to discuss the next steps >in IPv6 standardization, implementation, transition, and deployment. >We propose also to allocate a third day for non-working-group business, >such as coordination of the 6bone, 6ren, and other IPv6-related >initiatives. A more concrete agenda is in preparation, but of >immediate concern is deciding where to meet. We have narrowed it >down to two choices: > > (1) the San Francisco Bay Area > > (2) Grenoble, France > >The meeting dates will be February 2-4. > >We would like to hear as soon as possible (like, within the next 24 hours) >from those of you who would like to attend the meeting but will be able >to attend in only one of those two places. Specifically: > > - If you can attend in either place, do not reply. > > - If you cannot attend in either place, do not reply, > > - If you can attend in only one of those two places, > please reply as soon as possible to Bob, Bob, Tony, and me > (our addresses are in the Cc: line, above; please do NOT reply > to the three mailing lists in the To: line!), and tell us > in which place you can attend. > >Thanks, >Steve > > >

1 0

Fw: (IPng 6884) Last Call: Mobility Support in IPv6 to Proposed Standard
by Thomas Trede 16 Dec '98

16 Dec '98

FYI. Regards, Thomas Trede -----Original Message----- From: The IESG (by way of Bob Hinden <hinden(a)iprg.nokia.com>) <iesg-secretary(a)ietf.org> To: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Dienstag, 15. Dezember 1998 19:12 Subject: (IPng 6884) Last Call: Mobility Support in IPv6 to Proposed Standard > >The IESG has received a request from the IP Routing for Wireless/Mobile >Hosts Working Group to consider Mobility Support in IPv6 ><draft-ietf-mobileip-ipv6-07.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 January 7, 1999. > >Files can be obtained via >http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-07.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