From owner-extdom.ssm-interest@sj-msg-core-1.cisco.com  Fri Dec  1 18:20:56 2000
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26302
	for <ssm-archive@odin.ietf.org>; Fri, 1 Dec 2000 18:20:56 -0500 (EST)
Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA21599
	for <ssm-interest@external.cisco.com>; Fri, 1 Dec 2000 14:07:29 -0800 (PST)
Received: from proxy2.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id eB1M7Nk08464
	for <ssm-interest@external.cisco.com>; Fri, 1 Dec 2000 14:07:23 -0800 (PST)
Received: from mailman.sprintlabs.com (mx.sprintlabs.com [208.30.174.2])
	by proxy2.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id OAA11487
	for <ssm-interest@external.cisco.com>; Fri, 1 Dec 2000 14:06:32 -0800 (PST)
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2652.78)
	id <XJD1RW60>; Fri, 1 Dec 2000 14:04:20 -0800
Received: from sprintlabs.com (ip199-2-53-56.sprintlabs.com [199.2.53.56]) by mailman.sprintlabs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.78)
	id XJD1RW69; Fri, 1 Dec 2000 14:04:16 -0800
From: Supratik Bhattacharyya <Supratik@sprintlabs.com>
To: ssm-interest@external.cisco.com
Message-ID: <3A281FAB.8E24B7AB@sprintlabs.com>
Date: Fri, 01 Dec 2000 14:01:16 -0800
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Agenda for San Diego meeting.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Agenda Bashing
5 min

Update on architecture spec                                         10
min
(draft-holbrook-ssm-arch-01.txt)
[Hugh Holbrook]

Update on framework document                                    5 min
(draft-bhattach-ssm-framework-01.txt)
[ Supratik Bhattacharyya]

Remaining issues in draft-idmr-igmpv3-ssm-00.txt          10 min

Update on PIM spec                                                    5
min
(draft-ietf-pim-sm-v2-new-01.txt)

SSM and IPv6
15 min
[Brian Haberman]

Revisit topics from last WG meeting :                          10 min
   Reverse IGMP to the source
   Tunneling over non-multicast capable domains

Wrap
Up                                                                    5
min







From owner-extdom.ssm-interest@sj-msg-core-1.cisco.com  Sun Dec  3 12:04:37 2000
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20797
	for <ssm-archive@odin.ietf.org>; Sun, 3 Dec 2000 12:04:37 -0500 (EST)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id IAA28658
	for <ssm-interest@external.cisco.com>; Sun, 3 Dec 2000 08:09:20 -0800 (PST)
Received: from proxy3.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id eB3G9P315693
	for <ssm-interest@external.cisco.com>; Sun, 3 Dec 2000 08:09:25 -0800 (PST)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by proxy3.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id IAA16590
	for <ssm-interest@external.cisco.com>; Sun, 3 Dec 2000 08:09:10 -0800 (PST)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id eB3G44438015;
	Sun, 3 Dec 2000 17:04:04 +0100
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id RAA08614;
	Sun, 3 Dec 2000 17:04:03 +0100 (MET)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id RAA25645;
	Sun, 3 Dec 2000 17:04:23 +0100 (CET)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200012031604.RAA25645@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vida Rolland <Rolland.Vida@lip6.fr>
cc: ipng@sunroof.eng.sun.com, ssm-interest@external.cisco.com,
        Supratik Bhattacharyya <supratik@sprintlabs.com>
Subject: Re: MLDv3 - Internet Draft 
In-reply-to: Your message of Wed, 08 Nov 2000 18:30:19 +0100.
             <3A098DAB.52FD42BD@rp.lip6.fr> 
Date: Sun, 03 Dec 2000 17:04:23 +0100
Sender: Francis.Dupont@enst-bretagne.fr

 In your previous mail you wrote:

   Here is the abstract of an Internet Draft proposal, called "Multicast
   Listener Discovery Version 3 (MLDv3) for IPv6"
   (<draft-vida-mld-v3-00.txt>)
   
=> was this I-D proposed to the Internet Draft Editor (I can't find it
in the repository)?

