Outbound interface as a selector?
Dan McDonald <danmcd@Eng.Sun.Com> Sun, 17 October 1999 22:33 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by mail.imc.org (8.9.3/8.9.3) with ESMTP id PAA07490; Sun, 17 Oct 1999 15:33:47 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id RAA13217 Sun, 17 Oct 1999 17:16:36 -0400 (EDT)
From: Dan McDonald <danmcd@Eng.Sun.Com>
Message-Id: <199910172118.OAA14917@kebe.Eng.Sun.COM>
Subject: Outbound interface as a selector?
To: ipsec@lists.tislabs.com
Date: Sun, 17 Oct 1999 14:18:55 -0700
X-Legal-Disclaimer: Please note that the information being provided does not constitute a warranty or a modification of any agreement you may have with Sun Microsystems, Inc., its subsidiaries or its customers.
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Consider the case of IPv6 link-local multicast. Say I have two multicast SAs for dstaddr == ff02::2 (all-routers mcast). Let's say further that one SA is for one link, and the other SA is for the other link. Unless I hardcode SPIs into the user API (which is a BAD idea), I need to distinguish between the two SAs. The only way I can think of is to use the outgoing interface as a selector for outbound d-grams (and for that matter, inbound d-grams too). Off the top of your heads, do you see anything really broken about the idea of outbound interface as a selector? Dan
- Outbound interface as a selector? Dan McDonald
- Re: Outbound interface as a selector? Angelos D. Keromytis
- Re: Outbound interface as a selector? Henry Spencer
- Re: Outbound interface as a selector? Stephen Kent