IETF Logo Mail Archive

Re: SA identification

Jari Arkko <jari.arkko@kolumbus.fi> Thu, 22 March 2001 17:46 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.9.3/8.9.3) with ESMTP id JAA10671; Thu, 22 Mar 2001 09:46:33 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id LAA13987 Thu, 22 Mar 2001 11:36:30 -0500 (EST)
Message-ID: <3ABA2B9E.6060405@kolumbus.fi>
Date: Thu, 22 Mar 2001 18:43:10 +0200
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17-icclin i686; en-US; m18) Gecko/20001107 Netscape6/6.0
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>
Cc: ipsec@lists.tislabs.com
Subject: Re: SA identification
References: <p05010401b6dfaec6aa35@[128.33.238.44]>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

Stephen Kent wrote:

> Some mobility problems  could be addressed if we ignored destination 
> address.
>  

Also, the configuration of manual SAs to protect v6 control signaling
traffic on e.g. an office WLAN network would be a lot easier if the 
destination
address was ignored [draft-arkko-manual-icmpv6-sas-00.txt].

Multicast is used in that case as well, but in that particular application
coordinating the multicast SPI numbers would be easier than in
the general case of internet TV viewers scattered around the globe.

Jari

v2.23.0 | Report a Bug | By Email