Regards

Francis.Dupont@enst-bretagne.fr


From owner-extdom.ssm-interest@sj-msg-core-4.cisco.com  Tue Dec  5 07:14:22 2000
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA22224
	for <ssm-archive@odin.ietf.org>; Tue, 5 Dec 2000 07:14:21 -0500 (EST)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id DAA25345
	for <ssm-interest@external.cisco.com>; Tue, 5 Dec 2000 03:08:49 -0800 (PST)
Received: from proxy1.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id eB5B91114575
	for <ssm-interest@external.cisco.com>; Tue, 5 Dec 2000 03:09:01 -0800 (PST)
Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2])
	by proxy1.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id DAA09680
	for <ssm-interest@external.cisco.com>; Tue, 5 Dec 2000 03:08:42 -0800 (PST)
Received: from rp.lip6.fr (tibre.lip6.fr [132.227.74.2])
          by isis.lip6.fr (8.9.3/jtpda-5.3.2) with ESMTP id LAA02145
          ; Tue, 5 Dec 2000 11:42:17 +0100
Received: from rp.lip6.fr (otos.lip6.fr [132.227.61.47])
          by rp.lip6.fr (8.8.8/jtpda-5.2) with ESMTP id LAA09664
          ; Tue, 5 Dec 2000 11:42:16 +0100 (MET)
Message-ID: <3A2CC688.10A0BD6A@rp.lip6.fr>
Date: Tue, 05 Dec 2000 11:42:16 +0100
From: Vida Rolland <Rolland.Vida@lip6.fr>
Organization: Laboratoire Lip6
X-Mailer: Mozilla 4.75 [fr] (WinNT; U)
X-Accept-Language: fr
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
CC: ipng@sunroof.eng.sun.com, ssm-interest@external.cisco.com
Subject: Re: MLDv3 - Internet Draft
References: <200012031604.RAA25645@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by sj-msg-core-4.cisco.com id DAA25346
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA22224

The MLDv3 draft was not proposed to the Internet Draft Editor as it was a
preliminary version. We were waiting for the new version of the IGMPv3
draft, that actually came out a few days ago. We are working now on adapting
MLDv3 to the changes that were made in the new IGMPv3 version.

A new version of the MLDv3 draft will be available in a couple of days.

Regards,
Rolland Vida, LIP6, Paris

Francis Dupont a écrit :

>  In your previous mail you wrote:
>
>    Here is the abstract of an Internet Draft proposal, called "Multicast
>    Listener Discovery Version 3 (MLDv3) for IPv6"
>    (<draft-vida-mld-v3-00.txt>)
>
> => was this I-D proposed to the Internet Draft Editor (I can't find it
> in the repository)?
>
> Regards
>
> Francis.Dupont@enst-bretagne.fr



From owner-extdom.ssm-interest@sj-msg-core-2.cisco.com  Sat Dec  9 14:44:07 2000
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14532
	for <ssm-archive@odin.ietf.org>; Sat, 9 Dec 2000 14:44:07 -0500 (EST)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id KAA13870
	for <ssm-interest@external.cisco.com>; Sat, 9 Dec 2000 10:40:20 -0800 (PST)
Received: from proxy1.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id eB9IeSf21615
	for <ssm-interest@external.cisco.com>; Sat, 9 Dec 2000 10:40:28 -0800 (PST)
Received: from nt1.rocori.k12.mn.us (nt1.rocori.k12.mn.us [207.229.251.2])
	by proxy1.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id KAA06089
	for <ssm-interest@external.cisco.com>; Sat, 9 Dec 2000 10:40:08 -0800 (PST)
Message-Id: <200012091840.KAA06089@proxy1.cisco.com>
From: Mail Sender<postmaster@rusgoods.ru>
To: sroberto@one.net
CC: srvloc@srvloc.org, srvloc-request@srvloc.org, ssantaniello@grr.com,
        ssb@fast.no, ssm-interest@external.cisco.com
Subject: Russian Goods and Service from Moscow
Reply-To: mailsender@mailsender.ru
Date: 09.12.2000
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii


