From owner-malloc@catarina.usc.edu  Tue Jun  6 17:50:23 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 RAA19678
	for <malloc-archive@odin.ietf.org>; Tue, 6 Jun 2000 17:50:22 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id OAA19996
	for malloc-list; Tue, 6 Jun 2000 14:39:55 -0700 (PDT)
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 OAA19991
	for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 14:39:51 -0700 (PDT)
Received: (from pavlin@localhost)
	by rumi.usc.edu (8.9.3/8.9.3) id OAA38045
	for malloc@catarina.usc.edu; Tue, 6 Jun 2000 14:39:51 -0700 (PDT)
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id JAA17406
	for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 09:11:38 -0700 (PDT)
Received: from p-biset.issy.cnet.fr (p-biset.issy.cnet.fr [139.100.0.33])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id JAA07913 for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 09:11:37 -0700 (PDT)
Received: by p-biset.issy.cnet.fr with Internet Mail Service (5.5.2448.0)
	id <MD0PNP6Y>; Tue, 6 Jun 2000 18:09:43 +0200
Message-ID: <B932E841DDE0D0119D2300609759036C0122C62B@l-mhs4.lannion.cnet.fr>
From: SENECLAUZE Gregoire FTRD/DAC/LAN
	 <gregoire.seneclauze@rd.francetelecom.fr>
To: "'malloc@catarina.usc.edu'" <malloc@catarina.usc.edu>
Subject: Relationship with ICANN/IANA
Date: Tue, 6 Jun 2000 18:08:51 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id JAA17407
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi, 

Where could I find informations regarding attribution of multicast addresses
(I mean blocks that should be affected to an autonomous systems for
example..)

ICANN is now responsible for this task I think, but I did not find anything
regarding multicast on ICANN's website (www.icann.org)

I thought some people in this working group may have some informations
regarding this.

Thank you for your help

Grégoire.

-------------------------------------------------------------------
Grégoire Sénéclauze
France Telecom CNET   DAC-NTR
2, Avenue Pierre Marzin, 22307 Lannion Cedex
+33 (0)2 96 05 30 73  (tel)
+33 (0)2 96 05 18 52  (fax)
gregoire.seneclauze@francetelecom.fr
-------------------------------------------------------------------


From owner-malloc@catarina.usc.edu  Tue Jun  6 18:37:17 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 SAA20299
	for <malloc-archive@odin.ietf.org>; Tue, 6 Jun 2000 18:37:16 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id PAA20314
	for malloc-list; Tue, 6 Jun 2000 15:24:46 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id PAA20308
	for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 15:24:45 -0700 (PDT)
Received: from porto.abacom.com (porto.abacom.com [207.253.166.29])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id PAA00299 for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 15:24:44 -0700 (PDT)
Received: (qmail 13604 invoked by uid 7791); 6 Jun 2000 22:22:03 -0000
Received: from paris11-nas2-20-105.dial.proxad.net (HELO cybercable.fr) ([213.228.20.105]) (envelope-sender <mom@cybercable.fr>)
          by porto.abacom.com (qmail-ldap-1.03) with SMTP
          for <gregoire.seneclauze@rd.francetelecom.fr>; 6 Jun 2000 22:22:03 -0000
Message-ID: <393D7985.C6BA8894@cybercable.fr>
Date: Wed, 07 Jun 2000 00:21:58 +0200
From: Marc-Olivier =?iso-8859-1?Q?M=E9hu?= <mom@cybercable.fr>
Reply-To: mom@cybercable.fr
X-Mailer: Mozilla 4.72 (Macintosh; I; PPC)
X-Accept-Language: fr,pdf
MIME-Version: 1.0
To: SENECLAUZE Gregoire FTRD/DAC/LAN 
 <gregoire.seneclauze@rd.francetelecom.fr>
CC: "'malloc@catarina.usc.edu'" <malloc@catarina.usc.edu>
Subject: Re: Relationship with ICANN/IANA
References: <B932E841DDE0D0119D2300609759036C0122C62B@l-mhs4.lannion.cnet.fr>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit

SENECLAUZE Gregoire FTRD/DAC/LAN wrote:
> 
> Hi,
> 
> Where could I find informations regarding attribution of multicast addresses
> (I mean blocks that should be affected to an autonomous systems for
> example..)

The static multicast allocations are listed at 

http://www.isi.edu/in-notes/iana/assignments/multicast-addresses

