Re: issue 12: interaction with other protocols doing RR

We have gotten less input on this issue than on
others, but the way that I read this is the
following:

(1) We have a basic agreement that we define
     what MOBIKE RR provides, and if other
     protocols are happy with that then they
     can use it without doing their own.

(2) THere was a discussion if this works the
     other way around, i.e., from another protocol
     to MOBIKE. Tero argued for this and Pasi
     presented a counter argument. I think the
     counter argument made sense, and since Tero
     was silent I'm going to assume you were OK
     with it too.

(3) Atul suggested that APIs be worked on. We
     at the IETF are typically not chartered to
     work on APIs; I'm sure you see obvious ways
     of doing this in your implementation, however.
     But in MOBIKE, we are chartered to actually work
     on one API, the PFKEY API. It may be that
     this would be a part of the that work, or maybe
     not -- time will tell. But its clear that it
     is not a requirement for the protocol work to
     proceed. So we'll remember this when and if we
     get to the PFKEY part. (Folks: we need to produce
     are base spec before we get any further!)

In conclusion I think we can close this one too.

--Jari