www.rusgoods.com    www.rusgoods.ru
================================================================
We present you the production of the 1-st Moscow Watch Factory "Poljot" (Flying). From the simple mechanical 
watch of the series 2609 till unique, composite and precise mechanical o'clock - Marine timer . 
  It is unique factory in Russia, which makes mechanical hours with the Swiss quality. Factory, which makes 
watches for the Russian Air Forces , Russian Naval Forces. 
  All mechanical watch which we offer to you, will be delivered to you directly from the factory. If it isn't in the 
warehouse of the factory, we will place your order directly at the 1-st Moscow Watch Factory without any 
middlemans.
 The submarine "Kursk" had on board mechanical marine hronometr 6MX. 
 ===============================================================
The "table" of orders.    Here you can to order, to find, to know almost everything, than the Russia is rich, 
everything 
that does not contradict Russian Federation laws. 
Here you can receive or order:

The information about any enterprise, firm, organization, or person in Russia 
The production or any goods of Russian manufactories, and other things if it is possible. 
===============================================================
www.rusgoods.com    www.rusgoods.ru


From owner-extdom.ssm-interest@sj-msg-core-2.cisco.com  Wed Dec 13 14:04:07 2000
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03771
	for <ssm-archive@odin.ietf.org>; Wed, 13 Dec 2000 14:04:07 -0500 (EST)
Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id JAA22525
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 09:44:04 -0800 (PST)
Received: from proxy2.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id eBDHhuc20858
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 09:44:00 -0800 (PST)
Received: from multicasttech.com (ns2.multicasttech.com [63.105.122.8])
	by proxy2.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id JAA13911
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 09:42:40 -0800 (PST)
Received: from [207.137.70.59] (HELO 21rst-century.com)
  by multicasttech.com (CommuniGate Pro SMTP 3.3)
  with ESMTP id 620643; Wed, 13 Dec 2000 12:24:54 -0500
Message-ID: <3A37B286.D1BDEBF3@21rst-century.com>
Date: Wed, 13 Dec 2000 12:31:51 -0500
From: Marshall Eubanks <tme@21rst-century.com>
Reply-To: tme@21rst-century.com
Organization: Multicast Technologies
X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: ssm-interest@external.cisco.com,
        Supratik Bhattacharyya <supratik@sprintlabs.com>
Subject: SSM Address Space
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello;

   In the SSM meeting yesterday there was a little discussion about
the SSM address space. Now, I think that using something other than 
232/8 for Global scope SSM iss a VERY bad idea. Everyone should know
how hard it is to get the whole Internet to coordinate on something -
you would then for sure have domains that multicast peer using SSM on one
side and ISM on the other for the same address range - which would be bad
for interoperability and for deployment.

   Having said that, I can easily see that as SSM applications become available,
then people will want to use them for administratively or ttl scoped
address ranges.
Since it's localized, you can do what you want and not worry about interfering
with other peoples deployments.

   So, shouldn't the (framework?) draft state something like

SSM applications with global scope MUST be restricted to the 232/8
address range.
Applicatations in the 239/8 address range, or in other restricted scope
address 
ranges, MAY use SSM as desired; however, the administrator of the scoped address
space MUST ensure that SSM trees do not cross the scope domain boundaries.


                                   Regards
                                   Marshall Eubanks

   Multicast Technologies, Inc.
   10301 Democracy Lane, Suite 201
   Fairfax, Virginia 22030
   Phone : 703-293-9624          Fax     : 703-293-9609     
   e-mail : tme@on-the-i.com     http://www.on-the-i.com


From owner-extdom.ssm-interest@rtp-msg-core-1.cisco.com  Wed Dec 13 14:55:21 2000
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11080
	for <ssm-archive@odin.ietf.org>; Wed, 13 Dec 2000 14:55:20 -0500 (EST)
