Re: Outbound interface as a selector

Dan McDonald <danmcd@Eng.Sun.Com> Mon, 18 October 1999 19:50 UTC

From: Dan McDonald <danmcd@Eng.Sun.Com>
Message-Id: <199910181508.IAA00759@kebe.Eng.Sun.COM>
Subject: Re: Outbound interface as a selector
To: kent@bbn.com
Date: Mon, 18 Oct 1999 08:08:26 -0700
Cc: ipsec@lists.tislabs.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

Forwarded message:
From MAILER-DAEMON  Mon Oct 18 08:07:29 1999
Delivery-Date: Mon, 18 Oct 1999 08:07:29 -0700
Date: Mon, 18 Oct 1999 08:07:28 -0700 (PDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@eng.sun.com>
Message-Id: <199910181507.IAA00740@kebe.Eng.Sun.COM>
To: danmcd@kebe.eng.sun.com
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="IAA00740.940259248/kebe.Eng.Sun.COM"
Subject: Returned mail: User unknown
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--IAA00740.940259248/kebe.Eng.Sun.COM

The original message was received at Mon, 18 Oct 1999 08:07:28 -0700 (PDT)
from danmcd@localhost

   ----- The following addresses had permanent fatal errors -----
kent@bbn.com
ipsec@lists.tislabs.com

   ----- Transcript of session follows -----
... while talking to opal.eng.sun.com.:
>>> RCPT To:<ipsec@lists.tislabs.com>
<<< 550 5.7.1 <ipsec@lists.tislabs.com>... Relaying denied. IP name possibly forged [2000::56:a00:20ff:fe8f:cf02]
550 ipsec@lists.tislabs.com... User unknown
>>> RCPT To:<kent@bbn.com>
<<< 550 5.7.1 <kent@bbn.com>... Relaying denied. IP name possibly forged [2000::56:a00:20ff:fe8f:cf02]
550 kent@bbn.com... User unknown

--IAA00740.940259248/kebe.Eng.Sun.COM
Content-Type: message/delivery-status

Reporting-MTA: dns; kebe.Eng.Sun.COM
Arrival-Date: Mon, 18 Oct 1999 08:07:28 -0700 (PDT)

Final-Recipient: RFC822; kent@bbn.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; opal.eng.sun.com
Diagnostic-Code: SMTP; 550 5.7.1 <kent@bbn.com>... Relaying denied. IP name possibly forged [2000::56:a00:20ff:fe8f:cf02]
Last-Attempt-Date: Mon, 18 Oct 1999 08:07:28 -0700 (PDT)

Final-Recipient: RFC822; ipsec@lists.tislabs.com
Action: failed
Status: 5.1.1
Remote-MTA: DNS; opal.eng.sun.com
Diagnostic-Code: SMTP; 550 5.7.1 <ipsec@lists.tislabs.com>... Relaying denied. IP name possibly forged [2000::56:a00:20ff:fe8f:cf02]
Last-Attempt-Date: Mon, 18 Oct 1999 08:07:28 -0700 (PDT)

--IAA00740.940259248/kebe.Eng.Sun.COM
Content-Type: message/rfc822

Return-Path: <danmcd>
Received: (from danmcd@localhost)
	by kebe.Eng.Sun.COM (8.9.3+Sun/8.9.1) id IAA00738;
	Mon, 18 Oct 1999 08:07:28 -0700 (PDT)
From: Dan McDonald <danmcd>
Message-Id: <199910181507.IAA00738@kebe.Eng.Sun.COM>
Subject: Re: Outbound interface as a selector
To: kent@bbn.com
Date: Mon, 18 Oct 1999 08:07:27 -0700 (PDT)
Cc: ipsec@lists.tislabs.com
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

> Absent the use of IPsec, how would a user have selected one interface
> vs. another via the usual OS calls (or why would he care)?

I can select an interface for multicast traffic using sockets today.  IPv6's
advanced API also has additional facilities for this.

If I want to send a packet to ff02::1 or 224.0.0.1, I need to know which
interface I'm sending it out.  If I'm multihomed, I'd like to have two SAs
for destination 224.0.0.1 or ff02::1, where each SA is for an individual
link.

Dan

--IAA00740.940259248/kebe.Eng.Sun.COM--

Re: Outbound interface as a selector Dan McDonald