From mailman-admin@ietf.org  Thu Apr  1 18:48:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10288
	for <ssm-archive@lists.ietf.org>; Thu, 1 Apr 2004 18:48:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B99lg-0003Ai-VF
	for ssm-archive@lists.ietf.org; Thu, 01 Apr 2004 16:30:32 -0500
Date: Thu, 01 Apr 2004 11:24:26 -0500
Message-ID: <20040401162426.11029.36842.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ssm-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, ssm-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for ssm-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
ssm@ietf.org                             mifemu    
https://www1.ietf.org/mailman/options/ssm/ssm-archive%40lists.ietf.org


From exim@www1.ietf.org  Fri Apr  2 00:00:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09078
	for <ssm-archive@odin.ietf.org>; Fri, 2 Apr 2004 00:00:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9Dyz-0000kj-KF
	for ssm-archive@odin.ietf.org; Thu, 01 Apr 2004 21:00:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3220X6Q002885
	for ssm-archive@odin.ietf.org; Thu, 1 Apr 2004 21:00:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B9BYw-0006Iy-Rx
	for ssm-web-archive@optimus.ietf.org; Thu, 01 Apr 2004 18:25:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08787
	for <ssm-web-archive@ietf.org>; Thu, 1 Apr 2004 18:25:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9BYt-0001Y1-00
	for ssm-web-archive@ietf.org; Thu, 01 Apr 2004 18:25:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B9BY3-0001Ss-00
	for ssm-web-archive@ietf.org; Thu, 01 Apr 2004 18:24:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B9BXI-0001Mr-00
	for ssm-web-archive@ietf.org; Thu, 01 Apr 2004 18:23:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B99ND-0003dv-FQ
	for ssm-web-archive@ietf.org; Thu, 01 Apr 2004 16:05:15 -0500
Date: Thu, 01 Apr 2004 11:18:36 -0500
Message-ID: <20040401161836.11029.85977.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ssm-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	NO_REAL_NAME autolearn=no version=2.60

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, ssm-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for ssm-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
ssm@ietf.org                             daemut    
https://www1.ietf.org/mailman/options/ssm/ssm-web-archive%40ietf.org



From ssm-admin@ietf.org  Tue Apr 13 18:15:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14511
	for <ssm-archive@lists.ietf.org>; Tue, 13 Apr 2004 18:15:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDVxm-0003u2-8V; Tue, 13 Apr 2004 18:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDVtD-0002PA-2u
	for ssm@optimus.ietf.org; Tue, 13 Apr 2004 17:56:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12158
	for <ssm@ietf.org>; Tue, 13 Apr 2004 17:56:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDVt9-0007jb-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:56:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDVhF-0006CJ-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:43:58 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDVV0-00055a-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:31:19 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1BDVUz-0002Y3-Um
	for ssm@ietf.org; Tue, 13 Apr 2004 21:31:18 +0000
Date: Tue, 13 Apr 2004 14:31:16 -0700
From: Alex Zinin <zinin@psg.com>
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1998261226.20040413143116@psg.com>
To: ssm@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [ssm] AD-review comments on draft-ietf-ssm-arch-04.txt
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks-

 Please find attached my AD-review comments on the SSM architecture
 document.

-- 
Alex
http://www.psg.com/~zinin/

Generally the document is in a great shape. Very good job. I have one meta
issue and one editorial nit.

Meta:

 The document does not spell out what protocols hosts and routers MUST
 implement. I.e., this kind of document is expected to specify the
 mandatory-to-implement mechanisms that will ensure that hosts and routers can
 interoperate. However, there is no place in the document where it says
 something like "hosts supporting the SSM network service MUST implement IGMPv3
 for IPv4 and MLDv2 for IPv6", or "routers supporting the SSM network service
 MUST implement PIM-SSM..."

Editorial

 The following part:

> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119 [RFC 2119].

 should be moved inside the body of the document (preferably not in Abstract)

 Abstract:

> IP addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are
> designated as source-specific multicast (SSM) destination addresses and
> are reserved for use by source-specific applications and protocols.  For
> IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for
> source-specific multicast use.  It defines an extension to the Internet
                                  ^^
                                needs to be expanded. "This document" ?


 Section "Intellectual Property Rights Notice". To reflect the situation
 with Apple, this section also needs to include the following paragraph
 from RFC 2026.

         "The IETF has been notified of intellectual property rights
         claimed in regard to some or all of the specification contained
         in this document.  For more information consult the online list
         of claimed rights."