Received: from cisco.com (omega.cisco.com [171.69.63.141])
	by rtp-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id NAA25303
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 13:40:26 -0500 (EST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id KAA07051;
	Wed, 13 Dec 2000 10:41:58 -0800 (PST)
From: Toerless Eckert <eckert@cisco.com>
Message-Id: <200012131841.KAA07051@cisco.com>
Subject: Re: SSM Address Space
To: tme@21rst-century.com
Date: Wed, 13 Dec 2000 10:41:58 -0800 (PST)
Cc: ssm-interest@external.cisco.com,
        supratik@sprintlabs.com (Supratik Bhattacharyya)
In-Reply-To: <3A37B286.D1BDEBF3@21rst-century.com> from "Marshall Eubanks" at Dec 13, 2000 12:31:51 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Agreed in princile. 

Would it not be sufficient to say that an SSM address space can only be of
global scope if it is assigned by IANA for this purpose ?

Cheers
	Toerless


From owner-extdom.ssm-interest@sj-msg-core-4.cisco.com  Wed Dec 13 15:26:22 2000
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16263
	for <ssm-archive@odin.ietf.org>; Wed, 13 Dec 2000 15:26:21 -0500 (EST)
Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id KAA21905
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 10:43:30 -0800 (PST)
Received: from proxy3.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id eBDIhSn22692
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 10:43:28 -0800 (PST)
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by proxy3.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id KAA04545
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 10:43:20 -0800 (PST)
Received: from neserve0.corp.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148])
	id QQjtks07878;
	Wed, 13 Dec 2000 18:42:25 GMT
Received: by neserve0.corp.us.uu.net 
	id QQjtks14304;
	Wed, 13 Dec 2000 13:42:13 -0500 (EST)
From: jhall@UU.NET (Jeremy Hall)
Message-Id: <QQjtks14304.200012131842@neserve0.corp.us.uu.net>
Subject: Re: SSM Address Space
In-Reply-To: <3A37B286.D1BDEBF3@21rst-century.com> from Marshall Eubanks at "Dec
 13, 2000 12:31:51 pm"
To: tme@21rst-century.com
Date: Wed, 13 Dec 2000 13:42:12 -0500 (EST)
CC: ssm-interest@external.cisco.com,
        Supratik Bhattacharyya <supratik@sprintlabs.com>
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

sounds fine to me...I think people using SSM should use 232 regardless and
figure out how to do their own scoping.

_J

In the new year, Marshall Eubanks wrote:
> Hello;
> 
>    In the SSM meeting yesterday there was a little discussion about
> the SSM address space. Now, I think that using something other than 
> 232/8 for Global scope SSM iss a VERY bad idea. Everyone should know
> how hard it is to get the whole Internet to coordinate on something -
> you would then for sure have domains that multicast peer using SSM on one
> side and ISM on the other for the same address range - which would be bad
> for interoperability and for deployment.
> 
>    Having said that, I can easily see that as SSM applications become available,
> then people will want to use them for administratively or ttl scoped
> address ranges.
> Since it's localized, you can do what you want and not worry about interfering
> with other peoples deployments.
> 
>    So, shouldn't the (framework?) draft state something like
> 
> SSM applications with global scope MUST be restricted to the 232/8
> address range.
> Applicatations in the 239/8 address range, or in other restricted scope
> address 
> ranges, MAY use SSM as desired; however, the administrator of the scoped address
> space MUST ensure that SSM trees do not cross the scope domain boundaries.
> 
> 
>                                    Regards
>                                    Marshall Eubanks
> 
>    Multicast Technologies, Inc.
>    10301 Democracy Lane, Suite 201
>    Fairfax, Virginia 22030
>    Phone : 703-293-9624          Fax     : 703-293-9609     
>    e-mail : tme@on-the-i.com     http://www.on-the-i.com
> 



From owner-extdom.ssm-interest@sj-msg-core-1.cisco.com  Wed Dec 13 15:42:59 2000
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19256
	for <ssm-archive@odin.ietf.org>; Wed, 13 Dec 2000 15:42:59 -0500 (EST)
Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA09200
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 11:16:51 -0800 (PST)
Received: from proxy1.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id eBDJGi110957
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 11:16:44 -0800 (PST)
Received: from multicasttech.com (ns2.multicasttech.com [63.105.122.8])
	by proxy1.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id LAA19686
	for <ssm-interest@external.cisco.com>; Wed, 13 Dec 2000 11:16:34 -0800 (PST)
