[ssm] Re: a few ssm comments (fwd)

Leonard Giuliano <lenny@juniper.net> Thu, 16 January 2003 14:43 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12502 for <ssm-archive@lists.ietf.org>; Thu, 16 Jan 2003 09:43:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEwYJ27371; Thu, 16 Jan 2003 09:58:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GEpYJ27127 for <ssm@optimus.ietf.org>; Thu, 16 Jan 2003 09:51:34 -0500
Received: from merlot.juniper.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12334 for <ssm@ietf.org>; Thu, 16 Jan 2003 09:35:54 -0500 (EST)
Received: from maroon.jnpr.net (maroon.jnpr.net [172.24.244.36]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h0GEd9S04116; Thu, 16 Jan 2003 06:39:09 -0800 (PST) (envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost) by maroon.jnpr.net (8.11.6/8.11.3) with ESMTP id h0GEd8j90595; Thu, 16 Jan 2003 06:39:09 -0800 (PST) (envelope-from lenny@juniper.net)
X-Authentication-Warning: maroon.jnpr.net: lenny owned process doing -bs
Date: Thu, 16 Jan 2003 06:39:08 -0800
From: Leonard Giuliano <lenny@juniper.net>
X-X-Sender: <lenny@maroon.jnpr.net>
To: ssm@ietf.org
cc: pekkas@netcore.fi
Message-ID: <20030116063737.E89747-100000@maroon.jnpr.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [ssm] Re: a few ssm comments (fwd)
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 Tue, 17 Dec 2002 pekkas@netcore.fi wrote:

-)
-) Hello,
-)
-) I quickly read the two SSM drafts properly for the first time.  A few
-) minor comments.
-)
-) ssm-overview-04:
-)
-)                                                                    Thus
-)       the complexity of the multicast routing infrastructure for SSM is
-)       low, making it viable for immediate deployment. Note that MBGP is
-)       still required for distribution of multicast reachability
-)       information.
-)
-) ==> I would dispute the last sentence a bit.  It's not really necessary to
-) use MBGP at all if you're using PIM.
-)

Agreed, you don't NEED MBGP for PIM to work.  I think the point trying to
be made here is that SSM is no different than ASM when it comes to MBGP,
but the way it is currently worded doesn't make that clear.  Perhaps the
following wording might be better:

"Note that the necessity for MBGP in SSM is no different than in ASM.
That is, when topology incongruity or a separate M-RIB for RPF is desired,
MBGP can be used."


-Lenny



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