_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Tue Apr 13 19:07:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17837
	for <ssm-archive@odin.ietf.org>; Tue, 13 Apr 2004 19:07:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDWr3-0002cN-4n
	for ssm-archive@odin.ietf.org; Tue, 13 Apr 2004 18:58:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3DMw91v010059
	for ssm-archive@odin.ietf.org; Tue, 13 Apr 2004 18:58:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDWgE-0001NW-Jn
	for ssm-web-archive@optimus.ietf.org; Tue, 13 Apr 2004 18:46:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16647
	for <ssm-web-archive@ietf.org>; Tue, 13 Apr 2004 18:46:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDWgB-0003Ya-00
	for ssm-web-archive@ietf.org; Tue, 13 Apr 2004 18:46:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDWPY-0002Qg-00
	for ssm-web-archive@ietf.org; Tue, 13 Apr 2004 18:29:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDWBb-0001BB-00
	for ssm-web-archive@ietf.org; Tue, 13 Apr 2004 18:15:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDVxm-0003u2-8V; Tue, 13 Apr 2004 18:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BDVtD-0002PA-2u
	for ssm@optimus.ietf.org; Tue, 13 Apr 2004 17:56:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12158
	for <ssm@ietf.org>; Tue, 13 Apr 2004 17:56:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDVt9-0007jb-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:56:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BDVhF-0006CJ-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:43:58 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BDVV0-00055a-00
	for ssm@ietf.org; Tue, 13 Apr 2004 17:31:19 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1BDVUz-0002Y3-Um
	for ssm@ietf.org; Tue, 13 Apr 2004 21:31:18 +0000
Date: Tue, 13 Apr 2004 14:31:16 -0700
From: Alex Zinin <zinin@psg.com>
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1998261226.20040413143116@psg.com>
To: ssm@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [ssm] AD-review comments on draft-ietf-ssm-arch-04.txt
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks-

 Please find attached my AD-review comments on the SSM architecture
 document.

-- 
Alex
http://www.psg.com/~zinin/

Generally the document is in a great shape. Very good job. I have one meta
issue and one editorial nit.

Meta:

 The document does not spell out what protocols hosts and routers MUST
 implement. I.e., this kind of document is expected to specify the
 mandatory-to-implement mechanisms that will ensure that hosts and routers can
 interoperate. However, there is no place in the document where it says
 something like "hosts supporting the SSM network service MUST implement IGMPv3
 for IPv4 and MLDv2 for IPv6", or "routers supporting the SSM network service
 MUST implement PIM-SSM..."

Editorial

 The following part:

> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119 [RFC 2119].

 should be moved inside the body of the document (preferably not in Abstract)

 Abstract:

> IP addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are
> designated as source-specific multicast (SSM) destination addresses and
> are reserved for use by source-specific applications and protocols.  For
> IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for
> source-specific multicast use.  It defines an extension to the Internet
                                  ^^
                                needs to be expanded. "This document" ?


 Section "Intellectual Property Rights Notice". To reflect the situation
 with Apple, this section also needs to include the following paragraph
 from RFC 2026.

         "The IETF has been notified of intellectual property rights
         claimed in regard to some or all of the specification contained
         in this document.  For more information consult the online list
         of claimed rights."



_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Wed Apr 21 06:29:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09184
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 06:29:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGEuc-0000Bz-5l; Wed, 21 Apr 2004 06:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGEmk-0006Ka-TD
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 06:16:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08792
	for <ssm@ietf.org>; Wed, 21 Apr 2004 06:16:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGEmg-000109-Um
	for ssm@ietf.org; Wed, 21 Apr 2004 06:16:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGElp-0000sZ-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:15:57 -0400