Received: from [207.137.70.59] (HELO 21rst-century.com)
  by multicasttech.com (CommuniGate Pro SMTP 3.3)
  with ESMTP id 620682; Wed, 13 Dec 2000 13:41:28 -0500
Message-ID: <3A37C471.E522B20C@21rst-century.com>
Date: Wed, 13 Dec 2000 13:48:17 -0500
From: Marshall Eubanks <tme@21rst-century.com>
Reply-To: tme@21rst-century.com
Organization: Multicast Technologies
X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
CC: ssm-interest@external.cisco.com,
        Supratik Bhattacharyya <supratik@sprintlabs.com>
Subject: Re: SSM Address Space
References: <200012131841.KAA07051@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Toerless Eckert wrote:
> 
> Agreed in princile.
> 
> Would it not be sufficient to say that an SSM address space can only be of
> global scope if it is assigned by IANA for this purpose ?
> 
> Cheers
>         Toerless

That's a good idea - it makes it IPv6 compliant :)
-- 


                                   Regards
                                   Marshall Eubanks

  
   Multicast Technologies, Inc.
   10301 Democracy Lane, Suite 201
   Fairfax, Virginia 22030
   Phone : 703-293-9624          Fax     : 703-293-9609     
   e-mail : tme@on-the-i.com     http://www.on-the-i.com


From owner-extdom.ssm-interest@sj-msg-core-4.cisco.com  Fri Dec 22 02:02:42 2000
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22699
	for <ssm-archive@odin.ietf.org>; Fri, 22 Dec 2000 02:02:41 -0500 (EST)
Received: from sj-msg-av-2.cisco.com (sj-msg-av-2.cisco.com [171.71.163.110])
	by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id VAA16930
	for <ssm-interest@external.cisco.com>; Thu, 21 Dec 2000 21:52:53 -0800 (PST)
Received: from proxy3.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-2.cisco.com (8.10.1/8.10.1) with ESMTP id eBM5qpN24135
	for <ssm-interest@external.cisco.com>; Thu, 21 Dec 2000 21:52:52 -0800 (PST)
Received: from ns.live.com (ns.live.com [208.184.148.162])
	by proxy3.cisco.com (8.9.1b+Sun/8.9.3) with ESMTP id VAA15739
	for <ssm-interest@external.cisco.com>; Thu, 21 Dec 2000 21:52:39 -0800 (PST)
Received: from rsf-laptop.live.com (dhcp0.live.com [208.184.148.170])
	by ns.live.com (8.9.3/8.9.3) with ESMTP id VAA30116
	for <ssm-interest@external.cisco.com>; Thu, 21 Dec 2000 21:47:50 -0800 (PST)
	(envelope-from finlayson@live.com)
Message-Id: <4.3.1.1.20001221213044.00bb1640@localhost>
X-Sender: rsf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 21 Dec 2000 21:47:49 -0800
To: ssm-interest@external.cisco.com
From: Ross Finlayson <finlayson@live.com>
Subject: UMTP updated to handle tunneling of SSM sessions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

As you might have heard at the San Diego IETF (but not from me, as I wasn't 
there:-), I have recently revised the UMTP ("UDP Multicast Tunneling 
Protocol") specification to handle SSM sessions (in addition to ISM).  I 
have submitted the updated draft to the Internet Drafts editor; you can 
also read it online at <http://www.live.com/umtp.txt>.  I have also 
upgraded my UMTP server implementation ("liveGate").

UMTP allows multicast data to be received by users who are behind 
non-multicast-capable routers, without them having to modify their 
applications, or use raw sockets.  (Note, however, that for SSM sessions, 
the receiving application will need to be made aware of the fact that UDP 
tunneling will change the session's source address.)

UMTP is not the ideal way for users to receive SSM sessions (it's better 
for them to have real SSM-capable routers, or, failing that, use PIM 
tunneling), but it's one way to help bring SSM to the masses...

         Ross.