Otherwise, there are few ASes using GLOP allocation (Experimental
RFC2770) for 
allocation in order to get a /24 of globally unique multicast address
space. 

> ICANN is now responsible for this task I think, but I did not find anything
> regarding multicast on ICANN's website (www.icann.org)
> 

Malloc is working on other ways to provide some dynamic allocation
mechanism 
for multicast adresses. You could find more information about this at:

http://www.aciri.org/malloc/

Regards,
Marc-Olivier


-- 
Marc-Olivier Méhu                       
Cybercable                           email: mom@cybercable.fr
20 Place des Vins de France          phone: +33 1 53 44 83 14
75614 PARIS CEDEX 12	                fax:   +33 1 53 44 83 59
FRANCE					

You may delay, but Time will not.	-  Benjamin Franklin 
#include <canonical.disclaimer>      // only my own opinions, etc.


From owner-malloc@catarina.usc.edu  Tue Jun  6 20:40:08 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 UAA21283
	for <malloc-archive@odin.ietf.org>; Tue, 6 Jun 2000 20:40:06 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id RAA20957
	for malloc-list; Tue, 6 Jun 2000 17:31:54 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id RAA20952
	for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 17:31:53 -0700 (PDT)
Received: from dthaler.microsoft.com ([131.107.152.20])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id RAA25993 for <malloc@catarina.usc.edu>; Tue, 6 Jun 2000 17:31:52 -0700 (PDT)
Received: (from dthaler@localhost)
	by dthaler.microsoft.com (8.8.7/8.8.7) id TAA15948;
	Tue, 6 Jun 2000 19:02:18 -0700 (PDT)
	(envelope-from dthaler)
From: Dave Thaler <dthaler@dthaler.microsoft.com>
Message-Id: <200006070202.TAA15948@dthaler.microsoft.com>
Subject: WG Last Call on IPv6 allocation guidelines
To: malloc@catarina.usc.edu
Date: Tue, 6 Jun 2000 19:02:18 -0700 (PDT)
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 opens a WG Last Call on the Internet Draft
described below (the one on IPv6 allocation guidelines).
Please send your comments to the list by June 20.

Thanks,
Dave Thaler
MALLOC WG Co-chair

----- Forwarded message from Internet-Drafts@ietf.org -----

To: IETF-Announce: ;
Cc: malloc@catarina.usc.edu
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-malloc-ipv6-guide-00.txt
Date: Tue, 30 May 2000 06:35:02 -0400

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		: Dynamic Allocation Guidelines for IPv6 Multicast 
                          Addresses
	Author(s)	: B. Haberman
	Filename	: draft-ietf-malloc-ipv6-guide-00.txt
	Pages		: 5
	Date		: 26-May-00
	
With the current multicast address architecture and the proposed 
multicast address architecture, a set of guidelines is needed for 
multicast address allocation servers to use in assigning IPv6 
multicast addresses.  The purpose of these rules is to reduce the 
possibility of address collision not only at layer 3, but also on 
devices at layer 2.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-malloc-ipv6-guide-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-malloc-ipv6-guide-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@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-malloc-ipv6-guide-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.

[message/External-body is not supported, skipping...]

----- End of forwarded message from Internet-Drafts@ietf.org -----


From owner-malloc@catarina.usc.edu  Wed Jun 28 07:27:45 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 HAA18728
	for <malloc-archive@odin.ietf.org>; Wed, 28 Jun 2000 07:27:44 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id EAA09913
	for malloc-list; Wed, 28 Jun 2000 04:20:26 -0700 (PDT)
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 EAA09908
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 04:20:26 -0700 (PDT)
Received: (from pavlin@localhost)
	by rumi.usc.edu (8.9.3/8.9.3) id EAA02883
	for malloc@catarina.usc.edu; Wed, 28 Jun 2000 04:20:26 -0700 (PDT)
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id DAA09697
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 03:51:59 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id DAA19137 for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 03:51:58 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17844;
	Wed, 28 Jun 2000 06:48:39 -0400 (EDT)
Message-Id: <200006281048.GAA17844@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-nest-opt-05.txt
Date: Wed, 28 Jun 2000 06:48:39 -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		: MADCAP Multicast Scope Nesting State Option
	Author(s)	: R. Kermode
	Filename	: draft-ietf-malloc-madcap-nest-opt-05.txt
	Pages		: 14
	Date		: 27-Jun-00
	
