Nicely written that makes it so much easier to review. Thanks.
My comments in no particular order:
1. This document updates RFC 5996. I know one of my fellow ADs will ask
why this is an updates before they get to s2. Can we add something to
the introduction that says "This document updates RFC 5996 by providing
new requirements for all IKEv2 implementations" or something like that.
2. s1/s3 indicates parts are taken from RFC 2412. Did you ask Hilarie
if she was willing to grant you rights to publish under the current
IETF's TLP in order to avoid including the pre-5378 boilerplate? In a
nut shell if you copy text from an RFC before RFC 5378 you gotta ask.
If you don't get an answer you need to include some additional
boilerplate that says the draft includes pre-5378 text. All you need do
is send her a message (I'd try [email protected]) explaining the situation
and asking if she'd be willing to grant rights under the TLP
(http://trustee.ietf.org/license-info/). Just forward the response to
me so I know was done. If you'd rather not bother that's okay but then
you need to add the following to the end of the copy right notice section:
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10,
2008. The person(s) controlling the copyright in some of this material
may not have granted the IETF Trust the right to allow modifications of
such material outside the IETF Standards Process. Without obtaining an
adequate license from the person(s) controlling the copyright in such
materials, this document may not be modified outside the IETF Standards
Process, and derivative works of it may not be created outside the IETF
Standards Process, except to format it for publication as an RFC or to
translate it into languages other than English.
3. s2.3: RFC 5114 uses y^2 = x^3 + ax + b (mod p) instead of y**2 = x**3
+ ax + b mod p maybe best to stick with what's there or explain explain
that it's different.
4. s1: r/elliptic curve groups/Elliptic Curve (EC) groups
the term gets used later so you might as well introduce it early on
5. s3: r/ECC groups/EC groups or change it in s1 to match this section
5. s2.3/3: Seems like in s3 you added "*" to signify multiplication
should you also do that in s2.3 to keep them consistent?
6. Please don't forget to incorporate Johannes suggestion.
spt
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
