Re: [Hipsec] Base draft & ESP draft: snapshots

Pekka Nikander <pekka.nikander@nomadiclab.com> Thu, 18 August 2005 13:12 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E5kBg-000549-31; Thu, 18 Aug 2005 09:12:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E5kBZ-00053r-V3 for hipsec@megatron.ietf.org; Thu, 18 Aug 2005 09:11:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03123 for <hipsec@ietf.org>; Thu, 18 Aug 2005 09:11:56 -0400 (EDT)
Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E5klK-0008QW-Ky for hipsec@ietf.org; Thu, 18 Aug 2005 09:48:55 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id AC1AF212C91; Thu, 18 Aug 2005 16:11:48 +0300 (EEST)
In-Reply-To: <1124370248.8997.15.camel@localhost.localdomain>
References: <1124111403.10041.10.camel@localhost.localdomain> <E813B992-7307-471F-B070-664E0774C770@nomadiclab.com> <1124370248.8997.15.camel@localhost.localdomain>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <942EE334-6314-4626-83F0-B277EF0DE97A@nomadiclab.com>
Content-Transfer-Encoding: 7bit
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [Hipsec] Base draft & ESP draft: snapshots
Date: Thu, 18 Aug 2005 15:11:45 +0200
To: Petri Jokela <petri.jokela@nomadiclab.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: hipsec@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>
Sender: hipsec-bounces@lists.ietf.org
Errors-To: hipsec-bounces@lists.ietf.org

>> There appears to be a minor problem between 6.13 and 6.14.  6.13 says
>> that CLOSE may be answered with an ICMP, 6.14 that they are dropped.
>>
>
> Actually, there is a whole section "5.4.4  Non-existing HIP  
> Association"
> that discusses about responding to CLOSE and NOTIFY messages with an
> ICMP if we do not have any state with that peer. In Paris, I think we
> agreed that we are not going to respond to an incoming CLOSE with any
> message. Should we ignore also incoming NOTIFYs if there is no
> association? Is there any reason why we would like to answer to  
> NOTIFYs
> in UNASSOCIATED state?

Good question.  I don't have any strong opinion; I'm just worried about
us not being consistent.

>> Need to specify "LSI" briefly in Section 2 as it is used in 6.1
>>
>
> Should we remove all text related to LSIs, and concentrate only on  
> HITs
> in this draft? All LSI related stuff would be in
> draft-henderson-hip-applications.

Either way works for me.  I'd slightly prefer rewriting 6.1. and
6.2 so that they don't refer to LSIs as all, because IMHO those
two sections should be completely rewritten anyway.   They are
currently crumby, as a remaining issue resulting from the document
split.

--Pekka


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