The IETF Last Call on IKEv2bis is now over (but comments are still welcome). I
have made the following changes to the draft. I'll turn in the draft on Monday
after the face-to-face meeting, and our new AD will then put it on a future
IESG telechat. You'll have plenty of time to review the diffs before that
telechat so you can tell me if I muffed anything.
Thanks again for all the input!
--Paul Hoffman
D.16. Changes from draft-ietf-ipsecme-ikev2bis-08 to
draft-ietf-ipsecme-ikev2bis-09
These changes came during IETF Last Call.
Fixed some minor editorial nits.
In 1.3, changed "this notify" to "this notification".
In 2.6, changed "will cause two packets:" to "will cause two packets
to be sent:".
Moved the paragraph that starts "When the IKE_SA_INIT exchange does
not result" from 2.7 to 2.6. Also changed"the responder's SPI will
be zero" to "the responder's SPI will be zero also in the response
message".
In 2.8.2, last paragraph: Change the beginning of the sentence and
changed "older peers may receive these notifications" to "older peers
that implement RFC 4306 but not this document may receive these
notifications".
Fixed the first two paragraphs of 2.9 to talk about PFKEY in the
correct context.
In 2.23, clarified the paragraph that starts "An initiator can
use..." in many places, saying that it is UDP encapsulated ESP.
In 3.3.6, changed "If one of the proposals offered is for the Diffie-
Hellman group of NONE, the responder MUST ignore the initiator's KE
payload and omit the KE payload from the response" to "If one of the
proposals offered is for the Diffie-Hellman group of NONE, and the
responder selects that Diffie-Hellman group, then it MUST ignore the
initiator's KE payload and omit the KE payload from the response".
[Issue #176]
In 3.5, changed "IPv6-only implementations MAY be configurable to
send only ID_IPV6_ADDR instead of ID_IPV6_ADDR for IP addresses" to
"IPv6-only implementations MAY be configurable to send only
ID_IPV6_ADDR instead of ID_IPV4_ADDR for IP addresses".
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
