![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
In case you were wondering, the ipsecme Issue Tracker is available at: http://trac.tools.ietf.org/wg/ipsecme/trac/report Right now all we have is Tero’s comments on IKEv2-bis. But there
are more coming. Thanks, Yaron -----Original Message----- > I think that's a good idea, although what would they use for the > initial message ID for the new IKE SA. A random value?
The MsgIDs > from the old SA? They used the message id from old SA. Some also misread the "The IKE_SA initial setup messages will
always be number 0 and 1." to mean that no other messages can be with
message id 0 or 1 than those IKE SA setup messages (i.e. they had special handling for message id 0 packets). > Paul, I think we can accept this and move that last sentence to
the > main part of the message ID description. -- kivinen at safenet-inc.com _______________________________________________ IPsec mailing list IPsec at ietf.org https://www.ietf.org/mailman/listinfo/ipsec Scanned by Check Point Total Security Gateway. |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ IPsec mailing list IPsec at ietf.org https://www.ietf.org/mailman/listinfo/ipsec