Re: [IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis

2011-03-13 Thread Qin Wu
" To: ; Sent: Sunday, March 06, 2011 5:25 PM Subject: [IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis > Hi all > > I have just read the subject draft, and found this in section 6 (and similar > text in the introduction): > > Note that to support ERP, lower-layer s

Re: [IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis

2011-03-07 Thread Yoav Nir
On Mar 7, 2011, at 5:58 PM, Tero Kivinen wrote: > Yoav Nir writes: >> A bigger problem is that this text says that IKEv2 needs to be >> updated, but there is no draft for this update, nor has there been >> any message to this list about this proposed change. >> >> The simple change they requir

[IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis

2011-03-07 Thread Tero Kivinen
Yoav Nir writes: > A bigger problem is that this text says that IKEv2 needs to be > updated, but there is no draft for this update, nor has there been > any message to this list about this proposed change. > > The simple change they require is to section 3.16: >o Code (1 octet) indicates wh

Re: [IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis

2011-03-06 Thread Yoav Nir
On Mar 6, 2011, at 11:25 AM, Yoav Nir wrote: > > There's peer-initiated ERP (which would require peer-initiated IKE?) and > multiple simultaneous operations. I think it may come to a somewhat larger > draft. Sorry. peer=remote access client, so peer-initiated IKE is the norm. They real chang

[IPsec] HOKEY draft draft-ietf-hokey-rfc5296bis

2011-03-06 Thread Yoav Nir
Hi all I have just read the subject draft, and found this in section 6 (and similar text in the introduction): Note that to support ERP, lower-layer specifications may need to be revised. Specifically, the IEEE802.1x specification must be revised to allow carrying EAP messages of the n