- ipv6-wg - mailman.ripe.net

PDCD1
by ilupe74＠econonews.com 12 May '98

12 May '98

* NOTICE: ANSWERS ARE READ AUTOMATICALLY. - ONLY SEND US BACK THIS MESSAGE IF YOU ARE INTERESTED IN OUR JOURNAL. IF YOU WISH TO RECEIVE "BREAKFAST AND DIAMONDS" IN SPANISH, INDICATE IN THE E-MAIL SUBJECT: ES (e.g.: DCD1ES) - IF YOU SEND US BACK THIS MESSAGE MORE THAN ONCE, "BREAKFAST WITH DIAMONDS" WILL BE FORWARDED AS MANY TIMES AS YOU HAVE SENT IT. *ATENCION: LAS RESPUESTAS DE ESTE E-MAIL SE LEEN AUTOMATICAMENTE. - SOLO DEBERA REBOTAR ESTE MENSAJE EN CASO DE ESTAR INTERESADO EN NUESTRO PERIODICO. SI QUIERE RECIBIR "DESAYUNE CON DIAMANTES" EN ESPAÑOL AÑADA EN EL ASUNTO LA ABREVIATURA: ES (EJ.DCD1ES). - SI REBOTA MAS DE UNA VEZ ESTE E-MAIL LE ENVIAREMOS "DESAYUNE CON DIAMANTES" TANTAS VECES COMO LO HAYA REBOTADO. Dear Sir/Madam, Would you like to have breakfast with diamonds? You probably think that this only happens in movies. However, our wish is to make your dreams come true and that you have breakfast while reading the hottest economic news in "Breakfast with Diamonds". "Breakfast with Diamonds" is an ALIVE JOURNAL, since news are hourly updated, INTERACTIVE, since our subscribers have the opportunity to ask for further information of any piece of news (free service), and GLOBAL since it includes the most significant news worldwide. INFORMATION IS KNOWLEDGE AND KNOWLEDGE IS POWER If you wish to learn more about "Breakfast with Diamonds" we cordially invite you to visit our website: http://www.econonews.com If you wish to receive "Breakfast with Diamonds" for a free 30-day trial, you just have to send us back this message. Sorry for any inconvenience we may have caused you and thank you for your time. Yours faithfully, Breakfast with Diamonds Marketing Director

1 0

Draft agenda for RIPE 30
by Thomas Trede 11 May '98

11 May '98

Hello, sorry for the delay. If you have comments, addendums for the agenda, please let me know ! Regards, Thomas Proposed Agenda for the IPV6 Working Group RIPE-30, May 1998, Stockholm 1st Draft, 11.05.1998 1. Administrative stuff (Thomas Trede, chair) - volunteering of the scribe - agenda bashing 2. Reports - 6Bone - IETF, proceedings IPV6 - input/presentation by Bob Hinden ?? (to be arranged and himself to be asked !) - News about manufacturers implementation - input from the audience 3. Current status of RIPE regarding address assignments in IPV6 - with input from RIPE NCC (if available/necessary) 4. General Input from other Working Groups 5. AOB ------------------------------------------------------------------- Thomas Trede Nacamar Data Communications Senior Network Architect P.O.Box 102262 63268 Dreieich / Germany e-mail: trede(a)nacamar.net voice: +49-6103-993-910 www : www.nacamar.net fax : +49-6103-993-999 -------------------------------------------------------------------

1 0

(IPng 5789) I-D ACTION:draft-ietf-diffserv-headers-00.txt (fwd)
by Thomas Trede 09 May '98

09 May '98

