IETF Logo Mail Archive

Re: Re: Re: [ssm] SSM with IPSec

Toerless Eckert <eckert@cisco.com> Wed, 15 January 2003 22:15 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 RAA11894 for <ssm-archive@lists.ietf.org>; Wed, 15 Jan 2003 17:15:20 -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 h0FMTpJ14825; Wed, 15 Jan 2003 17:29:51 -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 h0FMKOJ14252 for <ssm@optimus.ietf.org>; Wed, 15 Jan 2003 17:20:24 -0500
Received: from sj-msg-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11564 for <ssm@ietf.org>; Wed, 15 Jan 2003 17:05:05 -0500 (EST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id h0FM8Sfm017552; Wed, 15 Jan 2003 14:08:28 -0800 (PST)
Received: (from eckert@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id OAA04648; Wed, 15 Jan 2003 14:08:17 -0800 (PST)
Date: Wed, 15 Jan 2003 14:08:17 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mark Baugher <mbaugher@cisco.com>
Cc: holbrook@cisco.com, Toerless Eckert <eckert@cisco.com>, Brad Huntting <huntting@glarp.com>, ssm@ietf.org, Brian Weis <bew@cisco.com>
Subject: Re: Re: Re: [ssm] SSM with IPSec
Message-ID: <20030115220817.GA23021@cypher.cisco.com>
References: <20030115171137.GK2103@cypher.cisco.com> <5.1.1.5.2.20030115123146.021e95a8@mira-sjc5-6.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5.1.1.5.2.20030115123146.021e95a8@mira-sjc5-6.cisco.com>
User-Agent: Mutt/1.4i
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>

Ok, thanks for the insight. One issue is still that the solution
needs to support the two cases:

   - independent security associations for (S1,G) and (S2,G) if
     G is an SSM group, because (S1,G) and (S2,G) don't necessarily
     have a connection.
   - same security association for (S1,G) and (S2,G) if G is an ASM
     group.

Now how to determine what kind of security association is needed, 
i don't know. Probably it would be a good thing if that could be determined
somewhat application specific, but not necessarily requiring the IPsec
framework to know the distinction between ASM/SSM.

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

v2.23.0 | Report a Bug | By Email