January 1999 - ipv6-wg - mailman.ripe.net

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

Fw: (IPng 7065) Grenoble meeting: maps
by Thomas Trede 19 Jan '99

19 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Alain Durand <Alain.Durand(a)imag.fr> 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> Date: Montag, 18. Januar 1999 20:03 Subject: (IPng 7065) Grenoble meeting: maps >Hi folks > >I've scanned some maps of Grenoble and the university campus. >You'll find them on http://www.ipv6.imag.fr/ietf1999.html > >Also, there are 10 places left for the social... > > - 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) I-D ACTION:draft-ietf-ngtrans-natpt-04.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 17:07 Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-natpt-04.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 : Network Address Translation - Protocol > Translation (NAT-PT] > Author(s) : G. Tsirtsis, P. Srisuresh > Filename : draft-ietf-ngtrans-natpt-04.txt > Pages : 15 > Date : 13-Jan-99 > > This document specifies a transition mechanism in addition to those > already specified in [TRANS]. The new mechanism provides an > end-to-end solution to allow IPv6-only hosts to communicate with > IPv4-only hosts and vice versa using Network Address Translation > and Protocol Translation. The scheme described does not require du- > al-stack hosts; nor does it mandate any routing related changes on > the hosts. The scheme is based on a combination of address transla- > tion theme as described in [NAT-TERM] and V6/V4 protocol transla- > tion theme as described in [SIIT]. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-natpt-04.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-natpt-04.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-natpt-04.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-natpt-04.txt

1 0

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