[IPsec] Issue #2: Where does N(SET_WINDOW_SIZE) go?

2009-04-03 Thread Tero Kivinen
Yaron Sheffer writes: > >From Appendix C: The specification does not say which messages can contain > N(SET_WINDOW_SIZE). It can possibly be included in any message, but it is > not yet shown below. > > SF discussion: Paul said, "wherever you wish." I agree on that. Logical places are: 1) In sep

[IPsec] Issue #63: Position of arbitrary notify payloads

2009-04-03 Thread Tero Kivinen
Yaron Sheffer writes: > Yaron: > > Appendix C: please also mention extension notifications [N+], other than in > C.6. > > Paul: > > Maybe copy it everywhere like we have [V+] That is ok for me. Btw, is there any reason why [V+] is not listed in the IKE_AUTH excghange with EAP in the intermedia

[IPsec] Issue #53: Handling of INITIAL_CONTACT

2009-04-03 Thread Tero Kivinen
Yaron Sheffer writes: > Yaron: > > 2.4: Clarif-7.9 is unclear: [this MUST be sent in the first IKE_AUTH > request.] 'however, receiving parties need to deal with it in other > requests' - what requests? How? Why should it ever happen? > > SF discussion: > > David Black: if you put initial_contac

Re: [IPsec] Issue #2: Where does N(SET_WINDOW_SIZE) go?

2009-04-03 Thread Tero Kivinen
Scott C Moonen writes: > > From Appendix C: The specification does not say which messages can > contain N(SET_WINDOW_SIZE). It can possibly be included in any message, > but it is not yet shown below. > > > > SF discussion: Paul said, $,1r|(Bwherever you wish.$,1r} (B> > Should we prohibit