RE: [Hipsec] some comments for mm-03

Miika Komu <miika@iki.fi> Sat, 22 April 2006 09:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXEJX-000475-Uo; Sat, 22 Apr 2006 05:22:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FXEJW-00046g-GF for hipsec@lists.ietf.org; Sat, 22 Apr 2006 05:22:02 -0400
Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FXEJU-00048Z-5X for hipsec@lists.ietf.org; Sat, 22 Apr 2006 05:22:02 -0400
Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 4F64531B7; Sat, 22 Apr 2006 12:21:59 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.1.1-niksula20060321 (2006-03-10) on twilight.cs.hut.fi
X-Spam-Level:
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1-niksula20060321
X-Spam-Niksula: No
Received: from kekkonen.cs.hut.fi (kekkonen.cs.hut.fi [130.233.41.50]) by twilight.cs.hut.fi (Postfix) with ESMTP id 9F8DE307A; Sat, 22 Apr 2006 12:21:57 +0300 (EEST)
Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3) with ESMTP id k3M9LuJv014796; Sat, 22 Apr 2006 12:21:57 +0300 (EEST)
X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs
Date: Sat, 22 Apr 2006 12:21:55 +0300
From: Miika Komu <miika@iki.fi>
X-X-Sender: mkomu@kekkonen.cs.hut.fi
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Subject: RE: [Hipsec] some comments for mm-03
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D01A2F09E@XCH-NW-5V1.nw.nos.boeing.com>
Message-ID: <Pine.SOL.4.64.0604221220490.25767@kekkonen.cs.hut.fi>
References: <77F357662F8BFA4CA7074B0410171B6D01A2F09E@XCH-NW-5V1.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: hipsec@lists.ietf.org
X-BeenThere: hipsec@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@lists.ietf.org>
List-Help: <mailto:hipsec-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=subscribe>
Errors-To: hipsec-bounces@lists.ietf.org

On Fri, 21 Apr 2006, Henderson, Thomas R wrote:

>> -----Original Message-----
>> From: Miika Komu [mailto:miika@iki.fi]
>> Sent: Monday, April 17, 2006 12:17 PM
>> To: Henderson, Thomas R
>> Cc: hipsec@lists.ietf.org
>> Subject: RE: [Hipsec] some comments for mm-03
>>
>>>>> Figure 12
>>>>
>>>> This figure reminds me that is it possible to have both
>> SPI1 and SPI2
>>>> mapping to the same ADDR21?
>>>
>>> Yes, in general, there may be different source addresses and hence
>>> different paths to the same destination address.
>>
>> Maybe this could be also mentioned briefly in the text. It is
>> not obvious
>> from figure or text.
>
> I have looked at this and am not sure whether there is an easy way to
> add this without complicating the description more than necessary-- I
> would be willing to consider a specific proposal, though.

I think this is notified in the text already:

   An address may appear on more than one SPI.  This creates no ambiguity
   since the receiver will ignore the IP addresses during SA lookup anyway.
   However, this document does not specify such cases.

This text is fine.

-- 
Miika Komu              miika@iki.fi          http://www.iki.fi/miika/

_______________________________________________
Hipsec mailing list
Hipsec@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hipsec