Tero Kivinen wrote:
> pasi.ero...@nokia.com writes:
> > Paul Hoffman wrote:
> >
> > > >B.1 (Group 1): We may want to add: "Use of this group is NOT
> > > RECOMMENDED."
> > >
> > > Please open a tracker issue for this. Even though this is obvious,
> > > it is a tad late to be suggesting new normative language.
> >
> > This "NOT RECOMMENDED" would belong in an update to RFC 4307,
> > not this document.
> 
> The current RFC4306 Security Considerations section already says:
> 
>             Group one is for historic purposes only and does not
>    provide sufficient strength except for use with DES, which is also
>    for historic use only.
> 
> and I would think that group and algorithms which are historic use
> only, are also NOT RECOMMENDED...
> 
> And yes, I agree it should really be in RFC4307, but the group is
> defined here, so word of it not being recommended, might be good idea
> in this document too.

Hmm... I think the current security considerations text is quite 
sufficient to discourage people from using this, and repeating the same 
thing with upper-case RFC 2119 keywords doesn't seem to add anything
(and we have earlier agreed those keywords belong in a separate 
document anyway).

Best regards,
Pasi
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to