--------------------

Tero Kivinen (2005-07-12):

> 3.1  MOBIKE_SUPPORTED notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

> 3.2  ADDITIONAL_ADDRESS notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

> 3.3  CHANGE_PATH notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

> 3.4  UNACCEPTABLE_PATH notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

> 3.5  COOKIE2 notification payload
<snip>
(already changed protocol id to zero).

> 3.6  NAT_PREVENTION notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

> 3.7  NAT_PREVENTED notification payload
<snip>
Also I think this notify does not relate to existing SA, so the
protocol ID should be 0.

--------------------

Pasi Eronen (2005-07-13):

Hmm... IKEv2 is not very clear on that part. There are some
notifications that are clearly about existing ESP/AH SAs, but in
some sense all the other notifications are (loosely) related to 
the IKE_SA. Draft-eronen-ipsec-ikev2-clarifications-03 also has 
text about this:

> 6.10  Protocol ID/SPI fields in Notify payloads
>
>   Section 3.10 says that the Protocol ID field in Notify
>   payloads "For notifications which do not relate to an
>   existing SA, this field MUST be sent as zero and MUST be
>   ignored on receipt".  However, the specification does not
>   clearly say which notifications are related to existing SAs
>   and which are not.
>
>   Since the main purpose of the Protocol ID field is to
>   specify the type of the SPI, our interpretation is that the
>   Protocol ID field should be non-zero only when the SPI field
>   is non-empty.
>
>   There are currently only two notifications where this is the
>   case: INVALID_SELECTORS and REKEY_SA.

The text above would seem to imply that Protocol ID 1 is never
used in notifications, so MOBIKE should also use ID 0.
This is OK with me..

(Do you agree with the text in the clarifications draft?)

--------------------

Tero Kivinen (2005-07-14):

I do agree on the clarification document text. I.e. the protocol ID is
associated with the SPI field, in a way that it is there only and only
when there is SPI in the SPI field of notification, and it is there to
distinguish from what protocol the SPI in the payload is. 

--------------------

Pasi Eronen (2005-07-18):

Use protocol ID 0 as proposed by Tero.

--------------------

Issue closed on 2005-07-26.

--------------------