This document defines a new option to the Multicast Address Dynamic
Client Allocation Protocol (MADCAP) to support nested scoping. The
new option's purpose is to allow clients to learn which scopes nest
inside each other, and hence may be used for expanding scope searches
or hierarchical multicast transport.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-malloc-madcap-nest-opt-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-nest-opt-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-nest-opt-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:	<20000627104856.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-malloc-madcap-nest-opt-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-malloc-madcap-nest-opt-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000627104856.I-D@ietf.org>

--OtherAccess--

--NextPart--



From owner-malloc@catarina.usc.edu  Wed Jun 28 16:12:31 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 QAA03336
	for <malloc-archive@odin.ietf.org>; Wed, 28 Jun 2000 16:12:30 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id NAA12100
	for malloc-list; Wed, 28 Jun 2000 13:04:03 -0700 (PDT)
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 NAA12095
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 13:04:02 -0700 (PDT)
Received: (from pavlin@localhost)
	by rumi.usc.edu (8.9.3/8.9.3) id NAA09473
	for malloc@catarina.usc.edu; Wed, 28 Jun 2000 13:04:02 -0700 (PDT)
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id NAA12073
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 13:02:18 -0700 (PDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id NAA27808 for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 13:02:18 -0700 (PDT)
Received: from kaipara.live.com (mg128-190.ricochet.net [204.179.128.190])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id MAA08848
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 12:58:42 -0700 (PDT)
Message-Id: <4.3.1.1.20000628124710.00b90ec0@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 28 Jun 2000 12:50:30 -0700
To: malloc@catarina.usc.edu
From: Ross Finlayson <finlayson@live.com>
Subject: Any web page listing MADCAP implementations?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk

I received a question from someone (who saw my name on the "Abstract API" 
I-D) asking about MADCAP implementations.  Is there any web page anywhere 
that lists MADCAP implementations?  In particular, does anyone know of 
MADCAP client (or server) implementations for Solaris or Linux?

	Ross.


From owner-malloc@catarina.usc.edu  Wed Jun 28 16:16: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 QAA03450
	for <malloc-archive@odin.ietf.org>; Wed, 28 Jun 2000 16:16:14 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id NAA12162
	for malloc-list; Wed, 28 Jun 2000 13:10:00 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id NAA12154
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 13:10:00 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id NAA02751 for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 13:09:59 -0700 (PDT)
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA15504;
	Wed, 28 Jun 2000 14:09:47 -0600 (MDT)
Received: from bcn.East.Sun.COM (bcn.East.Sun.COM [129.148.75.4])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA02377;
	Wed, 28 Jun 2000 16:09:46 -0400 (EDT)
Received: from sun.com (dhcp75-155 [129.148.75.155])
	by bcn.East.Sun.COM (8.9.1b+Sun/8.9.1) with ESMTP id QAA01190;
	Wed, 28 Jun 2000 16:09:46 -0400 (EDT)
Message-ID: <395A5B77.7DE20794@sun.com>
Date: Wed, 28 Jun 2000 16:09:27 -0400
From: Steve Hanna <steve.hanna@sun.com>
Organization: Sun Microsystems, Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ross Finlayson <finlayson@live.com>
CC: malloc@catarina.usc.edu
Subject: Re: Any web page listing MADCAP implementations?
References: <4.3.1.1.20000628124710.00b90ec0@shell7.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

I do not know of any such web page, nor do I know of any MADCAP
implementations for Solaris or Linux (at least, not at this point).
Anyone else?

-Steve

Ross Finlayson wrote:
> 
> I received a question from someone (who saw my name on the "Abstract API"
> I-D) asking about MADCAP implementations.  Is there any web page anywhere
> that lists MADCAP implementations?  In particular, does anyone know of
> MADCAP client (or server) implementations for Solaris or Linux?
> 
>         Ross.


From owner-malloc@catarina.usc.edu  Wed Jun 28 17:50:17 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 RAA05061
	for <malloc-archive@odin.ietf.org>; Wed, 28 Jun 2000 17:50:17 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id OAA12608
	for malloc-list; Wed, 28 Jun 2000 14:41:52 -0700 (PDT)
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 OAA12603
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 14:41:52 -0700 (PDT)
Received: (from pavlin@localhost)
	by rumi.usc.edu (8.9.3/8.9.3) id OAA13079
	for malloc@catarina.usc.edu; Wed, 28 Jun 2000 14:41:52 -0700 (PDT)
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id OAA12585
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 14:40:48 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by usc.edu (8.9.3.1/8.9.3/usc) with SMTP
	id OAA10046 for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 14:40:48 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 28 Jun 2000 13:10:08 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Wed, 28 Jun 2000 13:15:19 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4406.0
content-class: urn:content-classes:message
Subject: RE: Any web page listing MADCAP implementations?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFE13C.AAFF5BD4"
Date: Wed, 28 Jun 2000 13:08:47 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A56909EE88FF@SIT.platinum.corp.microsoft.com>
Thread-Topic: Any web page listing MADCAP implementations?
Thread-Index: Ab/hPTBN/kdMTTYkRSuS0eeSke0MOwAADEeg
From: "Munil Shah" <munils@Exchange.Microsoft.com>
To: "Steve Hanna" <steve.hanna@sun.com>, "Ross Finlayson" <finlayson@live.com>
Cc: <malloc@catarina.usc.edu>
X-OriginalArrivalTime: 28 Jun 2000 20:15:19.0739 (UTC) FILETIME=[94EBA8B0:01BFE13D]
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFE13C.AAFF5BD4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

If you are looking for *any* implementation, windows 2000 contains
MADCAP implementation. The win2k product doc has information about it
and the APIs are part of the SDK.

-----Original Message-----
From: Steve Hanna [mailto:steve.hanna@sun.com]
Sent: Wednesday, June 28, 2000 1:09 PM
To: Ross Finlayson
Cc: malloc@catarina.usc.edu
Subject: Re: Any web page listing MADCAP implementations?


I do not know of any such web page, nor do I know of any MADCAP
implementations for Solaris or Linux (at least, not at this point).
Anyone else?

-Steve

Ross Finlayson wrote:
>=20
> I received a question from someone (who saw my name on the "Abstract
API"
> I-D) asking about MADCAP implementations.  Is there any web page
anywhere
> that lists MADCAP implementations?  In particular, does anyone know of
> MADCAP client (or server) implementations for Solaris or Linux?
>=20
>         Ross.

------_=_NextPart_001_01BFE13C.AAFF5BD4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4406.0">
<TITLE>RE: Any web page listing MADCAP implementations?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>If you are looking for *any* implementation, windows =
2000 contains MADCAP implementation. The win2k product doc has =
information about it and the APIs are part of the SDK.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>

<BR><FONT SIZE=3D2>From: Steve Hanna [<A =
HREF=3D"mailto:steve.hanna@sun.com">mailto:steve.hanna@sun.com</A>]</FONT=
>

<BR><FONT SIZE=3D2>Sent: Wednesday, June 28, 2000 1:09 PM</FONT>

<BR><FONT SIZE=3D2>To: Ross Finlayson</FONT>

<BR><FONT SIZE=3D2>Cc: malloc@catarina.usc.edu</FONT>

<BR><FONT SIZE=3D2>Subject: Re: Any web page listing MADCAP =
implementations?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I do not know of any such web page, nor do I know of =
any MADCAP</FONT>

<BR><FONT SIZE=3D2>implementations for Solaris or Linux (at least, not =
at this point).</FONT>

<BR><FONT SIZE=3D2>Anyone else?</FONT>
</P>

<P><FONT SIZE=3D2>-Steve</FONT>
</P>

<P><FONT SIZE=3D2>Ross Finlayson wrote:</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; I received a question from someone (who saw my =
name on the &quot;Abstract API&quot;</FONT>

<BR><FONT SIZE=3D2>&gt; I-D) asking about MADCAP implementations.&nbsp; =
Is there any web page anywhere</FONT>

<BR><FONT SIZE=3D2>&gt; that lists MADCAP implementations?&nbsp; In =
particular, does anyone know of</FONT>

<BR><FONT SIZE=3D2>&gt; MADCAP client (or server) implementations for =
Solaris or Linux?</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Ross.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFE13C.AAFF5BD4--


From owner-malloc@catarina.usc.edu  Wed Jun 28 18:08:11 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 SAA05241
	for <malloc-archive@odin.ietf.org>; Wed, 28 Jun 2000 18:08:10 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id PAA12730
	for malloc-list; Wed, 28 Jun 2000 15:01:01 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id PAA12722
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 15:01:00 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id PAA23357 for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 15:00:59 -0700 (PDT)
Received: from eastmail2.East.Sun.COM ([129.148.1.241])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA13541
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 15:00:50 -0700 (PDT)
Received: from bcn.East.Sun.COM (bcn.East.Sun.COM [129.148.75.4])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA27456
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 18:00:49 -0400 (EDT)
Received: from sun.com (dhcp75-155 [129.148.75.155])
	by bcn.East.Sun.COM (8.9.1b+Sun/8.9.1) with ESMTP id SAA04244
	for <malloc@catarina.usc.edu>; Wed, 28 Jun 2000 18:00:49 -0400 (EDT)
Message-ID: <395A757E.8CC79F43@sun.com>
Date: Wed, 28 Jun 2000 18:00:30 -0400
From: Steve Hanna <steve.hanna@sun.com>
Organization: Sun Microsystems, Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: malloc <malloc@catarina.usc.edu>
Subject: Revised AAP draft
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 revised AAP spec to the Internet Drafts editor. This
document should soon be posted to the Internet Drafts archive. For now,
it is available from the MALLOC web site at:

 http://www.aciri.org/malloc/draft-ietf-malloc-aap-04.txt

This version removes the Scaling Analysis section, since there was not
agreement about it. Since this document has already passed WG Last Call
in a very similar form, it will now be submitted to the IESG with a
request to publish it as a Proposed Standard.

-Steve


From owner-malloc@catarina.usc.edu  Thu Jun 29 06:37:21 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 GAA25117
	for <malloc-archive@odin.ietf.org>; Thu, 29 Jun 2000 06:37:20 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id DAA15397
	for malloc-list; Thu, 29 Jun 2000 03:29:38 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id DAA15392
	for <malloc@catarina.usc.edu>; Thu, 29 Jun 2000 03:29:37 -0700 (PDT)
Received: from infres.enst.fr (infres.enst.fr [137.194.160.3])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id DAA04155 for <malloc@catarina.usc.edu>; Thu, 29 Jun 2000 03:29:35 -0700 (PDT)
Received: from horla.enst.fr (horla.enst.fr [137.194.161.1])
	by infres.enst.fr (Postfix) with ESMTP
	id 13BD445424; Thu, 29 Jun 2000 12:22:51 +0200 (MET DST)
Received: (from dax@localhost)
	by horla.enst.fr (8.9.1a/8.9.1) id MAA01635;
	Thu, 29 Jun 2000 12:22:25 +0200 (MET DST)
Date: Thu, 29 Jun 2000 12:22:25 +0200
From: Philippe Dax <dax@inf.enst.fr>
To: Ross Finlayson <finlayson@live.com>
Cc: malloc@catarina.usc.edu
Subject: Re: Any web page listing MADCAP implementations?
Message-ID: <20000629122225.A234@horla.enst.fr>
References: <4.3.1.1.20000628124710.00b90ec0@shell7.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1us
In-Reply-To: Ross Finlayson on Wed, Jun 28, 2000 at 12:50:30PM -0700
X-Organization: ENST
X-WWW: http://www.infres.enst.fr/~dax/
X-Whois: whois -h whois.ripe.net PD97
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk

Hello Malloc members,

At ENST we have developed a MAAS server which implements
MADCAP Protocol (RFC 2730) without the AAP part.
The code was written in C by students which can't follow up
their implementation.

We don't have any Web page, but the source is available by ftp at:

ftp://ftp.enst.fr/pub/network/multicast/maas/maas-0.1.tar.gz

--
Philippe

On 28/06, Ross Finlayson wrote:
| I received a question from someone (who saw my name on the "Abstract API" 
| I-D) asking about MADCAP implementations.  Is there any web page anywhere 
| that lists MADCAP implementations?  In particular, does anyone know of 
| MADCAP client (or server) implementations for Solaris or Linux?
| 
| 	Ross.


From owner-malloc@catarina.usc.edu  Fri Jun 30 08:32:19 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 IAA15631
	for <malloc-archive@odin.ietf.org>; Fri, 30 Jun 2000 08:32:18 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id FAA20806
	for malloc-list; Fri, 30 Jun 2000 05:10:27 -0700 (PDT)
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 FAA20801
	for <malloc@catarina.usc.edu>; Fri, 30 Jun 2000 05:10:26 -0700 (PDT)
Received: (from pavlin@localhost)
	by rumi.usc.edu (8.9.3/8.9.3) id FAA46839
	for malloc@catarina.usc.edu; Fri, 30 Jun 2000 05:10:26 -0700 (PDT)
Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id FAA20787
	for <malloc@catarina.usc.edu>; Fri, 30 Jun 2000 05:08:46 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id FAA03105 for <malloc@catarina.usc.edu>; Fri, 30 Jun 2000 05:08:47 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14751;
	Fri, 30 Jun 2000 08:05:20 -0400 (EDT)
Message-Id: <200006301205.IAA14751@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: malloc@catarina.usc.edu
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: MADCAP Multicast Scope Nesting State Option
	 to Proposed Standard
Date: Fri, 30 Jun 2000 08:05:20 -0400
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk



The IESG has approved the Internet-Draft 'MADCAP Multicast Scope
Nesting State Option' <draft-ietf-malloc-madcap-nest-opt-05.txt> as a
Proposed Standard.  This document is the product of the
Multicast-Address Allocation Working Group.  The IESG contact person is
Thomas Narten.


Technical Summary
 
 This document defines a new option to the Multicast Address Dynamic
 Client Allocation Protocol (MADCAP) to support nested scoping. The
 new option's purpose is to allow clients to learn which scopes nest
 inside each other, and hence may be used for expanding scope searches
 or hierarchical multicast transport.

Working Group Summary

 There was consensus in the WG for this option and no issues were
 raised during the Last Call.

Protocol Quality

 This protocol has been reviewed for the IESG by Thomas Narten and
 Vern Paxson.


From owner-malloc@catarina.usc.edu  Fri Jun 30 16:13:18 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 QAA25643
	for <malloc-archive@odin.ietf.org>; Fri, 30 Jun 2000 16:13:17 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id MAA22354
	for malloc-list; Fri, 30 Jun 2000 12:19:20 -0700 (PDT)
X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-malloc@catarina.usc.edu using -f
Received: from usc.edu (root@usc.edu [128.125.253.136])
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id MAA22349
	for <malloc@catarina.usc.edu>; Fri, 30 Jun 2000 12:19:18 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP
	id MAA22190 for <malloc@catarina.usc.edu>; Fri, 30 Jun 2000 12:19:19 -0700 (PDT)
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA23754;
	Fri, 30 Jun 2000 13:18:58 -0600 (MDT)
Received: from bcn.East.Sun.COM (bcn.East.Sun.COM [129.148.75.4])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA28759;
	Fri, 30 Jun 2000 15:18:57 -0400 (EDT)
Received: from sun.com (dhcp75-155 [129.148.75.155])
	by bcn.East.Sun.COM (8.9.1b+Sun/8.9.1) with ESMTP id PAA25842;
	Fri, 30 Jun 2000 15:18:56 -0400 (EDT)
Message-ID: <395CF28C.D7C96549@sun.com>
Date: Fri, 30 Jun 2000 15:18:36 -0400
From: Steve Hanna <steve.hanna@sun.com>
Organization: Sun Microsystems, Inc.
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: malloc <malloc@catarina.usc.edu>,
        Roger Kermode <Roger.Kermode@motorola.com>
Subject: Re: Protocol Action: MADCAP Multicast Scope Nesting State Optionto 
 Proposed Standard
References: <200006301205.IAA14751@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-malloc@catarina.usc.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thanks for your work on this, Roger. Good job!

-Steve

The IESG wrote:
> 
> The IESG has approved the Internet-Draft 'MADCAP Multicast Scope
> Nesting State Option' <draft-ietf-malloc-madcap-nest-opt-05.txt> as a
> Proposed Standard.  This document is the product of the
> Multicast-Address Allocation Working Group.  The IESG contact person is
> Thomas Narten.
> 
> Technical Summary
> 
>  This document defines a new option to the Multicast Address Dynamic
>  Client Allocation Protocol (MADCAP) to support nested scoping. The
>  new option's purpose is to allow clients to learn which scopes nest
>  inside each other, and hence may be used for expanding scope searches
>  or hierarchical multicast transport.
> 
> Working Group Summary
> 
>  There was consensus in the WG for this option and no issues were
>  raised during the Last Call.
> 
> Protocol Quality
> 
>  This protocol has been reviewed for the IESG by Thomas Narten and
>  Vern Paxson.