Issue 30: Protocol ID in notifications

[email protected] writes:
> > 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..

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. 
-- 
[email protected]