comments on draft-ike-mobike-design-03.txt

Hello,

I read draft-ike-mobike-design-03.txt and had a few comments/questions
as below:

Technical Comments:

- Section 4, fourth paragraph, it says "Using this API, the MOBIKE
  daemon can create entries in the Security Association (SAD) and
  Security Policy Databases (SPD)." I believe "this API" refers to
  PF_KEY which is initially designed as an interface to SAD. So, the
  draft should be accurate in this respect, IMHO.
- (In Section 5.1) Is my understanding correct that the three
  alternatives presented here could be exclusively used to indicate
  support for MOBIKE ? Or use of "critical" flag in the payload header
  is encouraged in every attempt of sending MOBIKE specific messages ?
- Section 5.8 (Scope of SA changes), I think this is very important
  issue. Separate management of IKE SA and IPsec SA in terms of address
  update allows us more flexible and (potentially) user-friendly
  operation although there will be more complexity and overhead to
  do so.

Editorial Comments:

- Section 3.1, second paragraph, s/statufu/stateful/
- Page 19, first bullet, last sentence, s/it/is/
- Section 5.6, page 20, second bullet,
  s/in order provide/in order to provide/
- Section 5.6, 3rd paragraph, first sentence,
  s/an IP addressed/an IP address/
- Section 5.6, 3rd paragraph,
  s/weaker guarantees then/weaker guarantees than/
- Section 5.6, 5th paragraph (page 21),
  s/material.A protection/material. A protection/
- Page 22, second bullet, first sentence, unnecessary
  "()" appears.
- Section 5.9, 2nd sentence, s/the it/it/


Regards,
Shinta