Reviewer: Menachem Dodge
Review result: Has Nits
This document is well written and very readable.
Nits
----
Section 5.3: The first paragraph appears to be repeated. It appears at the end
of page 11 and also at the start of page 12.
Section 5.4 first paragraph:
OLD --> "This information is incorporated to a list of NSFs under its control"
Suggest --> This information is incorporated in a list of NSFs under its
control"
Section 8: Security Considerations:
OLD --> In particular, the I2NSF Controller will handle cryptographic material
so that the attacker may try to access this information. Although we can
assume this attack will not likely
to happen due to the assumed security measurements to protect the I2NSF
Controller, it deserves some analysis in the hypothetical case the attack
occurs.
Suggest --> In particular, the I2NSF Controller will handle cryptographic
material thus the attacker may try to access this information. Although we can
assume this attack is not likely
to happen due to the assumed security measurements to protect the I2NSF
Controller, it still deserves some analysis in the hypothetical case that
the attack occurs.
Section 8.1 last bullet
OLD --> If certificates are used, the NSF MAY generate the private key and
exports the public key for certification to the I2NSF Controller. How the NSF
generates these cryptographic material (public key/ private keys) and exports
the public key it is out of scope of this document.
Suggest --> If certificates are used, the NSF MAY generate the private key and
export the public key for certification to the I2NSF Controller. How the NSF
generates these cryptographic material (public key/ private keys) and exports
the public key, is out of scope of this document.
_______________________________________________
I2nsf mailing list
I2nsf@xxxxxxxxhttps://www.ietf.org/mailman/listinfo/i2nsf
