- ipv6-wg - mailman.ripe.net

Fw: RFC 2928 on Initial IPv6 Sub-TLA ID Assignments
by Thomas Trede 30 Sep '00

30 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "RFC Editor" <rfc-ed(a)ISI.EDU> To: <IETF-Announce: ;> Cc: <rfc-ed(a)ISI.EDU>; <ipng(a)sunroof.eng.sun.com> Sent: Saturday, September 30, 2000 2:11 AM Subject: RFC 2928 on Initial IPv6 Sub-TLA ID Assignments > > A new Request for Comments is now available in online RFC libraries. > > > RFC 2928 > > Title: Initial IPv6 Sub-TLA ID Assignments > Author(s): R. Hinden, S. Deering, R. Fink, T. Hain > Status: Informational > Date: September 2000 > Mailbox: hinden(a)iprg.nokia.com, deering(a)cisco.com, > rlfink(a)lbl.gov, tonyhain(a)microsoft.com > Pages: 7 > Characters: 11882 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-ipngwg-iana-tlal-03.txt > > URL: ftp://ftp.isi.edu/in-notes/rfc2928.txt > > > This document defines initial assignments of IPv6 Sub-Top-Level > Aggregation Identifiers (Sub-TLA ID) to the Address Registries. It is > intended as technical input to the Internet Assigned Numbers Authority > (IANA) from the Internet Engineering Task Force (IETF) Internet > Protocol Next Generation (IPNG) and Next Generation Transition > (NGTRANS) working groups, as an input to the process of developing > guidelines for the allocation of IPv6 addresses. > > This document was originally developed to provide advice to IANA in > the fall of 1998 and is being published at this time for the > historical record. The Internet Architecture Board (IAB) subsequently > requested that the IANA delegate these assignments to the Address > Registries. The IANA did this and the Address Registries are now > using them to assign IPv6 addresses. > > This document is a product of the IPNG Working Group of the IETF. > > This memo provides information for the Internet community. It does > not specify an Internet standard of any kind. Distribution of this > memo is unlimited. > > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body > help: ways_to_get_rfcs. For example: > > To: rfc-info(a)RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution.echo > Submissions for Requests for Comments should be sent to > RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC > Authors, for further information. > > > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute > > ... > > Below is the data which will enable a MIME compliant Mail Reader > implementation to automatically retrieve the ASCII version > of the RFCs. >

1 0

Fw: I-D ACTION:draft-ietf-dnsext-message-size-01.txt
by Thomas Trede 29 Sep '00

29 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <namedroppers(a)ops.ietf.org>; <ipng(a)sunroof.eng.sun.com> Sent: Friday, September 29, 2000 1:01 PM Subject: I-D ACTION:draft-ietf-dnsext-message-size-01.txt > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the DNS Extensions Working Group of the IETF. > > Title : DNSSEC and IPv6 A6 aware server/resolver message size > requirements > Author(s) : O. Gudmundsson > Filename : draft-ietf-dnsext-message-size-01.txt > Pages : 6 > Date : 28-Sep-00 > > This document mandates support for EDNS0 in DNS entities claiming to > support DNS Security Extensions and A6 records. This requirement is > necessary because these new features increase the size of DNS > messages. If EDNS0 is not supported fallback to TCP will happen, > having a detrimental impact on query latency and DNS server load. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-dnsext-message-size-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-dnsext-message-size-01.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-dnsext-message-size-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. >

1 0

Fw: I-D ACTION:draft-ietf-ipngwg-uni-based-mcast-00.txt
by Thomas Trede 28 Sep '00

28 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, September 28, 2000 12:45 PM Subject: I-D ACTION:draft-ietf-ipngwg-uni-based-mcast-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 : Unicast-Prefix-based IPv6 Multicast Addresses > Author(s) : B. Haberman, D. Thaler > Filename : draft-ietf-ipngwg-uni-based-mcast-00.txt > Pages : 5 > Date : 27-Sep-00 > > This specification defines an extension to the multicast addressing > architecture of the IP Version 6 protocol. The extension presented > in this document allows for unicast-prefix-based allocation of > multicast addresses. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-uni-based-mcast-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-uni-based-mcast-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-uni-based-mcast-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

Routing protocols?
by Niall Murphy 27 Sep '00

27 Sep '00