FYI. Regards, Thomas ---------- Forwarded message ---------- Date: Fri, 08 May 1998 10:17:55 -0700 From: "by way of Bob Hinden <hinden(a)iprg.nokia.com>" <Internet-Drafts(a)ietf.org> To: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 5789) I-D ACTION:draft-ietf-diffserv-headers-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Differentiated Services Working Group of the IETF. Title : Definition of the Differentiated Services Field (DS Byte) in the IPv4 and IPv6 Headers Author(s) : K. Nichols, S. Blake Filename : draft-ietf-diffserv-headers-00.txt Pages : 11 Date : 07-May-98 Differentiated services are intended to provide scalable service discrimination in the Internet without the need for per-flow state and signaling at every hop. A variety of services may be built from a small, well-defined set of building blocks which are deployed in network nodes. The services may be either end-to-end or intra- domain. Services can be provided by a combination of: - setting bits in an IP header field at network edges and administrative boundaries, - using those bits to determine how packets are forwarded by the routers inside the network, and - conditioning the marked packets at network boundaries in accordance with the requirements or rules of each service. This document defines the IP header field, called the DS (for differentiated services) byte. In IPv4, it takes the place of the TOS octet; in IPv6, it takes the place of the Traffic Class octet. A differentiated services-capable network node includes a classifier that selects packets based on the value of the DS byte and is capable of delivering the specific packet forwarding treatment corresponding to that value. This document defines two packet forwarding treatments, or per-hop behaviors. Setting of the DS byte and other conditioning of the dynamic behavior of marked packets need only be performed at network boundaries and may vary in complexity. For a more complete understanding of differentiated services, this document should be read along with its companion documents, the differentiated services architecture [ARCH], the differentiated services framework [FWK], and other documents which specify additional per-hop behaviors, such as [Baker]. Internet-Drafts are 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-diffserv-headers-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-diffserv-headers-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-diffserv-headers-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. Content-Type: text/plain Content-ID: <19980508125124.I-D(a)ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-diffserv-headers-00.txt <ftp://ftp.ietf.org/internet-drafts/draft-ietf-diffserv-headers-00.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

Last Call: Internet Protocol, Version 6 (IPv6) Specification to Draft Standard (fwd)
by Fred Baker 06 May '98

06 May '98

At 7:37 AM -0700 5/6/98, jkrey(a)ISI.EDU wrote: >>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 May 19, 1998. > > It's really nice that the IETF/IESG always manages to find deadlines > just before or in between a RIPE meeting. Ignorance or intention ?-( > Could please RIPE make an official note on that !? We could decide to not schedule anything anytime during or within two weeks before a RIPE meeting, an IETF meeting, the interim meeting of any IETF working group, meetings of ITU, ANSI, or ISO Study Groups, meetings of APNIC, ARIN, APRICOT, NANOG, the IEEE Communications Society, ACM SIGCOMM, InterOp, and similar organization. I believe the net effect would be that all work was accomplished on Christmas Morning, since all such groups sensibly manage to miss that date. :^) :^) :^) On reflection, I think you'll agree that such scheduling is np-hard, and is not a reasonable expectation. You have the standard two weeks to reply, and if you need more, you could advise the AD in question (which would, I believe, be Thomas Narten) that you will need a little more time and tell him when you expect to get your comments to him. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If at first you don't succeed, call it version 1.0.

1 0

RE: (IPng 5773) Last Call: Internet Protocol, Version 6 (IPv6) Specification to Draft Standard (fwd)
by Christian Panigl, ACOnet/UniVie 06 May '98

06 May '98

>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 May 19, 1998. It's really nice that the IETF/IESG always manages to find deadlines just before or in between a RIPE meeting. Ignorance or intention ?-( Could please RIPE make an official note on that !? Tnx CP

1 0

None
by Joseph FARAULT 06 May '98

06 May '98

help == Please send e-mail to JFarault(a)POBoxes.com _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

None
by Joseph FARAULT 06 May '98

06 May '98

subscribe ipv6-wg == Please send e-mail to JFarault(a)POBoxes.com _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

(IPng 5773) Last Call: Internet Protocol, Version 6 (IPv6) Specification to Draft Standard (fwd)
by Thomas Trede 05 May '98

