From owner-malloc@catarina.usc.edu Fri Mar 10 22:24:51 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20484 for ; Fri, 10 Mar 2000 22:24:50 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id MAA39299 for malloc-list; Wed, 8 Mar 2000 12:08:21 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: from dthaler.microsoft.com ([131.107.152.20]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id MAA39294 for ; Wed, 8 Mar 2000 12:08:18 -0800 (PST) Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) id NAA00485 for malloc@catarina.usc.edu; Wed, 8 Mar 2000 13:43:15 -0800 (PST) (envelope-from dthaler) From: Dave Thaler Message-Id: <200003082143.NAA00485@dthaler.microsoft.com> Subject: malloc agenda items? To: malloc@catarina.usc.edu Date: Wed, 8 Mar 2000 13:43:15 -0800 (PST) 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 Please submit requests for agenda items for the Malloc WG meeting in Adelaide. Preferably include how much time you want, and a pointer to a draft. Thanks, -Dave From owner-malloc@catarina.usc.edu Fri Mar 10 22:30:22 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22266 for ; Fri, 10 Mar 2000 22:30:21 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id IAA43650 for malloc-list; Thu, 9 Mar 2000 08:57:14 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id IAA43645 for ; Thu, 9 Mar 2000 08:57:13 -0800 (PST) Received: from eastmail1.East.Sun.COM ([129.148.1.240]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00910 for ; Thu, 9 Mar 2000 09:56:48 -0700 (MST) Received: from sunlabs.East.Sun.COM (sunlabs.East.Sun.COM [129.148.75.250]) by eastmail1.East.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA25919 for ; Thu, 9 Mar 2000 11:56:47 -0500 (EST) Received: from sun.com (dhcp75-155 [129.148.75.155]) by sunlabs.East.Sun.COM (8.9.3+Sun/8.9.1) with ESMTP id LAA26064 for ; Thu, 9 Mar 2000 11:56:44 -0500 (EST) Message-ID: <38C7D734.9DCE4573@sun.com> Date: Thu, 09 Mar 2000 11:54:12 -0500 From: Steve Hanna Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: malloc Subject: Posted new AAP draft (draft-ietf-malloc-aap-03.txt) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit I have submitted a new AAP draft to the internet-drafts editor and posted a copy on the malloc web site at: http://www.aciri.org/malloc/draft-ietf-malloc-aap-03.txt This version reflects all comments I have received on the document, including the following changes: * Noted reserved port number: 2878. * Removed Appendix D (Unresolved Issues). * Added scaling analysis (section 6). * Added recommendation that hosts use MADCAP instead of AAP if a MADCAP server is available. * Changed last step in address selection preference algorithm (section 3.2.7) to choose randomly. This should reduce the likelihood of collisions. * Added discussion of allocation conflicts (section 3.2.3). * Added examples (Appendix A). I will request a Working Group last call for this document as soon as it hits the Internet Drafts archive. -Steve From owner-malloc@catarina.usc.edu Fri Mar 10 22:36:33 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25559 for ; Fri, 10 Mar 2000 22:36:31 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id HAA26113 for malloc-list; Mon, 6 Mar 2000 07:56:31 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: (from pavlin@localhost) by catarina.usc.edu (8.9.3/8.9.3) id HAA26107 for malloc@catarina.usc.edu; Mon, 6 Mar 2000 07:56:30 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id DAA25534 for ; Mon, 6 Mar 2000 03:58:11 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02536; Mon, 6 Mar 2000 06:57:50 -0500 (EST) Message-Id: <200003061157.GAA02536@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-malloc-mib-02.txt Date: Mon, 06 Mar 2000 06:57:49 -0500 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 Allocation MIB Author(s) : D. Thaler Filename : draft-ietf-malloc-malloc-mib-02.txt Pages : 41 Date : 03-Mar-00 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multicast address allocation. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-malloc-malloc-mib-02.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-malloc-mib-02.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-malloc-mib-02.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: <20000303144435.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-malloc-malloc-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-malloc-malloc-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000303144435.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-malloc@catarina.usc.edu Fri Mar 10 22:40:33 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26880 for ; Fri, 10 Mar 2000 22:40:31 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id KAA49573 for malloc-list; Fri, 10 Mar 2000 10:36:11 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: (from pavlin@localhost) by catarina.usc.edu (8.9.3/8.9.3) id KAA49567 for malloc@catarina.usc.edu; Fri, 10 Mar 2000 10:36:06 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id DAA48035 for ; Fri, 10 Mar 2000 03:30:27 -0800 (PST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29098; Fri, 10 Mar 2000 06:29:32 -0500 (EST) Message-Id: <200003101129.GAA29098@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-aap-03.txt Date: Fri, 10 Mar 2000 06:29:31 -0500 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 Allocation Protocol (AAP) Author(s) : M. Handley, S. Hanna Filename : draft-ietf-malloc-aap-03.txt Pages : 43 Date : 09-Mar-00 The document defines a Multicast Address Allocation Protocol (AAP) that forms a part of the Internet Multicast Address Allocation Architecture being defined by the IETF Multicast Address Allocation Working Group. AAP addresses the specific issue of coordination among Multicast Address Allocation Servers within a domain. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-malloc-aap-03.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-aap-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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-malloc-aap-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. --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: <20000309140257.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-malloc-aap-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-malloc-aap-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000309140257.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-malloc@catarina.usc.edu Fri Mar 10 23:34:14 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14451 for ; Fri, 10 Mar 2000 23:34:13 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id NAA50485 for malloc-list; Fri, 10 Mar 2000 13:03:13 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: from dthaler.microsoft.com ([131.107.152.20]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id NAA50480 for ; Fri, 10 Mar 2000 13:03:10 -0800 (PST) Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) id OAA04564; Fri, 10 Mar 2000 14:38:06 -0800 (PST) (envelope-from dthaler) From: Dave Thaler Message-Id: <200003102238.OAA04564@dthaler.microsoft.com> Subject: WG last call on AAP To: malloc@catarina.usc.edu Date: Fri, 10 Mar 2000 14:38:06 -0800 (PST) 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 This message starts a WG last call on the AAP spec: draft-ietf-malloc-aap-03.txt which is available in the usual I-D repositories, or from the MALLOC web site at http://www.aciri.org/malloc/ This last call will expire March 31 (after the Adelaide IETF meeting). Thanks, Dave Thaler MALLOC WG Co-chair From owner-malloc@catarina.usc.edu Sat Mar 11 02:05:02 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12024 for ; Sat, 11 Mar 2000 02:05:02 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id XAA78476 for malloc-list; Fri, 10 Mar 2000 23:01:34 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: (from pavlin@localhost) by catarina.usc.edu (8.9.3/8.9.3) id XAA78470 for malloc@catarina.usc.edu; Fri, 10 Mar 2000 23:01:33 -0800 (PST) Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id WAA78410 for ; Fri, 10 Mar 2000 22:54:17 -0800 (PST) Received: from seu.edu.cn (seic3.seu.edu.cn [202.119.24.13]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id WAA28042 for ; Fri, 10 Mar 2000 22:52:44 -0800 (PST) Received: from seu.edu.cn ([202.119.11.195]) by seu.edu.cn (8.9.3/8.9.3) with ESMTP id OAA12097 for ; Sat, 11 Mar 2000 14:33:57 +0800 (CST) Message-ID: <38C9E887.F5DE54F@seu.edu.cn> Date: Sat, 11 Mar 2000 14:32:40 +0800 From: Zhai Mingyu X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: malloc@catarina.usc.edu Subject: Multicast address Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-malloc@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit Hi, about Multicast address allocation I have some questions,i.e., whether the following two situations can appear or not. 1)In the same TTL scope,there are two sessions which all use the same multicast address( for example 233.7.117.2) ,but they use different Transport protocols, for example,one using UDP and another using XTP. 2)Likely there are two sessions which all use the same multicast address( for example 233.7.117.2) ,and same Transport protocol, for example using UDP.But these two session use different Destination Port,for example one using port number 22222 and another using 33333. I think these two situations can exist in Multicast address allocaton, is it right? From owner-malloc@catarina.usc.edu Sat Mar 11 02:29:47 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21640 for ; Sat, 11 Mar 2000 02:29:47 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id XAA78861 for malloc-list; Fri, 10 Mar 2000 23:23:58 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f Received: from rumi.usc.edu (rumi.usc.edu [128.125.51.41]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id XAA78677; Fri, 10 Mar 2000 23:19:20 -0800 (PST) Received: from rumi (localhost [127.0.0.1]) by rumi.usc.edu (8.9.3/8.9.3) with ESMTP id XAA25410; Fri, 10 Mar 2000 23:19:32 -0800 (PST) Message-Id: <200003110719.XAA25410@rumi.usc.edu> To: Zhai Mingyu cc: malloc@catarina.usc.edu Subject: Re: Multicast address In-reply-to: Your message of "Sat, 11 Mar 2000 14:32:40 +0800." <38C9E887.F5DE54F@seu.edu.cn> Date: Fri, 10 Mar 2000 23:19:32 -0800 From: Pavlin Ivanov Radoslavov Sender: owner-malloc@catarina.usc.edu Precedence: bulk > about Multicast address allocation I have some questions,i.e., whether > > the following two situations can appear or not. > 1)In the same TTL scope,there are two sessions which all use the same > multicast > address( for example 233.7.117.2) ,but they use different Transport > protocols, > for example,one using UDP and another using XTP. > 2)Likely there are two sessions which all use the same multicast > address( for example 233.7.117.2) ,and same Transport protocol, > for example using UDP.But these two session use different Destination > Port,for example one using port number 22222 and another using 33333. > > I think these two situations can exist in Multicast address allocaton, > is it right? Theoretically, yes, same multicast address with different transport protocol (or different port number) would mean different session. However, at the network level, IP multicast uses only the multicast address to make difference between the sessions/groups. E.g. the multicast routers uses only the multicast address to route the packets to the receivers. Otherwise, if you allow the Transport protocol and/or the port number to be a part of the session ID, the routers would need to lookup the protocol number and the port number of each packet as well. malloc tries to solve the address allocation problem only at the IP level by handling unique addresses to each session, and therefore it doesn't consider the protocol and the port numbers. Pavlin