At 11:46 PM +0300 5/9/10, Yaron Sheffer wrote: >RFC 4306 is the main specification for IKEv2, and RFC 4307 provides details >that are necessary to implement IKEv2 in an interoperable manner. So why do >you think that an Informative reference is more appropriate here? > >The relevant background, FWIW, is >http://www.ietf.org/iesg/statement/normative-informative.html.
The information in RFC 4307 is not required in order to implement the protocol in RFC 4306. It is required to interoperate in the most general sense only, that is, to interoperate with partners with whom you do not have prior arrangements. Some can read RFC 4306 without RFC 4307 and make an implementation that will interoperate just fine between organizations that communicate about their crypto preferences. Thus, the information in 4307 is informative but, if it makes you happy to make it a normative reference, there is no problem with that. Note that Russ Housley has a valid reason for asking for the reference to 4307 to be informative: other security protocols such as S/MIME have their 4307-equivalents as informative references. --Paul Hoffman, Director --VPN Consortium _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
