Re: [ssm] Dual homed multicast src and SSM

Beau Williamson <bwilliam@cisco.com> Wed, 13 October 2004 18:33 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22352 for <ssm-archive@lists.ietf.org>; Wed, 13 Oct 2004 14:33:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHnpr-0004Ey-8y; Wed, 13 Oct 2004 14:26:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHnkG-00039Q-5i for ssm@megatron.ietf.org; Wed, 13 Oct 2004 14:21:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21511 for <ssm@ietf.org>; Wed, 13 Oct 2004 14:21:05 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHnvF-0002Ab-Bx for ssm@ietf.org; Wed, 13 Oct 2004 14:32:26 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 13 Oct 2004 11:26:54 -0700
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9DIKPYJ007771; Wed, 13 Oct 2004 11:20:25 -0700 (PDT)
Received: from bwilliam-t30.cisco.com (rtp-vpn3-211.cisco.com [10.82.216.211]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA13198; Wed, 13 Oct 2004 11:20:29 -0700 (PDT)
Message-Id: <6.0.0.22.2.20041013131802.0325ba60@edison.cisco.com>
X-Sender: bwilliam@edison.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 13 Oct 2004 13:20:54 -0500
To: "Field, Brian" <Brian_Field@cable.comcast.com>, ssm@ietf.org
From: Beau Williamson <bwilliam@cisco.com>
Subject: Re: [ssm] Dual homed multicast src and SSM
In-Reply-To: <6FEB46B4943AA348B0776325DA8EC37F02060EC0@entcoexch01.broad band.att.com>
References: <6FEB46B4943AA348B0776325DA8EC37F02060EC0@entcoexch01.broadband.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
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>
Sender: ssm-bounces@ietf.org
Errors-To: ssm-bounces@ietf.org

Brian,

There is nothing specific to SSM that would prevent the trees from being 
setup between one AS and another.  The fact that the source domain is 
dual-homed only means that there are two paths form where Joins can arrive 
(from other domains).  This is of course controlled with normal BGP metrics 
and is no different from hosts in other AS's wishing to "send" unicast 
traffic to the source host.

Beau
At 10/12/2004 06:19 PM, Field, Brian wrote:

>Consider a network operating in SSM and a dual homed multicast src
>device.  Is there a standard way to setup the forwarding between the
>routers and the src device to get the SSM trees built properly?  Seems
>as if the device needs to eiter participate in routing and announce the
>src IP or run something like HSRP.  Issues with these approaches?
>Other options?
>
>Thanks
>Brian
>
>_______________________________________________
>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