Subject: [Hipsec] open issues for issue tracker

From: [email-masked] (Henderson, Thomas R)
Date: Fri Apr 30 16:07:00 2004

Catching up on recent mail, it seems like we need a few more issues:

[base]  ICMP error types for problems that occur before cookie is verified (message by PN on 4/27)

[base] UPDATE message handling (Section 8.11) needs some work

[base]  Issue12 could be updated by recent messages by PN (4/10) and myself (yesterday) on the subject.  Birthday seems to only be an R1 counter now, and Pekka suggested on 4/10 that it may be non-critical parameter.  Related to this is processing rules for multiple received R1s (maybe separate issue?-- multiple R1s could be due to sending multiple I1s in parallel-- Section 8.4.1)

[base] are issues 23 (R2-sent state), 33 (new cookie design), 21 (Reject/Notify), and 22 (Remove Resync) is closed state?  Are people happy with the new cookie?  I know that there was some question about the size of K being 24 bits vs. some other size.

Here are some possible ones from Petri too:

> REJECT mechanism (NOTIFY): We should probably define more 
> detailed the 
> data that should be included in the Notification data field 
> with each of 
> the error types.
> 
> New parameters in 6.2, HIP parameters, we have now allocated 
> all values 
> up to 13. Should there be left more space or not? And is the current 
> order of TLVs ok?
> 
> RESYNC mechanism changed.
> 
> Birthday changed.
> 
> Cookie mechanism changed. We have now opaque data in two locations: 
> PUZZLE/SOLUTION and in ECHO_REQ/RESP. Is it necessary to have 
> it in two 
> places?
> 

[mm] address check RR design (raised by JW yesterday and today)

[mm] use of multiple SAs (JW, 4/16 message)

(note-- I have not addressed rendezvous server open issues-- maybe another list?)

Tom