From owner-malloc@catarina.usc.edu Mon May 3 11:23:00 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19599 for ; Mon, 3 May 1999 11:23:00 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id HAA27154 for malloc-list; Mon, 3 May 1999 07:41:58 -0700 Received: from zipper.cisco.com (zipper.cisco.com [171.69.63.31]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id HAA27150 for ; Mon, 3 May 1999 07:41:46 -0700 Received: (dmm@localhost) by zipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) id HAA15245; Mon, 3 May 1999 07:39:55 -0700 (PDT) Date: Mon, 3 May 1999 07:39:55 -0700 (PDT) Message-Id: <199905031439.HAA15245@zipper.cisco.com> From: David Meyer To: internet-drafts@ietf.org cc: mboned@network-services.uoregon.edu, malloc@catarina.usc.edu, wijnen@VNET.IBM.COM, randy@psg.com, vern@ee.lbl.gov, sob@harvard.edu, steve.hanna@sun.com, dthaler@MICROSOFT.com, dmm@cisco.com, roll@stupi.se Subject: draft-ietf-mboned-static-allocation-00.txt Sender: owner-malloc@catarina.usc.edu Precedence: bulk Please remove this draft (previously titled draft-ietf-malloc-static-allocation-02.txt) from the MALLOC WG area and add it to the MBONED archive. Thanks, Dave ----- MBONED Working Group David Meyer Internet Draft Cisco Systems Peter Lothberg Sprint Category Experimental draft-ietf-mboned-static-allocation-00.txt May, 1999 Static Allocations in 233/8 1. Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. 2. Abstract This describes an experimental policy for use of the class D address space using 233/8 as the experimental statically assigned subset of the class D address space. This new experimental allocation is in addition to those described on [IANA] (e.g. [RFC2365]). This memo is a product of the Multicast Deployment Working Group (MBONED) in the Operations and Management Area of the Internet Engineering Task Force. Submit comments to or the authors. David Meyer [Page 1] Internet Draft draft-ietf-mboned-static-allocation-00.txt May, 1999 3. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. 4. Problem Statement Multicast addresses have traditionally been allocated by a dynamic mechanism such as SDR [SAP]. However, many current multicast deployment models are not amenable to dynamic allocation. For example, many content aggregators require group addresses which are fixed on a time scale which is not amenable to allocation by a mechanism such as described in [SAP]. Perhaps more seriously, since there isn't general consensus by providers, content aggregators, or application writers as to the allocation mechanism, the Internet is left without a coherent multicast address allocation scheme. The MALLOC working group is looking at a specific strategy for global multicast address allocation [MADCAP, MASC]. This experiment will proceed in parallel. MADCAP may be employed within AS's, if so desired. This document proposes an experimental method of statically allocating multicast addresses with global scope. This experiment will last for a period of one year, but may be extended as described in section 8. 5. Address Space For purposes of the experiment described here, the IANA should allocate 233/8. The remaining 24 bits will be administered in a manner similar to that described in RFC1797: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 233 | 16 bits AS | local bits | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ David Meyer [Page 2] Internet Draft draft-ietf-mboned-static-allocation-00.txt May, 1999 5.1. Example Consider, for example, AS 5662. Written in binary, left padded with 0s, we get 0001011000011110. Mapping the high order octet to the second octet of the address, and the low order octet to the third octet, we get 233.22.30/24. 6. Allocation As mentioned above, the allocation proposed here follows the RFC1797 (case 1) allocation scheme, modified as follows: the high order octet has the value 233, and the next 16 bits are a previously assigned Autonomous System number (AS), as registered by a network registry and listed in the RWhois database system. This allows a single /24 per AS. As was the case with RFC1797, using the AS number in this way allows the experiment to get underway quickly in that it automatically allocates some addresses to each service provider and does not require a registration step. 6.1. Private AS Space The address space mapped to the private AS space (as defined in [RFC1930], is reserved for future allocation. 7. Security Considerations The approach described here may have the effect of reduced exposure to denial of space attacks based on dynamic allocation. Further, since dynamic assignment does not cross domain boundaries, well known intra-domain security techniques can be applied. David Meyer [Page 3] Internet Draft draft-ietf-mboned-static-allocation-00.txt May, 1999 8. IANA Considerations IANA should allocate 233/8 for experimental assignments. This assignment should timeout one year after the assignment is made. The assignment may be renewed at that time. It should be noted that the experiment described here is in the same spirit the experiment described in [RFC1797]. 9. Acknowledgments This idea originated with Peter Lothberg's idea that we use the same allocation (AS based) as described in RFC 1797 in the class D address space. Randy Bush and Mark Handley contributed many insightful comments. 10. References [MADCAP] B. Patel, et. al., "Multicast Address Dynamic Client Allocation Protocol (MADCAP)", draft-ietf-malloc-madcap-04.txt, Feburay, 1999. [MASC] D. Estrin, et. al., "The Multicast Address-Set Claim (MASC) Protocol", draft-ietf-malloc-masc-01.txt, August, 1998. [IANA] www.isi.edu/in-notes/iana/assignments/multicast-addresses [RFC1797] IANA, "Class A Subnet Experiment", RFC 1797, April, 1995. [RFC1930] J. Hawkinson, et. al., "Guidelines for creation, selection, and registration of an Autonomous System (AS)", RFC1930, March, 1996. [RFC2365] David Meyer, "Administratively Scoped IP Multicast", July, 1998. [RFC2374] R. Hinden, et. al., "An IPv6 Aggregatable Global Unicast Address Format", July, 1998. [SAP] Handley, Mark, "SAP: Session Announcement Protocol", draft-ietf-mmusic-sap-00.txt, November, 1996. David Meyer [Page 4] Internet Draft draft-ietf-mboned-static-allocation-00.txt May, 1999 11. Author's Address David Meyer Cisco Systems, Inc. 170 W. Tasman Drive San Jose, CA 95134-1706 United States EMail: dmm@cisco.com Peter Lothberg Sprint VARESA0104 12502 Sunrise Valley Drive Reston VA, 20196 Email: roll@sprint.net David Meyer [Page 5] From owner-malloc@catarina.usc.edu Tue May 4 09:01:19 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29865 for ; Tue, 4 May 1999 09:01:17 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id FAA01868 for malloc-list; Tue, 4 May 1999 05:18:56 -0700 Received: from MAIL2 ([24.232.0.18]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id FAA01853; Tue, 4 May 1999 05:18:30 -0700 Received: from smtp.cvtci.com.ar - 200.16.224.120 by cvtci.com.ar with Microsoft SMTPSVC; Tue, 4 May 1999 09:11:46 -0300 From: "PromoMail"@catarina.usc.edu Date: Tue, 04 May 1999 09:16:30 Subject: Bases de Datos Message-ID: <000f74611120459MAIL2@cvtci.com.ar> Sender: owner-malloc@catarina.usc.edu Precedence: bulk Apparently-To: malloc-list@catarina.usc.edu Bases de Datos Disponemos de Bases de Datos de E-Mail Argentinos con las cuales podrá promocionar sus productos o servicios. Con resultados sorprendentes en cantidad y rapidez!! Bases de Datos: 10000 E-Mails Argentinos $ 70.- 20000 E-Mails Argentinos $ 90.- 25000 E-Mails Argentinos $ 100.- 40000 E-Mails Argentinos $ 140.- 60000 E-Mails Argentinos $ 190.- 73000 E-Mails Argentinos $ 210.- Todas las Bases de Datos vienen en CD-Rom en formato .DBF, .TXT, .XLS y .MDB y .DOC Solicite información a: dito@alean.com.ar o telefónicamente 4952-2420 Si este mensaje no es de su interés, disculpe la molestia. Si nos envía un mail a: dito@alean.com.ar colocando en Subject: BORRAR Su dirección será borrada de nuestras bases de datos. From owner-malloc@catarina.usc.edu Tue May 4 09:28:56 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01563 for ; Tue, 4 May 1999 09:28:54 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id FAA01911 for malloc-list; Tue, 4 May 1999 05:48:06 -0700 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id FAA01907 for ; Tue, 4 May 1999 05:48:01 -0700 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29205; Tue, 4 May 1999 08:47:14 -0400 (EDT) Message-Id: <199905041247.IAA29205@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: malloc@catarina.usc.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-malloc-arch-01.txt Date: Tue, 04 May 1999 08:47:13 -0400 Sender: owner-malloc@catarina.usc.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast-Address Allocation Working Group of the IETF. Title : The Internet Multicast Address Allocation Architecture Author(s) : D. Estrin, M. Handley, D. Thaler Filename : draft-ietf-malloc-arch-01.txt Pages : 11 Date : 03-May-99 This document proposes a multicast address allocation architecture for the Internet. The architecture is three layered, comprising a client->server protocol, an intra- domain protocol and an inter-domain protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-malloc-arch-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-malloc-arch-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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-malloc-arch-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19990503123250.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-malloc-arch-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-malloc-arch-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19990503123250.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-malloc@catarina.usc.edu Thu May 6 15:33:51 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA02347 for ; Thu, 6 May 1999 15:33:51 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id MAA12947 for malloc-list; Thu, 6 May 1999 12:06:38 -0700 Received: from servernt.cscompu.com.ar ([200.16.214.2]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id MAA12942 for ; Thu, 6 May 1999 12:06:22 -0700 Message-Id: <199905061906.MAA12942@catarina.usc.edu> Received: from pc-jm (PC_JM.cscompu.com.ar [10.200.0.88]) by servernt.cscompu.com.ar (Post.Office MTA v3.5.3 release 223 ID# 0-52876U1000L100S0V35) with SMTP id ar for ; Thu, 6 May 1999 16:15:30 -0300 Date: Thu, 06 May 1999 16:01:07 -0300 From: IIBA Subject: Cursos Intensivos de Informática de Sábados y Domingos. Reply-To: capacitacion@iname.com To: malloc@catarina.usc.edu X-Mailer: dbMail v1.3b1 by Mach5 Software. Please report spamming to dbspam@mach5.com. Sender: owner-malloc@catarina.usc.edu Precedence: bulk AT: malloc@catarina.usc.edu NO DEJE PASAR ESTA OPORTUNIDAD DE CAPACITARSE YA! INVIERTA UN FIN DE SEMANA Y GANE. RESERVE YA SU VACANTE CUPOS LIMITADOS OBJETO: Los cursos apuntan a resolver la problemática de las personas que deben capacitarse rapidamente y con el mejor nivel. Se entregará certificado de realización del curso. Práctica intensiva personalizada sobre computadoras (1 PC por alumno, 100% de práctica). GARANTIA DE APRENDIZAJE. CURSOS DISPONIBLES: Windows 95 (2 días - 16 hs.). $ 150,-- Windows 98 - Operación (2 días 16 hs.). $ 150,-- Windows 98 - Comunicaciones e Internet (1 día 8 hs.). $ 90,-- Internet (1 día 8 hs.). $ 90,-- Word 97 - Básico (2 días 16 hs.). $ 150,-- Word 97 - Avanzado (1 día 8 hs.). $ 90,-- Excel 97 - Básico (2 días 16 hs.). $ 150,-- Excel 97 - Avanzado (2 días 16 hs.). $ 150,-- AutoCAD 14 - Dibujo en 2 dimensiones (2 días 16 hs.). $ 150,-- AutoCAD 14 - Dibujo en 3D y Modelado de Sólidos (2 días 16 hs.). $ 150,-- OTROS CURSOS: Ventas Access 95 Access 97 Corel Draw 6.0 Corel Draw 8.0 Excel 95 Introducción al PC Office 95 Office 97 PowerPoint 95 PowerPoint 97 Visual Basic 4.0 Windows NT 4 - Workstation Word 95 Descuentos por más de un curso o a grupos de personas (consultar). Puede consultar los contenidos de los cursos, sus duraciones y costos por e-mail a capacitacion@iname.com FECHAS Y HORARIOS DISPONIBLES: Mayo de 1999: Sábado 08-05 Domingo 09-05 Sábado 15-05 Domingo 16-05 Sábado 23-05 Domingo 24-05 Sábado 30-05 Domingo 31-05 En horarios de 9 a 13 hs. y 15 a 19 hs (consultar por horarios especiales). LUGAR: Los cursos de realizarán en Capital Federal (también se realizan cursos a distancia). RESERVAR VACANTE (Cupos limitados). A los interesados rogamos enviar los datos siguientes y nos pondremos en contacto . NOMBRE Y APELLIDO: EMPRESA y CARGO (Si corresponde): TELEFONO: CURSO(S) DE INTERES: FECHAS DE INTERES: Cordialmente, Lic. Graciela Dálmine Depto. de Capacitación Instituto Informático Buenos Aires capacitacion@iname.com Agradecemos su atención. Si este mensaje no es de su interés rogamos sepa disculpar las molestias ocasionadas y enviar un e-mail a capacitacion@iname.com con la palabra BORRAR en el asunto. From owner-malloc@catarina.usc.edu Fri May 7 19:29:03 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13554 for ; Fri, 7 May 1999 19:29:03 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id QAA18764 for malloc-list; Fri, 7 May 1999 16:03:33 -0700 Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id QAA18760 for ; Fri, 7 May 1999 16:03:27 -0700 Received: by INET-IMC-05 with Internet Mail Service (5.5.2524.0) id ; Fri, 7 May 1999 16:02:56 -0700 Message-ID: <5BF896CAFE8DD111812400805F1991F70A025A20@RED-MSG-08> From: Dave Thaler To: "'Steve Hanna'" , Munil Shah , Baiju Patel Cc: "'malloc@catarina.usc.edu'" Subject: RE: comments/questions on draft-ietf-malloc-madcap-04.txt Date: Fri, 7 May 1999 16:02:51 -0700 X-Mailer: Internet Mail Service (5.5.2524.0) Sender: owner-malloc@catarina.usc.edu Precedence: bulk My understanding is that for well-known scopes, such as global, it ought to be possible for a client to skip the scope enumeration step, and just send a request. My question then, if you agree with the above, is: what's the scope ID for global? Is it the first global address (224.0.1.0)? Or is it 0.0.0.0? Secondly, as Steve pointed out a while ago, the scope end address is required if the client wants to use scope-relative addresses (which is why it's already there in MADCAP). Since the server may be allocating out of a smaller range than the full scope range, I believe the spec should specifically state that the scope range given to the client is not necessarily the scope range the server allocates from (or does it already say this somewhere?) A corrolary is that the Scope ID is not necessarily the first address in the range the server is allocating from. -Dave From owner-malloc@catarina.usc.edu Mon May 10 11:29:53 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07364 for ; Mon, 10 May 1999 11:29:51 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id IAA24694 for malloc-list; Mon, 10 May 1999 08:02:24 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id IAA24690 for ; Mon, 10 May 1999 08:02:19 -0700 Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA26087; Mon, 10 May 1999 08:02:16 -0700 (PDT) Received: from suneast.East.Sun.COM (suneast.East.Sun.COM [129.148.1.27]) by eastmail2.East.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA06944; Mon, 10 May 1999 11:02:11 -0400 (EDT) Received: from bcn.East.Sun.COM (bcn [129.148.75.4]) by suneast.East.Sun.COM (8.9.1b+Sun/8.8.8) with SMTP id LAA17746; Mon, 10 May 1999 11:02:12 -0400 (EDT) Received: from sun.com by bcn.East.Sun.COM (SMI-8.6/SMI-SVR4) id LAA11302; Mon, 10 May 1999 11:02:11 -0400 Message-ID: <3736F448.A860706B@sun.com> Date: Mon, 10 May 1999 10:59:20 -0400 From: Steve Hanna Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Thaler CC: Munil Shah , Baiju Patel , "'malloc@catarina.usc.edu'" Subject: Re: comments/questions on draft-ietf-malloc-madcap-04.txt References: <5BF896CAFE8DD111812400805F1991F70A025A20@RED-MSG-08> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit Dave Thaler wrote: > My understanding is that for well-known scopes, such as global, > it ought to be possible for a client to skip the scope enumeration > step, and just send a request. I agree. If a particular server does not support the indicated scope, the server will not respond to a DISCOVER message. > My question then, if you agree with the above, is: > what's the scope ID for global? Is it the first global > address (224.0.1.0)? Or is it 0.0.0.0? From section 3.5 of draft-ietf-malloc-madcap-04.txt: ... The scope id is the first multicast address in the scope. ... So the scope ID for the global scope is 224.0.1.0. > Secondly, as Steve pointed out a while ago, the scope end address > is required if the client wants to use scope-relative addresses > (which is why it's already there in MADCAP). > > Since the server may be allocating out of a smaller range than > the full scope range, I believe the spec should specifically state > that the scope range given to the client is not necessarily the > scope range the server allocates from (or does it already say this > somewhere?) A corrolary is that the Scope ID is not necessarily > the first address in the range the server is allocating from. Well, the MADCAP spec doesn't really get into the internal mechanics of how the server allocates addresses. The server might have one or more ranges of addresses over which it has complete control. Or it might request addresses as needed from a pool. There might be an operator with a pencil and paper, crossing things off a list. It shouldn't make any difference to the client (although things might be a bit slow in the pencil and paper case). If you think it would be useful to say something about this, I'll see what I can do. -Steve From owner-malloc@catarina.usc.edu Tue May 11 20:45:24 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05628 for ; Tue, 11 May 1999 20:45:23 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id RAA01580 for malloc-list; Tue, 11 May 1999 17:22:40 -0700 Received: from ns.bigbear.net (lai-ca4-68.ix.netcom.com [209.110.247.68]) by catarina.usc.edu (8.6.10/8.6.9) with SMTP id RAA01550; Tue, 11 May 1999 17:22:16 -0700 From: toukol@mindspring.com Message-Id: <199905120022.RAA01550@catarina.usc.edu> Subject: Homeworkers Needed! Date: Tue, 11 May 1999 13:48:52 Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Sender: owner-malloc@catarina.usc.edu Precedence: bulk Dear Future Associate, You Can Work At Home & Set Your Own Hours. Start earning Big Money in a short time NO Newspaper Advertising! Your job will be to stuff and mail envelopes for our company. You will receive $.25 for each and every envelope you stuff and mail out. Just follow our simple instructions and you will be making money as easy as 1… 2… 3 For example stuff and mail 200 envelopes and you will receive $50.00. Stuff and mail 1000 and you will receive $250.00. Stuff and mail 2000 and you will receive $500.00 and more Never before has there been an easier way to make money from home! Our Company's Home Mailing Program is designed for people with little or no experience and provides simple, step by step instructions. There is no prior experience or special skills necessary on your part, Just stuffing envelopes. We need the help of honest and reliable home workers like you. Because we are overloaded with work and have more than our staff can handle. We have now expanded our mailing program and are expecting to reach millions more with our offers throughout the US and Canada. Our system of stuffing and mailing envelopes is very simple and easy to do! You will not be required to buy envelopes or postage stamps. We will gladly furnish all circulars at no cost to you. We assure you that as a participant in our program you will never have to mail anything objective or offensive. There are no quotas to meet, and there no contracts to sign. You can work as much, or as little as you want. Payment for each envelope you send out is Guaranteed! Here is what you will receive when you get your first Package. Inside you will find 100 envelopes, 100 labels and 100 sales letters ready to stuff and mail As soon as you are done with stuffing and mailing these first letters, your payment will arrive shortly, thereafter. All you have to do is to order more free supplies and stuff and mail more envelopes to make more money. Our sales literature which you will be stuffing and mailing will contain information outlining our highly informative manuals that we are advertising nationwide. As a free gift you will receive a special manual valued at $24.95, absolutely free, just for joining our Home Mailers Program. Plus you will get your own special code number, so that we will know how much you are to get paid. And to make re-ordering of more envelopes, that our company supplies very simple for you. We are giving you this free bonus because we want you to be confident in our company and to ensure that we will be doing business with you for a long time. Benefits Of This Job: 1. You do not have to quit your present job, to earn more money at home 2. You can make between $2,500 to $4,500 a month depending on the amount of time you are willing to spend stuffing and mailing envelopes 3. This is a great opportunity for the students, mothers, disabled persons or those who are home bodies. To secure your position and to show us that you are serious about earning extra income at home we require a one-time registration fee of $35.00. This fee covers the cost of your initial start up package, which includes 100 envelopes, 100 labels and 100 sales letters and a manual, your registration fee will be refunded back to you shortly thereafter. Money Back Guarantee! We guarantee that as soon as you stuff and mail your first 300 envelopes You will be paid $75.00 and your registration fee will be refunded. Many of you wonder why it is necessary to pay a deposit to get a job. It is because we are looking for people that seriously want to work from home. * If 3.000 people told us they wanted to start working from home and we sent out 3.000 packages free to every one. And then half of the people decided not to work, this would be a potential loss of more than $60,000 in supply's and shipping that we have sent out to people that don't want to work We have instituted this policy to make sure that you really want to work and at least finish your first package. To Get Started Today Please Enclose Your Registration Fee of $35 Check,Cash Or Money Order and fill out the application below and mail to: AHWA CO Pmb 1928 E. Highland Blvd Ste #F104-902 Phoenix, Az 85016 Name_____________________________________________________ Address___________________________________________________ City____________________________________ State______________ Zip Code________________ Telephone Number(s)_________________________________________ E-mail Address______________________________________________ For all orders, please allow seven (7) days for delivery and up to 10 days. Cash and Money Orders will result in faster shipping of your package. From owner-malloc@catarina.usc.edu Sat May 22 13:33:17 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00208 for ; Sat, 22 May 1999 13:33:17 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id KAA13301 for malloc-list; Sat, 22 May 1999 10:14:50 -0700 Received: from server-2.laufquen.com.ar (ppp669-infovia.infovia.com.ar [209.13.148.161]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id KAA13297; Sat, 22 May 1999 10:14:36 -0700 Message-Id: <199905221714.KAA13297@catarina.usc.edu> Received: from jorge (209.13.148.233 [209.13.148.233]) by server-2.laufquen.com.ar with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id LMFQY29W; Sat, 22 May 1999 14:10:43 -0300 X-Mailer: Aureate Group Mail Free Edition From: Camas Rebatibles To: solucionar problemas de espacio Date: Sat, 22 May 1999 14:16:02 -0300 Subject: La solución perfecta para ganar espacio Reply-To: info@camasrebatibles.com.ar Organization: Camas MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit Desde hace más de 20 años estamos en la industria de las CAMAS REBATIBLES y sus muebles asociados. Conocemos el valor del espacio. Usted sabe, el mayor obstáculo para usar un ambiente para cualquier otra cosa, como una oficina, o para hacer ejercicios, o para que sus hijos jueguen, o para recibir amigos, o simplemente para sentirse cómodo, es la CAMA. No importa si es de una o dos plazas, cualquier cama domina el ambiente y limita la funcionalidad y la decoración. Podrá obtener mayor información en nuestro sitio en Internet www.camasrebatibles.com.ar Si este mensaje no es de su interes, disculpe la molestia. Si nos envía un mail a: Info@camasrebatibles.com.ar colocando en Subject: BORRAR Su dirección será borrada de nuestra base de datos CAMAS REBATIBLES S.R.L. ---------------------------------------------------------------------- This Message sent with Aureate Group Mail Free Edition http://groupmail.aureate.com From owner-malloc@catarina.usc.edu Tue May 25 10:32:05 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17539 for ; Tue, 25 May 1999 10:32:05 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id HAA21289 for malloc-list; Tue, 25 May 1999 07:01:54 -0700 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id HAA21285 for ; Tue, 25 May 1999 07:01:48 -0700 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15763; Tue, 25 May 1999 10:01:15 -0400 (EDT) Message-Id: <199905251401.KAA15763@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: malloc@catarina.usc.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-malloc-madcap-05.txt Date: Tue, 25 May 1999 10:01:14 -0400 Sender: owner-malloc@catarina.usc.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multicast-Address Allocation Working Group of the IETF. Title : Multicast Address Dynamic Client Allocation Protocol (MADCAP) Author(s) : S. Hanna, B. Patel, M. Shah Filename : draft-ietf-malloc-madcap-05.txt Pages : 48 Date : 24-May-99 This document defines a protocol, Multicast Address Dynamic Client Allocation Protocol (MADCAP), that allows hosts to request multicast addresses from multicast address allocation servers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-malloc-madcap-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-malloc-madcap-05.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-malloc-madcap-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19990524125720.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-malloc-madcap-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-malloc-madcap-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19990524125720.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-malloc@catarina.usc.edu Tue May 25 11:55:17 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22402 for ; Tue, 25 May 1999 11:55:16 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id HAA21436 for malloc-list; Tue, 25 May 1999 07:40:25 -0700 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by catarina.usc.edu (8.6.10/8.6.9) with SMTP id HAA21428 for ; Tue, 25 May 1999 07:40:11 -0700 Received: from couch.dnrc.bell-labs.com ([135.180.160.30]) by dirty; Tue May 25 10:39:45 EDT 1999 Received: from dnrc.bell-labs.com (jdrosen.lra.lucent.com [135.17.250.118]) by couch.dnrc.bell-labs.com (8.8.8/8.8.8) with ESMTP id KAA18846 for ; Tue, 25 May 1999 10:39:44 -0400 (EDT) Message-ID: <374AB649.EE0FB6F@dnrc.bell-labs.com> Date: Tue, 25 May 1999 10:40:09 -0400 From: Jonathan Rosenberg Organization: Bell Laboratories X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: malloc@catarina.usc.edu Subject: Questions on AAP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit members of malloc, I apologize if these questions have been answered on the lists, or are discussed in the latest AAP draft (-01, dated Aug 1998) and I just missed them. Any answers would be most appreciated: 1. If a MAAS pre-allocates an address, what is the start and end times it would put in the ACLM/AIU? It won't know these until the madcap request arrives, which is after the ACLM has been sent. 2. Which MASC routers send an ASRP? If just one, how is it determined which one? If all, it seems possible (likely even) that each MAAS might report a different number of addresses as in use for each set advertised by the MASC router. In this case, which should the MASC router pay attention to? 3. It seems like the MASC router could use the AIU messages it sees from MAAS to construct the same information sent in the ASRP. In that case, the ASRP would not be needed. Is its function mainly to relieve the MASC router of this burden? Thanks in advance, Jonathan R. -- Jonathan D. Rosenberg Lucent Technologies Member of Technical Staff 101 Crawfords Corner Rd. High Speed Networks Research Holmdel, NJ 07733 FAX: (732) 834-5379 Rm. 4C-526 EMAIL: jdrosen@bell-labs.com URL: http://www.cs.columbia.edu/~jdrosen From owner-malloc@catarina.usc.edu Tue May 25 12:27:05 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA24026 for ; Tue, 25 May 1999 12:27:04 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id IAA21773 for malloc-list; Tue, 25 May 1999 08:48:28 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id IAA21769 for ; Tue, 25 May 1999 08:48:23 -0700 Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA27549 for ; Tue, 25 May 1999 08:48:21 -0700 (PDT) Received: from suneast.East.Sun.COM (suneast.East.Sun.COM [129.148.1.27]) by eastmail2.East.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA01629 for ; Tue, 25 May 1999 11:48:18 -0400 (EDT) Received: from bcn.East.Sun.COM (bcn [129.148.75.4]) by suneast.East.Sun.COM (8.9.1b+Sun/8.8.8) with SMTP id LAA08555 for ; Tue, 25 May 1999 11:48:18 -0400 (EDT) Received: from sun.com by bcn.East.Sun.COM (SMI-8.6/SMI-SVR4) id LAA09196; Tue, 25 May 1999 11:48:13 -0400 Message-ID: <374AC584.6117531@sun.com> Date: Tue, 25 May 1999 11:45:08 -0400 From: Steve Hanna Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: malloc Subject: New MADCAP draft -05 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit As you have seen, a new version of the MADCAP spec has been posted at http://www.ietf.org/internet-drafts/draft-ietf-malloc-madcap-05.txt This version reflects the outcome of discussions with our Area Directors and others. A list of significant changes is included below. Many minor changes were also made, such as fixing typographical errors. Please review these changes and send email to the malloc list or the authors if you have any concerns. Thanks, Steve Hanna --------------------- * Renamed Client Identifier to Lease Identifier. * Changed INFORM's code to 8 throughout the document. It used to be 0 in some places and 8 in others. * Changed SHOULD to MUST and MAY to SHOULD in several places to improve probability that conformant implementations will interoperate successfully. * In section 2.2.8, changed text to say that Minimum Lease Time and Maximum Start Time MAY be included in a RENEW message. Also mentioned that if Start or Max Start is included, Current Time MUST be. Also explicitly described defaults if options are missing. These defaults are different than what was implied (but not explicitly stated) before. For instance, Lease Time defaults to max available instead of whatever's remaining in the current lease. * INFORM messages now MUST include an Option Request List option. Before, this was optional. * In Table 5 (Options allowed in MADCAP messages), ACK in response to RELEASE MUST NOT include Current Time. ACK in response to INFORM still MAY include Current Time, since the client may have requested Current Time using the Option Request List. * Described risks of making it easy to guess a Lease Identifier. Suggested using a cryptographically random number generator. * Added new Error option. Only allowed in NAK. See section 3.17 for details. * Servers SHOULD NAK errors unless this might cause a NAK loop. See section 2.6 for details. * All constants are now listed in a new Appendix B. All constants now have RECOMMENDED values that should work nicely together. * Added more discussion of clock skew. There are separate constants for [CLOCK-SKEW-ALLOWANCE] and [EXTRA-ALLOCATION-TIME] now. These MUST be configurable. * [RESPONSE-CACHE-INTERVAL] MUST be no more than 5 minutes now. This allows the client to safely reuse an xid, msgtype, Lease ID combination after 10 minutes. * Mention server doesn't need to cache a packet if it ignores it. * Recommended retransmission algorithm is RECOMMENDED now, not just an example. Also, reduced the number of retransmissions to three. * Added a RECOMMENDED technique for choosing xids. Start with a random number when you boot and increment to reduce chances of collision. * Added an overview section at the beginning and a section with definitions of terms. * Removed the requirement that a multicast REQUEST MUST have the same xid as the multicast DISCOVER that it is following up on. * When using the Feature List option, servers now use the required list to indicate which features were implemented in processing this message. The supported list indicates which features the server supports (as before). From owner-malloc@catarina.usc.edu Tue May 25 22:44:39 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04320 for ; Tue, 25 May 1999 22:44:39 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id TAA24333 for malloc-list; Tue, 25 May 1999 19:25:47 -0700 Received: from hugo.usc.edu (hugo.usc.edu [128.125.51.40]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id TAA24325; Tue, 25 May 1999 19:25:42 -0700 Received: from hugo (localhost [127.0.0.1]) by hugo.usc.edu (8.8.5/8.6.9) with ESMTP id TAA07931; Tue, 25 May 1999 19:25:41 -0700 (PDT) Message-Id: <199905260225.TAA07931@hugo.usc.edu> To: Jonathan Rosenberg cc: malloc@catarina.usc.edu Subject: Re: Questions on AAP In-reply-to: Your message of "Tue, 25 May 1999 10:40:09 EDT." <374AB649.EE0FB6F@dnrc.bell-labs.com> Date: Tue, 25 May 1999 19:25:41 -0700 From: Pavlin Ivanov Radoslavov Sender: owner-malloc@catarina.usc.edu Precedence: bulk > 1. If a MAAS pre-allocates an address, what is the start and end times > it would put in the ACLM/AIU? It won't know these until the madcap > request arrives, which is after the ACLM has been sent. The start time will by typically the current time. Using "start time" = now + something translates into "address reservation". malloc does not target explicitly "address reservation", because it makes things more complicated. At least, in MASC there is "timestamp" and "lifetime", so all "address reservations" requests by MADCAP/AAP will translate into "want to use immediately" at the MASC level. The end time will be based on whatever information AAP has: addresses usage in the past, explicit configuration, or just some default "lifetime". > 2. Which MASC routers send an ASRP? If just one, how is it determined ~~~~ I believe this has to be MAAS, because ASRP is sent by MAAS to MASC. > which one? If all, it seems possible (likely even) that each MAAS might > report a different number of addresses as in use for each set advertised > by the MASC router. In this case, which should the MASC router pay > attention to? Any (or all) MAAS can send ASRP messages. MASC doesn't really care who is the originator, because ASRP are used by MASC only to monitor total address usage by the domain. All MASC servers will look only in the address range and expiration time among all received ASRP messages. > 3. It seems like the MASC router could use the AIU messages it sees from > MAAS to construct the same information sent in the ASRP. In that case, Right. I believe the primary reason to have ASRP is because the information it carries is aggregated and is the only information MASC needs. Mark? Pavlin > the ASRP would not be needed. Is its function mainly to relieve the MASC > router of this burden? > > Thanks in advance, > Jonathan R. > -- > Jonathan D. Rosenberg Lucent Technologies > Member of Technical Staff 101 Crawfords Corner Rd. > High Speed Networks Research Holmdel, NJ 07733 > FAX: (732) 834-5379 Rm. 4C-526 > EMAIL: jdrosen@bell-labs.com > URL: http://www.cs.columbia.edu/~jdrosen From owner-malloc@catarina.usc.edu Wed May 26 07:26:02 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20906 for ; Wed, 26 May 1999 07:26:02 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id EAA25636 for malloc-list; Wed, 26 May 1999 04:01:17 -0700 Received: from mercurio.datamarkets.com.ar ([200.42.0.92]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id EAA25611; Wed, 26 May 1999 04:00:53 -0700 From: tecnosi@datamarkets.com.ar Received: from smtp.datamarkets.com.ar (host016100.ciudad.com.ar [200.42.16.100]) by mercurio.datamarkets.com.ar (8.9.3/8.9.3) with SMTP id HAA09407; Wed, 26 May 1999 07:56:47 -0300 Message-Id: <199905261056.HAA09407@mercurio.datamarkets.com.ar> Date: Wed, 26 May 1999 07:58:45 Subject: CURSOS DE INGLES Sender: owner-malloc@catarina.usc.edu Precedence: bulk Apparently-To: malloc-list@catarina.usc.edu INVIERTA EN CAPACITACION O PAGUE EL COSTO DE LA IGNORANCIA SI NO AHORA, ¿CUANDO? ¿Por que elegirnos para la Capacitación en Inglés? 1. FLEXIBILIDAD: Ajustamos el contenido de los cursos a las Necesidades propias de la Empresa y de su gente, siendo el principal objetivo la Integración del Idioma con la actividad de cada participante. 2. PROFESIONALISMO: Nuestro Equipo Docente esta integrado por Profesores con Título Nacional y Nativos, con amplia Experiencia en Capacitación Empresaria. 3. RESULTADOS: Realizamos Evaluaciones de Nivel antes de comenzar el curso, para determinar la distribución de los alumnos en grupos homogéneos conforme su nivel de idioma. Realizamos Evaluaciones y un Informe Personal Trimestral, lo cual le permite medir los Resultados de la Capacitación. 4. CONVENIENCIA: Dictamos los cursos en su Empresa, en forma individual o grupal, y en el Horario de su Conveniencia. Aconsejamos una frecuencia mínima de 2 clases semanales de una hora y media. 5. ARANCELES: El arancel por hora y por grupo, se calcula según la cantidad de integrantes del mismo, siendo de $ 25.- para un participante, y un adicional de $ 5.- por cada participante que se integre al mismo grupo. Participantes por grupo: 1 2 3 4 Arancel por hora y por grupo: $25 $30 $35 $40 Los precios no incluyen IVA. ESPERAMOS SU LLAMADO AL 15-4975-0797 ENGLISH SKILLS Si este mensaje no es de su interés, disculpe la molestia. From owner-malloc@catarina.usc.edu Wed May 26 20:16:01 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA06432 for ; Wed, 26 May 1999 20:16:00 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id NAA01149 for malloc-list; Wed, 26 May 1999 13:26:33 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id NAA01145 for ; Wed, 26 May 1999 13:26:22 -0700 Received: from eastmail2.East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA07120 for ; Wed, 26 May 1999 13:26:24 -0700 (PDT) Received: from suneast.East.Sun.COM (suneast.East.Sun.COM [129.148.1.27]) by eastmail2.East.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA16498 for ; Wed, 26 May 1999 16:26:21 -0400 (EDT) Received: from bcn.East.Sun.COM (bcn [129.148.75.4]) by suneast.East.Sun.COM (8.9.1b+Sun/8.8.8) with SMTP id QAA02520 for ; Wed, 26 May 1999 16:26:22 -0400 (EDT) Received: from sun.com by bcn.East.Sun.COM (SMI-8.6/SMI-SVR4) id QAA15682; Wed, 26 May 1999 16:26:18 -0400 Message-ID: <374C5830.93215AC4@sun.com> Date: Wed, 26 May 1999 16:23:12 -0400 From: Steve Hanna Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: malloc Subject: WG last call for MADCAP -05 draft Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit This is a Working Group last call for comments on the latest MADCAP specification: draft-ietf-malloc-madcap-05.txt. A previous version of this document went through Working Group Last Call and IETF Last Call. Since then, the document has been revised in response to input from several Area Directors. Since significant changes were made in this draft, we have decided to send the document back for another Working Group Last Call. Please send any comments on the specification to this mailing list or to the document's authors on or before June 2. Once working group consensus has been achieved, the specification will be forwarded to the IESG for IETF Last Call and subsequent publication as a Proposed Standard. Thanks, Steve Hanna From owner-malloc@catarina.usc.edu Mon May 31 09:27:40 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04478 for ; Mon, 31 May 1999 09:27:40 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id FAA13873 for malloc-list; Mon, 31 May 1999 05:58:11 -0700 Received: from charybdis.rus.uni-stuttgart.de (root@charybdis.rus.uni-stuttgart.de [129.69.1.58]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id FAA13869 for ; Mon, 31 May 1999 05:57:59 -0700 Received: from artemis.rus.uni-stuttgart.de (artemis.rus.uni-stuttgart.de [129.69.1.28]) by charybdis.rus.uni-stuttgart.de (8.8.8/8.8.8) with ESMTP id OAA27103 for ; Mon, 31 May 1999 14:57:31 +0200 (MET DST) env-from (Robert.Stoy@RUS.Uni-Stuttgart.DE) Received: from kssun1.rus.uni-stuttgart.de (kssun1.rus.uni-stuttgart.de [129.69.30.20]) by artemis.rus.uni-stuttgart.de (8.8.8/8.8.8) with ESMTP id OAA05703 for ; Mon, 31 May 1999 14:57:30 +0200 (MET DST) env-from (stoy@kssun1.rus.uni-stuttgart.de) Received: (from stoy@localhost) by kssun1.rus.uni-stuttgart.de (8.8.8+Sun/8.8.8) id OAA09249 for malloc@catarina.usc.edu; Mon, 31 May 1999 14:57:27 +0200 (MET DST) From: "Robert Stoy" Message-Id: <990531145726.ZM9247@kssun1.rus.uni-stuttgart.de> Date: Mon, 31 May 1999 14:57:26 +0200 X-Mailer: Z-Mail (4.0.1 13Jan97) To: malloc@catarina.usc.edu Subject: MASC/BGMP implementation ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-malloc@catarina.usc.edu Precedence: bulk Dear all, I'm quite new on this list, maybe I have missed some information that someone can provide ? My question is with regard to an implementation of the MASC/BGMP architecture. Is there a time schedule of an implementation, or already some components' implementation in process or available (maybe a beta release) ? Best Regards Robert Stoy -- __________________________________________________________________________ Robert Stoy Allmandring 30 PKB D-70550 Stuttgart Computing Center 'RUS' Germany University of Stuttgart Phone ++49 (0) 711 685 5859 Fax ++49 (0) 711 6787626 http://www-ks.rus.uni-stuttgart.de/PKB E-mail stoy@rus.uni-stuttgart.de __________________________________________________________________________ From owner-malloc@catarina.usc.edu Mon May 31 14:15:28 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05851 for ; Mon, 31 May 1999 14:15:27 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id KAA14147 for malloc-list; Mon, 31 May 1999 10:31:08 -0700 Received: from kit.isi.edu (kit.isi.edu [128.9.160.207]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id KAA14143 for ; Mon, 31 May 1999 10:31:03 -0700 Received: (from eddy@localhost) by kit.isi.edu (8.9.2/8.8.7) id KAA00240; Mon, 31 May 1999 10:29:52 -0700 (PDT) (envelope-from eddy) From: Rusty Eddy Message-Id: <199905311729.KAA00240@kit.isi.edu> Subject: Re: MASC/BGMP implementation ? In-Reply-To: <990531145726.ZM9247@kssun1.rus.uni-stuttgart.de> from Robert Stoy at "May 31, 1999 2:57:26 pm" To: Robert.Stoy@rus.uni-stuttgart.de (Robert Stoy) Date: Mon, 31 May 1999 10:29:52 -0700 (PDT) Cc: malloc@catarina.usc.edu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit > Dear all, > > My question is with regard to an implementation of the MASC/BGMP > architecture. Is there a time schedule of an implementation, or > already some components' implementation in process or available > (maybe a beta release) ? > there is a alpha version of bgmp in gated-5. it will be included as part of the snapshot in a couple weeks i believe. see www.gated.org for more info. - rusty From owner-malloc@catarina.usc.edu Mon May 31 14:32:58 1999 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05931 for ; Mon, 31 May 1999 14:32:58 -0400 (EDT) Received: (from majordomo@localhost) by catarina.usc.edu (8.6.10/8.6.9) id KAA14171 for malloc-list; Mon, 31 May 1999 10:59:50 -0700 Received: from hugo.usc.edu (hugo.usc.edu [128.125.51.40]) by catarina.usc.edu (8.6.10/8.6.9) with ESMTP id KAA14167; Mon, 31 May 1999 10:59:46 -0700 Received: from hugo (localhost [127.0.0.1]) by hugo.usc.edu (8.8.5/8.6.9) with ESMTP id KAA20396; Mon, 31 May 1999 10:59:45 -0700 (PDT) Message-Id: <199905311759.KAA20396@hugo.usc.edu> To: Rusty Eddy cc: Robert.Stoy@rus.uni-stuttgart.de (Robert Stoy), malloc@catarina.usc.edu Subject: Re: MASC/BGMP implementation ? In-reply-to: Your message of "Mon, 31 May 1999 10:29:52 PDT." <199905311729.KAA00240@kit.isi.edu> Date: Mon, 31 May 1999 10:59:45 -0700 From: Pavlin Ivanov Radoslavov Sender: owner-malloc@catarina.usc.edu Precedence: bulk > > Dear all, > > > > My question is with regard to an implementation of the MASC/BGMP > > architecture. Is there a time schedule of an implementation, or > > already some components' implementation in process or available > > (maybe a beta release) ? > > > there is a alpha version of bgmp in gated-5. it will be included > as part of the snapshot in a couple weeks i believe. see > www.gated.org for more info. Alpha version of stand-alone MASC is in process of testing and is planned for release within approximately 2 weeks. Pavlin