05 May '98

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Tue, 05 May 1998 06:55:47 -0400 From: The IESG <iesg-secretary(a)ietf.org> Reply-To: iesg(a)ietf.org To: IETF-Announce:;;;;@CNRI.Reston.VA.US;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 5773) Last Call: Internet Protocol, Version 6 (IPv6) Specification to Draft Standard The IESG has received a request from the IPNG Working Group to consider the following as Draft Standards: o Internet Protocol, Version 6 (IPv6) Specification <draft-ietf-ipngwg-ipv6-spec-v2-01.txt> replacing RFC 1883, currently a Proposed Standard. o Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification <draft-ietf-ipngwg-icmp-v2-00.txt> replacing RFC 1885, currently a Proposed Standard o Path MTU Discovery for IP version 6 <rfc1981>, currently 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 May 19, 1998. Files can be obtained via ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-ipv6-spec-v2-01.txt ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipngwg-icmp-v2-00.txt ftp://ftp.isi.edu/in-notes/rfc1981.txt Implemenation Reports for all three 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

(no subject)
by Martin Bauer-Marschallinger 23 Apr '98

23 Apr '98

subscribe

1 0

RE: IPv6 Address Management Plan
by Jim Fleming 22 Apr '98

22 Apr '98

On Wednesday, April 22, 1998 7:14 AM, Jim Fleming[SMTP:JimFleming@doorstep.unety.net] wrote: @Jim Fleming, @ @Sorry to be slow in responding, I just saw your email (below) of the 20th. @ @Your question is one of IPv6 address architecture and thus is best @discussed on the ipng mail list at: @ Thanks for responding and pointing this in the right direction. If people need more information on how the IPv8 addresses are managed, they might want to look at this list of G:S numbers and review the comments below. http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt In the IPv8 Plan there are 2,048 slots. This is like tracking the Fortune 500. The goal is to locate the "strongest" TLDs in the world and assign them to a slot. The G:S number on the slot determines which part of the IPv8 address space is automatically delegated to the stewards for that TLD. The format of the addresses is G:S.x.x.x.x. To make sure that the IPv4 world is not forgotten, the IPv8 Plan calls for the entire IPv4 address space to be delegated for stewardship purposes to the 2,048 TLD authorities. This is like 2,048 IANAs. As an example... In the IPv8 Plan, the 207.32.X.X IPv4 address space is delegated to the TLD authority with the G:S slot numbered 7:32. This is currently assigned to the .ROOF Top Level Domain. Here are all of the IPv4 blocks that would fall under the stewardship of the .ROOF TLD. This TLD authority would also be responsible for the 7:32.X.X.X.X IPv8 address space which is as large as the current Internet. This should provide enough resources to manage to help keep the .ROOF registries and registrars in business. -------- IPv4 Blocks Delegated to G:S = 7:32 -------------- 7.32.0.0 15.32.0.0 23.32.0.0 31.32.0.0 39.32.0.0 47.32.0.0 55.32.0.0 63.32.0.0 71.32.0.0 79.32.0.0 87.32.0.0 95.32.0.0 103.32.0.0 111.32.0.0 119.32.0.0 127.32.0.0 135.32.0.0 143.32.0.0 151.32.0.0 159.32.0.0 167.32.0.0 175.32.0.0 183.32.0.0 191.32.0.0 199.32.0.0 207.32.0.0 215.32.0.0 223.32.0.0 231.32.0.0 239.32.0.0 247.32.0.0 255.32.0.0 /* * * usage: ipv4list g:s * * Generates a list of IPv4 address blocks given an IPv8 G:S number * * Copyright 1998, Unir Corporation, All Rights Reserved * */ #include <stdio.h> main(argc,argv) int argc; char *argv[]; { int g; int s; int i; int k; int n; if((argv[1][0] >= '0') && (argv[1][0] <= '7')){ g = argv[1][0] - '0'; } else{ exit(-1); } if(argv[1][1] != ':'){ exit(-2); } s = atoi(&argv[1][2]); k = ((g<<24) + (s<<16)) & 0x07ff0000; for(i=0; i<32; i++){ n = (i<<27) + k; printf("%d.%d.%d.%d\n", (n>>24)&0xff, (n>>16)&0xff, (n>>8)&0xff, n&0xff); } } ====== - Jim Fleming Unir Corporation IBC, Tortola, BVI

1 0