Hi folks, I am looking at doing some IPv6 routing and I'm wondering what the status of the various routing protocols is: 1) RIP is working I've been told (but I don't want to use it) 2) Is BGP working/defined? 3) What about IS-IS? 4) Who is doing production v6 routing at the moment? Thanks for any comments you might have. Niall -- Enigma Consulting

5 4

Fw: Last Call: Privacy Extensions for Stateless Address Autoconfiguration in IPv6 to Proposed Standard
by Thomas Trede 27 Sep '00

27 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "The IESG" <iesg-secretary(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Monday, September 25, 2000 8:25 PM Subject: Last Call: Privacy Extensions for Stateless Address Autoconfiguration in IPv6 to Proposed Standard > > The IESG has received a request from the IPNG Working Group to consider > Privacy Extensions for Stateless Address Autoconfiguration in IPv6 > <draft-ietf-ipngwg-addrconf-privacy-03.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 October 9, 2000. > > Files can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addrconf-privacy-03.tx t > -------------------------------------------------------------------- > 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: Request to Advance "Privacy Extensions for Stateless Address Autoconfiguration in IPv6"
by Thomas Trede 23 Sep '00

23 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: "Bob Hinden" <hinden(a)iprg.nokia.com> To: <Erik.Nordmark(a)eng.sun.com> Cc: <scoya(a)ietf.org>; <deering(a)cisco.com>; <ipng(a)sunroof.eng.sun.com>; <narten(a)raleigh.ibm.com> Sent: Friday, September 22, 2000 9:06 PM Subject: Request to Advance "Privacy Extensions for Stateless Address Autoconfiguration in IPv6" > Erik, > > The chairs of the IP Next Generation working group, on behalf of the > working group, request that the following document be published as an > Proposed Standard: > > Title : Privacy Extensions for Stateless Address > Autoconfiguration in IPv6 > Author(s) : T. Narten, R. Draves > Filename : draft-ietf-ipngwg-addrconf-privacy-03.txt > Pages : 16 > Date : 20-Sep-00 > > A working group last call for this document was completed on August 17, > 2000. The -03 version of the draft resolves issues raised during the > working group 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: I-D ACTION:draft-ietf-ipngwg-addrconf-privacy-03.txt
by Thomas Trede 21 Sep '00

21 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <Internet-Drafts(a)ietf.org> To: <IETF-Announce: ;> Cc: <ipng(a)sunroof.eng.sun.com> Sent: Thursday, September 21, 2000 12:39 PM Subject: I-D ACTION:draft-ietf-ipngwg-addrconf-privacy-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 : Privacy Extensions for Stateless Address > Autoconfiguration in IPv6 > Author(s) : T. Narten, R. Draves > Filename : draft-ietf-ipngwg-addrconf-privacy-03.txt > Pages : 16 > Date : 20-Sep-00 > > Nodes use IPv6 stateless address autoconfiguration to generate > addresses without the necessity of a DHCP server. Addresses are > formed by combining network prefixes with an interface identifier. On > interfaces that contain embedded IEEE Identifiers, the interface > identifier is typically derived from it. On other interface types, > the interface identifier is generated through other means, for > example, via random number generation. This document describes an > extension to IPv6 stateless address autoconfiguration for interfaces > whose interface identifier is derived from an IEEE identifier. Use of > the extension causes nodes to generate global-scope addresses from > interface identifiers that change over time, even in cases where the > interface contains an embedded IEEE identifier. Changing the > interface identifier (and the global-scope addresses generated from > it) over time makes it more difficult for eavesdroppers and other > information collectors to identify when different addresses used in > different transactions actually correspond to the same node. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addrconf-privacy-03.tx t > > 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-addrconf-privacy-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-addrconf-privacy-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

Fw: The Global IPv6 Summit in Japan
by Thomas Trede 15 Sep '00

15 Sep '00

FYI. Regards, Thomas Trede ----- Original Message ----- From: <cfp(a)jp.ipv6forum.com> To: <ipng(a)sunroof.eng.sun.com>; <ngtrans(a)sunroof.eng.sun.com> Sent: Thursday, September 07, 2000 3:47 AM Subject: The Global IPv6 Summit in Japan > Hello folks, > > "The Global IPv6 Summit in Japan" will be held in the next week of > IETF San-Diego. Presentations/Panels are spoken in Japanese but we > will prepare translators between Japanese and English. > > We would like to call for your participation. > > We prepare a session called "Business report on IPv6 around the > world". This would be a good chance for your company to appeal your > business strategy on IPv6. We would also like to call for your > presentation. > > See you in Osaka. > > // Global IPv6 Summit in Japan Steering Group > > ---- > Call for participations and presentations for > "The Global IPv6 Summit in Japan" > > <<Abstract>> > > The Global IPv6 Summit, under the organization of the IPv6 Forum, is > held regularly around the world to accelerate the deployment of > IPv6. We are happy to announce that this conference will be held in > Japan, one of the leading countries in the areas of IPv6 development > and deployment. > > The Internet is built on the foundations of the Internet Protocol > (IP). The current version of IP is named IPv4 after its version > number. The total number of devices that IPv4 can identify is limited > to about 4.3 billion. It's hard to see the Internet becoming the > foundation of a true, universal communications infrastructure when > this number is compared to the human population. > > In fact, it is expected that the entire address space of IPv4 will be > exhausted by around 2008. So, address assignment/allocation is > currently being carried out under a very restrictive policy. NAT > (Network Address Translator) was introduced as a temporary solution, > resulting in the loss of some of the original functionality of the > Internet. > > The principles of the Internet are end-to-end and bidirectional > communication. This means every node can communicate with every other > freely without any restrictions caused by intermediate nodes. Since > NAT broke these principles, it became difficult for unexpected novel > applications to appear in the current environment of the Internet. > > To resolve the exhaustion of IP addresses, extending its address space > is a straightforward solution. IPv6, the next generation of IP, > provides a huge number of IP addresses and makes NAT obsolete allowing > the Internet to recover its original principles. > > IPv6 is a paradigm recovery for applications. After deploying IPv6 and > recovering end-to-end/bidirectional communication, we cannot imagine > what kind of applications will appear. > > This conference will introduce the current deployment status of IPv6 > throughout the world. Also, panel discussions are planned, both on > "How IPv6 will Change Business" and on "Case Studies: Making the > Change to IPv6". > > Getting Internet people together, including those who are involved in > IPv6 activities and IPv4 business and management, we intend to discuss > the future of Internet business and the direction of engineering. > This conference will be beneficial for everyone including, but not > limited to, engineers, researchers, network managers and business > people. We would like to invite each of you to participate. > > <<The Host>> > > Global IPv6 Summit in Japan Steering Group > (Contact: info(a)jp.ipv6forum.com) > > <<Logistics>> > > Date: > December 18 - 19, 2000 > (As a part of Internet Week 2000) > Venue: > Grand Cube Osaka (Osaka International Convention Center) > 5-3-51, Nakanoshima, Kita-ku, Osaka 530-0005, JAPAN > Phone: +81-6-4803-5555 > Fax: +81-6-4803-5620 > E-mail: soumu(a)gco.co.jp > http://www.gco.co.jp/index.html > (The same place as Internet Week 2000) > > <<Registration Fee>> > > <Conference Fee> > > Early registration Regular/ > discount On-site registration > (until Oct 31) > Non-student 10,000 JPY 15,000 JPY > Student 2,000 JPY 2,000 JPY > > <Reception Free> > > Non-student 5,000 JPY > Student 3,000 JPY > > > <<Program>> > > December 18 (Mon) > > Keynote Speech 1: Dr. Jun Murai, WIDE Project > Session 1: Business report on IPv6 in Japan > Session 2: Status report from Asian countries > Session 3: Panel on how IPv6 will change business > > Reception > > December 19 (Tue) > > Keynote Speech 2: Dr. Steve Deering, Cisco Systems > Session 4: Business report on IPv6 around the world > Session 5: Case Studies: Making the Change to IPv6 > > <<Participation>> > > This conference will be held as a part of Internet Week 2000. Please > refer to the following page for registration: > > http://www.jp.ipv6forum.com/ > > <<Presentation Proposal>> > > The program committee calls for presentation proposal for "Session 4: > Business report of IPv6 in foreign contrives". Candidates are sTLA > holders and IPv6 vendors. Please propose a "10 minutes" presentation > on your IPv6 business. > > If you would like to give a presentation, please send an e-mail > message in the following form. Please note that we may not accept all > proposal due to the time limitations of the program. > > Format: See below > Deadline: September 30, 2000 > Notification date: October 6, 2000 > > To: cfp(a)jp.ipv6forum.com > Subject: presentation proposal > > Name : > Title : > Email : > Telephone number: > Organization : > Department : > > Your proposal in plain text (no more than 250 words) > explaining as concretely as possible your point of view and > what kind of presentation can be expected. > ---- > > > -------------------------------------------------------------------- > 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

Re: IAB/IESG Recommendations on IPv6 Address Delegation
by Turchanyi Geza 13 Sep '00

13 Sep '00

Fred, I would like to add a few comments and a proposal to your marvellous summary. (Even if it is very difficult to say anything at this stage). Comments: 1, The IPv6 address scheme might be valid for two centuries or even longer, and not only for 50 years. 2, The proposed "sparce allocation for subsribers (sites)", "dence allocation for providers (networks)" should work very well for customers, however, not necessarly for providers. You mentioned already the multihoming issues. There is an other open issue: how to scale effectively the routing. Proposal: I suggest adding a clause to your summary: ADDRESS ALLOCATION POLICY will be reviewed every five years. If different address allocation policy will be set up for any reason, then all subscribers and providers having already address space should adopt themselves to the new policy within TEN years, the latest. If they do not adopt, their not properly allocated address space will be blocked from the global routing. Many thanks for your time, best regards, Geza Turchanyi

2 1

agenda for joint ipv6/lir-wg session
by David Kessens 08 Sep '00

08 Sep '00

Please see below for the agenda for the joint session of the ipv6 wg and lir wg on ipv6 allocation policies. Thanks, David K. ---- A. Administrative stuff - appointment of scribe - agenda bashing B. Overview of open issues and changes in the new version of the ipv6 allocation policies document (Joao Luis Silva Damas, RIPE NCC) C. Overview of IAB/IESG Recommendations on IPv6 Address Delegation (Bob Hinden) D. Panel discussion with Bob Hinden/Steve Deering/Joao. (and other people that we will approach during the meeting). Z. AOB ---

1 0