Received: from saturn.mahidol.ac.th ([202.28.162.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGEko-0000dP-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:14:54 -0400
Received: from muscan2 (muscan2.mahidol.ac.th [202.28.162.14])
	by saturn.mahidol.ac.th (8.12.10/8.12.5) with SMTP id i3LA4CRD032199
	for <ssm@ietf.org>; Wed, 21 Apr 2004 17:04:12 +0700
Received: from 202.28.162.18 by muscan2 (InterScan E-Mail VirusWall NT); Wed, 21 Apr 2004 17:21:50 +0700
Received: from [10.22.103.27] ([10.22.103.27])
	by mail.mahidol.ac.th (8.12.10/8.11.6) with ESMTP id i3L9uWEB027137
	for <ssm@ietf.org>; Wed, 21 Apr 2004 16:56:32 +0700
Date: Wed, 21 Apr 2004 19:14:06 +0900
From: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>
To: ssm@ietf.org
Message-Id: <20040421185149.259F.CCVVS@mahidol.ac.th>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.2 required=5.0 tests=DEAR_SOMETHING autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Subject: [ssm] Any SSM implementations on PC routers ?
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear Sir,

	I would like to know whether there is any "open source" 
	for the SSM implementation ?
	I mean the routing daemon, not the IGMPv3 nor the MLDv2.

	As far as I know, Cisco and Juniper routers can support 
	SSM routing, but I haven't heard of the free software running on
	PC routers such as on the *BSD or the Linux.

Thank you very much in advance.

Sincerely Yours,
Vasaka

--------------------------------------------------------
Vasaka Visoottiviseth
Computer Science Department, Faculty of Science
Mahidol University, Thailand
http://www.sc.mahidol.ac.th/sccs/
-------------------------------------------------------


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Wed Apr 21 06:34:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09465
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 06:34:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGF2e-0003GX-9t
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 06:33:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LAXKqs012553
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 06:33:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGF08-0002Bs-M4
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 06:30:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09260
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 06:30:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGF04-0002YN-Pr
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:30:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGEzA-0002Rn-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:29:45 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGEyQ-0002LV-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:28:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGEuc-0000Bz-5l; Wed, 21 Apr 2004 06:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGEmk-0006Ka-TD
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 06:16:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08792
	for <ssm@ietf.org>; Wed, 21 Apr 2004 06:16:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGEmg-000109-Um
	for ssm@ietf.org; Wed, 21 Apr 2004 06:16:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGElp-0000sZ-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:15:57 -0400
Received: from saturn.mahidol.ac.th ([202.28.162.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGEko-0000dP-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:14:54 -0400
Received: from muscan2 (muscan2.mahidol.ac.th [202.28.162.14])
	by saturn.mahidol.ac.th (8.12.10/8.12.5) with SMTP id i3LA4CRD032199
	for <ssm@ietf.org>; Wed, 21 Apr 2004 17:04:12 +0700
Received: from 202.28.162.18 by muscan2 (InterScan E-Mail VirusWall NT); Wed, 21 Apr 2004 17:21:50 +0700
Received: from [10.22.103.27] ([10.22.103.27])
	by mail.mahidol.ac.th (8.12.10/8.11.6) with ESMTP id i3L9uWEB027137
	for <ssm@ietf.org>; Wed, 21 Apr 2004 16:56:32 +0700
Date: Wed, 21 Apr 2004 19:14:06 +0900
From: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>
To: ssm@ietf.org
Message-Id: <20040421185149.259F.CCVVS@mahidol.ac.th>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.10
Content-Transfer-Encoding: 7bit
Subject: [ssm] Any SSM implementations on PC routers ?
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.2 required=5.0 tests=DEAR_SOMETHING autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear Sir,

	I would like to know whether there is any "open source" 
	for the SSM implementation ?
	I mean the routing daemon, not the IGMPv3 nor the MLDv2.

	As far as I know, Cisco and Juniper routers can support 
	SSM routing, but I haven't heard of the free software running on
	PC routers such as on the *BSD or the Linux.

Thank you very much in advance.

Sincerely Yours,
Vasaka

--------------------------------------------------------
Vasaka Visoottiviseth
Computer Science Department, Faculty of Science
Mahidol University, Thailand
http://www.sc.mahidol.ac.th/sccs/
-------------------------------------------------------


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Wed Apr 21 06:55:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10735
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 06:55:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFGw-00005V-JX; Wed, 21 Apr 2004 06:48:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGF9r-0005tU-Sq
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 06:40:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09814
	for <ssm@ietf.org>; Wed, 21 Apr 2004 06:40:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGF9n-0003s7-MD
	for ssm@ietf.org; Wed, 21 Apr 2004 06:40:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGF8q-0003jx-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:39:45 -0400
Received: from galilei.v6.hitachi.co.jp ([133.145.167.4] helo=v6.hitachi.co.jp)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGF7s-0003Zr-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:38:45 -0400
Received: from s30.uki-uki.net (galilei.v6.hitachi.co.jp [IPv6:2001:200:165::1])
	by v6.hitachi.co.jp (8.12.11/8.11.6) with ESMTP id i3LAcdnt011711;
	Wed, 21 Apr 2004 19:38:39 +0900 (JST)
	(envelope-from suz@crl.hitachi.co.jp)
Date: Wed, 21 Apr 2004 19:38:37 +0900
Message-ID: <x7wu49sjiq.wl%suz@crl.hitachi.co.jp>
From: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>
To: ccvvs@mucc.mahidol.ac.th
Cc: ssm@ietf.org
Subject: Re: [ssm] Any SSM implementations on PC routers ?
X-cite: xcite 1.33
In-Reply-To: <20040421185149.259F.CCVVS@mahidol.ac.th>
References: <20040421185149.259F.CCVVS@mahidol.ac.th>
User-Agent: User-Agent: Wanderlust/2.11.26 (Wonderwall) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Network Systems Research Dept., Central Research Laboratory, Hitachi, Ltd, Japan
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>

>>>>> On Wed, 21 Apr 2004 19:14:06 +0900
>>>>> ccvvs@mucc.mahidol.ac.th(Vasaka Visoottiviseth)  said:

> 	I would like to know whether there is any "open source" 
> 	for the SSM implementation ?
> 	I mean the routing daemon, not the IGMPv3 nor the MLDv2.
>
> 	As far as I know, Cisco and Juniper routers can support SSM
> 	routing, but I haven't heard of the free software running on
> 	PC routers such as on the *BSD or the Linux.

KAME-SNAP contains SSM-ready IPv6 PIM-SM daemon "pim6sd" (also
included in freebsd-ports).

Please see
	http://www.kame.net/
for further detail.

Thanks,
----
SUZUKI, Shinsuke @ Hitachi / KAME Project

 

	

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Wed Apr 21 07:02:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11522
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 07:02:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFTt-0004rH-It
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 07:01:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LB1TJk018671
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 07:01:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFPH-0003HS-Hs
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 06:56:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10810
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 06:56:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGFPD-0005vl-EB
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:56:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGFOE-0005lQ-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:55:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGFNH-0005cw-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 06:54:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFGw-00005V-JX; Wed, 21 Apr 2004 06:48:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGF9r-0005tU-Sq
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 06:40:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09814
	for <ssm@ietf.org>; Wed, 21 Apr 2004 06:40:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGF9n-0003s7-MD
	for ssm@ietf.org; Wed, 21 Apr 2004 06:40:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGF8q-0003jx-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:39:45 -0400
Received: from galilei.v6.hitachi.co.jp ([133.145.167.4] helo=v6.hitachi.co.jp)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGF7s-0003Zr-00
	for ssm@ietf.org; Wed, 21 Apr 2004 06:38:45 -0400
Received: from s30.uki-uki.net (galilei.v6.hitachi.co.jp [IPv6:2001:200:165::1])
	by v6.hitachi.co.jp (8.12.11/8.11.6) with ESMTP id i3LAcdnt011711;
	Wed, 21 Apr 2004 19:38:39 +0900 (JST)
	(envelope-from suz@crl.hitachi.co.jp)
Date: Wed, 21 Apr 2004 19:38:37 +0900
Message-ID: <x7wu49sjiq.wl%suz@crl.hitachi.co.jp>
From: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>
To: ccvvs@mucc.mahidol.ac.th
Cc: ssm@ietf.org
Subject: Re: [ssm] Any SSM implementations on PC routers ?
X-cite: xcite 1.33
In-Reply-To: <20040421185149.259F.CCVVS@mahidol.ac.th>
References: <20040421185149.259F.CCVVS@mahidol.ac.th>
User-Agent: User-Agent: Wanderlust/2.11.26 (Wonderwall) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Network Systems Research Dept., Central Research Laboratory, Hitachi, Ltd, Japan
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>>>>> On Wed, 21 Apr 2004 19:14:06 +0900
>>>>> ccvvs@mucc.mahidol.ac.th(Vasaka Visoottiviseth)  said:

> 	I would like to know whether there is any "open source" 
> 	for the SSM implementation ?
> 	I mean the routing daemon, not the IGMPv3 nor the MLDv2.
>
> 	As far as I know, Cisco and Juniper routers can support SSM
> 	routing, but I haven't heard of the free software running on
> 	PC routers such as on the *BSD or the Linux.

KAME-SNAP contains SSM-ready IPv6 PIM-SM daemon "pim6sd" (also
included in freebsd-ports).

Please see
	http://www.kame.net/
for further detail.

Thanks,
----
SUZUKI, Shinsuke @ Hitachi / KAME Project

 

	

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Wed Apr 21 07:28:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12782
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 07:28:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFoj-0004PJ-CE; Wed, 21 Apr 2004 07:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFhj-0001rh-FW
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:15:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12170
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:15:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGFhi-0000vK-VS
	for ssm@ietf.org; Wed, 21 Apr 2004 07:15:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGFgi-0000lp-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:14:45 -0400
Received: from astrolabe.info.ucl.ac.be ([130.104.229.109] helo=info.ucl.ac.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGFfo-0000eV-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:13:48 -0400
Received: from bush.info.ucl.ac.be (freebsd3 [130.104.230.60])
	by info.ucl.ac.be (8.12.11/8.12.11) with ESMTP id i3LBDYiD021824;
	Wed, 21 Apr 2004 13:13:36 +0200 (MET DST)
Subject: Re: [ssm] Any SSM implementations on PC routers ?
From: Xavier Brouckaert <xbr@info.ucl.ac.be>
To: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>
Cc: ssm@ietf.org
In-Reply-To: <20040421185149.259F.CCVVS@mahidol.ac.th>
References: <20040421185149.259F.CCVVS@mahidol.ac.th>
Content-Type: text/plain
Organization: UCL
Message-Id: <1082545952.27642.29.camel@bush>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Wed, 21 Apr 2004 13:12:32 +0200
Content-Transfer-Encoding: 7bit
X-INGI-MailScanner-Information: Please contact the ISP for more information
X-INGI-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear Vasaka,

It is on the roadmap of the XORP project.
See http://www.xorp.org/ and
http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
However, AFAIK, nobody has taken care of implementing the ipv6 multicast
routing component in the linux kernel.
>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
multicast routing."

Regards,
Xavier


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Wed Apr 21 07:38:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13176
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 07:38:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGG0R-00087b-I3
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 07:35:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LBZ7Ym031205
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 07:35:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFvN-0006mr-Kv
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 07:29:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12843
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 07:29:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGFvN-0002oH-1m
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 07:29:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGFuQ-0002gG-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 07:28:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGFtW-0002YZ-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 07:27:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFoj-0004PJ-CE; Wed, 21 Apr 2004 07:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGFhj-0001rh-FW
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:15:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12170
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:15:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGFhi-0000vK-VS
	for ssm@ietf.org; Wed, 21 Apr 2004 07:15:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGFgi-0000lp-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:14:45 -0400
Received: from astrolabe.info.ucl.ac.be ([130.104.229.109] helo=info.ucl.ac.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGFfo-0000eV-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:13:48 -0400
Received: from bush.info.ucl.ac.be (freebsd3 [130.104.230.60])
	by info.ucl.ac.be (8.12.11/8.12.11) with ESMTP id i3LBDYiD021824;
	Wed, 21 Apr 2004 13:13:36 +0200 (MET DST)
Subject: Re: [ssm] Any SSM implementations on PC routers ?
From: Xavier Brouckaert <xbr@info.ucl.ac.be>
To: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>
Cc: ssm@ietf.org
In-Reply-To: <20040421185149.259F.CCVVS@mahidol.ac.th>
References: <20040421185149.259F.CCVVS@mahidol.ac.th>
Content-Type: text/plain
Organization: UCL
Message-Id: <1082545952.27642.29.camel@bush>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Wed, 21 Apr 2004 13:12:32 +0200
Content-Transfer-Encoding: 7bit
X-INGI-MailScanner-Information: Please contact the ISP for more information
X-INGI-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear Vasaka,

It is on the roadmap of the XORP project.
See http://www.xorp.org/ and
http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
However, AFAIK, nobody has taken care of implementing the ipv6 multicast
routing component in the linux kernel.
>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
multicast routing."

Regards,
Xavier


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Wed Apr 21 08:01:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15000
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 08:01:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGEs-0005kx-DA; Wed, 21 Apr 2004 07:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGC0-0004qO-Ek
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:47:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13758
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:47:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGBz-0005H9-I7
	for ssm@ietf.org; Wed, 21 Apr 2004 07:47:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGB6-00056o-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:46:08 -0400
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGAB-0004xa-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:45:11 -0400
Received: from [68.100.124.243] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 2293773; Wed, 21 Apr 2004 07:44:44 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [ssm] Any SSM implementations on PC routers ?
To: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>, ccvvs@mucc.mahidol.ac.th
Cc: ssm@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Wed, 21 Apr 2004 07:44:44 -0400
Message-ID: <web-2293773@multicasttech.com>
In-Reply-To: <x7wu49sjiq.wl%suz@crl.hitachi.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

On Wed, 21 Apr 2004 19:38:37 +0900
 SUZUKI Shinsuke <suz@crl.hitachi.co.jp> wrote:
> >>>>> On Wed, 21 Apr 2004 19:14:06 +0900
> >>>>> ccvvs@mucc.mahidol.ac.th(Vasaka Visoottiviseth)  said:
> 
> > 	I would like to know whether there is any "open source" 
> > 	for the SSM implementation ?
> > 	I mean the routing daemon, not the IGMPv3 nor the MLDv2.
> >

Every PIM-SM implementation supports PIM-SSM. It's the same
routing protocol; all you need is to turn off (filter)
RP traffic for any SSM channels. Details are in 

http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-v2-new-09.txt

section 4.9.1

Regards
Marshall Eubanks
> > 	As far as I know, Cisco and Juniper routers can support SSM
> > 	routing, but I haven't heard of the free software running on
> > 	PC routers such as on the *BSD or the Linux.
> 
> KAME-SNAP contains SSM-ready IPv6 PIM-SM daemon "pim6sd" (also
> included in freebsd-ports).
> 
> Please see
> 	http://www.kame.net/
> for further detail.
> 
> Thanks,
> ----
> SUZUKI, Shinsuke @ Hitachi / KAME Project
> 
>  
> 
> 	
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From ssm-admin@ietf.org  Wed Apr 21 08:10:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15441
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 08:10:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGRR-0001aq-Mw; Wed, 21 Apr 2004 08:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGMP-0007kK-LY
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:57:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14307
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:57:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGMO-0006wd-Mm
	for ssm@ietf.org; Wed, 21 Apr 2004 07:57:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGKR-0006Ua-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:55:47 -0400
Received: from aardvark.cs.ucl.ac.uk ([128.16.11.150])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGJU-0006Lf-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:54:49 -0400
Received: from aardvark.cs.ucl.ac.uk (localhost [127.0.0.1])
	by aardvark.cs.ucl.ac.uk (8.12.9p2/8.12.8) with ESMTP id i3LBskxF046576;
	Wed, 21 Apr 2004 12:54:46 +0100 (BST)
	(envelope-from mjh@aardvark.cs.ucl.ac.uk)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: Xavier Brouckaert <xbr@info.ucl.ac.be>
cc: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>, ssm@ietf.org,
        pavlin@icir.org
Subject: Re: [ssm] Any SSM implementations on PC routers ? 
In-reply-to: Your message of "Wed, 21 Apr 2004 13:12:32 +0200."
             <1082545952.27642.29.camel@bush> 
Date: Wed, 21 Apr 2004 12:54:46 +0100
Message-ID: <46575.1082548486@aardvark.cs.ucl.ac.uk>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>


>It is on the roadmap of the XORP project.
>See http://www.xorp.org/ and
>http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
>However, AFAIK, nobody has taken care of implementing the ipv6 multicast
>routing component in the linux kernel.
>>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
>multicast routing."

XORP itself provides PIM-SM using IPv4 or IPv6.  But obviously you
need to run XORP on an OS with a forwarding path that has appropriate
support.

If you need PIM-SM using IPv6, right now the best bet is probably to
use FreeBSD 4.9 (or FreeBSD 5.x, but 4.9 is probably preferable).  The
kernel changes needed for efficient PIM usage are already included in
FreeBSD.  Probably best to wait for the XORP 1.0 release due out
shortly though, or at least run the latest CVS snapshot.

The remaining issue would be if you need to use this as an SSM edge
router, because then you'll need IGMPv3/MLDv2 router support to allow
local hosts to join.  Currently we only have IGMPv2 and MLDv1 router
support in XORP.  IGMPv3/MLDv2 is on the roadmap for later this year.

Pavlin Radoslavov is the XORP multicast guru.  He'll no doubt correct
me if I got anything wrong.

Cheers,
	Mark

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Wed Apr 21 08:11:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15514
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 08:11:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGSM-000244-7C
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 08:03:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LC3wjB007931
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 08:03:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGRJ-0001OP-4S
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 08:02:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15076
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 08:02:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGRI-00004J-6R
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:02:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGQM-0007j4-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:01:55 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGPa-0007bN-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:01:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGEs-0005kx-DA; Wed, 21 Apr 2004 07:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGC0-0004qO-Ek
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:47:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13758
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:47:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGBz-0005H9-I7
	for ssm@ietf.org; Wed, 21 Apr 2004 07:47:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGB6-00056o-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:46:08 -0400
Received: from lennon.multicasttech.com
	([63.105.122.7] helo=multicasttech.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGAB-0004xa-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:45:11 -0400
Received: from [68.100.124.243] (account <marshall_eubanks@multicasttech.com>)
  by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
  with HTTP id 2293773; Wed, 21 Apr 2004 07:44:44 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [ssm] Any SSM implementations on PC routers ?
To: SUZUKI Shinsuke <suz@crl.hitachi.co.jp>, ccvvs@mucc.mahidol.ac.th
Cc: ssm@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Wed, 21 Apr 2004 07:44:44 -0400
Message-ID: <web-2293773@multicasttech.com>
In-Reply-To: <x7wu49sjiq.wl%suz@crl.hitachi.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

On Wed, 21 Apr 2004 19:38:37 +0900
 SUZUKI Shinsuke <suz@crl.hitachi.co.jp> wrote:
> >>>>> On Wed, 21 Apr 2004 19:14:06 +0900
> >>>>> ccvvs@mucc.mahidol.ac.th(Vasaka Visoottiviseth)  said:
> 
> > 	I would like to know whether there is any "open source" 
> > 	for the SSM implementation ?
> > 	I mean the routing daemon, not the IGMPv3 nor the MLDv2.
> >

Every PIM-SM implementation supports PIM-SSM. It's the same
routing protocol; all you need is to turn off (filter)
RP traffic for any SSM channels. Details are in 

http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-v2-new-09.txt

section 4.9.1

Regards
Marshall Eubanks
> > 	As far as I know, Cisco and Juniper routers can support SSM
> > 	routing, but I haven't heard of the free software running on
> > 	PC routers such as on the *BSD or the Linux.
> 
> KAME-SNAP contains SSM-ready IPv6 PIM-SM daemon "pim6sd" (also
> included in freebsd-ports).
> 
> Please see
> 	http://www.kame.net/
> for further detail.
> 
> Thanks,
> ----
> SUZUKI, Shinsuke @ Hitachi / KAME Project
> 
>  
> 
> 	
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From exim@www1.ietf.org  Wed Apr 21 08:22:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16357
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 08:22:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGdj-0006Xm-9Q
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 08:15:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LCFhJE025149
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 08:15:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGaP-0005X1-Mx
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 08:12:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15591
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 08:12:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGaO-0001We-Oq
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:12:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGZW-0001K9-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:11:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGY6-00019v-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 08:09:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGRR-0001aq-Mw; Wed, 21 Apr 2004 08:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGGMP-0007kK-LY
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 07:57:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14307
	for <ssm@ietf.org>; Wed, 21 Apr 2004 07:57:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGGMO-0006wd-Mm
	for ssm@ietf.org; Wed, 21 Apr 2004 07:57:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGGKR-0006Ua-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:55:47 -0400
Received: from aardvark.cs.ucl.ac.uk ([128.16.11.150])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGGJU-0006Lf-00
	for ssm@ietf.org; Wed, 21 Apr 2004 07:54:49 -0400
Received: from aardvark.cs.ucl.ac.uk (localhost [127.0.0.1])
	by aardvark.cs.ucl.ac.uk (8.12.9p2/8.12.8) with ESMTP id i3LBskxF046576;
	Wed, 21 Apr 2004 12:54:46 +0100 (BST)
	(envelope-from mjh@aardvark.cs.ucl.ac.uk)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: Xavier Brouckaert <xbr@info.ucl.ac.be>
cc: Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>, ssm@ietf.org,
        pavlin@icir.org
Subject: Re: [ssm] Any SSM implementations on PC routers ? 
In-reply-to: Your message of "Wed, 21 Apr 2004 13:12:32 +0200."
             <1082545952.27642.29.camel@bush> 
Date: Wed, 21 Apr 2004 12:54:46 +0100
Message-ID: <46575.1082548486@aardvark.cs.ucl.ac.uk>
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


>It is on the roadmap of the XORP project.
>See http://www.xorp.org/ and
>http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
>However, AFAIK, nobody has taken care of implementing the ipv6 multicast
>routing component in the linux kernel.
>>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
>multicast routing."

XORP itself provides PIM-SM using IPv4 or IPv6.  But obviously you
need to run XORP on an OS with a forwarding path that has appropriate
support.

If you need PIM-SM using IPv6, right now the best bet is probably to
use FreeBSD 4.9 (or FreeBSD 5.x, but 4.9 is probably preferable).  The
kernel changes needed for efficient PIM usage are already included in
FreeBSD.  Probably best to wait for the XORP 1.0 release due out
shortly though, or at least run the latest CVS snapshot.

The remaining issue would be if you need to use this as an SSM edge
router, because then you'll need IGMPv3/MLDv2 router support to allow
local hosts to join.  Currently we only have IGMPv2 and MLDv1 router
support in XORP.  IGMPv3/MLDv2 is on the roadmap for later this year.

Pavlin Radoslavov is the XORP multicast guru.  He'll no doubt correct
me if I got anything wrong.

Cheers,
	Mark

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



From ssm-admin@ietf.org  Wed Apr 21 17:12:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14755
	for <ssm-archive@lists.ietf.org>; Wed, 21 Apr 2004 17:12:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOaJ-0003cO-8y; Wed, 21 Apr 2004 16:44:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGM4z-00035K-IW
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 14:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05369
	for <ssm@ietf.org>; Wed, 21 Apr 2004 14:04:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGM4x-0005HO-7R
	for ssm@ietf.org; Wed, 21 Apr 2004 14:04:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGM40-00055t-00
	for ssm@ietf.org; Wed, 21 Apr 2004 14:03:13 -0400
Received: from possum.icir.org ([192.150.187.67])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGM30-0004rs-00
	for ssm@ietf.org; Wed, 21 Apr 2004 14:02:11 -0400
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.12.9p1/8.12.8) with ESMTP id i3LI20r6060522;
	Wed, 21 Apr 2004 11:02:00 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200404211802.i3LI20r6060522@possum.icir.org>
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
cc: Xavier Brouckaert <xbr@info.ucl.ac.be>,
        Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>, ssm@ietf.org,
        pavlin@icir.org
Subject: Re: [ssm] Any SSM implementations on PC routers ? 
In-Reply-To: Message from Mark Handley <M.Handley@cs.ucl.ac.uk> 
   of "Wed, 21 Apr 2004 12:54:46 BST." <46575.1082548486@aardvark.cs.ucl.ac.uk> 
Date: Wed, 21 Apr 2004 11:02:00 -0700
From: Pavlin Radoslavov <pavlin@icir.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>

> >It is on the roadmap of the XORP project.
> >See http://www.xorp.org/ and
> >http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
> >However, AFAIK, nobody has taken care of implementing the ipv6 multicast
> >routing component in the linux kernel.
> >>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
> >multicast routing."
> 
> XORP itself provides PIM-SM using IPv4 or IPv6.  But obviously you
> need to run XORP on an OS with a forwarding path that has appropriate
> support.
> 
> If you need PIM-SM using IPv6, right now the best bet is probably to
> use FreeBSD 4.9 (or FreeBSD 5.x, but 4.9 is probably preferable).  The
> kernel changes needed for efficient PIM usage are already included in
> FreeBSD.  Probably best to wait for the XORP 1.0 release due out
> shortly though, or at least run the latest CVS snapshot.
> 
> The remaining issue would be if you need to use this as an SSM edge
> router, because then you'll need IGMPv3/MLDv2 router support to allow
> local hosts to join.  Currently we only have IGMPv2 and MLDv1 router
> support in XORP.  IGMPv3/MLDv2 is on the roadmap for later this year.
> 
> Pavlin Radoslavov is the XORP multicast guru.  He'll no doubt correct
> me if I got anything wrong.

Everything is correct with a small clarification.
If you need PIM-SM for IPv4, then you have to run FreeBSD-4.9 or 5.1
(or later).
If you need PIM-SM for IPv6, then older versions of FreeBSD with
KAME's IPv6 support should be fine too.

Pavlin

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


From exim@www1.ietf.org  Wed Apr 21 18:32:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25302
	for <ssm-archive@odin.ietf.org>; Wed, 21 Apr 2004 18:32:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGQ2K-0004C3-AP
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 18:17:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i3LMHiVd016118
	for ssm-archive@odin.ietf.org; Wed, 21 Apr 2004 18:17:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGPAd-0004e7-2Q
	for ssm-web-archive@optimus.ietf.org; Wed, 21 Apr 2004 17:22:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15358
	for <ssm-web-archive@ietf.org>; Wed, 21 Apr 2004 17:22:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGPAa-0001UF-Pq
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 17:22:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGP7k-0000fH-00
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 17:19:17 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGP6W-0000JF-02
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 17:18:00 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BGP0g-0007r7-QO
	for ssm-web-archive@ietf.org; Wed, 21 Apr 2004 17:11:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGOaJ-0003cO-8y; Wed, 21 Apr 2004 16:44:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BGM4z-00035K-IW
	for ssm@optimus.ietf.org; Wed, 21 Apr 2004 14:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05369
	for <ssm@ietf.org>; Wed, 21 Apr 2004 14:04:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BGM4x-0005HO-7R
	for ssm@ietf.org; Wed, 21 Apr 2004 14:04:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BGM40-00055t-00
	for ssm@ietf.org; Wed, 21 Apr 2004 14:03:13 -0400
Received: from possum.icir.org ([192.150.187.67])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BGM30-0004rs-00
	for ssm@ietf.org; Wed, 21 Apr 2004 14:02:11 -0400
Received: from possum.icir.org (localhost [127.0.0.1])
	by possum.icir.org (8.12.9p1/8.12.8) with ESMTP id i3LI20r6060522;
	Wed, 21 Apr 2004 11:02:00 -0700 (PDT)
	(envelope-from pavlin@possum.icir.org)
Message-Id: <200404211802.i3LI20r6060522@possum.icir.org>
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
cc: Xavier Brouckaert <xbr@info.ucl.ac.be>,
        Vasaka Visoottiviseth <ccvvs@mucc.mahidol.ac.th>, ssm@ietf.org,
        pavlin@icir.org
Subject: Re: [ssm] Any SSM implementations on PC routers ? 
In-Reply-To: Message from Mark Handley <M.Handley@cs.ucl.ac.uk> 
   of "Wed, 21 Apr 2004 12:54:46 BST." <46575.1082548486@aardvark.cs.ucl.ac.uk> 
Date: Wed, 21 Apr 2004 11:02:00 -0700
From: Pavlin Radoslavov <pavlin@icir.org>
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
	<mailto:ssm-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

> >It is on the roadmap of the XORP project.
> >See http://www.xorp.org/ and
> >http://www.xorp.org/releases/0.1/docs/design_arch/design_arch.pdf
> >However, AFAIK, nobody has taken care of implementing the ipv6 multicast
> >routing component in the linux kernel.
> >>From xorp/pim/README : "Note that currently Linux doesn't support IPv6
> >multicast routing."
> 
> XORP itself provides PIM-SM using IPv4 or IPv6.  But obviously you
> need to run XORP on an OS with a forwarding path that has appropriate
> support.
> 
> If you need PIM-SM using IPv6, right now the best bet is probably to
> use FreeBSD 4.9 (or FreeBSD 5.x, but 4.9 is probably preferable).  The
> kernel changes needed for efficient PIM usage are already included in
> FreeBSD.  Probably best to wait for the XORP 1.0 release due out
> shortly though, or at least run the latest CVS snapshot.
> 
> The remaining issue would be if you need to use this as an SSM edge
> router, because then you'll need IGMPv3/MLDv2 router support to allow
> local hosts to join.  Currently we only have IGMPv2 and MLDv1 router
> support in XORP.  IGMPv3/MLDv2 is on the roadmap for later this year.
> 
> Pavlin Radoslavov is the XORP multicast guru.  He'll no doubt correct
> me if I got anything wrong.

Everything is correct with a small clarification.
If you need PIM-SM for IPv4, then you have to run FreeBSD-4.9 or 5.1
(or later).
If you need PIM-SM for IPv6, then older versions of FreeBSD with
KAME's IPv6 support should be fine too.

Pavlin

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm



